AMD Processors
Decrease font size
Increase font size
Topic Title: AMD opetron dual prosessor Tyan S2882 M/B
Topic Summary:
Created On: 05/23/2005 02:07 AM
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
View similar topics View similar topics
View topic in raw text format. Print this topic.
 05/23/2005 02:07 AM
User is offline View Users Profile Print this message

Author Icon
vinodkn
Junior Member

Posts: 2
Joined: 05/23/2005

Tyan M/B S2882 with 2 AMD Aptron processors.

Loaded the server with WINDOWS 2003 SERVER 64 BIT EDITION .
AFTER 3 DAYS GETTING THIS ERROR IN THE EVENT VIEWER.


/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif' /> Look in to this ASAP





Event Type: Warning

Event Source: WMIxWDM

Event Category: None

Event ID: 106

Date: 5/20/2005

Time: 3:30:50 PM

User: N/A

Computer: BEP

Description:

Machine Check Event reported is a corrected error.



For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp' ">http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 01 00 00 00 01 00 00 00 ........

0008: d1 6f 54 cd 22 5d c5 01 ÑoTÍ"]Å.

0010: 00 00 00 00 00 00 00 00 ........

0018: 00 00 00 00 00 00 00 00 ........

0020: 33 08 00 00 00 40 31 94 3....@1”

0028: 80 b9 91 6c 00 00 00 00 €¹‘l....

0030: 00 00 00 00 00 00 00 00 ........

0038: 00 00 00 00 00 00 00 00 ........

0040: 00 00 00 00 00 00 00 00 ........

0048: 00 00 00 00 00 00 00 00 ........

0050: 00 00 00 00 00 00 00 00 ........

0058: 00 00 00 00 00 00 00 00 ........

0060: 00 00 00 00 00 00 00 00 ........

0068: 00 00 00 00 00 00 00 00 ........

0070: 00 00 00 00 00 00 00 00 ........

0078: 00 00 00 00 00 00 00 00 ........

0080: 00 00 00 00 00 00 00 00 ........

0088: 00 00 00 00 00 00 00 00 ........

0090: 00 00 00 00 00 00 00 00 ........

0098: 00 00 00 00 00 00 00 00 ........

00a0: 00 00 00 00 00 00 00 00 ........

00a8: 00 00 00 00 00 00 00 00 ........

00b0: 00 00 00 00 00 00 00 00 ........

00b8: 00 00 00 00 00 00 00 00 ........

00c0: 00 00 00 00 00 00 00 00 ........

00c8: 00 00 00 00 00 00 00 00 ........

00d0: 00 00 00 00 00 00 00 00 ........

00d8: 00 00 00 00 00 00 00 00 ........

00e0: 00 00 00 00 00 00 00 00 ........

00e8: 00 00 00 00 00 00 00 00 ........

00f0: 00 00 00 00 00 00 00 00 ........

00f8: 00 00 00 00 00 00 00 00 ........



Explanation

A hardware error was resolved by your system. The type of error cannot be determined because the error record returned by the firmware is not in the required format. For detailed information about the hardware that caused the problem, refer to the event log.




Below link is for your reference.


http://support.microsoft.com/d...spx?...us;889249&sd=ee' ">http://support.microsoft.com/d...=kb;en-us;889249&sd=ee
 06/02/2005 03:41 PM
User is offline View Users Profile Print this message

Author Icon
FistiCuff
Junior Member

Posts: 19
Joined: 04/19/2005

90% of the time when the Event ID 106 is fired, it means that you have a bad stick of memory. Your system may begin to halt or freeze up as well. According to the MS Knowledgebase article you referenced, it looks like the faulty stick of memory is in the CPU0 bank.

Because the memory controller is built on to the CPU itself, the CPU could also be causing the error, but in my experience it is usually caused by a bad DIMM. The 106 event is a machine check that was corrected. If you see these errors more and more frequently, then you should start testing each DIMM in the system individually.

Regards,
FistiCuff
/blink.gif' border='0' style='vertical-align:middle' alt='blink.gif' />


-------------------------

FistiCuff can also be found at...
Multicore CPU Forum (AMD - IBM - Intel)' ">http://www.dualcoreforum.com
64-bit Application Architects' ">http://www.64bitprogrammers.com
 06/05/2005 12:01 PM
User is offline View Users Profile Print this message

Author Icon
derGhostrider
Case Modder

Posts: 1465
Joined: 04/04/2004

I did not check the ID at the MS homepage but I agree to FistiCuff.

You may also exchange all memory modules (first onto slot 4, second into slot 3, third into slot 2, fourth into slot 1) and check if the report changes to another slot.

Did you already check the BIOS-Event-Log for entries? Corrected ECC and/or non-corrected ECC-failures should be logged there, too.

Maybe you can also check the ECC and chipkill options and change both to enable to correct some more memory failures on the fly.

-------------------------
Regards,
  Ghostrider

·CPUs - 2*Opteron 246
·Mainboard - Tyan Thunder K8W S2885ANRF
·RAM - 4*Corsair TwinX1024RE-3200LL (4GB, 8*512MB, DDR400, 2-3-2)
·Graphics - HIS IceQ-II X800Pro
·HDD - Western Digital Raptor WD740GD, 74GB, 10k
·RAID - 3Ware 7850, 64bit PCI, 8chn hardware RAID
·RAID-HDDs - 5*WD800JB
·Optical - 1*SlimSize CD-ROM; 1*NEC7441 DVD-RW
·Sound - Creative SoundBlaster X-Fi Elite Pro

Statistics
112018 users are registered to the AMD Processors forum.
There are currently 0 users logged in.

FuseTalk Hosting Executive Plan v3.2 - © 1999-2014 FuseTalk Inc. All rights reserved.



Contact AMD Terms and Conditions ©2007 Advanced Micro Devices, Inc. Privacy Trademark information