Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Windows 8.1 ntoskrnl.exe BSOD - Tried many tests, running out of options...
New Posts  All Forums:Forum Nav:

Windows 8.1 ntoskrnl.exe BSOD - Tried many tests, running out of options...

post #1 of 16
Thread Starter 
Hi all,

Running x64 Windows 8.1, I've been having this BSOD ever since I built the machine a few months ago. It can happen totally randomly, even when I do nothing (one time happened during a shower), but it seems to happen more frequently when playing games, and even more frequently when streaming them on Twitch.tv.

The "culprit" is most often ntoskrnl.exe, but also sometimes others, like win32k.sys

I've turned on Driver Verifier pretty early, checking every driver that's not made by Microsoft.

I have not overclocked anything.

What I tried:
  • Catalyst control center says the GPU drivers are up to date. I reinstalled drivers anyway, still got blue screens. After that I even completely removed the GPU (running on internal graphics) but they still occurred so I put it back.
  • memtest86+ says no problem
  • HDD has no problem either.
  • My system is rated (with two different online tests) to use ~370W, so I've bought a 430W PSU. I was afraid the BSODs were caused by lack of power, so I changed it to a 550W PSU, but that did not stop them.

I've tried looking at minidumps with WinDbg following the tutorial in the sticky, but I can't really make head or tail of the info.

I'm out of options there... If it's not my GPU driver, nor my RAM sticks, nor my HDD, nor my PSU, then I'm not sure what else is left. You're my last hope!


All my minidumps (40 of them)

Wiwiweb_minidumps.zip 1082k .zip file


Thanks a lot in advance!
Specs (Click to show)
· OS -Windows 8.1, x64
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer): I purchased it and installed it.
· Age of system (hardware): 3-4 months
· Age of OS installation - have you re-installed the OS: No

· CPU: Intel Core i5-4570 3.2GHz Quad-Core
· Video Card: Sapphire Radeon HD 7950 3GB
· MotherBoard: Gigabyte GA-H87-D3H ATX LGA1150
· Power Supply - brand & wattage: Corsair 430W, later changed to Corsair 550W

Windows7_Vista_jcgriff2.zip 2453k .zip file
post #2 of 16
A ntoskrnl.exe BSOD means that the Windows kernel, the most basic part of the Windows OS, failed. There can be literally thousands of causes.

Best bet is to look at Windows Event Viewer and see what was going on just before a BSOD. Sometimes that can steer you in the right direction.
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
FX6300 Black M5A99X EVO R2.0 Nvidia GTS450 Team Vulcan PC3 12800 
Hard DriveOptical DriveCoolingOS
Samsung 840 PRO Asus DRW-1608P (x2) Custom Water Cooling Win7 (Ult), Win 8.1 & Win Server 2012 R2 
MonitorKeyboardPowerCase
2 X Samsung 915N Ducky Shine III, Blue Cherry/Blue LEDs PCP&C 1kw Lian Li PC-71 (W/Window) 
MouseAudio
Logiteck G400s none 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
FX6300 Black M5A99X EVO R2.0 Nvidia GTS450 Team Vulcan PC3 12800 
Hard DriveOptical DriveCoolingOS
Samsung 840 PRO Asus DRW-1608P (x2) Custom Water Cooling Win7 (Ult), Win 8.1 & Win Server 2012 R2 
MonitorKeyboardPowerCase
2 X Samsung 915N Ducky Shine III, Blue Cherry/Blue LEDs PCP&C 1kw Lian Li PC-71 (W/Window) 
MouseAudio
Logiteck G400s none 
  hide details  
Reply
post #3 of 16
Quote:
Originally Posted by Wiwiweb View Post

Hi all,

Running x64 Windows 8.1, I've been having this BSOD ever since I built the machine a few months ago. It can happen totally randomly, even when I do nothing (one time happened during a shower), but it seems to happen more frequently when playing games, and even more frequently when streaming them on Twitch.tv.

The "culprit" is most often ntoskrnl.exe, but also sometimes others, like win32k.sys

I've turned on Driver Verifier pretty early, checking every driver that's not made by Microsoft.

I have not overclocked anything.

What I tried:
  • Catalyst control center says the GPU drivers are up to date. I reinstalled drivers anyway, still got blue screens. After that I even completely removed the GPU (running on internal graphics) but they still occurred so I put it back.
  • memtest86+ says no problem
  • HDD has no problem either.
  • My system is rated (with two different online tests) to use ~370W, so I've bought a 430W PSU. I was afraid the BSODs were caused by lack of power, so I changed it to a 550W PSU, but that did not stop them.

I've tried looking at minidumps with WinDbg following the tutorial in the sticky, but I can't really make head or tail of the info.

I'm out of options there... If it's not my GPU driver, nor my RAM sticks, nor my HDD, nor my PSU, then I'm not sure what else is left. You're my last hope!


All my minidumps (40 of them)

Wiwiweb_minidumps.zip 1082k .zip file


Thanks a lot in advance!
Specs (Click to show)
· OS -Windows 8.1, x64
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer): I purchased it and installed it.
· Age of system (hardware): 3-4 months
· Age of OS installation - have you re-installed the OS: No

· CPU: Intel Core i5-4570 3.2GHz Quad-Core
· Video Card: Sapphire Radeon HD 7950 3GB
· MotherBoard: Gigabyte GA-H87-D3H ATX LGA1150
· Power Supply - brand & wattage: Corsair 430W, later changed to Corsair 550W

Windows7_Vista_jcgriff2.zip 2453k .zip file

I have two questions for you.
A) How long did you run memtest86+ for? Running ti for a couple of hours is not enough - i typically run it for atleast several hours (or more) on systems that I'm troubleshooting.

B) Chrome was involved in several of those BSOD. I know this from analyzing your crash dumps. It is not necessarily the main culprit behind your BSODs. I have much more to say on this later. BRB.
Edited by DaChosenOne - 3/12/14 at 8:30am
post #4 of 16
Initially I thought it was bad memory by looking at one of your crash dumps but I wanted to analyze a few more dumps before coming back to post.

I took a look at the two most recent ones from March and an older one that dates back to Nov 30, 2013. You have a driver that is causing those BSODs - that is my unprofessional assessment. I could be wrong about that but after analyzing 3 different crash dumps - they all point to the same thing.

Crash Dump Dated 03/11/2014
=================================================
Here you have a bugcheck code of 0x1a_402
Basically anytime you see 0x1a; that indicates a memory management issue. That can encompass things like memory corruption, applications trying to access certain parts of memory that are reserved or off limits; parity issues. etc. The 402 at the end of it ... well that part stumps me. According to this MSDN page, 403 indicates:
The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.

However that is not the same as 402. I searched for 0x1a_402 on the MSDN website but i could not find anything regarding this. Why am I posting it here? Pay attention to where it says "....page table and PFNs are out of sync". And it's off by a single bit. Initially I didn't think much of it until I saw the details of your next crash dump. See line 7 (argument 4) where it says "nearby bytes within the same page have a single bit error". There is a correlation here!


Crash Dump Dated 03/10/2014
=================================================
I will copy & paste here because the information given by Win Debugger yields some good information.

Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: ffffcf800bff8e50, address trying to free
Arg2: ffffcf800bff8a5f, address where one bit is corrupted
Arg3: 00000000009901a8, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error

A driver freed an address, but nearby bytes within the same page have a single bit error.


^^ so basically here you have a driver that is not releasing itself from memory properly.


Crash Dump Dated 11/30/2013
=================================================
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them. A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 00000000777c2772, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 0000000000000004, Thread->KernelApcDisable
Arg4: ffffd000246b1b80, Previous KernelApcDisable


When I googled "APC_INDEX_MISMATCH", this is one of the websites that came up in my search. Again, it fits in line with what I have discovered thus far. Unfortunately, I'm not enough of an expert to tell you which particular driver(s) is causing the crashes. What I would recommend for you is that you update the system drivers ASAP. You said that you build this system a few months ago. Did you use the drivers that came with the CD or did you download the latest version(s) from the website? Visit the website for your motherboard (and graphics card) - make sure that you've got the latest versions installed for each hardware component.
Edited by DaChosenOne - 3/12/14 at 9:04am
post #5 of 16
Memtest-86? I don't use it. Well, maybe to look for a completely dead stick.
I just run the computer, if it doesn't BSOD, I'm a happy camper.

A ntoskrnl.exe BSOD dump isn't going to tell you anything other that the kernel failed.
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
FX6300 Black M5A99X EVO R2.0 Nvidia GTS450 Team Vulcan PC3 12800 
Hard DriveOptical DriveCoolingOS
Samsung 840 PRO Asus DRW-1608P (x2) Custom Water Cooling Win7 (Ult), Win 8.1 & Win Server 2012 R2 
MonitorKeyboardPowerCase
2 X Samsung 915N Ducky Shine III, Blue Cherry/Blue LEDs PCP&C 1kw Lian Li PC-71 (W/Window) 
MouseAudio
Logiteck G400s none 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
FX6300 Black M5A99X EVO R2.0 Nvidia GTS450 Team Vulcan PC3 12800 
Hard DriveOptical DriveCoolingOS
Samsung 840 PRO Asus DRW-1608P (x2) Custom Water Cooling Win7 (Ult), Win 8.1 & Win Server 2012 R2 
MonitorKeyboardPowerCase
2 X Samsung 915N Ducky Shine III, Blue Cherry/Blue LEDs PCP&C 1kw Lian Li PC-71 (W/Window) 
MouseAudio
Logiteck G400s none 
  hide details  
Reply
post #6 of 16
its probably the ram. When memory goes bad it literally can cause every kind of error to popup yet not be fixable until the culprit stick is found. Also reusing an old hard drive that has bad sectors causes errors along those lines as well.

memtest86 is found on hirenbootcd which is free to download, great program.
    
CPUMotherboardGraphicsRAM
Intel i7 6700 MSI B150 Mortar Artic Zotac GTX 1060 3GB Crucial 8 GB DDR4-2400 
Hard DriveOptical DriveOSMonitor
256 Mushkin Triactor Pioneer BR-RW Windows 10 LTSB x64 Seiki 4K 60HZ 42 inch 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Intel i7 6700 MSI B150 Mortar Artic Zotac GTX 1060 3GB Crucial 8 GB DDR4-2400 
Hard DriveOptical DriveOSMonitor
256 Mushkin Triactor Pioneer BR-RW Windows 10 LTSB x64 Seiki 4K 60HZ 42 inch 
  hide details  
Reply
post #7 of 16
Thread Starter 
Quote:
Originally Posted by billbartuska View Post

What I would recommend for you is that you update the system drivers ASAP. You said that you build this system a few months ago. Did you use the drivers that came with the CD or did you download the latest version(s) from the website? Visit the website for your motherboard (and graphics card) - make sure that you've got the latest versions installed for each hardware component.

Wow, thanks a lot for this extensive response. Though I did already change the GPU driver, it's true that I did not change other drivers yet. I went on my motherboard's manufacturer website and reinstalled a few drivers on this page. Namely, the Audio, Chipset, and LAN drivers. We'll see if that did the trick.
Quote:
Originally Posted by billbartuska View Post

Best bet is to look at Windows Event Viewer and see what was going on just before a BSOD. Sometimes that can steer you in the right direction.

Thanks, I will check it out if it happens again.
Quote:
Originally Posted by dlee7283 View Post

its probably the ram. When memory goes bad it literally can cause every kind of error to popup yet not be fixable until the culprit stick is found. Also reusing an old hard drive that has bad sectors causes errors along those lines as well.

memtest86 is found on hirenbootcd which is free to download, great program.

Yes, I thought so too, but I already ran memtest86+ for almost 10 hours with no error. Check out this picture.
post #8 of 16
Quote:
Originally Posted by dlee7283 View Post

its probably the ram. When memory goes bad it literally can cause every kind of error to popup yet not be fixable until the culprit stick is found. Also reusing an old hard drive that has bad sectors causes errors along those lines as well.

memtest86 is found on hirenbootcd which is free to download, great program.

The OP has already told us in his original post that he ran memtest86+ & found no issues.

Also bear in mind that not all BSODs are due to defective memory sticks. If you take the time learn how to analyze crash dumps, you can solve a variety of problem just by looking at some simple things.
Quote:
Originally Posted by Wiwiweb View Post

Wow, thanks a lot for this extensive response. Though I did already change the GPU driver, it's true that I did not change other drivers yet. I went on my motherboard's manufacturer website and reinstalled a few drivers on this page. Namely, the Audio, Chipset, and LAN drivers. We'll see if that did the trick.

Sure no problem and let us know if the BSODs continue to happen.

EDIT:

Wiwiweb, in case the BSODs continue to happen after updating your system drivers, it would be helpful if you changed your windows configuration from a "memory dump" to a full "kernel dump". The key difference here is that with the full kernel dump, I'll be able to load any faulting modules using Win Debugger and glean more information that way. To make this change, go to your Advanced System Properties and follow the screenshot I've provided.

Edited by DaChosenOne - 3/12/14 at 4:52pm
post #9 of 16
Quote:
Originally Posted by Wiwiweb View Post

Quote:
Originally Posted by billbartuska View Post

Best bet is to look at Windows Event Viewer and see what was going on just before a BSOD. Sometimes that can steer you in the right direction.

Thanks, I will check it out if it happens again.

That's the beauty of Event Viewer. Pretty much everything that happened since you built the computer and booted Windows for the first time is there. Changing the sort to "errors only" will save you a lot of time scrolling around.

My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
FX6300 Black M5A99X EVO R2.0 Nvidia GTS450 Team Vulcan PC3 12800 
Hard DriveOptical DriveCoolingOS
Samsung 840 PRO Asus DRW-1608P (x2) Custom Water Cooling Win7 (Ult), Win 8.1 & Win Server 2012 R2 
MonitorKeyboardPowerCase
2 X Samsung 915N Ducky Shine III, Blue Cherry/Blue LEDs PCP&C 1kw Lian Li PC-71 (W/Window) 
MouseAudio
Logiteck G400s none 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
FX6300 Black M5A99X EVO R2.0 Nvidia GTS450 Team Vulcan PC3 12800 
Hard DriveOptical DriveCoolingOS
Samsung 840 PRO Asus DRW-1608P (x2) Custom Water Cooling Win7 (Ult), Win 8.1 & Win Server 2012 R2 
MonitorKeyboardPowerCase
2 X Samsung 915N Ducky Shine III, Blue Cherry/Blue LEDs PCP&C 1kw Lian Li PC-71 (W/Window) 
MouseAudio
Logiteck G400s none 
  hide details  
Reply
post #10 of 16
Quote:
Originally Posted by billbartuska View Post

That's the beauty of Event Viewer. Pretty much everything that happened since you built the computer and booted Windows for the first time is there. Changing the sort to "errors only" will save you a lot of time scrolling around.


I don't necessarily have against using Event Viewer to troubleshoot problems as I have used it many times myself. But encouraging Wiwiweb to use it solve his BSOD problem is just downright inefficient and will probably just lead him on a wild goose chase. The whole reason why tools like Wini Debugger exists in the first place is to troubleshoot BSODs accurately without too much guessing. Again, I don't necessarily have anything against Event Viewer, but in the case of BSOD's it sometimes does not render key pieces of information such as the bugcheck code that is so useful in tracking down BSODs.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Crash Analysis and Debugging
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Windows 8.1 ntoskrnl.exe BSOD - Tried many tests, running out of options...