The problem only happens when overclocked while booting. A simple solution is to force it to stock settings until after the boot process. How difficult is that?
Huh? I missed that info.
The second design flaw to hit the GeForce GTX 1080 and GTX 1070 after the fan revving bug, isn't confined to the reference "Founders Edition" cards, but affects all GTX 1080 and GTX 1070 cards. Users of monitors with dual-link DVI connectors are noticing problems in booting to Windows with pixel clocks set higher than 330 MHz. You can boot to windows at default pixel clocks, and when booted, set the refresh-rates (and conversely pixel clocks) higher than 330 MHz, and the display works fine, it's just that you can't boot with those settings, and will have to revert to default settings each time you shut down or restart your machine.
A user of a custom-design GTX 1070 notes that if the refresh rate of their 1440p monitor is set higher than 81 Hz (the highest refresh rate you can achieve with pixel clock staying under 330 MHz) and the resolution at 2560 x 1440, the machine doesn't correctly boot into Windows. The splash screen is replaced with flash color screens, and nothing beyond. The system BIOS screen appears correctly (because it runs at low resolutions). The problem is also said to be observed on a custom-design GTX 1080, and has been replicated by other users on the GeForce Forums.
I'm guessing this will be a BIOS-level fix.
Some hardcore gamers prefer DP-only Korean monitors with high refresh rates because they provide low latency (due to the fact that they have no video processing capabilities, even an OSD). There will definitely be at least a few GTX 1080 buyers for whom this will be a problem.
Buying a 1070/1080 and then a cheapo monitor without g sync makes sense..
Perhaps it effects more than OCing, but again, the problem ONLY happens during the boot process, and all that would be required is to lower the pixel clocks to stock (or perhaps to 60hz as maybe it affects 120hz/144hz at stock?), and presto, you can boot, and go back to what ever pixel rate you want.
Doing some calculations a 4K monitor @60Hz would be ~500MHz. A 1440 @ 144 Hz (modern gaming monitor) would be ~540MHz. So, there are plenty of people that this affects who aren't O/C'ing their monitors.
Doing some calculations a 4K monitor @60Hz would be ~500MHz. A 1440 @ 144 Hz (modern gaming monitor) would be ~540MHz. So, there are plenty of people that this affects who aren't O/C'ing their monitors.
Either way, there is a solution to this. They just have to either force a lower resolution and/or hz at boot. The fact it only happens during the boot makes it more likely there is a more elegant solution.
Yes, it's annoying, but people acting like they can't solve the issue are simply Nvidia haters.
Who said it can't be solved? I'm sure nVidia will fix it. It's good to know that in the meantime there's a workaround.
lol at calling people who talk about it haters.
The person who called me out for myself saying it can be solved. (I'm not going back to look, but feel free to go back).
And anyways, to the previous post, I just realized that Dual Link DVI-D doesn't support 4K at 60hz, so it's not a problem there anyway. And I do not believe 1440p monitors with Dual Link DVI-D supported high refresh rates either, so it probably is only the custom OC'ed refresh rates unless 144hz at 1080p breaks 330MHz.
I can see his concern. You might not be able to run anything at the nVidia driver level before the bug occurs. I think since you are so certain that he wonders if you might know how to fix it.
The problem only happens when overclocked while booting. A simple solution is to force it to stock settings until after the boot process. How difficult is that?
It would be a complete PITA to have to change monitor resolutions every time you shut down, and then have to change them back when you boot up. It personally would infuriate me if I had to do this every single time I shutdown/booted.
Sure very short term, it is doable if a fix comes out. If that fix does not come, then I would be selling the card immediately.
And you still didn't answer my question as to *why* you know its fixable via software.
Because as I said before. I can create a work around with my knowledge. Windows Task Scheduler lets you setup an event trigger at log in, and shutdown. I just have to Google for a program that let's me change resolution/refresh rates with a command line option and set up a Window Task Schedule for it. I wouldn't have to do anything once setup.
Surely Nvidia can do the same thing at the very least, and do it cleaner.
A workaround is not fixing anything though.
Now, I can understand that because so few configurations use DVI for that res and refresh rate that nVidia could have missed it. Hopefully there's something simple that will fix it. If this is happening for example when the nVidia drivers load, then it's pretty likely a driver problem. It might be able to be fixed in the bios? If the best they can do is a workaround that runs some script or other exe to force the lower res on boot, that would be little more than a hack, IMO.
It would be a script if I had to deal with it now (you can call that a hack), but Nvidia can do the same from within their software. If you didn't know, just about every device uses the Windows Task Scheduler on boot to load up their software, such as the Nvidia Control Panel.
Like I have said, there is a software solution. Whether it is a driver fix, BIOS fix, or a work around that just turns off custom resolutions at log off, and turns off back on when you log in, there is a fix.
That would be crazy if true. They had to validate at 4k right? That just isn't the sort of fringe case that goes unnoticed.
BIOS fix doesn't work. Plenty of people don't know what BIOS is, even more don't know how to flash a new BIOS.
If this was AMD they would get called out left and right lol.
Instead, AMD just left the DVI port off altogether. I guess that is a clever workaround for this issue...
And LOL at people who think this effects 4K resolution at all.
Because displays usually ship with one and not a DP cable. Ok, they are cheaper than HDMI but why use one if it is not required?Not sure why people are using DVI instead of DP?