Hello BenDover, I will try to help you. It is difficult to debug a system with a single dump file, but we'll give it a shot. First thing is be as descriptive as possible in your system specs and list everything in your computer such as PSU and CPU cooler. Manufacturer and model help us to help you. We sometimes need to look up a component and need the necessary info to do that. Also, if you are overclocking anything, please set it back to default levels until we get things straightened out.
The first thing I will tell you is to uninstall any Gigabyte Utilities. They are a confirmed cause of BSODs.
This is what your dump files said
Code:
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff6fb7d0c244c, 1, fffff800026f8b0d, 2}
Could not read faulting driver name
Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+3f390 )
This is what was listed as the cause
Code:
cfosspeed6
start end module name
fffff880`02e0d000 fffff880`02feb000 cfosspeed6 T (no symbols)
Loaded symbol image file: cfosspeed6.sys
Image path: \SystemRoot\system32\DRIVERS\cfosspeed6.sys
Image name: [COLOR=red]cfosspeed6.sys[/COLOR]
Timestamp: Mon Jul 21 11:06:41 2014 (53CD3A91)
CheckSum: 001D672B
ImageSize: 001DE000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
That is cFosSpeed - The Internet Accelerator Please uninstall it.
Also, open a 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.