Question ntoskrnl.exe errors

[Flipside89k]

Hi Everyone, I’m a long time lurker of the forums but first time poster/requestor of assistance.

I have been having issues with BSOD lately with the majority relating to ntoskrnl.exe errors that have been identified through minidumps.



System built 2018

Motherboard: Asus z370-a Prime 1151

CPU: Intel i7 8700k 3.7Ghz

GPU: Inno3D Geforce GTX 1080

Ram: HyperX Predator 3000Mhz DDR4 16GB (2x8GB)

Boot drive: Kingston 240GB SSD

Other drives: Seagate 2TB SATA 7200 RPM / Samsung 970 M.2 NVME 1TB

Cooler: Cooler master ML240L

Case: Coolermaster MasterCase H500P

PSU: Coolermaster 750W Modular Bronze 80plus



The initial problem I faced was after leaving my computer to make lunch – the computer refused to boot into windows and would only boot into BIOS. I found in there the SSD that I had been using as the boot drive for windows was no longer recognised.

I replaced this drive with an Adata 240GB SSD and reinstalled windows from USB (Windows 10 x64)

While installing windows updates and Geforce experience drivers I was constantly receiving blue screen errors;

I tried several things to try and remedy this:

• Removed all extra storage drives (SATA and M.2)
• Changed keyboard and mouse to generic USB
• Removed 1 stick of ram at a time and retested
• Re-seated each RAM stick firmly
• Formatted the boot drive and reinstalled windows 10
• Ran windows memory test (No errors found)
• Ran memorytest86 on a full test (No errors found)

I decided on replacing the RAM for new sticks as I was contemplating this anyway – so I purchased some Kingston Fury 2x16GB 3200Mhz ram and installed this. I was advised from the shop I bought the machine from that this would be compatible.

I was then able to rebuild the machine and install all the needed windows updates/drivers and software etc and start using the computer again.



I have since been able to purchase a new GPU – AORUS Master Geforce GTX 3070ti 8GB which I have installed and been using for roughly the past week. I have now started to receive more blue screen errors.

Updated Specs:

Motherboard: Asus z370-a Prime 1151

CPU: Intel i7 8700k 3.7Ghz

GPU: Aorus Master 3070ti 8GB

Ram: Kingston Fury 32GB 3200Mhz (2x16GB)

Boot drive: Adata 240GB SSD

Other drives: Seagate 2TB SATA 7200 RPM / Samsung 970 M.2 NVME 1TB

Cooler: Cooler master ML240L

Case: Coolermaster MasterCase H500P

PSU: Coolermaster 750W Modular Bronze 80plus



I have been using the computer for over a week with the new GPU installed without any issues but today playing battlefield V I have had multiple BSOD errors while playing.

I have looked at BlueScreenView and WhoCrashed

I ran the SFC /scannow command and there were some corrupted system files found initially but doing this has not resolved the problem.

I tried running the game again and I still receive the same errors after about 20-30 minutes of playing.

Drop box link to the latest minidumps:

https://www.dropbox.com/s/uys2d2absuzjqcy/Minidumps 17th Feb 22.zip?dl=0


Hopefully someone can offer some assistance as to what might be causing my issues,



On Thu 17/02/2022 15:01:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021722-9140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F7610)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80048724BA5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 17/02/2022 15:01:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0x201DC)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80048724BA5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Thu 17/02/2022 13:49:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021722-11875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F7610)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF80127C0D1DD, 0xFFFFBC019F2E9920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 17/02/2022 13:18:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021722-11531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F7610)
Bugcheck code: 0x50 (0xFFFFF80639C0A655, 0x10, 0xFFFFF80639C0A655, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 17/02/2022 11:07:59 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021722-15015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F7610)
Bugcheck code: 0xA (0xFFFF86C340B9493E, 0x2, 0x0, 0xFFFFF806196EFECA)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 17/02/2022 09:02:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021722-12375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F73B0)
Bugcheck code: 0xA (0x7FFFFFF, 0x2, 0x1, 0xFFFFF80462C0A310)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Fix_that_Glitch]

Try using ddu uninstaller to totally remove your Nvidia gpu drivers. Display Driver Uninstaller Download version 18.0.4.8 (guru3d.com) Install it, pick your Nvida gpu and have it uninstall your drivers and restart your pc. Then install new Nvidia driver without installing Geforce Experience. See if this helps at all. Also check your hardware and sound drivers for any updates.

 

[Flipside89k]

I ran the uninstaller to remove the Nvidia drivers as suggested; started playing Battlefield V again and monitoring GPU temps - showing to be around 60 degrees while playing.

I finished a round and when loading into the next map I got another BSOD

On Thu 17/02/2022 16:58:41 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021722-9390-01.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0x427a0)
Bugcheck code: 0x101 (0x10, 0x0, 0xFFFFE380824C9180, 0x7)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.



On Thu 17/02/2022 16:58:41 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: cpuz152_x64.sys (cpuz152_x64+0x50d1)
Bugcheck code: 0x101 (0x10, 0x0, 0xFFFFE380824C9180, 0x7)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\temp\cpuz152\cpuz152_x64.sys
product: CPUID service
company: CPUID
description: CPUID Driver
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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: cpuz152_x64.sys (CPUID Driver, CPUID).
Google query: cpuz152_x64.sys CPUID CLOCK_WATCHDOG_TIMEOUT


I'm looking at that and beginning to think that the CPU is overheating with the new GPU being installed? I will run the game again and monitor the CPU temperatures.

EDIT: Started up the game and within minutes of running the game I noticed the CPU temperature was spiking sometimes up and over 90 degrees.
Would it be advantageous to replace the AIO I have for a larger unit and replace the thermal paste on my CPU?

 

[Fix_that_Glitch]

Ok so do you run cpuid while gaming, and any other programs when gaming, even antivirus?

 

[Fix_that_Glitch]

Also, run the check disk utility.

 

[Flipside89k]

I ran chkdsk on all drives and nothing was found.

No other programs were running except the launcher for the game and MSI afterburner to monitor temperatures. I was getting constant running temperatures while gaming around 80 to 85 degrees which I thought was a bit high.
I gave the AIO radiator a good clean out as it was a bit dusty and removed the old thermal paste and still received high temperatures.

While gaming I was watching all the core temperatures and they were spiking particularly high over 100 degrees on core 4 and 9.

I ran the AIO at 100% constantly and still didn't reduce - the blue screen was occuring between maps when the game was loading (from M.2 drive) the core temps were spiking on 4 and 9 over 100 then shutting the computer down.


Overall I decided to diagnose it as a CPU fault and decided to upgrade my 8700k - It is coming up on 4 years old anyway so I'm due an upgrade.

Thank you for your assistance anyway Fix_that_glitch!

 

[Fix_that_Glitch]

Yes so, your temps are too high and the gpu is probably shutting down, and it doesn't help that your cpu is running hot. Try upping the fan speed on your gpu manually to say 70 percent, instead of letting it run in auto mode.

 

[dto69]

I have the exact build as you, and a 212evo air cooler and same errors.
WhoCrashed and bluescreen view proved utterly useless, as all fixer apps seem to be, since it sends you on a drivers hunt and memory compatibility and error hunt when it isnt one, its a temp spike hunt.

It was of course my fault (and that of ASUS and their MCE), because I had 2 CM cpu fans in a push pull config, and all was well. I took one out for another rig and left a pull fan, so it doesnt bother the RAM. Worked fine, until it didnt, and BSOD's started.
I fixed it by disabling ASUS multicore enhancement and upping the cpu voltage a bit. Stable with no BSODs.
I swapped the fan to push, and all is well.

PS
Since your AIO is coming up on 5 years old, it could be that it served its lifespan.

 

[Colif]

who crashed only tells you what crashed, not what cause is. Most of time it blames ntoskrnl which is the windows kernel. It might have been what crashed but thats cause it is involved in everything.

If op still has problems, one crash mentioned DirectX. Almost everytime I see it in a BSOD the cause is GPU drivers.

I think I have seen CPU-Z cause a BSOD recently

 

[dto69]

who crashed only tells you what crashed, not what cause is. Most of time it blames ntoskrnl which is the windows kernel. It might have been what crashed but thats cause it is involved in everything.

If op still has problems, one crash mentioned DirectX. Almost everytime I see it in a BSOD the cause is GPU drivers.

I think I have seen CPU-Z cause a BSOD recently

I agree, what threw me off was that it kept indicating it was a driver issue. Until now I was lucky and my builds never crashed or acted weird, so as a result, I am unknowledgeable in troubleshooting. Funny you should mention, it was a final directX crash that really confused me and forced me to look for alternatives. Jaystwocents pointed out how MCE can spike the cores or more often in my case how it undervolted during idle, causing instability. After logging voltage and temps it showed me the problem instantly.

Finding the problem tho, is always a nice feeling