Blue Screen DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

Hello Guys

I was using a Dell Latitude E6500 but I put it aside for the past months due to too many blue screens. All Dell could advise was to reinstall everything....

But now that I found the forum I hope one of the experts can help. The laptop is running with Vista Ultimate 64bit SP2.

Blue screens appear randomly but seem to be more frequent when using USB ports.

I attach the last minidump for your review.

Thanks for your help

Debug is here:

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: fffff680000f521d, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffffa6003345ba2, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e8a080
fffff680000f521d
CURRENT_IRQL: 2
FAULTING_IP:
usbuhci!UhciProcessDoneAsyncTd+66
fffffa60`03345ba2 f6460401 test byte ptr [rsi+4],1
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffffa6001b1b910 -- (.trap 0xfffffa6001b1b910)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa6001b1bb08 rbx=0000000000000000 rcx=fffffa8009794880
rdx=fffffa6004267100 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa6003345ba2 rsp=fffffa6001b1baa0 rbp=fffffa8009794880
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffffa6004267000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
usbuhci!UhciProcessDoneAsyncTd+0x66:
fffffa60`03345ba2 f6460401 test byte ptr [rsi+4],1 ds:00000000`00000004=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80001cb1fee to fffff80001cb2250
STACK_TEXT:
fffffa60`01b1b7c8 fffff800`01cb1fee : 00000000`0000000a fffff680`000f521d 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffa60`01b1b7d0 fffff800`01cb0ecb : 00000000`00000000 00000000`00000000 fffffa80`0d18e400 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`01b1b910 fffffa60`03345ba2 : fffffa60`005efcc0 fffffa60`03384ff5 fffffa60`020d4d10 fffffa80`0671eb40 : nt!KiPageFault+0x20b
fffffa60`01b1baa0 fffffa60`03346420 : fffffa80`097158f0 00000000`0000eb6e 00000000`00000000 fffffa80`0970a938 : usbuhci!UhciProcessDoneAsyncTd+0x66
fffffa60`01b1bb10 fffffa60`03343197 : 00000000`00000002 fffffa80`09715620 00000000`00000000 fffffa80`097931a0 : usbuhci!UhciPollAsyncEndpoint+0x5e0
fffffa60`01b1bb70 fffffa60`0334eeaa : fffffa80`0671eb48 fffffa60`03368edc 00000000`00000000 fffffa60`0334e6d6 : usbuhci!UhciPollEndpoint+0x1b
fffffa60`01b1bba0 fffffa60`03354e17 : 00000000`00000040 00000000`00000004 fffffa80`09715620 fffffa80`09793bf0 : USBPORT!MPf_PollEndpoint+0x92
fffffa60`01b1bbd0 fffffa60`033644ff : 00000000`38496573 fffffa80`097931a0 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0xa53
fffffa60`01b1bc40 fffffa60`0335018b : fffffa80`32696368 fffffa80`09793bf0 fffffa60`30745378 fffffa80`097931a0 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x267
fffffa60`01b1bcc0 fffff800`01cbb8d7 : fffffa80`09793c08 00000000`34776478 00000000`00000000 fffffa60`005ef580 : USBPORT!USBPORT_Xdpc_Worker+0x26f
fffffa60`01b1bd10 fffff800`01cbca72 : fffffa60`0334ff1c fffffa60`005ec180 00000000`00000000 fffffa60`005f5d40 : nt!KiRetireDpcList+0x117
fffffa60`01b1bd80 fffff800`01e8e5c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
fffffa60`01b1bdb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4

STACK_COMMAND: kb
FOLLOWUP_IP:
usbuhci!UhciProcessDoneAsyncTd+66
fffffa60`03345ba2 f6460401 test byte ptr [rsi+4],1
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: usbuhci!UhciProcessDoneAsyncTd+66
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbuhci
IMAGE_NAME: usbuhci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 494b269f
FAILURE_BUCKET_ID: X64_0xD1_usbuhci!UhciProcessDoneAsyncTd+66
BUCKET_ID: X64_0xD1_usbuhci!UhciProcessDoneAsyncTd+66
Followup: MachineOwner

The system was trying to read something from a USB drive. What was plugged in? Try updating the firmware in your DVD drive. If it still occurs it might be SP2. Try a system restore as a last resort. The Bugcheck strike means that the IRQL that was interrupted.

oursdur said:

Hello Guys

I was using a Dell Latitude E6500 but I put it aside for the past months due to too many blue screens. All Dell could advise was to reinstall everything....

But now that I found the forum I hope one of the experts can help. The laptop is running with Vista Ultimate 64bit SP2.

Blue screens appear randomly but seem to be more frequent when using USB ports.

I attach the last minidump for your review.

Thanks for your help

Click to expand...

Oursdur

Hi and welcome. this dump was caused by usbuchi.sys which is part of the Microsoft USB miniport driver. I noticed 2 things first you have SP1 not two that in itself would help, and two the date on this driver is somewhat old. I would suggest Re-installing the usb driver and upgrading to sp2. If you have a backup that you can restore from that would also be a work around. Another workaround is to run the system file checker (SFC /scannow) to see if ther are any errors

Good luck

Ken


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


Loading Dump File [C:\Users\K\Desktop\Mini052709-03.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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.22318.amd64fre.vistasp1_ldr.081125-1506
Machine Name:
Kernel base = 0xfffff800`01c61000 PsLoadedModuleList = 0xfffff800`01e26db0
Debug session time: Wed May 27 11:25:28.694 2009 (GMT-4)
System Uptime: 0 days 0:40:20.557
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff680000f521d, 2, 0, fffffa6003345ba2}

Probably caused by : usbuhci.sys ( usbuhci!UhciProcessDoneAsyncTd+66 )

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: fffff680000f521d, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffffa6003345ba2, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e8a080
fffff680000f521d

CURRENT_IRQL: 2

FAULTING_IP:
usbuhci!UhciProcessDoneAsyncTd+66
fffffa60`03345ba2 f6460401 test byte ptr [rsi+4],1

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffffa6001b1b910 -- (.trap 0xfffffa6001b1b910)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa6001b1bb08 rbx=0000000000000000 rcx=fffffa8009794880
rdx=fffffa6004267100 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa6003345ba2 rsp=fffffa6001b1baa0 rbp=fffffa8009794880
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffffa6004267000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
usbuhci!UhciProcessDoneAsyncTd+0x66:
fffffa60`03345ba2 f6460401 test byte ptr [rsi+4],1 ds:00000000`00000004=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001cb1fee to fffff80001cb2250

STACK_TEXT:
fffffa60`01b1b7c8 fffff800`01cb1fee : 00000000`0000000a fffff680`000f521d 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffa60`01b1b7d0 fffff800`01cb0ecb : 00000000`00000000 00000000`00000000 fffffa80`0d18e400 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`01b1b910 fffffa60`03345ba2 : fffffa60`005efcc0 fffffa60`03384ff5 fffffa60`020d4d10 fffffa80`0671eb40 : nt!KiPageFault+0x20b
fffffa60`01b1baa0 fffffa60`03346420 : fffffa80`097158f0 00000000`0000eb6e 00000000`00000000 fffffa80`0970a938 : usbuhci!UhciProcessDoneAsyncTd+0x66
fffffa60`01b1bb10 fffffa60`03343197 : 00000000`00000002 fffffa80`09715620 00000000`00000000 fffffa80`097931a0 : usbuhci!UhciPollAsyncEndpoint+0x5e0
fffffa60`01b1bb70 fffffa60`0334eeaa : fffffa80`0671eb48 fffffa60`03368edc 00000000`00000000 fffffa60`0334e6d6 : usbuhci!UhciPollEndpoint+0x1b
fffffa60`01b1bba0 fffffa60`03354e17 : 00000000`00000040 00000000`00000004 fffffa80`09715620 fffffa80`09793bf0 : USBPORT!MPf_PollEndpoint+0x92
fffffa60`01b1bbd0 fffffa60`033644ff : 00000000`38496573 fffffa80`097931a0 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0xa53
fffffa60`01b1bc40 fffffa60`0335018b : fffffa80`32696368 fffffa80`09793bf0 fffffa60`30745378 fffffa80`097931a0 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x267
fffffa60`01b1bcc0 fffff800`01cbb8d7 : fffffa80`09793c08 00000000`34776478 00000000`00000000 fffffa60`005ef580 : USBPORT!USBPORT_Xdpc_Worker+0x26f
fffffa60`01b1bd10 fffff800`01cbca72 : fffffa60`0334ff1c fffffa60`005ec180 00000000`00000000 fffffa60`005f5d40 : nt!KiRetireDpcList+0x117
fffffa60`01b1bd80 fffff800`01e8e5c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
fffffa60`01b1bdb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4


STACK_COMMAND: kb

FOLLOWUP_IP:
usbuhci!UhciProcessDoneAsyncTd+66
fffffa60`03345ba2 f6460401 test byte ptr [rsi+4],1

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: usbuhci!UhciProcessDoneAsyncTd+66

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbuhci

IMAGE_NAME: usbuhci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 494b269f

FAILURE_BUCKET_ID: X64_0xD1_usbuhci!UhciProcessDoneAsyncTd+66

BUCKET_ID: X64_0xD1_usbuhci!UhciProcessDoneAsyncTd+66

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

I just started getting this message, too. Got my computer about a month ago. Out of nowhere it starts doing this on boot-up and I can't even run it in safe mode..

It then also added to the blue screen:

"A driver has overrun a stack-based buffer. This overrun could potentially allow a malicious user to gain control of this machine."

And Technical Information:

"STOP: 0x000000F7 (0x86212884, 0xEC089CAA, 0x13676355, 0x00000000)"

I think this is it, I'm reading it off of a very small picture on my phone that I took of it. Anyways, any help with this would be lovely because I'm off to college in a few days and I'm bringing this thing..

bountyhunterx said:

I just started getting this message, too. Got my computer about a month ago. Out of nowhere it starts doing this on boot-up and I can't even run it in safe mode..

It then also added to the blue screen:

"A driver has overrun a stack-based buffer. This overrun could potentially allow a malicious user to gain control of this machine."

And Technical Information:
"STOP: 0x000000F7 (0x86212884, 0xEC089CAA, 0x13676355, 0x00000000)"

I think this is it, I'm reading it off of a very small picture on my phone that I took of it. Anyways, any help with this would be lovely because I'm off to college in a few days and I'm bringing this thing..

Click to expand...

Upload the .dmp files or take a look at the guide in my sig. The .dmp files should be in C:\Windows or C:\Minidump. Update all your drivers for now and possible the BIOS.

How do I do that though? I can't start my computer without getting this error. Safe mode doesn't work, either. :/

Try safe mode with command prompt - type sfc /scannow.

Grr, still just blue screening and looping back to restart..

bountyhunterx said:

Grr, still just blue screening and looping back to restart..

Click to expand...

Try hitting F8 until advanced system settings appear

I mean after I started it in Safe Mode with command prompt it just blue screened and looped back, right after loading windows files.

Safe mode with command prompt then run the command.

Can't, when I try to start my computer in ANY mode the blue screen appears and the computer restarts.

bountyhunterx said:

Can't, when I try to start my computer in ANY mode the blue screen appears and the computer restarts.

Click to expand...

You'll need a new install, after a fresh format. Back up any files by donwloading an ubuntu live cd and copying anything from the partition to a backup hard drive or dvd drive if you haven't already.

Wait, so is it possible to back things up if I can't get my computer to start up?

bountyhunterx said:

Wait, so is it possible to back things up if I can't get my computer to start up?

Click to expand...

Yes. Ubuntu can read NTFS partitions, so your hard drive should be listed under Places in the live cd as a xxxGB partitiion if the motherboard detects your hard drive. Navigate in the partition to C:\Users\xxx where the xxx's are your username and copy the documents, etc. You can also use a rescue cd if that doesn't work, but try the first method.

So how exactly do I do this? Sorry, I've never done any of this before and I'm not very familiar with Ubuntu.

Get the desktop version from here:

Download Ubuntu | Ubuntu

then burn it to cd with Imgburn:

www.imgburn.com/

Make sure you burn the .iso with the right option, then reboot with the cd in your drive. The Ubuntu live cd should load, otherwise go into BIOS and change the boot options. Then in the Places menu, look for your hard drive, and follow the steps above.


If that doesn't work, then we'll see what to do next.

Thanks a lot, you've been incredibly helpful. I'll try this tomorrow and let you know how it went!

Frostmourne said:

The system was trying to read something from a USB drive. What was plugged in? Try updating the firmware in your DVD drive. If it still occurs it might be SP2. Try a system restore as a last resort. The Bugcheck strike means that the IRQL that was interrupted.

Click to expand...

------------------------------

Hello Frostmourne

And thanks for the feedback. As you can see from the date of the minidump file, it has been quite a while so I can't recall what was the actual event triggering the blue screen. I can only say that blue screen were happening more when
- usb devices were connected (any type)
- laptop was on docking station

Now regarding your solution, can you please explain () how to upgrade the firmware in my DVD drive?

I also checked the restore points available but they are all past the blue screen date,so I wonder if it would change anything?

Thanks

zigzag3143 said:

Oursdur

Hi and welcome. this dump was caused by usbuchi.sys which is part of the Microsoft USB miniport driver. I noticed 2 things first you have SP1 not two that in itself would help, and two the date on this driver is somewhat old. I would suggest Re-installing the usb driver and upgrading to sp2. If you have a backup that you can restore from that would also be a work around. Another workaround is to run the system file checker (SFC /scannow) to see if ther are any errors

Good luck

Ken
---------

Click to expand...

Hi Ken

And thanks for the welcome, you have no idea how hard it is difficult to find someone to debug a blue screen when you are sitting in the middle of Africa...

And also apologies for the confusion caused by system specs as shown in the footer of my post but they refer to my current system (also a Dell Latitude E6500 but with Vista Business SP1). The laptop I refer to in this post is a Latitude E6500 but with Ultimate SP2 (at least this what Control Panel says).

Now regarding your suggested solution to update the USB driver, how do I do that? If I go to the device manager there at least a dozen of items listed under "USB controllers". Which one has to be changed?

Thanks

Oursdur