Sign in with
Sign up | Sign in
Your question
Closed

BSOD caused by ntoskrnl.exe

Last response: in Windows 7
Share
September 16, 2012 3:54:39 PM

So I've been looking around the web to see if I could find someone in a similar situation I was in, and haven't found anything that would fix this problem -_- So I thought I'd try my luck just asking for help.

Basically my computer likes to bluescreen left and right and I don't know what to do about it.

Here are all the dump files(not many because I reinstalled windows in hopes of it stopping):
https://rapidshare.com/files/3921902664/091512-21496-01...
https://rapidshare.com/files/2512611484/091412-37175-01...
https://rapidshare.com/files/1486798386/091612-16192-01...
https://rapidshare.com/files/102173744/091612-20904-01....

Thanks in advance for all your help!

forgot to mention:
I have Windows 7 64 Bit SP1

Update: Just got a new blue screen, and it seems that there's another problem... here's the dumpfile:
https://rapidshare.com/files/4178354657/091612-17253-01...
September 16, 2012 4:04:11 PM

What OS are you using (ie WinXP 32bit or Win7 32bit or 64bit)? I'll analyze your dmp file if you let me know.
September 16, 2012 4:15:13 PM

oh I thought windows 7 was implied by the forum I posted this in lol, but it's windows 7 x64 SP1, specifically Home Premium (although I don't think that's relevant)
Related resources
September 16, 2012 6:06:54 PM

let me know if you need any other information!
September 16, 2012 6:55:07 PM

No, you're good - I just have work today and my clients will get pissed if I'm answering free forum questions on their dime. I'll get this taken care of ASAP.
September 16, 2012 6:55:55 PM

No problem at all, take your time :) 
September 17, 2012 6:01:01 AM

OK - I think the issue is a bad piece of RAM based on the bugcheck codes you are getting. We can test this by you pulling all but one stick out and running the computer like normal. If you get a BSOD or if it won't start, swap it for another stick. What is your RAM configuration?

I couldn't get a definitive answer from your minidmps because of a /nodebug switch that is apparently in a configuration file somewhere on your computer.

To get more detailed minidumps, you can turn on the driver verifier:

http://www.sevenforums.com/crash-lockup-debug-how/65331...

After this gets turned on your crash dumps will be much more verbose and detailed and it will help us get to the bottom.

Let's start by doing the RAM test above and then we can switch to the verifier if the RAM test is inconclusive.
September 17, 2012 6:28:05 PM

I thought it could potentially be a RAM problem, the only thing is that I ran a memtest a day or two ago with 4 or 5 passes and didn't get a single error :/  Also, my computer runs fine, it just blue screens at random points in time.
September 17, 2012 10:08:28 PM

New update: now my computer won't even turn on (doesn't even go to bios), nothing shows up on the monitor, not even with and external GPU (which I know works). I now think it's the motherboard that's screwed up but I don't even know what to do with myself, I'm going insane...
!