BSOD stop: 0x000007F (0X00000000, 0X00000000,0X00000000,0X00000000)

Discussion in 'Windows Vista General Discussion' started by aachahbo, Jan 6, 2008.

  1. aachahbo

    aachahbo Guest

    BSOD stop: 0x000007F (0X00000000, 0X00000000,0X00000000,0X00000000)
    HELP!

    I use Windows Vista Ultimate. When resuming van standby I get a blue
    screen:

    stop: 0x000007F (0X00000000, 0X00000000,0X00000000,0X00000000)

    when I analyse the minidump file, it say that the bluescreen is caused
    by usbscan.sys. I think that is driver is used bij Lexmark printer
    x1155.

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

    Loading Dump File [C:\Windows\Minidump\Mini010208-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: c:\websymbols\
    Executable search path is:
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6000.20697.x86fre.vista_ldr.071009-1543
    Kernel base = 0x82400000 PsLoadedModuleList = 0x82511e10
    Debug session time: Wed Jan 2 13:46:45.353 2008 (GMT+1)
    System Uptime: 0 days 2:04:23.620
    Loading Kernel Symbols
    .........................................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    *
    *
    * Bugcheck Analysis
    *
    *
    *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 7F, {0, 0, 0, 0}
    Probably caused by : usbscan.sys ( usbscan!USTransfer+54d )
    Followup: MachineOwner
    ---------



    Any help is appreciated.

    Ali
     
    aachahbo, Jan 6, 2008
    #1
    1. Advertisements

  2. aachahbo

    aachahbo Guest

    complete bugcheck analysis:


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

    Loading Dump File [C:\Windows\Minidump\Mini010208-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: c:\websymbols\
    Executable search path is:
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6000.20697.x86fre.vista_ldr.071009-1543
    Kernel base = 0x82400000 PsLoadedModuleList = 0x82511e10
    Debug session time: Wed Jan 2 13:46:45.353 2008 (GMT+1)
    System Uptime: 0 days 2:04:23.620
    Loading Kernel Symbols
    .........................................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    *
    *
    * Bugcheck Analysis
    *
    *
    *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 7F, {0, 0, 0, 0}
    Probably caused by : usbscan.sys ( usbscan!USTransfer+54d )
    Followup: MachineOwner
    ---------
    1: kd> !analyze -v
    *******************************************************************************
    *
    *
    * Bugcheck Analysis
    *
    *
    *
    *******************************************************************************
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault). The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
    use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
    use .trap on that value
    Else
    ..trap on the appropriate frame will show where the trap was
    taken
    (on x86, this will be the ebp that goes with the procedure
    KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
    Arg2: 00000000
    Arg3: 00000000
    Arg4: 00000000
    Debugging Details:
    ------------------

    BUGCHECK_STR: 0x7f_0
    TRAP_FRAME: a73e7b4c -- (.trap 0xffffffffa73e7b4c)
    ErrCode = 00000000
    eax=00000014 ebx=892fa968 ecx=8715a420 edx=00000000 esi=883b5970
    edi=00000001
    eip=90b51d67 esp=a73e7bc0 ebp=a73e7bf8 iopl=0 nv up ei pl zr na
    pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
    efl=00010246
    usbscan!USTransfer+0x54d:
    90b51d67 f775ec div eax,dword ptr [ebp-14h]
    ss:0010:a73e7be4=00000000
    Resetting default scope
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    PROCESS_NAME: LXBKbmon.exe
    CURRENT_IRQL: 1
    LAST_CONTROL_TRANSFER: from 825bd427 to 824d8736
    STACK_TEXT:
    a73e7aec 825bd427 0000007f a73ec000 90b51d67 nt!KeBugCheck+0x14
    a73e7b40 8248d848 a73e7b4c a73e7bf8 90b51d67
    nt!Ki386CheckDivideByZeroTrap+0x44
    a73e7b40 90b51d67 a73e7b4c a73e7bf8 90b51d67 nt!KiTrap00+0x88
    a73e7bf8 90b52146 8715a420 85c65de0 00000001 usbscan!USTransfer+0x54d
    a73e7c2c 90b4fa98 8715a420 00000078 88370cd8 usbscan!USWrite+0x98
    a73e7c4c 82427f65 8715a420 85c65de0 85c65de0 usbscan!USDispatchIO+0xe4
    a73e7c64 82588f5d 00000004 85c65de0 85c65f4c nt!IofCallDriver+0x63
    a73e7c84 82594350 8715a420 88370cd8 00000001
    nt!IopSynchronousServiceTail+0x1e0
    a73e7d18 8248caea 8715a420 00000000 00000000 nt!NtWriteFile+0x6fc
    a73e7d18 775a0f34 8715a420 00000000 00000000 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be
    wrong.
    0012f9b0 00000000 00000000 00000000 00000000 0x775a0f34

    STACK_COMMAND: kb
    FOLLOWUP_IP:
    usbscan!USTransfer+54d
    90b51d67 f775ec div eax,dword ptr [ebp-14h]
    SYMBOL_STACK_INDEX: 3
    SYMBOL_NAME: usbscan!USTransfer+54d
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: usbscan
    IMAGE_NAME: usbscan.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 4549b6e9
    FAILURE_BUCKET_ID: 0x7f_0_usbscan!USTransfer+54d
    BUCKET_ID: 0x7f_0_usbscan!USTransfer+54d
    Followup: MachineOwner
    ---------
    1: kd> lmvm usbscan
    start end module name
    90b4a000 90b57000 usbscan (pdb symbols)
    c:\websymbols\usbscan.pdb\29D47C4EB3EC4D2392A438AEE639EF8D1\usbscan.pdb
    Loaded symbol image file: usbscan.sys
    Mapped memory image file:
    c:\websymbols\usbscan.sys\4549B6E9d000\usbscan.sys
    Image path: \SystemRoot\system32\DRIVERS\usbscan.sys
    Image name: usbscan.sys
    Timestamp: Thu Nov 02 10:14:17 2006 (4549B6E9)
    CheckSum: 00010B95
    ImageSize: 0000D000
    File version: 6.0.6000.16386
    Product version: 6.0.6000.16386
    File flags: 0 (Mask 3F)
    File OS: 40004 NT Win32
    File type: 3.0 Driver
    File date: 00000000.00000000
    Translations: 0409.04b0
    CompanyName: Microsoft Corporation
    ProductName: Microsoft® Windows® Operating System
    InternalName: usbscan.sys
    OriginalFilename: usbscan.sys
    ProductVersion: 6.0.6000.16386
    FileVersion: 6.0.6000.16386 (vista_rtm.061101-2205)
    FileDescription: USB Scanner Driver
    LegalCopyright: © Microsoft Corporation. All rights reserved.
     
    aachahbo, Jan 6, 2008
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.