Welcome to SevenForums.
Please uninstall the following software using the free version of
Revo Uninstaller (Use advanced mode to uninstall):-
Code:
- Start Menu\Programs\GIGABYTE Public:Start Menu\Programs\GIGABYTE Public
- Start Menu\Programs\GIGABYTE\AutoGreen Public:Start Menu\Programs\GIGABYTE\AutoGreen Public
- Start Menu\Programs\GIGABYTE\ET6 Public:Start Menu\Programs\GIGABYTE\ET6 Public
- Start Menu\Programs\GIGABYTE\GHOST(6980) Public:Start Menu\Programs\GIGABYTE\GHOST(6980) Public
Quote:
GIGABYTE On/Off Charge driver. See here for details -
GIGABYTE ON/OFF Charge
May cause BSOD on Windows 7 systems - uninstall to test
Avast! antivirus is also contributing in BSOD-s. Please uninstall and replace with Microsoft Security Essentials at least to test.
Code:
Start Menu\Programs\avast! Free Antivirus Public:Start Menu\Programs\avast! Free Antivirus Public
Recommended antivirus program for Windows 7 based on stability compared to others:-

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.
Run a full scan with both (separately) once downloaded, installed and updated.
Upload a screenshot of your hard disk using crystal disk info and summary tab using speccy:
Run the System File Checker that scans the of all protected
Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
- Click on the

- Type CMD on Search
- Left click and Run as Administrator
- Type SFC /scannow
Full tutorial here:
Run Disk Check on your hard disk for file system errors and bad sectors on it:
Free up the start-up, nothing except the antivirus is usually needed.
Update the video card drivers in the following manner:
Click on the Start

► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; NVIDIA and restart the system. Delete remnants of its drivers/older drivers using
Driver Fusion/Sweeper
Download link and stabled version:
*Report if there is any improvement.
Then test your ram, Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Quote:
The goal is to test all the RAM sticks and all the motherboard slots.
Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.
If you get errors, stop the test and continue with the next step.
1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.
2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.
If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.
In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Errors are sometimes found after 8 passes.

Do this test overnight, before going to bed.
BUG CHECK SUMMARY: Code:
STOP 0x00000019: BAD_POOL_HEADER
Usual causes: Device driver
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: csrss.exe
..................................................................
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM),
Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
BugCheck 50, {fffff8bf0fae5d8f, 8, fffff8bf0fae5d8f, 5}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+437c1 )
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: SearchIndexer.
..................................................................
STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure,
Installing a faulty or mismatched hardware (especially memory) or a failure after installing it,
3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards,
Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard,
Missing Service Pack
BugCheck 7F, {8, 80050033, 406f8, fffff8800f6e1c88}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+2b7c88 )
Timestamp: Tue May 15 13:35:36 2012 (4FB20748)
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: Stress.exe
..................................................................
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM),
Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
BugCheck 50, {ffffffffffffffd0, 1, fffff8000f8e432c, 0}
*** WARNING: Unable to verify timestamp for AppleCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
Could not read faulting driver name
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : AppleCharger.sys ( AppleCharger+1a9b ) [GIGABYTE On/Off Charge driver. See here for details - http://www.gigabyte.us/MicroSite/185/on-off-charge.htm
May cause BSOD on Windows 7 systems - uninstall to test]
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
Timestamp: Wed Nov 02 08:46:00 2011 (4EB0AEE8)
..................................................................
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
BugCheck 1A, {41790, fffffa8004dd8ac0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: dllhost.exe
..................................................................
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
BugCheck 1A, {41790, fffffa8004dd8b20, ffff, 0}
Probably caused by : win32k.sys ( win32k!FreeView+a2 )
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: rundll32.exe
..................................................................
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM),
Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
BugCheck 50, {fffff8af02eb1010, 0, fffff8000f9b89bc, 5}
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Could not read faulting driver name
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: audiodg.exe
...................................................................
STOP 0x00000024: NTFS_FILE_SYSTEM
Usual causes: Disk corruption, insufficient physical memory, Device driver,
Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
BugCheck 24, {1904fb, fffff88003593468, fffff88003592cc0, fffff8000f83ff75}
Probably caused by : ntkrnlmp.exe ( nt!RtlSubtreePredecessor+9 )
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System Good luck.