Unexpected/random BSODs

[clew]

Hi,
My system have been crashing quite a lot this past few days, resulting in BSOD.
the last BSOD that occurred was while i am looking into the event log trying to look for the previous crash.
I'm not sure how to analyze them or debug them.

Attached the files from SF Diagnostic Tools

Hope someone can help me.
Thanks

 

[bagavan]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {703304, 2, 1, 8348b341}

Probably caused by : ntkrpamp.exe ( nt!KiSignalThread+8b )

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

2: 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: 00703304, 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: 8348b341, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8357c848
Unable to read MiSystemVaType memory at 8355be20
 00703304 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiSignalThread+8b
8348b341 894804          mov     dword ptr [eax+4],ecx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFFFFF8E721000

TRAP_FRAME:  8e71ca6c -- (.trap 0xffffffff8e71ca6c)
ErrCode = 00000002
eax=00703300 ebx=8e700120 ecx=898c8ad4 edx=00000001 esi=874cdca0 edi=8e703308
eip=8348b341 esp=8e71cae0 ebp=8e71cae8 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
nt!KiSignalThread+0x8b:
8348b341 894804          mov     dword ptr [eax+4],ecx ds:0023:00703304=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8348b341 to 83452cdb

STACK_TEXT:  
8e71ca6c 8348b341 badb0d00 00000001 95fa70cb nt!KiTrap0E+0x2cf
8e71cae8 8348b229 00000000 00000102 874cdd38 nt!KiSignalThread+0x8b
8e71cb1c 8344962f 8e700120 00000102 00000000 nt!KiTryUnwaitThread+0x60
8e71cb3c 8348b9d9 8e700120 8e71cba4 874cdd30 nt!KiSignalNotificationObject+0x31
8e71cb80 8348b6c7 8e700120 00000001 8e701a80 nt!KiTimerWaitTest+0x1e6
8e71cc68 8348b5fa 8e700120 8e71cca8 00000000 nt!KiProcessExpiredTimerList+0x8b
8e71ccdc 8348978e 000b6b1d 88ec74a8 8e705800 nt!KiTimerExpiration+0x25c
8e71cd20 834895b8 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
8e71cd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSignalThread+8b
8348b341 894804          mov     dword ptr [eax+4],ecx

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiSignalThread+8b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f7f43

FAILURE_BUCKET_ID:  0xA_nt!KiSignalThread+8b

BUCKET_ID:  0xA_nt!KiSignalThread+8b

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

 

[clew]

hmmm so it seems many received the "Probably caused by : ntkrpamp.exe" but not directly where the problem lays.

Thanks bagavan, but is it possible to elaborate more on what should i do? what i can catch on that windbg result is only that line, and clueless what to do next.

 

[JMV2009]

This indicated memory corruption. Use memtest86 and memtest from hcidesign.com, both overnight. Use driver verifier on the non-microsoft drivers without low resource simulation.