Comments on: Crash Dump Analysis Patterns (Part 57) https://www.dumpanalysis.org/blog/index.php/2008/04/03/crash-dump-analysis-patterns-part-57/ Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics Sat, 30 May 2026 10:48:30 +0000 http://wordpress.org/?v=2.3.3 By: Dmitry Vostokov https://www.dumpanalysis.org/blog/index.php/2008/04/03/crash-dump-analysis-patterns-part-57/#comment-741750 Dmitry Vostokov Mon, 23 Apr 2018 19:49:09 +0000 https://www.dumpanalysis.org/blog/index.php/2008/04/03/crash-dump-analysis-patterns-part-57/#comment-741750 Recently we observed internal errors in Visual C++ compiler followed by memory management bugchecks a few seconds later. Recently we observed internal errors in Visual C++ compiler followed by memory management bugchecks a few seconds later.

]]> By: Dmitry Vostokov https://www.dumpanalysis.org/blog/index.php/2008/04/03/crash-dump-analysis-patterns-part-57/#comment-741720 Dmitry Vostokov Tue, 04 Oct 2016 17:28:23 +0000 https://www.dumpanalysis.org/blog/index.php/2008/04/03/crash-dump-analysis-patterns-part-57/#comment-741720 For WHEA_UNCORRECTABLE_ERROR (124) we have additional WinDbg commands !whea, !errrec, and !errpkt: 2: kd> !whea Error Source Table @ fffff8004bbd4a90 4 Error Sources Error Source 0 @ ffffe00014376bd0 Notify Type : {14374010-e000-ffff-984a-bd4b00f8ffff} Type : 0x0 (MCE) Error Count : 1 Record Count : 4 Record Length : 728 Error Records : wrapper @ ffffe000110e0000 record @ ffffe000110e0028 : wrapper @ ffffe000110e0728 record @ ffffe000110e0750 : wrapper @ ffffe000110e0e50 record @ ffffe000110e0e78 : wrapper @ ffffe000110e1578 record @ ffffe000110e15a0 Descriptor : @ ffffe00014376c29 Length : 3cc Max Raw Data Length : 141 Num Records To Preallocate : 4 Max Sections Per Record : 4 Error Source ID : 0 Flags : 00000000 [...] 2: kd> !errrec ffffe000110e0028 ============================================ Common Platform Error Record @ ffffe000110e0028 ------------------------------------------------------------------------------- Record Id : 01d21a1a7e5fffd1 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 9/30/2016 9:05:50 (UTC) Flags : 0x00000000 ============================================ Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe000110e00a8 Section @ ffffe000110e0180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Micro-Architectural Error Flags : 0x00 CPU Version : 0x00000000000306a9 Processor ID : 0x0000000000000002 ============================================ Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffe000110e00f0 Section @ ffffe000110e0240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000002 CPU Id : a9 06 03 00 00 08 10 02 - bf e3 ba 7f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffe000110e0240 ============================================ Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe000110e0138 Section @ ffffe000110e02c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal unclassified (Proc 2 Bank 4) Status : 0xb200000000100402 For WHEA_UNCORRECTABLE_ERROR (124) we have additional WinDbg commands !whea, !errrec, and !errpkt:

2: kd> !whea
Error Source Table @ fffff8004bbd4a90
4 Error Sources
Error Source 0 @ ffffe00014376bd0
Notify Type : {14374010-e000-ffff-984a-bd4b00f8ffff}
Type : 0×0 (MCE)
Error Count : 1
Record Count : 4
Record Length : 728
Error Records : wrapper @ ffffe000110e0000 record @ ffffe000110e0028
: wrapper @ ffffe000110e0728 record @ ffffe000110e0750
: wrapper @ ffffe000110e0e50 record @ ffffe000110e0e78
: wrapper @ ffffe000110e1578 record @ ffffe000110e15a0
Descriptor : @ ffffe00014376c29
Length : 3cc
Max Raw Data Length : 141
Num Records To Preallocate : 4
Max Sections Per Record : 4
Error Source ID : 0
Flags : 00000000
[…]

2: kd> !errrec ffffe000110e0028
============================================
Common Platform Error Record @ ffffe000110e0028
——————————————————————————-
Record Id : 01d21a1a7e5fffd1
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 9/30/2016 9:05:50 (UTC)
Flags : 0×00000000

============================================
Section 0 : Processor Generic
——————————————————————————-
Descriptor @ ffffe000110e00a8
Section @ ffffe000110e0180
Offset : 344
Length : 192
Flags : 0×00000001 Primary
Severity : Fatal

Proc. Type : x86/x64
Instr. Set : x64
Error Type : Micro-Architectural Error
Flags : 0×00
CPU Version : 0×00000000000306a9
Processor ID : 0×0000000000000002

============================================
Section 1 : x86/x64 Processor Specific
——————————————————————————-
Descriptor @ ffffe000110e00f0
Section @ ffffe000110e0240
Offset : 536
Length : 128
Flags : 0×00000000
Severity : Fatal

Local APIC Id : 0×0000000000000002
CPU Id : a9 06 03 00 00 08 10 02 - bf e3 ba 7f ff fb eb bf
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0 @ ffffe000110e0240

============================================
Section 2 : x86/x64 MCA
——————————————————————————-
Descriptor @ ffffe000110e0138
Section @ ffffe000110e02c0
Offset : 664
Length : 264
Flags : 0×00000000
Severity : Fatal

Error : Internal unclassified (Proc 2 Bank 4)
Status : 0xb200000000100402

]]> By: Dmitry Vostokov https://www.dumpanalysis.org/blog/index.php/2008/04/03/crash-dump-analysis-patterns-part-57/#comment-705659 Dmitry Vostokov Mon, 18 Feb 2013 22:30:26 +0000 https://www.dumpanalysis.org/blog/index.php/2008/04/03/crash-dump-analysis-patterns-part-57/#comment-705659 KERNEL_STACK_INPAGE_ERROR (77) The requested page of kernel data could not be read in. Caused by bad block in paging file or disk controller error. In the case when the first arguments is 0 or 1, the stack signature in the kernel stack was not found. Again, bad hardware. An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates the data could not be read from the disk due to a bad block. Upon reboot autocheck will run and attempt to map out the bad sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging file is on a SCSI disk device, then the cabling and termination should be checked. See the knowledge base article on SCSI termination. Arguments: Arg1: 0000000000000001, (page was retrieved from disk) Arg2: fffffa800818e870, value found in stack where signature should be Arg3: 0000000000000000, 0 Arg4: fffff8800c6e5e80, address of signature on kernel stack 2: kd> k Child-SP RetAddr Call Site fffff880`0371da18 fffff800`03110b01 nt!KeBugCheckEx fffff880`0371da20 fffff800`030c8c54 nt! ?? ::FNODOBFM::`string'+0x51e31 fffff880`0371db30 fffff800`030c8bef nt!MmInPageKernelStack+0x40 fffff880`0371db90 fffff800`030c8928 nt!KiInSwapKernelStacks+0x1f fffff880`0371dbc0 fffff800`0332be5a nt!KeSwapProcessOrStack+0x84 fffff880`0371dc00 fffff800`03085d26 nt!PspSystemThreadStartup+0x5a fffff880`0371dc40 00000000`00000000 nt!KiStartSystemThread+0x16 KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: 0000000000000001, (page was retrieved from disk)
Arg2: fffffa800818e870, value found in stack where signature should be
Arg3: 0000000000000000, 0
Arg4: fffff8800c6e5e80, address of signature on kernel stack

2: kd> k
Child-SP RetAddr Call Site
fffff880`0371da18 fffff800`03110b01 nt!KeBugCheckEx
fffff880`0371da20 fffff800`030c8c54 nt! ?? ::FNODOBFM::`string’+0×51e31
fffff880`0371db30 fffff800`030c8bef nt!MmInPageKernelStack+0×40
fffff880`0371db90 fffff800`030c8928 nt!KiInSwapKernelStacks+0×1f
fffff880`0371dbc0 fffff800`0332be5a nt!KeSwapProcessOrStack+0×84
fffff880`0371dc00 fffff800`03085d26 nt!PspSystemThreadStartup+0×5a
fffff880`0371dc40 00000000`00000000 nt!KiStartSystemThread+0×16

]]> By: Dmitry Vostokov https://www.dumpanalysis.org/blog/index.php/2008/04/03/crash-dump-analysis-patterns-part-57/#comment-682386 Dmitry Vostokov Tue, 22 Jan 2013 23:48:26 +0000 https://www.dumpanalysis.org/blog/index.php/2008/04/03/crash-dump-analysis-patterns-part-57/#comment-682386 Another example is this: <p align="left"><font size="1"><code><pre>WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: fffffa8004b46748, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.</pre></code></font></p> <p align="left"><font size="1"><code><pre>1: kd> dt -r _WHEA_ERROR_RECORD fffffa8004b46748 hal!_WHEA_ERROR_RECORD +0x000 Header : _WHEA_ERROR_RECORD_HEADER +0x000 Signature : 0x52455043 +0x004 Revision : _WHEA_REVISION +0x000 MinorRevision : 0x10 '' +0x001 MajorRevision : 0x2 '' +0x000 AsUSHORT : 0x210 +0x006 SignatureEnd : 0xffffffff +0x00a SectionCount : 3 +0x00c Severity : 1 ( WheaErrSevFatal ) +0x010 ValidBits : _WHEA_ERROR_RECORD_HEADER_VALIDBITS +0x000 PlatformId : 0y0 +0x000 Timestamp : 0y1 +0x000 PartitionId : 0y0 +0x000 Reserved : 0y00000000000000000000000000000 (0) +0x000 AsULONG : 2 +0x014 Length : 0x3a0 +0x018 Timestamp : _WHEA_TIMESTAMP +0x000 Seconds : 0y00100010 (0x22) +0x000 Minutes : 0y00101011 (0x2b) +0x000 Hours : 0y00001100 (0xc) +0x000 Precise : 0y0 +0x000 Reserved : 0y0000000 (0) +0x000 Day : 0y00010110 (0x16) +0x000 Month : 0y00000100 (0x4) +0x000 Year : 0y00001010 (0xa) +0x000 Century : 0y00010100 (0x14) +0x000 AsLARGE_INTEGER : _LARGE_INTEGER 0x140a0416`000c2b22 +0x020 PlatformId : _GUID {00000000-0000-0000-0000-000000000000} +0x000 Data1 : 0 +0x004 Data2 : 0 +0x006 Data3 : 0 +0x008 Data4 : [8] "" +0x030 PartitionId : _GUID {00000000-0000-0000-0000-000000000000} +0x000 Data1 : 0 +0x004 Data2 : 0 +0x006 Data3 : 0 +0x008 Data4 : [8] "" +0x040 CreatorId : _GUID {cf07c4bd-b789-4e18-b3c4-1f732cb57131} +0x000 Data1 : 0xcf07c4bd +0x004 Data2 : 0xb789 +0x006 Data3 : 0x4e18 +0x008 Data4 : [8] "???" +0x050 NotifyType : _GUID {e8f56ffe-919c-4cc5-ba88-65abe14913bb} +0x000 Data1 : 0xe8f56ffe +0x004 Data2 : 0x919c +0x006 Data3 : 0x4cc5 +0x008 Data4 : [8] "???" +0x060 RecordId : 0x01cae219`673474d3 +0x068 Flags : _WHEA_ERROR_RECORD_HEADER_FLAGS +0x000 Recovered : 0y0 +0x000 PreviousError : 0y1 +0x000 Simulated : 0y0 +0x000 Reserved : 0y00000000000000000000000000000 (0) +0x000 AsULONG : 2 +0x06c PersistenceInfo : _WHEA_PERSISTENCE_INFO +0x000 Signature : 0y0000000000000000 (0) +0x000 Length : 0y000000000000000000000000 (0) +0x000 Identifier : 0y0000000000000000 (0) +0x000 Attributes : 0y00 +0x000 DoNotLog : 0y0 +0x000 Reserved : 0y00000 (0) +0x000 AsULONGLONG : 0 +0x074 Reserved : [12] "" +0x080 SectionDescriptor : [1] _WHEA_ERROR_RECORD_SECTION_DESCRIPTOR +0x000 SectionOffset : 0x158 +0x004 SectionLength : 0xc0 +0x008 Revision : _WHEA_REVISION +0x000 MinorRevision : 0x1 '' +0x001 MajorRevision : 0x2 '' +0x000 AsUSHORT : 0x201 +0x00a ValidBits : _WHEA_ERROR_RECORD_SECTION_DESCRIPTOR_VALIDBITS +0x000 FRUId : 0y0 +0x000 FRUText : 0y0 +0x000 Reserved : 0y000000 (0) +0x000 AsUCHAR : 0 '' +0x00b Reserved : 0 '' +0x00c Flags : _WHEA_ERROR_RECORD_SECTION_DESCRIPTOR_FLAGS +0x000 Primary : 0y1 +0x000 ContainmentWarning : 0y0 +0x000 Reset : 0y0 +0x000 ThresholdExceeded : 0y0 +0x000 ResourceNotAvailable : 0y0 +0x000 LatentError : 0y0 +0x000 Reserved : 0y00000000000000000000000000 (0) +0x000 AsULONG : 1 +0x010 SectionType : _GUID {9876ccad-47b4-4bdb-b65e-16f193c4f3db} +0x000 Data1 : 0x9876ccad +0x004 Data2 : 0x47b4 +0x006 Data3 : 0x4bdb +0x008 Data4 : [8] "???" +0x020 FRUId : _GUID {00000000-0000-0000-0000-000000000000} +0x000 Data1 : 0 +0x004 Data2 : 0 +0x006 Data3 : 0 +0x008 Data4 : [8] "" +0x030 SectionSeverity : 1 ( WheaErrSevFatal ) +0x034 FRUText : [20] ""</pre></code></font></p> Another example is this:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004b46748, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

1: kd> dt -r _WHEA_ERROR_RECORD fffffa8004b46748
hal!_WHEA_ERROR_RECORD
   +0x000 Header           : _WHEA_ERROR_RECORD_HEADER
      +0x000 Signature        : 0x52455043
      +0x004 Revision         : _WHEA_REVISION
         +0x000 MinorRevision    : 0x10 ''
         +0x001 MajorRevision    : 0x2 ''
         +0x000 AsUSHORT         : 0x210
      +0x006 SignatureEnd     : 0xffffffff
      +0x00a SectionCount     : 3
      +0x00c Severity         : 1 ( WheaErrSevFatal )
      +0x010 ValidBits        : _WHEA_ERROR_RECORD_HEADER_VALIDBITS
         +0x000 PlatformId       : 0y0
         +0x000 Timestamp        : 0y1
         +0x000 PartitionId      : 0y0
         +0x000 Reserved         : 0y00000000000000000000000000000 (0)
         +0x000 AsULONG          : 2
      +0x014 Length           : 0x3a0
      +0x018 Timestamp        : _WHEA_TIMESTAMP
         +0x000 Seconds          : 0y00100010 (0x22)
         +0x000 Minutes          : 0y00101011 (0x2b)
         +0x000 Hours            : 0y00001100 (0xc)
         +0x000 Precise          : 0y0
         +0x000 Reserved         : 0y0000000 (0)
         +0x000 Day              : 0y00010110 (0x16)
         +0x000 Month            : 0y00000100 (0x4)
         +0x000 Year             : 0y00001010 (0xa)
         +0x000 Century          : 0y00010100 (0x14)
         +0x000 AsLARGE_INTEGER  : _LARGE_INTEGER 0x140a0416`000c2b22
      +0x020 PlatformId       : _GUID {00000000-0000-0000-0000-000000000000}
         +0x000 Data1            : 0
         +0x004 Data2            : 0
         +0x006 Data3            : 0
         +0x008 Data4            : [8]  ""
      +0x030 PartitionId      : _GUID {00000000-0000-0000-0000-000000000000}
         +0x000 Data1            : 0
         +0x004 Data2            : 0
         +0x006 Data3            : 0
         +0x008 Data4            : [8]  ""
      +0x040 CreatorId        : _GUID {cf07c4bd-b789-4e18-b3c4-1f732cb57131}
         +0x000 Data1            : 0xcf07c4bd
         +0x004 Data2            : 0xb789
         +0x006 Data3            : 0x4e18
         +0x008 Data4            : [8]  "???"
      +0x050 NotifyType       : _GUID {e8f56ffe-919c-4cc5-ba88-65abe14913bb}
         +0x000 Data1            : 0xe8f56ffe
         +0x004 Data2            : 0x919c
         +0x006 Data3            : 0x4cc5
         +0x008 Data4            : [8]  "???"
      +0x060 RecordId         : 0x01cae219`673474d3
      +0x068 Flags            : _WHEA_ERROR_RECORD_HEADER_FLAGS
         +0x000 Recovered        : 0y0
         +0x000 PreviousError    : 0y1
         +0x000 Simulated        : 0y0
         +0x000 Reserved         : 0y00000000000000000000000000000 (0)
         +0x000 AsULONG          : 2
      +0x06c PersistenceInfo  : _WHEA_PERSISTENCE_INFO
         +0x000 Signature        : 0y0000000000000000 (0)
         +0x000 Length           : 0y000000000000000000000000 (0)
         +0x000 Identifier       : 0y0000000000000000 (0)
         +0x000 Attributes       : 0y00
         +0x000 DoNotLog         : 0y0
         +0x000 Reserved         : 0y00000 (0)
         +0x000 AsULONGLONG      : 0
      +0x074 Reserved         : [12]  ""
   +0x080 SectionDescriptor : [1] _WHEA_ERROR_RECORD_SECTION_DESCRIPTOR
      +0x000 SectionOffset    : 0x158
      +0x004 SectionLength    : 0xc0
      +0x008 Revision         : _WHEA_REVISION
         +0x000 MinorRevision    : 0x1 ''
         +0x001 MajorRevision    : 0x2 ''
         +0x000 AsUSHORT         : 0x201
      +0x00a ValidBits        : _WHEA_ERROR_RECORD_SECTION_DESCRIPTOR_VALIDBITS
         +0x000 FRUId            : 0y0
         +0x000 FRUText          : 0y0
         +0x000 Reserved         : 0y000000 (0)
         +0x000 AsUCHAR          : 0 ''
      +0x00b Reserved         : 0 ''
      +0x00c Flags            : _WHEA_ERROR_RECORD_SECTION_DESCRIPTOR_FLAGS
         +0x000 Primary          : 0y1
         +0x000 ContainmentWarning : 0y0
         +0x000 Reset            : 0y0
         +0x000 ThresholdExceeded : 0y0
         +0x000 ResourceNotAvailable : 0y0
         +0x000 LatentError      : 0y0
         +0x000 Reserved         : 0y00000000000000000000000000 (0)
         +0x000 AsULONG          : 1
      +0x010 SectionType      : _GUID {9876ccad-47b4-4bdb-b65e-16f193c4f3db}
         +0x000 Data1            : 0x9876ccad
         +0x004 Data2            : 0x47b4
         +0x006 Data3            : 0x4bdb
         +0x008 Data4            : [8]  "???"
      +0x020 FRUId            : _GUID {00000000-0000-0000-0000-000000000000}
         +0x000 Data1            : 0
         +0x004 Data2            : 0
         +0x006 Data3            : 0
         +0x008 Data4            : [8]  ""
      +0x030 SectionSeverity  : 1 ( WheaErrSevFatal )
      +0x034 FRUText          : [20]  ""

]]> By: Crash Dump Analysis » Blog Archive » Crash Dump Analysis AntiPatterns (Part 14) https://www.dumpanalysis.org/blog/index.php/2008/04/03/crash-dump-analysis-patterns-part-57/#comment-156089 Crash Dump Analysis » Blog Archive » Crash Dump Analysis AntiPatterns (Part 14) Fri, 04 Jun 2010 23:43:18 +0000 https://www.dumpanalysis.org/blog/index.php/2008/04/03/crash-dump-analysis-patterns-part-57/#comment-156089 [...] wouldn’t be so quick. Check Hardware Error pattern post and comments there. So let’s de-analyze the analysis. “c0000005 is Access [...] […] wouldn’t be so quick. Check Hardware Error pattern post and comments there. So let’s de-analyze the analysis. “c0000005 is Access […]

]]> By: Crash Dump Analysis » Blog Archive » Fault context, wild code and hardware error: pattern cooperation https://www.dumpanalysis.org/blog/index.php/2008/04/03/crash-dump-analysis-patterns-part-57/#comment-135016 Crash Dump Analysis » Blog Archive » Fault context, wild code and hardware error: pattern cooperation Tue, 16 Mar 2010 22:38:21 +0000 https://www.dumpanalysis.org/blog/index.php/2008/04/03/crash-dump-analysis-patterns-part-57/#comment-135016 [...] Most fault IPs were showing signs of Wild Code pattern and that most probably implicated Hardware Error (Looks like WinDbg suggests that MISALIGNED_IP implicates hardware). Here is the listing of [...] […] Most fault IPs were showing signs of Wild Code pattern and that most probably implicated Hardware Error (Looks like WinDbg suggests that MISALIGNED_IP implicates hardware). Here is the listing of […]

]]> By: Dmitry Vostokov https://www.dumpanalysis.org/blog/index.php/2008/04/03/crash-dump-analysis-patterns-part-57/#comment-134399 Dmitry Vostokov Mon, 15 Mar 2010 00:15:43 +0000 https://www.dumpanalysis.org/blog/index.php/2008/04/03/crash-dump-analysis-patterns-part-57/#comment-134399 Another possibility of a hardware error: frequent multiple unrelated bugchecks and / or bugchecks in memory dumps with valid instructions at faulting IP. Beware also about misaligned IP that can also look as a valid instruction. Another possibility of a hardware error: frequent multiple unrelated bugchecks and / or bugchecks in memory dumps with valid instructions at faulting IP. Beware also about misaligned IP that can also look as a valid instruction.

]]>