- Mar 10, 2013
- 59
- 0
- 10,640
http://s23.postimg.org/zfu3fmm17/eventviewer_error_ID_19.png
event viewer giving me some errors. And i cleared the log, upped the volts, and prime is now running smooth and no choppiness when moving windows around fast (before it would lagg then sometimes crash explorer.exe while prime / IBT running)
Well even though im at 1.305 volts (cpu-z) and 1.2960 (AID64) i still get these errors while running prime. No more "RED!" errors but the yellow ones seem to be not good / related to overclocking.
I will tomorrow morning after prime passes testing while i sleep, remove the overclock, clear the log and using stock / a lower OC test the event viewer.
I just learned to look for WHEA errors while overclocking, though all seems stable i would like to not have these pop up. and every time an error code 19 pops up i get an "information" one pop up too with event id 7036 (below are some quotes that show up when i click each one)
the above 4 quotes come from the event id 7036 (though they don't seem important / may just be just a normal event logging)
but the event id 19 is the one im concerned with
(then if i view the friendly view details i get the below information)
after some research I've found that it relates to overclocking and that lowering the oc / upping the volts will fix it but im not that high of an overclock / no prime errors after 6 hours blend and 2 hours in place ftt (still going)
has anyone else found a fix for this that isn't upping the volts?
messing with the PLL volts? memory frequency being lowered from 1600 to 1333?
System specs
event viewer giving me some errors. And i cleared the log, upped the volts, and prime is now running smooth and no choppiness when moving windows around fast (before it would lagg then sometimes crash explorer.exe while prime / IBT running)
Well even though im at 1.305 volts (cpu-z) and 1.2960 (AID64) i still get these errors while running prime. No more "RED!" errors but the yellow ones seem to be not good / related to overclocking.
I will tomorrow morning after prime passes testing while i sleep, remove the overclock, clear the log and using stock / a lower OC test the event viewer.
I just learned to look for WHEA errors while overclocking, though all seems stable i would like to not have these pop up. and every time an error code 19 pops up i get an "information" one pop up too with event id 7036 (below are some quotes that show up when i click each one)
"The WinHTTP Web Proxy Auto-Discovery Service service entered the stopped state."
"The Diagnostic System Host service entered the stopped state."
"The Application Experience service entered the running state."
"The Tablet PC Input Service service entered the running state."
"The Diagnostic System Host service entered the stopped state."
"The Application Experience service entered the running state."
"The Tablet PC Input Service service entered the running state."
the above 4 quotes come from the event id 7036 (though they don't seem important / may just be just a normal event logging)
but the event id 19 is the one im concerned with
"A corrected hardware error has occurred.
Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor ID: 0
The details view of this entry contains further information. "
MciStat 0x9000004000010005
System
Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor ID: 0
The details view of this entry contains further information. "
MciStat 0x9000004000010005
System
(then if i view the friendly view details i get the below information)
Provider
[ Name] Microsoft-Windows-WHEA-Logger
[ Guid] {C26C4F3C-3F66-4E99-8F8A-39405CFED220}
EventID 19
Version 0
Level 3
Task 0
Opcode 0
Keywords 0x8000000000000000
- TimeCreated
[SystemTime] 2014-02-16T07:17:26.814105900Z
EventRecordID 67920
- Correlation
[ ActivityID] {4993E03A-DA30-46DA-9D22-B5AF59317BDE}
- Execution
[ ProcessID] 1760
[ ThreadID] 5816
[ Name] Microsoft-Windows-WHEA-Logger
[ Guid] {C26C4F3C-3F66-4E99-8F8A-39405CFED220}
EventID 19
Version 0
Level 3
Task 0
Opcode 0
Keywords 0x8000000000000000
- TimeCreated
[SystemTime] 2014-02-16T07:17:26.814105900Z
EventRecordID 67920
- Correlation
[ ActivityID] {4993E03A-DA30-46DA-9D22-B5AF59317BDE}
- Execution
[ ProcessID] 1760
[ ThreadID] 5816
after some research I've found that it relates to overclocking and that lowering the oc / upping the volts will fix it but im not that high of an overclock / no prime errors after 6 hours blend and 2 hours in place ftt (still going)
has anyone else found a fix for this that isn't upping the volts?
messing with the PLL volts? memory frequency being lowered from 1600 to 1333?
System specs
i5 3570K @ 4.5Ghz
asrock z77 extreme4
ZALMAN CNPS9700
RAM below
G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL9D-8GBRL
asrock z77 extreme4
ZALMAN CNPS9700
RAM below
G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL9D-8GBRL
Facebook
Twitter
Instagram