BSOD 0x000000d1 when opening Cubase or Guitar Rig.

Pikka Bird · 27 Jul 2014

Hey dudes.

My computer recently (today) developed a nasty habit of crashing to BSOD whenever I start up Cubase 5.1 or Guitar Rig 5. The initial splash card will come up, and then bam! It used to work flawlessly with no hangups or crashes at all. The only change to my setup since last time I had both applications fired up is that yesterday I took my computer off the desk and put it on the floor to make room for a set of studio monitors, and I probably didn't use the same USB ports when I plugged everything back in. I tried uninstalling and reinstalling Cubase, but to no avail.

Here's a picture of the actual BSOD, if that's any use at all (I guess everything is in the minilogs anyways, or...?)

This is sort of urgent because the band and I are recording an album and we're pretty much on the home stretch and this is a major road block for the entire project.

koolkat77 · 29 Jul 2014

Welcome to the forum Pikka Bird,

The BSOD was caused by Etron USB 3.0 Extensible Host Controller Driver

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa8c0fdbf090, 2, 0, fffff88007215e34}

*** WARNING: Unable to verify timestamp for EtronXHCI.sys
*** ERROR: Module load completed but symbols could not be loaded for EtronXHCI.sys
Probably caused by : EtronXHCI.sys ( EtronXHCI+4e34 )

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800035000e0
GetUlongFromAddress: unable to read from fffff80003500198
 fffffa8c0fdbf090 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
EtronXHCI+4e34
fffff880`07215e34 418b8c818c000000 mov     ecx,dword ptr [r9+rax*4+8Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF80004820FB0

TRAP_FRAME:  fffff80004820360 -- (.trap 0xfffff80004820360)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000002fffffffd rbx=0000000000000000 rcx=0000000000000004
rdx=0000000000000024 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007215e34 rsp=fffff800048204f0 rbp=0000000000000c00
 r8=0000000000000000  r9=fffffa800fdbf010 r10=0000000000000004
r11=fffffa8009b3a2a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
EtronXHCI+0x4e34:
fffff880`07215e34 418b8c818c000000 mov     ecx,dword ptr [r9+rax*4+8Ch] ds:fffffa8c`0fdbf090=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032c9469 to fffff800032c9f00

STACK_TEXT:  
fffff800`04820218 fffff800`032c9469 : 00000000`0000000a fffffa8c`0fdbf090 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`04820220 fffff800`032c80e0 : 00000043`02020000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`04820360 fffff880`07215e34 : fffffa80`08673bb0 00000000`0000001e fffffa80`08ec1930 fffffa80`077cc220 : nt!KiPageFault+0x260
fffff800`048204f0 fffffa80`08673bb0 : 00000000`0000001e fffffa80`08ec1930 fffffa80`077cc220 00000000`0000001e : EtronXHCI+0x4e34
fffff800`048204f8 00000000`0000001e : fffffa80`08ec1930 fffffa80`077cc220 00000000`0000001e fffffa80`08ec1930 : 0xfffffa80`08673bb0
fffff800`04820500 fffffa80`08ec1930 : fffffa80`077cc220 00000000`0000001e fffffa80`08ec1930 00000000`00000000 : 0x1e
fffff800`04820508 fffffa80`077cc220 : 00000000`0000001e fffffa80`08ec1930 00000000`00000000 fffff880`072194a6 : 0xfffffa80`08ec1930
fffff800`04820510 00000000`0000001e : fffffa80`08ec1930 00000000`00000000 fffff880`072194a6 00000000`00000002 : 0xfffffa80`077cc220
fffff800`04820518 fffffa80`08ec1930 : 00000000`00000000 fffff880`072194a6 00000000`00000002 fffffa80`077cc220 : 0x1e
fffff800`04820520 00000000`00000000 : fffff880`072194a6 00000000`00000002 fffffa80`077cc220 fffffa80`08673a60 : 0xfffffa80`08ec1930


STACK_COMMAND:  kb

FOLLOWUP_IP: 
EtronXHCI+4e34
fffff880`07215e34 418b8c818c000000 mov     ecx,dword ptr [r9+rax*4+8Ch]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  EtronXHCI+4e34

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: EtronXHCI

IMAGE_NAME:  EtronXHCI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e2de090

FAILURE_BUCKET_ID:  X64_0xD1_EtronXHCI+4e34

BUCKET_ID:  X64_0xD1_EtronXHCI+4e34

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

0: kd> lmvm EtronXHCI
start             end                 module name
fffff880`07211000 fffff880`07224500   EtronXHCI T (no symbols)           
    Loaded symbol image file: EtronXHCI.sys
    Image path: EtronXHCI.sys
    Image name: EtronXHCI.sys
    Timestamp:        Tue Jul 26 03:30:56 2011 (4E2DE090)
    CheckSum:         00020826
    ImageSize:        00013500
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Try updating it from here: Etron Technology, Inc.

Also install Service Pack One: Learn how to install Windows 7 Service Pack 1 (SP1)

Please uninstall Daemon Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7.

Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

As an alternative, many people recommend the use of Total Mounter or Magic ISO

The below software can contribute to BSOD's. Remove them with Revo Uninstaller.

Code:

Start Menu\Programs\GIGABYTE	Public:Start Menu\Programs\GIGABYTE	Public
Start Menu\Programs\GIGABYTE\AutoGreen	Public:Start Menu\Programs\GIGABYTE\AutoGreen	Public
Start Menu\Programs\GIGABYTE\EnergySaver2	Public:Start Menu\Programs\GIGABYTE\EnergySaver2	Public
Start Menu\Programs\GIGABYTE\ET6	Public:Start Menu\Programs\GIGABYTE\ET6	Public
Start Menu\Programs\GIGABYTE\Smart 6	Public:Start Menu\Programs\GIGABYTE\Smart 6	Public

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-

Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Pikka Bird · 29 Jul 2014

Thanks a lot, Koolkat. So it was a problem with the port I'd stuck my audio interface into after the move? Who'd a thunk it, eh? I did update the driver, and it didn't BSOD, but still wasn't performing well, so I moved it to another USB port (a good old two variant) and it's all fine. That really irks me, I thought USB 3 was fully backwards compatible, but maybe the drivers I'm finding just aren't too great.

Anyways, smooth sailing from now on. Thanks again.