Memory Dump - machine keeps restarting

Hi Guys,

i have a machine that is just restarting itself randomly but constantly.
i have reinstalled the operating system and its still doing the same thing which lead me to hardware issue.

i have posted the memory dump i got from the last reboot.

can anybody shed some light on what might be causing this to happen?

thanks
stef08

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Mini082709-01.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 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.090206-1233
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Thu Aug 27 16:15:03.484 2009 (GMT+1)
System Uptime: 0 days 2:27:02.421
Loading Kernel Symbols
...............................................................
..........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8053ae2f, b9f01aa8, 0}

Probably caused by : hardware ( nt!_SEH_epilog+4 )

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: 8053ae2f, The address that the exception occurred at
Arg3: b9f01aa8, 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!_SEH_epilog+4
8053ae2f 890d00000000 mov dword ptr ds:[0],ecx

TRAP_FRAME: b9f01aa8 -- (.trap 0xffffffffb9f01aa8)
ErrCode = 00000002
eax=00000000 ebx=0000008b ecx=00000000 edx=0005eb90 esi=b9f01ca4 edi=0400fe98
eip=8053ae2f esp=b9f01b1c ebp=b9f01d4c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!_SEH_epilog+0x4:
8053ae2f 890d00000000 mov dword ptr ds:[0],ecx ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: svchost.exe

MISALIGNED_IP:
nt!_SEH_epilog+4
8053ae2f 890d00000000 mov dword ptr ds:[0],ecx

LAST_CONTROL_TRANSFER: from 8054088c to 8053ae2f

STACK_TEXT:
b9f01d4c 8054088c 00000002 0400fd60 00000138 nt!_SEH_epilog+0x4
b9f01d4c 7c90e514 00000002 0400fd60 00000138 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0400fd38 7c90d93a 7c831137 00000002 0400fd60 0x7c90e514
0400feec 606b1d3a 0400ff00 0086ccf8 00000003 0x7c90d93a
0400ff2c 606b1cf1 6079e000 606b25ed 0086ccf8 0x606b1d3a
0400ff4c 606b1a14 015df324 0465dac0 0465dac0 0x606b1cf1
0400ff80 606b737b 00000000 015df324 015df32c 0x606b1a14
0400ffb4 7c80b699 0465dac0 015df324 015df32c 0x606b737b
0400ffec 00000000 606b7356 0465dac0 00000000 0x7c80b699


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!_SEH_epilog+4
8053ae2f 890d00000000 mov dword ptr ds:[0],ecx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!_SEH_epilog+4

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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

1: kd> lmvm hardware
start end module name
1: kd> .trap 0xffffffffb9f01aa8
ErrCode = 00000002
eax=00000000 ebx=0000008b ecx=00000000 edx=0005eb90 esi=b9f01ca4 edi=0400fe98
eip=8053ae2f esp=b9f01b1c ebp=b9f01d4c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!_SEH_epilog+0x4:
8053ae2f 890d00000000 mov dword ptr ds:[0],ecx ds:0023:00000000=????????

 

hi pete,

thanks for your reply.
its not the hardrive because i got a new harddrive and installed a fresh operating system. i will test the RAM and see if that helps. could it be driver issues? i have noticed that the sound is not working either. It says that there is no audio mixer installed. the volume control panel is all greyed out.

if you think of anything else can you let me know

stef08

 

Is there anyway of getting to know what motherboard is installed without opening the machine and maybe what drivers are needed for the chipset?

i had to install a Nvidia driver set for to get the ethernet etc working.

 

i look after alot of different machines, therefore i cannot put up the spec on my profile.

i have swapped the RAM module in this machine and placed it in another slot on the board.
i will just have to wait and see if this works? hopefully it will work.