Three Different BSOD's

bkoyl1 · 26 Apr 2010

See attached zip files.

I would appreciate any help here.

For the first two I have no clue as to why the computer crashed.

For the third I suspect it has something to do with my printer.

See attached.

Jonathan_King · 26 Apr 2010

Your printer being the cause makes sense with one of them. I also wonder if PC Tools is causing the problem. I recommend uninstalling both your printer driver and software, and PC Tools, and see what happens.

Code:

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_042610-21325-01.zip\042610-21325-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: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a17000 PsLoadedModuleList = 0xfffff800`02c54e50
Debug session time: Mon Apr 26 12:32:17.460 2010 (GMT-4)
System Uptime: 0 days 0:00:29.364
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa980c1c7228, 0, fffff88003bd2514, 5}


Could not read faulting driver name
Probably caused by : usbscan.sys ( usbscan!USDeviceControl+49c )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa980c1c7228, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88003bd2514, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbf0e0
 fffffa980c1c7228 

FAULTING_IP: 
usbscan!USDeviceControl+49c
fffff880`03bd2514 410fb74cf500    movzx   ecx,word ptr [r13+rsi*8]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  LXBKbmon.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800388a710 -- (.trap 0xfffff8800388a710)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=fffffa800cc1e620
rdx=fffffa800c20b750 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003bd2514 rsp=fffff8800388a8a0 rbp=0000000000000000
 r8=fffffa800c1c71b0  r9=ffffffffffffffff r10=fffff88003bcc160
r11=fffff8800388a900 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
usbscan!USDeviceControl+0x49c:
fffff880`03bd2514 410fb74cf500    movzx   ecx,word ptr [r13+rsi*8] ds:0004:00000000`00000000=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b06801 to fffff80002a87600

STACK_TEXT:  
fffff880`0388a5a8 fffff800`02b06801 : 00000000`00000050 fffffa98`0c1c7228 00000000`00000000 fffff880`0388a710 : nt!KeBugCheckEx
fffff880`0388a5b0 fffff800`02a856ee : 00000000`00000000 fffffa80`07af0b10 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x40ecb
fffff880`0388a710 fffff880`03bd2514 : fffffa80`07af0b10 00000000`00000000 00000000`80002008 fffff880`0388a920 : nt!KiPageFault+0x16e
fffff880`0388a8a0 fffff880`03bce949 : fffff880`0388a9e0 fffffa80`0c20b750 fffffa80`0c1c7060 fffff880`03bcc110 : usbscan!USDeviceControl+0x49c
fffff880`0388a930 fffff880`04be8825 : fffffa80`0c20ba18 fffffa80`0c20ba60 fffffa80`0c177460 fffffa80`0c20b750 : usbscan!USDispatchIO+0x10d
fffff880`0388a970 fffff800`02da36b7 : fffffa80`0cc1e620 fffff880`0388ac60 fffffa80`00000000 fffffa80`0cc1e620 : ksthunk!CKernelFilterDevice::DispatchIrp+0x11d
fffff880`0388a9d0 fffff800`02da3f16 : 00000000`00000111 00000000`00000074 00000000`00000001 00000000`0040bec0 : nt!IopXxxControlFile+0x607
fffff880`0388ab00 fffff800`02a86853 : 00000000`00000111 fffff960`000f085a 00000000`00000000 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
fffff880`0388ab70 00000000`73a62dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008ebf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73a62dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbscan!USDeviceControl+49c
fffff880`03bd2514 410fb74cf500    movzx   ecx,word ptr [r13+rsi*8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbscan!USDeviceControl+49c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbscan

IMAGE_NAME:  usbscan.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bd2d4

FAILURE_BUCKET_ID:  X64_0x50_usbscan!USDeviceControl+49c

BUCKET_ID:  X64_0x50_usbscan!USDeviceControl+49c

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