Forum Discussion
The patch that includes the work around for the Intel CPU crashes went live at 10 AM Pacific time today. It is version 1.1.3.
I'd be very interested in learning whether this fixes the crashes for everybody, even without lowering CPU speed.
Thank you for the feedback.
That crash I mentioned the other day that you commented on happened at 5.1 ghz @ 1.360v bios setting (loadline calibration =Turbo, so load voltage was probably about 1.340v).
I did another run after that crash at the same voltage that day (same windows session) and got an "CPU Internal Parity Error" (WHEA Correctable).
Not 100% sure this is the exact timestamp of that error, but this happened *after* the crash I had posted.
A corrected hardware error has occurred.
Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 10
The details view of this entry contains further information.
so whatever Intel bug that was being generated was changing bits somewhere, and if it was "corrected", the game would continue playing and a WHEA would be logged. If it wasn't corrected, then you get one of those two 2F2DA breakpoints or something like as you mentioned.
With the new patch out:
I *REDUCED* the cpu core voltage at 5.1 ghz from 1.360v to 1.335v.
Been playing 1 hour 40 minutes.
ZERO crashes so far.
ZERO WHEA "Internal Parity Errors" generated.
So far it's been an improvement but I've seen "long sessions" in the past without WHEA parity correctable errors, then suddenly the game crashed when I got my hopes up.
But this is an improvement. I'll keep playing and keep testing the results. But preliminary answer is: "Good so far!"
Is Intel acknowledging this bug in their firmware? I know how stubborn Intel can be...
I know how to get new microcode ahead of time (before it's put into bioses), that's easy: Just download VMWare microcode updater and the microcodes as discussed here:
https://www.win-raid.com/t3355f47-Intel-AMD-amp-VIA-CPU-Microcode-Repositories-Discussion.html
and then the DAT to bin converter over here:
https://onedrive.live.com/?authkey=!AE_9xt1wnaLT5lk&id=11F4002E1134F403!617750&cid=11F4002E1134F403
Then you can download the microcode patcher itself (that has a current DAT file conversion already) from here:
https://mega.nz/#!gZBzBIib!wNZwqhegXl1FME7h5HLhsfAT55Xk_EyTN6QNBo7l6Qo
For new microcodes that are not in "Microcode.dat", you can convert the bin files from the archives to a new DAT file, then patch it with the mega microcode vmrware updater, after you rename your new dat file to "microcode.dat" and copy it into the cpucodeupdater folder manually.
Anyway tl;dr: it's a definite improvement *so far*. I'll keep playing all day until I find how stable it is.