New Build, 8320 @ 4.0Ghz tossing Whea Logger 19 error

Toggle sidebar Toggle sidebar
O

OverclockingNoob

Honorable
Dec 11, 2013
4
0
10,510
Hey guys, started a new build, and I've noticed event viewer tossing up multiple Whea Logger Event 19 errors.

This has started ever since the CPU was overclock, and the system seems stable. I've had no crashes, and no other issues, beyond BF4 crashing, which seems to tie into those errors, but then again BF4 crashes heavily on its own.

The CPU is not being heavily overclocked, only to 4Ghz off the stock 3.5, and at stock voltage with no other setting being touched. While Prime95 has only had a 3 hour run, it detected zero problems, and during those 3 hours, temps never exceeded 40c, and under gaming loads, it never breeches that mark either.

Is there something else that could be causing this? I have memtest ready to run overnight on the chance it may be RAM, but im looking into all options to make sure the CPU isn't at fault. Listed the specs as well if it helps.

Thanks for any advice!

Asrock Extreme4 990FX
AMD 8320 @ 4Ghz
Corsair H100i Cooler
G Skill Ripjaw DDR3 1333 - 16GB
Corsair 750w PSU
 
Sort by date Sort by votes
O

OverclockingNoob

Honorable
Dec 11, 2013
4
0
10,510


No other issues that I've seen. The Whea Logger doesn't seem to cause any problems, but I want to try and be proactive on my first real try at overclocking. Stock clocking is my plan for tomorrow to see what happens however.

 
Upvote 0 Downvote
arges86

arges86

Distinguished
Aug 31, 2008
1,775
0
20,360
So Microsoft says:
Some of the main hardware problems which cause machine check exceptions include:

  • ■System bus errors (error communicating between the processor and the motherboard)
    ■Memory errors that may include parity and error correction code (ECC) problems. Error checking ensures that data is stored correctly in the RAM; if information is corrupted, then random errors occur.
    ■Cache errors in the processor; the cache stores important data and code. If this is corrupted, errors often occur.
    ■Poor voltage regulation (i.e. power supply problem, voltage regulator malfunction, capacitor degradation)
    ■Damage due to power spikes
    ■Static damage to the motherboard
    ■Incorrect processor voltage setting in the BIOS (too low or too high)
    Overclocking
    ■Permanent motherboard or power supply damage caused by prior overclocking
    ■Excessive temperature caused by insufficient airflow (possibly caused by fan failure or blockage of air inlet/outlet)
    ■Improper BIOS initialization (the BIOS configuring the motherboard or CPU incorrectly)
    ■Installation of a processor that is too much for your motherboard to handle (excessive power requirement, incompatibility)
    ■Defective hardware that may be drawing excessive power or otherwise disrupting proper voltage regulation

So, I'd remove the overclock, and start over, increasing slowly.
Also, when i run Prime95 for stability, I run it for 24 hours, not just 3
 
Upvote 0 Downvote
O

OverclockingNoob

Honorable
Dec 11, 2013
4
0
10,510



I fully understand running Prime95 for longer, and its been on my to do list, but hard for me to stick the PC in a test for a whole day when I'm constantly using it for a multitude of projects. Its on my to do list.

I did get a chance to run Memtest overnight, and with 7 hours in, its showing 17 errors so far, could this be causing the errors? I've seen several others with similar issues, and the RAM being the culprit, but not sure why the processor would kick up errors.

As for the rest of the article, I have updated the drivers, and bios, and temperatures are not an issue. I will remove the overclock this evening after work as well to test. If the overclock is the issue, is there anything that can be changed or modified to eliminate the error? I have tried messing with the voltage in small increments, but no differences. As it stands, I've only changed the multiplier and nothing else with the overclock.
 
Upvote 0 Downvote
O

OverclockingNoob

Honorable
Dec 11, 2013
4
0
10,510
As an update to the post, reversing the overclock ceased the error, so it is tied to the overclock. 18 hours of Memtest showed 34 errors total over 5 passes, which will need to be looked into.

I have tried playing with the power options for the board, and that didn't seem to be the issue. Im assuming ill need to play with the settings more to figure it out, as I don't have a clue what would be tripping the error.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom