• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1036
  • Last Modified:

Remote desktop crashes remote computer

When trying to Remote Desktop to a computer (across a Cisco VPN connection) I get a black screen, the logon prompt never appears and it eventually times out and says broken network connection. After that the computer crashes - doesn’t respond to any more remote desktop connections and cant be accessed over the network - shared folders are inaccessible etc but it does respond OK to pings. The computer does not respond at the console either and has to be powered off/reset to recover. This problem is only affecting the Dell Precision T3500 workstations we have, OS is Windows XP SP3.

I thought that the problem might be the nVidia video card drivers. But updating the video card drivers just caused other problems with the displays.

Has anyone else had this problem?
0
dee_nz
Asked:
dee_nz
1 Solution
 
jambraunCommented:
I'm not familiar with the CISCO routers or else I'd have more troubleshooting tasks to add.  The switches aren't blocking any ports, aren't throttling information, and are set to communicate correctly, right?  I guess also, there are no issues with the ports?  

Another thing to try is turning down everything that requires more information to be transmitted, i.e. color depth, no audio, no local devices, turn off all the 'Experience' setting until you can verify they aren't causing issues.  Also change the speed tot he lowest speed for now.

Those are just some things to check.  You could also test the remote desktop connection with a secondary package like LogMeIn...just to see if it works.  
0
 
MikeIT ProfessionalCommented:
What kind of Anti-Virus or Anti-Spyware are you running?  Just for kicks, disable them, and see if you can connect....
0
 
dee_nzAuthor Commented:
Thanks for your comments.
Just to clarify remote desktop only crashes on the Dell Precision T3500 workstations. RDP is OK for all the other desktops & servers. I have tried these remote desktop connection settings - experience settings none ticked, no printers, no clipboard no sound and the workstation still crashed when I tried to remote desktop connect to it. Any other ideas?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
dee_nzAuthor Commented:
Just saw this in the event log on this machine, looks like the last error before it restart itself.

Event Type:      Error
Event Source:      nv
Event Category:      None
Event ID:      108
Date:            25/04/2011
Time:            9:31:30 p.m.
User:            N/A
Computer:      WORKSTATION27
Description:
The driver nv4_disp for the display device \Device\Video0 got stuck in an infinite loop. This usually indicates a problem with the device itself or with the device driver programming the hardware incorrectly. Please check with your hardware device vendor for any driver updates.
0
 
jambraunCommented:
I'm not able to verify this possible fix but a search I made for a similar issue involving a T3500 and an Nvidia card suggested a registry edit.  The page is in Italian so I had to do some translating:

http://babelfish.yahoo.com/translate_url?doit=done&tt=url&intl=1&fr=bf-home&trurl=http%3A%2F%2Fwww.google.com%2Furl%3Fsa%3Dt%26source%3Dweb%26cd%3D4%26ved%3D0CC4QFjAD%26url%3Dhttp%253A%252F%252Fantnotex.wikidot.com%252Fdell-precision-t3500-windows-problem%26ei%3Dum61TdqbNtOhtwfzyJnqDg%26usg%3DAFQjCNHJ5mcrDpSsrxk5x54b1DlTDRKq3Q&lp=it_en&btnTrUrl=Translate


DELL T3500 Remote Desktop Crash
link of reference:
http://computingondemand.com/?p=1141
link for the fix:
http://computingondemand.com/wp-content/uploads/2008/09/nvidiaregfix.reg

in order to resolve the problem it unloads the fix and you add to the registry
or manually:
Start->Esegui->Regedit
you go in
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager \ Memory Management
you add to value DWORD with name “SessionImageSize” and value 20

or it creates and it imports rows .reg with the following one contained

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager \ Memory Management]
“SessionImageSize " =dword: 00000020

It's worth a shot.  I don't think adding a "SessionImageSize" will break anything.  
0
 
jambraunCommented:
I would also see if there are any updated drivers or even previous versions of the drivers you could obtain and try for the video card
0
 
jambraunCommented:
...I really need an edit button.  Sorry for the tripple post.  You could also try replacing the video card and seeing if it works, just to officially narrow down the problem.
0
 
dee_nzAuthor Commented:
Hi again,
I started out trying to update the video drivers. Dell have no updated drivers available and when I used the latest NVIDIA drivers I had other problems with the display and Dell advised using their driver version. I’m going to raise a support case with Dell about this and will also try the SessionImageSize registry entry. Thanks.
0
 
dee_nzAuthor Commented:
Hi,
After much RDP testing the problem is not fixed. I had x2 of our T3500's crash when I tried to remote desktop connect to them last night.

Dell have suggested replacing the video card & motherboards - which is great because we have x8 of these machines!

Attached is the bug check analysis - looks like its still an nVidia driver problem.

Do you think its worth trying a SessionImageSize registry setting of maybe 16?
Any more thoughts?
-D

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\user\Desktop\machine\Mini050411-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Tue May  3 21:16:03.715 2011 (UTC + 12:00)
System Uptime: 5 days 1:16:04.031
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {8aadfb20, 8a79d6d0, 8a528a98, 1}

*** WARNING: Unable to verify timestamp for mssmbios.sys
Unable to load image watchdog.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for watchdog.sys
Probably caused by : nv4_disp.dll ( nv4_disp!NV4_WaitWhileVBlankActive+2 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 8aadfb20, Pointer to a stuck thread object.  Do .thread then kb on it to find
	the hung location.
Arg2: 8a79d6d0, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 8a528a98, Pointer to offending driver name.
Arg4: 00000001, Number of times this error occurred.  If a debugger is attached,
	this error is not always fatal -- see DESCRIPTION below.  On the
	blue screen, this will always equal 1.

Debugging Details:
------------------


FAULTING_THREAD:  8aadfb20

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  csrss.exe

LAST_CONTROL_TRANSFER:  from e151d010 to be035ff2

STACK_TEXT:  
a01e7a70 e151d010 00000001 00000000 be03e7ab nv4_disp!NV4_WaitWhileVBlankActive+0x2
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0xe151d010


STACK_COMMAND:  .thread 0xffffffff8aadfb20 ; kb

FOLLOWUP_IP: 
nv4_disp!NV4_WaitWhileVBlankActive+2
be035ff2 897c240c        mov     dword ptr [esp+0Ch],edi

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nv4_disp!NV4_WaitWhileVBlankActive+2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4949c2b5

FAILURE_BUCKET_ID:  0xEA_IMAGE_nv4_disp.dll_DATE_2008_12_18

BUCKET_ID:  0xEA_IMAGE_nv4_disp.dll_DATE_2008_12_18

Followup: MachineOwner
---------

Open in new window

0
 
dee_nzAuthor Commented:
Update:
Dell have released a BIOS update for the T3500s - A10 so have installed that.
I have change the registry setting for SessionImageSize to 16
Have tried the driver that Dell recommend and also the latest NVIDIA driver.
But remote desktop is still crashing these machines.
The video card has been replaced in one T3500 to see if that makes a difference..

Some more expert help please ;)
0
 
LeeTutorretiredCommented:
I've requested that this question be deleted for the following reason:

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
 
dee_nzAuthor Commented:
I would like to accepted jambraun's comment as the solution.
Even though problem is not fixed it is definitely caused by the video card drivers so would like to award points.
Thanks.
0
 
dee_nzAuthor Commented:
I would like to accepted jambraun's comment as the solution.
Even though problem is not fixed it is definitely caused by the video card drivers so would like to award points.
Thanks.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now