C
Confuzzled
Greetings, I have a new system that has a blue-screen issue that has me
totally stumped.
System information: P4-3.0ghz, Asus P5L VM1394, 2x1gig Corsair DDR 533,
using integrated audio, NIC and video. 1 SATA 160gig Seagate drive, Antec
Smart Power 450W.
Temps are good: 35C CPU, 38C peak. Sys temp: 33C-35C (has two 120mm fans
and stock. Voltages all look good. 12v hovers around 12.56v though but
seems okay.
System occasionally will blue-screen w/ minidump randomly. Maybe once/twice
a day. Programs open when this occurs: Outlook 2003 + AVG Free, systray
RealTek HD Manager, Intel Graphics Media Accelerator. Can come from a fresh
boot, fire up Outlook... send/receive new messages.. and periodically this
will spawn a blue screen/reboot.
I ran Memtest86+ overnight, 27 passes. No memory errors detected. I did
try upgrading to the latest BIOS (930) for the mainboard, no change. I also
ran Microsoft Update and it fetched numerous Outlook/Office updates. No
change.
The minidump isn't very helpful for trying to isolate what component/driver
may be having the issue. I've switched this to full memory dump and awaiting
my next bluescreen in hopes this might yield further insight. I'll
copy/paste the windgb from the minidumps in hopes someone can help further!
I'm at witts end and really unsure what to look at next. Any tips/insights
greatly appreciated!
===================================
BugCheck 1000008E, {c0000005, 80571fff, a7ee2908, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
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: 80571fff, The address that the exception occurred at
Arg3: a7ee2908, 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!CmpRemoveFromDelayedClose+4e
80571fff 8902 mov [edx],eax
TRAP_FRAME: a7ee2908 -- (.trap ffffffffa7ee2908)
ErrCode = 00000002
eax=e10297bc ebx=a7ee2b90 ecx=e28f3440 edx=00000000 esi=e102ca44 edi=e28f3440
eip=80571fff esp=a7ee297c ebp=a7ee2980 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nt!CmpRemoveFromDelayedClose+0x4e:
80571fff 8902 mov [edx],eax ds:0023:00000000=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 80571f29 to 80571fff
STACK_TEXT:
a7ee2980 80571f29 e28f3440 00000000 a7ee29cc nt!CmpRemoveFromDelayedClose+0x4e
a7ee2990 80571af1 e28f3440 a7ee2bf4 00000200
nt!CmpReferenceKeyControlBlock+0x15
a7ee29cc 805718c8 a7ee29fc 00000000 a7ee2b7c nt!CmpCacheLookup+0x1f5
a7ee2bb0 80571ef1 00059750 89be7980 890cac08 nt!CmpParseKey+0x10d
a7ee2c28 8056f2a8 00000850 a7ee2c68 00000040 nt!ObpLookupObjectName+0x119
a7ee2c7c 80571dbe 00000000 89be7980 8056e901 nt!ObOpenObjectByName+0xea
a7ee2d50 804dd99f 00c9db34 00000001 00c9da88 nt!NtOpenKey+0x1af
a7ee2d50 7c90eb94 00c9db34 00000001 00c9da88 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00c9da64 00000000 00000000 00000000 00000000 0x7c90eb94
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
80571ff4 - nt!CmpRemoveFromDelayedClose+43
[ 55:71 ]
1 error : !nt (80571ff4)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BYTE
STACK_COMMAND: .trap ffffffffa7ee2908 ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
Followup: memory_corruption
totally stumped.
System information: P4-3.0ghz, Asus P5L VM1394, 2x1gig Corsair DDR 533,
using integrated audio, NIC and video. 1 SATA 160gig Seagate drive, Antec
Smart Power 450W.
Temps are good: 35C CPU, 38C peak. Sys temp: 33C-35C (has two 120mm fans
and stock. Voltages all look good. 12v hovers around 12.56v though but
seems okay.
System occasionally will blue-screen w/ minidump randomly. Maybe once/twice
a day. Programs open when this occurs: Outlook 2003 + AVG Free, systray
RealTek HD Manager, Intel Graphics Media Accelerator. Can come from a fresh
boot, fire up Outlook... send/receive new messages.. and periodically this
will spawn a blue screen/reboot.
I ran Memtest86+ overnight, 27 passes. No memory errors detected. I did
try upgrading to the latest BIOS (930) for the mainboard, no change. I also
ran Microsoft Update and it fetched numerous Outlook/Office updates. No
change.
The minidump isn't very helpful for trying to isolate what component/driver
may be having the issue. I've switched this to full memory dump and awaiting
my next bluescreen in hopes this might yield further insight. I'll
copy/paste the windgb from the minidumps in hopes someone can help further!
I'm at witts end and really unsure what to look at next. Any tips/insights
greatly appreciated!
===================================
BugCheck 1000008E, {c0000005, 80571fff, a7ee2908, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
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: 80571fff, The address that the exception occurred at
Arg3: a7ee2908, 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!CmpRemoveFromDelayedClose+4e
80571fff 8902 mov [edx],eax
TRAP_FRAME: a7ee2908 -- (.trap ffffffffa7ee2908)
ErrCode = 00000002
eax=e10297bc ebx=a7ee2b90 ecx=e28f3440 edx=00000000 esi=e102ca44 edi=e28f3440
eip=80571fff esp=a7ee297c ebp=a7ee2980 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nt!CmpRemoveFromDelayedClose+0x4e:
80571fff 8902 mov [edx],eax ds:0023:00000000=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 80571f29 to 80571fff
STACK_TEXT:
a7ee2980 80571f29 e28f3440 00000000 a7ee29cc nt!CmpRemoveFromDelayedClose+0x4e
a7ee2990 80571af1 e28f3440 a7ee2bf4 00000200
nt!CmpReferenceKeyControlBlock+0x15
a7ee29cc 805718c8 a7ee29fc 00000000 a7ee2b7c nt!CmpCacheLookup+0x1f5
a7ee2bb0 80571ef1 00059750 89be7980 890cac08 nt!CmpParseKey+0x10d
a7ee2c28 8056f2a8 00000850 a7ee2c68 00000040 nt!ObpLookupObjectName+0x119
a7ee2c7c 80571dbe 00000000 89be7980 8056e901 nt!ObOpenObjectByName+0xea
a7ee2d50 804dd99f 00c9db34 00000001 00c9da88 nt!NtOpenKey+0x1af
a7ee2d50 7c90eb94 00c9db34 00000001 00c9da88 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00c9da64 00000000 00000000 00000000 00000000 0x7c90eb94
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
80571ff4 - nt!CmpRemoveFromDelayedClose+43
[ 55:71 ]
1 error : !nt (80571ff4)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BYTE
STACK_COMMAND: .trap ffffffffa7ee2908 ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
Followup: memory_corruption