💻 Software
Analyzing a WinDbg dump after a BSOD - "An expected clock interrupt was not received"
Fresh7 days ago
Mar 15, 20265437 viewsConfidence Score0%
0%
Problem
About six months ago I upgraded my computer hardware - new mobo, CPU, RAM, etc. It's run like a champ until just recently. This morning when I went to my computer it had a BSOD. I used WinDbg to analyze the minidump. Can someone help analyze these results? Here are the initial results: When I ran t…
Error Output
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, fffff88002f65180, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCON…Unverified for your environment
Select your OS to check compatibility.
1 Fix
Canonical Fix
Unverified Fix
New Fix – Awaiting Verification
Fix for: Analyzing a WinDbg dump after a BSOD - "An expected clock interrupt was not received"
Low Risk
Basically, one of your processors has detected that one of your OTHER processors has stopped receiving clock interrupts. The one that detected the condition then bugchecks and tells you which processor was hung: The question then becomes, "what was …
Awaiting Verification
Be the first to verify this fix
Sign in to verify this fix