Check Windows Event logs Viewer for WHEA CPU internal parity errors indicating overclock instability. TheoryHardware reports errors to Windows Hardware Error Architecture.
Hardware reports corrected errors (recoverable) or uncorrected errors (not).
WHEA errors in Windows Event Viewer logs.
HWiNFO has WHEA error count sensor.
Skylake-X cores detect internal parity errors.
Parity error means data in a register or cache did not get stored correctly?
Skylake-X cores fix some internal parity errors.
Fixing data before processing prevents possible core crash or memory corruption.
Ideal no parity errors.
Parity errors indicate slightly unstable overclock.
Increase VCore or lower CPU frequency.
Less common, reduce memory overclock?
ExampleOverclocking memory, first to 3400.
All Prime95 spot tests pass.
Prime95 stability test fails at 254 minutes.
Cannot replicate Prime95 stability failure with spot tests at failing sizes (1280K->56K).
RealBench, Aida64, Time Spy, Fire Strike, Cinebench all pass.
Notice Time Spy demo sometimes crashes.
Time Spy application error in Windows Event log, exception code 5.
Exception code 5 means access violation - Time Spy attempts to read wrong memory?
Time Spy demo crashing more often with memory overclock?
Memory overclock at fault?
Boost DIMM voltage, VCIN, memory frequency (to 3466, in case better ratios).
Still 1 out of 10 crash on Time Spy demo.
Review old test data and Windows Event Viewer log:
Time Spy demo application errors in Windows Event Viewer log before memory overclock.
Update to 1.06 BIOS (Spectre fix) four days before start of parity errors.
From 0 to 5 WHEA parity errors each day.
Time Spy application errors usually within minutes of WHEA parity errors!
Parity errors start when shifting from 44x to 45x core multiplier.
So:
Probably not just memory overclock - WHEA and Time Spy application errors started before.
Probably not Spectre fix - WHEA errors not immediately after.
Probably WHEA parity errors and Time Spy Demo crash related - times close.
Insufficient VCore for 45x core multiplier?
WHEA error usually appears by 5th Time Spy demo run after restart
Start Vcore +0.001 and run 5 Time Spy demos.
1.174Vcore, Time Spy demo stops crashing, still WHEA errors.
1.177Vcore, one Time Spy demo crash; still WHEA errors.
1.180Vcore, no Time Spy demo crash; still WHEA errors. :(
Drop frequency to 44x, no Time Spy demo crash; no WHEA errors; 10x Time Spy demo runs.
Frequency back to 45X, 1.90Vcore, Time Spy demo crash; still WHEA errors. :(!
1.120VCore, no Time Spy demo crashes; no WHEA Errors; 10x Time Spy demo runs! :)
1.195VCore, no Time Spy demo crashes; no WHEA errors; 10x Time Spy demo runs.
Prime95 56K in-place FFT 5 minute test cycle comparison temps +5C (91C @ 16 minutes).
ConfigFrom 32x Mesh Ratio config above:
VIN: 1.92
VCore: 1.1195 (can go down to 1.1191?)
VDIMM1: 1.375
VDIMM2: 1.386
Fast Boot: Off
Force Memory Retraining: Enabled
VDIMM2 different because BIOS actual voltage lower than VDIMM2 set in BIOS.
Those VDIMM1/VDIMM2 settings create same BIOS actual voltage for both DIMM banks.
Fast Boot off, retraining on in case lack of memory training problematic.
VIN and VDIMM increase while troubleshooting WHEA errors not needed?
May go back:
VIN: 1.91
VDIMM1: 1.35
VDIMM2: 1.35
Fast Boot: On
Force Memory Retraining: Disabled
TipCreate two custom views in Windows Event Viewer.
WHEA = All events by source WHEA-Logger.
Application Error = All events by source Application-Error.
Check frequently when overclocking.
ReferWHEAWHEA Overclock Partial Instability WHEA Error Overclock Instability Full Discussion WHEA Errors And CPU FrequencyWHEA Errors Caused By Spectre Fix? Intel WHEA Error DecodingIntel WHEA Error Discussion & Diagnostic
post edited by geninfo - Friday, February 09, 2018 5:13 PM