Just upgraded to Vista 64. Second monitor doesn't work any more

Lum

Lum

Lum

Soldato
Joined
23 Nov 2008
Posts
3,283
Location
South Wales
Ok this is annoying, just upgraded to Vista 64 (formerly XP32) in anticipation of another 2gb of DDR3 that's coming my way and already I'm having problems.

When I reboot the system it comes back up with my secondary monitor disabled, and I can't even re-enable it in the normal way as doing so just immediately disables it again. I have to drop my main monitor down to 1024x768 (the resolution of the second monitor), apply it, then put the resolution back up and position it how I want.

If I log out and back in again it remembers the configuration but it will not survive a shutdown and restart.

This was a format+reinstall from SP1 media, so it's not any lingering bits of XP causing it.

So far I've tried disabling TMM and setting the iViewHelper registry key to 0, neither has had any effect

System specs:
Mobo: Asus P5E64-WS Evolution (X48, bios: 0701, intel inf driver: 9.0.0.1011)
RAM: 2x 1gb KingstonValueRAM (memtest86 says it's fine)
CPU: C2D E6750 (not overclocked)
Graphics: Powercolor 4870 (not overclocked other than the factory OC, driver: catalyst 8.11)
Hard drive: 2x WD 80gb thing in RAID0 (intel raid driver: 8.6.0.1007)
Primary monitor: Hazro HZ26Wi @ 1920x1200 (no driver available)
Secondary monitor: Samsung SyncMaster 152v @ 1024x768 (only 32bit inf available)
 
Last edited:
Latest gfx drivers? I run a very similar dual monitor setup under Vista x64 (a 24" Benq 1920x1200 and a 15" Samsung 1024x876) with an 8800GT so the o/s is more than capable.
 
Yes, Catalyst 8.11 are the latest drivers from ATI.
I've found a workaround though, if I use hibernate rather than shutdown, my config is remembered. Only problem is it keeps moving the monitor to the right rather than the left, and this can be fixed by disabling TMM, a service that's supposed to make multiple monitors easier to use by remembering your configuration.

If it's working with your nVidia card, then the conclusion is obviously that the ATI drivers suck, and also that TMM doesn't work properly either!
 
If you go into ATI's CCC and then go to display properties and then enable it that works for me. I find that I have problems with trying to enable it normally.
 
Tried that, have the same problem and need the same workaround to enable it, and it still forgets it when I shut down.

The hibernate trick will get me by for now (although Avira has just informed me it wants a reboot - grr) I dunno what they've done to hibernate on Vista but it's much faster, is it flushing the cache and only storing the bits of memory that have useful stuff in, or something? It'd be nice to see a solution for this. Do ATI take any notice of bug reports or should I just wait for 8.12 and hope it's fixed?
 
Not to really provide a solution, but just to confirm that I'm using Vista64 with dual monitors and an Nvidia card quite happily.

Might be worth hunting around some ATI forums?

Hmm, just re-read lokkers post. I'm using two identical 25" widescreen monitors at the same resolution, I've never tried two different monitors at different resolutions. That might be an ATI related problem?
 
Last edited:
just to add..

in work i'm running a hd2400pro in vista64 and it's been flawless since day 1 with dual screens, i just use the windows part, dunno if i even have ccc installed (can't remember)

suing cat11
 
Well given that when I resize my screen (first step in getting it to allow me to enable the second monitor) I've now noticed a little balloon pops up for a second saying the display driver ati2mdav or something like that stopped responding and was restarted.

Guess I have to wait until the 10th for Catalyst 8.12

In the meantime I sent a support ticket to ATI, got a reply 2 hours later telling me that display corruption is probably caused by overheating (yeah right, even Crysis doesn't put the card above 55 degrees). I seriously hope that was an automated reply because otherwise their support techies have even worse comprehension skills than Dell's!

Oh for bonus points, even with TMM disabled, when Vista comes out of screensaver, my Samsung monitor gets moved to the right of the Hazro, not the left where it belongs
 
Last edited:
It's most likely driver issues, so you've done the best course of action by contacting AMD. On a side note, I'm using a quad monitor setup, so Vista can definetly do dual :D
 
i thought tmm had to be enabled for dual screens as thats what gave support for the second screen... I think thats what i remember reading when i was disabling services on my htpc
 
Single 4850 1Gb (8.11 cats), vista 64 and two monitors at different resolutions and no problems like that. Just the occasional bluescreen from the atikmdag.sys.
I have the CCC installed, but used windows to set up the dual displays.
 
4850 512MB on 8.11's here and identical 22" monitors, no problems here. So not an ATi problem. And as for the post above, I've never had a bluescreen because of ATi
 
The key point there is identical monitors. I have to drop my primary monitor to an equal or lower resolution than the second (which also causes atikmdag to stop responding and need a restart) before I can enable the second one.

If it's not an ATI problem then what is it? Currently they're trying to blame my motherboard because the P5E64 WS Evo isn't on the Microsoft certified list and they want me to replace the motherboard before they're prepared to investigate further.

Edit: it is on the certified list, they didn't just read past page1 of the Asus search results, it's listed as "P5E64...." not "Asus P5E64..." so is nearer the end. This is fantastic, I wonder what their next excuse will be?

I have a crappy old PCI Radeon here, maybe I should install that and run my second monitor off it? You can't do dual monitors with a combination of ATI and nVidia on Vista can you?

Edit2: hahaha, they pointed me at this knowledgebase article which once again blames everything but their hardware, but then states "If you have this issue and can reproduce it on command, it is not random or intermittent, please collect the following information to submit to us." (msinfo, dxdiag etc.) so they're still not off the hook.
 
Last edited:
Am running an x1950pro here with two screens, a Samsung 20inch at 1680x1050 and a digital photo frame with a resolution like 700x400 with no problems save that Samurize won't open on the correct screen. The Samsung is connected via DVI and the Digital Photo Frame is connected via S-Video. Perhaps try different Catalyst Drivers or poke around in the CCC to see if there's some strange setting or something ticked. Also running Vista 64-bit as well.
 
Well since the Catalyst 8.12rc3 release came out today I thought I would give it a whirl.
Uninstalled the old drivers, rebooted, installed the new drivers, it comes up and both monitors are active, and it's even remembered that my second monitor is rotated... awesome!

Then I realise that my main monitor has been set to 1680x1050. I set it back to 1920x1200 and reboot just as a curiosity and we're back to one monitor and the ATIKMDAG stopped responding error part way through the process of enabling the second one.

Still at least it doesn't lose the position of the second monitor when coming off the screensaver any more.
 
hi ...

ATI HD4870/512
Dell 24" @1900x1200 & Sony 19" @1280x1024

Running Vista64 sp1
cat drivers 8.10
ultramon 2.7.1

np running both monitors m8
 
Update.

Upgraded to 8.12 didn't fix the problem, did fix the ATIKMDAG crash though.

What has fixed the problem is disabling the "Reduce DVI frequency on high resolution displays" option. With that unticked the monitor configuration seems to work fine, unfortunately I need that option ticked as my primary monitor is a Hazro and thus suffers from artifacts if you don't tick it.

My assumption is that this option switches the signal to use the CVT Reduced Blanking timing standard which only really works with digital displays. My secondary monitor is a 1024x768 "analogue" LCD ie. VGA only and detected as a CRT by ATI and thus ATI will want to run it with standard timings. Perhaps the driver is unhappy about starting up with one monitor running reduced blanking and the other running standard.
 
You must log in or register to reply here.
Back
Top Bottom