having physical memory dump issues with K8V Deluxe

[THELAIR]

Hey guys,

Setup is as follows
Asus K8V Deluxe 1004 BIOS (latest)
Athlon64 3000+ (stock OEM HS/F)
Corsair 512MB XMS PC3200 Low Latency DDR CL2 w/ Platinum Heatspreader (CMX512-3200LLPT)
ATI AiW 9600 Pro latest catalyst drivers etc
2x WD Raptor's in RAID 0 on VIA SATA raid controller
1x WD 250GB SATA on Promise SATA raid controller (not in raid mode)
Plextor 8x DVD burner
SB Audigy 2 ZS
Win XP SP1
default bios settings, nothing overclocked. Disabled onboard audio.

According to the Asus manual, with 2 dims, whether they be single or dual sided (how the hell can i tell??) the memory chips should be occupying DIMS 1 and 2 (of the 3). I have done that.

However i am still experiencing intermittent blue screen of death physical memory dumps.

It's quite odd, I can go a few days playing games, and everything is fine, then reboot for whatever reason, and blam winXP loads into a blue screen.

The latest issue happened when I applied some further Windows XP updates, now I can not get windows XP to load one way or another, even safe mode. Loading last known good configuration also failed, making me think its still somehow hardware related.

What is wrong? Is it my RAM? Faulty motherboard?

I experienced physical memory dumps on both the 1002 bios and 1004 bios.

any insight appreciated.

I hate the feeling of an untrustyworthy, unstable system.

 

[Peter]

Don't ask. Test. www.memtest86.com

 

[mechBgon]

What voltage is your memory set for, and what timings is it set for? What brand, model and wattage of power supply do you have?


<-- *senses the need to download a copy of the K8V Deluxe owners' manual in PDF format very soon*

 

[JC]

Originally posted by: Peter
Don't ask. Test. www.memtest86.com

Yeah, but....

I used memtest86 on my KG7 (2x XMS3200LLPT-256) and got loads of errors at test #5 (thread). I still couldn't tell if it was the mobo or the RAM. Now having changed out the KG7 for an A7N8X, memtest reports no errors.

JC

 

[Peter]

Interpreting the results gives you a good idea of whether the RAM is bad or the mainboard. If you get random errors all over the place, then you got a signalling or timing issue, often caused by too aggressive BIOS settings or actually a faulty mainboard. If you get rather static and reproducable error locations, it's a typical case of bad bit cells in the DIMM.

 

[JC]

Originally posted by: Peter
Interpreting the results gives you a good idea of whether the RAM is bad or the mainboard. If you get random errors all over the place, then you got a signalling or timing issue, often caused by too aggressive BIOS settings or actually a faulty mainboard. If you get rather static and reproducable error locations, it's a typical case of bad bit cells in the DIMM.

Well in that thread I linked to, I detailed how I backed down timings, tried one/both sticks, and how the errors always occurred at test #5. And yet, it proved to be a mobo issue in the end. So much for logical interpretation

 

[Peter]

Test #5 is the toughest for timing and signalling issues, so much is for sure. The fact that you got so many errors in that test would have indicated to me that it's either a mainboard related problem (timing/signalling) or a DIMM whose advertized speed is higher than what it actually achieves.

 

[wkabel23]

When I got an Asus board the Onboard LAN and the USB 2.0 Drivers kept giving me problems, see if that works.

Other than that, how do you like the AMD 64 3000+? Please post your opinions, mine is coming in a few days (with the same board).

 

[wkabel23]

Try disabling Legacy USB if it is on. I've heard this can cause problems on Asus boards for P4s.

 

[Tbirdkid]

disable everything. and make sure your fsb spread spectrum is set to .50 along with the agp spread spectrum. i had the same issue.... that was it. also, try to find a new updated bios

 

[THELAIR]

Update, I havnt run memtest yet, but I did a new reinstall of the system after having set the memory settings to their lowest/slowest settings, and so far so good, no memory dumps yet.