Windows bug check 0x133 — read-only evidence

Checked on 2026-09-16 (Europe/Vienna). No GPU load, settings changes, driver changes, restarts, or permission changes were performed.

Confirmed event

Windows System event 1001, provider Microsoft-Windows-WER-SystemErrorReporting, was recorded at 2026-09-16T22:26:17.6531019+02:00:

0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff801799c53c8, 0x0000000000000000)
Dump: C:\WINDOWS\Minidump\091626-13375-01.dmp
Report ID: 907bd142-1fd8-43c4-b94f-fd23cf9c6022

The time above is the event recording time after reboot; it is not an independently established exact crash time. See system-events.json for the event messages and accompanying 41/6008 events.

Interpretation

Microsoft identifies bug check 0x133 as DPC_WATCHDOG_VIOLATION. Parameter 1 equal to 1 means the system cumulatively spent too long at IRQL DISPATCH_LEVEL or higher. Parameter 2 is the watchdog period; parameter 3 points to the watchdog triage block. Microsoft notes that with parameter 1 equal to 1 the stopped code need not be the offending code.

Source: Microsoft Learn: Bug Check 0x133, read 2026-09-16.

This event alone identifies neither a concrete driver nor failed hardware. No nvlddmkm attribution can be made from this dump until its stack and watchdog data are read.

Analysis blockers

Get-Item on the dump returned PermissionDenied, with the exact message:

Access to the path 'C:\WINDOWS\Minidump\091626-13375-01.dmp' is denied.

The matching WER queue folder was visible with last-write time 2026-09-16T22:31:16.995793+02:00, but listing its contents and reading Report.wer were denied:

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_8c6bb23915d168495fd601e4c76d9b2d204d_00000000_0b96d7a0-4d2b-4eca-89c4-4429b23a4b2d

access-checks.json preserves the exact errors. No access-control changes or privilege escalation were attempted.

No cdb.exe, windbg.exe, windbgx.exe, or kd.exe was found on PATH. No WinDbg Appx package was found for this user. Searches of Windows Kits and the user's WindowsApps aliases found no debugger executable. C:\Program Files (x86)\Windows Kits\10\Debuggers\x64 contains only four support DLLs (listed in debugger-inventory.json), so its existence does not indicate a usable debugger installation.

Consequently !analyze -v, stack extraction, and module attribution were not performed. A readable copy of the existing dump plus a debugger is required to progress; no additional crash reproduction is needed for that step.