ntoskrnl.exe BSODs on Windows 10

morgansoleil · 18 Jun 2020

I've been getting BSODs since I first ran my new build using Windows 10.

Various errors such as:
interrupt_exception_not_handled,
memory_management,
system_service_exemption,
irql_not_less_or_equal.

This usually happens when I'm gaming or watching a video, but sometimes right after rebooting after one of these errors. After analyzing minidump files, it's consistently caused by ntoskrnl.exe.
I've tried reinstalling windows 10 and replacing my RAM sticks with no avail.
SFC scan results "Windows Resource Protection found corrupt files but was unable to fix some of them."
DISM scan "Error: 0x800f081f
The source files could not be found."
All my drivers are up to date in device manager, but when using third party driver checker (Auslogics Driver Updater and Outbyte Driver Updater) I come across an issue when updating the driver Standard NVM Express Controller. When I update it, Windows 10 won't boot at all and I need to restore to a previous point before the update.

DESKTOP-F8A2EG6-(2020-06-18_16-27-15).zip

I've been googling this so much and trying so many things and I can't figure it out...
Thanks in advance for your help!

philc43 · 18 Jun 2020

One possibility is that one of your memory modules may have a fault. At least two of the dumps mention memory corruption and the variety of different stopcodes tends to point towards a hardware failure. To test this please remove one of the memory modules and see if the system works better. Repeat the test with the other module if needed to try and confirm which one may have a problem.

morgansoleil · 18 Jun 2020

Thanks philc43. I will try this.
I hesitate to think it's due to the memory sticks only because I was originally using Team brand RAM and after having this issue, ordered new RAM from Crucial... Still the same issue with two sets of brand new RAM sticks.

philc43 · 18 Jun 2020

Okay, I hadn't realised you had already tried new RAM. It is unlikely that both sets are faulty but it is not impossible. There could be a problem with the motherboard slots so it is also worth trying a single RAM module in different slots to test this theory.

morgansoleil · 23 Aug 2020

" trying a single RAM module in different slots to test this theory."
I've tried this and I'm still getting the same BSODS caused by ntoskrnl.exe

Do you think I should purchase a new copy of Windows 10? I'm worried that this may be caused by a bad copy of Windows 10 that I purchased over Amazon. Perhaps it was some sort of scam.

Ztruker · 23 Aug 2020

NO, do not purchase a new copy of Windows 10. It is 99.9999999% unlikely you have a bad copy.

You can download a new copy from Microsoft, never a need, ever, to buy another copy.
Download Windows 10

Take the Create Windows 10 installation media path and have Media Creation Tool make a USB flash drive for you to use to do another Clean Install of Windows 10 if you want. It can also be used to do a Repair Install if you'd rather but I don't think that is your problem.

This is more than likely a hardware or device driver problem.

6/17 7:28PM dump

Code:

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8010d5b2e0e, The address that the exception occurred at
Arg3: ffffd70ad3a9c648, Parameter 0 of the exception
Arg4: ffffc6006f946920, Parameter 1 of the exception

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for Netwtw08.sys

That's your Intel(R) Wireless-AC 9560 160MHz card/chip. Driver is dated: Wed Oct 16 08:42:02 2019

See if you can find a newer driver or see about replacing the WiFi card.

It would also be good to test your RAM.

===================================================
Up through DDR3, follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
DDR4, follow this tutorial: MemTest86 v8.1 Free Memory Testing Tool Review

Both of these are diagnostic tools designed to test Random Access Memory (RAM) for faults. They will verify that:

RAM will accept and keep random patterns of data sent to it
There are no errors when different parts of memory try to interact
There are no conflicts between memory addresses

They run from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

Warning

MemTest86+ and Memtest86 need to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM. The new version of Memtest86 only allows 4 passes for the free version so run it twice, back to back.

If you are asked to run MemTest86+ or Memtest86 by a Ten Forums member make sure you run the full 8 (or 4+4) passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

Note

Both of these diagnostics has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ or 4+4 passes of Memtest86 is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run it overnight, starting just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

If you do not find any problems then try Driver Verifier:

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more ever7y two hours until all are selected or you get a BSOD.

Enable and Disable Driver Verifier in Windows 10

morgansoleil · 26 Aug 2020

Ztruker, thanks for your reply, I will save my money in good conscience. You're right, my Wifi card driver wasn't up to date, so I've since updated it, but am still getting the same ntoskrnl.exe BSODS. I'm attaching more recent dump files, so there is something more recent to look at.
DESKTOP-F8A2EG6-(2020-08-26_16-33-41).zip

In the meantime, I will follow your advice to run memtest84 (4+4 passes) and upload my response here. However, Id be very surprised to find problems here. When I first built this PC (with Team brand memory), I was getting these BSODS so I purchased brand new Crucial brand memory sticks (same specs) but nothing has changed.

Ztruker · 26 Aug 2020

This is what the Users Guide says about the RAM in your PC:

ntoskrnl.exe BSODs on Windows 10-image.png

Which slots do you have the RAM plugged into?

Both new dumps were the same:

Code:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffd6c540027008, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8067aee69b3, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

Still looks like memory problems to me.

It's possible this could be caused by a device driver, though unlikely. Let's see what Driver Verifier shows after you've finished memtest86. If it doesn't yield any errors then:
Run Driver Verifier

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more ever7y two hours until all are selected or you get a BSOD.

Enable and Disable Driver Verifier in Windows 10