Hi Vandrid
The minidump didn't tell me more thing diffrent from the above
Have you run the memtest86 for at least 7 passes?
The bugcheck indicated error 0x1000008E, please read this article:
Bug Check 0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
The instruction for HD check is below:
HD Diagnostic
Bugcheck:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.243\061810-19437-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82816000 PsLoadedModuleList = 0x8295e810
Debug session time: Sat Jun 19 09:58:14.544 2010 (UTC + 7:00)
System Uptime: 3 days 18:37:46.308
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
.......................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 82a5d0eb, 9e355cac, 0}
Probably caused by : ntkrpamp.exe ( nt!NtClose+4f )
Followup: MachineOwner
---------
0: 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: c0000005, The exception code that was not handled
Arg2: 82a5d0eb, The address that the exception occurred at
Arg3: 9e355cac, 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:
nt!NtClose+4f
82a5d0eb c9 leave
TRAP_FRAME: 9e355cac -- (.trap 0xffffffff9e355cac)
ErrCode = 00000000
eax=00000000 ebx=82a5d09c ecx=9194f888 edx=746c6644 esi=01b3f320 edi=0000149c
eip=82a5d0eb esp=9e355d20 ebp=1e355d28 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!NtClose+0x4f:
82a5d0eb c9 leave
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8285942a to 82a5d0eb
STACK_TEXT:
9e355d28 8285942a 0000149c 01b3f324 76e364f4 nt!NtClose+0x4f
9e355d28 76e364f4 0000149c 01b3f324 76e364f4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01b3f324 00000000 00000000 00000000 00000000 0x76e364f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!NtClose+4f
82a5d0eb c9 leave
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!NtClose+4f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc007
FAILURE_BUCKET_ID: 0x8E_nt!NtClose+4f
BUCKET_ID: 0x8E_nt!NtClose+4f
Followup: MachineOwner
---------
let us know if you need help
Tuan
Quote