WHQL 175.16 - remote desktop fails Options

[KrevNasty]

I have a 7800 GS and the same exact issue, I'm going to try rolling back the driver.

[ZeWaren]

This problem is not specific to any one graphics company.  It can probably happen with printer drivers too.

The root of the problem is that the session image space is too small and it can't load any more drivers into it.  The session image space is shared for the display driver drivers and printer drivers.  rdpdd = remote desktop protocol display driver.

You can fix this bug by increasing the size of the session image space via a registry key.  Add the following key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

"SessionImageSize"=dword:00000020

0x20 == 32 MB works on my system anyway.
[right][snapback]409535[/snapback][/right]

This DID solve the problem. Thanks a lot!

[Drogen_Omen]

This problem is not specific to any one graphics company.  It can probably happen with printer drivers too.

The root of the problem is that the session image space is too small and it can't load any more drivers into it.  The session image space is shared for the display driver drivers and printer drivers.  rdpdd = remote desktop protocol display driver.

You can fix this bug by increasing the size of the session image space via a registry key.  Add the following key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

"SessionImageSize"=dword:00000020

0x20 == 32 MB works on my system anyway.

if that doesnt work try increasing the session memory size.

00000020 = 32MB
00000040 = 64MB
00000060 = 96MB (this one only seamed to work for about 10 mins and then connection would dropout)
00000080 = 128MB (this one worked for me perfectly)

[Menace]

Works for me as well. Thanks!
I did have to reboot the machine however.
XP SP3 and NVidia 8800 GTS.

[Calix]

Thanks a lot bandom rastard. You don't know how long I have been looking for a solution for this problem. After upgrading once to the 17x.xx series, even after downgrading, remote desktop was broken for me.

Drogen Omen, thank you for your tips as well. I'm using the 128MB one. However, I do have a question if you can answer it. Do you know if this is dependent on your video card ram? I have a 8800GTX 768MB card.

[Drogen_Omen]

Thanks a lot bandom rastard. You don't know how long I have been looking for a solution for this problem. After upgrading once to the 17x.xx series, even after downgrading, remote desktop was broken for me.

Drogen Omen, thank you for your tips as well. I'm using the 128MB one. However, I do have a question if you can answer it. Do you know if this is dependent on your video card ram? I have a 8800GTX 768MB card.
[right][snapback]440644[/snapback][/right]

Hey no problem mate.

i forgot to say restart after making the registry changes...

in regards to your question yes it does depend on ram size of your video card.

i have the same card as you (XFX 8800 GTX 768MB) and found that none of the other settings worked but as soon as i changed it to the 128 mmory allocation it worked.

i have since tried this registry setting on other machines with smaller cards ranging from Gforce 2 Pro 64MB RAM to 7900GTX 512MB and you can specify the 128mb one even if they are smaller.

also i dont think its a NVIdia issue... it seems to work fine nomater what video driver you have but as soon as you do the Windows updates and it updates the Remote Desktop to the new version thats when it stops working...

so make sure you point the finger at Microsoft... NVidia keep up the good work never had any issues with my Nvidia cards.

ATI rot in hell...

[Armchair Allstar]

I thought I should register for the forums and post b/c this thread saved me allot of troubleshooting.


I had around a year old Nvidia drivers on my system and remote desktop had been working flawlessly.

A couple days ago I upgrade to the latest released drivers (at that time) 175.19 and the remote desktop connections ceased to work. It would try to connect for a couple seconds then return to the initial window without error messages.

Yesterday (9/25/08) I read this thread then rechecked Nvidia's driver site and to my suprise 178.13 was released. I installed them, rebooted, and RDC functionality was restored!

Thanks all!

[Mavantix]

I too figured I'd register and record my input. This thread saved me a lot of frustration too.

I just installed fresh XP Pro SP3, and downloaded 178.13 WHQL XP which totally locked up my system (like freeze so bad numlock wouldn't even turn on/off) when I tried to RDP to the machine. No event log error messages. Would have to hard reset the system.

Downgrading to 169.21 resolved the issue. (I did not try the registry trick on page 4 before downgrading.)

Thanks all!

Motherboard: nForce4 (ECS KN1 SLI Extreme)
Video Card: GeForce 6600 256MB (XFX PV-T43P-UDS7)
OS: Win XP Pro SP3 (slipstream with nLite from XP2 CD)

[sullysnet]

registry fixed my issue, thanks but for some reason and I still can't figure it out my Nview settings for dual monitors stop working. For days or hours it is fine then boom my applications open across all monitors when maximized, I also loose controlling them. Felt I log off usually fixes it but usually takes a full reboot.

Using 163.75 it happens must less but fills my even log with

The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: NVIEW : iexplore: Shared heap exhausted or damaged, process ID 105c, total alloc:37a60....

[Appropri8]

if you don't know how to edit the registry maually, or don't want to here are the reg files required.

they are labeled acording to the size of the session image space.

if you don't trust me, i wouldn't, right click on the .reg file and click edit, you will see what it does.

P.S

i just need to say i love forums, i dont post much but everytime i have an obscure problem with my pc and i type it into google a forum comes to the rescue, not the manufacturer of the device or software thats playing up!

sorry for ranting on, i just need to get it of my chest, i'm so annoyed at microsoft for not addressing this problem and nvidia for the same.
people pay a lot of money for software and hardware, when it goes wrong you expect the people who sold it to you in an unfit state to fix it, not other people on the internet, who out their own good will go out of their way to fix it or you.

P.P.S

if i went to pc world and bought windows vista ultimate for £225, when it goes wrong, which it will, microsoft probably wont fix it for me so i'll end up back on a forum.
if i download ubuntu for free, when it goes wrong, which it also will, i'll be on a forum again.
i HATE game companies for not releasing their titles on linux, damn you for making me pay £225 for NOTHING!!! AARRRGHH!!!


i feel better now, sorry for going way off topic and making you read all of this.

This post has been edited by Appropri8: Dec 18 2008, 11:21 AM

Attached File(s)

 nvidia_rdc_fix.zip ( 1.42K ) Number of downloads: 60

 

[John Miller]

I have tried every available driver I can find for the NVIDIA GeForce 7600 GS and the registry edit for the SessionImageSize.
Remote Desktop does run as a process but there is no visible window.

Is anyone else still having trouble?

[charbeck]

I have tried every available driver I can find for the NVIDIA GeForce 7600 GS and the registry edit for the SessionImageSize.
Remote Desktop does run as a process but there is no visible window.

Is anyone else still having trouble?

I am running 180.48 drivers and am having the same issue. The SessionImageSize registry tweak did not help my situation either..

[Bungletron]

Hi

I searched for quite a while until I found this fix, 64mb SessionImageSize registry fix is working for me now. I am only a faux geek so can anyone explain what this registry hack actually does? For a start the line had to be added to my registry, what would the default value be? Is it in any way detrimental to my system performance otherwise?

Would be great to hear your thoughts,

Regards

Bungletron

[charbeck]

Hi

I searched for quite a while until I found this fix, 64mb SessionImageSize registry fix is working for me now. I am only a faux geek so can anyone explain what this registry hack actually does? For a start the line had to be added to my registry, what would the default value be? Is it in any way detrimental to my system performance otherwise?

Would be great to hear your thoughts,

Regards

Bungletron

I had to roll back to 175.19 to get remote desktop working again.

[vrapp]

NVidia now has an article about this in their KB:

Answer ID
2229
Last Updated
12/01/2008 04:29 PM

NVIDIA Software Development is aware of an issue where Microsoft Remote Desktop fails to load with driver version 169.61 or newer. NVIDIA and Microsoft Development are investigating this failure and will resolve the problem in the future. As a workaround you can import the following registry key using the Microsoft Registry Editor or install RDP workaround.reg attached to this article.

HKLM/System/CurrentControlSet/Control/SessionManager/MemoryManagement
"SessionImageSize"=dword:00000020

[charbeck]

NVidia now has an article about this in their KB:

Answer ID
2229
Last Updated
12/01/2008 04:29 PM

NVIDIA Software Development is aware of an issue where Microsoft Remote Desktop fails to load with driver version 169.61 or newer. NVIDIA and Microsoft Development are investigating this failure and will resolve the problem in the future. As a workaround you can import the following registry key using the Microsoft Registry Editor or install RDP workaround.reg attached to this article.

HKLM/System/CurrentControlSet/Control/SessionManager/MemoryManagement
"SessionImageSize"=dword:00000020

Doesn't work on my machine (nor does increasing to 64 or 128) - I have seen other people post that this did not help them as well.

Had to revert back to an older driver for Remote Desktop to start working again.

Boo to that.

[xannonite]

Increasing the SessionImageSize did not work for me. Instead I was able to resolve the issue by removing the /3GB switch as mentioned in this KB article:

http://support.microsoft.com/KB/942432

I tried increasing the desktop heap size to see if I could continue to use the /3GB switch, but it did not work. I ultimately had to remove the switch. Here are some articles on adjusting the desktop heap size:

http://blogs.zdnet.com/Bott/?p=269

http://blogs.msdn.com/ntdebugging/archive/...p-overview.aspx

[csdstudio]

^ Yup. Only by removing the 3GB switch could I get my RDP back up and running like before installing the new drivers.

So who's problem is this? Nvidia? MS?

8800GTX on XP SP3

[kniki123]

Hi,too glad i wasn't the only one suffering from this prob. By the way,any updates bout this? Still could't fix my prob. Hope to hear more suggestions. Thanks!



Regards,
kniki123
Placement financier

[Armchair Allstar]

Hi,too glad i wasn't the only one suffering from this prob. By the way,any updates bout this? Still could't fix my prob. Hope to hear more suggestions. Thanks!



Regards,
kniki123
Placement financier

I haven't had any problems with all the latest drivers. Right now I'm on 190.38. You may also want to try removing the desktop wallpaper.