3DMark
Time measurement data not available. The validity of the result cannot be determined
Every time I run a 3Dmark benchmark it keeps giving me the annoying error "Time measurement data not available. The validity of the result cannot be determined". I wish there was an actual log dump that would give some useful information instead of a generic error.

Things I've tried:

Removing the overclock settings for my memory so now it's back to stock
Uninstalling/reinstalling 3dmark
uninstalling/reinstalling Futuremark SystemInfo
made sure I don't have any monitoring programs running that could cause systeminfo to crash

No idea how to get this working. I'm at a loss. The program is great when it worked but now for some reason it stopped working.

Some of my system:

EVGA RTX 2080TI FTW3 Ultra
i7 7700k
G.Skill Trident Z RGB 3866 (2x8GB)
1TB 970 Pro M.2
Asus Maximus IX Formula

I still have my old raid 0 ssd partition i'll probably try booting into to see if it's a software issue but I'd really appreciate it if someone could give me some solid advice out there. Thank you in advance

*EDIT*
I just finished booting into my raid 0 SSD partition and still same error ¯\_(ツ)_/¯
Last edited by TheStealthAssassin; Apr 24, 2019 @ 2:29pm
< >
Showing 1-15 of 17 comments
𝔇ave Apr 24, 2019 @ 5:34pm 
check to see if your BIOS time is in sync with your OS time.
Dang you had me excited at first. I checked the BIOS and it was out of sync, it was 3 hours behind so I set it and I think it was only a minute off of the actual time but still received the same error unfortunately
𝔇ave Apr 24, 2019 @ 8:55pm 
are you using monitoring software live rivatuner or some other overlay at all? if so try disabling it

oh nm i just read u tried that
Last edited by 𝔇ave; Apr 24, 2019 @ 8:57pm
UL_Jarnis  [developer] Apr 24, 2019 @ 11:56pm 
Try disabling hardware monitoring. You will lose the monitoring graphs, but if SystemInfo is crashing mid-run due to some conflict, this might cure that.
I just tried disabling "SystemInfo hardware monitoring" and left "Scan SystemInfo" on and still received the same result
UL_Jarnis  [developer] Apr 25, 2019 @ 11:11pm 
There will be a new version of SystemInfo today (within the next 8 hours). Try again with that.
Hey Jarnis, I just downloaded the new version and tried again with the hardware monitoring disabled and received the same error. I enabled it and tried again and received "Time measuring inaccurate. Results are invalid." Hope that helps and thank you for getting back to me on this
UL_Jarnis  [developer] Apr 26, 2019 @ 5:52am 
Can you give a link to the result saying "inaccurate". That is different from "not available". Inaccurate means it now got timer data, but it sees that your system has conflicting time information when comparing motherboard RTC clock to system clock and couple of other timing sources, at which point scoring cannot be validated. Easiest cause for this type of problem is OCing CPU outside BIOS. But it could also be buggy BIOS or somehow faulty motherboard.
Last edited by UL_Jarnis; Apr 26, 2019 @ 6:49am
I can try to make sure the clock in BIOS matches the exact time. Also I can see if there is a BIOS update, just get nervous since updating the BIOS usually messes up the RAID config. I'll do that anyways to see if that helps. I haven't done any overclocking since I wanted to start getting a baseline of where I'm at then I was going to overclock my GPU and CPU then run the test again, then add my custom loop liquid cooling to see the difference in performance. This program has worked in the past with the same hardware but I believe it was one of the updates that came through that caused issues.

Edit:
Also wasn't sure what you meant by a link to the result. I can't link to it since it's not posting my results
Last edited by TheStealthAssassin; Apr 26, 2019 @ 2:39pm
UL_Jarnis  [developer] Apr 26, 2019 @ 10:21pm 
Whenever you get the run complete,. you can always click "compare result online". That opens in a browser. URL to that page.
Oh my bad, I didn't realize I could still generate a link if it was invalid.
Here it is:

https://www.3dmark.com/3dm/35703460?
UL_Jarnis  [developer] Apr 27, 2019 @ 11:10am 
Yes this is missing the timer data, so nothing can be done. If you have one that says "inaccurate" instead, link to that.

Generally this type of issues are fixed either through BIOS updates, BIOS settings changes or removing background programs that interfere with SystemInfo.
TheStealthAssassin Apr 27, 2019 @ 11:29am 
https://www.3dmark.com/spy/7013419 <that one should have the inaccurate.

I just finished backing up so will be doing a BIOS update here. Hopefully that fixes it. I'll report back
TheStealthAssassin Apr 27, 2019 @ 12:11pm 
Looks like I already have the latest BIOS update from ASUS. I also made sure nothing was overclocked and the time was accurate.
UPDATE!!!! I finally received a valid score. I'm not sure which one fixed it since I did a couple things but it was one of these two. I replaced the BIOS battery and I replaced my riser cable for my video card with a longer one (preparing for the liquid cooling build). I guess re-seating the video card counts as 3 things but that seemed to fix it.

The only issue I have left is Time Spy flickers but none of the other benchmarks seem to have that problem. I've uninstalled both 3D Mark and Futuremark SystemInfo and reinstalled, however still running into flickering issues.
< >
Showing 1-15 of 17 comments
Per page: 1530 50

Date Posted: Apr 24, 2019 @ 2:11pm
Posts: 17