<Event xmlns="** http://schemas.microsoft.com/win/2004/08/events/event**" > <System> <Provider Name=" Microsoft-Windows-Kernel-Power " Guid=" {331c3b3a-2005-44c2-ac5e-77220c37d6b4} " /><EventID>41</EventID><Version>8</Version><Level>1</Level><Task>63</Task><Opcode>0</Opcode><Keywords>0x8000400000000002</Keywords><TimeCreated SystemTime=" 2024-11-21T07:37:07.3471937Z " /><EventRecordID>56135</EventRecordID><Correlation /><Execution ProcessID=" 4 " ThreadID=" 8 " /><Channel>System</Channel><Computer>DESKTOP-NV14JER</Computer><Security UserID=" S-1-5-18 " /></System> <EventData> <Data Name=" BugcheckCode ">30</Data><Data Name=" BugcheckParameter1 ">0xffffffffc0000005</Data><Data Name=" BugcheckParameter2 ">0xfffff8027a9177e5</Data><Data Name=" BugcheckParameter3 ">0xfffffc888ccbdb18</Data><Data Name=" BugcheckParameter4 ">0xfffff8027e68b920</Data><Data Name=" SleepInProgress ">0</Data><Data Name=" PowerButtonTimestamp ">0</Data><Data Name=" BootAppStatus ">0</Data><Data Name=" Checkpoint ">0</Data><Data Name=" ConnectedStandbyInProgress ">false</Data><Data Name=" SystemSleepTransitionsToOn ">0</Data><Data Name=" CsEntryScenarioInstanceId ">0</Data><Data Name=" BugcheckInfoFromEFI ">false</Data><Data Name=" CheckpointStatus ">0</Data><Data Name=" CsEntryScenarioInstanceIdV2 ">0</Data><Data Name=" LongPowerButtonPressDetected ">false</Data></EventData> </Event> I was suddenly gaming when my PC suddenly crashed with the error code KMODE_UNHANDLED_EXCEPTION_CAUGHT. I do not know what caused it.

Sorry, I was offline, please upload any new minidump files your may have for analysis.

Apologies, the mini dump is on the previous page of replies.

There is only the previous minidump file on that link, is there no new minidump files created?

KMODE_EXCEPTION_NOT_HANDLED help?

Anonymous

<Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">
<System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" /><EventID>41</EventID><Version>8</Version><Level>1</Level><Task>63</Task><Opcode>0</Opcode><Keywords>0x8000400000000002</Keywords><TimeCreated SystemTime="2024-11-21T07:37:07.3471937Z" /><EventRecordID>56135</EventRecordID><Correlation /><Execution ProcessID="4" ThreadID="8" /><Channel>System</Channel><Computer>DESKTOP-NV14JER</Computer><Security UserID="S-1-5-18" /></System>
<EventData> <Data Name="BugcheckCode">30</Data><Data Name="BugcheckParameter1">0xffffffffc0000005</Data><Data Name="BugcheckParameter2">0xfffff8027a9177e5</Data><Data Name="BugcheckParameter3">0xfffffc888ccbdb18</Data><Data Name="BugcheckParameter4">0xfffff8027e68b920</Data><Data Name="SleepInProgress">0</Data><Data Name="PowerButtonTimestamp">0</Data><Data Name="BootAppStatus">0</Data><Data Name="Checkpoint">0</Data><Data Name="ConnectedStandbyInProgress">false</Data><Data Name="SystemSleepTransitionsToOn">0</Data><Data Name="CsEntryScenarioInstanceId">0</Data><Data Name="BugcheckInfoFromEFI">false</Data><Data Name="CheckpointStatus">0</Data><Data Name="CsEntryScenarioInstanceIdV2">0</Data><Data Name="LongPowerButtonPressDetected">false</Data></EventData> </Event>

I was suddenly gaming when my PC suddenly crashed with the error code KMODE_UNHANDLED_EXCEPTION_CAUGHT. I do not know what caused it.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

50 answers

Anonymous

0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff804181177e5, The address that the exception occurred at
Arg3: fffff8041e0737e8, Parameter 0 of the exception
Arg4: fffff8041e08b920, Parameter 1 of the exception

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2078

    Key  : Analysis.Elapsed.mSec
    Value: 4039

    Key  : Analysis.IO.Other.Mb
    Value: 10

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 39

    Key  : Analysis.Init.CPU.mSec
    Value: 609

    Key  : Analysis.Init.Elapsed.mSec
    Value: 72440

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 111

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1e

    Key  : Failure.Bucket
    Value: AV_afd!AfdTLSuperConnectComplete

    Key  : Failure.Hash
    Value: {619a5fb7-7c85-ecb6-3062-8585889ba681}

    Key  : Stack.Pointer
    Value: PRCBException

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

Here is the minidump

0 comments

Anonymous

2024-11-22T21:46:51+00:00

Will this help?
Was this answer helpful?

0 comments No comments
DaveM121 934.5K Reputation points Independent Advisor

2024-11-23T07:15:41+00:00

Sorry, I was offline, please upload any new minidump files your may have for analysis.
Was this answer helpful?

0 comments No comments
Anonymous

2024-11-23T07:22:51+00:00

Apologies, the mini dump is on the previous page of replies.
Was this answer helpful?

0 comments No comments
DaveM121 934.5K Reputation points Independent Advisor

2024-11-23T07:45:07+00:00

There is only the previous minidump file on that link, is there no new minidump files created?
Was this answer helpful?

0 comments No comments