[goldeneye]

This is a very peculier problem that I have never come accross. This is only happening on a certain type of machine;- DELL OPTIPLEX 755's and in three seperate locations around our site there is only one 755 that this doesn't seem to be affecting.

What happens is when you log in as an administrator it seems to login ok then after a short period (seconds) and a couple of clicks (at which point an error beep occurs), then mouse freezes and will not move and you have to force restart to get back to login. Now the funny thing is that when you login under any other standard account, other than administrative, the computer works fine, no crashes no problems!!

We have tried deleting all profiles then logging in but with no joy. The only thing that works is a complete clone or by going through the Windows XP repair option, but even then this is only a temporary fix and within a week the computers were back there same state.......>!!!!!

Anyone come accross this or got any ideas because we're baffled?

Thanks

Gold

Edited by goldeneye, 16 February 2010 - 08:09 AM.

[Advertisements]

Anyone got any ideas with this, Am totally stuck???

[goldeneye]

Anyone got any ideas with this, Am totally stuck???

[dj.dom]

Which videocard is in the system?

We have exactly the same problem with two Optiplex 740 including a separate "RADEON HD 2400 XT" after installing some hotfixes of the .net-environment using WSUS. The systems also freeze under the standard-user, if You try to use the video-managementtools in the taskbar.
After updating the videocard-drivers, the problems were gone.

Please try to update the video-drivers and give a feedback...

greetings
dom

[goldeneye]

Thanks Dom

This worked for us. Downloaded the updated driver but once unzipped and the install begins you'll get an error saying setup did not find a compatible driver. This may be because its being installed via safe mode as this is the only way to access the system as ADMIN without it crashing. You have to go into computer management instead and update the driver that way. Once this is done the system works fine.

This is a weird one. We'd also done a .net 3.0 update not long before so this could well be the source of the conflict.

New one on me but all solved now.