Windows Server 2003 system error

[Damodred]

Hello

I think Im in a need of assistance :( Last couple of days Ive got some problems with something. Programs and games not really crashing but I get a message from time to time in the Event Viewer called WMIxWDM and then EventID 106. I can also read
"Symbolic Name: MCA_WARNING_UNKNOWN_NO_CPU
Message: Machine Check Event reported is a corrected error"

NOw the computer doesnt die on me or anything but programs tend to jump back into Windows (unless I I run a windowed mode ofcourse, then I just get the message). I can run Prime95 and Memtest86 without any problems except the message.

Searching at MS Support I find this:

"RESOLUTION
To resolve this issue, you must read the data at the bottom of the event ID to determine the number of the CPU that reported the Machine Check Architecture exception. For example, event ID 107 may contain the following data:

0000: 01 00 00 00 01 00 00 00 ........
0008: 4a d3 bd a4 be b4 c4 01 JÓ½¤¾´Ä.
0010: 02 00 00 00 00 00 00 00

The offset 0010 reveals the number of the CPU that reported the Machine Check Architecture exception. In this example, the CPU that caused the exception is CPU number 2."


In my case it says
"0010: 00 00 00 00 00 00 00 00" which would mean its cpu 0...I dont get it, whats wrong with my system?

Thanks in advance :)

[Jay_oasis]

this an AMD system?

if so do you still need to install the CPU drivers?

http://support.microsoft.com/kb/889249

[Damodred]

Hmm I dont know, I made the installation two years back from now and can hardly remember it. Its not until late it has started to show so I figured it should be some sort of hardware error. But I will take a look at the cpu software.

[zacdl]

From what it looks like, it could be BIOS, as MS says in this KB article: http://support.microsoft.com/kb/895560

Might try flashing your BIOS.

If you would have kept reading in that KB article you quoted, you would have found this:

After you have determined the number of the CPU that reported the Machine Check Architecture exception, contact the manufacturer of the CPU to determine how to troubleshoot the issue.
Meaning it could very well be a driver. Check AMD's website for updated drivers.

[Damodred]

Turned out that it was some complication with the ram. After clearing the bios and made sure it was stable at default speeds I then overclocked back to my old overclock setup and now it works again. Guess there are too many settings on the DFI Lanpartys :)

Thanks all!

[Nasty_Savage]

You overclock a machine running server 2003? :D

[Damodred]

haha yea. Actually two computers running Win 2003 Standard are fairly overclocked (and 100% stable). The WS in sign is overclocked from 200HTT to 300HTT, running memory at 270FSB and the FS is running at 250HTT with synced ram. Best thing is, the WS is a real beast when it comes to the cpu. I actually lowered the volt to the cpu from 1.4v to 1.375 and its still rockstable (prime95 and 3dmark03 running for 48 hours). Been like this for the last two years now.