Some BSODs are caused by Gigabyte on-Off charger, which is a very often culprit.
Code:
BugCheck 50, {fffff88804420428, 0, fffff8800441d4a0, 5}
*** WARNING: Unable to verify timestamp for UsbCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for UsbCharger.sys
Could not read faulting driver name
Probably caused by : UsbCharger.sys ( UsbCharger+24a0 )
Followup: MachineOwner
---------
Uninstall is suggested. I'd recommend you to
http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html, 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.
Intel Gigabit network is failing.
Code:
fffff880`125467c8 fffff880`1016c9efUnable to load image e1d62x64.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for e1d62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1d62x64.sys
e1d62x64+0x279e[/COLOR]f
Search for possible updates in
https://downloadcenter.intel.com/default.aspx
Juniper network is failing, too.
Code:
fffff880`12546048 fffff880`0542eb30Unable to load image jnprna6.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for jnprna6.sys
*** ERROR: Module load completed but symbols could not be loaded for jnprna6.sys
jnprna6+0x6b30[/COLOR]
It appears to be recent, but still search for updates. Probably in
Network Security Solutions - Networking Performance Optimization
Search for Intel XHCI drivers in
https://downloadcenter.intel.com/default.aspx, too.
Not getting any evidence against it, but I would suggest you to uninstall PeerBlock, at least as a test, as it causes dense network related BSODs.
Plus, due to the versatility of the issues, test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
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 results.