Two Minute Drill: NMI

re: Two Minute Drill: NMI

Jason — Sat, 05 Jan 2013 11:37:53 GMT

I have a HP ProLiant DL385 G5 with ILO 2 and it refused to create the memory.dmp when performing the NMI. The reg has been set correctly, HP have replaced the motherboard, firmware and psp is up to date. It's driving my crazy! The server is able to create a memory.dmp when using NotMyFault.exe /crash so I don't believe it is an OS issue. Just don't know what else I can do. Any suggestions?

re: Two Minute Drill: NMI

AdamT — Mon, 13 Feb 2012 10:01:22 GMT

Three years later, and I found out what caused my phantom 0xDEADDEAD bugcheck. It's the bugcheck code used by Egenera hardware (EgenBmc.sys) when you issue an NMI to the system.

re: Two Minute Drill: NMI

Tim Newton - MSFT — Tue, 27 Jan 2009 19:12:31 GMT

Hi Adam,

Yes, 0xDEADDEAD is a possible bugcheck code you can get from a manually initiated crash, but it is not one I see very often. I did some digging on the internet and found a couple of other people who have gotten that STOP code due to a faulty driver. Apparently, debug code occasionally gets left in and can cause this type of issue if there is a driver fault. I would check and see if any new driver updates were installed any time recently. Hope this helps.

Tim Newton

re: Two Minute Drill: NMI

AdamT — Tue, 27 Jan 2009 03:48:29 GMT

Is 0xDEADDEAD not one of the bugcheck codes? If not - can you explain what may cause it?

I've encountered this bugcheck code, which is apparently manually initiated: http://msdn.microsoft.com/en-us/library/ms797162.aspx

- but yet the crash on ctrl+scroll key was not set, and the server was locked away in a rack, with no physical access recorded on the cameras.