Random BSOD x109

[ledsd]

thanks for the help , this is driving me crazzzy

this is very random and unable to repeat or make happen
have ran all test and diagnostics along with passmark bitprox64
have not been able to throw bsod even with driververifier
virus scans show nada, no rootkits
have disable VMware
removed gigabytes software
I was setup on dual boot with windows 8 and on windows 8 I never had a bsod. so that should clear any hardware or memory problem too.
I have done everything I can think up but I just cant get this down to the driver or program that is causing this

my specs:
windows 7 x64
Samsung ssd 120g
wd 500g 4 partitions
wd 1t
wd 1t
wd 1t mybook
wd 2t pluggable
wd 2t mybooklive
GeForce GTX 650
Hauppauge WinTV hvr-1800
usrobotics 56k pci fax modem

OS Name Microsoft Windows 7 Ultimate
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name WIN7_SSD
System Manufacturer Gigabyte Technology Co., Ltd.
System Model GA-970A-UD3
System Type x64-based PC
Processor AMD FX(tm)-6100 Six-Core Processor, 3300 Mhz, 3 Core(s), 6 Logical Processor(s)
BIOS Version/Date Award Software International, Inc. F8a, 12/20/2012
SMBIOS Version 2.4
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume6
Locale United States
Hardware Abstraction Layer Version = "6.1.7601.17514"
Time Zone Central Daylight Time
Installed Physical Memory (RAM) 12.0 GB
Total Physical Memory 12.0 GB
Available Physical Memory 8.96 GB
Total Virtual Memory 24.9 GB
Available Virtual Memory 21.6 GB
Page File Space 13.0 GB
Page File C:\pagefile.sys

 

[koolkat77]

Reduce items at start up:

Performing a Clean Startup in Windows 7

Add, or Remove Startup Programs in Windows 7
​

Your Antivirus software is basically whats just needed there.

I would recommend you take memtest again.

Test and Diagnose RAM Issues with Memtest86+:

RAM - Test with Memtest86+​

:info: Pay close attention to part 3 of the tutorial "If you have errors"

   Tip

• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d8a1fc25e4, b3b7465ef478f53a, fffff800039dea78, 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
---------

4: 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 http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
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: a3a039d8a1fc25e4, Reserved
Arg2: b3b7465ef478f53a, Reserved
Arg3: fffff800039dea78, 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

Debugging Details:
------------------


FAULTING_IP: 
nt! ?? ::NNGAKEGL::`string'+4e3a7
fffff800`039dea78 488b4c2460      mov     rcx,qword ptr [rsp+60h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x109

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03394498 00000000`00000000 : 00000000`00000109 a3a039d8`a1fc25e4 b3b7465e`f478f53a fffff800`039dea78 : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800039decfc - nt! ?? ::NNGAKEGL::`string'+4e62b
	[ 00:02 ]
1 error : !nt (fffff800039decfc)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

If you have an SSD, make sure the firmware is up-to-date.

Upload a screenshot using:

CrystalDiskInfo​

:tip: For how to upload a screenshot or file, read here

Test your Hard Drive by running:

Hard Drive Diagnostic Procedure​

CHKDSK is verifying files (stage 1 of 5)...
  253184 file records processed.                                         

File verification completed.
  8 large file records processed.                                   

  0 bad file records processed.                                     

  0 EA records processed.                                           

  0 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 5)...
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x295 is incorrect.
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
Correcting error in index $I30 for file 661.
The index bitmap $I30 in file 0x295 is incorrect.
Correcting error in index $I30 for file 661.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Sorting index $I30 in file 661.
  315060 index entries processed.                                        
Recovering orphaned file axvlc.dll.manifest (1623) into directory file 661.
  25 unindexed files scanned.                                        
Recovering orphaned file UNINST~1.EXE (1624) into directory file 661.
Recovering orphaned file uninstall.exe (1624) into directory file 661.
  0 unindexed files recovered.                                      
CHKDSK is verifying security descriptors (stage 3 of 5)...
  253184 file SDs/SIDs processed.                                        

Cleaning up 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.
Cleaning up 3 unused security descriptors.
Security descriptor verification completed.
  30939 data files processed.                                           

CHKDSK is verifying Usn Journal...
  37206280 USN bytes processed.                                            

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  253168 files processed.                                                

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  6391008 free clusters processed.                                        

Free space verification is complete.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.


 112639999 KB total disk space.
  86625716 KB in 206003 files.
     91056 KB in 30940 indexes.
        20 KB in bad sectors.
    359175 KB in use by the system.
     65536 KB occupied by the log file.
  25564032 KB available on disk.

      4096 bytes in each allocation unit.
  28159999 total allocation units on disk.
   6391008 allocation units available on disk.

Use the System File Checker tool and Run Disk Check:

Repair Windows 7 System Files with System File Checker

Run Disk Check in Windows 7 for Bad Sectors & Errors​