I am having an issue with 2 OptiPlex 380's (Possibly a 3rd, its still in the box).
The issue is, the computers are set to never go to sleep, the only thing that is set is that the display is supposed to shut off after a certain time.
After the monitor shuts off I will move the mouse to get it to come back on, and it starts freaking out. Any windows that are open start flashing and everything says 'Not Responding', I am unable to open up the task manager I just have to wait until it stops. In cases where the monitor has not been shut off for a while it usually comes back to normal after about 30 seconds, but in some cases it never comes back and I have to reboot the computer by pressing the power button. Sometimes the following error is in the event log.
Log Name: Application
Source: Application Hang
Date: 12/8/2010 4:57:59 PM
Event ID: 1002
Task Category: (101)
The program explorer.exe version 6.1.7600.16450 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 1330
Start Time: 01cb9729c20f9b75
Termination Time: 561
Application Path: C:\Windows\explorer.exe
Report Id: 8c6bda2c-031e-11e0-b84b-f04da2294608
<Provider Name="Application Hang" />
<TimeCreated SystemTime="2010-12-08T22:57:59.000000000Z" />
I have verified that it happens when the monitor shuts off because I changed the time to 1 minute and it does it every time, If I set it to never shut off it works fine. However that is not a solution, nor should it be for brand new computers.
Tonight I am going to try install the video driver from the dell website and see if that fixes anything.
Another thing I noticed is I went into the BIOS and set the standby mode from S1 to S3 (it might be the other way around I cant remember, the one I changed it to was the one that used more power and would resume faster) After setting this option when the monitor shuts off, nothing I do can make it come back on, I have to reset the computer to get it back on. The second computer does this from time to time, I haven't checked what the BIOS is set to for that.
I talked to Dell support over web chat and they told me to power cycle the computer by removing the power cord and holding the power button for 10 seconds and than reloading the defaults in the BIOS, however this did not work.
I will be setting up the 3rd computer today and I am guessing this one will do the same thing.
I am hoping that installing this drive will fix it but I am not holding my breath.
Any ideas or suggestions?
What specific monitor model?
What ports on the monitor and PC are connecting the two?
Are there any other cables going from the monitor to the PC?
This is from the System Config page on the Dell support site
FLAT PANEL DISPLAY..., 1909WB
The monitor was connected with a DVI cable to computer. The only other cables were the power cable, and the USB cable.
I switched the cable to a VGA and I have not noticed the problem now, however if I were to use DVI the problem continues.
On the other two machines, they are setup using DVI, after the monitor shuts off and sits idle for a period of time, there is nothing I can do to get it to come back other than powering off the PC and starting over again. I am guessing that by switching to VGA this will solve the problem, however, we should be able to use DVI.
This seems to be happening across a wide array of our Optiplex 380's, about 5-10 out of 100 systems experience this issue. All are on DVI, all are Dell Monitors.
A05 bios and the newest Intel graphics driver from support.dell.com posted 4/1/11 seems to have made it better on SOME but not all systems.
Support is worthless and suggests replacing motherboard and reinstalling the operating system, both "fixes" the problem still happens.
I would like to join in to this quire of complaints...
I have one Optiplex 380 which worked fine when it was connected to a Dell / E198 FP 19" TFT. Then suddenly I changed to a Dell / P2310Hc monitor and boom, I've got the same symptoms as you all.
Should I interpret your post Xponentia that regardless of the "fixes" (replacing motherboard and reinstalling OS) the problem still occurs?