Hello. I'm putting together a retro-gaming rig and I've encountered a problem. The motherboard is a QDI Kudoz 7x with 3 RAM slots + an AMD AthlonXP 2100+. The result of Memtest is always the same - it shows about 8 errors within the first few seconds of testing (so it's probably test 0 that fails), but after that it continues without any further errors. I have 4 sticks of DDR1 RAM (2 each from different manufacturers and different speeds). I've tried installing them individually into different slots. CMOS settings have been reset, I've tried manually adjusting memory timings etc., but the result is always the same. Is it possible that it's actully the CPU that's failing, say the L2 Cache? Thanks.
Memtest86+ fails within a few seconds with about 8 errors, then no mor
#1
Posted 06 January 2013 - 03:14 AM
#2
Posted 06 January 2013 - 04:01 AM
"GilliumX58" DESKTOP OCC Cool Club Member
Mobo: Asus P6TD Deluxe | Processor: Intel Core i7 920 @ 4ghz | CPU Cooler: Zalman CNPS9900MAXR | Videocard: MSI Twin Frozr HD7950
Memory: OCZ/Patriot 18GB 1600mhz | OS SSD: SanDisk Extreme 240GB SATA | PSU: PC Power & Cooling Silencer 750W
Monitor: *Debranded* HP 24" 2408H | CD/DVD: Samsung SH-S223F | Keyboard: Razer Tarantula | Mouse: Razer Lachesis
#3
Posted 06 January 2013 - 04:05 AM
Yes, same result. I know for a fact that at least 2 of the 4 RAM sticks work 100%, so I guess either the motherboard or the CPU is faulty. It seems weird, though, that all 3 RAM slots would fail ...
#4
Posted 06 January 2013 - 09:19 AM
Disable your USB Legacy Support, and retest each module individually.
Intel Core i7-3960X Asus P9X79-E WS, Nvidia Quadro K5000 & Tesla K20 in Maximus, Kingston KHX21C11T3FK8/64X, Seagate 600 Pro Series 240GB SSD X2, Seagate Constellation ES.3 1TB HDD X6 RAID-5, XSPC Hive Series H1 Cube, LEPA G1600-MA, Aquacomputer Airplex Modularity & EK Water Cooling, Windows 7 Ultimate 64-Bit, Dassault Systemes.
Intel Core i7-3930K Asus P9X79 Pro, Evga GTX770 Classified w/ACX 4GD5 in SLI, G.Skill Trident X Series F3-1600C7Q-32GTX, Samsung 840 Pro Series 256GB SSD, Corsair Carbide Series Air 540 Cube, Corsair Hydro Series H110, Corsair AXi AX1200i, Razer BlackWidow Ultimate & DeathAdder, Windows 7 Pro 64-Bit
#5
Posted 06 January 2013 - 10:22 AM
Great news, I seem to be getting somwhere! After loading the BIOS fail-safe defaults (instead of the optimized defaults), Prime95 has been running stable for half an hour now. Before, it would crash after about 5 mins. Time to zone-in on the BIOS setting that's causing this ... @Braegnok, I don't have any options like that, except for USB-keyboard support.
#6
Posted 06 January 2013 - 10:32 AM
When running MemTest, it's best to disable USB support in your BIOS, as in some cases it will cause false errors.
Edit : testing @ default settings, is good also.
Edited by Braegnok, 06 January 2013 - 01:02 PM.
Intel Core i7-3960X Asus P9X79-E WS, Nvidia Quadro K5000 & Tesla K20 in Maximus, Kingston KHX21C11T3FK8/64X, Seagate 600 Pro Series 240GB SSD X2, Seagate Constellation ES.3 1TB HDD X6 RAID-5, XSPC Hive Series H1 Cube, LEPA G1600-MA, Aquacomputer Airplex Modularity & EK Water Cooling, Windows 7 Ultimate 64-Bit, Dassault Systemes.
Intel Core i7-3930K Asus P9X79 Pro, Evga GTX770 Classified w/ACX 4GD5 in SLI, G.Skill Trident X Series F3-1600C7Q-32GTX, Samsung 840 Pro Series 256GB SSD, Corsair Carbide Series Air 540 Cube, Corsair Hydro Series H110, Corsair AXi AX1200i, Razer BlackWidow Ultimate & DeathAdder, Windows 7 Pro 64-Bit
#7
Posted 06 January 2013 - 01:59 PM
I'm baffled... The system is now running rock stable at even tighter BIOS and RAM settings than before, no sign of any errors. Ah well, lesson learned. If anyone experiences the same symptoms - namely, if you install some RAM into a machine and you're 100% certain that the RAM works, you might try running the BIOS with fail-safe defaults. BTW, I cleared the CMOS like three time before, but that always loads the optimized defaults.
#8
Posted 06 January 2013 - 03:13 PM
There must have been a timing setting off deep in the settings I'm guessing, something regarding the memory that wouldn't be easy to see but would invalidate stability quickly
"GilliumX58" DESKTOP OCC Cool Club Member
Mobo: Asus P6TD Deluxe | Processor: Intel Core i7 920 @ 4ghz | CPU Cooler: Zalman CNPS9900MAXR | Videocard: MSI Twin Frozr HD7950
Memory: OCZ/Patriot 18GB 1600mhz | OS SSD: SanDisk Extreme 240GB SATA | PSU: PC Power & Cooling Silencer 750W
Monitor: *Debranded* HP 24" 2408H | CD/DVD: Samsung SH-S223F | Keyboard: Razer Tarantula | Mouse: Razer Lachesis
#9
Posted 06 January 2013 - 03:31 PM
maybe it was grumpy and needed the dust knocked off of it. LOL
"It works Because I threatened it.
" - " did you show it the sledgehammer" - "No, A flight of stairs"
"I don't want to be much of a forum Nazi but this situation calls for a hail Bosco and blitzkrieg someone".
If that does not work I hop in a Madcat and Blast it to microscopic Particles.
#10
Posted 07 January 2013 - 08:09 AM
I'm baffled... The system is now running rock stable at even tighter BIOS and RAM settings than before, no sign of any errors. Ah well, lesson learned. If anyone experiences the same symptoms - namely, if you install some RAM into a machine and you're 100% certain that the RAM works, you might try running the BIOS with fail-safe defaults. BTW, I cleared the CMOS like three time before, but that always loads the optimized defaults.
Possible result of cleaning up the accumulated dusts and unwanted particles. ![]()

#11
Posted 07 January 2013 - 09:04 AM
No, not really:) It turns out it was most probably the tRCD timing. In BIOS, it's currently set to 3, but Aida64 reports it as 5. Works like a charm though. Also, the BIOS doesn't seem to know how to read the SPD timings properly, they're completely off, so I've set them manually. Oh, and another extra piece of advice for those of you who might want to get an older system up and running - WaybackMachine is your friend if you're looking for a BIOS for an old motherboard whose manufacturer and their website no longer exists:)
Basically, the only reason I brough this zombie to life was to utilize a soundcard that uses both A3D1.0, EAX1.0/2.0 and DirectSound3D capabilities along with Sensaura's HRTF algorithms. Thief 1 sure sounds great now with headphones and it's real easy to tell where your opponents are.
Edited by Enron x86, 07 January 2013 - 09:09 AM.
#12
Posted 07 January 2013 - 11:40 AM
I knew itNo, not really:) It turns out it was most probably the tRCD timing. In BIOS, it's currently set to 3, but Aida64 reports it as 5. Works like a charm though. Also, the BIOS doesn't seem to know how to read the SPD timings properly, they're completely off, so I've set them manually. Oh, and another extra piece of advice for those of you who might want to get an older system up and running - WaybackMachine is your friend if you're looking for a BIOS for an old motherboard whose manufacturer and their website no longer exists:)
Basically, the only reason I brough this zombie to life was to utilize a soundcard that uses both A3D1.0, EAX1.0/2.0 and DirectSound3D capabilities along with Sensaura's HRTF algorithms. Thief 1 sure sounds great now with headphones and it's real easy to tell where your opponents are.
Edited by boinker, 07 January 2013 - 09:38 PM.
language
"GilliumX58" DESKTOP OCC Cool Club Member
Mobo: Asus P6TD Deluxe | Processor: Intel Core i7 920 @ 4ghz | CPU Cooler: Zalman CNPS9900MAXR | Videocard: MSI Twin Frozr HD7950
Memory: OCZ/Patriot 18GB 1600mhz | OS SSD: SanDisk Extreme 240GB SATA | PSU: PC Power & Cooling Silencer 750W
Monitor: *Debranded* HP 24" 2408H | CD/DVD: Samsung SH-S223F | Keyboard: Razer Tarantula | Mouse: Razer Lachesis













