way to FORCE my system to use 1920 x 1080 x 32 @60Hz

[amiga5k]

I have a similar issue with my Samsung 2233SW: Sometimes when my system boots up, my screen resolution is wrong (It defaults to "Non-Pnp VGA Monitor" or something similar) and the highest resolution I can choose, even in advanced/list all modes is usually 1600 x 1200, which just looks weird in widescreen. If I reboot once or twice it will suddenly "fix" itself and recognize the Samsung properly.

When I first installed Windows 7, I did not install the driver from the Samsung disk, because it already correctly recognized it and all of its supported display modes. However, when I first had this problem, I decided to go ahead and install the driver from the disk and it helped... for about a week, then started doing it again. I also do not have CCC installed, but when I installed it, it didn't seem to help, since it will not allow me to select modes that it thinks are not supported by my "VGA" monitor.

So.... is there a way to FORCE my system to use 1920 x 1080 x 32 @60Hz, even if it thinks my monitor can not support it?

Thanks in advance!
Russell

p.s. I even re-installed Windows 7 because I thought that would get rid of the problem, but it soon re-appeared. It seemed to start after one of the updates, but I don't know which one (You can imagine how many megabytes of updates got downloaded upon a fresh install of Windows 7!). Probably the ATI update?

 

[sygnus21]

You need to look at two things here - video card drivers and monitor drivers. Please make sure you have the latest drivers for both.

You can get the latest video card drivers for your card here - ATI Video Card Drivers

Samsung monitor drivers here - Samsung

Also according to this the native resolution of that monitor is 1920 x 1080 so it should be defaulting at that res - http://www.samsung.com/us/system/co...kfvza/CreamMonitor_Datasheet_HR_Final_908.pdf

Let us know.

 

[amiga5k]

I have the latest on both. I'm wondering if the latest driver isn't the problem itself! But even if I have a non-optimum driver, it still doesn't make sense to me that the issue happens only sometimes, and that a simple reboot without doing anything else usually solves the problem. Isn't every Win 7 startup loading the same drivers?

Weird!

Russell

 

[sygnus21]

Yeah it is weird. I'd try reinsatlling the video drivers. Also what cable are you using to hook up the monitor?

Also check your device manager to see if there are any issues reported, i.e question marks or yellow triangles.

 

[thefabe]

Did you try driversweeper to remove all residual drivers before you re-installed your GPU driver?
http://downloads.guru3d.com/download.php?det=1655

Just a thought

Fabe

 

[sygnus21]

At this point in time I'd advise against using drive sweeper, for the time being.

 

[thefabe]

At this point in time I'd advise against using drive sweeper, for the time being.

Reason being so I know?
Fabe

 

[sygnus21]

Start with the simple by checking to make sure settings are correct. It could turn out to be a simple cable or setting problem.

 

[thefabe]

Agreed.

Fabe

 

[sygnus21]

We'll see what he has to say about my question of the cable. It may turn out that he does need to repair his drivers, and your solution may come in handy, but we need to keep it simple first.

BTW thanks

 

[stormy13]

At this point in time I'd advise against using drive sweeper, for the time being.

Reason being so I know?
Fabe

Another is that you linked to the old version, the latest is 3.2, and even it has problems (just check the Driver Sweeper forums). There are others as well, but I have explained them in other threads.

 

[amiga5k]

The monitor has two inputs: DVI and RGB. I have it connected to the video card (ATI 4850HD) via the RGB. On the video card end, I use the adapter that came with the video card which converts RGB->DVI (I'm guessing).

What leads me to think that it is a Windows Update related problem is that I had no problems with the video mode for the first full year that I had it set up this way. It wasn't until a Microsoft update about 2 or 3 months ago that I began to have problems, and only intermittently. Even through the RGB port (and adapter) the monitor is recognized correctly as a Samsung Syncmaster with the correct display capabilities, so I can't see how it could be a communication error with the monitor.

Would it be worth it to invest in a DVI to DVI cable? (The only reason I didn't up to this point is that as-is the picture quality is fantastic). Couldn't hurt I guess, eh?

Russell