BSOD 0x0000007E, fltmgr.sys

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows7 professional K Service Pack 1(64-bit)
       #1

    BSOD 0x0000007E, fltmgr.sys


    My PC went to blue screen 3 times recently, i missed the first & third one but second was 0x0000007E & fltmgr.sys

    2nd BSOD : I was playing "Heroes of the storm"(one of Blizzard games) when 2nd BSOD happened.
    3rd BSOD : I clicked mouse button to wake up my computer during sleep mode. And there was no signal in my monitor(black state) so I restarted my computer by reset button. After then I found a new minidump file.

    My windows version is Windows 7 professional K Service Pack 1 (64-bit).
    I ran memtest86+ & sfc /verifyonly & chkdsk but there was no error.

    Please identify the cause from the BSODs
    OTL

    Any help would be appreciated.
    Thanks,
      My Computer


  2. Posts : 7,050
    Windows 10 Pro
       #2

    Please run the DM Log Collector tool again and upload a new zip file, the current attached zip file misses some important files.
      My Computer


  3. Posts : 6
    Windows7 professional K Service Pack 1(64-bit)
    Thread Starter
       #3

    I ran DM Log Collector tool again & attached new zip file in this reply.
      My Computer


  4. Posts : 7,050
    Windows 10 Pro
       #4

    Unfortunately the zip still misses some files, try following below.



    Diagnostics Test

     System File Check


    Please try following:
    • Open an admin command prompt
    • Copy/paste "sfc/scannow" (without quotes) and press enter
    • When it finished reboot your system
    • Open again an admin command prompt
    • Enter sfc/scannow again

    If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
    System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

    If sfc/scannow says no problems were found, try running the DM Log Collector again.
      My Computer


  5. Posts : 6
    Windows7 professional K Service Pack 1(64-bit)
    Thread Starter
       #5

    I ran sfc/scannow command twice as you said and no problems were found
    So I ran DM Log Collector again and here is the result

    If there are missing files in this zip, please let me know what files missed
    I try to find out the files in my computer

    Thanks
      My Computer


  6. Posts : 7,050
    Windows 10 Pro
       #6

    Run this file as admin and see if that helps with it.
    Attachment 384155
      My Computer


  7. Posts : 6
    Windows7 professional K Service Pack 1(64-bit)
    Thread Starter
       #7

    This is the log file made by your DM_Log_Collector.bat
      My Computer


  8. Posts : 7,050
    Windows 10 Pro
       #8

    Very odd, only the size is growing but not the amount of files. We'll have to do it without them, but we need 1 missing file at least.
    An important file that is necessary is msinfo32.
    Please try following
    Press Windows key + r and enter "msinfo32" (without quotes)
    Save a file as msinfo32.nfo, locate this file in Windows Explorer, right click the file > copy to (or send to) > zip and upload the zip
    Attachment 384160

    Because I can't check your system information, I don't know if your system is up to date and it is important to have a system up to date with Windows Update because of stability, performance and several other reasons including fixes for BSOD's.

    Please update your BIOS to version F7.
    GIGABYTE - Moederbord - Socket 1150 - GA-H97-Gaming 3 (rev. 1.0)
      My Computer


  9. Posts : 6
    Windows7 professional K Service Pack 1(64-bit)
    Thread Starter
       #9

    Here is the msinfor32 file.

    I'll try to update my BIOS as you recommended.
      My Computer


  10. Posts : 7,050
    Windows 10 Pro
       #10

    I have looked a bit through the msinfo32 file, please remove Daemon tools. Daemon tools uses several drivers which are known for being very unstable because they are improper coded.

    Is your Crucial MX200 firmware up to date?
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 21:25.
Find Us