Hastebin

System Information (local)
--------------------------------------------------------------------------------

Computer name: DINGO
Windows version: Windows 10, 10.0, version 2009, build: 26200
Windows dir: C:\WINDOWS
Hardware: B650M-H/M.2+, ASRock
CPU: AuthenticAMD AMD Ryzen 5 7500F 6-Core Processor 8664, level: 25
12 logical processors, active mask: 4095
RAM: 33915052032 bytes (31,6GB)




--------------------------------------------------------------------------------
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 Tue 04/08/2026 15:54:57 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\080426-16187-02.dmp
This was probably caused by the following module: mmcss.sys (0xFFFFF8025A12354E) 
Bugcheck code: 0xD1 (0xFFFFE186AA0B3637, 0x2, 0x0, 0xFFFFF8025A12354E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\mmcss.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MMCSS Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Tue 04/08/2026 15:24:51 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\080426-15312-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x1316) 
Bugcheck code: 0x119 (0x1, 0x302E2C, 0x302E25, 0xFFFFCC8D2092F000)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation. 
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Tue 04/08/2026 14:45:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\080426-15937-01.dmp
This was probably caused by the following module: dxgmms2.sys (0xFFFFF802C3068040) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF802C3068040, 0xFFFFBA0C9CBC70C8, 0xFFFFA80182F498F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Tue 04/08/2026 14:08:19 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\080426-15953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4F90B0) 
Bugcheck code: 0xA (0x400000004, 0x2, 0x1, 0xFFFFF80580B4D7CC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Tue 04/08/2026 13:39:28 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\080426-16187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4F90B0) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803AF9D40B0, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. 
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Wed 13/05/2026 13:11:39 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\LiveKernelReports\ResourceTimeout-20260513-1311.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!IoSetFsZeroingOffsetRequired+0x2E11) 
Bugcheck code: 0x1CC (0xFFFF930C34C18800, 0xFFFF930C42F03080, 0x88F, 0x2D)
Error: CUSTOM_ERROR

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider 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 topic general suggestions for troubleshooting system crashes for more information. 

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.