New
#11
Another minidump file after i have started Diablo 3
Another minidump file after i have started Diablo 3
BSOd analyze
http://www.carrona.org/bsodindx.html#0x00000050
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
Test your memory using memtest86+ preferably overnight for 8 passes:Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff10006299618, 1, fffff80002f22316, 7} Could not read faulting driver name *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption --------- 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffff10006299618, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff80002f22316, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000007, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb9100 fffff10006299618 FAULTING_IP: nt!MmPrefetchForCacheManager+a fffff800`02f22316 4889540410 mov qword ptr [rsp+rax+10h],rdx MM_INTERNAL_CODE: 7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x50 PROCESS_NAME: System CURRENT_IRQL: 0 TRAP_FRAME: fffff8800314c930 -- (.trap 0xfffff8800314c930) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8800314cb40 rbx=0000000000000000 rcx=fffffa800f7029c0 rdx=000000000067a000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002f22316 rsp=fffff8800314cac8 rbp=fffff80002e27280 r8=0000000000036000 r9=0000000000000005 r10=000000000000000f r11=19d00003e6e7d921 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!MmPrefetchForCacheManager+0xa: fffff800`02f22316 4889540410 mov qword ptr [rsp+rax+10h],rdx ss:0018:fffff100`06299618=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002c30e97 to fffff80002c8a1c0 STACK_TEXT: fffff880`0314c7c8 fffff800`02c30e97 : 00000000`00000050 fffff100`06299618 00000000`00000001 fffff880`0314c930 : nt!KeBugCheckEx fffff880`0314c7d0 fffff800`02c882ee : 00000000`00000001 fffff100`06299618 00000003`e7a76900 00000000`0067a000 : nt! ?? ::FNODOBFM::`string'+0x43cd1 fffff880`0314c930 fffff800`02f22316 : fffff800`02c32887 fffffa80`0f7029c0 00000000`006c0000 00000000`0067a000 : nt!KiPageFault+0x16e fffff880`0314cac8 fffff800`02c32887 : fffffa80`0f7029c0 00000000`006c0000 00000000`0067a000 fffff800`02e27280 : nt!MmPrefetchForCacheManager+0xa fffff880`0314cad0 fffff800`02ccf1ae : fffffa80`0f7029c0 00000000`00000000 fffff800`00000005 00000000`00000701 : nt!CcPerformReadAhead+0x2f3 fffff880`0314cc00 fffff800`02c93841 : fffffa80`0cba1530 fffff800`02e27201 fffff800`02e888d0 00000000`00000003 : nt!CcWorkerThread+0x21e fffff880`0314ccb0 fffff800`02f20e6a : 00000100`00000000 fffffa80`0caa3b50 00000000`00000080 fffffa80`0ca95040 : nt!ExpWorkerThread+0x111 fffff880`0314cd40 fffff800`02c7aec6 : fffff880`03088180 fffffa80`0caa3b50 fffff880`03093040 03020304`01020401 : nt!PspSystemThreadStartup+0x5a fffff880`0314cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff80002f22319 - nt!MmPrefetchForCacheManager+d [ 24:04 ] 1 error : !nt (fffff80002f22319) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT Followup: memory_corruption
RAM - Test with Memtest86+
Post back results
I have tested the RAM and there are no errors.
I have 4 modules and I have tested it for 5 passes
Alright.
Lets insert one bye one each and see how your computer performs. Once you've tested them that way insert all together and see if you get bsod again.
Ok after testing the memories one by one all tests are successful, but i have discovered that now there is issue with DIMM ports A, because then the memories are in DIMM A port there are only errors but when they are in DIMMs B ports it is ok . I am thinking that this ASUS model motherboard is peace of crap because before two weeks ago they replaced my motherboard because the similar issue with DIMM B ports.
I have not overclocked but here is hardware issue![]()
yes you are right I will try to get another model and get back to you :)