Bug Check D1 from USBSTOR.SYS

GoldWave general discussions and community help
Post Reply
lurkusmaximus
Posts: 14
Joined: Wed Jun 21, 2006 4:49 pm

Bug Check D1 from USBSTOR.SYS

Post by lurkusmaximus »

When I rip CDs using Goldwave to a USB CD/DVD drive, I always get a BSOD out of USBSTOR.SYS (Bugcheck D1) when I change disks. This behavior does not happen when I use Music Match JukeBox or Roxio CD-Creator to rip CDs from the same drive. But it always happens when I use Goldwave version 5.14. Anyone else seen this phenomenen?
GoldWave Inc.
Site Admin
Posts: 4375
Joined: Wed Mar 10, 2004 6:43 pm
Location: St. John's, NL
Contact:

Re: Bug Check D1 from USBSTOR.SYS

Post by GoldWave Inc. »

Have you made any changes to your computer recently, such as adding more memory? Have you installed the latest service packs and updates?

Chris
lurkusmaximus
Posts: 14
Joined: Wed Jun 21, 2006 4:49 pm

Bug Check D1 from USBSTOR.SYS

Post by lurkusmaximus »

The change I recently made was the purchase of a Plextor PX-716UF USB DVD writer. The BSODs seem to all be related to disk changes on the USB drive. Goldwave appears to be the most consistent at giving the error. I have occasionally gotten a BSOD out of Plex Tools pro, the software that came with the drive, but it's always in USBSTOR.SYS which is supplied by Microsoft. I do have the memory dump and I could provide a stack backtrace if you would like.
GoldWave Inc.
Site Admin
Posts: 4375
Joined: Wed Mar 10, 2004 6:43 pm
Location: St. John's, NL
Contact:

Re: Bug Check D1 from USBSTOR.SYS

Post by GoldWave Inc. »

A BSOD error in USBSTOR.SYS indicates some kind of hardware problem. Make sure you have all the latest Windows service packs and hardware updates installed from Microsoft and the latest firmware for the drive from Plextor. Plugging the drive into a different USB port is worth a try too, but probably won't make any difference.

Chris
lurkusmaximus
Posts: 14
Joined: Wed Jun 21, 2006 4:49 pm

Post by lurkusmaximus »

It's not always a hardware problem. Many times it is a software error in the driver, USBSTOR in this case. I can see from the stack trace that Goldwave is doing a pass through to the USBSTOR.SYS driver. It couyld be a problem with a parameter passed to the driver as oppossed to a faulty piece of hardware. I'll see if I can post the stack trace to this forum later in the day.
lurkusmaximus
Posts: 14
Joined: Wed Jun 21, 2006 4:49 pm

Post by lurkusmaximus »

Here is the top level analysis from WinDebug. It shows the fault occuring in USBSTOR.SYS as it attempted to read address 0012f56d by the code residing at address f7c53c41. The instruction at that address was
USBSTOR!USBSTOR_TranslateCDBComplete+59
f7c53c41 8a4801 mov cl,[eax+0x1]

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: 0012f56d, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f7c53c41, address which referenced memory

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


READ_ADDRESS: 0012f56d

CURRENT_IRQL: 2

FAULTING_IP:
USBSTOR!USBSTOR_TranslateCDBComplete+59
f7c53c41 8a4801 mov cl,[eax+0x1]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f7c5492c to f7c53c41

TRAP_FRAME: 8054ff7c -- (.trap ffffffff8054ff7c)
ErrCode = 00000000
eax=0012f56c ebx=b25c4e6c ecx=860d9600 edx=00000000 esi=860d96f0 edi=b25c4e9c
eip=f7c53c41 esp=8054fff0 ebp=80550000 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
USBSTOR!USBSTOR_TranslateCDBComplete+0x59:
f7c53c41 8a4801 mov cl,[eax+0x1] ds:0023:0012f56d=??
Resetting default scope

STACK_TEXT:
80550000 f7c5492c 860d9600 84879008 b25c4e6c USBSTOR!USBSTOR_TranslateCDBComplete+0x59
80550028 804e3d38 8652c580 848790e4 00000000 USBSTOR!USBSTOR_CswCompletion+0xb8
80550058 f7021ee5 84879008 84849008 86f1a028 nt!IopfCompleteRequest+0xa2
805500c0 f7022b57 860d969c 00000000 86f1a7d8 USBPORT!USBPORT_CompleteTransfer+0x373
805500f0 f7023754 026e6f44 86f1a0e0 86f1a0e0 USBPORT!USBPORT_DoneTransfer+0x137
80550128 f7024f6a 86f1a028 804e2eb4 86f1a230 USBPORT!USBPORT_FlushDoneTransferList+0x16c
80550154 f7032fb0 86f1a028 804e2eb4 86f1a028 USBPORT!USBPORT_DpcWorker+0x224
80550190 f7033128 86f1a028 00000001 80558e80 USBPORT!USBPORT_IsrDpcWorker+0x37e
805501ac 804dbbd4 86f1a64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
805501d0 804dbb4d 00000000 0000000e 00000000 nt!KiRetireDpcList+0x46
805501d4 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x26


FOLLOWUP_IP:
USBSTOR!USBSTOR_TranslateCDBComplete+59
f7c53c41 8a4801 mov cl,[eax+0x1]
SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: USBSTOR!USBSTOR_TranslateCDBComplete+59

MODULE_NAME: USBSTOR

IMAGE_NAME: USBSTOR.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d6c

STACK_COMMAND: .trap ffffffff8054ff7c ; kb

FAILURE_BUCKET_ID: 0xD1_USBSTOR!USBSTOR_TranslateCDBComplete+59

BUCKET_ID: 0xD1_USBSTOR!USBSTOR_TranslateCDBComplete+59


Dumping the goldwave process I see the following thread:

PROCESS 848957d8 SessionId: 3 Cid: 1080 Peb: 7ffde000 ParentCid: 09a4
DirBase: 00e23000 ObjectTable: e1b47e00 HandleCount: 257.
Image: GoldWave.exe
VadRoot 85b61088 Vads 174 Clone 0 Private 2063. Modified 76. Locked 42.
DeviceMap e4d772a0
Token e6e7eae0
ElapsedTime 00:00:04.953
UserTime 00:00:00.609
KernelTime 00:00:01.328
QuotaPoolUsage[PagedPool] 58224
QuotaPoolUsage[NonPagedPool] 9920
Working Set Sizes (now,min,max) (3777, 50, 345) (15108KB, 200KB, 1380KB)
PeakWorkingSetSize 3789
VirtualSize 96 Mb
PeakVirtualSize 100 Mb
PageFaultCount 6870
MemoryPriority BACKGROUND
BasePriority 8
CommitCharge 3266

THREAD 8488aba0 Cid 1080.1534 Teb: 7ffdd000 Win32Thread: e51ab780 WAIT: (Executive) KernelMode Non-Alertable
b25c4e48 NotificationEvent
IRP List:
84879008: (0006,01d8) Flags: 00000000 Mdl: 84a6e700
84839008: (0006,0244) Flags: 00000070 Mdl: 00000000
Not impersonating
DeviceMap e4d772a0
Owning Process 848957d8 Image: GoldWave.exe
Wait Start TickCount 5461775 Ticks: 0
Context Switch Count 2721 LargeStack
UserTime 00:00:00.0406
KernelTime 00:00:00.0984
Start Address 0x7c810867
Win32 Start Address 0x00401a70
Stack Init b25c6000 Current b25c4dd4 Base b25c6000 Limit b25c1000 Call 0
Priority 8 BasePriority 8 PriorityDecrement 0 DecrementCount 16
*** ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys
*** ERROR: Module load completed but symbols could not be loaded for Cdr4_xp.SYS
*** ERROR: Module load completed but symbols could not be loaded for Cdralw2k.SYS
ChildEBP RetAddr
b25c4dec 804dc0f7 nt!KiSwapContext+0x2e (FPO: [Uses EBP] [0,0,4])
b25c4df8 804dc143 nt!KiSwapThread+0x46 (FPO: [0,0,0])
b25c4e20 f7c58727 nt!KeWaitForSingleObject+0x1c2 (FPO: [Non-Fpo])
b25c4eb0 f7c587b6 USBSTOR!PortpSendValidPassThrough+0xdb (FPO: [Non-Fpo])
b25c4ee8 f7c58163 USBSTOR!PortSendPassThrough+0x52 (FPO: [Non-Fpo])
b25c4f24 f7c581f3 USBSTOR!USBSTOR_SendPassThrough+0x45 (FPO: [Non-Fpo])
b25c4f40 804e37f7 USBSTOR!USBSTOR_DeviceControl+0x73 (FPO: [Non-Fpo])
b25c4f50 f7a94289 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
b25c4f64 f7a959fe Imapi!ImapiDefaultIrpHandler+0x7b (FPO: [Non-Fpo])
b25c4f94 804e37f7 Imapi!ImapiDispatchIoctl+0x6b0 (FPO: [Non-Fpo])
b25c4fa4 f7afc1c4 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
WARNING: Stack unwind information not available. Following frames may be wrong.
b25c4fcc f7afb2e1 PxHelp20+0x11c4
b25c5004 f6fe76dd PxHelp20+0x2e1
b25c5980 804e37f7 Cdr4_xp+0x86dd
b25c5990 f78b5c3a nt!IopfCallDriver+0x31 (FPO: [0,0,0])
b25c5a14 f7a476ef CLASSPNP!ClassDeviceControl+0x87e (FPO: [Non-Fpo])
b25c5aa8 f78b447f cdrom!CdRomDeviceControlDispatch+0x4b7 (FPO: [Non-Fpo])
b25c5ac4 804e37f7 CLASSPNP!ClassDeviceControlDispatch+0x48 (FPO: [Non-Fpo])
b25c5ad4 f7a53a35 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
b25c5adc f7a54c28 redbook!RedBookSendToNextDriver+0x35 (FPO: [Non-Fpo])
b25c5b20 804e37f7 redbook!RedBookDeviceControl+0x548 (FPO: [Non-Fpo])
b25c5b30 f7b7eade nt!IopfCallDriver+0x31 (FPO: [0,0,0])
b25c5b60 804e37f7 Cdralw2k+0x3ade
b25c5be4 8059ceb5 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
b25c5bf4 8059ce63 nt!RawReadWriteDeviceControl+0x60 (FPO: [Non-Fpo])
b25c5c34 804e37f7 nt!RawDispatch+0x114 (FPO: [Non-Fpo])
b25c5c44 8056a101 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
b25c5c58 80579a8a nt!IopSynchronousServiceTail+0x60 (FPO: [Non-Fpo])
b25c5d00 8057bfa5 nt!IopXxxControlFile+0x611 (FPO: [Non-Fpo])
b25c5d34 804de7ec nt!NtDeviceIoControlFile+0x2a (FPO: [Non-Fpo])
b25c5d34 7c90eb94 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ b25c5d64)
0012f484 00000000 0x7c90eb94


This clearly shows Goldwave calling into USBSTOR.SYS in pass through mode. Nothing wrong with that as long as all the parameters are correct. The stack which faulted appears to be from USBSTOR just working through all the deferred procedure calls from the interrupts the device was generating.
GoldWave Inc.
Site Admin
Posts: 4375
Joined: Wed Mar 10, 2004 6:43 pm
Location: St. John's, NL
Contact:

Post by GoldWave Inc. »

I do not know of any way that GoldWave could cause such an error. Even if the parameters were incorrect, that would only return an error to the program, not a BSOD.

Searching on Google gives similar reports, but none related to GoldWave. However, a similar topic was posted a couple of years ago.

Do you have access to another computer you can try using GoldWave and the USB drive on?

Chris
Togglehead
Posts: 98
Joined: Mon Apr 10, 2006 1:37 pm
Location: Jersey

Post by Togglehead »

i have most certainly seen goldwave have its errors for me at times....but i have never seen it BSOD.

...matter of fact...i RARELY see software cause a BSOD...but thats just me.

Is it a USB 2.0 drive with 2.0 drivers?

Maybe list your PC specs and ill see what my hardware brain can come up with....
lurkusmaximus
Posts: 14
Joined: Wed Jun 21, 2006 4:49 pm

Post by lurkusmaximus »

I've had it fail on two different machines. The first one is:

Dell Latitude D800 Laptop
2 GBytes RAM
Pentium M at 1.66 Ghz
Intel 82801DB/DBM USB 2.0 Enhanced Host Controller
XP Pro SP2 + Hotfixes
Samsung IDE DVD/CDRW (which works but much slower than my USB drive)
Plextor PX-716UF USB DVDRW (which fails because it's usbstor.sys that faults)


The second is:

Intel D845EGB2 Motherboard
2.4 GHz P4
1 GByte RAM
USB 2.0
Pioneer DVD-303 SCSI drive
Toshiba SD-R1102 DVD IDE Drive
Plextor PX-716UF USB DVDRW
Intel PCI to USB 2.0 Enhanced Host Controller (PCI card not USB on motherboard)
M-Audio Sound Card
XP Pro SP2 + Hotfixes

To tell you the truth, it would not surprise me for it to be a bug in USBSTOR.SYS. I really don't know how common USB DVDRW drives are today. But it sure is a heck of a lot faster than my aged SCSI and IDE DVD drives!
GoldWave Inc.
Site Admin
Posts: 4375
Joined: Wed Mar 10, 2004 6:43 pm
Location: St. John's, NL
Contact:

Post by GoldWave Inc. »

Does the CD device name shown in GoldWave include the version number of the drive? The latest version of the firmware on Plextor's website is 1.09 (available here).

If you hold down the Shift key (to block AutoRun) for a minute when changing the CD, does the error still occur?

Chris
lurkusmaximus
Posts: 14
Joined: Wed Jun 21, 2006 4:49 pm

Post by lurkusmaximus »

I upgraded the firmware from 1.02 to 1.09. Still failed in identical manner.

Tried holding down shift at disc change to prevent autorun. Still failed in identical manner.

Thanks for the good suggestions though!
GoldWave Inc.
Site Admin
Posts: 4375
Joined: Wed Mar 10, 2004 6:43 pm
Location: St. John's, NL
Contact:

Post by GoldWave Inc. »

Unfortunately I cannot think of anything else that might help. Since the BSOD happens with PlexTools Pro as well, Plextor's techical support may have some suggestions, given they created both the hardware and the software.

Chris
lurkusmaximus
Posts: 14
Joined: Wed Jun 21, 2006 4:49 pm

Post by lurkusmaximus »

Thanks for all your help! It's a real poser for sure!
Togglehead
Posts: 98
Joined: Mon Apr 10, 2006 1:37 pm
Location: Jersey

Post by Togglehead »

This sounds like a USB 2.0 error......

Is it possible youre using a USB 1.1 driver for a 2.0 device?

I only ask cuz im a hardware nut, and ive seen stranger happen for a borked driver install.
lurkusmaximus
Posts: 14
Joined: Wed Jun 21, 2006 4:49 pm

Post by lurkusmaximus »

On my laptop I only have USB 2.0 ports. On my other machine I have a mix of 1.0 and 2.0 ports. Both machines fail. I assume that USBSTOR.SYS is independent of USB level as that would be handled farther down the driver stack.
Post Reply