Meaning of Event ID 18 from WHEA-Logger in Win7?...

[mapesdhs]

While fixing a friend's PC (they had a login problem, all sorted out), I noticed numerous
Event ID 18 errors in the Windows log (Win7 Pro 64bit).

I've done a lot of forum site reading, found all sorts of suggestions concerning potential hw
issues, drivers, etc., but nothing so far has helped. Now I'm wondering if it really matters.

I'm a reasonably experienced oc'er, but this build is just a stock-speed basic setup (nothing
within was ever oc'd): ASUS M2N-VM DVI, Athon64 X2 6000+, 4GB (4x1 DDR2/800), 8800GT
(temporarily a GTX 460 instead for testing), 120GB SSD, a couple of rust spinners (250GB +
500GB), standard 700W PSU.

Exploring possible hw issues, the only thing I noticed was the -12V in HWMonitor is shown
as only approx. -6V; I tried with a completely different PSU but it still shows up this way. Does
this matter? Note the system has never thrown a BSOD or exhibited any other obvious fault
like a freeze or sudden shutdown.

Thoughts anyone? Perhaps the mbd has a fault? All the fans are working ok, including the
stock CPU fan. System is dust-free, etc. I checked the 8800GT with a Z68 setup, works fine.
Running 3D apps with a temp GTX 460 doesn't cause any issues. Am about to try memtest...

Ian.

 

[MarkW]

Applies to:

Windows Server 2008, Windows Vista, Windows Server 2008 R2, Windows 7

Details
Product: Windows Operating System
Event ID: 18
Source: Microsoft-Windows-WHEA-Logger
Version: 6.1
Symbolic Name: Boot Performance Monitoring
Message: A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Unknown Error
Processor ID: 1

The details view of this entry contains further information.


Explanation

This error indicates that there is a hardware problem. A machine check exception indicates a computer hardware error that occurs when a computer's central processing unit detects a hardware problem.

Note: WHEA stands for Windows Hardware Error Architecture.

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


User Action
Update the BIOS and the drivers for the motherboard chipset.
Update all the hardware drivers, if updates are available from your manufacturer.
Check the temperature inside the computer to make sure your processor and related peripherals are not overheating.
Check the fan on your CPU to make sure it is properly attached to the CPU.
If you have overclocked your CPU, reset your settings to the default settings.
Make sure you power supply fan is working correctly

 

[mapesdhs]

Thanks for the reply!

That's the first article one comes across when Googling, but alas it's of no real
help, too vague. I've already trawled through dozens of forum posts, still nothing
relevant for a fix. The trouble with the MS piece is it asserts there must be a
problem, but elsewhere their other articles say the error can occur when really
there might be nothing seriously wrong, so it's hard to know for sure.

Like I said, all aspects of drivers, BIOS, temps, oc'ing (none used), updates, etc.
already checked & tested ok. The only thing which looks out of place is that -12V
voltage reading in HWMonitor, but using a different PSU made no difference. If
it mattered though, odd that running any kind of benchmark doesn't cause a
pproblem like a crash or freeze.

Ian.

 

[MarkW]

Try reseting the BIOS to default values. You may well have to reset some options after doing this, but reset to default, save and power down. Unplug from the wall and let it sit for a minute. Then power back up and go back into the BIOS and set your boot order, save again and see if that changes anything. Might take a few days to see if no new entries are added to the event logs.

 

[mapesdhs]

Ok, I'll give that a whirl (apart from of course setting the SATA ports
to AHCI mode, that's essential).

Ian.