BSOD from ntokernel.exe

[simonsandvik]

Lately i have been getting constant BSOD and im having a hard time figuring out the culprit. I've looked at bluescreenview and it points to ntokernel.exe. I have updated intel drivers and the Intel Processor Diagnostic Tool gave me a full pass. Updated to latest Nvidea driver. I have also run the windows memory diagnostic which did not catch any errors. I used snappy driver and updated all drivers available. No overclocking. I have no idea how to proceed? Would be real grateful for any help available!

Dump files

Whocrashed:

Spoiler

On Wed 03.01.2018 21:31:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010318-44796-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFF89BFFE10C540, 0x1000000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT



On Wed 03.01.2018 21:31:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFF89BFFE10C540, 0x1000000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT



On Wed 03.01.2018 12:00:41 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010318-46906-01.dmp
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801AB4E7CF5, 0x1, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys KMODE_EXCEPTION_NOT_HANDLED



On Wed 03.01.2018 06:02:57 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010318-44921-01.dmp
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800FDB0FB01, 0xFFFFDA8068026D10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys SYSTEM_SERVICE_EXCEPTION



On Wed 03.01.2018 05:59:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010318-46859-01.dmp
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF807F62431C4, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys KMODE_EXCEPTION_NOT_HANDLED

Specs:
OS - Windows10 64-bit Version 6.2 (Build 9200)
MB - ASUS X99-A, Socket 2011-3
PSU - Cooler Master G750M, 750W PSU
CPU - Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
RAM - Crucial DDR4 2133MHz 16GB
GPU - MSI GeForce GTX 980 4GB
SSD - Samsung 960 EVO 1TB M.2 PCIe SSD
HDD - Seagate Barracuda 2TB 3.5"

 

[marksavio]

can you download HWmonitor? and let it run while you are using your computer. can you check your temperatures? CPU, GPU, PCH

 

[simonsandvik]

Ran HWmonitor for a while. This is what it gave me:

Spoiler

[img="tempratures"]https://i.imgur.com/TBNzwGC.jpg[/img]

HWmonitor report

 

[marksavio]

is this while you are running a GPU benchmark/running a game? then it looks fine to me.
is it still the same ntokernel BSOD? if youve done your memtest already. its most likely a driver issue.
most window updates lately are causing issues with devices. visit your motherboards website and check if they have new drivers versions. you can even reinstall drivers that already have the latest. reinstalling drivers will refresh its "settings" to put it simply. its like reseating your RAM/GPU which also sometimes fix issues. same with drivers.

you can check what specific driver is causing the issue by going to event viewer (winkey+s and type it.). custom views. administrative. scroll down to the time of the crashes and see if you can find an error prior it.

 

[simonsandvik]

ca 10 minutes of gameplay. BSOD's have mostly occurred during gameplay.

 

[Paul NZ]

1. Dont use the windows memory diag program, it's useless . Use memtest

2. Dont use 3rd party driver programs.

Some dont get the right drivers. And some can screw things up. if you want drivers, either get them from the manufacturer's site. Or from the mobo manufacturer's site.

Upload the small dmp files to onedrive then post the link

 

[simonsandvik]

Is there a way to list third party drivers?

minidump:
https://1drv.ms/f/s!Apjv_CBo_kNAhDLROYSkieZhvgNC

 

[marksavio]

you dont have to. you have the newest board of asus so tehy are still supporting it. you dont need 3rd party driver updaters.
just visit the site here and select your OS
https://www.asus.com/Motherboards/X99A/HelpDesk_Download/

and download this software. this has a tool called EZ updater. just run it and connect and update.
ASUS AI Suite 3

also make sure you boot to your BIOS and update it there as well. your BIOS will connect to the internet and update itself automatically for you.

 

[Paul NZ]

This file / driver ysusb64.sys is causing the 0x1e stop error

I would uninstall Daemontools, it's a known cause of crashes

This driver vbaudio_vmauxvaio64_win7.sys is 4 yrs old. It may also not be signed

Does it say the above drivers work in Windows 10?

This driver LGVirHid.sys is 9 yrs old

This driver NTIOLib_X64.sys is 8 yrs old. I would uninstall MSI afterburner, if it's installed.

Is PowerISO up to date? This driver Tpkd.sys is 6 yrs old. Update it or uninstall it

This file loopbe30.sys is 7 yrs old. Update whatever it is, or uninstall it

I think the main prob is 1/2 of your drivers are either out of date, or not compatible with Win10