loafer87gt
Limp Gawd
- Joined
- Feb 2, 2005
- Messages
- 466
I have been pulling my hair out for about the past month trying to figure out the cause of my random BSOD on my new Kentsfield build. 90% of the time I was getting a NV4disp.dll error leading me to believe that the Nvidia Forceware drivers were at fault. Anyways, in the past weeks the errors had become more frequent, and Tuesday morning I had an IRQ not less than equal error which led me to fire up memtest to once again test my modules. Immediately, I noticed a series of errors come up. Testing each of my four 1GB sticks at a time, I found one stick that generated a series of errors with the program. Pulling it out, and running just two of the modules, things appear rock solid, and I haven't had a program crash yet.
Could this module have been the source of my problems all along? When I had my first crash about a month ago, I ran memtest to see if it was a memory related problem and it ran through all night without a hitch. Is there any chance that Windows was stressing the module more than memtest and thats why I was having the random crashes?
Anywhoo, its nice to have things nice and stable again.
Could this module have been the source of my problems all along? When I had my first crash about a month ago, I ran memtest to see if it was a memory related problem and it ran through all night without a hitch. Is there any chance that Windows was stressing the module more than memtest and thats why I was having the random crashes?
Anywhoo, its nice to have things nice and stable again.