New
#31
Screenshot of Seagate Tools screen attached.
I've also taken the older Seagate drive out for now.
Screenshot of Seagate Tools screen attached.
I've also taken the older Seagate drive out for now.
Hmm. You now need to plan for a dismantle and re-seat the computer. Probably the cabling is not in perfect state, and it is a good cause of a stop 0xf4 BSOD.
And more
EDIT: As a final throw of the dice i've removed half the RAM. The RAM I have is on the motherboard manufacturer's approved RAM list (4x4GB Corsair Vengeance 1600) but I have read a few observations that some Gigabyte motherboards have been playing up with >2 DIMMs in place.
Last edited by bigfatron; 11 Jul 2013 at 16:54.
It should not be the final throw.
Have you tried the seatools test after re-seating the cables? What is the result? And what is the result of the memtest?
Moreover, there are some BSODs during using Steam. It is quite usual. Needs more troubleshooting on it.
When the Intel(R) Ethernet Connection I217-V driver e1d62x64.sys is failing despite of being the latest version, it is something there that is causing the blockage to the network. AVG is a known victim.
Uninstall AVG. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.
It will attempt to minimize the netio.sys caused BSOD.
Let us know the results, all inclusive. For any further BSOD, post it following the Blue Screen of Death (BSOD) Posting Instructions. It needs more troubleshooting, as it is a multiple issue and you are a steam gamer.
__________________________________________________________________________
BSOD ANALYSIS:
Code:BugCheck 1A, {41287, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+454f5 ) Followup: MachineOwner ---------------------------------------------------------------------------------- BugCheck D1, {fffffaa00dfd7430, 2, 1, fffff88001488211} *** WARNING: Unable to verify timestamp for e1d62x64.sys *** ERROR: Module load completed but symbols could not be loaded for e1d62x64.sys *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : NETIO.SYS ( NETIO!NetioDereferenceNetBufferListChain+132 ) Followup: MachineOwner ------------------------------------------------------------------------------------- BugCheck A, {fffffa001153ffd8, 2, 0, fffff80003071621} Probably caused by : ntkrnlmp.exe ( nt!AlpcpQueueIoCompletionPort+41 ) Followup: MachineOwner ---------
For Seatools I was stuck with the issue that it couldn't see any disks at all (I posted the screenshot as you requested). If you've got any theories on getting it to work then i'm open to suggestion. I did wonder if my BIOS having AHCI mode enabled was the issue and I should perhaps switch it back to IDE?
I know what you're saying about the antivirus stuff but i've now used three anti-virus products including MSE for an extended period and was getting the same crashes for all. Likewise the system has been scanned using a number of products several times with nothing untowards coming up.
As for reducing the number of DIMMs to two, I left the PC running in Windows overnight pulling down a load of games images over Steam, UPlay and Origin to keep it busy. I had also cranked the RAM frequency back up to 1600 as this previously increased the frequency of BSOD incidents (i've been running it at 1333 most of the time since i've had problems). Despite all this the machine did not crash in the 7 or so hours I left it running. It might just be luck but i'll know more when i've had a chance to run it over the weekend.
So far so good. BSOD incidents since switching to 2 DIMMs = 0. Had one lock-up but that was absolutely my own fault (accidentally flicked a cable out whilst sticking the side panel back on). Will update again in a day or two.
Monday morning and still absolutely solid as a rock on 2 DIMMs. I think we have our answer so its time to continue my frank conversation with Gigabyte.
Thanks again for all your help guys, your efforts have been massively appreciated.