BSOD with same bug check code third time in the last 2 weeks

OK, thanks.

Sorry for the delay. My internet has been down. But this is the result of the last dump

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d8baf886d3, b3b7465f0d755629, fffff80003336290, 1}
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See Kernel patch protection for x64-based operating systems
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d8baf886d3, Reserved
Arg2: b3b7465f0d755629, Reserved
Arg3: fffff80003336290, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
 0 : A generic data region
 1 : Modification of a function or .pdata
 2 : A processor IDT
 3 : A processor GDT
 4 : Type 1 process list corruption
 5 : Type 2 process list corruption
 6 : Debug routine modification
 7 : Critical MSR modification

I'm struggling to see anything beyond RAM here, no drivers are showing and nothing hints towards drivers at all. I'll have a think and try and work the dump files again, very strange.

Adechi, I asked Boozad to come take a look because all I could see is Ram. I asked you to run Driver Verifier because you ran Memtest86+ and it was still crashing. Sometimes a bad driver will cause a ram error. It seems that is not the case here.

Please look in Add Remove Programs and Uninstall any of the programs you find there. They are all Gigabyte utilities

Code:

APP Center
V-Tuner
System Information Viewer
Smart Recovery 2 
Smart Time Lock
Fast Boot
EZ Setup
EasyTune
@BIOS
Cloud Station 
USB Blocker
On/Off Charge™ / On/Off Charge™ 2
CFOS Speed Internet Accelerator Software

Then I need you to run memtest86+ again for as many passes as possible. If you get an error, stop the test.

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask

OK, I just wanted to be sure about the Gigabyte programs. I hate to ask you to run it again, but everything we can find in the dump files says Memory Corruption. Let it run as many passes as you can and before shutting it down, please post a picture of the screen. I just want to see what information it is reading.

OK, thanks.