Constant BSODs

#1
Im constantly getting BSOD's, mostly everyday, although while ive been researching the cause of it ive had about 5, which seems a bit weird. (all in space of an hour or so)

Im on windows 7 64bit, it should be noted that while i was running windows 7 32bit i had no such problems, maybe the occasional BSOD.






View attachment 052211-21106-01.dmp





Any help would be appreciated, let me know if you need anything else.
 


Attachments

Last edited:

kaos

Senior Member
#2
can u please upload any mindump for the bsod's
 


#3
When ever i edit my post, it breaks it. Here are both attachments

(Actually the dump file is in the 1st post, there is a link which is inbetween the CPU-z screenshots)
 


Attachments

Last edited:

kaos

Senior Member
#4
minidumps

Code:
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8a0015bd998, 2, 0, fffff88001130039}

Unable to load image \SystemRoot\system32\DRIVERS\stflt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for stflt.sys
*** ERROR: Module load completed but symbols could not be loaded for stflt.sys
Probably caused by : stflt.sys ( stflt+1ed9 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8a0015bd998, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001130039, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003105100
fffff8a0015bd998 

CURRENT_IRQL:  2

FAULTING_IP: 
fltmgr!GetContextFromStreamList+99
fffff880`01130039 488b4820        mov     rcx,qword ptr [rax+20h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c330 -- (.trap 0xfffff80000b9c330)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a0015bd978 rbx=0000000000000000 rcx=fffffa8004d4c4e0
rdx=fffffa8004d47270 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001130039 rsp=fffff80000b9c4c0 rbp=fffffa8002b032f8
r8=fffffa8004ead3c0  r9=fffff80000b9c5d8 r10=fffffa8004d4c4e8
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fltmgr!GetContextFromStreamList+0x99:
fffff880`01130039 488b4820        mov     rcx,qword ptr [rax+20h] ds:f000:fffff8a0`015bd998=fffffa8004d47270
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ed52a9 to fffff80002ed5d00

STACK_TEXT:  
fffff800`00b9c1e8 fffff800`02ed52a9 : 00000000`0000000a fffff8a0`015bd998 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c1f0 fffff800`02ed3f20 : 00000000`00000004 00000000`00000000 fffff800`00b9c648 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c330 fffff880`01130039 : 00000000`00000000 00000000`00000000 fffff800`00b9c570 fffff880`0112faae : nt!KiPageFault+0x260
fffff800`00b9c4c0 fffff880`0112fcb3 : fffffa80`04d4c4e0 fffffa80`04d4c4e0 fffffa80`02b031f0 fffffa80`04ead3c0 : fltmgr!GetContextFromStreamList+0x99
fffff800`00b9c540 fffff880`05624ed9 : fffffa80`04d4c4e0 00000000`00000000 fffff800`00b9c618 fffff800`00b9c618 : fltmgr!FltGetStreamHandleContext+0x43
fffff800`00b9c570 fffffa80`04d4c4e0 : 00000000`00000000 fffff800`00b9c618 fffff800`00b9c618 00000000`00000000 : stflt+0x1ed9
fffff800`00b9c578 00000000`00000000 : fffff800`00b9c618 fffff800`00b9c618 00000000`00000000 00000000`0000000f : 0xfffffa80`04d4c4e0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
stflt+1ed9
fffff880`05624ed9 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  stflt+1ed9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: stflt

IMAGE_NAME:  stflt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c2b57fc

FAILURE_BUCKET_ID:  X64_0xD1_stflt+1ed9

BUCKET_ID:  X64_0xD1_stflt+1ed9

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

does it happen when you boot from sleep
 


kaos

Senior Member
#5
UNINSTALL - SPYWARE TERMINATER
 


#6
Sleep mode is turned off. So dunno. Ill uninstall Spyware terminator. Although i do like the program.

I have had no BSODs for a few hours, however i got about 4-5 earlier, after the last one i ended running programs, these included
PowerISO
spyware terminator updater
MalwareBytes
IOBit Smart Defrag 2
Winamp Agent

Ill let you know if i experience any more.
 


Last edited:

kaos

Senior Member
#7
If u want programs to get rid of spyware thenu can use

spytbot search and destroy
this attacks
spyware etc.
 


#8
I already have Spyware S&D and malware bytes. However sometimes one program will miss something where another will pick it up.
 


kaos

Senior Member
#9
most programws will detect spyware but spyware terminater programs i beliee is the cause
 


#10
I ran the command sfc /scannow in cmd (saw it in another thread) Which has repaired quite a few things by the looks of it, the log is 2500kb (88kb once rar'd)

Ive attached the log anyway just incase. (i removed all log entries from previous days)
 


Attachments

kaos

Senior Member
#11
ok let me no how it goes :)
 


#12
Another BSOD. Any ideas?

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffe8001a6dc10, 2, 1, fffff80002ec360e}

Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+13e )

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

3: 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: fffffe8001a6dc10, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002ec360e, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ce100
 fffffe8001a6dc10 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiRemoveAnyPage+13e
fffff800`02ec360e f0410fba6c241000 lock bts dword ptr [r12+10h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88006520940 -- (.trap 0xfffff88006520940)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000042a30000 rbx=0000000000000000 rcx=fffff8a00a734000
rdx=fffffffff8327000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e958bb rsp=fffff88006520ad8 rbp=0000000000000001
 r8=0000000000000010  r9=0000000000000001 r10=00000000000042a3
r11=fffff8a00a733ff8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!memcpy+0x20b:
fffff800`02e958bb 488901          mov     qword ptr [rcx],rax ds:0002:fffff8a0`0a734000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e9e2a9 to fffff80002e9ed00

STACK_TEXT:  
fffff880`065201e8 fffff800`02e9e2a9 : 00000000`0000000a fffffe80`01a6dc10 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`065201f0 fffff800`02e9cf20 : fffffa80`03d9e480 fffff880`0408fd1e 00000000`00000001 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`06520330 fffff800`02ec360e : fffff880`06520500 00000000`0001060e fffffa80`003122a0 00000000`00000000 : nt!KiPageFault+0x260
fffff880`065204c0 fffff800`02eaf89f : 00000000`00000000 fffff880`00000000 fffff800`030d15c0 00000000`00000000 : nt!MiRemoveAnyPage+0x13e
fffff880`065205e0 fffff800`02ebc7be : 00000000`00000001 fffff8a0`0a734000 fffff880`06520940 fffff6fc`500539a0 : nt!MiResolveDemandZeroFault+0x54f
fffff880`065206d0 fffff800`02eaca2b : 00000000`00000000 fffff880`06520880 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x8ce
fffff880`065207e0 fffff800`02e9ce2e : 00000000`00000001 fffff8a0`0a734000 ffffffff`f8381500 fffff8a0`02a5aff8 : nt!MmAccessFault+0xe1b
fffff880`06520940 fffff800`02e958bb : fffff800`032b9163 fffff8a0`02a5afe8 00000000`00000001 fffff8a0`0a733fe8 : nt!KiPageFault+0x16e
fffff880`06520ad8 fffff800`032b9163 : fffff8a0`02a5afe8 00000000`00000001 fffff8a0`0a733fe8 fffff800`00000000 : nt!memcpy+0x20b
fffff880`06520ae0 fffff800`033082b0 : fffff880`06520c10 fffff8a0`02a55018 fffff8a0`0a726000 fffff8a0`0aba8000 : nt!PfTCreateTraceDump+0x2e3
fffff880`06520be0 fffff800`0330dea3 : fffffa80`05058101 00000000`00000080 fffffa80`02458890 fffff800`03023da8 : nt!PfTGenerateTrace+0x10
fffff880`06520c10 fffff800`0313b32e : ffffffff`ff676980 fffffa80`05058160 fffffa80`050c0b60 fffff800`02e96817 : nt!PfTLoggingWorker+0x113
fffff880`06520d40 fffff800`02e90666 : fffff880`031d3180 fffffa80`05058160 fffff880`031ddfc0 fffff880`01233384 : nt!PspSystemThreadStartup+0x5a
fffff880`06520d80 00000000`00000000 : fffff880`06521000 fffff880`0651b000 fffff880`06520740 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRemoveAnyPage+13e
fffff800`02ec360e f0410fba6c241000 lock bts dword ptr [r12+10h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiRemoveAnyPage+13e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiRemoveAnyPage+13e

BUCKET_ID:  X64_0xA_nt!MiRemoveAnyPage+13e

Followup: MachineOwner
---------
Btw i do have a kernal dump and a full memory dump available, i can do anything you'd like with those and post results if you need.
 


Attachments

Last edited:

kaos

Senior Member
#13
download a program called memtest86+

test one stick at a time

allow 7 passes to run then change to the next stick, or if this errors stop which ever comes first

this will take some time,

make sure u have updated chipset drivers, graphics card , do this first if u wnt then the ram
 


#14
By test one stick at a time you mean remove one?

Chipset, motherboard and graphics drivers are all up-to-date.

Downloaded the program and will run it when im not using the computer, since i can game perfectly fine without BSODs.
 


kaos

Senior Member
#15
take every single stick of ram out

put 1 back in , run the test

stop at 7 passes or errors which ever happens first

if this sticke errors put it to the side

put the next stick in do the same and so on untill every ram stick has been tested
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top