Windows 10 constant crash by ntoskrnl.exe

[Jaky333]

--------------------------------------------------------------------------------------------------------------------------
Dump File : 051317-4843-01.dmp
Crash Time : 13/05/2017 9:51:41 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`7d8d45de
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`a7aa25be
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+af5a
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+16c310
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\051317-4843-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 15063
Dump File Size : 630,396
Dump File Time : 13/05/2017 9:52:18 PM
--------------------------------------------------------------------------------------------------------------------------

I have been getting various BSOD crashes recently and I have tried methods from other threads and haven't been able to address my issue. I have tried updating drivers and also updating BIOS.
Any help would be appreciated, thank you.

My computer specs:
MSI Z972 Krait Edition
Intel core i5-4690k 3.50GHz
Nvdia Geforce GTX 970
12 gb ram (3* 4gb HyperX at 1866.32 MHz)
Microsoft Window 10 Pro

Recent crashes:
http://imgur.com/a/k4a5m

 

[Colif]

what the is a fitbit - https://www.fitbit.com/au/home

also related to corsair link - http://www.shouldiremoveit.com/Corsair-Link-USB-Dongle-Driver-Removal-34896-program.aspx
http://www.corsair.com/en-eu/support/faqs/corsair-link

see bottom for some programs that use it - http://www.shouldiblockit.com/siusbxp.dll-8d32be58b5f5bd7317628bf6be577db7.aspx

 

[Jaky333]

what the is a fitbit - https://www.fitbit.com/au/home

also related to corsair link - http://www.shouldiremoveit.com/Corsair-Link-USB-Dongle-Driver-Removal-34896-program.aspx
http://www.corsair.com/en-eu/support/faqs/corsair-link

see bottom for some programs that use it - http://www.shouldiblockit.com/siusbxp.dll-8d32be58b5f5bd7317628bf6be577db7.aspx

Haha, looks like I ain't fit enough to know.

Yeah, I also read how it might be liquid cooler related. The program I identify using is the NZXT Kraken Control. I haven't had a great experience using it but it gives me enough statistics to be useful.

What should be my next move be? Should I unistall NZXT Kraken Control, or is it a hardware issue? I'm also not quite sure if it is running in the background at the moment.

http://imgur.com/a/QMRA5

Currently computer has been running fine for 6 hours straight, turning on the application to see if it can initiate a crash.

 

[Colif]

do you have latest version of cam? I assume thats what its called, its what clicking on download for app of NZXT web site does? you could close it off or remove and re run driver verifer and see if you get any other bsod. perhaps set a system restore point so you can use that to escape the boot loop?

your choice, or just wait for another crash. we haven't really fixed it yet

 

[Colif]

Just some (maybe not pertinent) information: I get the same error at the same offset, viz. ntoskrnl.exe+16c310

This has been happening incessantly for the last few weeks - usually when I am not near my Windows 10 SP4, and I suspect a problem with entering/resuming sleep mode. However, I am not sure what I should/can do to point the finger at a particular driver.

Best wishes

Did you make a post about it? If you do, attach dump files or just ask on teforums like I suggested above in this thread.

NTOSKRNL = New Technology operating system kernel. It seems to get blamed for over half bsod so its name appearing in yours isn't a sign this is the same as your errors..

Sorry - I was just observing and affirming. I realise what NTOSKRNL is but I was making the observation that the offset was the same (which is normally relevant). Given that there are possibly people that may wish to help with the analysing of the dumps, I have loaded three of them and the MSINFO output here https://www.dropbox.com/sh/x4bo72fwvgd7a54/AACseszLyJ74xJfjIghsiumia?dl=0

Thanks in advance - I appreciate the help

Yeah, i sort of guessed what you meant about the offset after I posted. If anyone who can read dumps wanders in, would be nice if they look at both lots of dumps.

 

[SmallHerbivore]

--------------------------------------------------------------------------------------------------------------------------
Dump File : 051317-4843-01.dmp
Crash Time : 13/05/2017 9:51:41 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`7d8d45de
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`a7aa25be
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+af5a
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+16c310
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\051317-4843-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 15063
Dump File Size : 630,396
Dump File Time : 13/05/2017 9:52:18 PM
--------------------------------------------------------------------------------------------------------------------------

I have been getting various BSOD crashes recently and I have tried methods from other threads and haven't been able to address my issue. I have tried updating drivers and also updating BIOS.
Any help would be appreciated, thank you.

My computer specs:
MSI Z972 Krait Edition
Intel core i5-4690k 3.50GHz
Nvdia Geforce GTX 970
12 gb ram (3* 4gb HyperX at 1866.32 MHz)
Microsoft Window 10 Pro

Recent crashes:
http://imgur.com/a/k4a5m

Interestingly I am having exactly the same issue with the same address offset http://i.imgur.com/QD7jkBN.png

also notably this only happens on wake from sleep mode for me. i suspect that it has something to do with the new windows 10 creator update, because if you search for that crash address https://www.google.com/search?q=ntoskrnl.exe%2B16c310 you'll find overwhelmingly posts start around the time users started upgrading to the latest windows creators update. e.g. i updated on the 14th of may as shown by windows live update, and the first bsod happened on the 15th http://i.imgur.com/eK80mzA.png it should be noted that my system has been very stable up until this date and i'm not even sure i've had a bsod till this started happening.

 

[Colif]

MS are trying to blame non MS anti virus for the cause

We found some threads similar to your issue and most of the users have identified that the problem is related to some third-party antivirus software. If you are running a third-party antivirus software, we recommend that you disable or uninstall them and use the built-in Windows Defender.
If the issue still persists, try to run the System File Checker tool

https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/windows-10-creators-update-bsod-kernel-crash/b8ec01a2-4086-4048-8557-417eb79ce813

and there may be some truth in that if you haven't upgraded it recently. Creators edition is a new version of windows, like any new version you might need newer drivers to use it. Same with other software.

 

[Jaky333]

I've received feedback on tenforum, who looked at my dump files. They also found the problem to be Silicone Labs USBXpress Development Kit 'SiUSBXp.sys'.

https://www.tenforums.com/bsod-crashes-debugging/84919-bsod-various-issues-have-tried-many-different-fixes.html

From there I was able to identify some old chipset drivers to update, however not sure if that has directly fixed the 'SiUSBXp.sys' or BSOD. Systems been running fine, but I can't be too certain.

Drivers that I've updated:
http://imgur.com/a/j1jvA

 

[Colif]

fingers crossed. BSOD don't wave a white flag, they just stop. the only way you know its fixed is when they don't happen.

 

[jamesnovak]

I've been getting the same thing since the Creators Update with the code CRITICAL_PROCESS_DIED. I've reinstalled a clean windows instance twice now with all the latest drivers and a recent BIOS update. I've run hardware checks on both internal disks and RAM, all say they are fine.

I noticed that if I configure for a full memory dump, the dump file is not created. If I configure for a Kernel mem dump, I see a dump file.

my caused by driver is ntoskrnl.exe, with the same Crash Address : ntoskrnl.exe+16c310.

I have a Dell Precision 5510 x64
Processor - CoreTM i7-6820HQ
video: NVIDIA Quadro M1000M
32GB Ram

 

[cjack123]

I was experiencing BSOD at same ntoskrnl crash address since updating to creator edition last week. In my case I was getting SYSTEM SERVICE EXCEPTION. It happened the same time every day. Finally figured out that it was Malwarebytes' scheduled threat scan that was triggering it somehow and was able to replicate the BSOD with a manually started scan. Just thought that I would post in case this helps anyone.

 

[okanbilke]

I was having the same problem. I found the solution. This problem is caused by the video card driver but it is not solved by reloading. you must run this program http://www.guru3d.com/files-details/display-driver-uninstaller-download.html in safe mode. then install latest geforce driver.