New
#671
I can confirm 3DMark people will look at the log file and get back to you, at least they did in my case. I just sent my log file to info@futuremark.com. A guy got back to me quickly and answered additional questions I had.
Responses were a bit vague, though. I was asking him why Time Spy was crashing with XOC OSD enabled. Basically he was saying XOC OSD isn't up to the "complicated" testing Time Spy performs, so disable it. Easy answer or maybe it was an obvious guess for him.
The problem is it's not just Time Spy but other apps in the suite as well. And as noted not just on this new build, but previous ones as well. As I said, 3DMark doesn't like me. That said, the only thing common to 3 systems is the GPU
Anyway I'll post at their forums when I get round to it. Being kind of lazy about it right now.
Thanks.
I doubt it. And I don't believe it's a driver issue unless 3DMark is having issues with all AMD GPU drivers.
And yeah, I've been close to pulling the trigger on a EVGA 1080 FTW2 card. Nearly did it twice, including yesterday. But I have other needs to consider including my photography needs. Need to consider color fidelity. I know NVidia and AMD displayed colors are slightly different. Add to that all I know is ATI (AMD) so even a minor adjustment in color would be highly noticeable to me. This is why I'm hesitant to jump from AMD to NVidia. Were the roles reversed, it'd be the other way - hesitant to move from NVidia to AMD.
Again, thanks.
Hi,
Crashing is normal as far as I've seen
Uninstall and reinstall is about all I've done.
Waiting for trim to clear up 35gb's of wasted space from uninstalling these buggy benchmark installs
@sygnus21, Drew I know you said you were crashing with your card at stock. Is your CPU overclocked? I just tried to run it with my card stock. I crashed within 5 seconds of the benchmark starting. It did the same thing 4 times in a row. My CPU is all that is overclocked. It is perfectly stable. I can run AIDA, Prime, IBT or anything else with no problem. I can play any game I have with no problem. So, just on a whim, I went into BIOS and raised my Vcore by .015 and ran it again. It ran and completed. What was strange was that Firestrike crashed too before before I increased my Vcore. Afterwards it ran fine too. You may want to give that a try just to see.
I know my CPU is perfectly stable before I increased the voltage. Why increasing it made it run I have no idea unless it is something to do with the coding Mark 3D uses that you just have to power through. That is only a WAG, but the best I can come up with.
That to me makes no sense because i added Vcore a few days before this mess happened
I know this was the case with you Steve but i think this goes deeper than we think because all of us are experiencing the same thing and we all have 1080ti's maybe our PCI Lanes being overvolted by the card i have no idea but it has to be something with our cards
i usually will run 1.40 on 6850k but i increased it to 1.42 v and it is crashing i know i am stable i ran intel extreme tuner and other stress test on this system
Normally i have my setting on my GPU cranked up so i don't know what gives