BSOD when turning off PC


  1. Posts : 6
    windows 7
       #1

    BSOD when turning off PC


    hello

    i have again problem with my PC.
    i´ve installed cisco vpn client and i think this can be problem, but i am not sure, because for two days after vpn install pc was ok and then problems appeared.
    so here is my story:
    i turned pc on. i connected to my wifi automatically after startup. everything was ok (i had pc on for e.g. 4 hours). and then i hibernated. after resuming from hibernation, pc was not able to connect to wifi or even see wifi networks - with wifi on (nothing changed when i turned it off and on, off ...). so i wanted to restart and then BSOD

    please, can someone tell me what is the problem?
    thank you very much in advance
      My Computer


  2. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #2

    Hello Welcome to SF,

    I guess we won't be able to run your Dump files because it the build is different so it won't recoganize the the image on our Computer. You could try to apply LDR Fix then if the crash happens then post us the Dump file here is the Link Error message on a blue screen on a computer that is running Windows 7 or Windows Server 2008 R2: "STOP: 0x0000000A" it might fix the issue with Dump files.

    Hope this helps,
    Captain
      My Computer


  3. Posts : 6
    windows 7
    Thread Starter
       #3

    hello Captain.

    thank you for info.
    i´ve applied that hotfix, but BSOD is still appearing (again when trying to restart/turn off pc after resume from hibernation), so i am attaching new dump

    thank you for your time
      My Computer


  4. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #4

    eeyore said:
    hello Captain.

    thank you for info.
    i´ve applied that hotfix, but BSOD is still appearing (again when trying to restart/turn off pc after resume from hibernation), so i am attaching new dump

    thank you for your time
    Hello,

    The Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

    Please do the following:
    - activate/validate the Windows installation at Genuine Microsoft Software
    - run sfc.exe /scannow to replace any problem files
    - open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
    - If that doesn't fix it, then wipe the hard drive and reinstall Windows
    - don't use "leaked"/torrent builds

    Post us the MSINFO32 file we will see what we can do !!

    MSINFO32:
    Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
    Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.

    If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

    Hope this helps,
    Captain
      My Computer


  5. Posts : 6
    windows 7
    Thread Starter
       #5

    - my win is activated
    - sfc.exe:
    Verification 100% complete.
    Windows Resource Protection did not find any integrity violations.

    why there is problem reading my dump file? i had problem few months ago with power state failure ... i´ve uploaded dump and that one was readable. were there any updates that made my dumps unreadable?
      My Computer


  6. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #6

    eeyore said:
    - my win is activated
    - sfc.exe:
    Verification 100% complete.
    Windows Resource Protection did not find any integrity violations.

    why there is problem reading my dump file? i had problem few months ago with power state failure ... i´ve uploaded dump and that one was readable. were there any updates that made my dumps unreadable?
    Yup a recent security update might have changed or updated the Kernel version. MS is still trying to work on this issue to fix it. The workaround is to run the analysis on the Computer that has crashed i.e. on your Computer. If you wanna try download the Debugging Tools and can you run it by yourself. Here in this section you have some Tutorials Crash and lockup debug 'How To' - Windows 7 Forums

    Hope this helps,
    Captain
      My Computer


  7. Posts : 6
    windows 7
    Thread Starter
       #7

    thank you Captain.

    tried to run some debugging tools. it stopped when debugging (but there was also error with ntoskrnl.exe).

    so i´ve uninstalled that cisco vpn client and it looks ok now

    thank you for your time and help
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    eeyore said:
    hello

    i have again problem with my PC.
    i´ve installed cisco vpn client and i think this can be problem, but i am not sure, because for two days after vpn install pc was ok and then problems appeared.
    so here is my story:
    i turned pc on. i connected to my wifi automatically after startup. everything was ok (i had pc on for e.g. 4 hours). and then i hibernated. after resuming from hibernation, pc was not able to connect to wifi or even see wifi networks - with wifi on (nothing changed when i turned it off and on, off ...). so i wanted to restart and then BSOD

    please, can someone tell me what is the problem?
    thank you very much in advance
    Love to but cant



    The Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

    Please do the following:
    - activate/validate the Windows installation at Genuine Microsoft Software
    - run sfc.exe /scannow to replace any problem files
    - open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
    - If that doesn't fix it, then wipe the hard drive and reinstall Windows
    - don't use "leaked"/torrent builds





    [cdoe]

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


    Loading Dump File [C:\Users\K\Desktop\040110-19437-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*F:\symbols*Symbol information
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7600 UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x82c3a000 PsLoadedModuleList = 0x82d82810
    Debug session time: Thu Apr 1 11:24:41.578 2010 (GMT-4)
    System Uptime: 0 days 8:57:12.763
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 00000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
    Arg2: 00000258, Timeout in seconds.
    Arg3: 84cc0798, The thread currently holding on to the Pnp lock.
    Arg4: 82d60b24

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

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command 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: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command 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: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    [/code]
      My Computer


  9. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #9

    eeyore said:
    thank you Captain.

    tried to run some debugging tools. it stopped when debugging (but there was also error with ntoskrnl.exe).

    so i´ve uninstalled that cisco vpn client and it looks ok now

    thank you for your time and help
    Before running the Dump file go to File > Image path and set the path to C:\Windows\System32 then run the analysis that might work.

    Hope this helps,
    Captain
      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 21:15.
Find Us