ntoskrnl.exe BSOD

Darren

Darren

Moderator
Staff member
Alright so I got my computer rebuilt after it being dropped and everything seems to be doing okay. Had a crash last night that freaked it out but now it's backup and running. Gotten this BSOD twice today. Once right after loading a picture and again right after changing a graphics setting in a game. Not sure if that's at all related.

I know it's from ntoskrnl.exe but beyond that not sure where to start.

Here's the files from Blue Screen viewer.


==================================================
Dump File : 020313-16941-01.dmp
Crash Time : 2/3/2013 5:36:57 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`01e9ae25
Parameter 3 : fffff880`09a24a30
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7efc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020313-16941-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 275,416
==================================================

==================================================
Dump File : 020313-20326-01.dmp
Crash Time : 2/3/2013 3:52:57 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7ef90
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : x64
Crash Address : ntoskrnl.exe+7ef90
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020313-20326-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 275,416
==================================================
 
Okay I ran Memtest and got this result. I have no idea what it really means. Just got one bad result at the very end of the pass.

20130203212053.jpg
 
It could be from a bad stick of ram. Can you zip up those minidump files and attach them to your next post?
 
I'll also point out that I'm almost positive this is a result of the computer being dropped so I'm guessing physical damage to something.
 
The first one was cause by steam and the second one was something with the system, not getting a specific file or piece of hardware at fault.

So yeah, you still could have some sort of damage.
 
Try running memtest with each stick of RAM individually. If it appears again, then you have a bad stick.
 
johnb35 said:
The first one was cause by steam and the second one was something with the system, not getting a specific file or piece of hardware at fault.

So yeah, you still could have some sort of damage.
Click to expand...

That's odd. Neither of the BSOD's happened while playing a game in Steam, although it was open. I've also had 2 total freezes that required a manual restart. One was during GTA4 and another during CS:GO. I'll run memtest again with each stick individually later.
 
I'm also something called Drive Verified that's supposed to automatically blue screen whenever there's an issue. Then the minidump file will tell me exactly what caused it. Supposedly. I haven't gotten a blue screen since turning that on. The CSGO crash happened after that but it wasn't a BSOD.


Also, how do I read mini dump files? What should I open it with?
 
You are talking about driver verifier not drive verified. You would need to use windows debugging tools to read dump files.
 
Alright well I have progress. I started running Memtest today. Ran one of my blue sticks (Kingston) on the 4th slot from the CPU. All was fine so moved onto one of my Red sticks (Ripjaw). As soon as I attempted too boot it gave me three short beeps. Apparently that's a RAM failure of some sort. I tried it in the other 2 slots that weren't covered by the cooler and it worked just fine. The blue had worked but the red didn't in that slot. So tried the next red. Did the exact same thing. Last blue worked just as the first had. So essentially my red RAM and 4th slot don't get along. This makes sense as before the drop I had the RAM set as red, blue, red, blue with blue being in the 4th slot. All was fine then. I switched them to get the heatfins of my Ripjaw out from under my 212 when I rebuilt a couple nights ago. Put RAM back to the way it was and it booted up just fine. Reapplied Thermal Paste for good measure as my temps had been a bit high and I'm good to go. Hopefully it stays working... :/

TL;DR Red ram doesn't like 4th slot. Blue doesn't mind. Switched so blue is in 4th slot and it works like a champ (so far).
 
You must log in or register to reply here.
Back
Top