Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

HPE Gen10 servers fails with PSOD Machine Check Exception: Fatal (unrecoverable) MCE (52261)

Last Updated: 12/18/2019Categories: TroubleshootingTotal Views: 12697Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

HPE Gen10 servers running ESXi 6.0.x fails with PSOD  Machine Check Exception: Fatal (unrecoverable) MCE randomly.

PSOD backtrace looks similar:

2017-10-01T02:40:01.688Z cpu50:55173)Backtrace for current CPU #50, worldID=55173, rbp=0x0
2017-10-01T02:40:01.688Z cpu50:55173)0x43947c29bcf8:[0x418039b0515a]Power_HaltPCPU@vmkernel#nover+0x1ee stack: 0x417ff9a83f20, 0x41804c9
2017-10-01T02:40:01.688Z cpu50:55173)0x43947c29bd48:[0x418039a12078]CpuSchedIdleLoopInt@vmkernel#nover+0x2f8 stack: 0x21aaa22dde9e0, 0x1
2017-10-01T02:40:01.688Z cpu50:55173)0x43947c29bdc8:[0x418039a157d3]CpuSchedDispatch@vmkernel#nover+0x16b3 stack: 0x43927eaa7100, 0x0, 0
2017-10-01T02:40:01.688Z cpu50:55173)0x43947c29bee8:[0x418039a16398]CpuSchedWait@vmkernel#nover+0x240 stack: 0x41003b4acde0, 0x0, 0xa000
2017-10-01T02:40:01.688Z cpu50:55173)0x43947c29bf68:[0x418039a164ea]CpuSched_VcpuHalt@vmkernel#nover+0x11e stack: 0xffffffff00002001, 0x
2017-10-01T02:40:01.688Z cpu50:55173)0x43947c29bfb8:[0x4180398ac529]VMMVMKCall_Call@vmkernel#nover+0x139 stack: 0x4180398ac074, 0x0, 0x4
2017-10-01T02:40:01.712Z cpu50:55173)ESC[45mESC[33;1mVMware ESXi 6.0.0 [Releasebuild-5572656 x86_64]ESC[0m
Machine Check Exception: Fatal (unrecoverable) MCE on PCPU50 in world 55173:vmm0:fvst-ca System has encountered a Hardware Error - Please contact the hardware vendor

ESXi6.0.x installation may also fail with an error as shown in screenshot

Note:The preceding log excerpts are only examples.Date,time and environmental variables may vary depending on your environment.

Cause

ESXi  was mapping 8 GB above the top of memory which allows the  CPU to touch addresses above the top of memory and causing the failure.

Resolution

To resolve this issue upgrade to VMware ESXi ,Patch release ESXi-6.0.0-20171104001 or later.
For more information refer to the HPE customer advisory

Disclaimer:VMware is not responsiblee for the reliability of any data,opinions,advice or statements made on third-party websites.Inclusion of such links does not imply that VMware endorses,recommends or accepts any responsibility for the content of such sites

Workaround

To workaround this  Go HPE RBSU and set the memory to be at 1TB. Contact HPE Support for more information.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vSphere 6.5 およびその互換性のある VMware 製品の更新手順 (2147289)

KB
•
vCenter Server Appliance または Platform Service Controller の dnsmasq.log ファイルが原因で root パーティションがいっぱいである (52258)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.0

Take Our Survey

Support Assistant