BSOD - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - Crash after maybe 2 minutes of load

KleverOne

Member
Joined
Nov 28, 2020
Posts
8
My desktop started blue screening last week, was only doing it once a day or so, I figured I would get to it later.... Go forward to last night and it BSOD, and I rebooted and BSOD again within about 2 minutes of windows load. I went into safe mode, same thing.

I ran chkdsk last night, it ran 4 hours, and upon reboot same thing, I pulled out all but one stick of ram, BSOD, I traded the ram stick BSOD. I went into Windows recovery and tired to roll back the image, and it told me it could not access the file, and try another point...

At this point I am not sure what my next step should be, I can get into DOS and grab the dump file, but I cannot get into the GUI to do anything at all at this point, was looking for some pro help here to avoid reformating...

I have went into DOS and grabbed the MEMORY.dmp file, its about 2.8 gigs. but not suave enough to figure out how to open it with a secondary program...

Cheers all, any insight would be appreciated b/c I do not want to have to reformat....

Desktop
ryzen 7 3800
MSI Carbon gaming pro x570
64 gigs ram
2080 TI
 
Please upload the MEMORY.DMP file onto a file sharing site such as DropBox or Google Drive, and then provide us with the link in your next post.
 
Please upload the MEMORY.DMP file onto a file sharing site such as DropBox or Google Drive, and then provide us with the link in your next post.

Ok so I was stupid and used to Windows 7. I figured out how to get into safe mode, and everything actually works here. I also disabled all the non window services from starting, booted normal and that seemed to have made it more stable. So that being said I was able to get run log collector on the PC and this is the link

Speccy
Speccy.txt

Sysnative Log collector
SysnativeFileCollectionApp.zip

I also ran the BlueScreenviewer and its showing what appears to be this process...

ntoskrnl.exe

I have ran a long running memory diagnostics and the RAM does check out as good, so I guess im kinda in a pause mode b/c im not entirely sure what this service even does.

Cheers!
 
Hi KleverOne ,

The collected BSOD bugchecks were 7E.
Others seen in the logs were D1 and an older 7F.

Windows error reporting was deleted.
During the troubleshooting allow these to collect.
Please don't use Windows disk cleanup, Ccleaner, Glary utilities, Wise cleaner, etc.

The Sysnative log collector appears to have been run while in safe mode.
After performing the steps below return to normal boot (turn off clean boot too) and if there is a BSOD post new Sysnative log collector results.

Boot into Safe Mode on Windows 10
Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

1) Open administrative command prompt (ACP) and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


13) The BIOS: Version/Date American Megatrends Inc. 1.00, 6/14/2019
(approximately 10 missed upgrades)
Upgrade the BIOS to the most up to date non-beta BIOS

MSI Global


Code:
Description
- Updated AMD AGESA ComboAm4v2PI 1.1.0.0 Patch C
- Updated AMD AGESA ComboAm4v2PI 1.0.8.1
- Improved PS/2 KB/Mouse compatibility.
- Improved memory compatibility.
- Updated AMD AGESA ComboAm4v2PI 1.0.0.2
- Improved optical device compatibility.
- Improved system boot up time.
- Improved PCI-E device compatibility.
- Update AMD ComboPI1.0.0.4 Patch B (SMU v46.54)
- Improved system boot up time
- Improved NVMe device compatibility
- Supports AMD Ryzen 5 2400G and Ryzen 3 2200G CPU
- Update AMD ComboPI1.0.0.3abba
- Update AMD ComboPI1.0.0.3abb
- Improve memory compatibility
- Update AMD ComboPI1.0.0.3a


14) Uninstall: logi_joy_vir_hid.sys
Logitech G HUB Virtual HID Device Driver
(also remove the Joy8 Stick)


15) If the computer has Ccleaner (do not install the software if it is not already installed) > click windows tab or custom clean > scroll down to system and advanced > post an image into the thread
If the computer has other cleaning software post similar settings into the thread.


16) Run HD Sentinel: (free or trial edition)
Hard Disk Sentinel - HDD health and temperature monitoring
Hard Disk Sentinel - HDD health and temperature monitoring
For each drive post images of these tabs into the thread:
Overview tab
Temperature
SMART
Disk performance


Code:
logi_joy_vir_hid    Logitech G HUB Virtual HID Device Driver    c:\windows\system32\drivers\logi_joy_vir_hid.sys    Kernel Driver    No    Manual    Stopped    OK    Normal    No    No

Code:
logi_joy_vir_hid.sys Mon Apr 20 11:57:11 2020 (5E9DD467)
 
Ok so I also removed the NVIDIA drivers, but still trying to remove the NVIDA control panel.

When I do a normal boot the computer no longer gives me a blue screen but a total freeze. I went back in safe more and ran these commands as follows...

Microsoft Windows [Version 10.0.18363.1139]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Users\>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1139

Image Version: 10.0.18363.1139

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\Users\>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1139

Image Version: 10.0.18363.1139

[===========================84.9%================= ]
[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Users\One>chkdsk /scan
The type of the file system is NTFS.
This service cannot be started in Safe Mode

A snapshot error occured while scanning this drive. Run an offline scan and fix.

C:\Users\One>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESTRO\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk6\\Partition4"'
Property(s) update successful.

C:\Users\One>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESTRO\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk6\\Partition4"'
Property(s) update successful.

C:\Users\One>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\Users\>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\Users\>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\Users\>bcdedit /enum

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {0d49df38-a65d-11e9-ae5a-e6290cc2637f}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {0d49df3a-a65d-11e9-ae5a-e6290cc2637f}
displaymessageoverride CommandPrompt
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {0d49df38-a65d-11e9-ae5a-e6290cc2637f}
nx OptIn
safeboot Network
bootmenupolicy Standard

I can upload the DISM log if that would be helpful. I have also updated the firmware on the mobo....

I will go into normal mode and rerun the sysnative script.
 
So when I do not boot into safe mode I do not have time to run the script before the computer locks up... Have tried about 6 times and it always seems to freeze at about the same time every time.
 
When available update the progress with post #4 steps #13 - #16.

List non-Microsoft software:
a) antivirus
b) firewall
c) drive encryption
 
When available update the progress with post #4 steps #13 - #16.

List non-Microsoft software:
a) antivirus
b) firewall
c) drive encryption

13) I had already updated the firmware on the motherboard
14) Do not see these in my device manager.... These would be under sound, video and game controllers?
15)
1606769978365.png

16) I already have had this installed and all my hard drives check in good, I can include
screen shots but everything is healthy and running at acceptable temps.

Non-Microsfot Software
Anti-virus - Use windows defender and scan with Malware Bytes sometimes but it doesnt load unless I tell it to
Firewall - Use Windows
Drive encryption - None
 
Last edited:
Ok so I also removed the NVIDIA drivers, but still trying to remove the NVIDA control panel.

When I do a normal boot the computer no longer gives me a blue screen but a total freeze. I went back in safe more and ran these commands as follows...


For Ccleaner see post #4 step #15: scroll down to system and advanced > post an image into the thread

Only advanced was posted. Please include system.



In this thread we did not discuss Nvidia drivers.

That was in another website thread.


logi_joy_vir_hid.sys was the misbehaving driver in one collected mini dump file.

It appears that you had already uninstalled this misbehaving driver.



Having multiple forum threads open simultaneously appears to be confusing you.

And it will eventually confuse those offering help.


Which other websites have you opened threads for the same problem?
 
For Ccleaner see post #4 step #15: scroll down to system and advanced > post an image into the thread

Only advanced was posted. Please include system.



In this thread we did not discuss Nvidia drivers.

That was in another website thread.


logi_joy_vir_hid.sys was the misbehaving driver in one collected mini dump file.

It appears that you had already uninstalled this misbehaving driver.



Having multiple forum threads open simultaneously appears to be confusing you.

And it will eventually confuse those offering help.


Which other websites have you opened threads for the same problem?

I am following this one the most. The nvida drivers where uninstalled mainly b/c I have had issues with those drivers previously and figure it would be helpful to just remove them.... Also seeing how the freezes where happening it appeared to be a similar issue I have seen in the past with those drivers.

On a good note, I guess I was being stupid and didn't think to stop the start-up processes, I only had a handful starte, but i disabled them all and the PC seems most stable, have not had a crash yet. in the past hour.

I would like to know what was causing it, so I did turn 4 of the processes back, ones I didn't think had any issues, and was correct, no bad behaviour again in about an hour.....

So that being said I still have the nvida control panel installed, and am thinking of just reinstalling those drivers and give it another reboot....

I have a feeling I know what is causing the issue, I have a HDMI to USB converter for one of my monitors, and I have a feeling that might be the cause...

Instially I was thinking it was powertools, or a wallpaper app I have running but I had noticed screen flickering on that monitor since this issue started, and I really havge not trusted taht driver as is, b/ci its some one off device/driver.......

So I think its one of those 3 that is causing the issue, right now I have them all turned off and no issues. Once i reinstall the Nvidia drivers I think that will tell me more, will keep you posted!

Cheers for the hand here bro!
 
I am following this one the most. The nvida drivers where uninstalled mainly b/c I have had issues with those drivers previously and figure it would be helpful to just remove them.... Also seeing how the freezes where happening it appeared to be a similar issue I have seen in the past with those drivers.
To keep track of the different steps on the different websites for the same BSOD problem can be challenging.

The other websites were not yet displayed.

Weren't you instructed to uninstall Nvidia GPU drivers and / or use Windows driver verifier?

To reduce / eliminate any confusion let's close this thread so that you can continue with one of the websites.
 
To keep track of the different steps on the different websites for the same BSOD problem can be challenging.

The other websites were not yet displayed.

Weren't you instructed to uninstall Nvidia GPU drivers and / or use Windows driver verifier?

To reduce / eliminate any confusion let's close this thread so that you can continue with one of the websites.

This is not my first time time trying to troubleshoot a BSOD. I have always felt it helpful to open afew threads, and usually would start moving forward with the one site that seemed the most helpful, has always worked for me, and your suggestions had been very helpful... and I was intending to work the rest of the problem on this one. I def am power user but not a forensics expert, so insight such as yours is most helpful.

One person did suggest uninstall the drivers BUT the main reason I uninstalled the nvida drivers, was I have had numerous issues in the past with them, on multiple PCs, and this seemed like a logical thing to do, until I was able to get the OS stable. Especially considering the graphic glitches I was seeing when the computer froze. I had seen similar behavior, and actually that and the flickering of the monitor with the USB monitor, leads me to think that, that driver might be the cause of it since Windows issued the new update the other week. Strangely enough rolling back that update did not resolve the issue, I tried that before even opening a thread.

Cheers, and thanks for the help bro!
 
Quick update, so I was able to stop the bsod and then it startd running very slow.... I exhausted everything SSD drivers, CPU drivers, tried rolling back updates, computer still was running beyond sluggish...

Last night I applied the latest Windows update, hoped back on today since the update was finished and the computer is running great... I have a ton of software to reinstall, BUT it appears the Windows patch from the other week hosed something up on my computer.... Looks like they patched the patch.......

The strange thing is I could find no information on what the back patch broke, or any mention of it.....

Needless to say i think it was a bad Windows patch that broke the PC and a patch of the patch fixed it!

Cheers!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top