New AMD PC blackscreen crashes while gaming

G

gronsvartkatt

Active member
Joined
Mar 1, 2024
Posts
31
  • A brief description of your problem (but you can also include the steps you tried) Completely new built (by me) computer blackscreen crashes while gaming (red dead2 and doom 2016 on steam. I was able to play cracked version of Doom Eternal without issues). The crashes seem somewhat related to loading or scene changes but it can also randomly crash during gameplay. Usually within 1h. Sometimes it has crashed back to desktop without the restart but usually not. I can provide screen of HWinfo for temps but i dont think they are too high. I have done new clean installation of windows, memtest86+, occt cpu testing it gives errors when xmp is on but not with it turned off, but gaming problem persists with XMP off still, different gpu stresstests with no errors, changed different poweroptions and messed around with other settings in windows, turned off freesync on screen, etc..
  • System Manufacturer? x
  • Laptop or Desktop? Desktop
  • Exact model number (if laptop, check label on bottom)
  • OS ? (Windows 11, 10, 8.1, 8, 7, Vista) Windows 10
  • x86 (32bit) or x64 (64bit)? 64-bit
  • (Only for Vista, Windows 7) Service pack?
  • What was original installed OS on system? First install was Windows 11 i then did clean install of Windows 10
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM
  • Age of system? (hardware) 2 weeks
  • Age of OS installation? couple of days
  • Have you re-installed the OS? Yes
  • CPU AMD 7600X
  • RAM (brand, EXACT model, what slots are you using?) G.Skill Trident Z5 RGB DDR5 32GB (2 x 16GB) 6000MHz , F5-6000J3636F16GX2-TZ5RS
  • Video Card XFX 6950XT Speedster 319 Merc
  • MotherBoard - (if NOT a laptop) Asrock b650m Pro Rs Wifi
  • Power Supply - brand & wattage (if laptop, skip this one) Corsair RM850e (850W)
  • Is driver verifier enabled or disabled? Not sure
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth) Only what came with OS
  • Are you using proxy, vpn, ipfilters or similar software? No
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) No
  • Are you currently under/overclocking? Are there overclocking software installed on your system? No (AMD Adrenaline installed)
 

Attachments

I also ran WhoCrashed , posting results also

System Information (local)



Computer name: DESKTOP-D6QN7M4
Windows version: Windows 10, 10.0, version 2009, build: 19045 (x64)
Windows dir: C:\Windows
Hardware: B650M Pro RS WiFi, ASRock
CPU: AuthenticAMD AMD Ryzen 5 7600X 6-Core Processor 8664, level: 25
Processor count:12 logical processors, active mask: 4095
RAM: 31863,9MB





Crash Dump Analysis



Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump
C:\Windows\LiveKernelReports
C:\Windows\LiveKernelReports

On Tue 2024-02-27 23:28:33 your computer crashed or a problem was reported


Crash dump file: C:\Windows\LiveKernelReports\win32k.sys\win32k.sys-20240227-2328.dmp (Minidump)
Bugcheck code: 0xAB(0x1, 0xB0, 0x0, 0x1)
Bugcheck name:SESSION_HAS_VALID_POOL_ON_EXIT
Bug check description:This bug check indicates that a session unload occurred while a session driver still held memory.
Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver.


On Tue 2024-02-27 23:27:45 your computer crashed or a problem was reported


Crash dump file: C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20240227-2327.dmp (Minidump)
Bugcheck code: 0x141(0xFFFFC30DFCEDE460, 0xFFFFF8005D73FF20, 0x0, 0x49F0)
Bugcheck name:VIDEO_ENGINE_TIMEOUT_DETECTED
Driver or module in which error occurred: amdkmdag.sys (amdkmdag+0xFFF20)
File path:amdkmdag.sys
Description: ATI Radeon Kernel Mode Driver
Product: ATI Radeon Family
Company: Advanced Micro Devices, Inc.
Bug check description:This indicates that one of the display engines failed to respond in timely fashion.
Analysis:This is a video related crash. A third party driver was identified as the probable root cause of this system error.
It is suggested you look for an update for the following driver:
amdkmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query:amdkmdag Advanced Micro Devices, Inc. VIDEO_ENGINE_TIMEOUT_DETECTED


On Tue 2024-02-27 21:55:08 your computer crashed or a problem was reported


Crash dump file: C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20240227-2155.dmp (Minidump)
Bugcheck code: 0x141(0xFFFFC30DF2ED5050, 0xFFFFF8005D73FF20, 0x0, 0x3D0C)
Bugcheck name:VIDEO_ENGINE_TIMEOUT_DETECTED
Driver or module in which error occurred: amdkmdag.sys (amdkmdag+0xFFF20)
File path:amdkmdag.sys
Description: ATI Radeon Kernel Mode Driver
Product: ATI Radeon Family
Company: Advanced Micro Devices, Inc.
Bug check description:This indicates that one of the display engines failed to respond in timely fashion.
Analysis:This is a video related crash. A third party driver was identified as the probable root cause of this system error.
It is suggested you look for an update for the following driver:
amdkmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query:amdkmdag Advanced Micro Devices, Inc. VIDEO_ENGINE_TIMEOUT_DETECTED


On Tue 2024-02-27 21:43:26 your computer crashed or a problem was reported


Crash dump file: C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20240227-2143.dmp (Minidump)
Bugcheck code: 0x141(0xFFFFC30DDFFEC010, 0xFFFFF8005D73FF20, 0x0, 0xEA0)
Bugcheck name:VIDEO_ENGINE_TIMEOUT_DETECTED
Driver or module in which error occurred: amdkmdag.sys (amdkmdag+0xFFF20)
File path:amdkmdag.sys
Description: ATI Radeon Kernel Mode Driver
Product: ATI Radeon Family
Company: Advanced Micro Devices, Inc.
Bug check description:This indicates that one of the display engines failed to respond in timely fashion.
Analysis:This is a video related crash. A third party driver was identified as the probable root cause of this system error.
It is suggested you look for an update for the following driver:
amdkmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query:amdkmdag Advanced Micro Devices, Inc. VIDEO_ENGINE_TIMEOUT_DETECTED


On Tue 2024-02-27 21:36:06 your computer crashed or a problem was reported


Crash dump file: C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20240227-2136.dmp (Minidump)
Bugcheck code: 0x141(0xFFFFC30DF2EE7050, 0xFFFFF8005D73FF20, 0x0, 0x2504)
Bugcheck name:VIDEO_ENGINE_TIMEOUT_DETECTED
Driver or module in which error occurred: amdkmdag.sys (amdkmdag+0xFFF20)
File path:amdkmdag.sys
Description: ATI Radeon Kernel Mode Driver
Product: ATI Radeon Family
Company: Advanced Micro Devices, Inc.
Bug check description:This indicates that one of the display engines failed to respond in timely fashion.
Analysis:This is a video related crash. A third party driver was identified as the probable root cause of this system error.
It is suggested you look for an update for the following driver:
amdkmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query:amdkmdag Advanced Micro Devices, Inc. VIDEO_ENGINE_TIMEOUT_DETECTED


On Tue 2024-02-27 20:56:50 your computer crashed or a problem was reported


Crash dump file: C:\Windows\Minidump\022724-4093-01.dmp (Minidump)
Bugcheck code: 0x1A(0x41792, 0xFFFFEC80FA633B90, 0x100000, 0x0)
Bugcheck name:MEMORY_MANAGEMENT
Bug check description:This indicates that a severe memory management error occurred.
Analysis:A corrupted PTE has been detected. This is possibly a software problem. This is a typical case of memory corruption.
This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues


On Tue 2024-02-27 20:56:50 your computer crashed or a problem was reported


Crash dump file: C:\Windows\MEMORY.DMP (Kernel memory dump)
Bugcheck code: 0x1A(0x41792, 0xFFFFEC80FA633B90, 0x100000, 0x0)
Bugcheck name:MEMORY_MANAGEMENT
Bug check description:This indicates that a severe memory management error occurred.
Analysis:A corrupted PTE has been detected. This is possibly a software problem. This is a typical case of memory corruption.
This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues


On Tue 2024-02-27 20:56:06 your computer crashed or a problem was reported


Crash dump file: C:\Windows\Minidump\022724-4140-01.dmp (Minidump)
Bugcheck code: 0xA(0xFFFFF802CBCBF058, 0x2, 0x0, 0xFFFFF8024A123FE0)
Bugcheck name:IRQL_NOT_LESS_OR_EQUAL
Bug check description:This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver.


On Tue 2024-02-27 19:40:05 your computer crashed or a problem was reported


Crash dump file: C:\Windows\LiveKernelReports\AMD_WATCHDOG\AMD_WATCHDOG-20240227-1940.dmp (Minidump)
Bugcheck code: 0xA1000001(0x1, 0x0, 0x0, 0x0)
Bugcheck name:CUSTOM_ERROR
Driver or module in which error occurred: amdfendr.sys (amdfendr+0x4F4DC)
File path:amdfendr.sys
Description: AMD Crash Defender
Product: AMD Driver
Company: Advanced Micro Devices, Inc.
Analysis:A third party driver was identified as the probable root cause of this system error.
It is suggested you look for an update for the following driver:
amdfendr.sys (AMD Crash Defender, Advanced Micro Devices, Inc.).
Google query:amdfendr Advanced Micro Devices, Inc. CUSTOM_ERROR


On Mon 2024-02-26 21:06:06 your computer crashed or a problem was reported


Crash dump file: C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20240226-2106.dmp (Minidump)
Bugcheck code: 0x193(0x804, 0xFFFFFFFFC0000034, 0x108, 0xFFFFF804A153B684)
Bugcheck name:VIDEO_DXGKRNL_LIVEDUMP
Driver or module in which error occurred: amdkmdag.sys (amdkmdag+0x146B684)
File path:amdkmdag.sys
Description: ATI Radeon Kernel Mode Driver
Product: ATI Radeon Family
Company: Advanced Micro Devices, Inc.
Bug check description:A livedump triggered by dxgkrnl occurred. You may have problems with your graphics driver or hardware.
Analysis:This is a video related crash. A third party driver was identified as the probable root cause of this system error.
It is suggested you look for an update for the following driver:
amdkmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query:amdkmdag Advanced Micro Devices, Inc. VIDEO_DXGKRNL_LIVEDUMP





Conclusion



10 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

amdkmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
amdfendr.sys (AMD Crash Defender, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.

Read the suggestions displayed in the bugcheck analysis above.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
The analysis process took 0:00:14 (h:mm:ss).
 
Hello and welcome to the forum.

It would be more useful for you to upload those LiveKernelReports dumps so that we can analyse them properly. They're not captured by the SysnativeBSODCollectionApp because they're dumps taken when a problem occurs from which Windows is able to recover. The WhoCrashed and BlueScreenView tools are frankly of very limited use when analysing BSODs and crashes. It's a bit like trying to describe the inside of a house just by looking through the letterbox.

Based on the two BSOD dumps that were uploaded it would be very useful in the first instance to test your RAM. With 2 x 16GB sticks the most reliable way to do that is simply to remove one stick and run on just the other for a few days - or until you get another BSOD/crash. Then swap sticks and run on just that stick for a few day -or again, until you get a BSOD or crash. The main advantages of this method of testing RAM is, firstly, you can continue to work normally whilst testing your RAM and, secondly, it's guaranteed to highlight a flaky stick.

Let's see how that RAM test goes before we look further, but do please upload the LiveKernelReport dumps in the meantime.
 
Hello, thanks!
I will try running with only one stick at a time and see. How can i attach the dumpfiles, seems like the fileformat isnt supported? Should i put in a RAR or ZIP?
I just tried downloading Hogwarts Legacy wich also blackscreen crashed so it would seem like hardware issue almost 100% right? Blackscreen in 3 separate games (rdr2, hogwarts, doom2016)
Im on latest non-BETA BIOS and latest AMD Adrenaline (24.2.1). Windows is updated.
Edit: Attached a RARfile with the dumpfiles i could find
 

Attachments

Last edited:
I won't claim that I've looked at every single live dump - there are a lot of them - but all those that I have looked at are graphics related. Most are 0x141 VIDEO_ENGINE_TIMEOUT_DETECTED dumps, this indicates that there was a graphics hand and the Windows Timeout Detection and Recovery feature got involved to reset the driver and graphics card to resolve the hang. This usually results in a crash-to-desktop of the app using the graphics at the time. Most of the other live kernel dumps are 0x1B8 VIDEO_MINIPORT_BLACK_SCREEN_LIVEDUMP, these are written when you hold the power button down to force a restart. Was that because of a full system hang?

I really would like you to give the one-RAM-stick testing every chance because flaky RAM can cause all manner of strange issues.

You graphics driver seems to be up to date...
Code: 
0: kd> lmvm amdkmdag
Browse full module list
start             end                 module name
fffff802`6c330000 fffff802`72303000   amdkmdag T (no symbols)          
    Loaded symbol image file: amdkmdag.sys
    Image path: amdkmdag.sys
    Image name: amdkmdag.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Feb 15 21:44:36 2024 (65CE69A4)
    CheckSum:         05F8324D
    ImageSize:        05FD3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
Mini Kernel Dump does not contain unloaded driver list
However this is the driver in which all the 0x141 bugchecks (that I've looked at) occurred. This means that these problems - which Windows was able to recover from - were either graphics driver related or graphics card related. It may be worth removing and re-seating the graphics card, that does sometimes cure similar problems.

Let's see how a length one-RAM-stick test goes on each RAM stick. Once we've eliminated RAM we can look at other possibilities.

Regarding uploads, either .zip or .rar is generally the best way to upload dumps etc.
 
So I have now tried with both sticks separately (In B2 slot, as recommended by Motherboard manual) and still getting blackscreen into restart crashes. Also tried reseating the GPU. Thinking about RMA components and would love some advice what is the most likely perpertrator here. Is there something i could test to rule out some components?
The forced restarts are probably because of the blackscreen, then it restarts after about 5 seconds while fans and RGB still going
 
We're not at the RMA stage yet, this could still easily be a driver problem. I think we need to focus on the two minidumps first and worry about the (less critical) live kernel dumps afterwards. They could of course be linked to the same root cause.

You've tested your RAM in the best way possible, so now we need to see whether a rogue driver is the cause of these two BSODs. What often happens is that a rogue driver fouls up in some way but the foul-up is not detected until sometime later when some other, perfectly innocent, thread accesses the shared data structure that the rogue driver fouled-up. It's at that point that we get the BSOD but the resulting dump of course doesn't tell us anything about the (long gone) rogue driver that originally fouled-up.

The tool we use in this situation is Driver Verier, it's built-in to Windows so is quite safe. Full details on enabling and running Driver Verifier can be found at Driver Verifier Instructions - BSOD - Windows 11, 10, 8(.1), 7 and Vista. Read through those instructions first before you enable Driver Verifier to be sure you fully understand what you'll be doing.

Please note: because Driver Verifier applies additional checks to selected drivers as they are loaded there is a small performance impact in running Driver Verifier. This is something you'll have to live with whilst Driver Verifier is enabled. Also, drivers can only be checked as they are loaded, so it's very important that you use every device, every app, every feature, so that all kernel drivers are loaded at some point whilst Driver Verifier is enabled. This is a very useful tool for highlighting rogue drivers and I do encourage you to persevere with it.

A final note: when Driver Verifier detects a flaky driver it will BSOD, so (hopefully) you'll see many BSODs whilst running with Driver Verifier enabled. By analysing those BSOD dumps we should be able to identify the flaky driver that's causing your issues.
 
Okay, I have activated Driver Verifier and will atempt to cause some juicy BSODs :)
Where can i find the dumps that are generated in that case?
 
Please run the SysnativeBSODCollectionApp again and upload the resulting zip file.
 
If Driver Verifier generates a BSOD the dumps will be in the minidumps folder (C:\Windows\Minidump) but there are no new dumps in there. Your System log also shows that there have been no BSODs, although I can see several crashes (error 41). This is a strong indication that your issue is most likely hardware related. Driver Verier didn't fail any third-party drivers and you're not typically seeing BSODs, just crashes. That indicates that the hardware is failing underneath Windows giving the kernel no opportunity to catch or log the error.

I think now we need to look again at the mass of live kernel 0x141 dumps you've been having for your Radeon RX6950XT graphics card. I can see that you have the iGPU in your AMD CPU disabled....
Code: 
AMD Radeon(TM) Graphics    PCI\VEN_1002&DEV_164E&SUBSYS_164E1002&REV_C7\4&16012499&0&0041    This device is disabled.
This is perfectly normal of course when using a dGPU but this does give us the opportunity to test the system without the RX6950XT card. I'd suggest you enable the iGPU and remove the RX6950XT, plugging the monitor into the motherboard port. Obviously there will be a big graphics performance hit doing this, but if you can't make it BSOD with the RX6950XT removed then we'll know that the card (or possibly the driver) is at fault. At this stage this is a test well worth doing - despite the graphics performance hit.

BTW. If you need to run the SysnativeBSODCollectionApp again it would help if you changed your system language to English first. ;)
 
ubuysa said:
If Driver Verifier generates a BSOD the dumps will be in the minidumps folder (C:\Windows\Minidump) but there are no new dumps in there. Your System log also shows that there have been no BSODs, although I can see several crashes (error 41). This is a strong indication that your issue is most likely hardware related. Driver Verier didn't fail any third-party drivers and you're not typically seeing BSODs, just crashes. That indicates that the hardware is failing underneath Windows giving the kernel no opportunity to catch or log the error.

I think now we need to look again at the mass of live kernel 0x141 dumps you've been having for your Radeon RX6950XT graphics card. I can see that you have the iGPU in your AMD CPU disabled....
Code: 
AMD Radeon(TM) Graphics    PCI\VEN_1002&DEV_164E&SUBSYS_164E1002&REV_C7\4&16012499&0&0041    This device is disabled.
This is perfectly normal of course when using a dGPU but this does give us the opportunity to test the system without the RX6950XT card. I'd suggest you enable the iGPU and remove the RX6950XT, plugging the monitor into the motherboard port. Obviously there will be a big graphics performance hit doing this, but if you can't make it BSOD with the RX6950XT removed then we'll know that the card (or possibly the driver) is at fault. At this stage this is a test well worth doing - despite the graphics performance hit.

BTW. If you need to run the SysnativeBSODCollectionApp again it would help if you changed your system language to English first. ;)
Click to expand...

That sounds like a good idea to test without the dGPU, I will try this today. Should i turn off driver verifier for this or keep it running? And I will change system language! :)
Thank you so much for support!
 
Also, I noted that while running Verifier the power draw and tems on the GPU are much lower, i guess this is normal? Also, the game crashes much faster with it running, within a couple of minutes. This is before taking out GPU, just trying a few times to get a minidump from the crashes.
 
Okay little update again, I reinstalled Adrenaline and chipset drivers, that made me get BSOD with screentearing and also minidumps so Im attaching them also, this happened almost instantly after reboot so I have now turned off driver verifier since it creates instant BSOD
 

Attachments

Constant Driver Verifier BSODs is a good thing because it shows that you have an unstable driver. In both those dumps, which were generated by Driver Verifier failing a third-party driver, the unstable driver is AMDRyzenMasterDriver.sys. It's failed because of a memory pool leakage, possibly because it's failing to properly free it's memory pool allocations before unloading...
Code: 
FAILURE_BUCKET_ID:  0xc4_62_LEAKED_POOL_IMAGE_AMDRyzenMasterDriver.sys
This is exactly the type of driver error that Driver Verifier is useful for detecting.

The version of this driver that you have is dated Aug 2023...
Code: 
11: kd> lmvm AMDRyzenMasterDriver
Browse full module list
start             end                 module name
fffff802`f0d10000 fffff802`f0d3f000   AMDRyzenMasterDriver T (no symbols)           
    Loaded symbol image file: AMDRyzenMasterDriver.sys
    Image path: AMDRyzenMasterDriver.sys
    Image name: AMDRyzenMasterDriver.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Aug  1 10:37:54 2023 (64C8B652)
    CheckSum:         0001AE6D
    ImageSize:        0002F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I'm not an AMD user but AFAIK the AMD Ryzen Master tool is really only needed for overclocking, which you said in your OP you're not doing. Can you try fully uninstalling the AMD Ryzen Master tool and see whether the BSODs stop?
 
Yeah its a bit perplexing since i havent installed it, guessing it comes with Amd Adrenaline software / GPU drivers or the chipset drivers? Or Windows update has downloaded the drivers? But program "Ryzen Master" didnt exist on computer when BSODs happened. I now have installed latest version of it and will see what happens..if issue still persists i guess i try uninstall it now that program actually exists on computer.
The program Ryzen Master worked fine after i downloaded it, after restart it wont launch just gives an error. I also cant uninstall it "because it doesnt have an app associated with it" ....I really dont understand this mess, maybe I somehow messed up when i reinstalled Adrenaline and chipset drivers i guess, since the Verifier BSODS didnt happen before that.
A bit lost for course of action, should i try running with the iGPU or troubleshoot drivers more?
 
Last edited:

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

Back
Top