Random BSOD - error 1E

tgmorris99 · 01 Oct 2014

The SSD FW is current according to Samsung Magician.

I burned the Seatools iso to a CD and it boots but even after changing the controller mode to IDE it still winds up on a blank screen after all the other text appears. Is it worth running the Windows version of the tool?

All the Windows updates are successful other than KB2861208, which a lot of people report as failing. I tried it as a standalone install and it also gets the error as "not applicable" or being blocked by something else. I also tried using the Update Readiness tool and it reported no errors so perhaps it (KB2861208) really doesn't apply to the version of .NET I have installed as it (4.5) came from the Gigabyte website. I guess I could uninstall it and let it download.

ETA: I ran the Seatools for Windows short tests on my 2 HDD and everything was a Pass as was the SMART results.

essenbe · 01 Oct 2014

No, it's just the error I was getting came from a Windows Update and all of the indications so far have been storage related, or hard drive related. So, if you can't get Seatools to run from DOS, use the Windows installer version. The DOS version will just give a better test because the hard drive is not in use when you are testing it, but the Windows version will do OK.

What I actually got was

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff8800158a313, 0, 706}
Probably caused by : hardware ( fltmgr!CleanupStreamListCtrl+23 )
Followup: MachineOwner

which is Microsoft Filesystem Filter Manager

If you recall, earlier I got iaStor which is the AHCI controller of your hard drives. Everything is revolving around the hard drives or the file system errors.

You may want to run Check Disk also Disk Check

tgmorris99 · 02 Oct 2014

OK. I'll do a longer check tonight. In the meantime here's yet another failure right after being awakened to do a nightly backup. BC = 50.

tgmorris99 · 03 Oct 2014

So I had yet another BSOD when a backup was scheduled and I've attached that dump.

I've also just put in a new 2TB HDD to replace the 2 separate drives I was using so we'll see if that helps things even though both drives passed all the Seatools tests.

essenbe · 03 Oct 2014

I couldn't find much in the dump files. All references were to Page File, Filter manager and NTFS file system and I/O Procedures, which are normally hard drive/storage related. Either that or ram.

tgmorris99 · 03 Oct 2014

I guess we'll see what happens tonight with the new HDD. The pagefile is on the SSD so hopefully that's not the problem. I'll let the computer wake up tonight to do the backup of the new drive and see how things go. If that works I'll run the verifier again for a couple of backup cycles to see if it catches anything. With any luck the new drive will have solved the problem even though the old drives never had any issues with the old mobo.

ETA: I see you were talking about possible issues when using rapid mode - which I have enabled on my 840 Pro... just wondering if that could be the problem?

essenbe · 03 Oct 2014

Am I wrong that most of your problems have been with your WHS backups and waking from sleep? The page file on the SSD should not be a problem at all. I have 8 SSDs and they all have the Page File on them with no issue.

tgmorris99 · 04 Oct 2014

The last couple of dumps seems to be related to finishing the backup or shortly thereafter. I only mentioned the SSD as you had mentioned possible issues with Rapid Mode.

I'll let things run with the new HDD for a couple of days and just see if things have magically been fixed by the newer drive.

essenbe · 04 Oct 2014

Just to test, if you have problems with the scheduled backups, could you try to run them manually when your computer is not sleeping, just to see if that may be a problem?

tgmorris99 · 08 Oct 2014

I don't want to jinx anything but things have been running OK since I swapped in the new HDD in place of the 2 older drives even though they passed all the tests. One difference is that the older drives were SATA 2 while the new HDD and the SSD are SATA 3. While that shouldn't matter it looks like things may be working - but it's only been 2 days since my last reboot.

The next step (tomorrow) is to add in the media hub to the mix and see if that works now too. If that hangs together then I'll consider this solved.