Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Need help identifying cause of constant BSOD
New Posts  All Forums:Forum Nav:

Need help identifying cause of constant BSOD - Page 2

post #11 of 19
Nah, that's not a temperature you should be worrying about, especially in this upcoming warm weather.

Rather than there being a crash dump in C:/Windows/Minidump, it may have written a MEMORY.DMP dump in C:/Windows itself. Is there one in there with a date that corresponds to your latest crash?
post #12 of 19
Thread Starter 
No "memory.dmp" under C:/windows mellowsmiley.gif
post #13 of 19
Interesting.

Well, while we wait for another BSOD to occur and another dump to work with, have you run Memtest yet as I have recommended in my earlier post? There are many reasons for dumps not being written, memory issues is one of them.
post #14 of 19
Thread Starter 
I have tried memtest in the past and i didn't get any error after 10 passes. will try it again.
post #15 of 19
Yeah, do it again. "In the past" can mean a lot of things with hardware wink.gif
post #16 of 19
Thread Starter 
Had another bsod without actually playing anything. No dump file was made either. hmmsmiley02.gif

Haven't had the chance to run memtest yet but i will get to it soon.
post #17 of 19
Quote:
Originally Posted by Boxes View Post

Had another bsod without actually playing anything. No dump file was made either. hmmsmiley02.gif
Haven't had the chance to run memtest yet but i will get to it soon.

Let me know when you do.
post #18 of 19
Thread Starter 
So I ran memtest on one of my 4gig sticks of ram for 10 passes (took a while sleepsmiley02.gif) and i didn't get any errors. I decided to leave the other 4gig stick out and so far i haven't had any problems.
post #19 of 19
Now that you've passed on one stick, I'd recommend testing the other smile.gif
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Need help identifying cause of constant BSOD