BSOD clicking folders in file explorer, STOP 0xb8

Idolon said:

I have a new (about two weeks old) Dell XPS 14 which is randomly getting BSODs, most of which occurred shortly after double-clicking on folders in file explorer. BlueScreenView blames ntoskrnl.exe, iusb3xhc.sys, iusb3hub.sys, rdwm1098.sys or some combination of those for the crashes.

The majority of crashes are 0xb8, ATTEMPTED_SWITCH_FROM_DPC. One 0xa, IRQL_NOT_LESS_OR_EQUAL also occurred, which I believe happened when I tried to start a YouTube video. I am not sure if this crash is related the others.

My laptop has two USB 3.0 ports, one of which is connected to a Plugable 7 port USB 2.0 hub. Attached to the hub are the following:

• ASUS SDRW-08D1S-U optical drive (2 ports)
• Logitech Unifying Receiver
• Roland UA-1G audio interface

According to Google, rdwm1098.sys is probably part of the UA-1G driver, which leads me to believe that the audio interface isn't playing nicely with USB 3.0. What I can't explain is—if this is an audio interface problem—why this only seems to happen when I open folders in file explorer. When it crashes, the navigation sound effect (click sound) does fully play before the screen momentarily goes black, then switches to the BSOD screen. My computer has no trouble playing audio through the UA-1G otherwise.

I will leave my UA-1G disconnected for now to see if the crashes go away. Unfortunately, the crashes are very irregular, so it will be difficult to tell if the change has helped.

Can anyone help me find the cause of these crashes?

Hello there!

The dump files were a little vague. But according to what you said there is a good chance that it's UA-1G. Sometimes just disconnecting the device won't do it. You need to uninstall the software and drivers with it.

Run SFC Scan SFC /SCANNOW Command - System File Checker


BSOD BUGCHECK SUMMARY

Code:

Loading Dump File [C:\Documents and Settings\Shyam\_jcgriff2_\dbug\__Kernel__\080512-25022-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Aug  6 06:34:55.493 2012 (GMT+5)
System Uptime: 1 days 0:05:43.961
BugCheck 100000B8, {fffffa800a8e0060, fffff8800336ffc0, 0, 0}
*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0xB8
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
Bugcheck code 100000B8
Arguments fffffa80`0a8e0060 fffff880`0336ffc0 00000000`00000000 00000000`00000000
BiosVersion = A04
BiosReleaseDate = 06/26/2012
SystemManufacturer = Dell Inc.
SystemProductName = XPS L421X
MaxSpeed:     1700
CurrentSpeed: 1696
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Documents and Settings\Shyam\_jcgriff2_\dbug\__Kernel__\080412-27222-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Aug  4 15:34:46.564 2012 (GMT+5)
System Uptime: 1 days 21:33:09.032
BugCheck 100000B8, {fffff880033e1fc0, fffffa80042c7040, 0, 0}
*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0xB8
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
Bugcheck code 100000B8
Arguments fffff880`033e1fc0 fffffa80`042c7040 00000000`00000000 00000000`00000000
BiosVersion = A04
BiosReleaseDate = 06/26/2012
SystemManufacturer = Dell Inc.
SystemProductName = XPS L421X
MaxSpeed:     1700
CurrentSpeed: 1696
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Idolon said:

Thanks. I've been running without the UA-1G connected since my first post and it hasn't crashed so far. I'll have to send Roland's tech support an email so they can look at the problem.

That's good news. Thanks for the update. :)

Idolon said:

Well, Roland's US tech support has never seen this problem, but they forwarded my crash logs and system info to the engineers in Japan who write the software.

Thanks for the update. Do let us know how it does :)