[BSOD: BugCheck 1000000A]

I keep on getting this BSOD, I ran the debugger and got this, I cant seem to find whats wrong, Can someone look at this for me.

Thanks
Jason



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


Loading Dump File [C:\Documents and Settings\Jason\Local Settings\Temp\WERa32a.dir00\Mini082708-05.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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Wed Aug 27 18:18:49.062 2008 (GMT-4)
System Uptime: 0 days 2:35:03.827
Loading Kernel Symbols
......................................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {9000, 1c, 0, 804e1ffc}

Probably caused by : hardware ( nt!KiTimerExpiration+30 )

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






0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00009000, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 804e1ffc, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: 00009000

CURRENT_IRQL: 1c

FAULTING_IP:
nt!KiTimerExpiration+30
804e1ffc b75f mov bh,5Fh

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: Idle

MISALIGNED_IP:
nt!KiTimerExpiration+30
804e1ffc b75f mov bh,5Fh

LAST_CONTROL_TRANSFER: from 804dcd22 to 804e1ffc

STACK_TEXT:
80556428 804dcd22 80561300 00000000 000915f4 nt!KiTimerExpiration+0x30
80556450 804dcc07 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
80556454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTimerExpiration+30
804e1ffc b75f mov bh,5Fh

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiTimerExpiration+30

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
---------

 

Thanks Pete for all the information, I ran a memory test with Memstat-86 program and came back OK.

I'm going to run a diagnostic on the hard drive and use EVEREST.

Will let you know

Jason