Windows 10 constant crash by ntoskrnl.exe

Toggle sidebar Toggle sidebar
J

Jaky333

Prominent
May 13, 2017
18
0
510
--------------------------------------------------------------------------------------------------------------------------
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
 
Sort by date Sort by votes
Thanks for the prompt response. I have tried updating my drivers through Msi Live Update two days ago, but the problem still persist. I am now not sure what I should try, or if I should use another method to update my drivers. I just ran a Memtest and that passed successfully.
 
Upvote 0 Downvote
Thank you for the responses, I haven't had luck dealing with the wireless or Lan drivers, wasn't even aware that my computer had wireless capabilities.
I have attempted clean installing the graphic card and used the Live Update 6, hopefully that will fix it.

Will reply back if another BSOD comes up or if it is running smoothly. Thanks again.
 
Upvote 0 Downvote
I have completed the Live Update 6 and reinstalled Nvidia drives using the DDU, but unfortunately experienced many more crashes still.
I waited a couple of days to see if I can gather more information to help me determine what is causing the crashesl. I noticed that it usually crashes when I watch videos from youtube/facebook. Actually haven't had a BSOD from gaming.

Attaching another screenshot of recent crashes. Thanks.

http://imgur.com/a/FQL9q
 
Upvote 0 Downvote
what date did you fix the errors? how many of those are from after the fixes? if before the 14th, then it still shows Nvidia. but if after then the 3 are blaming windows as usual.

ntoskrnl always gets the blame but it is because its responsible for so much in windows, it stands for New Technology Operating System Kernel.
wdf01000.sys = Kernel Mode Driver Frameworks service is another essential part of windows


you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, run bluescreenview and see what driver it reveals, it should just blame ntoskrnl

note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again
download the Windows 10 media creation tool and use it to make a win 10 installer on USB

The instructions to stop it are in the link above I will show u anyway
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose command Prompt
type verifer /reset and press enter
restart PC
 
Upvote 0 Downvote
I had to do it twice, so it would be the 15th onward where I had Nvidia correctly installed. I accidentally reinstalled GeForce Experience on my first DDU refresh. So anything on the 16th would be from after the fix.

I have ran driver verifer before, but I was not able to get any useful information from that or not sure what to do afterward, but one of the BSOD in that screenshot was from using it. I will do it again and send over the results. Thanks for the information, the part around ntoskrnl was interesting.
 
Upvote 0 Downvote
i would ask you for the minidumps but the program that reads them has been getting corrupted results in the last few weeks so instead, you might be best reading the posting instructions on page below and asking on there as they have other tools they can use

https://www.tenforums.com/bsod-crashes-debugging/
 
Upvote 0 Downvote
What a legend, will keep you posted.

Just wondering, what are the chance of the BSOD being caused by hardware issue? Have noticed that my computer being quite loud recently, especially when booting up my computer for the first time each day, which settles down after a couple of minutes, but the temperature reading from my liquid cooler application isn't very high.
 
Upvote 0 Downvote
could it be the fans just need cleaning?

the 1st of the 3 recent errors is an irq error, they are normally drives, sometimes can be ram. I don't think any of them look like hardware

system service exception - You can try running chkdsk /f if you have an ssd or chkdsk /f /r on a hdd in command prompt (admin) - it will want to run it at start up so agree and restart PC. It might take a while
System thread exception not handled - here are some steps - http://www.troublefixers.org/laptops/fix-system-thread-exception-not-handled-in-windows-10/590/?doing_wp_cron=1494923637.1575980186462402343750 (don't download anything)
 
Upvote 0 Downvote
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
 
Upvote 0 Downvote


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..
 
Upvote 0 Downvote
hal.dll = part of windows that sits between hardware and windows. Now since driver verifer finds no drivers, maybe it is a hardware problem though I would think the dump files would narrow it down more than me guessing.

I don't know what version of win 10 you are running so I might as well get the dump files and see if they can be read
Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c /minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)


did you get any result from tenforums?

the loudness, is it fans or something else? can you tell where it comes from in case? I don't think its cause, just curious what cause is.
 
Upvote 0 Downvote
Sorry for the misinformation about the verifier, it has came up with errors but I reformatted the computer when the computer was placed in a constant loop of crashes. I wasn't able to prevent the verifier from resetting.

I did it again and got stuck on this, anything I should try? Currently unable to get back into the computer

http://imgur.com/a/mrNTi

Fyi, running Window 10 Pro
 
Upvote 0 Downvote
try verifer.exe /reset (shouldn't make any difference)

go into troubleshoot/advanced/system restore and see if any date just before you ran verifer? it seems to trap so many in that pickle I now started suggesting people make a system restore point before starting, just to be safe.

I don't know if booting into safe mode and then command prompt and trying to verifer off will make any difference
choose troubleshoot
choose advanced
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
PC will restart and load safe mode
open command prompt, try again

main difference is in safe mode you logged in


only other way out I think is to run reset and keep files/settings - still means needing to reinstall stuff again. Its why I don't suggest verifer right away as it has this habit.
 
Upvote 1 Downvote
@Colif Thank you (the safe mode worked), managed to get out of it, phew... (was a scary feeling, haha) Will update with dump soon.

@The Paladin, I might have... cause I had to fix frames issues before my crashes and might have changed something. Don't want to rule this option out, how would I check for it?
Backstory for that: noticed my frames for all games was dropping, turns out the fix was to set my battery performance to balanced, but I tried a lot of options so I might have touched something by accident.

Just a screenshot from Blue Screen Viewer after using Verifier
http://imgur.com/a/QhpHh

What cloud service do you recommend to upload the dump file, is it meant to be that big? 450 mb?
 
Upvote 0 Downvote
SiUSBxp.sys = Silicone Labs USBXpress Development Kit ... not sure what this is for but its what caused BSOD in verifier.

http://community.silabs.com/t5/Software-Libraries/USBXpress-Development-Tools/ba-p/128732

if you know what it is, remove it

do this to make dumps smaller - might already have a minidump fodler since you used BSV -
Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c /minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)
 
Upvote 0 Downvote


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
 
Upvote 0 Downvote


I have uploaded my mini dump file onto tenforum, hopefully will finally be able to address this issue.
https://www.tenforums.com/bsod-crashes-debugging/84919-bsod-various-issues-have-tried-many-different-fixes.html#post1027997

About the 'Silicone Labs USBXpress Development Kit', I'm not quite sure what that is either and I can't find it in my system :/. will keep digging about it
 
Upvote 0 Downvote
Yeah, still a buzz to me. I had a look at this and tried some of it, but it didn't pick up any errors.
http://www.fixoserror.com/fix-siusbxp-sys-blue-screen-error-step-by-step.html

There was also this article that seems to have the same issue (Final Post). However I am unable to identify which driver it is. Something about a FitBit driver.
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/bsod-memory-management-and-other-errors-on-newly/a1d77c07-0612-4b93-bebc-a8aee099ae87

I don't have any other USB attached beside my mouse and keyboard and it has crashed with just those. Only other usb I plugged in recently was the Media Window Creation Tool.

Thanks for sticking around so long to help me address my issue.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom