BSOD with set of 4 RAM??? But fine otherwise.

[croftyness]

I have 4x4gb corsair vengeance on a ASUS P8z77 v pro mobo.. I have had the setup working for a while, until one day I started getting BSODs.

I started investigating the memory

I have tested each RAM separately on memtest86. All pass the test on their own. (1 Pass)
Two will also work together fine. (no errors)
However when they are all together it's unstable and BSOD comes back. Including memtest errors.

To check the slots I ran two test, each with two RAM in alternative slots.

From what I understand all drivers are up to date, I have reset the CMOS and restored default bios settings. But still have the same problem.

Recently I have upgraded my BIOS and overclocked. However I used ASUS software to do it from the internet.
My computer also rarely boots up first time with a set of 4. It will get half way start again then boot up.

I'm happy to supply information you ask for : )

 

[croftyness]

EXMAPLES

On Thu 03/01/2013 19:18:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010313-11169-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x50 (0xFFFFFA8045AD24E8, 0x0, 0xFFFFF800031C7C2C, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 03/01/2013 19:18:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010313-11169-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x50 (0xFFFFFA8045AD24E8, 0x0, 0xFFFFF800031C7C2C, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 03/01/2013 03:38:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010313-11497-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x15B09B)
Bugcheck code: 0xD1 (0xFFF7760C, 0x2, 0x1, 0xFFFFF8800865009B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Wed 02/01/2013 23:52:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010213-11122-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF88007606E92)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF88007606E92)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Wed 02/01/2013 23:36:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010213-11325-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xC5 (0xFFFFF8100305A6B0, 0x2, 0x0, 0xFFFFF80002FFFA4E)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 02/01/2013 23:14:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010213-10826-01.dmp
This was probably caused by the following module: avgidsdrivera.sys (0xFFFFF8800796B33E)
Bugcheck code: 0x50 (0xFFFFF87FD397F168, 0x0, 0xFFFFF8800796B33E, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\avgidsdrivera.sys
product: AVG IDS
company: AVG Technologies CZ, s.r.o.
description: IDS Application Activity Monitor Driver.
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avgidsdrivera.sys (IDS Application Activity Monitor Driver., AVG Technologies CZ, s.r.o. ).
Google query: AVG Technologies CZ, s.r.o. PAGE_FAULT_IN_NONPAGED_AREA

 

[vahn0100]

You will want to run a memtest of each individual stick in each individual slot, so a total of 16 tests. what this will do is eliminate the possibility of it being a stick and slot combination. If all comes clear, more than likely its a motherboard issue causing the problem.