Question Overclocking a i7-9700k - Repeated Event 19's in the WHEA Logger

[kelly.miller]

I built this computer using the following setup: https://pcpartpicker.com/list/4JLPw6
(I used the EVGA GeForce 970 SSC and the drives out of my old computer for now)

Everything worked great for the first few months, with only an odd crash at 5.2 GHz. I just turned it down to 5.1 GHz and kept going. Up until a few weeks ago.

Suddenly, the computer starts crashing on startup repeatedly, and only stops when I turn off Asus' adaptive overclocking entirely and turn the processor down to 4.8 GHz. I tried a few things (ran perfectly under the Intel Processor Diagnostic Tool, and under an OCCT stress test on the processor; crashed immediately when I stress tested the power supply, though), but figured I could live with 4.8 GHz.

Now, a few weeks later, my Windows logs are filling up with these:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
  <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />
  <EventID>19</EventID>
  <Version>0</Version>
  <Level>3</Level>
  <Task>0</Task>
  <Opcode>0</Opcode>
  <Keywords>0x8000000000000000</Keywords>
  <TimeCreated SystemTime="2019-09-28T00:41:27.843721700Z" />
  <EventRecordID>267334</EventRecordID>
  <Correlation ActivityID="{ebbc9170-09a4-4c75-b83b-3d738f20ca69}" />
  <Execution ProcessID="3956" ThreadID="7636" />
  <Channel>System</Channel>
  <Computer>GameComputer</Computer>
  <Security UserID="S-1-5-19" />
  </System>
 <EventData>
  <Data Name="ErrorSource">1</Data>
  <Data Name="ApicId">12</Data>
  <Data Name="MCABank">3</Data>
  <Data Name="MciStat">0xcc40008000010179</Data>
  <Data Name="MciAddr">0x106c2c9000</Data>
  <Data Name="MciMisc">0x206485</Data>
  <Data Name="ErrorType">9</Data>
  <Data Name="TransactionType">2</Data>
  <Data Name="Participation">256</Data>
  <Data Name="RequestType">7</Data>
  <Data Name="MemorIO">256</Data>
  <Data Name="MemHierarchyLvl">1</Data>
  <Data Name="Timeout">256</Data>
  <Data Name="OperationType">256</Data>
  <Data Name="Channel">256</Data>
  <Data Name="Length">928</Data>
  <Data Name="RawData">435045521002FFFFFFFF03000200000002000000A00300001A2900001C0913140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F890C52C229D8E75D50100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000098020000080100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000200000000000000000000000000000000000000000000007F010000000000000002010000010000EC0609000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C00000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000C00000000000000EC0609000008100CFFFBFA7FFFFBEBBF0000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F005E200000000000902C6C10000000000000000000000000000000000000000000000000000000020000000100000045D40C769575D50106000000000000000000000000000000000000000300000079010100800040CC00902C6C100000008564200000000000000000000C000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
  </EventData>
  </Event>

Two a minute, every minute. I'm not entirely sure what to do, but considering I've went from 5.2 GHz to 5.1 GHz to 4.8 GHz and I don't like where this is going, I'd like some pointers as to how to pinpoint the exact problem so I can replace whichever part isn't working...

 

[PC Tailor]

Can you confirm that the WHEA errors stop occuring when you reset the BIOS to complete defaults?

 

[kelly.miller]

I actually tried setting it to defaults after it crashed once yesterday. It won't even start with defaults; it crashes immediately with a Corrected Machine Exception.

 

[PC Tailor]

Well you may want to check the next time it appears:
<Execution ProcessID="3956" ThreadID="7636" />

The Process ID is in your Task Manager labelled PID - and every process will have a unique one, it may be worth just seeing what the process it is executing when the issue occurs. Obviously WHEA is Windows Hardware Error Architecture so something is probably going askew.

I would usually say ignore these, as it can also be caused by drivers (such as GPU drivers) however being as you're also experiencing crashes, that's a different matter.
How long have you had the PSU?

 

[kelly.miller]

Well you may want to check the next time it appears:
<Execution ProcessID="3956" ThreadID="7636" />

The Process ID is in your Task Manager labelled PID - and every process will have a unique one, it may be worth just seeing what the process it is executing when the issue occurs. Obviously WHEA is Windows Hardware Error Architecture so something is probably going askew.

I would usually say ignore these, as it can also be caused by drivers (such as GPU drivers) however being as you're also experiencing crashes, that's a different matter.
How long have you had the PSU?

I actually toyed with the idea of swapping my old comp PSU in (it's a Corsair RM1000) and seeing if the errors continue to happen, as I found it odd that stress testing the power supply caused it to exception immediately. I'm actually waiting for an order to come early this week (mostly velcro straps, adhesive hooks and so on; I'm going to re-route all the cables to increase airflow in the front).
I ordered everything on June 10th and got it all a few days later. So 3 1/2 months.
Edit: Turned it on and got more errors, so I looked up the PID. The process is the Windows Diagnostic Policy Service. Disabled it, no more errors. Still running at 4GHz, though...

 

[Ketchup79]

When/if you have enough crashes due to stability issues, sometimes you will run into system files being damaged, so I do wonder if that might be the case here. From an elevated command window, type sfc /scannow.

I would also recommend grabbing the latest bios (1302 as of today) as there have been several releases with performance and stability improvement since initial release.

 

[kelly.miller]

Yep, tried both yesterday. No dice.

 

[Ketchup79]

Ok. Where did you get the drivers you are using (did you download everything Asus has available, or did you just download the drivers Windows said it needed)?

If it were me, I would grab an extra drive and install Windows and all my drivers. If the problem continues, there is a good chance it's a hardware problem (or possible BIOS setting issue).

 

[kelly.miller]

Well, I always go and get the latest drivers whenever I install new hardware, and double that if I have to reinstall Windows (which I did, because I was running Windows 7 on the computer before that, and this one also had new hard drives to boot). I also have a Pro subscription to IOBit Driver Booster, which lets me know when drivers are out of date, and I have none at this point in time.

 

[Ketchup79]

Iobit could be feeding you incorrect drivers, plus there is the whole question into the security of that program:

Q&A - Malwarebytes blocked IObit driver booster

Recently got an issue regarding Iobit Driver Booster, Malwarebytes has blocked and quarantined the setup file immediately as a suspicious file.

malwaretips.com

 

[kelly.miller]

Okay, I finally went and swapped out the power supply for my old system power supply (it's a Corsair RM 1000). Same errors are occurring, and now they're happening if I set it to anything over 4.2 GHz. I'm starting to think either the CPU or the motherboard has had it...

 

[kelly.miller]

Sorry for double-posting, but does anyone possibly know an effective way for me to determine if the problem is with the processor or the motherboard? I don't want to spent $Cdn500+ replacing the wrong component, unless they're both no good.

 

[Ketchup79]

Are you still crashing, or just seeing the message in your event logs?

 

[kelly.miller]

Are you still crashing, or just seeing the message in your event logs?

Still crashing. Same error; Machine Check Exception.