Sign in with
Sign up | Sign in
Your question

Bsod please help! got detailed info!

Last response: in Windows 7
Share
August 3, 2011 11:28:11 PM


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


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

Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0x82c38000 PsLoadedModuleList = 0x82d814d0
Debug session time: Wed Aug 3 13:23:45.600 2011 (UTC - 5:00)
System Uptime: 0 days 15:12:38.410
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 1, 8e77a7ba}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_TxCsqRemoveIrp+213 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8e77a7ba, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82da1848
Unable to read MiSystemVaType memory at 82d80e20
00000000

CURRENT_IRQL: 2

FAULTING_IP:
USBPORT!USBPORT_TxCsqRemoveIrp+213
8e77a7ba 8901 mov dword ptr [ecx],eax

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: 807e0b6c -- (.trap 0xffffffff807e0b6c)
ErrCode = 00000002
eax=8781ba20 ebx=82c730e8 ecx=00000000 edx=85e230f0 esi=874d5970 edi=85e90a40
eip=8e77a7ba esp=807e0be0 ebp=807e0bf0 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
USBPORT!USBPORT_TxCsqRemoveIrp+0x213:
8e77a7ba 8901 mov dword ptr [ecx],eax ds:0023:00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8e77a7ba to 82c795cb

STACK_TEXT:
807e0b6c 8e77a7ba badb0d00 85e230f0 870ca7ec nt!KiTrap0E+0x2cf
807e0bf0 82c54939 85e23028 85e230f0 82c730e8 USBPORT!USBPORT_TxCsqRemoveIrp+0x213
807e0c0c 8e777da6 85e23302 85431b7c 85e23bcc nt!IoCsqRemoveIrp+0x43
807e0c2c 8e7786f6 85e23028 85e230f0 85e23a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x18c
807e0c54 8e7749ce 85e23028 85e23a98 85e23002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
807e0c78 82cb01b5 85e23aa4 85e23002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
807e0cd4 82cb0018 807c4120 807c9800 00000000 nt!KiExecuteAllDpcs+0xf9
807e0d20 82cafe38 00000000 0000000e ffffdfff nt!KiRetireDpcList+0xd5
807e0d24 00000000 0000000e ffffdfff fbfea7be nt!KiIdleLoop+0x38


STACK_COMMAND: kb

FOLLOWUP_IP:
USBPORT!USBPORT_TxCsqRemoveIrp+213
8e77a7ba 8901 mov dword ptr [ecx],eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: USBPORT!USBPORT_TxCsqRemoveIrp+213

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME: USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c04bd

FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_TxCsqRemoveIrp+213

BUCKET_ID: 0xD1_USBPORT!USBPORT_TxCsqRemoveIrp+213

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

1: kd> .trap 0xffffffff807e0b6c
ErrCode = 00000002
eax=8781ba20 ebx=82c730e8 ecx=00000000 edx=85e230f0 esi=874d5970 edi=85e90a40
eip=8e77a7ba esp=807e0be0 ebp=807e0bf0 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
USBPORT!USBPORT_TxCsqRemoveIrp+0x213:
8e77a7ba 8901 mov dword ptr [ecx],eax ds:0023:00000000=????????
1: kd> lmvm USBPORT
start end module name
8e773000 8e7be000 USBPORT (pdb symbols) downstreamstore\usbport.pdb\06E2E8C17F4B40B9A9ED8F0E5BCE65092\usbport.pdb
Loaded symbol image file: USBPORT.SYS
Mapped memory image file: downstreamstore\USBPORT.SYS\4D8C04BD4b000\USBPORT.SYS
Image path: \SystemRoot\system32\DRIVERS\USBPORT.SYS
Image name: USBPORT.SYS
Timestamp: Thu Mar 24 21:58:05 2011 (4D8C04BD)
CheckSum: 000514E3
ImageSize: 0004B000
File version: 6.1.7601.17586
Product version: 6.1.7601.17586
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: usbport.sys
OriginalFilename: usbport.sys
ProductVersion: 6.1.7601.17586
FileVersion: 6.1.7601.17586 (win7sp1_gdr.110324-1501)
FileDescription: USB 1.1 & 2.0 Port Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.

More about : bsod detailed info

a b $ Windows 7
August 4, 2011 2:03:46 AM

Hi there,

Well, the info you provided is very helpful. It points to the driver USBPort.sys as a possible cause.

My Win-7 Ultimate 64bit SP-1 has this file in the System32\Drivers directory, with a creation date of 3/24/11 and a size of 317KB.
That date may indicate it was updated when I installed SP-1 service pack.

Could you have possibly installed a webcam or some other USB device that may have installed an earlier version or even corrupt version of USBPort.sys?
Check the USBPort.sys file properties in the Drivers subdirectory to see if it is the same size and date created as the one on this computer.

To confirm it's the culprit, disconnect all USB devices (use a PS2 keyboard if you have one) and see if you get the BSOD.
The IRQL_NOT_LESS_OR_EQUAL BSOD error is usually a driver problem.
August 4, 2011 6:38:37 AM

mine says the same creation date but has 278kb size.
all i got hooked up is a usb mouse but i do hook other devices up like my ipod touch and usb game controller but i dont have them hooked in all the time. i dont have a ps2 mouse. do you think a usb to ps2 adapter would work the same? becuase i got one of those. thanks for the reply
Related resources
a b $ Windows 7
August 4, 2011 3:34:13 PM

jdh440 said:
mine says the same creation date but has 278kb size.
all i got hooked up is a usb mouse but i do hook other devices up like my ipod touch and usb game controller but i dont have them hooked in all the time. i dont have a ps2 mouse. do you think a usb to ps2 adapter would work the same? becuase i got one of those. thanks for the reply


Yes, using a USB to PS2 converted adapter will place the mouse on an IRQ, not on the USB bus. Then see without any USB devices if you have any more BSOD stops. If not, then it points to the culprit. Did you by chance install about the time as this problem began any USB devices?

Other thing to do (and report on) is go to your Event Viewer, and in the top section, in the Custom Views, Adm Events, see if there is any information related to a Critical Error at the time you had the last BSOD. If so, follow the links to the MS web site to see if they have information as to how to correct it. Report back

In the interim, we can check to see if that driver is available to download and replace yours.

Possibly others can check their USBPort.sys file size and creation date, so see if possibly the one you are using is older. They should be the same size.
August 4, 2011 4:06:09 PM

my usb to ps2 adapter isn't working, i can't test it unless i buy a new mouse. i'll check my bios to see what the usb settings are set to and reply back.
August 4, 2011 4:16:25 PM

my bios says it is set to hi speed which is the full usb 2.0 speed, the other option is legacy support it was turned on. so i guess the bios settings are good. i still don't know why my ps2 adapter isn't working i've had a ps2 mouse before i got the usb mouse but the click button started to mess up. so i know that the port works.
a b $ Windows 7
August 4, 2011 7:59:53 PM

jdh440 said:
my bios says it is set to hi speed which is the full usb 2.0 speed, the other option is legacy support it was turned on. so i guess the bios settings are good. i still don't know why my ps2 adapter isn't working i've had a ps2 mouse before i got the usb mouse but the click button started to mess up. so i know that the port works.


Remember when you connect a PS2 mouse or keyboard, have your computer turned off, then reboot with devices connected, or it can damage the MB.
!