ntoskrnl.eve causing BSOD on 8.1

[roguish]

I keep getting blue screens any randomly, and it always seems to be because of ntoskrnl.exe.

Its a relatively new build and its been doing it since pretty much built it.

Hardware:
AMD FX9590 5.09ghz
Corsair 32GB (4x8GB) DDR3 CMY32GX3M4A1866C9
Asus Sabertooth 990FX
eVGA GTX780 ti

Last two dumps:
==================================================
Dump File : 072614-23609-01.dmp
Crash Time : 26/07/2014 5:45:56 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff802`879620b1
Parameter 3 : 00000000`00000000
Parameter 4 : ffffffff`ffffffff
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+153fa0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.17085 (winblue_gdr.140330-1035)
Processor : x64
Crash Address : ntoskrnl.exe+153fa0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072614-23609-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 297,048
Dump File Time : 26/07/2014 5:47:22 PM
==================================================

==================================================
Dump File : 072614-20984-01.dmp
Crash Time : 26/07/2014 1:44:49 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff801`66975763
Parameter 3 : 00000000`00000000
Parameter 4 : ffffffff`ffffffff
Caused By Driver : NETIO.SYS
Caused By Address : NETIO.SYS+d763
File Description : Network I/O Subsystem
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.16384 (winblue_rtm.130821-1623)
Processor : x64
Crash Address : ntoskrnl.exe+153fa0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072614-20984-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 297,040
Dump File Time : 26/07/2014 1:46:03 AM
==================================================

 

[roguish]

We're going to need more information than that. Are you consistently doing a specific task at the time of the blue screens? Also, you should post more info regarding to the bluescreen (more than: It was caused by ntoskrnl.exe).

It seems to be when I start playing games. Games like League of Legends play fine, but I have been able to get through more than 20 minutes of the new Wolfenstein. My CPU is watercooled though. and coretemp never shows it going over 45. What sort of information about the blue screen?


EDIT: sorry i only typed the short version because i had to make an account.

 

[johnbl]

one of your bugchecks indicates a network file:
the most direct cause would be a bug in your network driver. (update the driver)
if you are using a USB network card, you need update your chipset driver and your network driver (and maybe your BIOS)

 

[roguish]

one of your bugchecks indicates a network file:
the most direct cause would be a bug in your network driver. (update the driver)
if you are using a USB network card, you need update your chipset driver and your network driver (and maybe your BIOS)

No, Im just using the onboard network card. Ive updated the drivers, will let you know if I blue screen.

UPDATE: I havent had a blue screen yet, but now the pc just freezes and I have to do a hard reboot. This only has happened when playing games though, twice now. I have a Corsair H105i cpu cooler and stock everything else. I can't imagine Im overheating as coretemp isnt registering any high temps on the CPU. I have found an apparent issue with the sabertooth 990fx board that apparenrtly the Vcore temp spikes? Maybe that could be the issue? Or could it be the GPU?

 

[johnbl]

sometimes you can get deadlocks in the graphics driver, these tend to be timing dependent but you can sometimes change the timing by disabling the audio support of your graphics driver if you don't run your sound from your graphics cables. (go to device manager and disable the extra high definition sound devices you are not using)

since you have a NVidia card you might consider disabling some of the streaming driver support if you don't use it. It does not tend to work well if you have bugs in your network driver.

if you really want to find the cause of the problem, update all of your drivers. then run verifier.exe and set some debug flags to have windows check the drivers for common problems. Windows will bugcheck but it will also put in tracking info to catch the bad driver.
http://msdn.microsoft.com/en-us/library/windows/hardware/ff545448(v=vs.85).aspx

 

[roguish]

sometimes you can get deadlocks in the graphics driver, these tend to be timing dependent but you can sometimes change the timing by disabling the audio support of your graphics driver if you don't run your sound from your graphics cables. (go to device manager and disable the extra high definition sound devices you are not using)

since you have a NVidia card you might consider disabling some of the streaming driver support if you don't use it. It does not tend to work well if you have bugs in your network driver.

if you really want to find the cause of the problem, update all of your drivers. then run verifier.exe and set some debug flags to have windows check the drivers for common problems. Windows will bugcheck but it will also put in tracking info to catch the bad driver.
http://msdn.microsoft.com/en-us/library/windows/hardware/ff545448(v=vs.85).aspx

Cheers man, Ill try that now. Hopefully I dont have to take it back in.