tsl
this one was caused by memory corruption, but the cause was not identified. I did notice that there are several drivers that are really old (circa 2006, 2007) and that may be a contributing factor.
I would download and run memtest86. Let it run for hours (ovenight) to check. If you have another bsod upload it. In the meantime im going to identify the old drivers for you. \\Ken
\
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Mini092709-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*
Symbol information
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x81a1e000 PsLoadedModuleList = 0x81b35c70
Debug session time: Sun Sep 27 06:31:54.794 2009 (GMT-4)
System Uptime: 0 days 0:00:11.512
Loading Kernel Symbols
...............................................................
................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 81c4a7de, 88523c80, 8852397c}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 81c4a7de, The address that the exception occurred at
Arg3: 88523c80, Exception Record Address
Arg4: 8852397c, Context Record Address
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!EtwpLogger+e5
81c4a7de 2b442420 sub eax,dword ptr [esp+20h]
EXCEPTION_RECORD: 88523c80 -- (.exr 0xffffffff88523c80)
ExceptionAddress: 81c4a7de (nt!EtwpLogger+0x000000e5)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 0bbb9d70
Attempt to read from address 0bbb9d70
CONTEXT: 8852397c -- (.cxr 0xffffffff8852397c)
eax=bbc08314 ebx=00000000 ecx=01ca3f5d edx=00000000 esi=83696008 edi=bbc08314
eip=81c4a7de esp=88523d48 ebp=88523d7c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246
nt!EtwpLogger+0xe5:
81c4a7de 2b442420 sub eax,dword ptr [esp+20h] ss:0010:88523d68=bb25c973
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 0bbb9d70
READ_ADDRESS: GetPointerFromAddress: unable to read from 81b55868
Unable to read MiSystemVaType memory at 81b35420
0bbb9d70
FOLLOWUP_IP:
nt!EtwpLogger+e5
81c4a7de 2b442420 sub eax,dword ptr [esp+20h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 81bf3c42 to 81c4a7de
STACK_TEXT:
88523d7c 81bf3c42 83696008 a51d99eb 00000000 nt!EtwpLogger+0xe5
88523dc0 81a5cefe 81c4a6f9 83696008 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
81c4acc8 - nt!EtwpFlushActiveBuffers+261
[ 6a:7a ]
1 error : !nt (81c4acc8)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BIT
STACK_COMMAND: .cxr 0xffffffff8852397c ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption
---------
