1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Windows Vista BSOD after waking up from sleep mode

Discussion in 'Legacy Windows' started by kto, 2009/02/21.

  1. 2009/02/21
    kto

    kto Inactive Thread Starter

    Joined:
    2009/02/21
    Messages:
    3
    Likes Received:
    0
    vista x64 always crashes after waking up from sleep mode, sometimes after a few seconds, sometimes after a few minutes (IRQL_NOT_LESS_OR_EQUAL).
    debugwiz.exe (with windbg x64) gives


    Opened log file 'c:debuglog.txt'

    Microsoft (R) Windows Debugger Version 6.11.0001.402 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

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

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
    Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
    Machine Name:
    Kernel base = 0xfffff800`02660000 PsLoadedModuleList = 0xfffff800`02825db0
    Debug session time: Sat Feb 21 11:24:31.411 2009 (GMT+3)
    System Uptime: 1 days 1:44:00.904
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............
    Loading User Symbols
    Loading unloaded module list
    ............................
    The call to LoadLibrary(exts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    The call to LoadLibrary(kdexts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {0, 2, 1, fffff800026828d1}

    The call to LoadLibrary(exts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    The call to LoadLibrary(kdexts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    The call to LoadLibrary(exts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    The call to LoadLibrary(kdexts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    The call to LoadLibrary(exts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    The call to LoadLibrary(kdexts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    Probably caused by : ntkrnlmp.exe ( nt!KeInsertHeadQueue+2e1 )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff800026828d1, address which referenced memory

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

    The call to LoadLibrary(exts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    The call to LoadLibrary(kdexts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    The call to LoadLibrary(exts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    The call to LoadLibrary(kdexts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    The call to LoadLibrary(exts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    The call to LoadLibrary(kdexts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************

    ADDITIONAL_DEBUG_TEXT:
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: nt

    FAULTING_MODULE: fffff80002660000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35

    WRITE_ADDRESS: The call to LoadLibrary(exts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    The call to LoadLibrary(kdexts) failed, Win32 error 0n2
    Please check your debugger configuration and/or network access.
    0000000000000000

    CURRENT_IRQL: 0

    FAULTING_IP:
    nt!KeInsertHeadQueue+2e1
    fffff800`026828d1 488907 mov qword ptr [rdi],rax

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    LAST_CONTROL_TRANSFER: from fffff800026b50ee to fffff800026b5350

    STACK_TEXT:
    fffffa60`017c4638 fffff800`026b50ee : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffffa60`017c4640 fffff800`026b3fcb : 00000000`00000001 fffff6fd`4002b060 00000000`00000000 fffffa80`01000080 : nt!ZwUnloadKeyEx+0x23ce
    fffffa60`017c4780 fffff800`026828d1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ZwUnloadKeyEx+0x12ab
    fffffa60`017c4910 fffff800`02756d55 : fffffa80`01000080 00000000`00000000 00000000`00055558 00000000`00000000 : nt!KeInsertHeadQueue+0x2e1
    fffffa60`017c4970 fffff800`0275747c : 00000000`00000005 00000000`00000005 00000000`00400000 fffffa80`05642c38 : nt!KdEnableDebugger+0x205
    fffffa60`017c49b0 fffff800`0270e7e1 : 00000000`00000010 00000000`00000246 fffffa80`00f1aa00 fffff800`026c9d95 : nt!KdEnableDebugger+0x92c
    fffffa60`017c49e0 fffff800`02674724 : 00000000`00000006 fffffa80`00f1aa00 fffffa80`072e7840 fffff880`11cd5df8 : nt!wctomb+0xf0d9
    fffffa60`017c4a30 fffff800`028ce62f : fffffa80`05641000 00000000`00000001 00000000`1a3cb000 fffff800`0267003f : nt!MmUnmapIoSpace+0x928
    fffffa60`017c4b40 fffff800`0267cd3c : fffffa80`05641000 00000000`1a3cb000 fffff800`027f28a0 00000000`00000001 : nt!RtlStringFromGUID+0x2697
    fffffa60`017c4b90 fffff800`026ceffa : fffffa80`0444d7a0 fffff800`027d4600 fffffa80`0525b160 007f5000`00000000 : nt!RtlRealSuccessor+0x2ec
    fffffa60`017c4c70 fffff800`026c205a : fffffa80`039ca600 fffff800`0285e8b0 fffffa80`043a8410 fffffa80`00000000 : nt!ExRaiseStatus+0x14ca
    fffffa60`017c4cf0 fffff800`028d7ff3 : fffffa80`039ca600 420a7401`02788366 fffffa80`039c5720 00000000`00000080 : nt!FsRtlNumberOfRunsInBaseMcb+0x126
    fffffa60`017c4d50 fffff800`026ef546 : fffffa60`005ec180 fffffa80`039c5720 fffffa60`005f5d40 00000000`00000001 : nt!ProbeForRead+0xbd3
    fffffa60`017c4d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!_misaligned_access+0x4f6

    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nt!KeInsertHeadQueue+2e1
    fffff800`026828d1 488907 mov qword ptr [rdi],rax
    SYMBOL_STACK_INDEX: 3
    SYMBOL_NAME: nt!KeInsertHeadQueue+2e1
    FOLLOWUP_NAME: MachineOwner
    IMAGE_NAME: ntkrnlmp.exe
    BUCKET_ID: WRONG_SYMBOLS

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

    thanks!
     
    kto,
    #1
  2. 2009/02/21
    Gandalf

    Gandalf Inactive

    Joined:
    2009/02/20
    Messages:
    8
    Likes Received:
    0
    If you are overclocking, I suggest you revert to standard clocking to see if the problem stops.

    If you are not overclocking, then try this...

    Here is a memory test procedure that creates a CD to use for testing the memory.

    Download the ISO current version (memtest86+-1.70.iso.zip) to your PC.

    Extract the .zip file to a location that you know, like the Desktop. You should end up with the file Memtest86+-1.70.iso

    Note: If you have WinRAR (or similar) installed, it will look like an unzippable archive with nothing inside. Do not open it with WinRAR.

    Go to your favorite CD burning software, and choose to burn from an image file. Point to the memtest.iso file and hit the burn button.

    Insert a blank CD into the drive and let it do its magic.

    You now have a memtest bootable CD. Leave the CD in the drive and boot from CD by pressing a key, then running the test. You may need to enter BIOS/Setup via relevant key on your computer and set first boot device.

    NOTE: The longer you run a memory test the better. The more memory you have the longer it should run. Minimum recommended time: 24 hours.

    How to set first boot device in BIOS/Setup:

    Restart the computer/laptop and on the post screen. It should say "To enter setup press?" This could be F1, F2 or Del key or another, refer to your machines manual or manufacturers website. Once in BIOS locate boot order tab and set first boot device to CD, then save and exit.

    Hope this helps.
     
    Gandalf,
    #2


  3. to hide this advert.

  4. 2009/02/21
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    As a sidenote to Gandalf's post please be aware ....
    The only satisfactory way of testing RAM is to test the installed RAM in various configurations. If you have a single module swap it around the slots. If you have a pair of modules run each one singly, swapping between slots; then run them in pairs swapping between pairs of slots. If you have 2 sets of matched modules do not get them mixed up.

    You will have seen from your log that there is a symbol problem - you must be connected to the internet when debugging.
     
    PeteC,
    #3
  5. 2009/02/21
    kto

    kto Inactive Thread Starter

    Joined:
    2009/02/21
    Messages:
    3
    Likes Received:
    0
    I am definitely connected to the internet when debugging. however, debugwiz.exe is said to work incorrectly with vista x64.
    does "Probably caused by : ntkrnlmp.exe" suggest something is wrong with memory in particular?
    will post the results of memtest86 here (the current version is http://www.memtest.org/download/2.11/memtest86+-2.11.iso.zip btw)
     
    kto,
    #4
  6. 2009/02/22
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
    You can download the symbol file/s manually.
    http://www.microsoft.com/whdc/devtools/debugging/debugstart.mspx
    The default location to save the symbols is C:\Symbols, otherwise you will need to change the path
    SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Matt
     
    mattman,
    #5
  7. 2009/02/22
    kto

    kto Inactive Thread Starter

    Joined:
    2009/02/21
    Messages:
    3
    Likes Received:
    0
    despite the correct symbols (Windows_Longhorn.6001.080118-1840.amd64fre.Symbols.exe) now being installed in c:\symbols, i get

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -

    plus, memtest86+ does not seem to find any errors
     
    kto,
    #6
  8. 2009/02/23
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
    Maybe if you can't beat 'em, join 'em :). Try copying the symbols folder into the C:\Windows or one of those other folders. If it works there, change the path to
    SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols

    Did you set the debugwiz.exe to Run as administrator?

    Matt
     
    mattman,
    #7

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...