Repository navigation
Tell the AI and the report that a power-button-hold crash does not document its cause - #390
Merged
Merged
Conversation
A 0x1C8 (power button held) or 0xE2 (keyboard or debugger) dump records the user's forced action, not the hang or crash that came first, so the root cause is not in it. Both analysis prompts now say so: the culprit is reported as unknown, a stalled-system finding is an unconfirmed lead, and the recommendations point at how to find the real cause (Kernel-Power 41, Reliability Monitor, recent updates, capturing the next freeze). The BSOD AI rules, the stats meaning for 0x1C8/0xE2 and the local parameter decoding (hold time in ms, triage block pointer) match. Sourced from Microsoft Learn. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A dump from a held power button (0x1C8), the keyboard hotkey or a debugger (0xE2, 0xDEADDEAD) records that action, not the hang or crash before it. The report facts now carry a forcedCrash note, shown as a callout on the report card and included in the forum summary and the markdown export. Live-dump forms are left out: the system kept running. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
faratech
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
FORCED_CRASH_GUIDANCEblock: say the root cause is not established, report the culprit asUnknown (not captured in this dump), treat any stalled-system finding as an unconfirmed lead, don't blame the power button or the user, and recommend how to find the real cause (Kernel-Power Event ID 41, Reliability Monitor, recent driver/firmware/Windows updates, temperatures and storage health, enabling a kernel or complete dump to catch the next freeze). The BSOD AI chat rules, the stats meanings and the local-path parameter decoding (hold time in ms,nt!_POP_POWER_BUTTON_TRIAGE_BLOCK) say the same.npm run checkpasses. The prompt prefix changed, so the first analyses after deploy will not share the old prompt cache.🤖 Generated with Claude Code