Blue Screen death odd times

PocketAcesDMB said:

All info on Comp specs in my profile..Thanks for any help in advance

Memory corruption probably caused by a driver

Please run memtest and driver verifier to find which driver (I suspect your Avast)

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86.com - Memory Diagnostic

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Code:

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\051811-33821-01.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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c18000 PsLoadedModuleList = 0xfffff800`02e5d650
Debug session time: Wed May 18 13:51:40.343 2011 (GMT-4)
System Uptime: 1 days 13:49:30.686
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 0, fffff80002d4aaeb}

Probably caused by : memory_corruption ( nt!MiStoreSetEvictPageFile+b )

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

1: 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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002d4aaeb, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec7100
 0000000000000008 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiStoreSetEvictPageFile+b
fffff800`02d4aaeb 488b5008        mov     rdx,qword ptr [rax+8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880033fc8d0 -- (.trap 0xfffff880033fc8d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8005fb6e30
rdx=00000000fa8007d4 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d4aaeb rsp=fffff880033fca68 rbp=00000000fa8007d4
 r8=00000000fa8007d4  r9=0000000000000002 r10=0000000000000000
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiStoreSetEvictPageFile+0xb:
fffff800`02d4aaeb 488b5008        mov     rdx,qword ptr [rax+8] ds:ff00:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c972a9 to fffff80002c97d00

STACK_TEXT:  
fffff880`033fc788 fffff800`02c972a9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`033fc790 fffff800`02c95f20 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`033fc8d0 fffff800`02d4aaeb : fffff800`02d4c02c fffffa80`05f57350 00000000`00000001 fffffa80`05fb6e30 : nt!KiPageFault+0x260
fffff880`033fca68 fffff800`02d4c02c : fffffa80`05f57350 00000000`00000001 fffffa80`05fb6e30 fffff800`02ca98ec : nt!MiStoreSetEvictPageFile+0xb
fffff880`033fca70 fffff800`02d03161 : fa8007d4`52d000c0 00000000`00000000 fa8007d4`52d000c0 fffff800`02dc3fbd : nt!MiReleaseConfirmedPageFileSpace+0x7c
fffff880`033fcaf0 fffff800`02f385fb : fffffa80`07d45250 00000000`00000000 00000000`0008c081 fffffa80`08ad3580 : nt! ?? ::FNODOBFM::`string'+0x2bd1d
fffff880`033fcbc0 fffff800`02ce50a1 : fffffa80`07d45258 00000000`00000001 00000000`00000000 00000000`00000631 : nt!MiSegmentDelete+0x7b
fffff880`033fcc00 fffff800`02ce4f65 : 00000000`00000000 00000000`00000080 fffffa80`0396cb30 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131
fffff880`033fccc0 fffff800`02f3432e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDereferenceSegmentThread+0x10d
fffff880`033fcd40 fffff800`02c89666 : fffff880`03163180 fffffa80`039f0b60 fffff880`0316dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033fcd80 00000000`00000000 : fffff880`033fd000 fffff880`033f7000 fffff880`033fc7f0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiStoreSetEvictPageFile+b
fffff800`02d4aaeb 488b5008        mov     rdx,qword ptr [rax+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiStoreSetEvictPageFile+b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiStoreSetEvictPageFile+b

BUCKET_ID:  X64_0xA_nt!MiStoreSetEvictPageFile+b

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

hi zigzag after 4 tests(still testing) so far i have zero errors so far using memtest....after using driver verifer testing all devices i rebooted (i did this before memtest) it blue screened at reboot and when i got into windows avast was off....anyway i can fix avast or is it an issue with avast itself

i also have the os/ program files on a seperate partition if that matters

PocketAcesDMB said:

hi zigzag after 4 tests(still testing) so far i have zero errors so far using memtest....after using driver verifer testing all devices i rebooted (i did this before memtest) it blue screened at reboot and when i got into windows avast was off....anyway i can fix avast or is it an issue with avast itself

You can probably fix Avast but it is a known BSOD cause on some systems.

I would remove and replace with Microsoft Security Essentials

http://files.avast.com/files/eng/aswclear5.exe

http://www.microsoft.com/security_essentials/

Uninstalling avast replacing with Microsoft Security Essential i hope it wont slow my comp down and doesn't suck

PocketAcesDMB said:

Uninstalling avast replacing with Microsoft Security Essential i hope it wont slow my comp down and doesn't suck

It is lighter on system resources, and is good at what it does. From a BSOD perspective it doesnt cause many like most others.

zigzag3143 said:

PocketAcesDMB said:

Uninstalling avast replacing with Microsoft Security Essential i hope it wont slow my comp down and doesn't suck

It is lighter on system resources, and is good at what it does. From a BSOD perspective it doesnt cause many like most others.

we shall see how this does..i love avast i hope that was the issue im gonna send my stuff to avast too see if they know the issue

New blue screen with Security Essentials installed now.... this is becoming annoying

new issue in post 9 please help