I have not flashed BIOS. I hate doing that, but I guess I'm about out of options.

I'll try the single DIMM thing again. I played around with that a couple weeks ago, but I was only trying to run fallout 3 at the time. I'll give it a more comprehensive test.

As to the driver issue, is there any way to tell, by the error messages, what driver is causing the issue? That's been the most frustrating part of this whole experience. If I just knew where the problem was......

Anyway, will post back after I've tried the above.

Hi there, I'm going to ask Madmonkey to take a look at those codes.
In the mean time, if you could follow
http://www.pchelpforum.com/blue-scre...een-death.html
That would be great.

Hi Jay,

Thanks for weighing in. I typically do not get BSOD's, rather just crashes to desktop with the generic "(insert application) has encountered an error and needs to close. Sorry for the inconvenience."

Is there something I can do with that dialogue box that might help? I can EASILY reproduce there errors, so let me know and I can cook something up pretty quick.

As always, thanks for all your help guys.

E.D. Wayne

Alright guys, status update:

Took out each DIMM and ran the system on each one independently. Produced the same errors.

I switched around the DIMM slots used. Nothing there.

Tried running Memtest86 on the PAIR of DIMMS. I hadn't done that before as I had read that running MemTest on DIMMS in pairs can produce false errors. Well, I tried it anyway. Would not complete the test.

I got this. Don't know what it means, but maybe it can help:

Unexpected Interrupt

Type: 00000100
PC: c483d089
CS: 5f5e5b0c
Eflag: 5755c35d
Code: d231e375
DS: c0feffca
SS: 8310c483

I also flashed the BIOS. Went fine, except for one interesting little note. On the very first reboot after the flash, I got a CMOS checksum error. But I went into BIOS, re-enabled my raid controller and sata ports and set the boot priority, and I haven't had an issue since. Just that once. I don't know if that means anything, but I found it interesting.

One other thing. I wanted to completely rule out GPU overheating, so I downloaded the hardware monitor from CPUID and ran 3DMark 06 to put the system under load. Under load, the GPU clocked at 60 deg Celcius. Should be good. I checked some forums, and that's actually a little below avergae for a GTX 285. Most people seem to run in the mid 70's under load, or at least those that aren't using advanced aftermarket cooling solutions. Max GPU temp as listed by NVidia's tech specs is 105 deg Celcius. So I think I'm okay there.

But, before 3D Mark crashed (yes, it crashes too), I got some graphical artifacts. And then I finally got a real error message!

"nv4_disp display driver has stopped working normally. Please save your work and reboot."

So, obviously my video driver didn't care for SOMETHING I was doing. Sadly, I still don't know what the something is.

Well, that's all I've got for now.

Thanks again for all your help guys. I appreciate it.

E.D. Wayne

Oh, hey. Those errors create dmp files as well. Here are a few I managed to dig up. Must have been around for awhile.

Hope these help.

Nice!

Hi Evil (welcome to PCHF by the way).

The logs are showing memory corruption, and the fact your experiencing issues during a memtest really confirms it for me. Memory problems are usually the result of faulty memory (obviously), overclocking or undervoltage. Motherboard or PSU related issues are less likely but still possible.