BSOD Remote desktop RDPUDD.dll

T3hAnswer · 27 Aug 2013

Hey!

Getting BSOD-s when opening youtube links in remote desktop session. Last link was youtube video using HTML5. Both computers are running Windows 7, 64bit and RDP 8.0.

Dumps refer to rdpudd.dll, which should be UMRDP display driver. I have included the minidumps. Google doesn't show almost nothing regarding that dll so it seems rather rare bug (i guess most people don't try to watch videos with remote desktop).

Also i can't really be sure if it really is BSOD, cause this being remote desktop issue i just know that remote comp hangs and then restarts.

Thanks in advance!

Arc · 27 Aug 2013

Hello T3hAnswer.

Dont use a BETA version of a display driver. See if it works stable with the latest 320.49 WHQL at first. If not, try version 314.22 WHQL.

How to uninstall and reinstall nvidia display driver:

Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
Now follow Drivers - Clean Left over Files after Uninstalling
Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 320.49 / 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Also update Creative sound card driver from Creative Worldwide Support

Let us know the results.

T3hAnswer · 27 Aug 2013

Those beta drivers helped me regarding the BSOD that was caused by nvlddmkm.sys. I recently got new videocard and the drivers that came with that caused BSOD-s(as you can see from the older minidumps in there).Installing beta drivers fixed the problem(it's even mentioned in the nvidia fix list). nvlddmkm.sys bsod was much more frequent and random so i can't go back to those drivers. With rdpudd.dll bsod I atleast know what sort of causes it and don't have to deal with it when I'm home.

The problem with rdpudd.dll is older and predates this videocard(last videocard was actually AMD's).

I found this thread in MS forums and only solution offered in there is turning off RDP 8.0.
(Windows 7 SP1 Remote Desktop SYSTEM_SERVICE_EXCEPTION - Microsoft Community)

This goes well with my experience of using the same comps and opsystems but using the older remote desktop protocol and not having the bsods. Unfortunately rdp 8.0 is MUCH better so i kind of want to keep using it.

I'll update the audio driver but i'm pretty sure it's not the cause of this.

Arc · 27 Aug 2013

Remote Desktop Protocol is a system element and it is not the actual reason of the BSOD, despite of the crash dump output. 90% of stop 0x3B instances are due to misinstalled (sometimes failing) display drivers.

Yes, 320.49 WHQL is buggy. You may try 320.18 then (in case that your GPU may not support 314.22 WHQL) But the total removal and clean reinstall of the display driver is needed there. RDPUDD is a display element after all .... but the system element. So check for the third party elements to be free from errors.