Operating System - Linux
1827293 Members
2793 Online
109717 Solutions
New Discussion

Uhhuh. NMI received. Dazed and confused

 
Eric MCP
New Member

Uhhuh. NMI received. Dazed and confused

This message was occuring on a Proliant DL580 server. After running Smartstart Diagnostics, the ram and cpu checked out ok. I also booted with HP Proliant Firmware CD (version 7.91), and updated the BIOS for the RAID controllers, hard drives, and system ROM (with the correct supplemental file download to a floppy) after finding the following on HP's knowledge base (take out spaces)

h t t p s : / / w w w 13 . itrc . hp . c o m /service/cki/docDisplay.do?docId=emr_na-c01583480&docLocale=en&admit=109447627+1248981631870+28353475

although my server was not a "G5". This didnt hurt anything, but the server still had the warning message and annoying ever-increasing lockups. It turned out to be a failing network card. After removing the existing network card, and installing a different one the

"Uhhuh. NMI received. Dazed and confused, but trying to continue
You probably have a hardware problem with your RAM chips"

messages have stopped, as well as the server lockups. It was an intermittent hardware failure, which eventually started taking the server down with 10 minutes of booting. Im glad its finally resolved now. I suggest removing any any unecessary hardware from any computer with this error, and if that doesnt elminate the problem - try swapping any hardware you can til you isolate the problem. Although it "suggests" RAM to be the cause - its not always the system RAM....

Good luck
2 REPLIES 2
Siert Zijl
Advisor

Re: Uhhuh. NMI received. Dazed and confused

I've seen this behaviour by using the deprecated st.o instead of sg.o with backups.

After switchting to sg.o the problem was solved.
Linux system administrator
Viktor Balogh
Honored Contributor

Re: Uhhuh. NMI received. Dazed and confused