Blue screens that drive me crazy since I bought a new motherboard (windows 8.1)

Hi guys,
I have tried several things to solve my problem, without results... Please help, I'm desperate

- I did a memtest86+ during 16h (almost 7 complete passes) : 0 error.
- I tested all my HDD (with the softwares of the brand : seagate, wd, samsung) : no error, the programs say that my hdd are in good health.
- I did a scandisk on each HDD.
- My temperatures are ok -> CPU : 37° (max on charge 60°) ; Mobo : 40° (max 52°) ; GPU : 35° (max 88°).
- I came back on Windows 7 (I did a new install) and I installed the drivers on the gigabyte website + only necessary programs to have a normal activity (firefox, vlc, libreoffice...) : same problem of blue screen than in Windows 8.1.

I don't know what's happening, and it drives me crazy. Those problems have emerged since I changed my motherboard and my Ram. The fact that I didn't have those problems with my old Asus mainboard make me think that's a hardware problem. But all the tests are good !!? Maybay it's a incompatibility ? I don't know what to do...

Here's my WhoCrashed log on Windows 8.1. I think that it suggests a memory problem :

On Wed 22-04-15 17:24:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042215-6093-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR

On Wed 22-04-15 17:23:14 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF680003B0500, 0x80000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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 Tue 21-04-15 14:05:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042115-6000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1A (0x41793, 0xFFFFF680000C4B20, 0x2, 0x1)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
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 Sun 19-04-15 15:58:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041915-7125-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF800009DD9C4)
Bugcheck code: 0x109 (0xA3A01F589202270D, 0xB3B72BDEE4815D24, 0xFFFFF800009DD9C4, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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 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 Mon 13-04-15 12:57:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041315-6343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x50 (0xFFFFF6840000F308, 0x0, 0xFFFFF803016BF67E, 0x2)
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 Wed 08-04-15 21:28:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040815-8468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0x109 (0xA3A00F58B7E829BE, 0xB3B71BDF0A656D11, 0xFFFFF803FB607668, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 kernel has detected critical kernel code or data corruption.
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.

Here's the WhoCrashed log on Windows 7 :

On Wed 29/04/2015 16:27:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042915-11076-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF88000E42C87)
Bugcheck code: 0x50 (0xFFFFF880030A1068, 0x1, 0xFFFFF88000E42C87, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
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 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 29/04/2015 16:27:25 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x33C87)
Bugcheck code: 0x50 (0xFFFFF880030A1068, 0x1, 0xFFFFF88000E42C87, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
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 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.

Any idea ? Thank you !
Joël

I forgot :
- I also updated the BIOS of my motherboard,
- and the firmware of my SSD.
No change.

Crashes continue on Win7, but for different reasons that Win8.1 (see log of WhoCrashed below).
Any idea ?

On Sat 02/05/2015 11:12:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050215-10342-01.dmp
This was probably caused by the following module: cng.sys (cng+0x4D6E5)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF880011416E5, 0xFFFFF88008DF19C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sat 02/05/2015 11:12:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cng.sys (cng!AppHashComputeFileAttributes+0x11675)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF880011416E5, 0xFFFFF88008DF19C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.

Hi bonou2, thank you for your answer !

I hate Windows update, and I always disable it during the installation of Windows. So, it couldn't be Windows update...
Furthermore, my installation of Windows is EXACTLY the same as before, when I had my old motherboard, and I had no pb at all !

The difference is the hardware (mobo and ram + new HDD), and so the drivers of the mobo (chipset AMD 970 + SB950, network card, usb 3).
The fact that I have exactly the same problems with Win7 and Win8.1 is disturbing : that makes me think that's a hardware problem. What do you think ?

Now I have to find other sticks of DDR3 to verify if the memory is not the cause of my troubles. I will also test an other CPU, and disconnect all others HDD than my main SSD and all USB devices (and maybe my soundcard, to be sure). If it crashes again, it will mean that my mobo is responsible. Am I right ?

It's so irritating... That was an upgrade to improve my PC, and now I take so much time to do benchmarks and several tests to solve the problem...

I have exchanged the RAM with a friend (He gave me his sticks, I gave him mine), and now he has blue screen. So it was the RAM...