玩真三时候电脑突然画面静止，呈死机现象，只有背景声音而画面不能动。想起前段时间也会出现的，在运行大型游戏时候会出现突然黑屏或者自动重启但背景有声音的情况，我想，极有可能是显卡驱动存在问题，我的Win2003系统，硬件驱动兼容方面不是多好，于是网上查询了解决方法，实话说，没有彻底的解决办法，问题摆在这里。
查看系统日志，果然与Ati显卡驱动有点问题，因为我在电脑上装有Win7和WinXP，貌似很少这种情况。
解决办法，这个只有更换驱动或者系统，硬件驱动存在不兼容咱也没办法，估计还与,net的编程软件有关系。看微软的问题记录 [注：截至到2021-11-16，上述链接在ms那边已经404了]，如下记录：
\SystemRoot\System32\RDPDD.dll failed to load
RATE THIS
弹出应用程序: : SystemRootSystem32ativvaxx.dll failed to load 解决办法:
SystemRootSystem32ativvaxx.dll failed to load:BooRadely 4 Jan 2008 6:51 PM 114
This is an FYI post for an issue we've seen on a couple of Windows 2003 SP2 servers internally. Hopefully if someone hits this in the wild they'll be able to find this post on the intertubes.
Symptom:
When attempting to connect from the client via RDP, you would click “connect” and then soon after it would silently fail and “connect” would be clickable again.
Each time when attempting to connect, the server would log this event:
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 9/25/2007
Time: 12:13:57 PM
User: N/A
Computer: ServerX
Description:
Application popup: : \SystemRoot\System32\RDPDD.dll failed to load
For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00000000 006c0002 00000000 4000001a
0010: c0000017 c000009a 00000000 00000000
0020: 00000000 00000000
Our Resolution
A) We found that in our cases it was an issue with the ATI driver and by either rolling back the ATI driver for the display on the server or upgrading the display driver on the server resolved the issue. Reports in the comments show the same for Nvidia drivers
B) In another instance it was found that by going to: Display Properties --> Settings --> Advanced --> Troubleshoot, turn off "Hardware acceleration” resolved the issue as well without adjusting the drivers.
C) On the internet I've seen posts showing SFC to help but in my cases it did not.
Update from comments:
D) A solution found at http://forums.nvidia.com/index.php?showtopic=67147&hl=remote%20desktop&st=60 worked for me (and others.)
It's a registry fix that increases the size of the session image space. Add the following key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
"SessionImageSize"=dword:00000020
Where 00000020 is hex for 32
In any case the event was a red herring and was just a generic error being bubbled up from Win32k.sys..
Technorati tags: Windows 2003, RDP, SP2
Business up front, Windows 2003
弹出应用程序: : SystemRootSystem32ativvaxx.dll failed to load 解决办法 - 我才是大雄 - 我和我的花兒們弹出应用程序: : SystemRootSystem32ativvaxx.dll failed to load 解决办法 - 我才是大雄 - 我和我的花兒們弹出应用程序: : SystemRootSystem32ativvaxx.dll failed to load 解决办法 - 我才是大雄 - 我和我的花兒們弹出应用程序: : SystemRootSystem32ativvaxx.dll failed to load 解决办法 - 我才是大雄 - 我和我的花兒們
弹出应用程序: : SystemRootSystem32ativvaxx.dll failed to load 解决办法 - 我才是大雄 - 我和我的花兒們
Comments
Geek Lectures - Things geeks should know about ? Blog Archive ? \SystemRoot\System32\RDPDD.dll failed to load 4 Jan 2008 7:08 PM
PingBack from http://geeklectures.info/2008/01/04/systemrootsystem32rdpdddll-failed-to-load/
velga 9 Jan 2008 5:02 PM
I only had this problem after installing .NET 3. on W2K3-SrvHunSP2+Term Serv. Ati driver adjusting solved it.
Thx!
BooRadely 10 Jan 2008 11:56 AM
Alright glad it helped!
Anonymous 24 Jan 2008 4:32 PM
Great info! I had the same problem after installing .Net 3.5....it was just driving me crazy!
Roger McCubbins 6 Mar 2008 11:34 PM
I have a client with new Dell XP machines and nothing but seemingly random glitches with connecting to them via RDP. First it was BSoDs. ATI seemed the culprit from the bugcheck, but there was no updated Dell ATI driver. Updating with the ATI driver from the ATI/AMD website seemed to help, but there were still lockups after accessing via RDP the first time.
Now, we've got a couple machines that just refuse the connection, with the above error you about. Imagine my surprise when ATI was your culprit!
I think the VERY latest driver off the website is going to resolve my problem, but honestly? I've been trying to track this down for months.
ATI + .Net is a clue. I couldn't get them to break out of the box, but after all our apps were on, they did it. One app installs .Net 2.0 - my money is on that combo.
Paul R. Dietz 25 Mar 2008 2:54 PM
Had this appear on XP Pro on a dual-core AMD system after updating the ATI Radeon drivers.
Disabled Hardware Acceleration and RDP now works again.
Skynet 15 May 2008 5:16 PM
I yesterday updated to nvidia driver 175.16, and remote desktop works nomore.
It seems there's a strong relationship between video drivers and RD. But since this is a very old problem (i found many discussions about it which have been started in 2006 and 2007), MS should release a patch to solve it.
BooRadely 16 May 2008 1:12 PM
It's actually a problem with the card/drivers not with the OS.
Luke Smith 29 May 2008 12:17 AM
Application popup: : \SystemRoot\System32\RDPDD.dll failed to load is showing numerous times in my Event viewer - system folder after I try to RDP to my machine from another computer. Basically, I hit "connect" in RDP, and the little box flashes and doesn't do anything. I am running Windows XP Pro. I would like to add to one of the previous posts from a user named "Skynet." I just installed nVidia display driver 175.16, and that's when my RDP broke. nVidia and Microsoft have yet to fix this problem, but I will be contacting nVidia about it, tomorrow. I will let you all know what I find out.
Luke Smith 29 May 2008 12:46 AM
UPDATE: I just wanted to confirm my previous post. nVidia display driver 175.16 BROKE my RDP. I rolled back the driver and restarted my computer. Lo-and-behold.... I was successfully able to RDP my machine from another machine. I'm definitely going to put in a support ticket or phone call to nVidia, tomorrow, to let them know of this problem.
blogfeuer 31 May 2008 7:54 AM
Same here in Germay. After Nvidia Update. RDP stopped.
Chris Franzen 1 Jun 2008 5:53 PM
Unbelievable, but true. Of course, Murphy let me use a headless system (no display, no keyboard) when I discovered it. The win installation on that machine used to have an ATI card, now it uses an NVIDIA...so I?ll roll back the NVIDIA driver to a previous release and re-check.
Why are we wasting our time with this .... uglyness???
mastman 3 Jun 2008 12:16 PM
It is ugliness, but the NVIDIA driver rollback finally saved me from over a week of changing security settings, uninstalling and reinstalling XP SP3, etc. RDP is working again.
dude 5 Jun 2008 2:51 AM
rolled back nvidia driver and sure enough rdp working now...can't beleive it great work and thanks a mill
Markus 6 Jun 2008 9:54 AM
Had this problem on a XP Professional box with ATI graphics card. Updating the driver fixed the problem.
Thanks a lot.
LOC 7 Jun 2008 8:58 AM
Thanks for the info! You saved me from hours of pointless fight with RDP and system settings. Nvidia rollback helped! Thanks again!
Hamm 7 Jun 2008 7:55 PM
Same here. 175.16 broke RDP for me. I rolled back the driver and it works now. As of this time 175.16 is still the latest driver. Thanks for sharing, guys.
bg 10 Jun 2008 12:09 AM
so which version is working for you guys?
mith 10 Jun 2008 2:56 PM
I'm using the nVidia 175.16 drivers, and am experiencing the same thing; yesterday it worked for one connection, after disconnect I can no longer connect. I'll just stick with VNC until they fix the drivers
Peter 19 Jun 2008 11:21 PM
Same issue after upgrading to Nvidia 175.16, really a pain because Spore is crashing with older drivers... then again, maybe I've created enough unnatural freaky creatures until the game comes out.
Les 20 Jun 2008 2:41 PM
Great info! I had Nvidia 175.16 driver version as well and could not remote into my PC. Once I installed driver version 6.14.11.6921 (12/5/07), I was able to remote into my PC.
Thanks for the help!
Reinhard 23 Jun 2008 1:06 PM
The Nvidia driver 175.19 released today has no resolution for this issue. My PC is only one of over 300 with Nvidia GeForce 6200 TM (but the only one with XP SP3), RDP is an often used feature. So we must avoid to install/build in this and the former driver over/in our RIS or WDS image for XP with integrated SP3 installations. Thank you NVidia 🙁
Reinhard
silicon 24 Jun 2008 11:57 AM
install nvidia drivers 169.21 if you want remote desktop to work, nvidia still doesn't know how to make proper drivers and apparently microsoft doesn't know how to test drivers either.
Words 24 Jun 2008 5:51 PM
Just so its recorded somewhere. I was having a problem with my XBOX 360 connecting to my Media Center PC, it would just hang on the "Contacting . . ." screen. I had updated my NVIDIA card with the 175.19 driver recently and this seems to be the problem. Rolling back to the previous driver resolved my XBOX problem as it seems to rely on this same DLL to connect and show Media Center on my TV via the XBOX.
Anthony 27 Jun 2008 9:47 AM
Using nVidia 175.19 and having a similar problem. Rebooting fixes it for a while but then it returns. Anyone know where I can get an older version of the nVidia drivers for a GeForce 6800GT?
thanks!
E Newton 30 Jun 2008 12:54 PM
This was happening off and on, now even about a reboot it doesnt work.
I fail to see how its a display driver problem when RDP is meant to virtualize the display...
However, I bet Vista's more component based architecture probably wont have the same issue
gfl 3 Jul 2008 4:27 PM
Thanks! Upgrading the nVidia driver fixed the problem for me. Who'd a thunk it ...
Matthew McKenzie 10 Jul 2008 11:50 PM
Hey folks, I happened across this blog post and figured others who find it might benefit from some additional info on the problem.
For the record, here is some relevant info on my WinXP systems:
System 1:
Asus A8N-32SLI
Nvidia GeForce 7600GS
System 2:
Abit A-N78HD with onboard Nvidia GeForce 8200 graphics
Nvidia GeForce 8600GS (running an additional display)
As many people have discovered, the issue cited in the title to this blog post affects the Nvidia 175.16 driver package. Last week, Nvidia released an update -- 175.19 -- that many people assumed would fix the problem.
I can personally confirm that the 175.19 drivers do NOT fix the problem, at least not on my systems.
On my Abit system, my options are very limited; the Nvidia 8200 onboard display is supported officially only on the GeForce 174.xx and 175.xx driver packages. I have a 174.74 driver package that I have not yet tried; perhaps this will fix the RDP issue.
My other option on this system involved using the 177.35 driver package. Nvidia has released this package only for its GTX series cards, but a PC modding enthusiast has posted a modded version of the 177.35 inf file that enables support for legacy Nvidia cards. I won't post the link here, since using modded inf files is not a good idea unless you are prepared to deal with possible serious problems that may result. You can find the link, however, with a little searching on the Nvidia support forums (forums.nvidia.com).
As for my Asus system, the solution is much easier: I have rolled back the drivers to version 163.75. A more recent release, 169.21, also fixes the remote desktop issue, but in my case, it introduces another problem -- after closing a remote desktop session, this system ends up in 4-bit, 800 x 600 display mode and cannot be changed without a reboot. Fortunately, the 7600GS is old enough that a number of older driver packages are also available.
Nvidia has done NOTHING to address the remote desktop issue. Many people assumed the 175.19 package was released mostly in order to fix this problem, but obviously that was not the case. I would urge any Nvidia users who have this problem to complain both to the company and on public forums like this one, in order to make it clear to the company that ignoring a problem like this is completely unacceptable and will carry serious negative PR consequences.
Hope this info helps, and good luck!
john 11 Jul 2008 4:03 PM
this just happened to me after i installed and rebootedhttp://pastebin.com/d75e1941e
i'm running windows xp pro sp3.. this is REALLY odd..
crispy602 14 Jul 2008 8:59 PM
yep looks like a confirmed bug, was scouring the nvidia forums and found this:
http://forums.nvidia.com/index.php?showtopic=67147&hl=remote+desktop
I managed to use the drivers here
http://www.laptopvideo2go.com/forum/index.php?showforum=94
and it fixed it
Scott 15 Jul 2008 8:27 AM
I have a GeForce 8600GTS and I have the 175.19 installed on my computer, and I can't TS to my computer. I installed the 169.21 driver and I can now TS to my box. To get get older drivers check out nvidias driver archive:http://www.nvidia.com/Download/Find.aspx?lang=en-us
Scott
tjebe 18 Jul 2008 11:41 AM
A solution found at http://forums.nvidia.com/index.php?showtopic=67147&hl=remote%20desktop&st=60 worked for me (and others.)
It's a registry fix that increases the size of the session image space. Add the following key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
"SessionImageSize"=dword:00000020
Where 00000020 is hex for 32
J Y 18 Jul 2008 1:30 PM
tjebe,
that registry edit worked! thanks for the help; you saved me a lot of work hunting for a solution.
Zane Perry 21 Jul 2008 12:38 AM
I just ran into this problem. First I tried to download the latest drivers to see if it has been fixed yet. No success. The registry hack worked. Thank you.
I wrote a post in the NVIDIA forum to try to bring this issue to their attention. Go ahead and check it out (and vote yes) to help encourage them to fix it.
http://forums.nvidia.com/index.php?showtopic=72956&hl=
Argh McFrustrated 21 Jul 2008 9:28 AM
What no one seems to bother to mention is if you do the reg hack on the computer you remote to (host) or the computer you remote from (client); or both. Adding the reg hack to the computer I remote from doesn't fix it.
Robert Trufant 25 Jul 2008 6:31 PM
The registry hack has to be placed on the host computer. Hope that this helps 🙂
andreaccs 27 Jul 2008 2:37 PM
same error for me. this was a life safer!!!!
Iury Boldyrev 29 Jul 2008 11:56 AM
by a fluke I found new solution for this problem. I have Windows Server 2003 with ATI Radeon & recently acquired trouble with Remote Desktop Connection.
I uninstalled ATI Control Center (demanding from "NET framework"), then all NET framework components, but RDC client stay could not connect & I received "RDPDD.dll failed to load" message again.
I don't want downgrade or uninstall Radeon driver or turn off Hardware acceleration permanently. I found this solution:
I temporarily turned off "Hardware acceleration” in "Troubleshoot" part of Display Properties; then connected Remote Desktop Client from my laptop, take Login screen & immediately TURNed ON "Hardware acceleration” ON SERVER. Then I tried logoff, connected again ("Hardware acceleration” stay ON ) & I take connecttion without "RDPDD.dll failed to load" messages in log. But I have not been rebooted server after that.
Exuse my awful English, please.
olli 30 Jul 2008 7:00 AM
Still getting this problem with 175.19 and RD.
I'm not getting any system events when the login fails.
I've checked my registry and that key doesn't exist, does anybody know if it's been renamed with SP3?
I have SessionViewSize (defaults to 30) and SessionPoolSize (defaults to 4).
Thanks a lot.
Steve Banford 30 Jul 2008 1:14 PM
This RDP issue began recently for me with our last influx of new workstations. They all have the newest Nvidia GeForce 98000 GTX graphics cards. Since disabling the graphics accelerator is not a option for us and I don't subscribe to using a earlier drivers I tried adding the registry key first. It solved the problem. I think I am going to call Nvidia about this. Thanks for everyones input. Very helpful. Steve Banford
Ian Hellier 5 Aug 2008 1:34 PM
Fix didn't work for me, although their 177 beta drivers did fix it.
Seems they either know about it or it fixed itself.
-ian
rboydston 19 Aug 2008 8:52 AM
http://www.nvidia.com/object/winxp_177.79_beta.html
177.79 beta solved it for me.
xp sp3 w nvidia 8600 gts
Reinier Post 27 Aug 2008 7:06 PM
The fix to add the registry key (no it doesn't exist beforehand) also worked for me.
(And I wouldn't be typing this if it didn't.)
Jon Green 30 Aug 2008 3:35 PM
This also fixed my loss of ability to print via LPR (Brother HL-1250, in case that's relevant and people are searching for a solution). I lost that, and remote desktop, after updating nvidia's video drivers.
HerbCSO 4 Sep 2008 7:59 AM
Sho' 'nuff, registry hack fixed it (latest NVIDIA 175.19 did it in for me). Thx for posting the solution!
Paul 10 Sep 2008 7:38 AM
I've done the reg hack, but it keeps coming back on a system with an ATI card and the latest driver (the small download, not the one with all the added stuff) even tried upping the value to 40 instead of 20 with no luck, it works for a while, then breaks again. Surely this is an issue MS and the gfx card manufacturers need to address? I use RD for mostly non-work reasons, but it's clearly affecting people who really need it
Matthias 15 Sep 2008 8:47 AM
It did not work for me.
(Nvidia-Card, XPSP3)
Matthias
Par 15 Sep 2008 6:53 PM
I started getting this problem on a computer I just built. It is an AMD X2 and a gigabit mobo with, this is the important part, on board ATI radeon hd3200. I did not disable hardware acceleration because of games I play, but I found installing the latest drivers from ATI's site fixed the problem.
Solution for ATI? Get updated drivers.
Paul 16 Sep 2008 11:41 AM
It'll work for a while Par, mine does if I just reload the drivers, then it dies on it's arse again a few days later, sometimes a reboot wakes it back up, others it kills it dead. Don't bother asking ATI, they'll claim it's unsupported. I'll be buying nVidia next time, at least they seem to have directly or indirectly made it work.
Rick 1 Oct 2008 11:02 PM
I downloaded Nvidia 178.13 today (released Sept 25, 2008) and it solved the problem for me.
kevin 9 Oct 2008 2:18 AM
Nvidia 178.13 also solved the problem for me. Amazing.
Greg Moore 10 Oct 2008 3:55 PM
I had this exact problem with an older (as of 10/10/2008) version of the NVIDIA drivers running on a GeForce 8600 controller.
After installing the vresion 178.13 drivers, it is now allowing RDP sessions in.
NOTE: We are also running this XP Professional station in /3GB mode.
tma 11 Oct 2008 5:34 PM
Please reboot(obvious? :/) the host computer AFTER the reg hack is done.
It worked for me that way.
MadMat 15 Oct 2008 4:41 PM
Ca a marché pour moi apres un reboot! Merci beaucoup!
Sam 3 Nov 2008 3:21 AM
This did the trick. Thanks.
Add the following key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
"SessionImageSize"=dword:00000020
Where 00000020 is hex for 32
Garry 4 Nov 2008 9:33 AM
Cool!!!! Finally, after several months of only having VNC as a ways of getting to one of my boxes, I can finally use RDP again 🙂
Arthur 11 Nov 2008 6:35 PM
Very very happy I found you pages!!
The regedit solution works for my Nvidia 8200, now RPD and Home Server Console are up and running again.
Nathan 12 Nov 2008 9:31 AM
Wow...this had been troubling me for a week+. I could RDP out to anything, but I was not able to connect to my machine using RDP from home, which was actually incredibly poor timing for it to fail. The day before, I installed a SQL Server test package on my machine which had required .NET 3.5 so I could learn more about SQL. I had installed SP3 a few months back, and had no connection issues until the .NET 3.5 was installed. I installed the latest ATI video drivers and it works fine now. THANKS!
Doug 13 Nov 2008 1:15 AM
I was having the same problem described with my Nvidia 6600GT.
I had display driver 175.19...
Upgraded to 178.24 and now Remote Desktop works fine!
Love, Doug.