BSOD! *grrr*

[usasma]

Well, it's either the memory or your motherboard.
Memory is cheaper than most motherboards - and is far easier to replace.

This quote seems to refer to the problem that you're experiencing (from this link: Memtest86.com - Memory Diagnostic ) Bold/Underline is mine.

Memory Testing Philosophy There are many good approaches for testing memory. However, many tests simply throw some patterns at memory without much thought or knowledge of memory architecture or how errors can best be detected. This works fine for hard memory failures but does little to find intermittent errors. BIOS based memory tests are useless for finding intermittent memory errors.
Memory chips consist of a large array of tightly packed memory cells, one for each bit of data. The vast majority of the intermittent failures are a result of interaction between these memory cells. Often writing a memory cell can cause one of the adjacent cells to be written with the same data. An effective memory test attempts to test for this condition. Therefore, an ideal strategy for testing memory would be the following:

1. write a cell with a zero
2. write all of the adjacent cells with a one, one or more times
3. check that the first cell still has a zero

It should be obvious that this strategy requires an exact knowledge of how the memory cells are laid out on the chip. In addition there is a never ending number of possible chip layouts for different chip types and manufacturers making this strategy impractical. However, there are testing algorithms that can approximate this ideal.

Sounds to me that the chips are letting information "bleed" over into adjacent chips - and the soft reset doesn't flush this out (while the hard reset does).

My guess is that it's the memory modules themselves - but that will have to be determined by trying other memory chips. Your money - your call. Good luck!

 

[adrift]

I'm not sure what it is about Windows 7 that makes it crash, but if you look at reviews on something like Newegg for later model versions of Corsair you'll see all types of folks complaining about their RAM crashing their OS's on them after about 6 to 9 months of use.

I wanted to make a correction to this post. Someone pointed out that I said Corsair when I mean Crucial. Corsair is typically very well reviewed memory, but I still think you were having some sort of heating/timing/voltage issue. I don't think your board is to blame but I could be wrong.

Ever since tweaking my Crucial memory I haven't had issues.

 

[diabillic]

I myself have a P5 series ASUS board running x64 RTM and haven't had an issue myself. Also had the RC build on here as well. What type of issues have been plaguing those boards?

 

[Halmeo]

(sorry for my bad eng)

I had the same problem for over 1 month with my gtx260.
Tested new drv and tdr fix all that you can do.

The card was tested at dealer and no problem. Replaced mobo, bought new memory new hdd .. still same problem. Bought e new nexus 600w powersupply.

Nothing did help.

This was the solution.

I downloaded nvflash. Made a bootable usb stick. Made a copy of my gtx260 bios with nvflash.

Modified the bios using NiBitor. Changed the value voltage (extra) from 1.12v to 1.06v

After that working fine.. Get the same points in 3dmark 06 and vantage. But my system is stable.. And i never get nvlddmkm bsod anymore
Here is a page that can help u flashing bios.
*GTX 260/280 Unofficial TPU! Thread* - techPowerUp! Forums