Bavor Posted June 7, 2020 Share Posted June 7, 2020 (edited) I tried 3DMark11 on a completely stock speed system before any overclocking and I'm getting an error message. 3DMark11 run correctly through all the tests then keeps giving this error at the end: "hexadecimal value 0x00, is an invalid character" 3DMark support says its an issue with 3DMark system info. I uninstalled Futuremakr System Info, rebooted, downloaded the latest version of system info, installed it, then rebooted and I still get the same issue. After it was uninstalled, I checked and everything related to Futuremark was removed from the appdata folder. It worked fine a few months ago on the same system, and now it doesn't work. Any other suggestion on how to fix it? Edited June 9, 2020 by Bavor fixed typos Quote Link to comment Share on other sites More sharing options...
jab383 Posted June 8, 2020 Share Posted June 8, 2020 We have to update 3dMark 11 to version 1.0.179 (was 1.0.132) at the same time as updating to the latest System Info versions. Check which 3dMark 11 version you are using. 1 Quote Link to comment Share on other sites More sharing options...
Bavor Posted June 8, 2020 Author Share Posted June 8, 2020 I'm using the newest versions of both. I also tried using an older version of systeminfo because I didn't have the problem a few months ago. I also tried running it without systeminfo enabled to see if that was the issue and I still get that error message. Quote Link to comment Share on other sites More sharing options...
Crew Leeghoofd Posted June 8, 2020 Crew Share Posted June 8, 2020 install first the old version of 3DMark11, then update it with the new version, then the new systeminfo should work 1 Quote Link to comment Share on other sites More sharing options...
Bavor Posted June 9, 2020 Author Share Posted June 9, 2020 (edited) On 6/8/2020 at 1:55 PM, Leeghoofd said: install first the old version of 3DMark11, then update it with the new version, then the new systeminfo should work I tried that. I downloaded an older 3DMark11 version. I had it update to the newest version. Then I installed Futuremark SystemInfo version 5.27. I still have the same issue. Futuremark support says its due to a zero in the XML fire that SystemInfo creates in a place where it shouldn't have a zero. I assume it means something in the system or benchmark results isn't being detected correctly. Edited June 9, 2020 by Bavor Quote Link to comment Share on other sites More sharing options...
Bavor Posted June 9, 2020 Author Share Posted June 9, 2020 I also tried it with Scan SystemInfo unchecked in the help screen and get the same error. Quote Link to comment Share on other sites More sharing options...
Bavor Posted June 14, 2020 Author Share Posted June 14, 2020 I've been though a bunch of troubleshooting with the Futuremark support people and still haven't figured out why the benchmark won't produce a result file. Other versions of 3DMark that use Futuremark SystemInfo work fine and produce valid results. I've uninstalled 3DMark11, rebooted, deleted any remaining files in the 3DMark11 folders, rebooted, and reinstalled and still have the same issue. I've used the same downloaded installer to install 3DMark11 on another system and it works without any issues. After multiple days of email exchanges with their support people I'm at the point where getting a spare drive and doing a new OS install may be my next troubleshooting step. 1 Quote Link to comment Share on other sites More sharing options...
Bavor Posted September 4, 2020 Author Share Posted September 4, 2020 I ended up fixing the issue by reinstalling Windows 10. Nothing else seemed to work. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.