Unhandled Exception when executing via RDP (OK when local)

I have recently put together a new development machine and loaded Windows 7 64 bit and VS2010.

I copied over all my projects (VB) from the old machine which was Windows 7 x86 and VS2008.

After following the conversion wizard in VS2010 and installing a third-party component I had forgotten about, my solutions opened and executed fine on the new machine.

Then I tried to work on one of my projects via RDP from a Windows XP machine (something I have done many, many times with the old machine) and the project crashes when run. I get the "no source availiable" tab and an AccessViolationException as soon as the splash screen has loaded. Going back to local operation, the project runs fine.

I've Googled this one to death and I can't find anything that relates to this problem at all. Any sugggestions would be gratefully received.

Thanks.

I do have multiple monitors but have never had a problem before with RDP. Anyways, I found other problems when opening other, older, projects in VS2010 so I uninstalled and reverted to VS2008. All OK now. Thanks for your help.

I was having an issue running Visual Studio 2010 via RDP where the IDE contents except the Solution Explorer wouldn't render. I went to Options->Environment->General->Visual experience and turned off the the "rich client visual experience" options. I suspect turning off "Use hardware graphics acceleration if available" did the trick.

I had also problem with RDP working in "windows 10" My connection other computers always run successful, but closing after 5-15 second. I very long try fix this error. And I open this exception in VS2015 and read full excaption:

Unhandled exception at 0x00007FFBE35A8283 (ntdll.dll) in mstsc.exe: 0xC0000374: Куча была повреждена (parameters: 0x00007FFBE35FF6B0).

At first I thinked my PC have truble with RAM memory, but I decide change RDP settings and it began work without problem. I changed the picture quality and uncheck using printer in other window. My rdp workin very nice now. I tried many fixes From the microsoftware, with updates and system files, but nothing helped. I am writing now if someone with the same collision can solve temporarily the problem by lowering the quality of the picture. On a remote computer, it may be very important to simply connect, especially if it is a server.