DRIVER_IRQL_NOT_LESS_OR_EQUAL

Post » Mon Mar 14, 2011 4:28 pm

So, since the beginning of today, for WHATEVER REASON (I didn't add or remove ANY HARDWARE, nor install ANY updates or drivers), my computer has been getting bluescreens during video games.

Using the WinDbg tool, I have deduced that it is some driver related issue. I'll post the last two error reports here:
Spoiler

********************************************************************************                                                                             **                        Bugcheck anolysis                                    **                                                                             ********************************************************************************Use !anolyze -v to get detailed debugging information.BugCheck B8, {0, 0, 0, 0}Unable to load image HIDCLASS.SYS, Win32 error 0n2*** WARNING: Unable to verify timestamp for HIDCLASS.SYSUnable to load image Wdf01000.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for Wdf01000.sys*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys*** WARNING: Unable to verify timestamp for LEqdUsb.Sys*** ERROR: Module load completed but symbols could not be loaded for LEqdUsb.Sys*** WARNING: Unable to verify timestamp for USBPORT.SYSUnable to load image sptd.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for sptd.sys*** ERROR: Module load completed but symbols could not be loaded for sptd.sysProbably caused by : HIDCLASS.SYS ( HIDCLASS!HidpSubmitInterruptRead+68 )Followup: MachineOwner---------1: kd> !anolyze -v********************************************************************************                                                                             **                        Bugcheck anolysis                                    **                                                                             ********************************************************************************ATTEMPTED_SWITCH_FROM_DPC (b8)A wait operation, attach process, or yield was attempted from a DPC routine.This is an illegal operation and the stack track will lead to the offendingcode and original DPC routine.Arguments:Arg1: 00000000, Original thread which is the cause of the failureArg2: 00000000, New threadArg3: 00000000, Stack address of the original threadArg4: 00000000Debugging Details:------------------CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  DRIVER_FAULTBUGCHECK_STR:  0xB8PROCESS_NAME:  csrss.exeLAST_CONTROL_TRANSFER:  from 80545c5b to 804f9f1eSTACK_TEXT:  b84dbba8 80545c5b 000000b8 ffffffff 00200246 nt!_woutput+0x3efb84dbbd8 b7254268 899f90a4 899b6008 899b6008 nt!NtTraceEvent+0x140b84dbbf0 b72540ec 89a1c62c 899f9090 b84dbc3b HIDCLASS!HidpSubmitInterruptRead+0x68b84dbc28 804f16c0 00000000 899b6008 00a1c62c HIDCLASS!HidpInterruptReadComplete+0x1d2b84dbc58 b39a5e93 898ff118 b84dbc90 b397027d nt!KiDeliverApc+0xccWARNING: Stack unwind information not available. Following frames may be wrong.b84dbc64 b397027d 00000000 b39ab148 898ff118 Wdf01000+0x63e93b84dbc90 b3972211 00000000 00000000 8a0dbaf8 Wdf01000+0x2e27db84dbcac b3972235 00000000 00000000 b84dbcd8 Wdf01000+0x30211b84dbcbc b395b824 00000000 00000008 00000008 Wdf01000+0x30235b84dbcd8 b82d95cf 898ff118 76700ee0 00000000 Wdf01000+0x19824b84dbd04 b82d9c8d 76700ee0 8a12c2aa 00000000 LEqdUsb+0x15cfb84dbd5c b3956bd5 761e1e40 75ed3d90 0000000f LEqdUsb+0x1c8db84dbd8c b3977bbc 76231e18 761e1e40 89dfb39c Wdf01000+0x14bd5b84dbdb4 b394f7dd 899ce453 89e1e1b8 00000000 Wdf01000+0x35bbcb84dbdd0 b394f8bf 01dce1e0 8905f378 b84dbdfc Wdf01000+0xd7ddb84dbde0 804f081d 00000000 899ce350 89dce1e0 Wdf01000+0xd8bfb84dbdfc 804f16c0 00000000 899ce350 8905f378 nt!MmCreateSection+0x65fb84dbe2c b68a20d5 899ce350 88fd1c08 8a0af028 nt!KiDeliverApc+0xccb84dbe94 b68a2d47 89dfb3e4 00000000 8a0af7d8 USBPORT!USBPORT_CompleteTransfer+0x373b84dbec4 b68a3944 026e6f44 8a0af0e0 8a0af0e0 USBPORT!USBPORT_DoneTransfer+0x137b84dbefc b68a513a 8a0af028 80546acc 8a0af230 USBPORT!USBPORT_FlushDoneTransferList+0x16cb84dbf28 b68b324b 8a0af028 80546acc 8a0af028 USBPORT!USBPORT_DpcWorker+0x224b84dbf64 b68b33c2 8a0af028 00000001 8a0e3310 USBPORT!USBPORT_IsrDpcWorker+0x38fb84dbf80 b7eb7ba0 8a0af64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166b84dbfbc 8a0e3db2 8a0e3310 b68b325c b84dbfd0 sptd+0x11ba0b84dbfc0 8a0e3310 b68b325c b84dbfd0 80545e7f 0x8a0e3db2b84dbfc4 b68b325b b84dbfd0 80545e7f 8a0af64c 0x8a0e3310b84dbfc8 b84dbfd0 80545e7f 8a0af64c 8a0af028 USBPORT!USBPORT_IsrDpcWorker+0x39fb84dbfcc 80545e7f 8a0af64c 8a0af028 00000000 0xb84dbfd0b84dbfd0 8a0af64c 8a0af028 00000000 00000000 nt!ExSetResourceOwnerPointer+0x7cb84dbfd4 8a0af028 00000000 00000000 002e0042 0x8a0af64cb84dbfd8 00000000 00000000 002e0042 004c0044 0x8a0af028STACK_COMMAND:  kbFOLLOWUP_IP: HIDCLASS!HidpSubmitInterruptRead+68b7254268 ??              ???SYMBOL_STACK_INDEX:  2SYMBOL_NAME:  HIDCLASS!HidpSubmitInterruptRead+68FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: HIDCLASSIMAGE_NAME:  HIDCLASS.SYSDEBUG_FLR_IMAGE_TIMESTAMP:  480254c5FAILURE_BUCKET_ID:  0xB8_HIDCLASS!HidpSubmitInterruptRead+68BUCKET_ID:  0xB8_HIDCLASS!HidpSubmitInterruptRead+68Followup: MachineOwner---------


Spoiler

********************************************************************************                                                                             **                        Bugcheck anolysis                                    **                                                                             ********************************************************************************Use !anolyze -v to get detailed debugging information.BugCheck B8, {0, 0, 0, 0}Unable to load image USBPORT.SYS, Win32 error 0n2*** WARNING: Unable to verify timestamp for USBPORT.SYS*** WARNING: Unable to verify timestamp for usbhub.sys*** WARNING: Unable to verify timestamp for usbccgp.sysProbably caused by : USBPORT.SYS ( USBPORT!USBPORT_FlushPendingList+5b1 )Followup: MachineOwner---------1: kd> !anolyze -v********************************************************************************                                                                             **                        Bugcheck anolysis                                    **                                                                             ********************************************************************************ATTEMPTED_SWITCH_FROM_DPC (b8)A wait operation, attach process, or yield was attempted from a DPC routine.This is an illegal operation and the stack track will lead to the offendingcode and original DPC routine.Arguments:Arg1: 00000000, Original thread which is the cause of the failureArg2: 00000000, New threadArg3: 00000000, Stack address of the original threadArg4: 00000000Debugging Details:------------------CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  DRIVER_FAULTBUGCHECK_STR:  0xB8PROCESS_NAME:  csrss.exeLAST_CONTROL_TRANSFER:  from 80545c5b to 804f9f1eSTACK_TEXT:  b84dbc50 80545c5b 000000b8 ffffffff 00000202 nt!_woutput+0x3efb84dbc78 80546ae0 badb0d00 00000001 89fe6200 nt!NtTraceEvent+0x140b84dbd1c b68454d9 8a0b6028 8909be70 80546acc nt!ExUnregisterCallback+0x5eb84dbd78 b68463c6 0214c008 ffffffff 80546acc USBPORT!USBPORT_FlushPendingList+0x5b1b84dbda8 b684d350 89cdc760 b84dbde0 b684cf14 USBPORT!USBPORT_QueueTransferUrb+0x248b84dbdb4 b684cf14 8a0b6028 8909be70 89d9805c USBPORT!USBPORT_AsyncTransfer+0x30b84dbde0 b6852088 89c8c030 8a0b6028 00000090 USBPORT!USBPORT_ProcessURB+0x3f4b84dbe00 b683b3d2 89c8c030 8909be70 8909be70 USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x7eb84dbe24 804ef19f 8909bf4c 89c8c188 89d9805c USBPORT!USBPORT_Dispatch+0x148b84dbe3c b823c82d 8909be70 89c8c030 8909be70 nt!MiFlushSectionInternal+0x256b84dbe5c b823d0ae 89c8cd50 8909be70 89da57b0 usbhub!USBH_PdoUrbFilter+0xbdb84dbe78 b823a5e4 89d9805c 8909be70 b84dbeb4 usbhub!USBH_PdoDispatch+0x202b84dbe88 804ef19f 89d10c20 8909be70 89de69b8 usbhub!USBH_HubDispatch+0x48b84dbeb4 b83b876b 89dbc7e0 8909be70 8a0b6028 nt!MiFlushSectionInternal+0x256b84dbed8 b83b85d3 89dbc7d8 8909be70 0000000f usbccgp!USBC_InternalDeviceControl+0x3bb84dbf14 804ef19f 89dbc720 8909be70 89de69b8 usbccgp!USBC_Dispatch+0x183b84dbf54 b83b8786 89ffda20 8909be70 89ffda20 nt!MiFlushSectionInternal+0x256b84dbf78 b83b85d3 89ffda18 8909be70 0000000f usbccgp!USBC_InternalDeviceControl+0x56b84dbfb4 804ef19f 89ffd960 8909be70 b83389c0 usbccgp!USBC_Dispatch+0x183b84dbfcc 80545e7f 89e01728 00000000 00000000 nt!MiFlushSectionInternal+0x256b84dbfe8 00000000 00000000 89da57ac 805459eb nt!ExSetResourceOwnerPointer+0x7cSTACK_COMMAND:  kbFOLLOWUP_IP: USBPORT!USBPORT_FlushPendingList+5b1b68454d9 ??              ???SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  USBPORT!USBPORT_FlushPendingList+5b1FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: USBPORTIMAGE_NAME:  USBPORT.SYSDEBUG_FLR_IMAGE_TIMESTAMP:  480254ceFAILURE_BUCKET_ID:  0xB8_USBPORT!USBPORT_FlushPendingList+5b1BUCKET_ID:  0xB8_USBPORT!USBPORT_FlushPendingList+5b1Followup: MachineOwner---------



Now, I JUST now updated my Nvidia drivers, but that didn't seem to fix the issue. I've seen several other reports that kept mentioning USBport.sys and USBhub.sys. Several reported back with a ATTEMPTED_SWITCH_FROM_DPC error.

Can someone please help out? This is driving me crazy.
User avatar
Jack Walker
 
Posts: 3457
Joined: Wed Jun 06, 2007 6:25 pm

Post » Mon Mar 14, 2011 5:07 pm

1) Update your BIOS.
2) Run http://www.memtest.org/.
User avatar
Rowena
 
Posts: 3471
Joined: Sun Nov 05, 2006 11:40 am

Post » Tue Mar 15, 2011 4:40 am

1) Update your BIOS.
2) Run http://www.memtest.org/.

Do I need to do these in order?

Also, which version of memtest should download?
User avatar
Dagan Wilkin
 
Posts: 3352
Joined: Fri Apr 27, 2007 4:20 am

Post » Mon Mar 14, 2011 5:17 pm

Great, I feel as if my computer is collapsing around me. Flashed my BIOS (now POST tells me that my computer failed to boot up correctly, but I can still boot...), updated graphics drivers (now it isn't working correctly and all my games crash or have insane graphical glitches), then attempted to roll back my driver and my computer froze, so now I'm doing a check disk because my C:\ drive is partially corrupt.

Yeah, this is why I have back ups.
User avatar
Julia Schwalbe
 
Posts: 3557
Joined: Wed Apr 11, 2007 3:02 pm

Post » Tue Mar 15, 2011 12:05 am

So now the GPU keeps acting as though it isn't connected (you are not currently using a display attached to nvidia gpu, it tells me). I also can not system restore anymore.

You know, I might just use my back ups.

Edit: Well, seems my graphic's card is shot. Can no longer take any loads, while my old 8600 works ship shape.

Well, off to newegg!

If anyone has an Nvidia graphics card to suggest, I would gladly like the advice.

edit numero dos: Seems it was actually my PCI-E port. Switching the card to the other port worked fine. Whatever, still getting that new card.
User avatar
Julie Ann
 
Posts: 3383
Joined: Thu Aug 23, 2007 5:17 am


Return to Othor Games