Question Loud PC fans, laggy, 100% CPU usage and then a BSOD ?

[MrrSpeaker]

Hello. I'd first like to say I'm pretty much at beginner level when it comes to PC stuff, so you'll have to excuse me. I've had issues with my PC for a long time, but nothing bad enough to make it unusable. I recently startet getting BSOD and tried using event viewer to find out the issue. I found an error code/ bug check that was called 0x000000a. After some googling, it was recommended on Microsoft website to use driver verifier through cmd. I tried this and was asked to restart my PC.

Now this is where it went really badly. Now my PC boots normally, but takes a very long time to get past the welcome screen. After getting to the main screen, everything gets super laggy, CPU usage goes to 100% because of "System interupts", all fans go crazy and loud, and after about 2 minutes I get BSOD. Error code on BSOD reads: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

I'm not really able to gather any information before BSOD. Any pointer, or at least where I can start? Last resort is to take my PC to a repair shop. Thanks!

Here is the link to the dump files: https://files.catbox.moe/lrcf79.rar

I managed to boot into Safe Mode with Networking, but still unsure what the issue could be. I'm starting to believe it may be a driver related problem, as Safe Mode uses very few drivers and only launches what is necessary. This is just a theory though.

 

[ubuysa]

A couple of questions...

1. Is it stable in Safe Mode? As you say, this is a stripped-down stable version of Windows.
   
   
2. Is Driver Verifier still enabled? If so, disable it by opening a command prompt and entering the command verifier /reset and reboot.

Of the six dumps uploaded, five of them are similar, all fail in the HIDCLASS.sys Windows driver with a 0xC0000005 exception code - indicating an invalid memory reference. The HIDCLASS.sys driver manages human interface devices (keyboards, mouse, game controllers, etc.) that are USB attached. If you have a wireless mouse and/or wireless keyboard then first off change the batteries. Then I would suggest unplugging all USB attached devices, except the keyboard and mouse - and use a wired keyboard and a wired mouse if you can, and see whether it still BSODs.

The other dump is caused by an invalid memory reference as a processor came out of the idle state. It's possible then that your problems could be RAM related. Your four 8GB sticks of G.Skill F4-3200C16D-16GTZR RAM are clocked at their design speed of 3200MHz, however this is an overclock, so I'd first like you to go into the BIOS setup, find the XMP profile settings for your RAM and disable them. The RAM will then run at its native (SPD) speed of 2133MHz. Let's see whether it's stable at that speed first.

BTW. It is worth remembering that your i9-9900K CPU is only guaranteed to support RAM at speeds up to 2666MHz (see https://www.intel.com/content/www/u...-16m-cache-up-to-5-00-ghz/specifications.html), so it's possible (although unlikely) that you may never be able to clock that RAM faster than 2666MHz.

 

[MrrSpeaker]

A couple of questions...

1. Is it stable in Safe Mode? As you say, this is a stripped-down stable version of Windows.
   
   
2. Is Driver Verifier still enabled? If so, disable it by opening a command prompt and entering the command verifier /reset and reboot.

Of the six dumps uploaded, five of them are similar, all fail in the HIDCLASS.sys Windows driver with a 0xC0000005 exception code - indicating an invalid memory reference. The HIDCLASS.sys driver manages human interface devices (keyboards, mouse, game controllers, etc.) that are USB attached. If you have a wireless mouse and/or wireless keyboard then first off change the batteries. Then I would suggest unplugging all USB attached devices, except the keyboard and mouse - and use a wired keyboard and a wired mouse if you can, and see whether it still BSODs.

The other dump is caused by an invalid memory reference as a processor came out of the idle state. It's possible then that your problems could be RAM related. Your four 8GB sticks of G.Skill F4-3200C16D-16GTZR RAM are clocked at their design speed of 3200MHz, however this is an overclock, so I'd first like you to go into the BIOS setup, find the XMP profile settings for your RAM and disable them. The RAM will then run at its native (SPD) speed of 2133MHz. Let's see whether it's stable at that speed first.

BTW. It is worth remembering that your i9-9900K CPU is only guaranteed to support RAM at speeds up to 2666MHz (see https://www.intel.com/content/www/u...-16m-cache-up-to-5-00-ghz/specifications.html), so it's possible (although unlikely) that you may never be able to clock that RAM faster than 2666MHz.

Thanks! This is very useful information! I've struggled with understanding the info in the dump files, so this is really helpful.

To answer your questions:

1. Yes, it is stable in Safe Mode.

2. Driver verifier I still enabled, I'll try disabling it in safe mode as soon as I get home.

I've also already tried unplugging everything, including my wired keyboard and wired mouse after logging in. To no avail sadly.

I did manually increase the speed of my RAM not too long ago, so I'll be sure to put that back to it's native speed since the prosessor won't really support the full speed of the RAM. Thank you for pointing this out.

I'll try all this as soon as I get home from work and will update after that. Thanks again!

 

[MrrSpeaker]

A couple of questions...

1. Is it stable in Safe Mode? As you say, this is a stripped-down stable version of Windows.
   
   
2. Is Driver Verifier still enabled? If so, disable it by opening a command prompt and entering the command verifier /reset and reboot.

Of the six dumps uploaded, five of them are similar, all fail in the HIDCLASS.sys Windows driver with a 0xC0000005 exception code - indicating an invalid memory reference. The HIDCLASS.sys driver manages human interface devices (keyboards, mouse, game controllers, etc.) that are USB attached. If you have a wireless mouse and/or wireless keyboard then first off change the batteries. Then I would suggest unplugging all USB attached devices, except the keyboard and mouse - and use a wired keyboard and a wired mouse if you can, and see whether it still BSODs.

The other dump is caused by an invalid memory reference as a processor came out of the idle state. It's possible then that your problems could be RAM related. Your four 8GB sticks of G.Skill F4-3200C16D-16GTZR RAM are clocked at their design speed of 3200MHz, however this is an overclock, so I'd first like you to go into the BIOS setup, find the XMP profile settings for your RAM and disable them. The RAM will then run at its native (SPD) speed of 2133MHz. Let's see whether it's stable at that speed first.

BTW. It is worth remembering that your i9-9900K CPU is only guaranteed to support RAM at speeds up to 2666MHz (see https://www.intel.com/content/www/u...-16m-cache-up-to-5-00-ghz/specifications.html), so it's possible (although unlikely) that you may never be able to clock that RAM faster than 2666MHz.

I've gotten back home, and to my relief, simply "exiting" the verifier mode for cmd fixed everything xD I do not know why. I'll be sure to edit the RAM tho just in case! Thanks again for the help

 

[MrrSpeaker]

UPDATE: The issue was originally fixed. However after updating my RAM speed to auto, and this issue could have happened before updating the RAM speed, I keep getting BSOD after BSOD. They range from DPC WHATCHDOG VIOLATION, which has happened the most, WHEA UNCORRECTABLE ERROR once and finally APX INDEX MISMATCH.

I'm once again kinda stuck 😅

Here is the dump file from todays BSOD's: https://files.catbox.moe/pcdpdn.rar

I am able to start my PC in Safe Mode with Networking once again, tho every time I try to use my browser (OperaGX), the browser stops working after a minute, and closing and reopening the browser is required for it to start working again.

 

[ubuysa]

There are two areas that I's suggest you need to look at...

Two of the BSODs were almost certainly caused by the Hamdrv.sys driver. This is a component of the Hamachi VPN and the version you have installed is ancient, dating from 2015...

1: kd> lmvm Hamdrv
Browse full module list
start             end                 module name
fffff800`4b020000 fffff800`4b02e000   Hamdrv   T (no symbols)          
    Loaded symbol image file: Hamdrv.sys
    Image path: Hamdrv.sys
    Image name: Hamdrv.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Mon Mar 30 16:28:42 2015 (55194F8A)
    CheckSum:         0000E45B
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I would disable or uninstall the Hamachi product and see whether the problem remains. Once you've shown it to be the cause you can see about getting an updated version. I suspect this is the main cause of your BSODs because that driver is loaded in all the dumps.

The other thing I notice in your dumps is that in every one of these dumps the vgk.sys driver unloaded immediately before the BSOD...

Unloaded modules:
fffff800`39f80000 fffff800`39f90000   dump_storpor
fffff800`39fc0000 fffff800`39ff0000   dump_stornvm
fffff800`39e20000 fffff800`39e3e000   dump_dumpfve
fffff800`8ff10000 fffff800`8ff1c000   WdmCompanion
fffff800`4b420000 fffff800`4b42c000   WdmCompanion
fffff800`4af10000 fffff800`4af2f000   dam.sys
fffff800`65e50000 fffff800`67c27000   vgk.sys
fffff800`26600000 fffff800`2660c000   WdBoot.sys
fffff800`276f0000 fffff800`27701000   hwpolicy.sys

The vgk.sys driver is part of the Vanguard anti-cheat tool and is a very well-known cause of BSODs. If removing the Hamachi VPN doesn't help then uninstall Vanguard (obviously some games will then be unplayable), reboot (to remove the driver) and then see whether it still BSODs.

 

[MrrSpeaker]

There are two areas that I's suggest you need to look at...

Two of the BSODs were almost certainly caused by the Hamdrv.sys driver. This is a component of the Hamachi VPN and the version you have installed is ancient, dating from 2015...

1: kd> lmvm Hamdrv
Browse full module list
start             end                 module name
fffff800`4b020000 fffff800`4b02e000   Hamdrv   T (no symbols)         
    Loaded symbol image file: Hamdrv.sys
    Image path: Hamdrv.sys
    Image name: Hamdrv.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Mon Mar 30 16:28:42 2015 (55194F8A)
    CheckSum:         0000E45B
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I would disable or uninstall the Hamachi product and see whether the problem remains. Once you've shown it to be the cause you can see about getting an updated version. I suspect this is the main cause of your BSODs because that driver is loaded in all the dumps.

The other thing I notice in your dumps is that in every one of these dumps the vgk.sys driver unloaded immediately before the BSOD...

Unloaded modules:
fffff800`39f80000 fffff800`39f90000   dump_storpor
fffff800`39fc0000 fffff800`39ff0000   dump_stornvm
fffff800`39e20000 fffff800`39e3e000   dump_dumpfve
fffff800`8ff10000 fffff800`8ff1c000   WdmCompanion
fffff800`4b420000 fffff800`4b42c000   WdmCompanion
fffff800`4af10000 fffff800`4af2f000   dam.sys
fffff800`65e50000 fffff800`67c27000   vgk.sys
fffff800`26600000 fffff800`2660c000   WdBoot.sys
fffff800`276f0000 fffff800`27701000   hwpolicy.sys

The vgk.sys driver is part of the Vanguard anti-cheat tool and is a very well-known cause of BSODs. If removing the Hamachi VPN doesn't help then uninstall Vanguard (obviously some games will then be unplayable), reboot (to remove the driver) and then see whether it still BSODs.

I tried updating my BIOS, and somehow the BSOD stopped appearing. I'll remove Hamachi non the less as it's never really being used. If at some point it starts coming back, I'll try removing Vanguard as well. Can't hurt to take a break from LoL anyways xD

Anyways, thank you so much for the help!