Folks,
Intel is good. I've had an i7-6700K-based build since March. It's had one or two minor stability issues, and I've finally narrowed it down. Running iterative loops of Intel's Processor Diagnostic Tool, I've discovered that the cpu fails the Floating Point test.
(Cool note: it passes a lot, but will occasionally fail. Just running the Floating Point test and looping it, it'll take anywhere from 1 to 160 passes before it fails. This points out the need to run diagnostics more than once.)
Whatever...the point: a quick phone call to Intel, a description of the issue and the test results, and I can get a cross-shipped RMA.
The hitch? They need the friggin' ATPO. That's a 2D encoded series of squares on the chip. Really? Their FAQ says to use a 3-5x macro zoom on a cellphone and use a decrypter and then send in the number.
C'mon. Really?
Anyone know how to read these things?
Ken
Intel is good. I've had an i7-6700K-based build since March. It's had one or two minor stability issues, and I've finally narrowed it down. Running iterative loops of Intel's Processor Diagnostic Tool, I've discovered that the cpu fails the Floating Point test.
(Cool note: it passes a lot, but will occasionally fail. Just running the Floating Point test and looping it, it'll take anywhere from 1 to 160 passes before it fails. This points out the need to run diagnostics more than once.)
Whatever...the point: a quick phone call to Intel, a description of the issue and the test results, and I can get a cross-shipped RMA.
The hitch? They need the friggin' ATPO. That's a 2D encoded series of squares on the chip. Really? Their FAQ says to use a 3-5x macro zoom on a cellphone and use a decrypter and then send in the number.
C'mon. Really?
Anyone know how to read these things?
Ken