Question Frequent BSODs - " SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) " ?

[Kinkajou]

Have been having frequent BSOD and have had to reinstall Windows a couple of times, this problem started early this year (around May).

The BSODs feel random as the PC could just be idling and it would blue screen. Sometimes it would blue screen on boot and sometimes it would run fine for a while until eventually, it decides to BSOD. Am running Windows 10 with latest BIOS.

Sometimes after a BSOD the computer will restart in recovery mode and will be unable to fix itself, it will also be unable to be run in safe mode.

Specifications:
Motherboard: MSI B650M GAMING PLUS WIFI
CPU: AMD Ryzen 5 7600X 6-Core Processor
Memory: 32 GB @
- 16 GB DDR5-4800, Corsair CMH32GX5M2E6000C36
- 16 GB DDR5-4800, Corsair CMH32GX5M2E6000C36
Graphics: AMD Radeon(TM) Graphics
Graphics: Gigabyte AMD Radeon RX 7600
Main Windows Drive: SSD, TEAM TM8FPK500G, 465.76 GB
Games Drive: SSD, Samsung SSD 990 EVO 1TB, 931.51 GB

What I have done to troubleshoot:
Ran: DISM.exe /Online /Cleanup-image /Restorehealth and sfc/scannow
Updated BIOS
Cleared CMOS
Ran memtest
Check thermals
Reinstalled Windows
Attempted to read and understand BSOD crash reports (to no avail)

The codes I have seen that I can remember
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
CRITICAL_PROCESS_DIED
IRQL_NOT_LESS_OR_EQUAL
SYSTEM_SERVICE_EXCEPTION

Will provide new DMP files on request from newer BSODs.

 

[ubuysa]

Don't upload the kernel dump unless we ask for it - it's large.

Can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

 

[Kinkajou]

Don't upload the kernel dump unless we ask for it - it's large.

Can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

Here is the SysnativeBSODCollectionApp zip file.

 

[ubuysa]

You talked about frequent BSODs but there is only one dump in that upload. The System log shows that there have been many other BSODs. What happened to their dumps? If you run a disk cleanup tool please stop it cleaning dumps!

Based on the one dump we have and on the arguments passed in the other dumps, and visible in the System log, I suspect that the most likely cause here is bad RAM. You have 32GB installed in two 16GB sticks, so the best way to test that RAM is to remove one stick for a few days or a week, or until you get another BSOD. Ensure the one stick is in the correct slot for a one-stick system.

Then swap the sticks over and run on the other stick for a few days or a week. If it BSODs on both sticks on their own then RAM is probably not the issue.

 

[Kinkajou]

You talked about frequent BSODs but there is only one dump in that upload. The System log shows that there have been many other BSODs. What happened to their dumps? If you run a disk cleanup tool please stop it cleaning dumps!

Based on the one dump we have and on the arguments passed in the other dumps, and visible in the System log, I suspect that the most likely cause here is bad RAM. You have 32GB installed in two 16GB sticks, so the best way to test that RAM is to remove one stick for a few days or a week, or until you get another BSOD. Ensure the one stick is in the correct slot for a one-stick system.

Then swap the sticks over and run on the other stick for a few days or a week. If it BSODs on both sticks on their own then RAM is probably not the issue.

I've found in my minidump folder another minidump folder was created inside it with more dumps (Probably my fault) and ran the SysnativeBSODCollectionApp again which has the other minidump files. It's the same link as before but it's a new zip file. Here is the link.

 

[ubuysa]

Now that I've seen the other dumps this looks even more like a RAM issue. Remove a RAM stick as I suggested in post #4.

 

[Kinkajou]

Now that I've seen the other dumps this looks even more like a RAM issue. Remove a RAM stick as I suggested in post #4.

Will have a go and see if I get any more BSODs. Will update in due time when the testing is finished.

Thank you so much for your help .

 

[Kinkajou]

After using the sticks individually for some time I have been able to get BSODs on one of the sticks but not the other. The system is a lot more stable running on an individual stick as well and as such has been taking a very long time to BSOD on the stick. Will have to follow up with Corsair Customer Support to see if I can get them replaced or refunded under warranty. Once again I would like to thank you so much for your help .