Windows 7 BSOD x64 (at random times)

koolkat77 · 05 Jan 2014

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {25a8, 2, 1, fffff80003336cb6}

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

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

4: 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: 00000000000025a8, 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: fffff80003336cb6, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b1100
GetUlongFromAddress: unable to read from fffff800034b11c0
 00000000000025a8 Nonpaged pool

CURRENT_IRQL:  2

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  CCC.exe

TRAP_FRAME:  fffff8800ac9c5d0 -- (.trap 0xfffff8800ac9c5d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003336cb6 rsp=fffff8800ac9c760 rbp=0000000000012d5d
 r8=fffff8800ac9c790  r9=0000000000000000 r10=0000000000000001
r11=fffff8800ac9c7b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x86:
fffff800`03336cb6 480fb328        btr     qword ptr [rax],rbp ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003279169 to fffff80003279bc0

STACK_TEXT:  
fffff880`0ac9c488 fffff800`03279169 : 00000000`0000000a 00000000`000025a8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0ac9c490 fffff800`03277de0 : fffff700`01080000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0ac9c5d0 fffff800`03336cb6 : fffffa80`037eda70 00000000`00000000 fffffa80`0857ad80 00000000`00000002 : nt!KiPageFault+0x260
fffff880`0ac9c760 fffff800`032ed9a9 : 80000001`28c10867 fffffa80`0a5a6818 fffff680`00014830 fffffa80`0a5a6818 : nt!MiReleaseConfirmedPageFileSpace+0x86
fffff880`0ac9c7e0 fffff800`03296c8f : 00000000`00000001 00000000`00000000 fffff683`ff7a92f0 fffffa80`0a5a6818 : nt! ?? ::FNODOBFM::`string'+0x380a1
fffff880`0ac9c870 fffff800`03286179 : fffff880`0ac9cae0 ffffffff`ffffffff fffffa80`0967cb50 fffff800`0327cc9f : nt!MiDispatchFault+0x95f
fffff880`0ac9c980 fffff800`03277cee : 00000000`00000001 00000000`02906000 00000000`00001101 00000000`00001126 : nt!MmAccessFault+0x359
fffff880`0ac9cae0 000007fe`f4f44b4b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`203fdf50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`f4f44b4b


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiReleaseConfirmedPageFileSpace+86
fffff800`03336cb6 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:  521ea035

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86

BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86

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

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

**Capt.Jack Sparrow** · 05 Jan 2014

ExodusNZ said:

Hi again guys

I have uninstalled AVG - And installed MES / Malwarebytes

But have just had another crash

Yes like koolkat77 asked MemTes86+ is a good idea. Meanwhile could you tell me what USB devices are you using? When did you last update the chipset & USB related drivers? I saw come traces in the earlier dump files.