none
windows xp sp3 休眠后蓝屏,有dump信息,求解决啊? RRS feed

  • 问题

  • 我的T61 由于升级硬盘,在重装windows xp后,每次休眠后都蓝屏,一下是dump文件的分析信息,大家看看是什么原因造成的啊?

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


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

    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt
    Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
    Debug session time: Thu Apr 29 13:11:47.906 2010 (GMT+8)
    System Uptime: 0 days 0:15:42.655
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    Loading Kernel Symbols
    .......................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ...............
    *** WARNING: Unable to verify timestamp for usbscan.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, f7166ae2, ba3c9b78, 0}

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    Probably caused by : usbscan.sys ( usbscan!USDeviceControl+2a0 )

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

    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    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.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: f7166ae2, The address that the exception occurred at
    Arg3: ba3c9b78, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"

    FAULTING_IP:
    usbscan!USDeviceControl+2a0
    f7166ae2 ??              ???

    TRAP_FRAME:  ba3c9b78 -- (.trap ffffffffba3c9b78)
    Unable to read trap frame at ba3c9b78

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x8E

    LOCK_ADDRESS:  80552f60 -- (!locks 80552f60)

    Resource @ nt!PiEngineLock (0x80552f60)    Available

    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

    1 total locks

    PNP_TRIAGE:
     Lock address  : 0x80552f60
     Thread Count  : 0
     Thread address: 0x00000000
     Thread wait   : 0x0

    LAST_CONTROL_TRANSFER:  from 804f018f to f7166ae2

    STACK_TEXT: 
    ba3c9c40 804f018f 86ae0a60 863fc008 806e7410 usbscan!USDeviceControl+0x2a0
    ba3c9c64 805817f7 86ae0a60 863fc008 86405700 nt!IopStartNextPacketByKeyEx+0x1
    ba3c9d00 8057a274 00000554 00000580 00000000 nt!PipApplyFunctionToSubKeys+0xcb
    ba3c9d34 8054261c 00000554 00000580 00000000 nt!IopGetSetSecurityObject+0xec
    ba3c9d34 7c92e4f4 00000554 00000580 00000000 nt!KiInterruptTemplate+0x72
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0164f80c 00000000 00000000 00000000 00000000 0x7c92e4f4


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    usbscan!USDeviceControl+2a0
    f7166ae2 ??              ???

    SYMBOL_STACK_INDEX:  0

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: usbscan

    IMAGE_NAME:  usbscan.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  480254ce

    SYMBOL_NAME:  usbscan!USDeviceControl+2a0

    FAILURE_BUCKET_ID:  0x8E_usbscan!USDeviceControl+2a0

    BUCKET_ID:  0x8E_usbscan!USDeviceControl+2a0

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

    2010年4月29日 6:28

全部回复