Random BSOD - error 1E

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.

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

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.

Code:

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

Code:

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.

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 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

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.