<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Notes about NMI_HARDWARE_FAILURE</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2006/12/23/notes-about-nmi_hardware_failure/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Tue, 05 May 2026 16:02:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/12/23/notes-about-nmi_hardware_failure/#comment-194150</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Mon, 18 Oct 2010 09:35:49 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/12/23/notes-about-nmi_hardware_failure/#comment-194150</guid>
		<description>It looks like an ASCII string "TDO"

1: kd&gt; .formats 4f4454
Evaluate expression:
  Hex:     00000000`004f4454
  Decimal: 5194836
  Octal:   0000000000000023642124
  Binary:  00000000 00000000 00000000 00000000 00000000 01001111 01000100 01010100
  Chars:   .....ODT
  Time:    Mon Mar 02 03:00:36 1970
  Float:   low 7.27952e-039 high 0
  Double:  2.56659e-317</description>
		<content:encoded><![CDATA[<p>It looks like an ASCII string &#8220;TDO&#8221;</p>
<p>1: kd> .formats 4f4454<br />
Evaluate expression:<br />
  Hex:     00000000`004f4454<br />
  Decimal: 5194836<br />
  Octal:   0000000000000023642124<br />
  Binary:  00000000 00000000 00000000 00000000 00000000 01001111 01000100 01010100<br />
  Chars:   &#8230;..ODT<br />
  Time:    Mon Mar 02 03:00:36 1970<br />
  Float:   low 7.27952e-039 high 0<br />
  Double:  2.56659e-317</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/12/23/notes-about-nmi_hardware_failure/#comment-193465</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Fri, 15 Oct 2010 19:27:40 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/12/23/notes-about-nmi_hardware_failure/#comment-193465</guid>
		<description>Can you shed any light on this?  I cannot find out the meaning of parameter1 for a "BugCheck 80", but am hoping it can give us a clue.

BugCheck 80, {4f4454, 0, 0, 0}

*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+3b42 )

Followup: MachineOwner
---------

nt!RtlpBreakWithStatusInstruction:
fffff800`01026c80 cc              int     3

Regards,

Tim</description>
		<content:encoded><![CDATA[<p>Can you shed any light on this?  I cannot find out the meaning of parameter1 for a &#8220;BugCheck 80&#8243;, but am hoping it can give us a clue.</p>
<p>BugCheck 80, {4f4454, 0, 0, 0}</p>
<p>*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys<br />
Probably caused by : intelppm.sys ( intelppm+3b42 )</p>
<p>Followup: MachineOwner<br />
&#8212;&#8212;&#8212;</p>
<p>nt!RtlpBreakWithStatusInstruction:<br />
fffff800`01026c80 cc              int     3</p>
<p>Regards,</p>
<p>Tim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Reflecting on 2008 (Part 1)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/12/23/notes-about-nmi_hardware_failure/#comment-119535</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Reflecting on 2008 (Part 1)</dc:creator>
		<pubDate>Wed, 27 Jan 2010 00:48:43 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/12/23/notes-about-nmi_hardware_failure/#comment-119535</guid>
		<description>[...] exception information can be accessed via .ecxr. windbg tips 0&#215;80070026 dmitri windbg gdb teb nmi_hardware_failure system_thread_exception_not_handled system_thread_exception_not_handled (7e) windbg command pool allocations have failed receivelotsacalls trap frame vista dr watson bios [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] exception information can be accessed via .ecxr. windbg tips 0&#215;80070026 dmitri windbg gdb teb nmi_hardware_failure system_thread_exception_not_handled system_thread_exception_not_handled (7e) windbg command pool allocations have failed receivelotsacalls trap frame vista dr watson bios [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 13f)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/12/23/notes-about-nmi_hardware_failure/#comment-61533</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 13f)</dc:creator>
		<pubDate>Mon, 05 Jan 2009 12:20:52 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/12/23/notes-about-nmi_hardware_failure/#comment-61533</guid>
		<description>[...] in running threads, the first one is a normal memory access fault (blue) and the other is forced NMI bugcheck to save a memory dump [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] in running threads, the first one is a normal memory access fault (blue) and the other is forced NMI bugcheck to save a memory dump [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: !analyze -v : Notes about NMI_HARDWARE_FAILURE</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/12/23/notes-about-nmi_hardware_failure/#comment-59174</link>
		<dc:creator>!analyze -v : Notes about NMI_HARDWARE_FAILURE</dc:creator>
		<pubDate>Thu, 11 Dec 2008 04:52:30 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/12/23/notes-about-nmi_hardware_failure/#comment-59174</guid>
		<description>[...] 이 문서는 http://www.dumpanalysis.org/blog blog 의 번역이며 원래의 자료가 통보 없이 변경될 수 있습니다. 이 자료는 법률적 보증이 없으며 의견을 주시기 위해 원래의 blog 를 방문하실 수 있습니다. (http://www.dumpanalysis.org/blog/index.php/2006/12/23/notes-about-nmi_hardware_failure/)&#34; [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] 이 문서는 <a href="http://www.dumpanalysis.org/blog" rel="nofollow">http://www.dumpanalysis.org/blog</a> blog 의 번역이며 원래의 자료가 통보 없이 변경될 수 있습니다. 이 자료는 법률적 보증이 없으며 의견을 주시기 위해 원래의 blog 를 방문하실 수 있습니다. (http://www.dumpanalysis.org/blog/index.php/2006/12/23/notes-about-nmi_hardware_failure/)&quot; [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
