Hi,
i got a bsod error code 0x0000008E (0x80000004, 0x804D4D020, 0xED3411E0, 0x00000000).
I then downloaded the debugger and analyzed my minidump.
but i dont get what they mean. I dont really know if its my ram being faulty or my psu as what i have read from the stickied thread.
Here's my analyzed results, do help me with it please.
Thanks in advance.
i got a bsod error code 0x0000008E (0x80000004, 0x804D4D020, 0xED3411E0, 0x00000000).
I then downloaded the debugger and analyzed my minidump.
but i dont get what they mean. I dont really know if its my ram being faulty or my psu as what i have read from the stickied thread.
Here's my analyzed results, do help me with it please.
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\jo\Desktop\Dumps\Mini092706-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 UP Free x86 compatible
Product: WinNt
Built by: 2600.xpclient.010817-1148
Kernel base = 0x804d0000 PsLoadedModuleList = 0x80545b28
Debug session time: Thu Sep 28 07:58:11.510 2006 (GMT+8)
System Uptime: 1 days 22:34:19.107
Loading Kernel Symbols
..........................................................................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {80000004, 804d4d02, ed3411e0, 0}
Probably caused by : ntoskrnl.exe ( nt!Dr_kss_a+16 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* 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: 80000004, The exception code that was not handled
Arg2: 804d4d02, The address that the exception occurred at
Arg3: ed3411e0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - No such interface supported
FAULTING_IP:
nt!Dr_kss_a+16
804d4d02 0f21c3 mov ebx,dr0
TRAP_FRAME: ed3411e0 -- (.trap ffffffffed3411e0)
Unable to read trap frame at ed3411e0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 00000000 to 804d4d02
STACK_TEXT:
ed341254 00000000 ed341a70 ed3417d4 ed341a7c nt!Dr_kss_a+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!Dr_kss_a+16
804d4d02 0f21c3 mov ebx,dr0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!Dr_kss_a+16
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 3b7de38f
FAILURE_BUCKET_ID: 0x8E_nt!Dr_kss_a+16
BUCKET_ID: 0x8E_nt!Dr_kss_a+16
Followup: MachineOwner
---------
Thanks in advance.
