Whea-Logger error coming out of nowhere...PC is at stock settings.

After running this system for almost 2 years this error occured. I heard this error was a hardware issue and I'm so scared that the cpu might be degrading. Now, the system was in fact stock settings and the weird part is that the cpu clock goes to like 4,514mhz and I didn't get any freezing, bsod, or crashes. So, I honestly don't know where to start because I'd be sooo bummed out that I'll be out of the PC if the pc turned out to be unstable. So.....I would like to know where to start because I mostly used the high performance setting in the power options in control panel for playing games. I would be appreciated for anyone to guide me with this. Thank you very much. :) Here are the pictures of those errors and the stuff from Hwinfo64 monitoring in the attatchments down below.

I don't think so. Note that its 4790k. I thought the base clock is 4.0mhz and the turbo is 4.3mhz. Last time I check the uefi bios, it seems everything is set to auto. Except the auto oc thing was disabled and the ram was set to xmp.

WOT said:

You are absolutely correct so I apologize for making that error; however, it still appears that you are running in turbo mode or advanced turbo mode.

Intel Turbo Boost Technology enables the processor to run above its base operating
frequency when the operating system requests the highest performance state.

In the OC Tweaker screen, you can set up overclocking features.

Advanced Turbo
You can use this option to increase your system performance. this option appears only when your CPU supports this function. This option appears only when you adopt K-Series CPU.

Yeah. Problem is that mine boost up to like 4.5mhz and its turbo speed goes to like 4.4mhz.
That whea logger thing got me a bit con erned and is there a way that the boost can boost to like its rated speeds not at 4.5mhz?

I'm not planning to overclock it though. With that whea error thing got me worried.

WOT said:

Did you check to see if one or both of those options were enabled? I added a screenshot (first post) to show you where one of them is?

Yup, i checked it and turbo boost is definitely enabled and load optimized cpu oc setting has been disabled.

I'd just realized something. Last night, before the whea logger error showed up, I downloaded a program called BlueStacks and I installed and launched it while World of Warcraft was running (since im in the middle of the raid). I could've sworned that mightve been related to bluestacks since I've havent started seeing it until this. Something tells me that some people may get that problem when when running on an android emulator such as bluestacks. You know later on I'll try to run WoW and running a light game known as Osu to see if that error pops out. Lets hope no instabilities in this one. *crosses fingers*

You know, it might not be related to my cpu because of this error and I hope its bluestacks.

WOT said:

Good luck.

Thank you and thank you for the help! :)
And I just ran BlueStacks again and the Whea error showed up again. So I'm possitive that its that program but once I played some WoW tonight and if its stable enough, I will confirmed it. I will update this too.

Update: Well, after 4 hours of WoW and Osu! last night, no new event id 19 whea-logger errors. All I have to say is all those errors goes to BlueStacks. Those only occurred after I launch BlueStacks on startup. If I launch BlueStacks again, I don't see any of it. Also, I check the details of all the whea-errors and all of those are the same.

Code:

Log Name:      SystemSource:        Microsoft-Windows-WHEA-LoggerDate:          5/8/2017 9:14:11 AMEvent ID:      19Task Category: NoneLevel:         WarningKeywords:      User:          LOCAL SERVICEComputer:      DefaultDescription:A corrected hardware error has occurred.Reported by component: Processor CoreError Source: Corrected Machine CheckError Type: Internal parity errorProcessor APIC ID: 4The details view of this entry contains further information.Event Xml:<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="2017-05-08T13:14:11.462827400Z" />    <EventRecordID>5076</EventRecordID>    <Correlation ActivityID="{C483E947-C8FF-4549-97FB-76F4E1F5C0E6}" />    <Execution ProcessID="2896" ThreadID="3528" />    <Channel>System</Channel>    <Computer>Default</Computer>    <Security UserID="S-1-5-19" />  </System>  <EventData>    <Data Name="ErrorSource">1</Data>    <Data Name="ApicId">4</Data>    <Data Name="MCABank">0</Data>    <Data Name="MciStat">0x90000040000f0005</Data>    <Data Name="MciAddr">0x0</Data>    <Data Name="MciMisc">0x0</Data>    <Data Name="ErrorType">12</Data>    <Data Name="TransactionType">256</Data>    <Data Name="Participation">256</Data>    <Data Name="RequestType">256</Data>    <Data Name="MemorIO">256</Data>    <Data Name="MemHierarchyLvl">256</Data>    <Data Name="Timeout">256</Data>    <Data Name="OperationType">256</Data>    <Data Name="Channel">256</Data>    <Data Name="Length">864</Data>    <Data Name="RawData">435045521002FFFFFFFF03000200000002000000600300000A0E0D00080511140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F890A4FA7A70F5C7D20100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000400000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000058020000080100000003000000000000011D1E8AF94257459C33565E5CC3F7E80000000000000000000000000000000002000000000000000000000000000000000000000000000057010000000000000002080000000000C30603000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000400000000000000C306030000081004BFFBFA7FFFFBEBBF00000000000000000000000000000000000000000000000000000000000000000100000001000000B1971FFBFCC7D20104000000000000000000000000000000000000000000000005000F0040000090000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>  </EventData></Event>

What I also found is that I found that these errors seem to be benign and can be safely ignored. Not sure if this affects the 4790k processors. If anyone finds this correct, then I'm kinda good. Here is the link:

WHEA Event ID 19 CPU-corrected hw error / i5 4690 |Intel Communities