• Guest, The rules for the P & N subforum have been updated to prohibit "ad hominem" or personal attacks against other posters. See the full details in the post "Politics and News Rules & Guidelines."

Video setting was reset every time login to a domain

mxnerd

Diamond Member
Jul 6, 2007
6,140
884
126
I have a PC with 785GX chipset (HD 4200).

It works fine if it's standalone machine in a workgroup. if I join the machine to the domain, the video card setting will be messed up and won't stick to the correct resolution 1680x1050. To say it more accurately, if the machine login the domain, the resolution is always rest to 800x600. If I want to reconfigure the resolution, there is no 1680x1050 resolution available , but 1600x1200 or 1600x600 and other weird resolutions, this is really annoying.

The Application Data or profile is not redirected to domain server at all and stays on local machine, I wonder what is causing this and how can I fix it. Have been removing and reinstalling video driver several times already and it didn't help.

Thanks.
 

VirtualLarry

No Lifer
Aug 25, 2001
51,917
6,882
126
That's pretty wierd, have you reported it to ATI?

Are you using RDP at all? RDP does wierd stuff with the video drivers.
 

mxnerd

Diamond Member
Jul 6, 2007
6,140
884
126
That's pretty wierd, have you reported it to ATI?
No. It just started yesterday all of a sudden. At first it was OK stand alone or login to the domain.

you using RDP at all? RDP does wierd stuff with the video drivers.
No.
 

mxnerd

Diamond Member
Jul 6, 2007
6,140
884
126
Seems that I fixed the problem.

I figured that probably the previous installed INTEL or NVIDA graphics drivers was affecting the system, so I uninstalled both.

After rebooting and several times login into the domain and looks like problem solved.

Really can't figure out why the PC worked OK for a while and all of a sudden was affected by non functioning video drivers? Oh, well.
 

mxnerd

Diamond Member
Jul 6, 2007
6,140
884
126
Actually removing INTEL or nVidia drivers did not fix the problem. Since the same symptom came back after a few times of reboots later.

Updated to newest DirectX Feb 2010 seems really fixed the problem this time.
 

ASK THE COMMUNITY