Sign in
 
HomeWindows 8Windows 7Windows VistaWindows XPMDOPWindows IntuneLibraryForums
Windows Client >
> 
> 
Blue Screen Error : Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2:

Answered Blue Screen Error : Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2:

  • Friday, April 02, 2010 6:15 PM
     
     
    Sign In to Vote
    0

    Hello,

    I have a recurring blue screen error my Dell Vostro 1320 (Windows 7) that appears frequently and exclusively, i checked a few posts here and none of them seem to fix, so i give the my dump file detials here and hopefully someone can help me out.

    my dump files as below:

    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Documents and Settings\Nag\Desktop\040110-40934-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`82d65ad4?
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Machine Name:
    Kernel base = 0x82c3f000 PsLoadedModuleList = 0x82d87810
    Debug session time: Fri Apr  2 07:58:13.090 2010 (GMT+5)
    System Uptime: 0 days 0:31:42.822
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................................
    Loading User Symbols
    Loading unloaded module list
    .....

     

    ......................................

    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Documents and Settings\Nag\Desktop\032610-43961-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`82d6bad4?
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Machine Name:
    Kernel base = 0x82c45000 PsLoadedModuleList = 0x82d8d810
    Debug session time: Sat Mar 27 05:12:33.250 2010 (GMT+6)
    System Uptime: 0 days 1:03:55.982
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................................
    Loading User Symbols
    Loading unloaded module list
    .....
    .............................

     


    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Documents and Settings\Nag\Desktop\032410-63430-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`82d3dad4?
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Machine Name:
    Kernel base = 0x82c17000 PsLoadedModuleList = 0x82d5f810
    Debug session time: Thu Mar 25 07:52:28.788 2010 (GMT+5)
    System Uptime: 0 days 0:32:17.520
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................................
    Loading User Symbols
    Loading unloaded module list
    .......

     

    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Documents and Settings\Nag\Desktop\033110-23103-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`82d69ad4?
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Machine Name:
    Kernel base = 0x82c43000 PsLoadedModuleList = 0x82d8b810
    Debug session time: Thu Apr  1 04:34:03.187 2010 (GMT+5)
    System Uptime: 0 days 1:05:48.919
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................................
    Loading User Symbols
    Loading unloaded module list
    .......

     

     

     

    • Edited by Nagendhar Monday, April 05, 2010 1:25 PM
    •  
     

All Replies

  • Friday, April 02, 2010 6:17 PM
     
     
    Sign In to Vote
    0
    The provided information is of little use. Can you upload the contents of c:\windows\minidump to your SkyDrive, and provide a link to the files here?  Maybe someone will check the dumps and offer guidance.
     
  • Monday, April 05, 2010 3:04 AM
    Moderator
     
     
    Sign In to Vote
    1

    Hi,

     

    Since Windows system uses separated user mode and kernel mode memory space, stop errors are usually caused by kernel portion components, such as a hardware device, third-party drivers, backup software or anti-virus services (buggy services).

     

    Please refer to the following steps to troubleshoot the issue.

     

    1. Boot the computer in Clean Boot for a test.

     

    2. Temporarily disable all unnecessary hardware devices in Device Manager, such as Modem, sound card or external device.

     

    For detail steps, we can refer to the link below:

     

    Device Clean Boot

     

    3. Run antivirus program and perform a full scanning.

     

    If the issue persists, please upload the minidump file (%systemroot%\minidump) to SkyDrive ( www.skydrive.live.com ), then share the link to me. I will be glad to assist you to analysis the data.

     

    Thanks,

    Novak

     

     
  • Monday, April 05, 2010 1:30 PM
     
     
    Sign In to Vote
    0

    Hi,

    Thanks for reply and I upload my dump files  in skydrive (contents of c:\windows\minidump), the link as below :

     

    http://cid-3abf63b02cec49f5.skydrive.live.com/browse.aspx/Dumpfiles
    http://cid-3abf63b02cec49f5.skydrive.live.com/browse.aspx/Dumpfiles?sa=476685602

     

     
  • Monday, April 05, 2010 3:32 PM
     
     Answered
    Sign In to Vote
    1

    You get a DRIVER_POWER_STATE_FAILURE bugcheck.

    Do the conditions described in these articles apply to you?

    Error message when you try to resume a Windows 7-based or a Windows Server 2008 R2-based computer from hibernation: "Stop 0x0000009F"

    Stop error when you put a computer that is running Windows 7 or Windows Server 2008 R2 to sleep or into hibernation, or when you restart the computer: "0x9F"

    Consider acquiring and installing an appropriate hotfix.

     
  • Friday, April 16, 2010 3:30 PM
     
     
    Sign In to Vote
    0
    Also look at your sleep pattern. Event Viewer -> System Logs -> Filter Current Log -> Event Source Kernel Power and Power Troubleshooter. See if the machine is constantly going in and out of sleep. If so, check the following setting. Device manager -> NIC > Properties -> Advanced -> Wake Up Capabilites -> Should be set to Magic Packet if you use WOL or None. Wake up Frames allows many things to wake the machine. The constant Wake-ups affects power consumtion and we think the cause of this Driver_Power_State_Failure on our machines as our was set to Both. Our machines are sleeping all night now and no crashes lately.
     
  • Monday, November 01, 2010 11:45 PM
     
     
    Sign In to Vote
    0

    Novak, I need help with the same. Here's the dump file from my system. 

    http://cid-ccb5d0912821a367.office.live.com/self.aspx/Public/110110-24117-01.dmp

    Thanks in advance!

     
  • Tuesday, November 02, 2010 3:10 AM
     
     
    Sign In to Vote
    0

    Rozoan, the driver that appears to be causing the crash is the dne2000.sys which may be part of the Cisco Systems VPN Client package.

    Can you try uninstalling the Cisco VPN Client and see if the issue resolves?

    Uninstalling the Cisco VPN Client may not remove the dne2000.sys (Deterministic Network Enhancer) driver so post back if issue remains after the uninstall.

     
  • Tuesday, December 07, 2010 1:57 PM
     
     
    Sign In to Vote
    0

    Hi there,

     

    I also have been having this issues. 3 of my systems have blue screened 

    Dumb files -

     https://cid-d729667e37d114f4.office.live.com/self.aspx/Dumps/Mini120610-04.zip

    https://cid-d729667e37d114f4.office.live.com/self.aspx/Dumps/Mini120610-03.zip

    https://cid-d729667e37d114f4.office.live.com/self.aspx/Dumps/Mini120610-02.zip

    Please assist.

     
  • Tuesday, December 07, 2010 2:55 PM
     
     
    Sign In to Vote
    0
    your links don't work
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
     
  • Wednesday, December 29, 2010 3:31 PM
     
     
    Sign In to Vote
    0

    I have the same problem. Please help!

      Problem Event Name:                        BlueScreen

      OS Version:                                          6.1.7600.2.0.0.256.48

      Locale ID:                                             1033

    Dump files: http://cid-e158d874e7ed3d01.office.live.com/self.aspx/.Public/122910-16270-01.zip

     
  • Wednesday, December 29, 2010 7:46 PM
     
     
    Sign In to Vote
    0

    Hi Christine,

    you the this error:

    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.

    which is caused by your (very old) nVIDIA driver:

        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sat Nov 21 04:55:33 2009

    Please go to the nVIDIA homepage, download and install the latest driver:

    http://www.nvidia.com/Download/Find.aspx?lang=en-us

    This should fix the error.


    best regards
    André

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
     
  • Wednesday, January 26, 2011 2:32 AM
     
     
    Sign In to Vote
    0

    Dear Andre,

    I've also been experience the same problems and have not been able to analyze the minidumps on my own.  The stop codes vary a lot.  Memory Diagnostics found hardware problems, but the stop codes seem to point to a faulty driver.  Can you please assist?

     

    https://cid-a16fa374d533ff4c.office.live.com/self.aspx/Minidumps/minidumps.zip

     
  • Wednesday, January 26, 2011 1:36 PM
     
     
    Sign In to Vote
    0

    Hi Jason,

    the link doesn't work. I can't see the dumps. put the file into your public folder or change the sharing permissions of the folder Minidumps.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
     
  • Monday, December 12, 2011 8:36 PM
     
     
    Sign In to Vote
    0

    Hi!

    I have a similar problep on my HP nw8440 mobile workstation.

    Here are the dmp files, please help!

    http://members.upclive.hu/mucsi.denes5/minidump.zip

    All 3 bluescreen appered during using the laptop via battery.


    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\121211-30466-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0x82a1f000 PsLoadedModuleList = 0x82b684f0
    Debug session time: Mon Dec 12 20:14:53.793 2011 (UTC + 1:00)
    System Uptime: 0 days 0:04:58.196
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............................................
    Loading User Symbols
    Loading unloaded module list
    ......

     


    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\120611-19281-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0x82a4f000 PsLoadedModuleList = 0x82b984f0
    Debug session time: Tue Dec  6 18:48:37.866 2011 (UTC + 1:00)
    System Uptime: 0 days 0:07:00.145
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................................
    Loading User Symbols
    Loading unloaded module list
    .......

     


    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\120211-24382-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0x82803000 PsLoadedModuleList = 0x8294c4f0
    Debug session time: Fri Dec  2 12:56:38.605 2011 (UTC + 1:00)
    System Uptime: 0 days 0:10:19.009
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................................
    Loading User Symbols
    Loading unloaded module list
    .......

     

     
  • Monday, December 12, 2011 11:13 PM
     
     
    Sign In to Vote
    0
    To start, see if HP has a newer BIOS for your system. It also looks like
    you started out with the debugger, but your symbols path is messed up,
    please see my post here for configuring it,
     
     0: kd>  !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
     
    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 00000061, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 00000000, 0.
    Arg3: 807bf120, The PRCB address of the hung processor.
    Arg4: 00000001, 0.
     
    Debugging Details:
    ------------------
     BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
     
    CUSTOMER_CRASH_COUNT:  1
     
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    CURRENT_IRQL:  1c
     
    STACK_TEXT:
    807f8454 82a9aa2f 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
    807f8490 82a9a07e 00026161 00000000 00004a00 nt!KeAccumulateTicks+0x242
    807f84d0 82a99f2b 82a56c2e 0ee5d2e8 00000000 nt!KeUpdateRunTime+0x145
    807f8528 82a9ebd7 807f851b 807f851b 000000d1 nt!KeUpdateSystemTime+0x613
    807f8528 82a56c2e 807f851b 807f851b 000000d1 nt!KeUpdateSystemTimeAssist+0x13
    807f85cc 82a9fdb9 ac52f000 00000000 807f8624 nt!KeFlushMultipleRangeTb+0x2d5
    807f85e0 82a7d670 a2a6a640 89cef540 a2a6a640 nt!MiFlushPteList+0x22
    807f86ac 88e141f6 ac530000 0001b000 089bddfa nt!MmSetAddressRangeModified+0x205
    807f8778 88e918f7 89cef540 6633e13d 00000000 Ntfs!LfsFlushLfcb+0x3de
    807f87cc 88e8fc12 01cef540 6633e13d 00000000 Ntfs!LfsFlushToLsnPriv+0x1a7
    807f8814 88e8f155 89cef540 00000001 00000000 Ntfs!LfsWriteLfsRestart+0x160
    807f885c 88ebf4ad 89db00f8 00000070 807f89b0 Ntfs!LfsWriteRestartArea+0x120
    807f8adc 88e91df8 807f8bdc 858c40d8 00000000 Ntfs!NtfsCheckpointVolume+0x1185
    807f8b30 88e91c19 807f8bdc 858c40d8 807f8cff Ntfs!NtfsCheckpointAllVolumesWorker+0x3b
    807f8b90 88e91f03 807f8bdc 00000000 88e91dbd Ntfs!NtfsForEachVcb+0x10c
    807f8d00 82a9ca6b 00000000 00000000 84abad48 Ntfs!NtfsCheckpointAllVolumes+0xac
    807f8d50 82c27fda 00000000 a5a04be3 00000000 nt!ExpWorkerThread+0x10d
    807f8d90 82ad01d9 82a9c95e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
     STACK_COMMAND:  kb
     
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: Unknown_Module
     
    IMAGE_NAME:  Unknown_Image
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
     
    FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
     
    BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
     
    Followup: MachineOwner
    ---------
     
    0: kd>  !sysinfo machineid
    Machine ID Information [From Smbios 2.4, DMIVersion 36, Size=1029]
    BiosMajorRelease = 15
    BiosMinorRelease = 17
    FirmwareMajorRelease = 64
    FirmwareMinorRelease = 24
    BiosVendor = Hewlett-Packard
    BiosVersion = 68YVD Ver. F.11
    BiosReleaseDate = 07/03/2007
    SystemManufacturer = Hewlett-Packard
    SystemProductName = HP Compaq nw8440 (RH418EA#ABD)
    SystemFamily = 103C_5336AN
    SystemVersion = F.11
    SystemSKU = RH418EA#ABD
    BaseBoardManufacturer = Hewlett-Packard
    BaseBoardProduct = 30A3
    BaseBoardVersion = KBC Version 40.18
     
     
    -- Mike Burr
    Technology
     
  • Wednesday, December 14, 2011 9:20 AM
     
     
    Sign In to Vote
    0
    I've updated the bios, the problem is still present.
     
  • Wednesday, December 14, 2011 6:33 PM
     
     
    Sign In to Vote
    0
    This could be related to a hardware problem in the processor, can you
    let it crash a few times and upload the dumps and I can see if the
    issues are occurring on a single processor?
     
    -- Mike Burr
    Technology
     
  • Thursday, December 15, 2011 1:05 PM
     
     
    Sign In to Vote
    0

    Here are the files:

    http://members.upclive.hu/mucsi.denes5/minidump.zip

    It only crashes when I'm on batterys if it counts.

    I've also downloaded the intel processor diagnostic tool and all tests were passed.

     
  • Saturday, December 31, 2011 10:18 AM
     
     
    Sign In to Vote
    0
    I've updated the minidump.zip file with an other dump file. It occured when I tried to wake up the laptop from sleep.
    • Edited by omlas01 Saturday, December 31, 2011 10:19 AM
    •  
     
  • Wednesday, January 04, 2012 6:13 PM
     
     
    Sign In to Vote
    0
    As the time passed, I think maybe the problem revealed itself. The bluescreen appears when I activate power save modes, for example ATI Powerplay (VGA), windows sleep. I disabled the sleep mode and set the powerplay in balanced mode and it seems there is no more freeze.
     
  • Friday, April 20, 2012 3:13 AM
     
     
    Sign In to Vote
    0

    Hi!

    I have a similar problem on my HP 8710W.

    I can not log on the computer after my computer showed bad_pool_header even though I reboot it in safe mode,

    so I re-install a new windows 7 and it can work well (the old system was reserved), and now I can choose which operation system I want to boot.

    I upload my dump file (booted form the old system) in skydrive, the link as below :

    https://skydrive.live.com/?cid=B2D7074A6204379C&id=B2D7074A6204379C%21160

    please help! Thanks a lot.

     
  • Thursday, June 07, 2012 1:53 PM
     
     
    Sign In to Vote
    0

    Hi,

    I, too, am experiencing a similar error.

    Log file here - http://sdrv.ms/KezjmE

    Can you please help out on this case.

    Thanks!!


    • Edited by Otlwstr Thursday, June 07, 2012 1:53 PM
    •  
     
  • Tuesday, October 16, 2012 8:18 PM
     
     
    Sign In to Vote
    0

    I am having the same issue.

    Dump file is located at: http://zigsphere.com/dumpreports/101612-25474-01.dmp

    Can anyone help me?

    Thanks

     
  • Wednesday, October 17, 2012 12:05 PM
     
     Answered
    Sign In to Vote
    1

    Hi ZigSphere,

    The error you are receiving, KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) referencing the ataport.sys, may indicate a malware issue.

    I would suggest to download and run the following two applications to see if they pick anything up:

    TDSSKiller:

    http://support.kaspersky.com/faq/?qid=208283363

    Malwarebytes Antimalware (free version) - do a "Full Scan":

    http://www.malwarebytes.org/products/malwarebytes_free

    If you need further help I would suggest to start a new topic on the issue.

     
  • Monday, March 18, 2013 7:34 PM
     
     
    Sign In to Vote
    0

    I cannot figure out what is causing the BSOD on this computer. Can anyone help me out.

    Thanks in advance

    Mcaudle85

    https://skydrive.live.com/redir?resid=9CCF49BF14B0B388!106&authkey=!APGDUl3-1HZL-pE

     
  • Tuesday, March 19, 2013 1:16 AM
     
     
    Sign In to Vote
    0

    Hi Mcaudle85,

    The minidump files showed a consistent KERNEL_DATA_INPAGE_ERROR (7a) stop error.

    Consider running a chkdsk /r on the hard driver.

    Running a chkdsk /r has the potential to take along time and, as general precaution, back up any critical files beforehand

    For clarity and to get better help consider starting a new topic on this BSOD issue.