3dmark Error Occurred
Armanda Kicks
This is a generic error message that comes up when something unexpected happens. These errors should include a full technical error message about the issue. If you do not know what could have caused the problem, contact us with the full error message and the most recent autosaved .3dmark-result file from Documents/3DMark/ folder for further assistance.
Benchmark Test with Time Spy with standard AMD Software Settings --> Permanent failure during Intro order Graphic Test 1 (Time Spy "An error occurred" ). Actually it only passed once after I reinstalled Windows and set preset to Loud, when I tried to repeat the test it failed again (See attached pic for Score)
Post your 3dmark 99 scores here!
I think we need 99 scores as older machines and cards that have difficulty with 2001.
If you need to download it 3dmark99 is still on Futuremarks legacy page for download.
Supported Features:
16-bit Rendering
Point Sampling
Point Sampling With Mip-Mapping
Bilinear Filtering
Bilinear Filtering With Mip-Mapping
Trilinear Filtering
Specular Gouraud Shading
Vertex Fox
Table Fog
W-Fog
Sub-Pixel Accuracy
Alpha Blending
Addivitive Alpha Blending
Multiplicative Alpha Blending
Vertex Alpha Blending
Vertex And Texture Alpha Blending
I was just playing around with 3d mark 99 max for the first time yesterday. I was comparing the tnt2 ultra and my voodoo 3. I don't have the whole thing but I did write down the final scores if that's of interest
maybe if I get bored later i'll pull out the rig and take screenshots and give all the juicy details. it should be saved on there. I tried testing my Matrox G200 and G250 but they crashed the system every time I started the benchmark with them.
Thats great, the more scores the better!
Just watch out for the V-sync issue 3dmark99 has on faster systems. If the first 2 tests aren't going above 60fps or get stuck at 15\30\45 its probably stuck on.
Making a profile for 3dmark 99 atleast for nvidia drivers with it forced off seems to keep it off.
On Windows 2000 it gives _except_handler4_common could not located in the dynamic link library msvcrt.dll
If I copy ddraw.dll from C:\Windows\System on Win2k to the 3dmark folder it gives:
The procedure entry point FT_Thunk could not be located in the dynamic link library KERNEL32.dll
A score of 1 ? Yea thats low.
Atleast it runs on a 486, but did that Virge display anything correctly? Last time I tried a Virge in 3dmark it pretty much rendered everything in monochrome with no textures.
I tried 3dmark 99 in XP on that Tualatin machine above and got the same errors you were in 2k. OS issue for sure.
To get it working, extract the first setup file, as it will give you are -113 install error on Windows XP. Then run the internal setup.exe in Windows 98/ME comp mode.
After that, when you try to launch the installed 3DMark 99 you will get an directx 6.1 error and then you need to inject this file into the 3DMark 99 installation folder, i.e c:\program files\MadOnion.com\3DMark 99 Max\
Nice scores!
I'm trying the XP fix, lets it works in Windows 8.1 64, but framerate gets locked to 60, No amount of forcing it off in the Catalyst Control panel is unlocking v-sync. Even D3d Overrider is not unlocking it ?
Gonna Try it on an actual XP machine next ?.
For those that are not already aware of the issue, the folks at Futuremark seem to be struggling to keep a consistent product in the latest 3DMark benchmark. In particular, Fire Strike. Sometime around the release of Time Spy things started getting screwy with Fire Strike and now it seems with every Fire Strike GUI version update the effect is progressively decreasing benchmark scores, and specifically the physics portion of the benchmark.
Kudos to @Papusan for noticing this months ago and asking me to have a look at it. He has been going back and forth with Futuremark about the problem and it seems they are either ignoring him or perhaps they do not view it as a high priority issue. Or, maybe because most people running Fire Strike are not observant enough to notice, care, or ask questions they feel they don't need to fix it.
Some people might say you cannot compare results across benchmark software versions, but that shouldn't hold water here. There is a leaderboard and searchable database of results that basically every benching enthusiast and PC reviewer relies on, and if there is not a very high degree of consistency between GUI versions the results in their database will become irrelevant, as will their leaderboard. The search filter does not have a field to filter by GUI version, so we can expect the results from the database and leaderboard to be increasingly misleading, inaccurate and unreliable over time. This certainly is not a desirable thing for what is supposedly the current defacto standard in PC benchmarks.
You will notice from the examples posted below that with each new version of Fire Strike the scores get lower and lower. These examples are consecutive runs on the same day, same machine, and identical CPU and GPU settings. The only thing that changes is Fire Strike benchmark results degrade with newer versions. We need Futuremark to understand and correct this.
If you agree this is a problem and want it to be fixed, please complain to Futuremark and let them know they need to put the brakes on and not do anything else with 3DMark until they have this mess under control. Gimmicky features are one thing, but inconsistent benchmark results makes 3DMark unreliable.
We would like to acknowledge that a representative of Futuremark has responded promptly to this article and provided an email address for those interested in communicating with them about the issue. We appreciate the accountability and responsiveness.
We sincerely are grateful for Futuremark's responsiveness. I provided additional test results to Mr. Kokko to corroborate the findings of @Papusan and they have released an update that is expected to resolve the issue. See the message from James below for more details.
We've confirmed that there was an issue with the GUI, and we're in the process of rolling out an update (3DMark v2.2.3509) that should fix the scoring discrepancy.
With this update, overall scores increase slightly by up to 0.3%. Scores from the Physics and CPU parts of benchmark tests may improve by up to 2.5%. These changes bring the scores from 3DMark v2.2.3509 back in line with results from earlier versions that did not have the GUI issue.
For context, it is normal for 3DMark scores to vary by up to 3% between runs since there are some factors in a modern, multitasking operating system that cannot be completely controlled. So again, all credit to @Papusan for noticing the problem and bringing it to us.
LOL, just click the link above the video. It shows what the video does and it's instant gratification. The only reason I made the video was for YouTube viewers and for increased exposure of the issue that warrants attention.
The lowest score is the "latest and greatest" version of Fire Strike. The benchmarks were run only minutes apart on the same machine with identical CPU and GPU settings with no changes whatsoever except for the version of Fire Strike.
Hey I watched all painful X minutes of the video... seems about 10+% drop in score Physics based. I can see this being an issue, but also an advantage to post your results ASAP! because people down the road will be less likely to beat you hahah
@Papusan has been communicating with them for a while now and since that started every version gets progressively worse, so I thought it was time to bubble this up for attention before it gets too far out of hand. I have not had any communication with them. It's important that they pay attention to this to preserve their reputation. If nobody can trust the results to be accurate and it becomes necessary to research the version number to draw comparisons that are not dramatically skewed it could really hurt them. I don't want that to happen, so the article here will hopefully be a wake-up call for them. The degradation of results are already significant over multiple software revisions and that will make it more difficult for professional reviewers to get a clear and reliable comparison of old versus new tech as well.
I have sent a new feedback mail to Futuremark v/jarlo Kokko for the 10th time... Futuremark have said long time ago to me in the mail that "They have reproduced in-house and investigation is ongoing" I have send them a lot of result for their investigation. Nothing happens as you can see in the pictures - links!!!
See results. Both older UI versions 2.0.2067_64 and 2.0.2809_64 will give 15002 in Physics with [email protected] and both 2 latest drivers from Nvidia!! Newer UI versjons of 3DM Suite will give up to 400 points lower physics in fire Strike. All tested with same Nvidia drivers, stock graphics and 4.8GHz on processor.
c80f0f1006