BSoD when accessing PC through Remote Desktop

I have an Windows XP PC in my company that had some viruses.  When I tried to remote desktop onto that machine it would immediately get the BSoD.  I had the computer shipped here and managed to clean up what I could but it still gets the BSoD.  
Everytime I try and access the PC via remote desktop I get a BSoD with the following information:

"STOP: c000021a {Fatal System Error}
The Session Manager system process terminated unexpectedly with a staus of 0xc0000005 (0x7c80fd2d 0x002ef800).
The system has been shut down."

Can anyone assist me with this?

Thanks in advance.
LVL 1
homerslmpsonAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dfxdeimosCommented:
Try running from the command prompt:

"sfc /scannow"
homerslmpsonAuthor Commented:
Didn't work. I tried what you suggested and it took a while to finish but when it was done I rebooted and it will still blue screen when you try to access it remotely.
dfxdeimosCommented:
Well, this may not be the answer you want to hear... but sometimes it just insn't worth the time to troubleshoot the issue.

Backup. Format. Reinstall. Restore.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

homerslmpsonAuthor Commented:
Yeah that's what I'm probably going to do.
Thanks for your help.
dfxdeimosCommented:
Best of luck.
sk_raja_rajaCommented:
1.That error is typically due to bad RAM or a bad Windows driver.  Swap the RAM out for ones you know are good.  If you don't have any, try the diagnostic program at www.memtest.org, but there's a remote possibility that it will pass the test and still be bad.

To fix corrupt Windows drivers, you can do a repair install: http://www.dougknox.com/xp/tips/xp_repair_install.htm 

2.Try going to hardware device manager, and force to "disable" the integrated graphics controller. It should show up with a "disabled" signal over its icon...its definitely got to be your video card.

3.http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/XP/Q_22397953.html
georgestarkCommented:
two words "printer drivers" normally the problem
georgestarkCommented:
wish we could answer all desktop questions with this and get the points. LOL
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.