![]() |
Windows 8.1 wake and crash
1 Attachment(s)
This is my first time posting so please let me know if you need more information. I'm running Windows 8.1 Enterprise 64bit with M01061 Displaylinks and driver 7.5.54609.0. Sometimes if I hibernate and wake up the system I end up with the system crashing on wake. I get a crashdump file which when I analyze it I see usbhub3 driver being shown as the cause. From what I understand this usually means something attached to the USB caused it which I have a few USB devices keyboard, mouse, external drive, and also the displaylinks. I'm unsure if the displaylinks are the cause. Any suggestions on next steps? I could remove the displaylinks and see if it happens again overnight as it won't happen if the system has been hibernated for a short time. I've attached the Displaylink support file is that helps.
|
This is the USB3.0 driver for the root hub of the laptop. It should not be possible to cause this to BSOD, but could be related to a device on the USB bus.
It could be due to a rare deadlock in our audio driver in v7.5, which should be fixed in the audio driver in v7.6. An Alpha is available here: http://displaylink.com/support/sla.php?fileid=112 Could you download and try this and see if it solves the issue? Wim |
I just installed it and will let you know in a week if I have a crash or not.
|
I have similar issues, and the alpha did not seem to fix them. My problem is not that I get a BSOD on resume from hibernate, but rather the system often reboots instead of resuming from hibernation. This is with a Surface Pro 2.
If there is anything I can do to help debug this issue, feel free to let me know. Peter |
Quote:
Please attach the logs from this tool: http://www.displaylink.com/support/ticket.php?id=269 When you reply please select "Manage Attachments" from the "Additional Options" section below. From there select Upload and navigate to the output of the tool. Thanks, James |
1 Attachment(s)
Here is the file.
Thanks for looking into this! |
As an update I haven't had any BSODs since updating to the alpha release except for my wifi driver and the bluetooth. As for odd reboots reported by the one user I had this happen too which can still be a BSOD. You can tell by looking for a minidumps in C:\Windows\minidump. I use bluescreenview and windbg to open them up and see which driver caused it though you may need to pull down symbols to narrow it down so it can get a little complicated but is doable if you google.
|
Quote:
Quote:
We do have a Surface Pro here that we test on and not seen this BSOD. Do you have any other USB devices connected? Would be worth disconnecting USB devices to try and see what the offender is. Wim |
Thanks for looking into this!
As for USB devices, most of the time I have my Dynadock attached, and occasionally I add USB storage devices to the USB port of the Dynadock. BTW, I have a Surface Pro 2, not a Surface Pro. Cheers, Peter |
1 Attachment(s)
Got another wakeup related crash. I attach the dump file for reference. No USB devices were attached to the system.
Thanks for looking into this! |
Quote:
Implicit thread is now ffffe000`b6800880 Probably caused by : WUDFRd.sys ( WUDFRd!WdfObjectList<RdDeviceInterface,RdDeviceInt erfaceParameters>::EnumFirst+22 ) This is caused by a driver for a removable USB drive (WUDFRd.sys) I'd suggest checking in with the USB drive manufacturer for the latest driver. Thanks, James |
Not sure how I should update the driver of the USB drive. Aren't these autoinstalled by Windows? I'm not even sure about the supplier of the drive...
Anyway, are there some quick instructions about how I can get the debug information you posted from the crash dump file myself? That way I don't have to bother you with DisplayLink unrelated issues. Thanks a lot! |
|
| All times are GMT. The time now is 04:33 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2026, vBulletin Solutions, Inc.