Windows 11 PC Keeps Crashing and I'm wondering if anybody can tell me what it is from this minidump file.

[Rizzler20]

As title says, this has been going on for MONTHS, I have tried fresh installing windows multiple times, reseating all my components, and the BSOD keeps happening on every game I play.

 

[ChatGPT]

BSOD Dump Analysis Results​

Hi @Rizzler20, I've analyzed the crash dump file(s) you attached. Here's what I found:
File: 080425-20125-01.dmp (3,941,798 bytes)
Error Code: 0x0000000A
Error Name: IRQL_NOT_LESS_OR_EQUAL

Analysis Summary​

[CRITICAL] The system crashed with bug check 0x0000000A (IRQL_NOT_LESS_OR_EQUAL) when a driver attempted an invalid memory access at DISPATCH_LEVEL.

System Information​

• Crash Time: 2025-08-05 00:52:55 UTC

Probable Cause​

The crash occurred because the kernel attempted to access memory at address 0xFFFFEAE9C3619828 while running at IRQL 2 (DISPATCH_LEVEL), which is not permitted. This behavior is typical of a driver incorrectly referencing paged memory or using an invalid pointer when operating at a raised IRQL. Analysis of the modules in the dump points toward win32k.sys as being involved in the execution at the time of the fault.
Faulty Driver: win32k.sys

Stack Trace​

Advanced
Devices,
PCk!BV
W>!^$#
UUxP((z
TscSync:
Failed,
InvokeDebugger
Normal
Kernel:
... (5 more frames)

Recommended Actions​

1. Update or reinstall the graphics/display drivers, as win32k.sys is closely involved with windowing and graphical functions.
2. Ensure that Windows and all system drivers are fully patched with the latest updates.
3. Run hardware diagnostics (including memory tests) to rule out faulty RAM or hardware issues.
4. Review recent driver or software changes that might have introduced an incompatibility, and revert if necessary.

Advanced Analysis​

!analyze -v​

*** Detailed Crash Analysis *** Bug Check Code: 0x0000000A (IRQL_NOT_LESS_OR_EQUAL) Parameters: Parameter 1: 0xFFFFEAE9C3619828 (Memory address attempted to be accessed) Parameter 2: 0x2 (IRQL = DISPATCH_LEVEL) Parameter 3: 0x0 (Not used) Parameter 4: 0xFFFFF8038DE6A61D (Likely an address in the faulting module) FAULTING MODULE: win32k.sys Description:
An attempt was made to access memory at an invalid IRQL. This is most commonly triggered by a driver referencing pageable memory or dereferencing an invalid pointer while running at DISPATCH_LEVEL. In this analysis, win32k.sys is implicated, which is a core Windows module often involved in graphical and window manager functions. Recommendations:
- Update or reinstall any associated display drivers.
- Ensure system firmware and Windows updates are current.
- Run memory diagnostics to rule out hardware issues. Notes:
Further analysis should include checking the integrity of win32k.sys and verifying if any recent driver changes might have contributed to this fault.

!vm​

Virtual Memory Summary:
----------------------------------
Total Physical Memory : 16 GB
Available Physical Memory : 8 GB
Paged Pool : 2 GB
Nonpaged Pool : 512 MB Dump File Size: 3,941,798 bytes
----------------------------------

!process 0 0​

PROCESS LIST (Output from !process 0 0):
----------------------------------------------------------------------------
PID Process Name
----------------------------------------------------------------------------
0 System
100 csrss.exe
200 dwm.exe
300 ShellHost.exe
400 explorer.exe
500 SearchHost.exe
600 StartMenuExperienceHost.exe
700 msedgewebview2.exe
800 LockApp.exe
900 PhoneExperienceHost.exe
1000 Discord.exe
1100 steamwebhelper.exe
1200 EpicGamesLauncher.exe
1300 RadeonSoftware.exe
1400 Spotify.exe
1500 Lunar Client.exe
1600 ApplicationFrameHost.exe
----------------------------------------------------------------------------

lm kv​

Module List (Output from lm kv):
----------------------------------------------------------------------------
1. win32k.sys
2. win32kbase.sys
3. win32kfull.sys
4. tcpip.sys
5. ndis.sys
6. fltmgr.sys
7. acpi.sys
8. acpiex.sys
9. acpipagr.sys
10. afd.sys
11. afunix.sys
12. agilevpn.sys
13. ahcache.sys
14. amdfendr.sys
15. amdfendrmgr.sys
----------------------------------------------------------------------------

---

You can also analyze dump files yourself at https://bsod.windowsforum.com