Solved Random BSOD - error 1E

[tgmorris99]

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]

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

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 http://www.sevenforums.com/tutorials/433-disk-check.html

 

[tgmorris99]

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]

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]

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]

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]

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]

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]

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]

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.

 

[essenbe]

That's great news. I would suggest that you take your time and add things slowly, testing each one. It will take much longer, but if you add something then start the hanging or crashing, you will know exactly what is causing it. But, good luck and keep us posted. I would really like to know. I hope things keep running well for you. Then once you feel like the problem is solved, please mark the thread as solved. Please keep us updated with your progress.

 

[tgmorris99]

After several days of running fine I decided to install the Renasas driver for the USB 3.0 PCIe hub on the media center. After two days I was getting some wonky results so I restored things back to before that install and things are stable again. Looks like the Renasas driver doesn't play nice with something so I sent back the media center and will get something that just plugs into the USB 3.0 header on the mobo.

I've marked this as solved as things are running fine w/o the addition of the media center drivers.

 

[essenbe]

Good job figuring out your problem. Let us know if you find other problems you can't figure out. Thanks for the feedback.

 

[tgmorris99]

Well, I jinxed things as I woke up to a reboot from a BSOD. While I was checking things it got another one so both are included in the attached. The first was around the time for the automated backup - which the server says completed OK.

 

[essenbe]

tgmorris99, It really seems that most of your problem has to do with your NAS and waking up from sleep. I have looked at your dump files and they seem to be showing pretty much the same thing as usual. Under most circumstances you would assume a bad hard drive or corrupted system files or something like that. But, in your case it seems to almost always be connected to your NAS and I'm almost out of ideas. There is what the dump file say.

fltmgr
start             end                 module name
fffff880`01598000 fffff880`015e4000   fltmgr     (pdb symbols)          c:\symcache\fltMgr.pdb\A008BBBF87CC421FA0E568076A16F4BA2\fltMgr.pdb
    Loaded symbol image file: fltmgr.sys
    Mapped memory image file: c:\symcache\fltmgr.sys\4CE7929C4c000\fltmgr.sys
    Image path: \SystemRoot\system32\drivers\fltmgr.sys
    Image name: fltmgr.sys
    Timestamp:        Sat Nov 20 03:19:24 2010 (4CE7929C)
    CheckSum:         0005452D
    ImageSize:        0004C000
    File version:     6.1.7601.17514
    Product version:  6.1.7601.17514
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     fltMgr.sys
    OriginalFilename: fltMgr.sys
    ProductVersion:   6.1.7601.17514
    FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
    FileDescription:  Microsoft Filesystem Filter Manager
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

That is the Microsoft Filesystem Filter Manager

MpFilter
start             end                 module name
fffff880`01260000 fffff880`012a2000   MpFilter T (no symbols)           
    Loaded symbol image file: MpFilter.sys
    Image path: \SystemRoot\system32\DRIVERS\MpFilter.sys
    Image name: MpFilter.sys
    Timestamp:        Wed Jul 09 21:43:06 2014 (53BDFDBA)
    CheckSum:         000425E6
    ImageSize:        00042000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Microsoft Windows AntiMalware protection system

I have asked someone else to come take a look. But, I still believe the problem seems to be between your NAS and Your computer. Correct me if I am wrong, but it seems to always be when the NAS decides to do a backup. One thing you may try, but I suspect wouldn't want to, is to go into your advanced power options and set your monitor to turn off whenever you want it to, but set sleep to never and hard drive to sleep never. That would keep your NAS from waking the computer from sleep. Plus, I think you said the NAS said the backup completed successfully, which I find hard to believe if it had a BSOD during the backup.

 

[Arc]

I want to add a little ....

Hi tgmorris99, can you uninstall/disable Samsung RAPID Mode as a test, just to see the situation when it is not present?

Will wait to see.

 

[essenbe]

I have one other suggestion. If you recall we uninstalled the Gigabyte Easy saver earlier in this thread, could you look for these 3 Gigabyte programs and see if you have them installed. If you do, please uninstall them and see if it helps. It has solved other's problems.

System Information Viewer
Cloud Station
App Center

 

[tgmorris99]

I want to add a little ....

Hi tgmorris99, can you uninstall/disable Samsung RAPID Mode as a test, just to see the situation when it is not present?

Will wait to see.

I'll disable this when I get back home.

I have one other suggestion. If you recall we uninstalled the Gigabyte Easy saver earlier in this thread, could you look for these 3 Gigabyte programs and see if you have them installed. If you do, please uninstall them and see if it helps. It has solved other's problems.

System Information Viewer
Cloud Station
App Center

I'm pretty sure they're not there but I'll check when I get back home. When I reinstalled everything this time around I did not use the system disk to do the install just the drivers I downloaded from the Gigabyte site and others like Intel, etc.

The backups (waking the system) worked fine for well over a year on the other mobo and h/w so it's definitely something with this combo of the new mobo and SSD as I'd had the SSD on the old mobo for a few weeks w/o any BSODs - though I don't recall if I'd enabled RAPID Mode on that setup or not. Since the problems seem to happen after the computer is awake and the backups start or complete I'm not sure what to think at this point.

For the time being I've enabled the verifier again to see if it catches anything.

In the spirit of only changing one thing at a time I'll leave the verifier on but disable RAPID Mode and let things cook for a few days.

 

[tgmorris99]

So I turned off RAPID Mode and don't have any of the Gigabyte programs in the "Installed" list. According to the WHS 2011 system the backup ran successfully last night but I again woke to a rebooted system after a BSOD. Interestingly, the time of the crash DMP file is earlier than the completion time of the backup and the clocks on both systems are within a few seconds of each other.

 

[Arc]

The raw stack of the crash dump flags various aspects like network, storage and ports. Really not a very healthy sign.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Scan the system for possible virus infection with the following programs only.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Will wait for the results, and the next BSOD. It is to see that how much of the flagged items can be removed. This process will lead us to the cause of the BSODs, as I am expecting.