Quantcast
Channel: PowerEdge General HW Forum - Recent Threads
Viewing all articles
Browse latest Browse all 5887

CPU0704 CPU1/CPU2 Machine check error detected on Front LCD Panel

$
0
0

We have an R730 that has been powercycling on it's own with a recurring amber front LCD with a CPU0704 CPU1(and CPU2) Machine check error detected. Power cycle system" message.

This first occured after the initial Windows Server 2012r2 load, Dell BIOS/Drivers/Firmware updates, McAfee, and Windows updates. We initially saw this once a week and it has occured more and more frequently, currently several times a day.

In the Windows Systems Event log these are registering as kernel power failures and the Lifecycle Controller logs show multiple(dozens) instances of "An OEM diagnostic event occured." within a couple of seconds preceded by the same CPU1/CPU2 machine check error.

Upon contacting Dell support we were asked to provide a DSET or TSR several times (despite a search returning that DSET has been retired and and TSR has been replaced with SupportAssist). Due to our environment limitations, the only way we are able to connect externally is via proxy and iDRAC doesn't support proxy configurations. We have tried running a Dell Tech recommended Support Live Image, and only to have our system reboot before being able to complete diagnostics.

Requesting CPU and motherboard replacements via Dispatch after referring efforts to the initial Service Request were denied asking us to update BIOS and selected firmware (which we did initially) and again asking for a DSET.

We're currently in communications to let support know we've already done this and feel like we've exhausted our options at this point. A search in forums indicate that BIOS updates or CPU replacements have worked in most cases -- as the BIOS is current. Just wondering if anyone else has come across this issue and has any recommendations.


Viewing all articles
Browse latest Browse all 5887

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>