Who Crashed B550 Tomahawk 32Gb 6800xt
Discover the magic of the internet at Imgur, a community powered entertainment destination. Lift your spirits with funny jokes, trending memes, entertaining gifs, inspiring stories, viral videos, and so much more from users.
imgur.com
My PC has recently started blackscreening while I'm AFK. I just upgraded the bios to the latest version and selected XMP to see if that would fix it. Previously I had been running 3800MT/s c16, 1.4v vDimm. I have watercooled the GPU & CPU. I have not tried running 1 stick of RAM yet.
Also I have used macrium reflect multiple times to avoid having to reinstall the OS and now it is giving me an error like it can't verify the contents of the C: drive after restoring a previous clone of the OS.
What's likely to be the problem?
Ryzen 9 5900x
MSI B550 Tomahawk motherboard
AMD 6800xt
8-pack 32Gb Teamgroup pro dark RAM @ XMP
850w platinum Asus ROG Thor power supply unit
Seagate Firecuda 530 4TB primary SSD C:drive
From WhoCrashed:
| Computer name: | 5900X6800XT |
| Windows version: | Windows 10, 10.0, version 2009, build: 19045 (x64) |
| Windows dir: | C:\Windows |
| Hardware: | MS-7C91, Micro-Star International Co., Ltd., MAG B550 TOMAHAWK (MS-7C91) |
| CPU: | AuthenticAMD AMD Ryzen 9 5900X 12-Core Processor 8664, level: 25 |
| Processor count: | 24 logical processors, active mask: 16777215 |
| RAM: | 32690.7MB |
Crash Dump Analysis
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 11/01/2024 09:22:24 your computer crashed or a problem was reported
| Crash dump file: | C:\Windows\Minidumps\011124-6953-01.dmp (Minidump) |
| Bugcheck code: | 0x133(0x1, 0x1E00, 0xFFFFF8015B6FB320, 0x0) |
| Bugcheck name: | DPC_WATCHDOG_VIOLATION |
| Bug check description: | The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). |
| Analysis: | This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. |
On Wed 10/01/2024 18:23:00 your computer crashed or a problem was reported
| Crash dump file: | C:\Windows\Minidumps\011024-7765-01.dmp (Minidump) |
| Bugcheck code: | 0x1E(0xFFFFFFFFC0000005, 0xFFFFF80058BC470C, 0x0, 0x0) |
| Bugcheck name: | KMODE_EXCEPTION_NOT_HANDLED |
| Bug check description: | This indicates that a kernel-mode program generated an exception which the error handler did not catch. |
| Analysis: | This could be caused by either a software or hardware problem. Hardware failure is often caused by overheating. Read this article on thermal issues |
On Tue 09/01/2024 09:26:14 your computer crashed or a problem was reported
| Crash dump file: | C:\Windows\Minidumps\010924-8515-01.dmp (Minidump) |
| Bugcheck code: | 0x133(0x1, 0x1E00, 0xFFFFF80139EFB320, 0x0) |
| Bugcheck name: | DPC_WATCHDOG_VIOLATION |
| Bug check description: | The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). |
| Analysis: | This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. |
Conclusion
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the suggestions displayed in the bugcheck analysis above.
The analysis process took 0:00:06 (h:mm:ss).
Got a link for minidumps:
Minidumps
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Last edited: