BSOD during diablo 3. bccode a

072513-10186-01.dmp 25.07.2013 05:46:51 IRQL_NOT_LESS_OR_EQUAL 0x0000000a fffff700`0128e898 00000000`00000000 00000000`00000001 fffff800`02e849d5 ntoskrnl.exe ntoskrnl.exe+75c00 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318-1533) x64 ntoskrnl.exe+75c00 C:\Windows\Minidump\072513-10186-01.dmp 8 15 7601 278*600 25.07.2013 05:48:07


this file. i booted up using the retail x64 windows 7 dvd and tried reformatting the ssd and it gave me a error x80070057. but i found the solution wich i hope u agree with that works wich is: delete ALL partitions
Create ONE partition with the maximum capacity of the drive.
Install Windows

wich i did. but i deleted it 1time then i got the reserved disk on 400mb not the usual 100mb so i kept deleting and reformatting til i got the reserved on 100mb. and then i installed.

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
Take a camera snap of the computer screen before closing memtest, and upload the picture for us.

If memtest comes to be clean, free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
________________________________________________________________________________
BSOD ANALYSIS:

Code:

.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff7000128e898, 0, 1, fffff80002e849d5}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

0: 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: fffff7000128e898, memory referenced
Arg2: 0000000000000000, 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: fffff80002e849d5, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030af100
GetUlongFromAddress: unable to read from fffff800030af1c0
 fffff7000128e898 Nonpaged pool

CURRENT_IRQL:  0

FAULTING_IP: 
nt!MmAccessFault+bb5
fffff800`02e849d5 498904d3        mov     qword ptr [r11+rdx*8],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  Diablo III.exe

TRAP_FRAME:  fffff8800687e7f0 -- (.trap 0xfffff8800687e7f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00041c83fffffffe rbx=0000000000000000 rcx=0000000000041c82
rdx=0000000000041c82 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e849d5 rsp=fffff8800687e980 rbp=fffff8800687ea00
 r8=fffff70001080000  r9=00000000000338dd r10=00000000000338dd
r11=fffff70001080488 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MmAccessFault+0xbb5:
fffff800`02e849d5 498904d3        mov     qword ptr [r11+rdx*8],rax ds:fffff700`0128e898=ba710600831c0400
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e771a9 to fffff80002e77c00

STACK_TEXT:  
fffff880`0687e6a8 fffff800`02e771a9 : 00000000`0000000a fffff700`0128e898 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx
fffff880`0687e6b0 fffff800`02e75e20 : 00000000`00000001 fffff700`0128e898 00000000`00000000 80000001`276c486f : nt!KiBugCheckDispatch+0x69
fffff880`0687e7f0 fffff800`02e849d5 : fffffa80`037644c0 fffff880`0687ea00 fffffa80`0e112b00 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0687e980 fffff800`02e75d2e : 00000000`00000001 00000000`31962000 00000000`00000001 00000000`0d350b14 : nt!MmAccessFault+0xbb5
fffff880`0687eae0 00000000`6e223573 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0e56fe1c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6e223573


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`02e75e20 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260

BUCKET_ID:  X64_0xA_nt!KiPageFault+260

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

here is the memtest86+ with 8 passes and no errors. so we know its not the ram. should i continue with the driver verifier?

yes, there is a fly on my monitor...

Did it ask for a reboot after you finished the settings?

If so, after the reboot verifier enables. Verifier makes the computer laggy.

You may open a command prompt and type verifier /query there and hit enter. If it results up a long list of drivers, DV is running there.

Yes, that is needed. You the computer to ins most crash prone actions. Try to replicate the BSODs.