Can your post the rest of the information files as outlined here: Blue Screen of Death (BSOD) Posting Instructions
This will give us additional information to work with.
Have you overclocked anything on your system?
Can you confirm that you tested your RAM with memtest86+?
This is important, your are having RAM faults, running the right test will tell us where the problem is from.
Also need your DRAM voltage, this is important as well, with 8GB ram you will need some adjustments, and I need to know where to start from.
BTW, voltages listed in CPUZ are not actual they are the recommended voltages, go to your BIOS and check under 'AI Tweaker' > DRAM Voltage.
If it only says 'Auto' then select 'Manual' and it should tell you a voltage.
If you don't have your motherboard manual, download it from my post above, you're going to need it.
After you tell me the DRAM voltage we are going to have to re-set some of the timings and adjust the voltages.
You can find this information on pages 2-11, 2-13 and 2-15 in your mobo manual.
Your last crash was STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
This indicates that a severe memory management error occurred.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa800570a7a0
Arg3: 0000000000000845
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41790
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002e7d459 to fffff80002ecdd00
STACK_TEXT:
fffff880`06a5f498 fffff800`02e7d459 : 00000000`0000001a 00000000`00041790 fffffa80`0570a7a0 00000000`00000845 : nt!KeBugCheckEx
fffff880`06a5f4a0 fffff800`02f0012a : fffffa80`09327060 00000000`00000000 f9900002`14799c66 f9900002`14799867 : nt! ?? ::FNODOBFM::`string'+0x21546
fffff880`06a5f5b0 fffff800`02f015d9 : 00000000`00000000 00000000`0c398fff 00000000`00000000 00000000`002120e6 : nt!MiDeleteVirtualAddresses+0x929
fffff880`06a5f770 fffff800`031e48b1 : fffffa80`099ce010 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`06a5f890 fffff960`001159f2 : ffff0800`00000001 fffffa80`08e81830 00000000`00000001 fffff800`02ed08a4 : nt!MiUnmapViewOfSection+0x1b1
fffff880`06a5f950 fffff960`0024eaab : 00000000`00000000 00000000`00000000 00000000`00004b05 00000000`00000000 : win32k!SURFACE::bDeleteSurface+0x502
fffff880`06a5faa0 fffff960`002cf4a8 : fffff900`c1ba48e0 00000000`00000001 fffff900`c1cb4cc0 00000000`7e12135d : win32k!GreDereferenceObject+0x7b
fffff880`06a5fae0 fffff960`002d04c7 : 00000000`00000000 00000000`7e12135d fffff900`c1ba48e0 00000000`03dfa92c : win32k!SFMLOGICALSURFACE::DeInitialize+0x88
fffff880`06a5fb20 fffff960`0022cb73 : 00000000`00000000 fffff900`c00c0010 fffff900`c1ba48e0 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`06a5fb60 fffff960`0024de0c : 00000000`00000001 00000000`00000001 fffff880`06a5fca0 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`06a5fba0 fffff800`02eccf93 : fffffa80`093987e0 fffffa80`093993e0 ffffffff`fffd67f0 fffffa80`093993e0 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`06a5fc20 000007fe`fe354a3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03bef9f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe354a3a
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!SURFACE::bDeleteSurface+502
fffff960`001159f2 eb05 jmp win32k!SURFACE::bDeleteSurface+0x509 (fffff960`001159f9)
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: win32k!SURFACE::bDeleteSurface+502
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4df2dbd1
FAILURE_BUCKET_ID: X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+502
BUCKET_ID: X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+502
Followup: MachineOwner
---------
Your next crash blames memory corruption also:
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
Followup: memory_corruption
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {ffffff8000000320, 2, 0, fffff880049582be}
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffff8000000320, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880049582be, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310c100
ffffff8000000320
CURRENT_IRQL: 2
FAULTING_IP:
dxgmms1!VidSchiProcessCompletedQueuePacketInternal+396
fffff880`049582be 48a12003000080f7ffff mov rax,qword ptr [FFFFF78000000320h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff880030b0690 -- (.trap 0xfffff880030b0690)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880030b07f0 rbx=0000000000000000 rcx=fffffa8008fcc7b0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880049582be rsp=fffff880030b0820 rbp=fffffa80071c25f0
r8=fffff880030b07f0 r9=0000000000000000 r10=fffffa8008fcc7d0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x396:
fffff880`049582be 48a12003000080f7ffff mov rax,qword ptr [FFFFF78000000320h] ds:c780:fffff780`00000320=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002edc2a9 to fffff80002edcd00
STACK_TEXT:
fffff880`030b0548 fffff800`02edc2a9 : 00000000`0000000a ffffff80`00000320 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`030b0550 fffff800`02edaf20 : 00000000`000186a0 00000000`00000000 00000000`0001cf1f fffffa80`07193c40 : nt!KiBugCheckDispatch+0x69
fffff880`030b0690 fffff880`049582be : fffffa80`07193c40 fffffa80`071c25f0 fffffa80`09001000 fffffa80`0818c000 : nt!KiPageFault+0x260
fffff880`030b0820 fffff880`049577da : fffffa80`00000000 fffffa80`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x396
fffff880`030b08e0 fffff880`04956e00 : fffffa80`00000000 fffff880`11258c35 00000000`00000000 00000000`00000001 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x3b6
fffff880`030b0980 fffff880`04956c4c : 00000000`00000001 fffffa80`08fcc010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`030b09d0 fffff880`0485d1cf : fffffa80`0816f480 00000000`00000000 00000000`00000022 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`030b0a20 fffff880`1113f138 : fffffa80`0818c000 fffffa80`0818c000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`030b0a50 fffffa80`0818c000 : fffffa80`0818c000 00000000`00000000 00000000`00000000 fffff880`1113f0cb : nvlddmkm+0xce138
fffff880`030b0a58 fffffa80`0818c000 : 00000000`00000000 00000000`00000000 fffff880`1113f0cb fffffa80`0818c000 : 0xfffffa80`0818c000
fffff880`030b0a60 00000000`00000000 : 00000000`00000000 fffff880`1113f0cb fffffa80`0818c000 00000000`00000000 : 0xfffffa80`0818c000
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
7 errors : !nt (fffff80002edc27d-fffff80002edcb4d)
fffff80002edc270 44 0f 29 60 90 44 0f 29 68 a0 44 0f 29 *78 b0 44 D.)`.D.)h.D.)x.D
...
fffff80002edc2f0 44 0f 29 60 90 44 0f 29 68 a0 44 0f 29 *78 b0 44 D.)`.D.)h.D.)x.D
...
fffff80002edc6b0 84 00 00 00 00 *08 66 66 0f 1f 84 00 00 00 00 00 ......ff........
...
fffff80002edca20 0f 6f 50 70 66 44 0f 6f 98 80 00 00 00 *6e 44 0f .oPpfD.o.....nD.
...
fffff80002edcaa0 0f 1f 84 00 00 *08 00 00 66 66 66 66 66 66 66 0f ........fffffff.
fffff80002edcab0 1f 84 00 00 00 *08 00 66 0f 1f 84 00 00 00 00 00 .......f........
...
fffff80002edcb40 f9 ff ff fb e8 97 64 0b 00 65 0f ae 14 *2d 80 01 ......d..e...-..
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
Followup: memory_corruption
---------
These are the first two crashes, neither are much help, they have very little information.
Not much info here, STOP 0x1000000A: IRQL_NOT_LESS_OR_EQUAL
Code:
*******************************************************************************
* *
* 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: fffff00003026f78, 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: fffff80002e98312, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bc100
fffff00003026f78
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiTimerExpiration+f2
fffff800`02e98312 48894808 mov qword ptr [rax+8],rcx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9caa0 -- (.trap 0xfffff80000b9caa0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff00003026f70 rbx=0000000000000000 rcx=fffff80003002328
rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e98312 rsp=fffff80000b9cc30 rbp=000000000000f905
r8=fffffa8004f5dc20 r9=00000000000000c0 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!KiTimerExpiration+0xf2:
fffff800`02e98312 48894808 mov qword ptr [rax+8],rcx ds:6460:fffff000`03026f78=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e8c2a9 to fffff80002e8cd00
STACK_TEXT:
fffff800`00b9c958 fffff800`02e8c2a9 : 00000000`0000000a fffff000`03026f78 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c960 fffff800`02e8af20 : fffff800`02fffe80 fffff780`00000320 00000000`0000f905 00000002`50c48534 : nt!KiBugCheckDispatch+0x69
fffff800`00b9caa0 fffff800`02e98312 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00007429 : nt!KiPageFault+0x260
fffff800`00b9cc30 fffff800`02e981c7 : 00000000`b9f12ac0 00000000`0000f905 00000000`b9f12abb 00000000`00000005 : nt!KiTimerExpiration+0xf2
fffff800`00b9ccd0 fffff800`02e84a2a : fffff800`02fffe80 fffff800`0300dcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTimerExpiration+f2
fffff800`02e98312 48894808 mov qword ptr [rax+8],rcx
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiTimerExpiration+f2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b
FAILURE_BUCKET_ID: X64_0xA_nt!KiTimerExpiration+f2
BUCKET_ID: X64_0xA_nt!KiTimerExpiration+f2
Followup: MachineOwner
---------