WHEA Warnings? (Event Viewer)

[ren3gade]

I OC'd my 3770k to 4.5GHz on 1.18v today. I ran prime95 blend for about an hour, and ADIA64 for 15 minutes, and temps never went over 75. But I got some WHEA-Logger warnings when running prime95...

A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 1

The details view of this entry contains further information.

Should I be worried?

 

[Y0GI]

I OC'd my 3770k to 4.5GHz on 1.18v today. I ran prime95 blend for about an hour, and ADIA64 for 15 minutes, and temps never went over 75. But I got some WHEA-Logger warnings when running prime95...

A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 1

The details view of this entry contains further information.

Should I be worried?

Looks like you have an unstable OC. Try increasing Vcore in 0.20 v. steps up to a maximum of 1.40 v. You should not need 1.40 v. but that is the max. You prolly need 1.250 v. to 1.28 v.

Yogi

 

[ren3gade]

I OC'd my 3770k to 4.5GHz on 1.18v today. I ran prime95 blend for about an hour, and ADIA64 for 15 minutes, and temps never went over 75. But I got some WHEA-Logger warnings when running prime95...

A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 1

The details view of this entry contains further information.

Should I be worried?

Looks like you have an unstable OC. Try increasing Vcore in 0.20 v. steps up to a maximum of 1.40 v. You should not need 1.40 v. but that is the max. You prolly need 1.250 v. to 1.28 v.

Yogi

Yogi, I bumped my voltage to 1.2v yesterday (from 1.8) and I ran Prime95 SFFs for 10 minutes, as well as AIDA64 for 10-15 minutes, and I didn't get any WHEA Warnings within Event Viewer like I was before. I will continue monitoring event viewer, but it appears that bumping up to 1.2v did the trick