New
#11
Got another crash. Swapping cables around now.
BSOD New build, Random times, multiple stop codes
-
-
New #12
We need to know the situation after swapping the cables.Code:ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified. DISK_HARDWARE_ERROR: There was error with disk hardware
-
New #13
Cables have been moved to different ports. Just waiting now...
-
New #14
Different cables and different ports, got another crash.
-
New #15
Had a few more crashes this afternoon ( 3 in the last hour). Full freezes, for a couple minutes then power off. No minidumps though.Last edited by annoyboye; 22 Jun 2014 at 22:03. Reason: Had mentioned a full dmp, but noticed it was days old
-
New #16
Got a dump this time. So many crashes tonight.
-
New #17
Both the new BSODs are stop 0xF4.
It is a storage related issue, which continues.Code:BugCheck F4, {3, fffffa800a179b30, fffffa800a179e10, fffff800037c4270} ----- ETW minidump data unavailable----- Probably caused by : csrss.exe Followup: MachineOwner ---------
At this point I would suggest you to RMA the SSD.
-
New #18
Bad News
So, I sent off my sdd for a replcement, got the new one in.
First night with it, got another BSOD. Would love you guys to take another look if possible. Thanks.
-
New #19
Can you uninstall avast, as a test?
Uninstall Avast using Avast Uninstall Utility. 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.
Let us know the result.
-
New #20
I actually uninstalled Avast a little before your post and have not had a crash since. I will give it a couple more days, but I think this might be solved.
Quote
Related Discussions