• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

3DMark11 Physics Issue

p_monks33

Golden Member
I have recently noticed terrible physics scores with my I7 2600k @ 4.7ghz, I watch my temps, they are in the 40's at 100% load on all cores during testing, I can't even stand to let the physics test run all the way though, because it is literally 3-4 FPS. I used to get about 34 FPS and 10700 Physics score, I would be lucky to break 500 now. I have taken my overclock away, same stuff. I have checked drivers, uninstalled and reinstalled 3dmark, what could be causing these issues?
 
That's pretty odd, but can I ask - which version of 3dMark you're using? Is it on Steam?

I had a similar issue with the Steam version of 3DMark (2013). I reported it to Steam and 3DMark months ago, they kind of pointed fingers at each other. It dropped my physics score by about 33% (but not 95% like in your case). Only affected the Steam version, not the free version from FutureMark.
 
Last edited:
Yeah, its the steam version. I will download the non steam one and see. I had someone say that there was a security update that hurt 3dmark scores, and maybe an SDK, or DX update.
 
That's pretty odd, but can I ask - which version of 3dMark you're using? Is it on Steam?

I had a similar issue with the Steam version of 3DMark (2013) I reported it to Steam and 3DMark months ago, they kind of pointed fingers at each other. It dropped my physics score by about 33% (but not 95% like in your case). Only affected the Steam version, not the free version from FutureMark.

Good call, just installed the standalone, and back to 32fps avg and 11000 score. Thanks alot. I have been dicking with this for like a week.
 
It was KB2670838 that broke the DX11 3DMark tests for me -- but at the time I was only focused on 3DMark, so I never circled back to see if it also broke 3DMark11.
 
Back
Top