Highlighted
Goshik
1 Copper

XPS 13 9350 BSOD caused by network driver from Dell

Symptoms:

You disconnect a USB-C adapter with Ethernet from you laptop, you send it to sleep, but it never goes there. Instead, display turns off and after 5 mins you see BSOD with 0x0000009f DRIVER_POWER_STATE_FAILURE error.

Cause:

Memory dump investigation showed the following:

FAILURE_ID_HASH_STRING: km:0x9f_4_rtux64w10_stackptr_error_image_usbhub3.sys

This means that the culprit is rtux64w10.sys, which is responsible for Realtek USB GbE Family Controller. The problematic version is 10.28.1002.2018, which I installed from Dell's website.

Solution:

Remove the network device associated with your USB-C adapter as shown on the screenshot. Reconnect the device and wait until the default version installs. In my case it was version 10.20.824.2017 and it seems to be much more stable than Dell's version.

mmc_2019-02-08_15-57-37.png

Hope it helps someone.

Labels (5)
2 Replies
JOcean
5 Tungsten

Re: XPS 13 9350 BSOD caused by network driver from Dell

Thanks for sharing that in the forum!

 




-Forum Member since 2016
-I do not work for Dell
-A user helping other users
-If you like an answer please click on thumbs up
-If a reply is a solution to your problem please click on Accept as Solution
Gaming on a home built ASUS B450-F Gaming with Ryzen 5 2600X
Real work on an Inspiron 15 5575
0 Kudos
botfixer
1 Copper

Re: XPS 13 9350 BSOD caused by network driver from Dell

Same here with our machines (Dell Precision 5510 / 5520). With Realtek USB Ethernet Driver published from Dell Command Update (10.28.1002.2018), after plug out the Dell WD15 Docking Station, everything looks fine.

But when the System goes to sleep, you try to reconnect the Dock or replug some USB Device (no matter if this is a USB-C oder USB 2.0, USB 3.0 Device) they not functional any more. When restarting the device it takes long (windows is restarting) and ends up in a bluscreen (DRIVER_POWER_STATE_FAILURE). Unfortunately my memorydump has no indication what the problem is, just ntoskernel.exe.

After investigating, we find it out. After deinstallation of the Realtek Driver (10.28.1002.2018) and restart, everything is going back to normal.

0 Kudos