![]() |
||
New Member
加入日期: Nov 2005
文章: 2
|
請教各位前輩,MEMTEST86+ 1.65其#1~#8測試項目的意義為何?
請教各位前輩,MEMTEST86+ 1.65其#1~#8測試項目的意義為何
我測出的結果#5~#8都有不良,但偶而換一下MODULE順序又會測不到 那我該如何處理? |
|||||||
![]() |
![]() |
Major Member
![]() 加入日期: Jun 2004
文章: 120
|
只要出現 error
就是有問題了 送修吧
__________________
![]() 響應 點擊 廣 告 支 持 PCDVD ================================ CPU:Mobile AMD Athlon 64 3000 (Oakville) M/B:MSI K8N NEO P (nForce3-250) RAM:TR-UCCC(649) /1G*2 (CL:3-3-3-8) VGA:ATI-REDAN9550 (256MB) NIC:nForce3 & POWER:HEC 335W HD:MAXTOR 40G & DVD+R: BENQ 1620 CDRW:GIGABYTE GO-R5232 Monitor: PHILIPS 170B5//DECAVIEW GF387 |
||
![]() |
![]() |
Advance Member
![]() ![]() 加入日期: Aug 2001 您的住址: 台北
文章: 326
|
參考看看吧
Memtest86+ 的Test 5和8 |
![]() |
![]() |
Major Member
![]() 加入日期: Feb 2005
文章: 193
|
要測多久才算阿...
跑個一圈 沒出現錯誤但是..... 要很多圈才準嗎?
__________________
*HMK-02 [CPU] AMD Athlon64 754 2800+ oc 3200+ ( 245*9 長期測試穩定中 ) 超不動~烙賽 ![]() [M/B] MSI K8N Neo-FSR ( 爛板為什麼不能跑同步 ) ![]() [RAM] Transcend SumSung DDR400 UCCC 1G [VGA] ATi Radeon 9700PRO ( 331/277 記憶體時脈上不去 ) ![]() [HDD1] Hitachi 160G/8M HDS722516VLAT80 [HDD2] Seagate 80G/2M ST380011A [DVD-RW] Pioneer A08XLA & BenQ 1640 [PSU] SeaSonic S12 380W ![]() [Mouse] Logitech Optical Mouse MX518 [Monitor] BENQ FP791 17' LCD *HMK-01 [CPU] AMD AthlonXP Barton 2500+ (沒鎖倍頻 ![]() [M/B] ASUS A7V8X-X (不能上200外頻的爛板 ![]() [RAM] ? DDR400 512MB [VGA] nVIDIA FX 5200 [HDD] Seagate 160G/8M [DVD-RW] NEC 3520A [Power] ? 350W [Mouse]Logitech Optical Mouse [Monitor]CRT IMAI 17' |
![]() |
![]() |
Elite Member
![]() ![]() ![]() ![]() ![]() 加入日期: Mar 2001 您的住址: Rivia
文章: 7,028
|
基本上PASS一次我是覺得還不夠
因為現在不用二十分鐘就PASS一次了,RAM可能還不夠熱 如果是測穩定度我建議至少RUN個一個小時以上吧 以前測朋友的電腦,從發生的情況來看判斷應該是RAM出了問題 實際測試的時候,是到了第三圈才出現ERROR的,朋友電腦無超頻 所以RAM是真的壞了,果然拔下來之後電腦就正常了
__________________
Folding@home with GPGPU集中討論串 Unix Review: ArchLinux●Sabayon●OpenSolaris 2008.5●Ubuntu 8.10 AVs Review: GDTC●AntiVir SS●ESS●KIS 09●NIS 09●Norton 360 V3 ![]() I Always Get What I Want. |
![]() |
![]() |
New Member
加入日期: Nov 2005
文章: 2
|
我只查到這些,哪位英文高手,幫忙"翻"一下
Memtest86 executes a series of numbered test sections to check for errors. These test sections consist of a combination of test algorithm, data pattern and caching. The execution order for these tests were arranged so that errors will be detected as rapidly as possible. Tests 8, 9, 10 and 11 are very long running extended tests and are only executed when extended testing is selected. The extended tests have a low probability of finding errors that were missed by the default tests. A description of each of the test sections follows: Test 0 [Address test, walking ones, no cache] Tests all address bits in all memory banks by using a walking ones address pattern. Errors from this test are not used to calculate BadRAM patterns. Test 1 [Moving Inv, ones&zeros, cached] This test uses the moving inversions algorithm with patterns of only ones and zeros. Cache is enabled even though it interferes to some degree with the test algorithm. With cache enabled this test does not take long and should quickly find all "hard" errors and some more subtle errors. This section is only a quick check. Test 2 [Address test, own address, no cache] Each address is written with its own address and then is checked for consistency. In theory previous tests should have caught any memory addressing problems. This test should catch any addressing errors that somehow were not previously detected. Test 3 [Moving inv, 8 bit pat, cached] This is the same as test zero but uses a 8 bit wide pattern of "walking" ones and zeros. This test will better detect subtle errors in "wide" memory chips. A total of 20 data patterns are used. Test 4 [Moving inv, 32 bit pat, cached] This is a variation of the moving inversions algorithm that shifts the data pattern left one bit for each successive address. The starting bit position is shifted left for each pass. To use all possible data patterns 32 passes are required. This test is very effective at detecting data sensitive errors in "wide" memory chips. Test 5 [Block move, 64 moves, cached] This test stresses memory by using block move (movsl) instructions and is based on Robert Redelmeier's burnBX test. Memory is initialized with shifting patterns that are inverted every 8 bytes. Then 4MB blocks of memory are moved around using the movsl instruction. After the moves are completed the data patterns are checked. Because the data is checked only after the memory moves are completed it is not possible to know where the error occurred. The addresses reported are only for where the bad pattern was found. Since the moves are constrained to a 8MB segment of memory the failing address will always be lest than 8MB away from the reported address. Errors from this test are not used to calculate BadRAM patterns. Test 6 [Modulo 20, ones&zeros, cached] Using the Modulo-X algorithm should uncover errors that are not detected by moving inversions due to cache and buffering interference with the the algorithm. As with test one only ones and zeros are used for data patterns. Test 7 [Moving inv, ones&zeros, no cache] This is the same as test one but without cache. With cache off there will be much less interference with the test algorithm. However, the execution time is much, much longer. This test may find very subtle errors missed by tests one and two. Test 8 [Block move, 512 moves, cached] This is the same as test #5 except that we do a lot more memory moves before checking memory. Errors from this test are not used to calculate BadRAM patterns. Test 9 [Moving inv, 8 bit pat, no cache] This is the first extended test. By using an 8 bit pattern with cache off this test should be effective in detecting all types of errors. However, it takes a very long time to execute and there is a low probability that it will detect errors not found by the previous tests. Test 10 [Modulo 20, 8 bit, cached] This is the first test to use the modulo 20 algorithm with a data pattern other than ones and zeros. This combination of algorithm and data pattern should be quite effective. However, it's very long execution time relegates it to the extended test section. Test 11 [Moving inv, 32 bit pat, no cache] This test should be the most effective in finding errors that are data pattern sensitive. However, without cache it's execution time is excessively long. |
![]() |
![]() |
Major Member
![]() 加入日期: Feb 2003
文章: 158
|
![]() Memtest86 V3.2 與 Memtest86+ V1.65這兩種版本有啥差異?
|
![]() |
![]() |