XP SP3, accessed via RDP from Win7 (both on home intranet)
RDP has worked fine, for 2 years, until today. RDP connection went BSOD { STOP 0x0000007E (0xC0000005, 0x00000000, 0xAE0531A8, 0xAE052EA4) } on trying to paste a file, copied on Win 7 computer, into Win XP file explorer. Had done about 2 hours of work in same RDP session before this happened, without issue.
After rebooting XP, tried to copy from XP computer...but Win 7 drives not mapped (they usually are). When RDP'd into XP, random clicking inside file explorer cause sBSOD (same hex codes, except last two, which change slightly). Otherwise fine.
Win XP --- direction connection, *not* RDP --- seems completely OK.
Minidmp file says rdpdr.sys as the culprit; BlueSreenView output:
rdpdr.sys rdpdr.sys+13f18 0xb821f000 0xb824ee80 0x0002fe80 0x480251d2 4/13/2008 2:32:50 PM
Worried that this is a seemingly very old rdpdr.sys, I tried to update it -- several Windows KB articles mention updates, but the only available MS download failed (after MS emailed me the zip file, the file wouldn't unzip properly...asking for next disk!!). I tried to use a new rdpdr.sys from opendll.com, but it was automatically removed (!) after I put it in C:\windows\system32\drivers (after renaming existing file to rdpdr.sys.old). I think the opendll.com version is 64 bit, which wouldn't work anyway with XP...
But all this seems very, very strange. It was working, for several years, with daily use...and suddenly went bad.
Any ideas??
Thanks
P.S. - WinXP is up-to-date (ran sysupdate after BSOD; previous update had been ~2 months prior). Avast! AV installed and up-to-date (in use for ~1.5 years, last update to program & virus defs *yesterday*).
P.P.S. - I'd attach the minidump file, but don't see how to do that here...
RDP has worked fine, for 2 years, until today. RDP connection went BSOD { STOP 0x0000007E (0xC0000005, 0x00000000, 0xAE0531A8, 0xAE052EA4) } on trying to paste a file, copied on Win 7 computer, into Win XP file explorer. Had done about 2 hours of work in same RDP session before this happened, without issue.
After rebooting XP, tried to copy from XP computer...but Win 7 drives not mapped (they usually are). When RDP'd into XP, random clicking inside file explorer cause sBSOD (same hex codes, except last two, which change slightly). Otherwise fine.
Win XP --- direction connection, *not* RDP --- seems completely OK.
Minidmp file says rdpdr.sys as the culprit; BlueSreenView output:
rdpdr.sys rdpdr.sys+13f18 0xb821f000 0xb824ee80 0x0002fe80 0x480251d2 4/13/2008 2:32:50 PM
Worried that this is a seemingly very old rdpdr.sys, I tried to update it -- several Windows KB articles mention updates, but the only available MS download failed (after MS emailed me the zip file, the file wouldn't unzip properly...asking for next disk!!). I tried to use a new rdpdr.sys from opendll.com, but it was automatically removed (!) after I put it in C:\windows\system32\drivers (after renaming existing file to rdpdr.sys.old). I think the opendll.com version is 64 bit, which wouldn't work anyway with XP...
But all this seems very, very strange. It was working, for several years, with daily use...and suddenly went bad.
Any ideas??
Thanks
P.S. - WinXP is up-to-date (ran sysupdate after BSOD; previous update had been ~2 months prior). Avast! AV installed and up-to-date (in use for ~1.5 years, last update to program & virus defs *yesterday*).
P.P.S. - I'd attach the minidump file, but don't see how to do that here...