Random BSOD, x5 today; various error codes

Most of the BSODs are stop 0x109, which is a mystery bugcheck from the troubleshooting perspective. Here it is reporting a memory corruption.

Code:

BugCheck 109, {a3a039d89c24e51c, b3b7465eeea1b472, fffff80003413035, 1}

*** 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
---------

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result.

Now let us search for any buggy driver that may cause memory corruption by sending bad info to it.

Enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

All them are pointing to some Gigabyte bloatware, which is too old, too. It is some bundled bloat of the motherboard's driver CD which should not be installed.

I'd recommend you to Clean Up Factory Bloatware, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

_____________________________________________________

Code:

BugCheck C4, {f6, 128, fffffa80079467d0, fffff88007fe1809}

*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )

Followup: MachineOwner
---------

Code:

    Image name: gdrv.sys
    Timestamp:        Fri Mar 13 08:52:29 2009

Code:

BugCheck 109, {a3a039d89d26c9dc, b3b7465eefa39932, fffff80003413030, 1}

*** 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
---------

As your post #3 ensures that the RAM is free from error, you need to give Driver Verifier another go.