Getting a lot of BSOD with different errors/different dumps

I wouldn't download drivers from a third party program, it isn't that reliable so i would just find them from the Nvidia website. When have you been getting these BSODs? Right when you started using the pc, after a download?

edit: new realtek drivers release a few days ago

http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

-------------------
I would run :
chkdsk /f /r <-------- check/fix issues with the harddrive
SFC.exe /scannow <-------- check for and fix any corruption in core windows files

if no errors found:
update BIOS from version f2 to version f4 from the gigabyte website
I don't think it is your problem but it will reset your BIOS defaults and a update can not hurt.
I mention this because the BIOS reported you used 1.6 v to your CPU, this is high. The new BIOS should select the correct default value.
I would also update any chipset drivers you can get directly from AMD (for the AMD sata controller)
using a 3rd party driver collecter/installer can sometimes be a issue. some of the motherboard provided drivers will have custom fixes for particular bugs in the hardware on that motherboard. (but I have no reason to suspect that is the issue)

Note: the debugger did not detect any memory corruption in any loaded core window modules.
I would run crystaldiskinfo and look at the info for the drive, maybe run a drive diagnostic tool on the drive



you have 2 net cards and a AMDsata controller.




Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
System Uptime: 0 days 14:45:10.832



BugCheck 1E, {ffffffffc0000005, fffff8001fc54df5, 0, ffffffffffffffff}
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8001fc54df5, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8001fc54df5, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

EXCEPTION_CODE: (NTSTATUS) 0xc0000005
2: kd> kc
Call Site
nt!KeBugCheckEx
nt! ?? ::FNODOBFM::`string'
nt!KiExceptionDispatch
nt!KiGeneralProtectionFault
nt!ExpInterlockedPopEntrySListFault16
nt!MiGetPage
nt!MiResolveDemandZeroFault
nt!MmAccessFault
nt!KiPageFault
0x0




BIOS Release Date 08/10/2012
machine info:

BIOS Version F2
Manufacturer Gigabyte Technology Co., Ltd.
Product Name GA-78LMT-USB3
Processor Version AMD FX(tm)-4100 Quad-Core Processor
Processor Voltage 90h - 1.6V


drivers of interest:
2: kd> lmvm bcmwlhigh664
start end module name
fffff880`0a648000 fffff880`0a77f000 bcmwlhigh664 (deferred)
Image path: \SystemRoot\system32\DRIVERS\bcmwlhigh664.sys
Image name: bcmwlhigh664.sys
Timestamp: Tue Apr 19 00:13:08 2011 (4DAD3604)
CheckSum: 001369BC
ImageSize: 00137000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Unloaded modules:
fffff880`0a648000 fffff880`0a77f000 bcmwlhigh664
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00137000
fffff880`0a6db000 fffff880`0a80c000 bcmwlhigh664
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00131000

2: kd> lmvm Rt630x64
start end module name
fffff880`074ef000 fffff880`075be000 Rt630x64 (deferred)
Image path: \SystemRoot\system32\DRIVERS\Rt630x64.sys
Image name: Rt630x64.sys
Timestamp: Mon Nov 25 23:32:54 2013 (52944EA6)
CheckSum: 000CE221
ImageSize: 000CF000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

floppy disk controller

2: kd> lmvm amdide64
start end module name
fffff880`00feb000 fffff880`00ff2000 amdide64 (deferred)
Image path: \SystemRoot\System32\drivers\amdide64.sys
Image name: amdide64.sys
Timestamp: Tue Dec 04 01:49:28 2012 (50BDC728)
CheckSum: 00009B91
ImageSize: 00007000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

amd sata controller driver

edit: most likely cause?
I would uninstall/remove all of your nvidia drivers including your graphics card sound drivers
they appear to be from different driver builds. Then install them directly from nvidia reboot and retest fro failure

here are some suspects
bcmwlhigh664 Tue Apr 19 00:13:08 2011 (network driver)
nvhda64v.sys Sun Jun 16 05:38:07 2013
nvlddmkm.sys Mon Nov 11 05:24:05 2013
nvvad64v.sys Fri Dec 27 08:41:28 2013
Rt630x64.sys Mon Nov 25 23:32:54 2013 (network driver)
fdc (floppy disk controller, really???)
scmndisp.sys Tue Jan 16 23:48:03 2007 <------- Netgear Neutral Wireless Solution
amdide64.sys Tue Dec 04 01:49:28 2012 (amdsata driver)

Notes: i would look at the netgear driver because of the file date
------------------------
I think you have a device driver that is causing the corruption, but the bugchecks are coming from other drivers that are victim's of the first driver's mistake. These are very hard to find. I would suspect ALL 3rd party drivers simply because the microsoft drivers get checked and updated via windows update when these errors are found.

if sfc.exe found a error it could not correct it is generally because of a driver is corrupted and the backup copy is also corrupted in its driver store.
on windows 8 you can fix this with the dism.exe command

start cmd.exe as a admin
dism.exe /online /cleanup-image /restorehealth <---- this will get a online copy from a trusted source

when it is done
run the sfc.exe /scannow
if it come up ok, then reboot
but run the sfc.exe /scannow command a second time after the reboot

depends on what file was actually fixed and if it was the cause of your problem.