Bugcheck 0x00000133 crashes started last night on 2 week old system.

[Schneider]

System crash while idle last evening, bugcheck was: 0x00000133. Updated AMD chipset driver. Crashed again middle of the night, same bugcheck (might have been running backup programs at the time). No crashes previous to this.

2 week old computer build reusing some parts

Windows 11 24H2, Original Install, Retail
MB, CPU, Ram, boot NVME ~2 weeks old. Powersupply ~ 3 months old, video card ~ 2 years old
OS installation about 2 weeks ago, has not been reinstalled
AMD Ryzen™ 9 9950X 16-Core, 32-Thread Unlocked Desktop Processor
CORSAIR Vengeance 96GB (2 x 48GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model CMK96GX5M2B6000Z30
ASUS GeForce RTX 4070Ti 12GB
ASUS ProArt X870E-CREATOR WiFi AMD AM5 X870E ATX Motherboard
Super Flower Leadex VII XG 1000W 80+ Gold
Driver verifier not installed
Bitdefender
No proxy etc
No disk image tools
No overclocking, memory speed set to CPU default 5600

Note: system has 3 older WD 4TB SSDs plus 2 new Samsung Pro 990 NVME plus and a newer 8TB WD HDD. 2 of 3 monitors new as of 3 days ago.

System is for Lightroom and Photoshop, not gaming.

http://speccy.piriform.com/results/chcHYviZc3GSIwWhf1x2qbM

All help is appreciated

 

[Schneider]

Ran sfc /scannow with no issues found

 

[axe0]

This may be a little tricky. With this sort of crashes we typically need a kernel dump located at C:\Windows\MEMORY.dmp, but from the logs I see there is no such kernel dump.

Could you double check the system recovery configuration is set for kernel dump

1. Open Settings app
2. Go to System and scroll down to About, click on it
3. Go to Advanced system settings
4. Under the section Startup and Recovery click Settings
5. At the dropdown in System Failure, select Kernel memory dump!d
6. Click OK, you can close the prompts now

Based on the stack in both minidumps, there's one driver waiting on multiple objects, which makes sense with this crash that's simply put about multiple processes taking longer than expected to complete. To find the causes (there are most likely multiple) and to give proper advice/suggestions, we'll need a kernel dump.

Bugcheck code 00000133
Arguments 00000000`00000001 00000000`00001e00 fffff803`c11c33a0 00000000`00000000
Debug session time: Sun Jan 26 08:43:01.648 2025 (UTC + 1:00)
System Uptime: 0 days 4:39:18.454
7: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffff8080`9d587cd8 fffff803`c0575129 nt!KeBugCheckEx
01 ffff8080`9d587ce0 fffff803`c0567b61 nt!KeAccumulateTicks+0x589
02 ffff8080`9d587d50 fffff803`c046ebfb nt!KiUpdateRunTime+0xc9
03 ffff8080`9d587dd0 fffff803`c04702ad nt!KeClockInterruptNotify+0x96b
04 ffff8080`9d587f50 fffff803`c087be9e nt!KiCallInterruptServiceRoutine+0x2ed
05 ffff8080`9d587fb0 fffff803`c087c6ac nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
06 fffffc0f`fa7b6db0 fffff803`c04619a0 nt!KiInterruptDispatchNoLockNoEtw+0x3c
07 fffffc0f`fa7b6f40 fffff803`c046f117 nt!KeSetEvent+0x540
08 fffffc0f`fa7b6fd0 fffff803`c046e13f nt!IopCompleteRequest+0x117
09 fffffc0f`fa7b70a0 fffff803`c0543835 nt!KiDeliverApc+0x5af
0a fffffc0f`fa7b7140 fffff803`c0472d83 nt!KiSwapThread+0x9d5
0b fffffc0f`fa7b71d0 fffff803`c041b6ae nt!KiCommitThreadWait+0x483
0c fffffc0f`fa7b7260 fffff803`a2133aa6 nt!KeWaitForMultipleObjects+0x56e
0d fffffc0f`fa7b7360 ffffd581`9f7641b0 ftser2k+0x3aa6
0e fffffc0f`fa7b7368 00000000`00000000 0xffffd581`9f7641b0

 

[Schneider]

Thanks, done, now to wait for the next crash.

 

[axe0]

It'll be too big to upload here probably. If another crash occurs with code 0x133, you can upload it to onedrive, google drive, dropbox or any other similar service you prefer, and post a share link. Please do check that we can download the file without needing to request permissions.

 

[ubuysa]

You are running 24H2 and you have a WD Black SN850X as your system drive. There is a known issue with some WD NVMe SSDs and 24H2 that can only be fixed by updating the firmware for the SSD. Download WD Dashboard and use that to update the SN850X firmware, see whether that solves the problem. It might.

 

[Schneider]

The WD Black SN850X is not my system drive, it is drive D and was not installed in this computer when the operating system was installed. It does have the current firmware. The operating system was installed on a new Samsung 990 Pro 4TB drive. Once I thought my new computer was running properly I transferred the storage drives from my old computer to the new one about 2 weeks ago.

No crashes last night. Backup programs did run to completion. Chrome and WhatsApp were running, Outlook was not although it was during previous crashes (trying to keep things simple). Will keep Outlook running.