Solved Win 8.1 USB 3.0 driver_irql_not_less_or_equal wdf01000.sys

toozerosickz · Jun 23, 2015

I just received a Dell XPS 13 9343 and am having problems with my usb 3.0 hard drive. It keeps crashing when transferring files. I have tried clean installs of 8.1 and even Windows 10.

If I hook it up to a 2.0 hub it works just fine, but slower speeds.

The error I get is driver_irql_not_less_or_equal wdf01000.sys.

Code:

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




Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available




************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff800`51273000 PsLoadedModuleList = 0xfffff800`5154c850
Debug session time: Tue Jun 23 18:10:53.908 2015 (UTC - 7:00)
System Uptime: 0 days 0:05:39.691
Loading Kernel Symbols
...............................................................
................................................................
.....Page 152490 not present in the dump file. Type ".hh dbgerr004" for details
.Page 152434 not present in the dump file. Type ".hh dbgerr004" for details
..........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7ffdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck D1, {b8, 2, 0, fffff8012c6c370a}


Page 14e567 not present in the dump file. Type ".hh dbgerr004" for details
Page 115a01 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : USBXHCI.SYS ( USBXHCI!Bulk_Transfer_CompleteCancelable+15a )


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


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


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




READ_ADDRESS: unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 00000000000000b8 


CURRENT_IRQL:  2


FAULTING_IP: 
Wdf01000!FxRequest::CompleteInternal+4a
fffff801`2c6c370a 488b91b8000000  mov     rdx,qword ptr [rcx+0B8h]


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


BUGCHECK_STR:  AV


PROCESS_NAME:  uTorrent.exe


ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre


DPC_STACK_BASE:  FFFFF80052F54FB0


TRAP_FRAME:  ffffd000a310d570 -- (.trap 0xffffd000a310d570)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
Unable to get program counter
rax=fffff9600042e650 rbx=0000000000000000 rcx=fffff90142b97c38
rdx=00000004000000f0 rsi=0000000000000000 rdi=0000000000000000
rip=00000000000000cd rsp=ffffd000a310d8e0 rbp=000001c000000000
 r8=0000000100000001  r9=0000000000000000 r10=fffff90144c00260
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz ac po nc
1000:00cd ??              ???
Resetting default scope


EXCEPTION_RECORD:  ffffd000a310d570 -- (.exr 0xffffd000a310d570)
ExceptionAddress: fffff90144c00000
   ExceptionCode: 00000000
  ExceptionFlags: 00000000
NumberParameters: 0


LAST_CONTROL_TRANSFER:  from fffff800513cf7e9 to fffff800513c3ca0


STACK_TEXT:  
fffff800`52f54598 fffff800`513cf7e9 : 00000000`0000000a 00000000`000000b8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`52f545a0 fffff800`513ce03a : 00000000`00000000 ffffe000`0cdf45b0 ffffe000`0cd15200 fffff800`52f54749 : nt!KiBugCheckDispatch+0x69
fffff800`52f546e0 fffff801`2c6c370a : 00000000`ffffffff fffff800`52f54901 ffffe000`0eed0160 fffff801`2e798d4c : nt!KiPageFault+0x23a
fffff800`52f54870 fffff801`2c6d0364 : ffffe000`0cdf4750 ffffe000`00000000 fffff800`52f54b20 fffff800`52f549d1 : Wdf01000!FxRequest::CompleteInternal+0x4a
fffff800`52f54930 fffff801`2e79bf52 : ffffe000`0cdf4750 fffff800`52f50000 00000000`00000004 ffffe000`0cdf45b0 : Wdf01000!imp_WdfRequestComplete+0x8c
fffff800`52f549a0 fffff801`2e79cec8 : ffffe000`0cdf4750 00000000`00000001 ffffe000`0cdf47d0 fffff800`52f54b20 : USBXHCI!Bulk_Transfer_CompleteCancelable+0x15a
fffff800`52f54a00 fffff801`2e78a067 : 00000000`00000780 ffffe000`0cc76990 00000000`00000000 00000000`00000000 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x3a8
fffff800`52f54ab0 fffff801`2c75bc81 : fffff800`51576180 00000000`00000f44 00001fff`f3389858 00000000`00400a02 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0x427
fffff800`52f54bb0 fffff800`51319c00 : fffff800`51578f00 fffff800`52f54e70 ffffe000`0cc767a0 ffffe000`097b0f44 : Wdf01000!FxInterrupt::DpcHandler+0xc1
fffff800`52f54be0 fffff800`51318eb7 : ffffe000`0c63f6e8 00000000`9e0068d7 fffff800`51576180 00000000`00000000 : nt!KiExecuteAllDpcs+0x1b0
fffff800`52f54d30 fffff800`513c6dd5 : 00000000`00000000 fffff800`51576180 ffffd000`9e586280 00000000`00000000 : nt!KiRetireDpcList+0xd7
fffff800`52f54fb0 fffff800`513c6bd9 : ffffe000`102d5000 00000000`00000000 fffff901`41a6eb80 fffff901`40165020 : nt!KxRetireDpcList+0x5
ffffd000`a310cc30 fffff800`513c8e45 : fffffa80`065e9800 fffff800`513c52b3 00000000`00000000 00000008`00000000 : nt!KiDispatchInterruptContinue
ffffd000`a310cc60 fffff800`513c52b3 : 00000000`00000000 00000008`00000000 fffff901`42443000 00000000`00000000 : nt!KiDpcInterruptBypass+0x25
ffffd000`a310cc70 fffff960`00218b4e : ffffd000`a310d570 fffff960`0010f574 ffffd000`a310d570 ffffd000`a310d5b0 : nt!KiInterruptDispatch+0x173
ffffd000`a310ce00 fffff960`0010f574 : ffffd000`a310d570 ffffd000`a310d5b0 00000000`42442de0 00000000`00000000 : win32k!BltLnkReadPat+0x43
ffffd000`a310ce10 fffff960`0010eaec : 00000000`00000000 fffff800`512cb358 ffffd000`a310d6c4 00000000`00000000 : win32k!BltLnkRect+0x734
ffffd000`a310d4b0 fffff960`0010cd22 : 00000000`00000000 00000000`002118a4 00000000`00000021 fffff800`51517973 : win32k!BltLnk+0x434
ffffd000`a310d870 fffff960`0007341f : fffff901`00000000 fffff960`00ffffff ffffd000`a310da68 fffff901`40000cf0 : win32k!EngBitBlt+0x2a2
ffffd000`a310d9e0 fffff960`00072a8c : 00000000`0000f0f0 fffff901`42b97c38 00000000`01900010 fffff901`0000f0f0 : win32k!GrePatBltLockedDC+0x35f
ffffd000`a310dac0 fffff960`00162db6 : 00000000`00f00021 ffffd000`a310dcf0 00000000`4e010fc9 00000000`00000000 : win32k!GrePolyPatBltInternal+0x29c
ffffd000`a310dc50 fffff960`00162d2b : fffff901`406401c0 fffff901`406401c0 00000000`07100abb fffff960`0019b694 : win32k!GrePolyPatBlt+0x76
ffffd000`a310dcc0 fffff960`0019b5e1 : fffff901`406401c0 fffff901`406401c0 00000000`00000004 00000000`4e010fc9 : win32k!FillRect+0x53
ffffd000`a310dd20 fffff960`0019b526 : 00000000`00000000 fffff901`406401c0 00000000`00000004 00000000`4e010fc9 : win32k!xxxPaintRect+0x91
ffffd000`a310dd50 fffff960`0019afea : 00000000`0185000f 00000000`00000000 00000000`000102d4 fffff901`42b97620 : win32k!xxxFillWindow+0x6a
ffffd000`a310ddd0 fffff800`513cf4b3 : 00000000`4e010fc9 ffffd000`a310dec0 fffff960`0019af24 00000000`00000000 : win32k!NtUserFillWindow+0xc6
ffffd000`a310de40 00000000`771f2352 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008d5f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771f2352




STACK_COMMAND:  kb


FOLLOWUP_IP: 
USBXHCI!Bulk_Transfer_CompleteCancelable+15a
fffff801`2e79bf52 488d4d58        lea     rcx,[rbp+58h]


SYMBOL_STACK_INDEX:  5


SYMBOL_NAME:  USBXHCI!Bulk_Transfer_CompleteCancelable+15a


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: USBXHCI


IMAGE_NAME:  USBXHCI.SYS


DEBUG_FLR_IMAGE_TIMESTAMP:  5527309b


IMAGE_VERSION:  6.3.9600.17795


BUCKET_ID_FUNC_OFFSET:  15a


FAILURE_BUCKET_ID:  AV_USBXHCI!Bulk_Transfer_CompleteCancelable


BUCKET_ID:  AV_USBXHCI!Bulk_Transfer_CompleteCancelable


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:av_usbxhci!bulk_transfer_completecancelable


FAILURE_ID_HASH:  {4993a1b5-1810-3a7e-3a43-18068d25fc19}


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

broe23 · Jun 24, 2015

Download Who Crashed from majorgeeks.com and it will tell you what the issue is.

toozerosickz · Jun 24, 2015

broe23 said:
Download Who Crashed from majorgeeks.com and it will tell you what the issue is.

Code:

[FONT=Segoe UI, Arial][SIZE=4][B]Crash Dump Analysis[/B][HR][/HR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]Crash dump directory: C:\Windows\Minidump[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]Crash dumps are enabled on your computer.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Thu 6/25/2015 12:27:24 AM GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\062415-9750-01.dmp
This was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=wdf01000.sys"]wdf01000.sys[/URL][/COLOR][/SIZE][/FONT] (0xFFFFF80088A3870A) 
Bugcheck code: 0xD1 (0xB8, 0x2, 0x0, 0xFFFFF80088A3870A)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_IRQL_NOT_LESS_OR_EQUAL"]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\drivers\wdf01000.sys
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Thu 6/25/2015 12:27:24 AM GMT your computer crashed[/B]
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=wdf01000.sys"]wdf01000.sys[/URL][/COLOR][/SIZE][/FONT] (Wdf01000+0x170A) 
Bugcheck code: 0xD1 (0xB8, 0x2, 0x0, 0xFFFFF80088A3870A)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_IRQL_NOT_LESS_OR_EQUAL"]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\drivers\wdf01000.sys
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Wed 6/24/2015 10:14:32 PM GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\062415-10765-01.dmp
This was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=wdf01000.sys"]wdf01000.sys[/URL][/COLOR][/SIZE][/FONT] (0xFFFFF801580D670A) 
Bugcheck code: 0xD1 (0xB8, 0x2, 0x0, 0xFFFFF801580D670A)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_IRQL_NOT_LESS_OR_EQUAL"]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\drivers\wdf01000.sys
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Wed 6/24/2015 1:10:53 AM GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\062315-5953-01.dmp
This was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=wdf01000.sys"]wdf01000.sys[/URL][/COLOR][/SIZE][/FONT] (0xFFFFF8012C6C370A) 
Bugcheck code: 0xD1 (0xB8, 0x2, 0x0, 0xFFFFF8012C6C370A)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_IRQL_NOT_LESS_OR_EQUAL"]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\drivers\wdf01000.sys
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][/COLOR][/SIZE][/FONT]
[FONT=Segoe UI, Arial][SIZE=4][B][HR][/HR]Conclusion[/B][HR][/HR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. 


Read the topic [URL="http://www.resplendence.com/whocrashed_troubleshooting"]general suggestions for troubleshooting system crashes[/URL] for more information. 

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. 

[/COLOR][/SIZE][/FONT]

derekimo · Jun 24, 2015

Without this info,

http://www.eightforums.com/bsod-cra...e-screen-death-bsod-posting-instructions.html

It will be hard to give detailed info.

But from your first post Windbg is flagging your USB3 driver,

Code:

Probably caused by : USBXHCI.SYS ( USBXHCI!Bulk_Transfer_CompleteCancelable+15a )Probably caused by : USBXHCI.SYS ( USBXHCI!Bulk_Transfer_CompleteCancelable+15a )

The results of Who crashed are generic, and in your case pointing to Microsoft drivers (As it often will) and incorrectly at that.

From the bugcheck it is a driver, you mention a couple of installs so have you installed the chipset drivers from the Dell support page?

Product Support | Dell US

toozerosickz · Jun 24, 2015

derekimo said:
Without this info,

http://www.eightforums.com/bsod-cra...e-screen-death-bsod-posting-instructions.html

It will be hard to give detailed info.

But from your first post Windbg is flagging your USB3 driver,

Code:

Probably caused by : USBXHCI.SYS ( USBXHCI!Bulk_Transfer_CompleteCancelable+15a )Probably caused by : USBXHCI.SYS ( USBXHCI!Bulk_Transfer_CompleteCancelable+15a )

The results of Who crashed are generic, and in your case pointing to Microsoft drivers (As it often will) and incorrectly at that.

From the bugcheck it is a driver, you mention a couple of installs so have you installed the chipset drivers from the Dell support page?

Product Support | Dell US

Yes. I tried installing each and every Dell driver after multiple BSODs. I also read multiple sources regarding Windows 8 and the USB 3 drivers. Some sites suggested disabling driver signatures and installing the Win 7 USB drivers, but I couldn't get that to work.

Here are my BSOD files https://onedrive.live.com/redir?resid=B513E857B85E6879!494&authkey=!APDDhBjTq5Ow8CU&ithint=file,zip

derekimo · Jun 24, 2015

I don't have any problems with my USB3 drivers, turning off driver signatures isn't a good idea anyway.

Are you missing any drivers in device manager? Anything with a :warn:

What's interesting is the dump file shows you are only using the USB3 driver from Microsoft's installer,

Code:

Image path: \SystemRoot\System32\drivers\USBXHCI.SYS
    Image name: USBXHCI.SYS
    Timestamp:        Thu Apr 09 19:08:27 2015 (5527309B)
    CheckSum:         00052B6E
    ImageSize:        00055000
    File version:     6.3.9600.17795
    Product version:  6.3.9600.17795
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     usbxhci.sys
    OriginalFilename: usbxhci.sys
    ProductVersion:   6.3.9600.17795
    FileVersion:      6.3.9600.17795 (winblue_r10.150409-1500)
    FileDescription:  USB XHCI Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Instead of Intel's driver which it should be using,

Code:

Intel(R) USB 3.0 eXtensible Host Controller - 0100 (Microsoft)	PCI\VEN_8086&DEV_[B][COLOR="#FF0000"]9CB1[/COLOR][/B]&SUBSYS_06651028&REV_03\3&11583659&0&A0

Looking up that device ID from your MSINFO32.nfo file points to an HP download.

Two of the three dumps also show you have driver verifier enabled,

Code:

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

Can you turn that off,

Driver Verifier - Enable and Disable - Windows 7 Help Forums

I think something else is causing that driver to fail since it's Microsoft's driver, I'm not sure what though.

What AV are you using?

toozerosickz · Jun 25, 2015

derekimo said:
I don't have any problems with my USB3 drivers, turning off driver signatures isn't a good idea anyway.

Are you missing any drivers in device manager? Anything with a

What's interesting is the dump file shows you are only using the USB3 driver from Microsoft's installer,

Code:

Image path: \SystemRoot\System32\drivers\USBXHCI.SYS Image name: USBXHCI.SYS Timestamp: Thu Apr 09 19:08:27 2015 (5527309B) CheckSum: 00052B6E ImageSize: 00055000 File version: 6.3.9600.17795 Product version: 6.3.9600.17795 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.7 Driver File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: usbxhci.sys OriginalFilename: usbxhci.sys ProductVersion: 6.3.9600.17795 FileVersion: 6.3.9600.17795 (winblue_r10.150409-1500) FileDescription: USB XHCI Driver LegalCopyright: © Microsoft Corporation. All rights reserved.

Instead of Intel's driver which it should be using,

Code:

Intel(R) USB 3.0 eXtensible Host Controller - 0100 (Microsoft) PCI\VEN_8086&DEV_[B][COLOR=#FF0000]9CB1[/COLOR][/B]&SUBSYS_06651028&REV_03\3&11583659&0&A0

Looking up that device ID from your MSINFO32.nfo file points to an HP download.

Two of the three dumps also show you have driver verifier enabled,

Code:

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

Can you turn that off,

Driver Verifier - Enable and Disable - Windows 7 Help Forums

I think something else is causing that driver to fail since it's Microsoft's driver, I'm not sure what though.

What AV are you using?

No missing drivers in device manager.

I turned on driver verifier for troubleshooting steps on the Microsoft community.

The only AV I'm using is Microsoft defender.

toozerosickz · Jun 25, 2015

So I found an extra external enclosure laying around and took the Seagate apart to use the other one. I am no longer getting crashes or errors and I'm able to transfer a 10GB file at 79MB/s average. It seems this computer does not like my Seagate enclosure even though it worked fine in my other laptop.

derekimo · Jun 25, 2015

Interesting, Thanks for posting back with your solution.

Solved Win 8.1 USB 3.0 driver_irql_not_less_or_equal wdf01000.sys

toozerosickz

New Member

My Computer

System One

broe23

Retired from the grind

My Computer

System One

toozerosickz

New Member

My Computer

System One

derekimo

Moderator

My Computer

System One

toozerosickz

New Member

My Computer

System One

derekimo

Moderator

My Computer

System One

toozerosickz

New Member

My Computer

System One

toozerosickz

New Member

My Computer

System One

derekimo

Moderator

My Computer

System One