Dell XPS 420 BSOD after sleep


  1. Posts : 2
    Windows 7
       #1

    Dell XPS 420 BSOD after sleep


    Recently instlalled 7 without a hitch and PC running problem free. However after sleep cannot always wake up without BSOD. Sometimes OK sometimes not. Problem issue is USB Driver but all Intel drivers up to date according to Windows and Driver Detective. Any ideas woudl be welcome. Minidump Attached
      My Computer


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

    keven said:
    Recently instlalled 7 without a hitch and PC running problem free. However after sleep cannot always wake up without BSOD. Sometimes OK sometimes not. Problem issue is USB Driver but all Intel drivers up to date according to Windows and Driver Detective. Any ideas woudl be welcome. Minidump Attached

    Hi and welcome

    No surprise its the USB driver LazerUSB.sys

    If driver dective isnt finding a newer one I would suggest doing it manually


    Ken J+





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


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

    Symbol search path is: SRV*d:\symbols*Symbol information
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0x82016000 PsLoadedModuleList = 0x8215e810
    Debug session time: Sun Dec 6 07:40:22.593 2009 (GMT-5)
    System Uptime: 0 days 0:09:52.608
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................
    Loading User Symbols
    Loading unloaded module list
    ........
    3: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    BUGCODE_USB_DRIVER (fe)
    USB Driver bugcheck, first parameter is USB bugcheck code.
    Arguments:
    Arg1: 00000002, BAD_URB The USB client driver has submitted a URB that is
    still attached to another IRP still pending in the bus
    driver.
    Arg2: 84aee008, Address of pending IRP.
    Arg3: 84b872a0, Address of IRP passed in.
    Arg4: a1877b70, Address URB that caused the error.

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

    *** WARNING: Unable to verify timestamp for LazerUsb.sys
    *** ERROR: Module load completed but symbols could not be loaded for LazerUsb.sys

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xFE

    PROCESS_NAME: System

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from 8eb2210c to 820f2d10

    STACK_TEXT:
    a18779d8 8eb2210c 000000fe 00000002 84aee008 nt!KeBugCheckEx+0x1e
    a1877a0c 8eb263ad 8507e028 84b872a0 a1877b70 USBPORT!USBPORT_Core_DetectActiveUrb+0x149
    a1877a50 8eb271f2 86980028 00000000 84b872a0 USBPORT!USBPORT_ProcessURB+0x705
    a1877a78 8eb217c5 86980028 84b872a0 881fc300 USBPORT!USBPORT_PdoInternalDeviceControlIrp+0xfb
    a1877aa0 820524bc 86980028 869802cc 84b872a0 USBPORT!USBPORT_Dispatch+0x18a
    a1877ab8 8f21ec8f 84b872a0 871380e8 00000000 nt!IofCallDriver+0x63
    a1877acc 8f21ee5a 869820e0 87138030 84b872a0 usbhub!UsbhFdoUrbPdoFilter+0x68
    a1877af0 8f21eb92 87138030 84b87358 87138030 usbhub!UsbhPdoInternalDeviceControl+0xf6
    a1877b04 820524bc 87138030 84b872a0 a1877b70 usbhub!UsbhGenDispatch+0x4a
    a1877b1c 934471e6 878aebe8 00000000 878b0024 nt!IofCallDriver+0x63
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a1877b54 93440fb3 878aebe8 a1877b70 878aebe8 LazerUsb+0x311e6
    a1877bd0 93440ffb 878aebe8 a1877be0 0050001f LazerUsb+0x2afb3
    a1877bec 934354e2 878aebe8 00000050 ffffffff LazerUsb+0x2affb
    a1877c34 9343fad3 ffffffff 00000004 00000001 LazerUsb+0x1f4e2
    a1877c64 9343f36b 84c0d228 00000001 a1877cb8 LazerUsb+0x29ad3
    a1877c74 8207eb33 87236028 84c0d228 848f73c0 LazerUsb+0x2936b
    a1877cb8 8f23802b 869820e0 84b64470 77485353 nt!IopfCompleteRequest+0x128
    a1877ccc 8f21e65d 86982028 871380e8 8828ad70 usbhub!UsbhPdoUnblockPendedD0IrpWI+0x87
    a1877cec 822367b5 86982028 84b64470 88284d48 usbhub!UsbhHubWorker+0x51
    a1877d00 82083f2b 88350640 00000000 88284d48 nt!IopProcessWorkItem+0x23
    a1877d50 8222466d 80000000 898f579e 00000000 nt!ExpWorkerThread+0x10d
    a1877d90 820d60d9 82083e1e 80000000 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    LazerUsb+311e6
    934471e6 ?? ???

    SYMBOL_STACK_INDEX: a

    SYMBOL_NAME: LazerUsb+311e6

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: LazerUsb

    IMAGE_NAME: LazerUsb.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 47151cbb

    FAILURE_BUCKET_ID: 0xFE_LazerUsb+311e6

    BUCKET_ID: 0xFE_LazerUsb+311e6

    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 2
    Windows 7
    Thread Starter
       #3

    Thanks Ken - Sorry I have taken so long to come back as I have been away from computers for the last few days and a pleasant change it was too. Anyway back to reality and the search for a new driver. Thanks again.
      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:26.
Find Us