Monitor goes dark then returns, mouse cursor freezes afterwards

[videobruce]

This isn't going to be easy to describe, but here goes;

I believe it is a thermal problem with the video card, but I'm not sure. After the box has been on for 30-60 minutes (or so) the monitor goes dark for a second then returns. This happens a few times and if it really gets bad (more frequent) the dark periods get longer that the monitor goes into standby mode then returns with the mouse cursor frozen that I have to reboot to get it back.

I know it's not the monitor, it's the video card not sending a signal to it and somehow also locking up the mouse (keyboard is ok).

This happened after installing S/W for a HP S20 photo scanner, BUT I don't think that is the problem because on my other bootable drive (in the same box) the problem is there but not as bad. It might be making it worse, but I don't think it is that easy. I'm also not sure it is the card itself, though it is the card that is not sending the video signal to the monitor.

Before I swap cards, anyone have any ideas? Here is the system:

Win 2k w/sp3
Epox 8RDA nForce 2 MB (latest bios and nForce 2 UDP)
AMD 2100b
2x256MB Corsair PC2700
Saphire ATI Radeon 9100 (latest ATI driver)
HP S20 scanner
Kodak DVC 325 camnera
Creative PC-Cam 600
SB Live value
Antec 330W Tru Power PSU

Device Manager ok
No viruses

I have pulled and reseated the video card, memory, processor (added a little more compond).
I have not overclocked anything.
No overheating apparent on processor or video card.

As I write this the system has been on for over 2 hours without a single incident (so far).

[Sylvander]

I don’t think it’s your video card that’s at fault.

This is a software problem.
I’m not sure about Windows 2000, but normally the mouse uses a 16 bit programme. When the cursor freezes it means some other 16 bit prog has hung and because ALL 16 bit prog’s use a communal message queue, all the other 16 bit prog’s sit waiting their turn at the processor, which never comes.
Since ALL 16 bit prog’s are affected, you will see some strange things happening, all related to the fact that all 16 bit prog’s running unseen have halted.
Someone will now say this is nonsense; that Win2k uses a totally different system. Check it out.
Can Win2k run in safe mode?
If so you should see no problem there.

In Windows 98 I would go to:
“Start>Programs>Accessories>System Tools>System Information>Software Environment>16-bit modules loaded”.
In my list one of those is my “Super VGA Display Driver”.
I’m surprised you get any display at all.
Perhaps the O/S disables unnecessary 16 bit prog’s to protect the display, the mouse being one of them [or the cause of the problem].
Tracking down the culprit will not be easy methinks.
If you had a backup [of the C: drive] taken before the problem was introduced you could re-format and restore the C: drive.
The alternative is to use something like “msconfig.exe” to track down the software that includes the troublesome 16 bit module.

Check this out http://support.microsoft.com/default.aspx?scid=kb;en-us;309055

[videobruce]

The hanging is only for a second after the display returns. It is only after repeated 'blackouts' (one right after another) that the cursor hangs for good.

Anyone else have input on this angle??

[Sylvander]

My monitor goes black quite regularly.
It’s set to do so after 10 minutes of inactivity.
I have no screensaver set.
Is yours set to shut down after some period of inactivity?
What if the programme attempting to shut down your monitor is 16 bit and it’s hitting trouble and the shut down aborts and the display comes back.
After every set period of inactivity it makes a fresh attempt and fails yet again.
Perhaps by chance it eventually affects the mouse [both being 16 bit prog’s].

Could I suggest that you allocate sounds to the “Open Program” & “Close Program” events in “Windows” “Sounds”.
[I use a beep and a whoosh]
When this unfortunate “event” occurs you may hear the “sounds” associated with the opening and closing of a program.
This would tell you that more is happening than first appears.
If you hear a beep [or whatever] and the screen goes black; then a whoosh and the image returns, you know this is not by chance, but is under the control of a program.
I have this going all the time and you’d be surprised at what goes on in the background.

You could also try running “System Monitor” to study what’s happening.
It’s in “Start>Programs>Accessories>System Tools”.

[Budfred]

I agree with Sylvander to check what is running background and see if anything is interfering. I would start with the programs associated with the new scanner and shut them off in msconfig to see if it makes a difference. I would also check power settings to make sure there isn't anything going on there that is interfering.

The other thing that occurred to me is that this could be due to an overly ambitious refresh rate for the monitor. Have you checked that?

To check for an overheating video (sounds unlikely), have a small desk fan blow air over the video card while you are working and see if the problem recurs.

Longshot options include: power flucuations, spyware glitches or failing monitor.

[videobruce]

Power time for the monitor is 45 minutes as I always set it for.
I have 15 processes (services) running at startup all but 2 are M$. The non M$ are MBM and a capture card .exe

The only change before this started to happen is the addition of the software for the HP scanner, but on my other bootable drive it does it also after I uninstalled the software (I shouldn't of installed it in the first place since there are 5 or 6 enum registry entries that are still there.

It's not the monitor since thew mouse cursor does freeze a second after the video returns.

The setup I have been running has been the same for a couple of months except for a HDD change other than the scanner addition.

Voltages from MBM look good, stable as a rock:

1.6
2.62
4.97
11.86

CPU 100F (air temp of board under CPU)
MB 85F

I'm just trying not to swap AGP boards if I don't have to.

[videobruce]

Update........

I swapped the video card and removed the scanner software including deleting enum registry entries that were left behind and the problem is still there.

Now.......is it the processor, MB, PSU or coruption left over from the software install of the HP scanner??

[Budfred]

Have you checked the refresh rate and run a spyware scan? The only other thing I can think of that might do something like this is a RAM problem. You might want to run DocMem to test your RAM....

[videobruce]

I think it's the processor. I ordered a 1.7 OEM w/ a optional 1 yr warrenty from Newegg for $49 delevered as a spaer since I don't have one and if it is the processor I will send the 2.1 back for replacement.

Spyware??? I don't use OE, IE or XP either.
Isn't that the only spyware out there anymore???

All of this is 3 months old and I did memory scans when it was new, but I could do another one. I did within Windows, but I will use Memory Test and DocMemory with a floppy and see.

[Budfred]

I don't use IE, OE or XP either, but I have to delete spyware regularly. If you connect to the internet, you will have at least attempted spyware. As a matter of fact, even if you don't connect, some software comes with spyware installed. I have a game program that won't run if I delete the spyware that came with it. Since I never connect to the internet when I am playing the games, I left the spyware there, but it is designed to let you play online while it quietly transmits data to the originator of the software.