Peak-Support
asked on
Win XP Pro crashes or freezes on RDP
I have a Windows XP Professional PC that I want to RDP into from another machine. It allows me to get to the login screen but as soon as I put in the credentials the XP Pro PC I am remoting into either crashes with a BSOD or just locks up.
I have attached the Minidump file with xml and txt.
It does not matter whether I RDP from a Windows 7 PC or a Vista PC - I have tried 3 different PCs as the client and get the same result on the server. If I do not RDP into the box it operates fine without problems. minidump.zip
I have attached the Minidump file with xml and txt.
It does not matter whether I RDP from a Windows 7 PC or a Vista PC - I have tried 3 different PCs as the client and get the same result on the server. If I do not RDP into the box it operates fine without problems. minidump.zip
joeyfaz
I'm willing to bet it's some sort of Driver issue. Check Device Manager and see if there are any missing or outdated drivers.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Who Crashed Analysis
On Fri 9/30/2011 2:43:59 AM GMT your computer crashed
crash dump file: C:\Users\Desktop\minidump\
uptime: 00:03:30
This was probably caused by the following module: win32k.sys (win32k+0x9BC00)
Bugcheck code: 0x1A (0x4128B, 0x5820, 0x0, 0xFFFFFFFFBF400000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\win32k
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Fri 9/30/2011 2:43:59 AM GMT your computer crashed
crash dump file: C:\Users\Desktop\minidump\
uptime: 00:03:30
This was probably caused by the following module: win32k.sys (win32k+0x9BC00)
Bugcheck code: 0x1A (0x4128B, 0x5820, 0x0, 0xFFFFFFFFBF400000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\win32k
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
ASKER
The PC is on-site at a customers and cannot be replaced. I am trying to arrange a time that I can get access this PC and then will post back. I will try the suggestions of changing the following drivers: Network, Graphics, Chipset.
Thanks.
Thanks.
ASKER
Updating Chipset, Network and Graphics fixed the issue - not sure which one was the cause.
The BSOD reported faulty drivers. I awarded points as I did because these people suggested specific drivers to try.
The BSOD reported faulty drivers. I awarded points as I did because these people suggested specific drivers to try.