Blue Screen Reoccurring x64 Win 7 Pro

sick of these at random times doing random things

PocketAcesDMB said:

sick of these at random times doing random things

Memory corruption caused by unknown driver... please run memtest and driver verifier


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

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.



Driver verifier

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\060611-29265-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`02c17000 PsLoadedModuleList = 0xfffff800`02e5c650
Debug session time: Mon Jun  6 15:48:42.531 2011 (GMT-4)
System Uptime: 1 days 1:25:00.173
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa80260180a8, 2, 1, fffff80002d4b036}

Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 )

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: fffffa80260180a8, 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: fffff80002d4b036, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec6100
 fffffa80260180a8 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReleaseConfirmedPageFileSpace+86
fffff800`02d4b036 480fb328        btr     qword ptr [rax],rbp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880033fc8e0 -- (.trap 0xfffff880033fc8e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8006b18010 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d4b036 rsp=fffff880033fca70 rbp=00000000fa8004cf
 r8=fffff880033fcaa0  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!MiReleaseConfirmedPageFileSpace+0x86:
fffff800`02d4b036 480fb328        btr     qword ptr [rax],rbp ds:fffffa80`06b18010=70fffe67b3cc5fff
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c962a9 to fffff80002c96d00

STACK_TEXT:  
fffff880`033fc798 fffff800`02c962a9 : 00000000`0000000a fffffa80`260180a8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`033fc7a0 fffff800`02c94f20 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`033fc8e0 fffff800`02d4b036 : fffffa80`048ddde0 00000000`00000000 fffffa80`05f389f0 fffff800`02ca88ec : nt!KiPageFault+0x260
fffff880`033fca70 fffff800`02d02161 : fa8004cf`568000c0 00000000`00000000 fa8004cf`568000c0 00000000`00000000 : nt!MiReleaseConfirmedPageFileSpace+0x86
fffff880`033fcaf0 fffff800`02f375fb : fffffa80`04cf5600 00000000`00000000 00000000`0008c081 fffffa80`0425c450 : nt! ?? ::FNODOBFM::`string'+0x2bd1d
fffff880`033fcbc0 fffff800`02ce40a1 : fffffa80`04cf5608 00000000`00000001 00000000`00000000 00000000`00000631 : nt!MiSegmentDelete+0x7b
fffff880`033fcc00 fffff800`02ce3f65 : 00000000`00000000 00000000`00000080 fffffa80`039cd840 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131
fffff880`033fccc0 fffff800`02f3332e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDereferenceSegmentThread+0x10d
fffff880`033fcd40 fffff800`02c88666 : 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!MiReleaseConfirmedPageFileSpace+86
fffff800`02d4b036 480fb328        btr     qword ptr [rax],rbp

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiReleaseConfirmedPageFileSpace+86

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86

BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86

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

update 1

upon running driver verifier at reboot i get the blue screen of SmartDefragDriver.sys...i have run memtest with no errors reported as well previousley

PocketAcesDMB said:

update 1

upon running driver verifier at reboot i get the blue screen of SmartDefragDriver.sys...i have run memtest with no errors reported as well previousley

So remove Iobits smart defragger. Smart Defrag | Best Disk Defrag Freeware | Free Defragmenter

And turn driver verifier off