PSOD

[Acsysam]

Hello everyone,

I have an issue with my server i was hoping you could help me with.

On my server screen i get this 0 :00 :29 :03.749. cpu0 : 1024)APIC :1470 : APICID 0X00 –ESR – 0X40 after leaving 2 or 3 virtuals machines on at the same time.

I also get sometimes the PSOD and i read somewhere that you could see where the problem was by "looking"

So here it is...(in attachement)

Hope you guys can help

thx

[hitchhiker]

open a support ticket if you can.

[gorto]

This dude has a Bad hex decoding function, but your PSOD doesn't appear to return a bad hex

VMkernel Error Decoder

This decoder can take either decimal, or hexidecimal error codes in the format of 0x0bad0000. There errors can appear in /var/log/vmkwarning, /var/log/vmkernel and sometimes in the vmware.log of a specific vmware virtual machine. Thanks to Mike Nisk for providing me with all of the data in an easy to import format.

Error in hex:

0xbad xy

[Texiwill]

Hello,

PSODs are usually caused by hardware. I would:

1) Open up the box and look for obvious issues (loose heatsinks)

2) Check the BIOS to see if it is configured properly

3) Run full vendor hardware diags w/o disk timeout tests for 24-48 hours

4) Run memtest86+ for 24-48 hours

Generally if it is hardware these will find it.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

[Acsysam]

Hello everyone and thank you for your replies.

I checked my connections by creating a new server on another physical machine that has the same hardware.Same problems came up.

So i then checked the BIOS where i changed the "ACPI Suspend type" from "S1(POS)" : to power on suspend under ACPI OS to "S3(STR)" : to suspend to RAM under ACPI OS and things where better--> no more PSOD but still have the warnings on my screen server " cpu0 1024 APIC :1470 ..."

To test if the problem would come up i gave my server a rough time--> 3 VMs on simultaniously+ a 4th which was installing windows .They each have 512 MB of RAM...too little ?

Anything else i should change in the BIOS ??

By the waz this is my hardware list:

- Motherboard Gigabyte GA-MA78GM-S2H

- Processeur AMD Phenom x4

- RAM Kingston 2x2Gb

- 2 hard drives SCSI Hitachi (2x70Gb)

- Network Adaptor Intel Pro/100GT

- 1 carte LSI SATA/RAID controller (LSISAS1064E)

Anything not compatible?

THx a lot for your help

[RParker]

> PSODs are usually caused by hardware. I would:

> 1) Open up the box and look for obvious issues (loose heatsinks)

> 2) Check the BIOS to see if it is configured properly

> 3) Run full vendor hardware diags w/o disk timeout tests for 24-48 hours

> 4) Run memtest86+ for 24-48 hours

5) update the BIOS and Hardware firmware.

If above steps don't work, reinstall ESX (preserving VMFS).

[Texiwill]

Hello,

I would also use Hardware that is on the HCL, but if your whitebox works then go for it. Just note, it is not supported for many reasons.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

[Acsysam]

Hey everybody !

THx a lot for your suggestions.i'm afraid my problem is still here but i give up,since everything works..for now at least .

Depending on the change i made i sometimes got the "famous" red warning without even starting Virtual Center !!

Thx again

[dtoubelis]

I'm getting same message and my hardware is similar:

• Motherboard Gigabyte GA-MA790GP-DS4H

• CPU AMD Phenom x4 9950

• Kingston 2x4GB ECC RAM

• 3Ware 9650-4LP SATA RAID

I wonder if it is specific to this CPU or motherboard or even memory. On the other hand it appears it does no other harm then throwing red console message. Just my 2 cents...