Sign in with
Sign up | Sign in
Your question

BSOD error

Last response: in Windows XP
Share
October 25, 2008 3:48:45 PM

Is there anyone who can read this minidump at tell me what could be causing my BSOD they are random and not sure what the problem is, thanks!


Loading Dump File [C:\WINDOWS\Minidump\Mini102508-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV**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
Built by: 2600.xpsp_sp2_gdr.080814-1233
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Oct 25 10:57:03.031 2008 (GMT-4)
System Uptime: 0 days 1:52:47.640
Loading Kernel Symbols
..........................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {aa5600, 2, 1, 806e4aca}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+167 )

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: 00aa5600, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 806e4aca, address which referenced memory

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


WRITE_ADDRESS: 00aa5600

CURRENT_IRQL: 2

FAULTING_IP:
hal!KeReleaseQueuedSpinLock+22
806e4aca f00fb119 lock cmpxchg dword ptr [ecx],ebx

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 8051be27 to 806e4aca

STACK_TEXT:
bacc380c 8051be27 00000000 00008000 00000000 hal!KeReleaseQueuedSpinLock+0x22
bacc3840 80696b94 8a9ba6a0 00000000 00000044 nt!MmZeroPageThread+0x167
bacc3dac 805ce858 80087000 00000000 00000000 nt!Phase1Initialization+0x1288
bacc3ddc 8054534e 8069590c 80087000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmZeroPageThread+167
8051be27 57 push edi

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MmZeroPageThread+167

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48a3f93a

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_W_nt!MmZeroPageThread+167

BUCKET_ID: 0xA_W_nt!MmZeroPageThread+167

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: 00aa5600, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 806e4aca, address which referenced memory

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


WRITE_ADDRESS: 00aa5600

CURRENT_IRQL: 2

FAULTING_IP:
hal!KeReleaseQueuedSpinLock+22
806e4aca f00fb119 lock cmpxchg dword ptr [ecx],ebx

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 8051be27 to 806e4aca

STACK_TEXT:
bacc380c 8051be27 00000000 00008000 00000000 hal!KeReleaseQueuedSpinLock+0x22
bacc3840 80696b94 8a9ba6a0 00000000 00000044 nt!MmZeroPageThread+0x167
bacc3dac 805ce858 80087000 00000000 00000000 nt!Phase1Initialization+0x1288
bacc3ddc 8054534e 8069590c 80087000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmZeroPageThread+167
8051be27 57 push edi

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MmZeroPageThread+167

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48a3f93a

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_W_nt!MmZeroPageThread+167

BUCKET_ID: 0xA_W_nt!MmZeroPageThread+167

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

More about : bsod error

October 25, 2008 9:14:26 PM

Well I have ran memory test now for the pass 4 hours and it has passed everytime, so does that mean there is nothing wrong with my ram?
!