Re: ntvdm.exe

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Jeffrey Randow (MVP) (jeffreyr-support_at_remotenetworktechnology.com)
Date: 06/10/04


Date: Thu, 10 Jun 2004 00:04:04 -0500

Glad that solved your problem... :)

Jeffrey Randow (Windows Networking & Smart Display MVP)
jeffreyr-support@remotenetworktechnology.com

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

On Tue, 8 Jun 2004 08:28:23 -0700, "Rob Phillips"
<anonymous@discussions.microsoft.com> wrote:

>Good morning, all,
>I just wanted to share a little FYI I finally figured out.
>I had placeda question on this board a few times whereas I
>was looking for help to determining the cause of ntvdm.exe
>to be spiking my CPU while using remote desktop. No one
>seemed to know what caused it, or didn't answer the post.
>In either case, I have determined it was the screen saver
>of the host PC causing the ntvdm.exe to use 90% of the CPU
>during remote sessions. I tried to change the screensaver,
>but instead, that screensaver would over-use the CPU. I
>have opted to disbles screensavers altogether on the host
>PC prior to connecting to the host PC. This has not only
>stopped the CPU issue I was having, but has increased the
>speed at which remote desktop refreshes and function at
>the client PC. Hope someone else can find some use in this
>information.



Relevant Pages

  • ntvdm.exe
    ... to be spiking my CPU while using remote desktop. ... of the host PC causing the ntvdm.exe to use 90% of the CPU ... that screensaver would over-use the CPU. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Screensaver timeout resets
    ... Panel->Display->Screen Saver Timeout. ... Jeffrey Randow (Windows Networking & Smart Display MVP) ... >screensaver set to kick in after 55 minutes of inactivity. ... >timeout always changes to 10 minutes after using Remote Desktop. ...
    (microsoft.public.windowsxp.work_remotely)
  • 3D Screensavers Cause Hardware Damage!
    ... Through a long and costly process of puzzling hardware failures I ... Windows Task Manager and monitor your CPU usage. ... screensaver other the 3D ones listed. ...
    (microsoft.public.win2000.general)
  • Re: 3D Screensavers Cause Hardware Damage!
    ... > Through a long and costly process of puzzling hardware failures I ... > Windows Task Manager and monitor your CPU usage. ... > screensaver other the 3D ones listed. ...
    (microsoft.public.win2000.general)
  • Re: d3dsaver.cpp
    ... The important thing is to make sure the screensaver doesn't use so much CPU ... I substituted normal priority and use IDLE ... > only while the D3dX sprite is offscreen. ...
    (microsoft.public.win32.programmer.directx.graphics)