• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

3Dmark11 GUI crashes !?

Gripen90

Gripen90

Gripen90

Associate
Joined
20 Nov 2009
Posts
2,050
Location
Haarby, DENMARK
After updating from Forceware 344.16 to both beta/whql 347.09 mid december and now whql 347.25 mid january I still have problems with 3Dmark11 to run with my GFX OC settings :(
Sudden freezes and crashes back to desktop with 3Dmark11 GUI error or with Nvidia driver not responding. And sometimes my GFX OC'ed is totally reset to zero after a driver not responding message (GPU-Z report stock settings while MSI Afterburner show OC settings:confused:), and when I then try to run 3Dmark11 again my cards run stock speed and then benchmark finishes fine:confused:.
It's so weird after these 347.xx drivers 3Dmark11 is acting up when I run my cards with OC. With 344.16 there was nothing.

All my games CoD M2/3,BLOP 1/2, BF3, HomeFront, Wolfenstein etc and 3Dmark FireStrike (Normal, Extreme, 4K), Unigine Valley 1.0, Heaven 4.0 run 100% fine and stable for hours with my GFX OC and 0 errors.

Another quirck I noticed which is the same on my two PC's one with GTX 970 SLi and the other GTX 970 3 way SLi. With Forceware 344.16 my CPU score was around 13'500poins, but after 347.09 it plummeted to 11'990points. The 347.25 driver upped the score a bit to 12'500points. It doesn't make sense either.
 
Oh yea forgot to ask if any one has experience the same then please share your experience and fixes - if you got it to work :)
 
Its because your OC settings are not 100% stable for 3DMark to adhere to. Pure and simple.
If you reset them to default you will find 3dmark runs. This proves the issue.

To be honest I am not bothered with it anymore. My cards are overclocked and run 100% fine in games. In 3DMark11 and 3DMark it crashes. In Heaven it runs all day. Same with Valley and the new Monster benchmark.

Also different drivers will give different scores in 3dmark. Read the nvidia drivers thread or the 3dmark threads for more info and assistance.
 
varkanoid said:
Its because your OC settings are not 100% stable for 3DMark to adhere to. Pure and simple.
If you reset them to default you will find 3dmark runs. This proves the issue.

To be honest I am not bothered with it anymore. My cards are overclocked and run 100% fine in games. In 3DMark11 and 3DMark it crashes. In Heaven it runs all day. Same with Valley and the new Monster benchmark.

Also different drivers will give different scores in 3dmark. Read the nvidia drivers thread or the 3dmark threads for more info and assistance.
Click to expand...

Hmm but with the Forceware 344.16 driver there was no issue with my OC settings, only after switching to these new 347.xx series the problem occours. Also that weird thing where the clocks after a CTD suddenly are reverted to stock clocks according to GPU-Z and but MSI Afterburner shows the OC settings (both the old 4.0 and new 4.1).
 
because 3D Mark is more Susceptible to changes in driver configuration and updates in combination with overclock settings. Always has been. The true test is to revert your GPU to default under 347.xx and run 3DMark and see if it crashes. If it doesnt its because of your OC settings/driver combination if it does its down to 3d Mark being pants.

All GPU-Z does is show the actual settings reported by the card. After a crash/driver not responding clocks revert to to defaults. MSI will show the OC settings but if you put the GPU under load it will run at defaults. Confirm this by the actuals shown in MSI. If you want your OC back you always need to reboot.
 
varkanoid said:
because 3D Mark is more Susceptible to changes in driver configuration and updates in combination with overclock settings. Always has been. The true test is to revert your GPU to default under 347.xx and run 3DMark and see if it crashes. If it doesnt its because of your OC settings/driver combination if it does its down to 3d Mark being pants.

All GPU-Z does is show the actual settings reported by the card. After a crash/driver not responding clocks revert to to defaults. MSI will show the OC settings but if you put the GPU under load it will run at defaults. Confirm this by the actuals shown in MSI. If you want your OC back you always need to reboot.
Click to expand...

Hmm 3Dmark11 can still make GUI errors and CTD's on stock clocks. Guess it hates these drivers... uninstalled the benchmark now and only testing with Unigine Heaven 4.0, Valley 1.0, 3Dmark FireStrike, Skydiver and 3Dmark Vantage.
 
Had my first CTD this morning after running with my second OC profile witch has a 103 power limit. (fire Strike)
The benchmark completed and a valid score was recorded but the program crashed as it was published.
Runs every time on 102 profile.
 
Gripen90 said:
Hmm 3Dmark11 can still make GUI errors and CTD's on stock clocks. Guess it hates these drivers... uninstalled the benchmark now and only testing with Unigine Heaven 4.0, Valley 1.0, 3Dmark FireStrike, Skydiver and 3Dmark Vantage.
Click to expand...

Depends if you've had a few crashes whilst overclocking, that too could've borked the install.
 
Geeman1979 said:
Depends if you've had a few crashes whilst overclocking, that too could've borked the install.
Click to expand...

I uninstalled and reinstalled 3Dmark11, and I even tried two different 3Dmark11 version releases. The older release was much more stable then the "new". The old 3Dm11 build wouldn't crash that easily.
 
You must log in or register to reply here.
Back
Top Bottom