This error was more ambiguous, some driver was failing or perhaps some overheating is happening:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 00000001, The address that the exception occurred at
Arg3: b3874cf0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
+1
00000001 ?? ???
TRAP_FRAME: b3874cf0 -- (.trap ffffffffb3874cf0)
ErrCode = 00000010
eax=890ee020 ebx=bf8017e5 ecx=890ee054 edx=bc6cc738 esi=00000001 edi=b3874d64
eip=00000001 esp=b3874d64 ebp=b3874d54 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000001 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 0117ff50 to 00000001
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b3874d60 0117ff50 7c90eb94 badb0d00 0117ff38 0x1
b3874d64 7c90eb94 badb0d00 0117ff38 00000000 0x117ff50
b3874d68 badb0d00 0117ff38 00000000 00000000 0x7c90eb94
b3874d6c 0117ff38 00000000 00000000 00000000 0xbadb0d00
b3874d70 00000000 00000000 00000000 00000000 0x117ff38
STACK_COMMAND: .trap 0xffffffffb3874cf0 ; kb
FOLLOWUP_IP:
+1
00000001 ?? ???
FAULTING_SOURCE_CODE:
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x8E
BUCKET_ID: 0x8E
Followup: MachineOwner
---------
To generate these debug messages, instructions are here:
http://support.microsoft.com/kb/315263Not for the faint of heart though...this is quite complex.
Flames? My firewall blocks flames...