Remote Desktop Connect to Computer with Dual Monitors

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a desktop with a pci video card running dual monitors. The desktop
onboard video card had to be disabled to do this. If I try to remote desktop
connect (RDC) to this computer from another (compX), then compX will show the
logon. After filling out logon dialog, the RDC on compX will freeze. More
importantly, the desktop with the dual monitors will show the blue screen of
death. How can this be? Removing the pci video card driver and re-enabling
the onboard video card fixes this problem. Please let me know if there are
any setting I can investigate. Thank you.
 
It's been awhile since I saw this problem, but I know that RDC does not
support connnecting to a system with multiple monitors. It most likely has
something to do with the video card configuration. Can you post any details
about the blue screen error message?
 
Dear Mr. Vernon;

The interesting thing: took out dual video card, re-enabled on-board video.
Tried to remote desktop connect, same result: blue screen of death on
computer that had dual vid card. Manufacturer insists they can RDC at their
place on their computers. Here is the info on the blue screen of death:

Problem has been detected... windows shtting down to prevet damage.

If this is first time...

Check to be sure hyou have adequate disk space.

Check with your hardware vendor. Diable BIOS memory options such as caching
or shadowing...

Tech info:

**STOP: 0x0000008E (0xC0000005,0xF70A7491,0xF4A3DF9C,0x00000000)

**ialmhts.sys Address F70A7491 base at F7093000,Date stamp 43530732

Beginning dump of physical memory...

That's all it says. I have 20 GB free space on hard drive and 1 GB of RAM
on the system. I have nothing starting up program - wise. Any suggestions
would be appreciated. Thank you.
 
Slag

The 8E is a very common stop error. This indicates that a kernel-mode program generated an exception which the error handler did not catch. The 0xC0000005 parameter indicates that a memory access violation occurred. However, this does not help much in troubleshooting the problem. It could have been caused by a hardware incompatibility, device driver, or system service.

First, search for the file "ialmhts.sys" on the remote system. Once found, right click the file and select the version tab for information on what hardware this device driver belongs to.

Next, look for more error messages that might help pinpoint the problem.

Check the Event Viewer for possible errors. Go to start/Run and type eventvwr and press OK. Click the Application and System menu items on the left and look for any "X" error messages that coincide with when you last saw this behavior. If any are found, double click the error entry to see the details, click the Copy Icon on the right side of the details dialog screen (looks like 2 pages of text) and paste the error details in a reply to this message. You only need to post the text starting with Event Type: and ending with the Description:. You can omit the Data section.

ie:

Event Type: Error
Event Source: <source>
Event Category: <category>
Event ID: <ID #>
Date: <date>
Time: <time>
User: <user name>
Computer: <computer name>
Description:
Application <program>, <version>, <address>

Finally, Go to Start/Run and type msinfo32 and press OK. Click Components/Problem Devices to check for possible hardware device problems. If anything is visible in this window, copy the information and post it in a reply. (Press CTRL+A to select all, then CTRL+C to copy, paste the results in a reply.)
 
Dear Mr. Vernon;

Turns out, reapplying service pack 2 gave the same blue screen of death
errors. After getting sp 2 to be reapplied, the thing now works. Thanks for
thinking about it.

Sincerely,
 
Back
Top