Windows 10: BSOD SYMBOL_NAME: nt!KiDoubleFaultAbort+344 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe

Discus and support BSOD SYMBOL_NAME: nt!KiDoubleFaultAbort+344 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe in Windows 10 BSOD Crashes and Debugging to solve the problem; ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Francis Manalang1, Jul 10, 2024.

  1. BSOD SYMBOL_NAME: nt!KiDoubleFaultAbort+344 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe


    ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToV8JsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true>>>>>>>>>>>>>

    :)
     
    Francis Manalang1, Jul 10, 2024
    #1
  2. gguthrie Win User

    BSOD started today...

    Thanks - I did the setup, but since this is intermittent, waiting for another failure. When I did the reboot, it did come up in "did not start properly" screen, but I did just restart.

    Looking at the last two minidumps, I noticed:

    The only user program I see is "Manycam.exe", which I have had instealled for 1+ years with no changes or updates...

    I'll repost when I get the specific error reported. Thanks - I've learned a new debugging tool!
     
    gguthrie, Jul 10, 2024
    #2
  3. BSOD SYMBOL_NAME: nt!KeAcquireSpinLockAtDpcLevel+30 Dump File

    I'm not sure how to read this or where to start. Hoping to get some assistance with my dump file:

    For analysis of this file, run !analyze -v

    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: fffff8035f61e380, The address that the exception occurred at

    Arg3: 0000000000000000, Parameter 0 of the exception

    Arg4: ffffffffffffffff, Parameter 1 of the exception



    Debugging Details:

    ------------------





    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 2



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on CDP-10K3WG3-PC



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 3



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 88



    Key : Analysis.System

    Value: CreateObject





    BUGCHECK_CODE: 1e



    BUGCHECK_P1: ffffffffc0000005



    BUGCHECK_P2: fffff8035f61e380



    BUGCHECK_P3: 0



    BUGCHECK_P4: ffffffffffffffff



    READ_ADDRESS: ffffffffffffffff



    EXCEPTION_PARAMETER2: ffffffffffffffff



    BLACKBOXBSD: 1 (!blackboxbsd)





    BLACKBOXNTFS: 1 (!blackboxntfs)





    BLACKBOXPNP: 1 (!blackboxpnp)





    BLACKBOXWINLOGON: 1



    PROCESS_NAME: System



    BAD_STACK_POINTER: fffff80366898158



    STACK_TEXT:

    fffff803`66898158 fffff803`5f8f5a6e : 00000000`0000001e ffffffff`c0000005 fffff803`5f61e380 00000000`00000000 : nt!KeBugCheckEx

    fffff803`66898160 fffff803`5f80006f : fffff803`5f8f5a4c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22

    fffff803`668981a0 fffff803`5f6e6dd7 : fffff803`66898710 00000000`00000000 fffff803`66882b60 fffff803`5f7facd4 : nt!RtlpExecuteHandlerForException+0xf

    fffff803`668981d0 fffff803`5f6e59d6 : fffff803`66882348 fffff803`66898e20 fffff803`66882348 fffff803`5c35a180 : nt!RtlDispatchException+0x297

    fffff803`668988f0 fffff803`5f7f8042 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186

    fffff803`66898fb0 fffff803`5f7f8010 : fffff803`5f8092a5 fffff803`651d2a00 fffff803`66882289 ffffd405`34ed51a0 : nt!KxExceptionDispatchOnExceptionStack+0x12

    fffff803`66882208 fffff803`5f8092a5 : fffff803`651d2a00 fffff803`66882289 ffffd405`34ed51a0 fffff803`704210f9 : nt!KiExceptionDispatchOnExceptionStackContinue

    fffff803`66882210 fffff803`5f804fe0 : ffffd405`3508d520 00000000`0000011d fffff803`6f8fb050 00000000`00000000 : nt!KiExceptionDispatch+0x125

    fffff803`668823f0 fffff803`5f61e380 : fffff803`668825f0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x320

    fffff803`66882580 fffff803`5f961d05 : 00000000`00000200 fffff803`6f991424 00000000`00000000 0000032a`71dbc932 : nt!KeAcquireSpinLockAtDpcLevel+0x30

    fffff803`668825b0 fffff803`5f6188be : 0000032a`7206dd90 00000000`00000000 00000002`a01159fb 00000000`00000000 : nt!PpmIdleUpdateConcurrency+0x35

    fffff803`668825f0 fffff803`5f617104 : 00000000`00000000 00001f80`00000000 00000000`00000003 00000000`00000002 : nt!PpmIdleExecuteTransition+0x163e

    fffff803`668829f0 fffff803`5f7facd4 : 00000000`00000000 fffff803`60127a00 ffffd405`3a2f3080 00000000`0000028a : nt!PoIdle+0x374

    fffff803`66882b60 00000000`00000000 : fffff803`66883000 fffff803`6687c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54





    SYMBOL_NAME: nt!KeAcquireSpinLockAtDpcLevel+30



    MODULE_NAME: nt



    IMAGE_NAME: ntkrnlmp.exe



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 30



    FAILURE_BUCKET_ID: 0x1E_c0000005_R_STACKPTR_ERROR_nt!KeAcquireSpinLockAtDpcLevel



    OS_VERSION: 10.0.19041.1



    BUILDLAB_STR: vb_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {aa18b827-2e4e-bca5-ed1a-4fa7842ab770}



    Followup: MachineOwner

    ---------



    0: kd> lmvm nt

    Browse full module list

    start end module name

    fffff803`5f400000 fffff803`60446000 nt (pdb symbols) c:\symbolcache\ntkrnlmp.pdb\CA8E2F01B822EDE6357898BFBF8629971\ntkrnlmp.pdb

    Loaded symbol image file: ntkrnlmp.exe

    Image path: ntkrnlmp.exe

    Image name: ntkrnlmp.exe

    Browse all global symbols functions data

    Image was built with /Brepro flag.

    Timestamp: 2F0A239F (This is a reproducible build file hash, not a timestamp)

    CheckSum: 00A62034

    ImageSize: 01046000

    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

    Information from resource tables:
     
    Orlando Cardenas, Jul 10, 2024
    #3
  4. FrankRXX Win User

    BSOD SYMBOL_NAME: nt!KiDoubleFaultAbort+344 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe

    Windows 11 22H2 BSOD when connecting to bluetooth headset

    Hello,

    After reinstalling Windows 11 I am getting BSODs when connecting to a bluetooth headset.

    Error: UNEXPECTED_KERNEL_MODE_TRAP

    Some info from the Minidump

    Any help to get this resolved would be highly appreciated.

    Kind regards,

    Frank
     
    FrankRXX, Jul 10, 2024
    #4
Thema:

BSOD SYMBOL_NAME: nt!KiDoubleFaultAbort+344 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe

Loading...
  1. BSOD SYMBOL_NAME: nt!KiDoubleFaultAbort+344 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe - Similar Threads - BSOD SYMBOL_NAME KiDoubleFaultAbort+344

  2. BSOD SYMBOL_NAME: nt!KiDoubleFaultAbort+344 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe

    in Windows 10 Gaming
    BSOD SYMBOL_NAME: nt!KiDoubleFaultAbort+344 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe: ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true...
  3. BSOD SYMBOL_NAME: nt!KiDoubleFaultAbort+344 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe

    in Windows 10 Software and Apps
    BSOD SYMBOL_NAME: nt!KiDoubleFaultAbort+344 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe: ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true...
  4. BSOD nt!KeBugCheckEx on 19045.3208

    in Windows 10 Gaming
    BSOD nt!KeBugCheckEx on 19045.3208: I use IDD to create virtual display, but after created, BSOD happend Low probabilitythis is minidump Details:------------------nt!KeBugCheckEx:fffff801`14ffc0c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffeb85`f10ce9f0=000000000000003b17: kd> !analyze...
  5. BSOD nt!KeBugCheckEx on 19045.3208

    in Windows 10 BSOD Crashes and Debugging
    BSOD nt!KeBugCheckEx on 19045.3208: I use IDD to create virtual display, but after created, BSOD happend Low probabilitythis is minidump Details:------------------nt!KeBugCheckEx:fffff801`14ffc0c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffeb85`f10ce9f0=000000000000003b17: kd> !analyze...
  6. BSOD SYMBOL_NAME: nt!KeAcquireSpinLockAtDpcLevel+30 Dump File

    in Windows 10 Gaming
    BSOD SYMBOL_NAME: nt!KeAcquireSpinLockAtDpcLevel+30 Dump File: I'm not sure how to read this or where to start. Hoping to get some assistance with my dump file: For analysis of this file, run !analyze -v 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * *...
  7. BSOD SYMBOL_NAME: nt!KeAcquireSpinLockAtDpcLevel+30 Dump File

    in Windows 10 Software and Apps
    BSOD SYMBOL_NAME: nt!KeAcquireSpinLockAtDpcLevel+30 Dump File: I'm not sure how to read this or where to start. Hoping to get some assistance with my dump file: For analysis of this file, run !analyze -v 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * *...
  8. BSOD SYMBOL_NAME: nt!KeAcquireSpinLockAtDpcLevel+30 Dump File

    in Windows 10 BSOD Crashes and Debugging
    BSOD SYMBOL_NAME: nt!KeAcquireSpinLockAtDpcLevel+30 Dump File: I'm not sure how to read this or where to start. Hoping to get some assistance with my dump file: For analysis of this file, run !analyze -v 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * *...
  9. BSOD-NT Kernel and System

    in Windows 10 BSOD Crashes and Debugging
    BSOD-NT Kernel and System: I started getting bluescreens out of no where, with no notable changes to the PC coming to mind. Here is the .dmp folder uploaded to onedrive: https://1drv.ms/u/s!AnytooK-At5Qjyon3n4-bgqBoxNx?e=s8pLER...
  10. BSOD-NT Kernel and System

    in Windows 10 BSOD Crashes and Debugging
    BSOD-NT Kernel and System: Hi all, I've got this BSOD every day, just every hour or so. I'm not sure the reason behind it, but is getting really uncomfortable to work with this computer. I've these screenshots of the error. I've reinstalled Windows and the drivers, could you plase help me to locate...