hi every body !!! ive got a blue screen error and the dump file is available at this this link !!
http://rapidshare.com/files/157116513/Mini102408-01.dmp.html
please help me solve this problem as soon as possible !! i tried for a system restore but it dint help !:(
my system config:
Intel(R)
pentium(R) D CPU 2.80 GHZ ,448 mb ram
im using sp2
THANKS IN ADVANCE:)
results of debug .looks like ram problem
=============
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\Jack\Desktop\Mini102408-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbolssp2
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Oct 24 10:26:40.859 2008 (GMT-3)
System Uptime: 0 days 0:07:00.556
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.......................................................................................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {e1883094, 1c, 0, 804fac65}
Probably caused by : memory_corruption ( nt!MiWaitForInPageComplete+2d6 )
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: e1883094, 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: 804fac65, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: e1883094
CURRENT_IRQL: 1c
FAULTING_IP:
nt!MiWaitForInPageComplete+2d6
804fac65 803b02 cmp byte ptr [ebx],2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 83dc1c11 to 804fac65
STACK_TEXT:
f255acbc 83dc1c11 00000000 00000000 00000000 nt!MiWaitForInPageComplete+0x2d6
WARNING: Frame IP not in any known module. Following frames may be wrong.
f255ace8 83dbf5b2 ffffffff 00000067 83dd77d8 0x83dc1c11
f255ad24 83dbd57d e1821d04 83dbff9d f255ad08 0x83dbf5b2
f255ad8c 83dbd30e e187bc9c 842e1bb8 83dc2297 0x83dbd57d
f255addc 805450ce 83dc2245 842e1bb8 00000000 0x83dbd30e
f255ae64 00000000 00000000 00000000 00000000 nt!WmiTraceMessageVa+0x35
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiWaitForInPageComplete+2d6
804fac65 803b02 cmp byte ptr [ebx],2
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiWaitForInPageComplete+2d6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1e
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xA_nt!MiWaitForInPageComplete+2d6
BUCKET_ID: 0xA_nt!MiWaitForInPageComplete+2d6
Followup: MachineOwner
---------