Shutdown BSOD Probably caused by : ntkrnlmp.exe ???


  1. Posts : 1
    Windows 7 x64
       #1

    Shutdown BSOD Probably caused by : ntkrnlmp.exe ???


    I some one can help me to understand this BSOD when I shutdown my PC.
    HP 3074ca with Windows 7 x64

    Thank you!

    Here my dump file:


    HTML Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\021510-23634-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: D:\Symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`0324c000 PsLoadedModuleList = 0xfffff800`03489e50
    Debug session time: Mon Feb 15 20:13:22.373 2010 (GMT-5)
    System Uptime: 1 days 0:30:52.590
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ............................................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000009F, {4, 258, fffffa800552c040, fffff80000b9c510}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    	subsystem.
    Arg2: 0000000000000258, Timeout in seconds.
    Arg3: fffffa800552c040, The thread currently holding on to the Pnp lock.
    Arg4: fffff80000b9c510
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  4
    
    FAULTING_THREAD:  fffffa800552c040
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff800032c5052 to fffff800032c3dda
    
    STACK_TEXT:  
    fffff880`03f77890 fffff800`032c5052 : fffffa80`0552c040 fffffa80`0552c040 00000000`00000000 00000000`00000008 : nt!KiSwapContext+0x7a
    fffff880`03f779d0 fffff800`032c71af : fffffa80`0552db60 fffff880`03b64180 fffff880`000000f2 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
    fffff880`03f77a60 fffff800`03286b1e : 00000000`00000000 fffff800`0000001b 00000000`00000000 fffff880`009b2100 : nt!KeWaitForSingleObject+0x19f
    fffff880`03f77b00 fffff800`032c61bc : ffffffff`fd9da600 fffffa80`0c19fe30 fffff800`034c0400 ffffecfa`0fc3b2c1 : nt!ExpWaitForResource+0xae
    fffff880`03f77b70 fffff800`035183cf : 00000000`00000000 00000000`00000000 00000000`00000001 fffff800`032c8ac1 : nt!ExAcquireResourceExclusiveLite+0x14f
    fffff880`03f77be0 fffff800`033be060 : 00000000`00000000 fffff800`034615f8 00000000`00000001 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1351c
    fffff880`03f77c10 fffff800`032cb161 : fffff800`033be020 fffff880`0234f480 fffffa80`17d2e100 fffffa80`1796db80 : nt!PnpDeviceActionWorker+0x40
    fffff880`03f77cb0 fffff800`03561166 : 81c35e5c`4168c483 fffffa80`0552c040 00000000`00000080 fffffa80`05491890 : nt!ExpWorkerThread+0x111
    fffff880`03f77d40 fffff800`0329c486 : fffff880`03d6a180 fffffa80`0552c040 fffff880`03d750c0 bb000000`80249c89 : nt!PspSystemThreadStartup+0x5a
    fffff880`03f77d80 00000000`00000000 : fffff880`03f78000 fffff880`03f72000 fffff880`03f779f0 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .thread 0xfffffa800552c040 ; kb
    
    FOLLOWUP_IP: 
    nt!KiSwapContext+7a
    fffff800`032c3dda 488d8c2400010000 lea     rcx,[rsp+100h]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!KiSwapContext+7a
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    
    FAILURE_BUCKET_ID:  X64_0x9F_nt!KiSwapContext+7a
    
    BUCKET_ID:  X64_0x9F_nt!KiSwapContext+7a
    
    Followup: MachineOwner
    ---------
    
    0: kd> k
    Child-SP          RetAddr           Call Site
    fffff880`03f77890 fffff800`032c5052 nt!KiSwapContext+0x7a
    fffff880`03f779d0 fffff800`032c71af nt!KiCommitThreadWait+0x1d2
    fffff880`03f77a60 fffff800`03286b1e nt!KeWaitForSingleObject+0x19f
    fffff880`03f77b00 fffff800`032c61bc nt!ExpWaitForResource+0xae
    fffff880`03f77b70 fffff800`035183cf nt!ExAcquireResourceExclusiveLite+0x14f
    fffff880`03f77be0 fffff800`033be060 nt! ?? ::NNGAKEGL::`string'+0x1351c
    fffff880`03f77c10 fffff800`032cb161 nt!PnpDeviceActionWorker+0x40
    fffff880`03f77cb0 fffff800`03561166 nt!ExpWorkerThread+0x111
    fffff880`03f77d40 fffff800`0329c486 nt!PspSystemThreadStartup+0x5a
    fffff880`03f77d80 00000000`00000000 nt!KxStartSystemThread+0x16
    0: kd> lmvm nt
    start             end                 module name
    fffff800`0324c000 fffff800`03829000   nt         (pdb symbols)          d:\symbols\ntkrnlmp.pdb\F8E2A8B5C9B74BF4A6E4A48F180099942\ntkrnlmp.pdb
        Loaded symbol image file: ntkrnlmp.exe
        Mapped memory image file: D:\Symbols\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
        Image path: ntkrnlmp.exe
        Image name: ntkrnlmp.exe
        Timestamp:        Mon Jul 13 19:40:48 2009 (4A5BC600)
        CheckSum:         0054B487
        ImageSize:        005DD000
        File version:     6.1.7600.16385
        Product version:  6.1.7600.16385
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        1.0 App
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ntkrnlmp.exe
        OriginalFilename: ntkrnlmp.exe
        ProductVersion:   6.1.7600.16385
        FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
        FileDescription:  NT Kernel & System
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    No definitive answers in what you've posted, please post the dump files so we can "massage them"
    https://www.sevenforums.com/crash-loc...d-problem.html
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:21.
Find Us