Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

help w/ bsod please


  • Please log in to reply
2 replies to this topic

#1 bemeli

bemeli

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:02:36 AM

Posted 18 February 2009 - 06:25 PM

hi, trying to help out a friend who's computer is crashing... hes running xp pro sp3. here's the stop error code:

stop: 0x8e (0xc0000005, 0x806373f1, 0xb395599c, 0x00000000) ok, looks like the trap frame arg 3 below in the dump file is different... have a number of crashes...

anyway, found the minidump file through the event viewer and installed windbg... here's what its got. any help would be much appreciated!

Microsoft ® Windows Debugger Version 6.11.0001.402 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Ben\Desktop\Mini021809-08.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Feb 18 17:30:10.453 2009 (GMT-5)
System Uptime: 0 days 0:00:54.156
Loading Kernel Symbols
...............................................................
...........................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 806373f1, f7ad699c, 0}

Probably caused by : ntkrpamp.exe ( nt!HvpGetCellMapped+5f )

Followup: MachineOwner
---------

1: 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: 806373f1, The address that the exception occurred at
Arg3: f7ad699c, 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!HvpGetCellMapped+5f
806373f1 8b4304 mov eax,dword ptr [ebx+4]

TRAP_FRAME: f7ad699c -- (.trap 0xfffffffff7ad699c)
ErrCode = 00000000
eax=00000500 ebx=00000500 ecx=831ba338 edx=00000003 esi=e1037008 edi=00000074
eip=806373f1 esp=f7ad6a10 ebp=f7ad6a58 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!HvpGetCellMapped+0x5f:
806373f1 8b4304 mov eax,dword ptr [ebx+4] ds:0023:00000504=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 8

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: services.exe

LAST_CONTROL_TRANSFER: from 8062faba to 806373f1

STACK_TEXT:
f7ad6a58 8062faba e1037008 00650074 e1037008 nt!HvpGetCellMapped+0x5f
f7ad6a74 80638c4e e1037008 e12feac4 e1037008 nt!CmpMarkValueDataDirty+0x44
f7ad6a90 80638ef3 e1037008 002fd620 e11f1544 nt!CmpMarkKeyValuesDirty+0xcc
f7ad6aac 80638f90 e1037008 002fd620 e133d624 nt!CmpFreeKeyValues+0x17
f7ad6ae8 806397ce e1037008 00160e60 e11a0e64 nt!CmpSyncKeyValues+0x26
f7ad6b2c 80639941 e234c000 00000400 00000001 nt!CmpCopySyncTree2+0x1f4
f7ad6b5c 80626042 e1037008 000001b8 e1037008 nt!CmpCopySyncTree+0x4f
f7ad6ccc 8062193a 00010002 f7ad6d64 f7ad6ce8 nt!CmpSaveBootControlSet+0x2b0
f7ad6cdc 8054161c 00000004 f7ad6d64 8050046d nt!NtInitializeRegistry+0x5e
f7ad6cdc 8050046d 00000004 f7ad6d64 8050046d nt!KiFastCallEntry+0xfc
f7ad6d58 8054161c 00000004 0079f8b0 7c90e4f4 nt!ZwInitializeRegistry+0x11
f7ad6d58 7c90e4f4 00000004 0079f8b0 7c90e4f4 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0079f8b0 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!HvpGetCellMapped+5f
806373f1 8b4304 mov eax,dword ptr [ebx+4]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!HvpGetCellMapped+5f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a

FAILURE_BUCKET_ID: 0x8E_nt!HvpGetCellMapped+5f

BUCKET_ID: 0x8E_nt!HvpGetCellMapped+5f

Followup: MachineOwner
---------

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,753 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:36 AM

Posted 18 February 2009 - 07:03 PM

Hi :thumbsup:.

Although I see various instances of situations like yours...I don't see anything that I would regard as conclusive diagnosis or cure.

As a general diagnostic procedure, I suggest running Memtest on your RAM. Nothing may be learned/gained by doing so, but it's one of the steps I would take if this were my system.

MemTest Manual - http://hcidesign.com/memtest/manual.html

Memtest86.com - Memory Diagnostic - http://www.memtest86.com/

Be aware that the .iso file which you download...must be converted into a bootable CD before it can run. You can use any program that purports to be an .iso-burner to create the bootable CD.

FWIW: I use Active@ ISO Burner - http://www.ntfs.com/iso_burner_free.htm to do this sort of task.

FWIW: Corrupt RAM, http://www.ehow.com/how_2020132_replace-corrupt-ram.html

Louis

#3 bemeli

bemeli
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:02:36 AM

Posted 18 February 2009 - 08:11 PM

thanks louis,
gave memtest a shot, but everything looks ok there - no errors...
-bemeli




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users