Jump to content

Random BSODs while playing some games

MrBlueSky
By MrBlueSky
in Troubleshooting
 Share
Go to solution Solved by Mavendow,
1 hour ago, MrBlueSky said:

It would appear i'm already running the most recent BIOS on the website - 4021, however I did run the script you sent

In that case, if you haven't already, I'd suggest following @Radium_Angel's suggestion of default BIOS settings. Usually there is a "reset to default" option. If setting everything to default doesn't fix your problem then the two biggest possibilities are a bad BIOS version or PSU voltage. Small possibility of borked motherboard, but I wouldn't rule it out.

 

The next easiest to check is PSU voltage. Grab a copy of HWiNFO and check that the voltages on each rail are within range and not oscillating. For example, I once had a random crash (mostly when playing games) which was caused by a <50ms oscellation of 0.05v on the 12v rail. Larger oscillations are tolerable when they occur over long timespans, but even a small oscillation can be problematic when it occurs rapidly. I say <50ms because HWinfo can only poll every 50ms. I was able to determine it was oscillating faster than that by changing the poll period and watching how often it changed. If setting a shorter poll period resulted in less voltage changes, this would suggest I was setting the poll period to some multiple of the actual oscillation time. Think of it like how car tires seem to spin backward when they move fast enough. I think my specific problem was fairly rare though. 😛

 

Finally, you can try an older BIOS version. Newer isn't always better. That said, AGESA ComboPI v1.2.0.3 was added in BIOS version 4002. AGESA ComboPI v1.2.0.2 fixed an obnoxious USB problem; the previous newest AGESA used was v1.2.0.1. So, going back any earlier than BIOS version 4002 is probably not a good idea. I found several Reddit threads suggesting AGESA ComboPI 1.2.0.3 Patch C was problematic for some people with x570 boards. However, the issue was very uncommon and appears to be related to Ryzen 3xxx or 5xxx series APUs (no reports from the 5800x) so that may be irrelevant.

 

If none of these suggestions help then open Event Viewer, navigate to "Administrative Events" (we only want to see when it fails) then select the option shown in the image below. After that, upload it here and I'll see if there's any broader patterns I can spot aside from the bugchecks and WHEA errors.

 

2021-11-13_175427.png.0763a3c216702ba3a8666c340c81bae1.png

Posted

Hello, heres a bit of info about my machine to start:

CPU - AMD Ryzen 5800x

GPU - Asus Strix Nvidia 1080Ti

MOBO - Asus Prime X570-Pro

RAM - Corsair CMK32GX4M2A2666C16 Vengeance LPX 32GB (2x16GB) DDR4 DRAM 2666MHz

PSU - Corsair RMi 1000W Gold

OS - Windows 10.0.19044 Build 19044

(Attached is my sysinfo file for extra info)

 

I will be playing some games (mainly FF14 and Halo Infinite) and randomly get a BSOD that quickly flashes and then reboots my computer. I was able to find the event in the Event Viewer, and got some info on it, which is also attached in XML format.

 

Somedays its better than others, other days it'll happen every 10-30 minutes and I basically cant play at all.

 

Any information or help would be greatly appreciated! This is getting very frustrating for me lol

 

sysinfo.txt bsod_event.txt

Link to comment
https://linustechtips.com/topic/1403604-random-bsods-while-playing-some-games/
Share on other sites
Link to post
Share on other sites
Posted

turn off the "automatic reboot" after a BSoD.

Then find and upload here (as attachments) any mini crash dumps you can find. I can tell you what's going on

NOTE: I no longer frequent this site. If you really need help, PM/DM me and my e.mail will alert me. 

Link to post
Share on other sites
Posted
  • Author
9 minutes ago, Radium_Angel said:

turn off the "automatic reboot" after a BSoD.

Then find and upload here (as attachments) any mini crash dumps you can find. I can tell you what's going on

Was fairly easy to reproduce, as soon as i logged into my game i got the following BSOD stop code: WHEA_UNCORRECTABLE_ERROR

Here are all of the events leading up to the critical error:
 

events.evtx

Link to post
Share on other sites
Posted
Just now, MrBlueSky said:

Was fairly easy to reproduce, as soon as i logged into my game i got the following BSOD stop code: WHEA_UNCORRECTABLE_ERROR

Here are all of the events leading up to the critical error:
 

events.evtx 68 kB · 0 downloads

I need the .dmp file, please. It's *much* more detailed

NOTE: I no longer frequent this site. If you really need help, PM/DM me and my e.mail will alert me. 

Link to post
Share on other sites
Posted
  • Author
9 minutes ago, aDoomGuy said:

Is your CPU overclocked? Typical BSOD for a bad overclock.

I never overclocked my CPU to my knowlege (why i buy X skews) but since this is a good recommendation, I'm going to play around with the CPU AI Tweaker settings in the BIOS to make sure its not this

Link to post
Share on other sites
Posted
5 minutes ago, MrBlueSky said:

Heres the most recent DMP i could find

011322-5343-01.dmp 1.75 MB · 0 downloads

Thank you, give me a moment.

NOTE: I no longer frequent this site. If you really need help, PM/DM me and my e.mail will alert me. 

Link to post
Share on other sites
Posted

Ok, a single crash dump is difficult to point to a solid issue, but here are some of the relevant details:

 

SYSTEM_SERVICE_EXCEPTION (3b)

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WerFault.exe

SYMBOL_NAME:  Ntfs!NtfsFindPrefixHashEntry+737

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys
___

 

It looks like the Windows Error Reporting Tool crashed because of a possibly corrupted NTFS file system.

Check your hard drive(s) health

NOTE: I no longer frequent this site. If you really need help, PM/DM me and my e.mail will alert me. 

Link to post
Share on other sites
Posted
  • Author
4 minutes ago, Radium_Angel said:

Ok, a single crash dump is difficult to point to a solid issue, but here are some of the relevant details:

 

SYSTEM_SERVICE_EXCEPTION (3b)

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WerFault.exe

SYMBOL_NAME:  Ntfs!NtfsFindPrefixHashEntry+737

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys
___

 

It looks like the Windows Error Reporting Tool crashed because of a possibly corrupted NTFS file system.

Check your hard drive(s) health

Checking my drive's SMART status returns status 'ok' for all drives, unless theres a better health test. Currently exploring the possibility of bad CPU voltage/clock settings as recommended above too

Link to post
Share on other sites
Posted
2 minutes ago, MrBlueSky said:

Checking my drive's SMART status returns status 'ok' for all drives, unless theres a better health test. Currently exploring the possibility of bad CPU voltage/clock settings as recommended above too

Use the hard drive's manufacturer tools to do an in-depth examination of the drives.

NOTE: I no longer frequent this site. If you really need help, PM/DM me and my e.mail will alert me. 

Link to post
Share on other sites
Posted
29 minutes ago, MrBlueSky said:

Checking my drive's SMART status returns status 'ok' for all drives, unless theres a better health test. Currently exploring the possibility of bad CPU voltage/clock settings as recommended above too

Can you send a screenshot with CrystalDiskInfo? If this issue won't be solved until tomorrow I will take a look at the dmp file as well, I'm busy right now.

 

Meanwhile you can run the command

sfc /scannow

with cmd and admin privileges.

Link to post
Share on other sites
Posted
  • Author
1 hour ago, Radium_Angel said:

Use the hard drive's manufacturer tools to do an in-depth examination of the drives.

Used Samsung Magician and it says the health for both drives is good. I was able to get a better DMP file but it is 33gb. I'm pretty sure compressing it would still be too large to upload, how should I go about this?

Link to post
Share on other sites
Posted
Just now, MrBlueSky said:

Used Samsung Magician and it says the health for both drives is good. I was able to get a better DMP file but it is 33gb. I'm pretty sure compressing it would still be too large to upload, how should I go about this?

Re-enable for mini crash dumps, I don't need anything that big to pinpoint errors.

https://www.windows10forums.com/articles/how-to-enable-minidump-logs-in-windows-10.50/

 

But instead of the Small memory dump that it suggests, drop down and use kernel memory dump instead

NOTE: I no longer frequent this site. If you really need help, PM/DM me and my e.mail will alert me. 

Link to post
Share on other sites
Posted
4 minutes ago, MrBlueSky said:

Used Samsung Magician and it says the health for both drives is good. I was able to get a better DMP file but it is 33gb. I'm pretty sure compressing it would still be too large to upload, how should I go about this?

Have you tried these?

1 hour ago, RTX 3071 said:

Can you send a screenshot with CrystalDiskInfo? If this issue won't be solved until tomorrow I will take a look at the dmp file as well, I'm busy right now.

 

Meanwhile you can run the command

sfc /scannow

with cmd and admin privileges.

 

Link to post
Share on other sites
Posted

You guys missed the most basic way to improve NTFS health.

 

Open command prompt (start menu -> type cmd -> right click -> "open as administrator")

Copy/paste the following and hit enter: 

fsutil dirty set c:
shutdown /r /t 0

Then wait for it to do its thing - don't hit any key when it says "press any key to skip."

 

This assumes you don't have DCOM errors in the Event Log; RuntimeBroker DCOM errors are the most common cause of NTFS problems as the RuntimeBroker is involved with file indexing and drive permissions. If there are any DCOM errors in your log you can either ignore them and run sfc/fsutil whenever you have problems or I can walk you through how to repair the errors permanently so your NTFS will not be corrupted in the future.

Link to post
Share on other sites
Posted
  • Author
1 hour ago, Mavendow said:

You guys missed the most basic way to improve NTFS health.

 

Open command prompt (start menu -> type cmd -> right click -> "open as administrator")

Copy/paste the following and hit enter: 

fsutil dirty set c:
shutdown /r /t 0

Then wait for it to do its thing - don't hit any key when it says "press any key to skip."

 

This assumes you don't have DCOM errors in the Event Log; RuntimeBroker DCOM errors are the most common cause of NTFS problems as the RuntimeBroker is involved with file indexing and drive permissions. If there are any DCOM errors in your log you can either ignore them and run sfc/fsutil whenever you have problems or I can walk you through how to repair the errors permanently so your NTFS will not be corrupted in the future.

It looks like i do get some DCOM warnings, should I worry about these?

dcom.evtx

Link to post
Share on other sites
Posted
  • Author
2 hours ago, Radium_Angel said:

Re-enable for mini crash dumps, I don't need anything that big to pinpoint errors.

https://www.windows10forums.com/articles/how-to-enable-minidump-logs-in-windows-10.50/

 

But instead of the Small memory dump that it suggests, drop down and use kernel memory dump instead

After doing this the DMP is still about 1Gb, whats the best way to upload it? I tried compressing using 7z but its still too large to upload here

Link to post
Share on other sites
Posted
9 minutes ago, MrBlueSky said:

After doing this the DMP is still about 1Gb, whats the best way to upload it? I tried compressing using 7z but its still too large to upload here

Hmmm, go back to the small memory dumps then....it should still have the info I need

NOTE: I no longer frequent this site. If you really need help, PM/DM me and my e.mail will alert me. 

Link to post
Share on other sites
Posted
39 minutes ago, MrBlueSky said:

Here is the contents of my C:\Windows\Minidump folder

011022-5578-01.zip 1.32 MB · 0 downloads

Ok, give me some time to sort through this.

NOTE: I no longer frequent this site. If you really need help, PM/DM me and my e.mail will alert me. 

Link to post
Share on other sites
Posted

1st crash dump:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  SearchApp.exe

SYMBOL_NAME:  dxgmms2!CVirtualAddressAllocator::FindNodeInFreeList+ed

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys
___

2nd crash dump:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WerFault.exe

SYMBOL_NAME:  Ntfs!NtfsFindPrefixHashEntry+737

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys
___

3rd crash dump:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000010, Error Source Type
Arg2: ffffdb0310ac2028
Arg3: ffffdb0300ed1b5c
Arg4: ffffdb0300f661a0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_AuthenticAMD__UNKNOWN
___

4th crash dump:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffff888b`83b78448 fffff805`7f7b60dc : 00000000`00000124 00000000`00000010 ffffe608`49af0028 ffffe608`3ca44aac : nt!KeBugCheckEx
ffff888b`83b78450 fffff805`7f7b6c39 : ffffe608`532d7090 ffffe608`532d7090 ffffe608`3ca44a80 ffffe608`44051378 : nt!WheaReportHwError+0x3ec
ffff888b`83b78530 fffff805`7f7b6d55 : 00000000`00000000 00000000`00000062 ffffe608`532d7090 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffff888b`83b78560 fffff805`836835d1 : 00000000`00000000 ffff888b`83b78780 ffffe608`3cb631a0 ffffe608`3cb5b0ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffff888b`83b785c0 fffff805`8367c830 : 00000000`00000000 ffffe608`3cb631a0 ffffe608`3cb691a0 00000000`00000000 : storport!StorpWheaReportError+0x9d
ffff888b`83b78650 fffff805`83664a94 : fffff805`836a9000 00000000`00000062 00000000`00000000 ffff888b`83b789f0 : storport!StorpMarkDeviceFailed+0x358
ffff888b`83b788e0 fffff805`8370a2ed : 00000000`00000500 ffffe608`3cb5b020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x17274
ffff888b`83b789b0 fffff805`8370d4c2 : ffffe608`c1000002 00000000`00000000 ffffe608`3cb5b020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffff888b`83b78a30 fffff805`8370c43f : ffffe608`3cb5b020 ffffe608`3cb63050 ffffe608`4c5a9540 80000000`00002000 : stornvme!NVMeControllerReset+0x10a
ffff888b`83b78a60 fffff805`83679f30 : ffffe608`4c5a9540 ffffe608`3cb63050 ffffe608`3ca9b080 ffffe608`39e8e750 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffff888b`83b78a90 fffff805`7f474825 : ffffe608`53edb080 ffffe608`53edb080 ffffe608`3cb63050 fffff805`8f2b5440 : storport!StorPortWorkItemRoutine+0x40
ffff888b`83b78ac0 fffff805`7f4b8655 : ffffe608`39ee5040 ffffe608`39ee5040 fffff805`7f4746f0 ffffe608`00000000 : nt!IopProcessWorkItem+0x135
ffff888b`83b78b30 fffff805`7f555995 : ffffe608`39ee5040 00000000`00000080 ffffe608`39ee7240 000fe067`b4bbbdff : nt!ExpWorkerThread+0x105
ffff888b`83b78bd0 fffff805`7f5fe938 : fffff805`7c8b6180 ffffe608`39ee5040 fffff805`7f555940 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff888b`83b78c20 00000000`00000000 : ffff888b`83b79000 ffff888b`83b72000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_AuthenticAMD__UNKNOWN
___

5th crash dump:

Pretty much the same as 4th.

 

 

_____

Ok, you have a hardware failure. 

WHEA_UNCORRECTABLE_ERROR (124)

Hardware is bad.

storport!StorpWheaReportError+0x9d

stornvme!ControllerReset+0x1a1

 

This is your m.2 slot.

Either it's gone bad, or the driver is hopelessly corrupt.

I'd start by turning off any XMP and/or OverClocking.

Run a fresh install of Win10.

If you still get it, replace m.2 drive

if it *still* happens, we have a bad board (but let's not start there, that's a last resort)

 

 

NOTE: I no longer frequent this site. If you really need help, PM/DM me and my e.mail will alert me. 

Link to post
Share on other sites
Posted
  • Author
2 minutes ago, Radium_Angel said:

1st crash dump:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  SearchApp.exe

SYMBOL_NAME:  dxgmms2!CVirtualAddressAllocator::FindNodeInFreeList+ed

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys
___

2nd crash dump:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WerFault.exe

SYMBOL_NAME:  Ntfs!NtfsFindPrefixHashEntry+737

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys
___

3rd crash dump:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000010, Error Source Type
Arg2: ffffdb0310ac2028
Arg3: ffffdb0300ed1b5c
Arg4: ffffdb0300f661a0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_AuthenticAMD__UNKNOWN
___

4th crash dump:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffff888b`83b78448 fffff805`7f7b60dc : 00000000`00000124 00000000`00000010 ffffe608`49af0028 ffffe608`3ca44aac : nt!KeBugCheckEx
ffff888b`83b78450 fffff805`7f7b6c39 : ffffe608`532d7090 ffffe608`532d7090 ffffe608`3ca44a80 ffffe608`44051378 : nt!WheaReportHwError+0x3ec
ffff888b`83b78530 fffff805`7f7b6d55 : 00000000`00000000 00000000`00000062 ffffe608`532d7090 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffff888b`83b78560 fffff805`836835d1 : 00000000`00000000 ffff888b`83b78780 ffffe608`3cb631a0 ffffe608`3cb5b0ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffff888b`83b785c0 fffff805`8367c830 : 00000000`00000000 ffffe608`3cb631a0 ffffe608`3cb691a0 00000000`00000000 : storport!StorpWheaReportError+0x9d
ffff888b`83b78650 fffff805`83664a94 : fffff805`836a9000 00000000`00000062 00000000`00000000 ffff888b`83b789f0 : storport!StorpMarkDeviceFailed+0x358
ffff888b`83b788e0 fffff805`8370a2ed : 00000000`00000500 ffffe608`3cb5b020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x17274
ffff888b`83b789b0 fffff805`8370d4c2 : ffffe608`c1000002 00000000`00000000 ffffe608`3cb5b020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffff888b`83b78a30 fffff805`8370c43f : ffffe608`3cb5b020 ffffe608`3cb63050 ffffe608`4c5a9540 80000000`00002000 : stornvme!NVMeControllerReset+0x10a
ffff888b`83b78a60 fffff805`83679f30 : ffffe608`4c5a9540 ffffe608`3cb63050 ffffe608`3ca9b080 ffffe608`39e8e750 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffff888b`83b78a90 fffff805`7f474825 : ffffe608`53edb080 ffffe608`53edb080 ffffe608`3cb63050 fffff805`8f2b5440 : storport!StorPortWorkItemRoutine+0x40
ffff888b`83b78ac0 fffff805`7f4b8655 : ffffe608`39ee5040 ffffe608`39ee5040 fffff805`7f4746f0 ffffe608`00000000 : nt!IopProcessWorkItem+0x135
ffff888b`83b78b30 fffff805`7f555995 : ffffe608`39ee5040 00000000`00000080 ffffe608`39ee7240 000fe067`b4bbbdff : nt!ExpWorkerThread+0x105
ffff888b`83b78bd0 fffff805`7f5fe938 : fffff805`7c8b6180 ffffe608`39ee5040 fffff805`7f555940 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff888b`83b78c20 00000000`00000000 : ffff888b`83b79000 ffff888b`83b72000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_AuthenticAMD__UNKNOWN
___

5th crash dump:

Pretty much the same as 4th.

 

 

_____

Ok, you have a hardware failure. 

WHEA_UNCORRECTABLE_ERROR (124)

Hardware is bad.

storport!StorpWheaReportError+0x9d

stornvme!ControllerReset+0x1a1

 

This is your m.2 slot.

Either it's gone bad, or the driver is hopelessly corrupt.

I'd start by turning off any XMP and/or OverClocking.

Run a fresh install of Win10.

If you still get it, replace m.2 drive

if it *still* happens, we have a bad board (but let's not start there, that's a last resort)

 

 

Interesting, something that may be related is when I tried updating the firmware for my nvme 860 evo it just wouldnt. Updated the firmware for my other samsung ssd just fine. Would it be possible to reinstall the driver or is that m2 ssd hopeless?

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×