LOOK: Vista/Win7 and 5040x1050?: FIXES IN 1st POST!

bsoder · Post by **bsoder** » 09 Jan 2009, 00:31

Awesome, works for me as well. The monitors report 62.7kHz 59Hz PN now. :)

P-Storm · Post by **P-Storm** » 09 Jan 2009, 01:39

thorvald, could you write a major warning in your post. If you write something wrong, than it could damage your monitor (like having a too high refresh rate and things like that)

thorvald · Post by **thorvald** » 09 Jan 2009, 03:52

thorvald, could you write a major warning in your post. If you write something wrong, than it could damage your monitor (like having a too high refresh rate and things like that)

Done!

icxnamjah · Post by **icxnamjah** » 09 Jan 2009, 10:55

Hello, I have three dell 20 inch monitors, the generic kind not the ultrasharp series.

I have tried everything.

I am on 32 bit vista running 177.41 drivers with the previous powerdesk software.

After updating the drivers and downloading the new powerdesk, using the software I tried setting the resolution to 5040x1050, but the screens go black and I am forced to restart and go into safe mode to remove the nvidia drivers and powerdesk.

After re-installing the 177.41 drivers and the previous powerdesk software, I was once again able to move the slider to 5040 x 1050 under windows' display settings.

Has anyone tried the new 181.20 drivers yet?

I have a gtx 295 on it's way is why I am asking :T

Typhoon2000 · Post by **Typhoon2000** » 10 Jan 2009, 02:10

I have 3x 2009W's using Vista x64. Under 175.41 I can get 5040x1050 x57hz. Just installed 181.20 and reinstalled GXM. All wide screen modes are selectable under Nvidia control panel and windows control panel. All modes show up on SGU. However if I now choose 5040x1050x57hz I get monitor out of range error. If I custom res to 5040x1050x60 as per matsim, I get a mode failed. 4320 x900 (3x1280x900) works fine at default 60hz and looks fine to my eyes on a 20". So all modes get installed correctly under vista 64 with 181.20 but I am unable to usefully use 5040x1050x57hz or 60hz, but I can use both under 175.41. I havent tried any of the earlier drivers. I am looking to get a new card myself, thinking about a 280 GTX if there is a significant price advatage over the 285.

E2badg · Post by **E2badg** » 10 Jan 2009, 08:31

I have a HP A6530f running Vista 64 Home Premium

A tripleHead2Go digital, FW 2.3.40 GXM 2.04.00.011
running 3x Acer X213W monitors.

I just updated my video card from a XFX GTX260 to a BFG GTX 295

on my GTX 260 I was able to get 5040x1050 @57Hz using Nvidia driver 180.48 (Created Custom Res in Nvidia control panel)

I upgraded to the GTX 295 upgraded drivers to Nvidia 181.20 ran the GXM Wizard at got the custom resolutions for 5040X1050 @57Hz but when I select this setting my monitors go black and say input not supported......I don't get it ...my monitors ran fine on the GTX 260 at 5040X1050 @57Hz, What can be the problem???

Tried creating custom resolution in Nvidia control panel..but when I run the test it says Custom mode test fails but the desktop is at 5040X1050 @57Hz and it looks fine. Can someone help me out...I also submitted a support ticket with Matrox.

Update...After installing the nvidia 181.20 driver and running the GXM Wizard when you get to the part were you select your resolution I've notices that 5040x1050 is listed @ 55Hz.......could this be the problem with the monitors "Input not supported" why does it say 55Hz????

Typhoon2000 · Post by **Typhoon2000** » 10 Jan 2009, 11:00

Tried creating custom resolution in Nvidia control panel..but when I run the test it says Custom mode test fails but the desktop is at 5040X1050 @57Hz and it looks fine. Can someone help me out...I also submitted a support ticket with Matrox.

Exactly the same with me, When I do custom res 5040x1050x57 fron Nvidia panel, I get custom mode fail but the screen is clearly in 5040x1050. This is with 181.2. When it do it via change resolution option the screen gives an out of range warning. I haven't tried 180.48.

A Small White Box · Post by **A Small White Box** » 10 Jan 2009, 16:44

Exactly the same with me, When I do custom res 5040x1050x57 fron Nvidia panel, I get custom mode fail but the screen is clearly in 5040x1050. This is with 181.2. When it do it via change resolution option the screen gives an out of range warning. I haven't tried 180.48.

Same problem with my setup. Custom res at the 60hz settings from above and it says the test failed, but the resolution is clearly working and my monitors (3x 2253BW) are reporting 60Hz. Using the latest 181.2 and latest Powerdesk.

Typhoon2000 · Post by **Typhoon2000** » 11 Jan 2009, 00:43

I tried the earlier 180.48 driver and what do you, know custom res 5040x1050 @ 57 works fine for me under vista x64 :D

E2badg · Post by **E2badg** » 11 Jan 2009, 00:59

I tried the earlier 180.48 driver and what do you, know custom res 5040x1050 @ 57 works fine for me under vista x64 :D

Glad it worked for you Typhoon....I'm stuck since I upgraded to GTX295 I only can use 181.2 also tried Beta Drivers 180.87 and 185.20.same issue.

Hope there is a fix soon.

E

A Small White Box · Post by **A Small White Box** » 11 Jan 2009, 02:39

I tried the earlier 180.48 driver and what do you, know custom res 5040x1050 @ 57 works fine for me under vista x64 :D

Tried rolling back to the old driver. Using the default Matrox wizard to set up the displays did not work as before, but then I tweaked the custom settings as detailed above and it works great now. Old driver worked for me.

svet-am · Post by **svet-am** » 11 Jan 2009, 20:06

good to see there are others complaining about this with the 181.20 drivers. I just did a fresh install for my 8800's and i was seeing the same problem.

Since the install was fresh and I didn't have anything vested in it, I'm re-installing again and I'm going to fall back to the 180's

gulfstream5 · Post by **gulfstream5** » 22 Jan 2009, 06:17

Has anyone figured out this MODE FAILED deal when trying to set a NVIDIA to 5040x1050? I am having the exact same problem where it clearly shows the resolution and is working but will not stay. So frustrating!!!

DirtyH · Post by **DirtyH** » 28 Jan 2009, 11:12

"4. Change GDI Refresh to 60 (this is the big change thanks to Nigel, used to be 57 as per other threads), bits per pixel 32.
5. Then click on 'Advanced'.
6. In the Back-end Parameters, Timing Standard drop-down box and change it to 'CVT Reduced Blank'.
7. Then select 'Manual' from the Timing Standard drop-down box.
Setup the Manual timing as per below:
Horizontal Front Porch: 64
Vertical Front Porch: 3
Active Horizontal Pixels: 5040
Active Vertical Lines: 1050
Horizontal Total: 5376
Vertical Total: 1068
Horizontal Sync width: 64
Vertical Sync width: 4
Horizontal Sync polarity: +
Vertical Sync polarity: -
Horizontal Scan Rate will likely show 60.88
Pixel Clock will likely show 319.7500
8. Click on 'Test' and you should get perfect 5040x1050 video with no OSD message."
Then it says "test failed" despite wonderful picture on screen!!
I would pay anybody a lot if he gave me a hint how to cheat this since I'm trying to get this working since half a year!

Thank you in advance,
Harry

NZCoyote · Post by **NZCoyote** » 28 Jan 2009, 21:41

"4. Change GDI Refresh to 60 (this is the big change thanks to Nigel, used to be 57 as per other threads), bits per pixel 32.
5. Then click on 'Advanced'.
6. In the Back-end Parameters, Timing Standard drop-down box and change it to 'CVT Reduced Blank'.
7. Then select 'Manual' from the Timing Standard drop-down box.
Setup the Manual timing as per below:
Horizontal Front Porch: 64
Vertical Front Porch: 3
Active Horizontal Pixels: 5040
Active Vertical Lines: 1050
Horizontal Total: 5376
Vertical Total: 1068
Horizontal Sync width: 64
Vertical Sync width: 4
Horizontal Sync polarity: +
Vertical Sync polarity: -
Horizontal Scan Rate will likely show 60.88
Pixel Clock will likely show 319.7500
8. Click on 'Test' and you should get perfect 5040x1050 video with no OSD message."
Then it says "test failed" despite wonderful picture on screen!!
I would pay anybody a lot if he gave me a hint how to cheat this since I'm trying to get this working since half a year!

Thank you in advance,
Harry

Your best bet is to role back your nvidia drivers to 180.48, update the matrox GXM and then follow those instructions.

DirtyH · Post by **DirtyH** » 29 Jan 2009, 09:10

Thank you, I'll try and let you know. :twisted:

Post by **Mach1.9pants** » 29 Jan 2009, 11:56

Has anyone figured out this MODE FAILED deal when trying to set a NVIDIA to 5040x1050? I am having the exact same problem where it clearly shows the resolution and is working but will not stay. So frustrating!!!

Have you tried the BETA GXM from the link in the first post? If you have a 200 series card you should be OK

DirtyH · Post by **DirtyH** » 30 Jan 2009, 20:37

Have you tried the BETA GXM from the link in the first post? If you have a 200 series card you should be OK

Yes, no success.
I don't understand why I'm not able to set res manually, in driver inf file there's only bullsh. nobody can recognize res and frequ.
Sorry, but I'm starting to hate this because this is a big waste of life time. Dear Matrox guys, if you read this, please put in your ads: suicide proballity grows buying this product: I have best graphics card, best monitors, great PC and have now to suffer from this sh., sorry but I'm really pi. now.
:evil:

Post by **Mach1.9pants** » 30 Jan 2009, 20:46

EDIT: aahh just noticed you are using the 8800GTX, it doesn't work with the BETA version, it is only 200 series...sorry ignore below :(

If you are trying the BETA GXM then you shouldn't have to use the custom res. The custom res was a fix for the out of range error with the older GXM's and the latest NV Vista drivers. When you go through the install routine of the BETA it should ask you (after confirming that it has connection to your TH unit) what res you want to use. Make sure you tick 'include triple wide' and then select 5040 for the triple wide selection box. It will then install itself and ask for a restart, on restart it will give you 5040.
The BETA GXM (which only works for series 200 GPUs) and the current, released, GXM both can set 5040x1050 no problem. The problem is when it is set many of us get monitor out of range errors with the released. The BETA fixes this error. So does using the released GXM and setting a custom res..however many of us, including me, cannot set a custom res no matter what.
So how is it failing for you? IF you are using the BETA don't set a custom res, just use the PD-SE (sorry I use GXM and PD-SE interchangeably! I mean let the Matrox software do it) to set 5040 and you should be done.

gulfstream5 · Post by **gulfstream5** » 01 Feb 2009, 01:47

EDIT: aahh just noticed you are using the 8800GTX, it doesn't work with the BETA version, it is only 200 series...sorry ignore below :(

If you are trying the BETA GXM then you shouldn't have to use the custom res. The custom res was a fix for the out of range error with the older GXM's and the latest NV Vista drivers. When you go through the install routine of the BETA it should ask you (after confirming that it has connection to your TH unit) what res you want to use. Make sure you tick 'include triple wide' and then select 5040 for the triple wide selection box. It will then install itself and ask for a restart, on restart it will give you 5040.
The BETA GXM (which only works for series 200 GPUs) and the current, released, GXM both can set 5040x1050 no problem. The problem is when it is set many of us get monitor out of range errors with the released. The BETA fixes this error. So does using the released GXM and setting a custom res..however many of us, including me, cannot set a custom res no matter what.
So how is it failing for you? IF you are using the BETA don't set a custom res, just use the PD-SE (sorry I use GXM and PD-SE interchangeably! I mean let the Matrox software do it) to set 5040 and you should be done.

I was able to get things working and now have 5040 x 1050 but FSX still shows a max of 4360 x 768 or something like that.

Widescreen Gaming Forum