Hello, ZoBlitz. I have looked at your dump files and they were all basically the same. They all listed the same cause in the header, but listed several causes in the dump itself. I am going to list them for you all in one dump. But, keep in mind that most of them were listed in several dumps.
Code:
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff80003296720}
[COLOR=red]Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsFreeCloneNetBufferList0+cf )[/COLOR]
Followup: MachineOwner
That is a Windows Update dealing with the network
fffff880`039fd958 fffff880`13a945b1Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** [COLOR=red]ERROR: Module load completed but symbols could not be loaded for atikmdag.sys[/COLOR]
atikmdag+0x295b1
Your Graphics driver
ffff880`039fd2a8 fffff880`14de76ebUnable to load image \SystemRoot\system32\DRIVERS\usbfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** [COLOR=red]ERROR: Module load completed but symbols could not be loaded for usbfilter.sys[/COLOR]
usbfilter+0x16eb
Obviously the USB system
fffff880`039fc610 fffff880`056a0000Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** [COLOR=red]ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys[/COLOR]
Rt64win7+0x14000
That is your Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
ffff880`039fc038 fffff880`06e262b0Unable to load image \SystemRoot\System32\Drivers\dump_amd_sata.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dump_amd_sata.sys
*** [COLOR=red]ERROR: Module load completed but symbols could not be loaded for dump_amd_sata.sys[/COLOR]
[COLOR=black]Part of the Sata Drivers[/COLOR]
fffff880`0391b9c8 fffff880`023565dcUnable to load image \SystemRoot\system32\DRIVERS\SamsungRapidDiskFltr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SamsungRapidDiskFltr.sys
[COLOR=red]*** ERROR: Module load completed but symbols could not be loaded for SamsungRapidDiskFltr.sys[/COLOR]
SamsungRapidDiskFltr+0x35dc
Samsung Rapid Mode
ffff880`0391b848 fffff880`04828165Unable to load image \SystemRoot\system32\DRIVERS\klim6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klim6.sys
[COLOR=red]*** ERROR: Module load completed but symbols could not be loaded for klim6.sys[/COLOR]
klim6+0x2165
That is the Kaspersky Lab Intermediate Network Driver
ffff880`0391b218 fffff880`01a668f0Unable to load image \SystemRoot\system32\DRIVERS\kneps.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for kneps.sys
[COLOR=red]*** ERROR: Module load completed but symbols could not be loaded for kneps.sys[/COLOR]
kneps+0x1d8f0
Kaspersky KNEPS Power driver
That is a lot of problems all at the same time. Obviously, there is only 1 or 2 of them are the cause, the rest are victims. If I had to hazard a guess right now, I would be looking at your network drivers. I would like you to go to your motherboard's web site and update all of your drivers. I would also like you to make sure all of your Windows Updates are current. Please check the update history and see if there are any failures. If there are, please look and see if they were later installed successfully.
Please go to Device Manager and see if there are any yellow triangles or exclamation marks on any of the entries there.
Next, please open an elevated command prompt ( click start, type
cmd in the search box,
right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste
sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
Please also take Rapid Mode off. After all of that, please see if your problems get better. Let me know the results please.