![]() ![]() But more or less, you can just run the game then mouse over and look at the details for the peaks on the graph for clock speed and see what it was doing when/if you get an ERR12 crash. If you detatch the graphs at the bottom, you can actually see what the card is doing over time (or just use the OSD). People run into this a lot when using liquid cooling blocks on GPUs in particular, because Nvidia's Boost 3.0 algorithm sees the card is only 40-50C and tries to ramp up the clocks too aggressively. the way Nvidia Boost 3.0 works, it may be trying to push the clocks higher than even the vBIOS boost clock (the one set by manufacturer) if it's cool enough. Yeah that's really not terribly high, but still. I don't remember how long i played last night with the 440.97 driver but i know it was more then 2, and this screen shot is from today.Įdit: I also have this in my Nvidia control panel. I tested the game for like 8 hours on driver version 430.86 and my current driver 440.97 for 3-4 hours. Well it turns out all i had to do was tick "Disable Full screen Optimization " and "Run this program as administrator" and no more screen freeze. I tired almost everything trying to fix this freeze but nothing worked. ![]() I even had a friend guide me to extraction one time. Warframe seemed to be the only game that would freeze the screen but continue playing. I normally play with my GPU overclocked, I did a 4 hour stress test with Furmark (extreme burn in test) so i know it is stable. (For me) Hopefully it can be fixed for you as well. I've been running some tests trying to fix this and i think i have finally fixed it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |