Frequent BSODs on seemingly unrelated tasks both active and idle

mKAYDM · 29 Jul 2019

Experiencing multiple daily BSODs since system was built. Only consistency seems to be that BSODs happen while either multitasking or sitting idle. When using single programs crashes seem to be less frequent.

BSODs can be minutes or hours apart. Frequent application crashes where none were are experienced on previous computer (Factorio, Chrome, MS Word, Assassins Creed Odyssey...) however not all games or programs crash. (In this specific context, I mean the application crashes frequently, not a BSOD. Although they seem related).

V2 Collector logs attached.

The system:

- Ryzen 3600, stock cooler, OC disabled
- GSkill Ripjaws 3200, OC disabled
- TUF B450M Plus Gaming (second motherboard, first one replaced at Asus recommendation based on these problems).
- Sabrent Rocket NVME
- WD Black 4tb (new model)
- GTX 1070
- Cooler Master Silent Gold Pro 1000w (yeah, it's way overpowered for this)
- Logitech G413 Keyboard, Logitech G502 mouse.

Probable causes from WhoCrashed and BlueScreenView:

ntoskrnl.exe

- This is listed as the probable cause in all one one instance in WhoCrashed and the only cause in BlueScreenView.

- I do not believe I have bad memory modules as I've run the system on each single 8gb stick and still experience the issue. Memtest86 and windows Memory diagnostic report no issues.

2. ntkrnlmp.exe

- This one is pretty ambiguous and could be so many different things but I've attempted almost every fix (within reason) on the first two pages deep on Google with no success.

Sample BSODs experienced:

- Kernel auto boost invalid lock release
- Kernel auto boost lock qcquisition with raised irql
- Kmode exception not handled
- Kernel security check failure
- Page fault in NonPaged area
- Unexpacted Store Exception
- System thread exception not handled
- IRQL not less of equal

Things attempted thus far:

- Pealed through WinDBG and WhoCrashed with full memory dump, minidump and kernel dumps (I'm not very experienced here with reading dump files but haven't found an answer).

- Windows Driver Verifier enabled to spark driver crashes (crashes before it gets to login). Analyzed those files, no answer.

- Full clean reformatted Windows 10 install from multiple versions (1903 back to early 17xx builds).

- Many windows restores, refreshes, reverts, sfc/ scannow | DISM |versions checks, etc...

- Reinstalled every driver (within reason) manually or through windows default versions (Audio, video, network, HIDs, storage, Chipsets, displays).

- Disabling drivers that may conflict (such as Nvidia HD audio and RealTek, different forms of video or networking).

- Disconnecting/trying only specific pieces of hardware (nvme swapped with ssd, different video card, no extra drives, each independent stick of ram, etc).

- Enabling/disabling BIOS settings, turning OCs off and on, voltages up and down, EZ Flash/bios updated... you name it. No solution.

- Disabled/uninstalled all antivirus/antimalware protection.

- Tons of other smaller things with lots and lots of reading (MemTest 86, Windows Memory Diagnostic, Prime95...) ... even checking voltages and fluctuation from the outlets.

philc43 · 30 Jul 2019

Hello mKAYDM,

Thanks for providing such a detailed summary of all that you have done so far to investigate the issue.

The crash dumps do not provide a huge amount of help since I can't pinpoint the cause either as being driver related or hardware related. It could be either.

For driver issues we usually suggest Driver Verifier which you have tried. Did you keep any of the crash dumps from these crashes so that we can examine them?

To rule out hardware issues please try running your system in safe mode with networking for a day and see if there are any BSOD events. If there are this tends to confirm a hardware issue.

If you need to try Driver Verifier again please follow this tutorial:

Diagnostic Test

DRIVER VERIFIER

Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please read and run driver verifier.

If you suspect a driver is causing a problem but do not have a clear idea which one it is then Driver Verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or until you have a bluescreen, whichever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset driver verifier from within safe mode, or in the troubleshooting options open command prompt and type verifier /reset.

Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

jdc1 · 30 Jul 2019

Not to detract from philc43's post, but the presence of multiple different BSOD errors is often a sign of a hardware problem.
As is the BSOD's recurring after a clean install of Windows.
That being said, it's also possible that lower-level drivers can cause the same type of issues (that's why a clean install of Windows is used to rule out the 3rd party drivers).

I suggest :
1) Memtest86 (not 86+): [url=https://www.memtest86.com/]MemTest86 - Official Site of the x86 Memory Testing Tool[/url]

2) SeaGate SeaTools for Windows (test ALL hard drives - HDD/SSD/USB/etc): [url=https://www.seagate.com/support/kb/how-to-use-seatools-for-windows-202435en/]How to use SeaTools for Windows | Seagate Support US[/url]

3) Intel Processor Diagnostic Tool: [url=https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool]Download Intel(R) Processor Diagnostic Tool[/url]
Disregard if not using an Intel processor

4) Furmark stress test for GPU: [url=https://geeks3d.com/furmark/downloads/]FurMark > Downloads[/url]
Read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall

5) OCCT: [url=https://www.ocbase.com/]OCBASE / OCCT[/url]
Read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall

If these hardware tests don't find anything, then you'll have to start troubleshooting by removing parts. Here's a page that describes this: [url=https://carrona.org/strpdown.html]Hardware Stripdown Troubleshooting[/url]
Although it's old, it's still relevant in these situations.

Good luck!

mKAYDM · 30 Jul 2019

Hey philc43!

Thank you very much for taking a look here.

I've re-enabled Verifier following the instructions in the link you provided and got some more crashes. I've attached the Minidump and V2 Collector files to this post. Really hope this helps.

Interesting note, once Verifier was enabled my computer would crash roughly 5-6 seconds after logging in, each and every time in the same way consistently. It would NOT crash at the login screen even after waiting 10 minutes at the login screen, no crash. There seems to be at least some consistency, which is nice for a change!

Once Verifier was disabled the crashes stopped (for the time being).

- - - Updated - - -

Hey jdc1,

I'm not familiar with SeaTools or OCCT, I'll look into them now and update.

MemTest86, FurMark and Prime95 do not return any issues related to ram (prime95 has produced errors but I'm almost certain that's related to the Auto-Boost function of the Ryzen chips and I can't reproduce the issue when OC is disabled).

I have tried testing each ram stick (no issues found) replacing all drives (including OS drive with a separate SSD) and the issues persist. Motherboard has been replaced by Asus.

The only components that have not changed at this point are the PSU and CPU. I'll report back soon.

philc43 · 30 Jul 2019

I've looked through the Driver Verifier Crash dumps and the only clue I can find is that the Logitech Keyboard might need its driver updating. If there is not a new one see if you can get Windows to update it via Device Manager.

Code:

6: kd> lmvm lgbusenum
Browse full module list
start             end                 module name
fffff809`25480000 fffff809`25484e00   LGBusEnum T (no symbols)           
    Loaded symbol image file: LGBusEnum.sys
    Image path: \SystemRoot\system32\drivers\LGBusEnum.sys
    Image name: LGBusEnum.sys
    Browse all global symbolsfunctionsdata
    Timestamp:        Mon Jun 13 11:47:08 2016 (575EFFAC)
    CheckSum:         00012B72
    ImageSize:        00004E00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Unable to load image \SystemRoot\system32\drivers\LGBusEnum.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for LGBusEnum.sys

MrPepka · 30 Jul 2019

Update:
Logitech Gaming Software (check updates in program or visit https://download01.logi.com/web/ftp/...4_Logitech.exe)

jdc1 · 30 Jul 2019

FYI - Prime 95 stresses:
- CPU cache
- RAM
- Memory controller (onboard the CPU in most modern CPU's)

Try CPU stress tests (I'm not familiar with those for the Ryzen, so you'll have to Google them)
OCCT has a PSU test - but the most reliable test for a PSU is to replace it with one that's known to be good. If you don't have one to test with, you can purchase one from a shop that'll let you return it if it's not needed. In the US, most major retailers (WalMart, Target, Staples, BestBuy, etc) have such a return policy.

Hard drive/SSD tests. Have you tested the system with only one HDD/SSD - and have you tried it with the replacement being the lone drive also. Have you tried different ports on the motherboard (most modern mobo's have 2 different sets of ports controlled by different controllers. I ask this because a misbehaving hard drive can make other devices seem to have problems.

Is there anything else plugged into the motherboard/external ports? Any USB devices? How about the keyboard and mouse?

Have you tried another video card (even though it passed FurMark)? I'm concerned about it because of the number of video related BSOD's (6 out of 35 - see list below)

Error Reports folder shows 35 BSOD errors:
- 2 STOP 0x3B: SYSTEM_SERVICE_EXCEPTION
- 3 STOP 0x50: PAGE_FAULT_IN_NONPAGED_AREA
- 2 STOP 0x139: KERNEL_SECURITY_CHECK_FAILURE
- 6 STOP 0x141: VIDEO_ENGINE_TIMEOUT_DETECTED
- 1 STOP 0x154: UNEXPECTED_STORE_EXCEPTION
- 1 STOP 0x162: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE
- 1 STOP 0x192: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
- 15 STOP 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
- 2 STOP 0xA: IRQL_NOT_LESS_OR_EQUAL
- 1 STOP 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION
- 1 STOP 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

- - - Updated - - -

Noted HIDCLASS.sys present just before Verifier appears in the stack of all 5 memory dumps.
This implies that a Human Interface Device was acting as Verifier was called.

I also note older drivers for a Logitech device and an XBox device.
Please uninstall these devices and physically remove them from the system (if it's a mouse/keyboard, I'd try another one to see if that's a problem).
I also see USB audio drivers in the dump. Are you using a USB audio device? If so, please uninstall it and physically remove it from the system (you can reinstall it after we're done testing). These devices are known to cause BSOD issues in some systems.

mKAYDM · 30 Jul 2019

@ jdc1, good catches on the Xbox and USB audio, this was an Xbox One wired controller and a Logitech G933 headset wireless dongle. I simple hadn't considered removing these (I have no excuse). I've uninstalled and unplugged them. At this time I only have a Logitech keyboard and mouse pluggin in (G413 and G502). I also had a seagate external USB hard drive that I've disconnected. No other devices.

@ philc43 and @ MrPepka ,
This is odd as I do have the logitech gaming software to keep drivers up to date which I've checked. This is a guess, but maybe it's one of the windows default keyboard/mouse drivers? Regardless, I'll uninstall and reinstall it all now and update with info.

Thanks everyone for the input. Much appreciated.

- - - Updated - - -

Follow-up question. When I go and uninstall the driver from device manager, I see an option to "Delete the driver software for this device" checkbox.
I tried that and afterwards was rewarded with two Logitech entries in Device Manager that cannot be identified by windows and windows is unable to find drivers for. Seems it really did deleted those drivers. I was unable to find drivers to replace them either. And while both the mouse and keyboard continued to work I could only get rid of the Yellow Exclamation mark on the devices by either disabling or reverting windows.

What's the recommendation here? Seems weird leaving them disabled.

philc43 · 31 Jul 2019

You may need to reinstall the Logitech gaming software to see if it gets rid of the yellow exclamation marks in device manager for the Logitech related drivers.

mKAYDM · 31 Jul 2019

I'm going to close this thread as I feel you all have already answered the core issue, the rest is my applying the correct solution. Thank you very much!