Which was the bigger waste of money...?

[Fumz]

There's no need to reformat... just find the 64-bit version of your driver.

This is what my search produces on that link:

Product Support Information



http://www.p4c.philips.com/cgi-bin/....143&slg=ENG&submit.x=0&submit.y=0&print=true
No search results found. 'driver'.

 

[RaIo]

Yes, I can't find it either. That site's pretty but useless...

I reformatted by the way, I didn't have anything installed aside from the essentials - but the result is the same. And this time I haven't installed anything monitor related.

It's the same story, even with the generic driver that Windows has - after a restart I have to adjust the resolution, and then reject the new settings for it to be displayed properly.

So guess I'll have to live with this... :huh:

 

[Mr GRiM]

I had a windows update Display driver that installed about a week ago and I was getting BSOD and screen freezing at random intervals.

At first I first thought maybe I was overclocking to high so tried turning it down a bit but that didn't help, then I remembered the update and wondered if that was my problem so I reinstalled the latest Nvidia update that I had and everything was fine again. Had me a bit worried for a bit that something major might have happened, I don't think I will use windows update for updating my display drivers again.

 

[RaIo]

This is clearly a compatability issue - the hardware is fine (monitor, GFX card and everything else), the drivers are all updated to the latest available, and tried various methods to get Windows to play along, but I think I've done everything I can for the time being.

Less than impressed to be honest, considering the hardware and software are from pretty big companies. You'd expect them to make something and ensure it'll work. Looks like I'll have to automate the process of adjusting the resolution following a reboot as a less than ideal option.

Thanks for trying to help though.

 

[Mr GRiM]

You have probably tried this but did you try the nvidia control panel setting the monitor to its native resolution.

 

[RaIo]

I don't have that option available...? And I'm not sure why I have that CRT option there, 'cause I have an LCD monitor.

 

[Mr GRiM]

Do you use a DVI cable or VGA cable connected to your monitor, I ask because I don't get the proper screen resolution with VGA, DVI is much better and computer will recognise the native resolution of your monitor with that cable.

 

[Fumz]

... I reformatted by the way, I didn't have anything installed aside from the essentials - but the result is the same. And this time I haven't installed anything monitor related.

It's the same story, even with the generic driver that Windows has - after a restart I have to adjust the resolution, and then reject the new settings for it to be displayed properly.

This is clearly a compatability issue - the hardware is fine (monitor, GFX card and everything else), the drivers are all updated to the latest available, and tried various methods to get Windows to play along, but I think I've done everything I can for the time being.

Less than impressed to be honest, considering the hardware and software are from pretty big companies. You'd expect them to make something and ensure it'll work. Looks like I'll have to automate the process of adjusting the resolution following a reboot as a less than ideal option..

Again, if Windows Update only has the bad driver, then that's what it's going to give you. On the re-install, you can't yet disable Windows Update, so it might very well be updating that bad driver. The only way to get around this is to re-install with your ethernet unplugged, that way Windows won't be able to do any of the silent updates.

Go to the device manager and expand Monitors. Right click on you monitor and select properties, then driver. If the driver provider says Samsung, then indeed you have been updated silently, which is what I suspect is going on here.

If it were me, I'd do one last re-install. First grab SP1 and save it somewhere... another drive or burn it to DVD...then re-install with your ethernet unplugged and load SP1.

 

[RaIo]

It was the cable.

On my XP rig, I connected the monitor and card using my old cable, that is to say a DVI-D cable. The monitor came with a VGA cable, and that's the one I was using to connect it to my new rig. I switched cables and that fixed it. Seems a bit retarded of Philips to give me a cable that only supports up to 1600*1200 when the monitor's native resolution is 1680*1050, but hey...

So to answer my initial question - which one was the bigger waste of money? Answer: Neither.

Thanks again for all the help guys, really helped a lot - I was running out of ideas here.

 

[Mr GRiM]

Your welcome mate glad you got it sorted.

 

[wysiwyg]

In your first post you said you select no to keep the settings.
Try selecting yes to keep the settings.

Err... no, not quite. After I calibrate the monitor, and save the settings, Windows shows the display as being 1680*1050. That's cool. It displays properly, until I restart, then it "defaults" to the factory settings (i.e. uncalibrated). When I check the settings after the restart it still shows 1680*1050, though it's clearly not, because the image is distorted, fuzzy and out of proportion. To get it to display properly, I have to go to the Personalize or nVidia control panel, to modify the display ,and then click Apply. After it changes the resolution (doesn't matter to what), I select No, for it to default back to 1680*1050 and -then- it displays like it's supposed to.

Check Microsoft site for updates for your monitor, I had the same problems with my previous monitor.