Question BSODs SYSTEM_THREAD_EXCEPTION_NOT_HANDLED caused by ntoskrnl.exe

[The Lovely Gamer]

Hello, I have been experiencing BSODs and programs closing while playing games on my PC. I ran Driver Verifier to find the issue and after opening a game, my computer crashed to a Blue Screen with the error SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. I opened the logs in Blue Screen Viewer and it said the issue was ntoskrnl.exe.

Here are my dump files:
https://drive.google.com/file/d/19Itn8bQyRTeeuDK5m4xx4V9dHXPCJ9-4/view?usp=sharing
https://drive.google.com/file/d/1VWL7KapbjvwfpFXofF3CBej62OSOAMyZ/view?usp=sharing
https://drive.google.com/file/d/1GuLOpaSjq8Q6RgWMkElCvfcKVM9naifm/view?usp=sharing

It seems that after I downloaded my Intel Chipset Drivers, the HIDCLASS.SYS error that originally occurred has stopped, but I'm not sure what is causing the ntoskrnl.exe error. Any help is very much appreciated, my PC is barely 2 years old and I would love for it to work properly again! Thank you.

 

[Colif]

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause

Bluescreenview just shows what crashed, very rarely it shows the cause.

What are specs of the PC?

I will ask a friend to convert the dumps.

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/oumq14bp/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler: Dump File Results

File information:	013121-7109-01.dmp (Jan 31 2021 - 03:35:45)
Bugcheck:	FAULTY_HARDWARE_CORRUPTED_PAGE (12B)
Probably caused by:	memory_corruption (Process: MemCompression)
Uptime:	0 Day(s), 7 Hour(s), 01 Min(s), and 32 Sec(s)

File information:	013121-6687-01.dmp (Jan 31 2021 - 14:14:45)
Bugcheck:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 51 Sec(s)

File information:	012921-8500-01.dmp (Jan 29 2021 - 20:08:17)
Bugcheck:	FAULTY_HARDWARE_CORRUPTED_PAGE (12B)
Probably caused by:	memory_corruption (Process: MemCompression)
Uptime:	0 Day(s), 4 Hour(s), 19 Min(s), and 34 Sec(s)

Possible Motherboard page: https://www.msi.com/Motherboard/mpg-z390-gaming-edge-ac
You have the latest BIOS already installed.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

2 page file errors
lets try resetting page file and see if it fixes itself
right click this pc and choose properties
in next pop up choose Advanced System Properties
on the advanced tab, click Settings next to Performance
on the advanced tab, choose change next to Virtual memory

Select no paging file (you will have to untick Automatically manage paging file size for all drives)

Rebooting will clear the pagefile,

then retrace the above steps and restore it by setting it to allow system managed size..

What storage drives do you have in PC? It probably helps to run chkdsk on C drive.

Middle error mentioned HIDCLASS. HIDCLASS devices are USB Mouse/Keyboards most of the time. Maybe your Logitech device?

 

[The Lovely Gamer]

Thank you both so much, I really appreciate the help.

Here are my system specs:
https://drive.google.com/file/d/1S9mq16Xl4yj1SyqXdTaH_ulvBgK5Se4z/view?usp=sharing

Here is all the hardware currently in my computer:
https://pcpartpicker.com/list/bf94j2

I ran the chkdsk on both my C: drive and other hard drive E:, both came back fine with no issues. These are the results:
https://drive.google.com/file/d/1M2_7CUYwbUM5lvI8mbKQiPoZO5pCD_zq/view?usp=sharing

I also did the paging file reset.
I will uninstall the Logitech Software (G Hub) for now and see how it works. Are there any extra steps I need to take to uninstall it, or will everything, drivers and all be removed with the G Hub program? I will also uninstall the Corsair iCue program just to be safe. I'll run another Driver Verifier check and post info if I get another Blue Screen. Thank you again for your help!

 

[The Lovely Gamer]

Update: Logitech G Hub refused to uninstall so I deleted all traces I could find and removed all Logitech drivers. Corsair iCue deleted smoothly. I ran my computer with Driver Verifier active and opened a game to reproduce the BSOD like previously. There have been no Blue Screens thus far. I will continue to monitor my PC but it seems to be fine as of now.

Edit: I got curious and reinstalled Logitech G Hub, ran Driver Verifier, and got 2 more BSODs with the same error:
https://drive.google.com/file/d/1eINi3X_rqINArLgiQSqqvL3ExRX4BcyI/view?usp=sharing

I uninstalled the drivers, kept G Hub installed, ran my PC with Driver Verifier on again with an attempt to reproduce the BSOD, and no BSOD happened. I'm wondering if the drivers provided by Logitech are bad or if there is some sort of conflict that is happening?

 

[Colif]

i have to wait for gardenman to wake up, he should be asleep for a few more hours still.

what drivers did you uninstall before running DV again?

if you insist in running DV, set start up so it boots into safe mode if needed at start up so you can disable DV, it has a habit of causing boot loops.

go to settings/update & security/recovery
under advanced startup, click restart now button
this restarts PC in a blue menu
choose troubleshoot
choose advanced
choose command prompt
Enter these BOLD commands and press ENTER after each.
(Note the colon after C with no space; then the spaces which are important - one after T before / & T before { & } before B & Y before L)
C:
BCDEDIT /SET {DEFAULT} BOOTMENUPOLICY LEGACY
EXIT

restart PC
now anytime you need to go into safe mode from boot,
Boot back up and "immediately" start tapping F8 (That means power button - then F8).
Hopefully that should get you into Safe Mode.

to cancel that so its normal boot, follow same steps as above and
C:
BCDEDIT /SET {DEFAULT} BOOTMENUPOLICY STANDARD
Restart but F8 will not work now.

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://jsfiddle.net/4fvq7a36/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler: Dump File Results

File information:	020221-6687-01.dmp (Feb 2 2021 - 02:34:40)
Bugcheck:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 54 Sec(s)

File information:	020221-17687-01.dmp (Feb 2 2021 - 02:32:48)
Bugcheck:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:	HIDCLASS.SYS (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 54 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

they are both HIDCLASS, one blames it and the other just mentions it in the stack text.
all of my USB devices except BT are hid class. Even my AIO is, since its connected via USB

So what USB have you go besides Mouse/KB as I may have overlooked something.

can you run this, it might give me a clue. It creates a ZIP file so if you can upload that it would be great. https://www.sysnative.com/forums/pages/bsodcollectionapp/

1st crash was after the pc was trying to get a driver to run, 2nd one is more or less identical but windows decided to blame HIDCLASS this time, it was indecisive in 1st crash.

Its weird, seeing way more USB problems the last month or so.

 

[The Lovely Gamer]

The drivers I uninstalled were the Logitech drivers that were installed by Logitech G Hub:
logi_core_temp.sys
logi_joy_bus_enum.sys
logi_joy_vir_hid.sys
logi_joy_xlcore.sys

My only USB devices are my Logitech 502 Hero mouse and Corsair K55 keyboard. I sometimes use an external hard drive to save files on for work and an Elgato HD60 S+ for streaming, but neither were plugged in at the time of the BSODs.

Here is the requested ZIP file:
https://drive.google.com/file/d/18hEiHdQzw3Qos7DIzgp1zTJ_hBPDw5bG/view?usp=drivesdk

Thanks for sticking with me, I hope this will all get sorted soon!

 

[The Lovely Gamer]

My computer seems to be fine without the Logitech drivers so far. I will have to make sure no future updates in G Hub reinstalls them. I never had issues with the older program, Logitech Gaming Software, so I'm still curious as to what the conflict is.

 

[Colif]

You can still install LGS if you want - https://support.logi.com/hc/en-au/articles/360025298053-Logitech-Gaming-Software
there are some devices that don't work well with G Hub, it didn't like my G910 at first.. or mainly my colour scheme.

I read your thread on my phone 2 days ago, and had meant to read the sysnative file, but I forgot who had given it to me, so i just found it now.

so according to sys info, your kb is on
kbdhid.sys

your mouse is on HIDUSB.sys

i have to remember what i was looking for.

windows store updates keep failing, might help to open the store , click on the 3 dots and check Downloads and Updates.

 

[The Lovely Gamer]

Hello! I tried using LGS again, crashed my computer as soon as I installed it. So for now I'm using Onboard Memory Manager. However, it seems my computer's Blue Screens have returned with a new error. I have no idea why, but this is my latest blue screen report:
https://drive.google.com/file/d/1gB_LmZEyU-_PDrp2pk97_pR2l719xqA8/view?usp=sharing

I've updated the store and deleted apps I didn't need. Thanks again!

 

[Colif]

We don't want new errors, we want them to stop.

Wait and see what it shows I guess.

 

[The Lovely Gamer]

I know, my computer keeps throwing new errors my way every time I think things are going smooth! So I ran Windows Memory Diagnostic again, and it came back telling me it found hardware issues. This concerned me considering I replaced my SSD about 2 months ago (it randomly stopped booting after bluescreens and no longer showed in BIOS anymore. I tried cycling power, it wouldn't revive. It wasn't quite 2. New SSD works fine so far.) I downloaded and ran Memtest86. Got errors. Took one RAM stick out, ran Memtest again, it came back fine after 4 cycles with no errors. I then took the good stick of RAM out and put in the other one. Memtest86 so far has 7k errors and it hasn't finished the second cycle yet. Looks like my one RAM stick might be the culprit. Odd considering my other Windows Memory Diagnostic Tests from a couple weeks ago were fine. I haven't overclocked my system or done anything outlandish with my PC, so a SSD and RAM failing on me in barely 2 years of use is crazy to me... My PC temps have been fine so I know overheating isn't an issue. Maybe I just got super unlucky? I'll keep the one stick of RAM that passed the MemTest in my PC and see how everything goes.

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/hpfvux8d/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	021421-7390-01.dmp (Feb 14 2021 - 04:14:00)
Bugcheck:	CRITICAL_PROCESS_DIED (EF)
Probably caused by:	memory_corruption (Process: svchost.exe)
Uptime:	0 Day(s), 8 Hour(s), 52 Min(s), and 32 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

I downloaded and ran Memtest86. Got errors. Took one RAM stick out, ran Memtest again, it came back fine after 4 cycles with no errors. I then took the good stick of RAM out and put in the other one. Memtest86 so far has 7k errors and it hasn't finished the second cycle yet. Looks like my one RAM stick might be the culprit.

Yep, 7k errors is sure higher than the only error count you want, 0

All the errors could be caused by that 1 stick.

If you have proof of purchase of the ram and a screen shot of the errors, you could RMA the ram and get a replacement set.

wishes I had suggested it earler.

 

[The Lovely Gamer]

No worries, you have been nothing but helpful! One of the first things I ran was Windows Memory Diagnostic when this all started happening and it came back with no issues. I'm thinking my RAM stick was working on and off and maybe now it's at the point where the errors are showing consistently, so Windows finally was able to catch it. I've filled out the RMA form on G.Skill's website. I hope that by replacing this RAM set, everything will finally go back to normal. I've spent many sleepless nights working with this darn PC!

 

[Colif]

i wouldn't rely on windows memory checker, i don't think I have ever run it. I normally go straight to memtest if I suggest anything.

7k errors likely to blame for everything so it should be fine after. Might want to reinstall windows after you get it back to make sure no lingering corrupted files.

 

[axe0axe0]

Windows memory diagnostics (WMD) test isn't very reliable, most of the times memtest86 or memtest86+ catch errors when WMD is unable to. Having said that, this doesn't mean that if WMD catches errors that the errors should automatically be ignored. WMD is capable of detecting problems, but it is not as good as memtest86 or memtest86+.