BSOD, windbg say caused by fltmgr.sys (fltmgr!FltpDispatch+72)


  1. Posts : 6
    Microsoft Windows 7 Ultimate X86
       #1

    BSOD, windbg say caused by fltmgr.sys (fltmgr!FltpDispatch+72)


    Hi all.
    I had a BSOD today, but it's not the first.
    I'm uploading the files, tried inspecting with winDBg but I have only two dmp files (cleared all few weeks ago):
    The one from 09/08 says it's win32k.sys and the one from today says it's fltmgr.sys.
    Tried using BlueScreenView, but no real information there (or I missed something).
    Would be happy to learn how you get the right info from all those logs.

    I'm attaching the rar file, hope someone could help :)
    Thanks a lot.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hello ronlut.

    A fltmgr.sys error may be caused by a large range of factors, and one of them is the storage controller. And in your case it is the issue I am thinking.

    Your Storage controller in use (RAID /SCSI mode) is NVIDIA nForce Serial ATA Controller, nvstor.sys; which is way old.
    Code:
    fffff880`00cc0000 fffff880`00ceb000   nvstor     (deferred)             
        Image path: \SystemRoot\system32\drivers\nvstor.sys
        Image name: nvstor.sys
        Timestamp:        Sat Mar 20 02:15:11 2010 (4BA3E257)
        CheckSum:         000291A5
        ImageSize:        0002B000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Updates are necessary. I dont know any right source to update it, you may search in your computer manufacturer's wabsite (GBT NVDAACPI).

    At the same time, as the fltmgr.sys may be blocked by an antivirus program's filter manager driver, I would suggest you to uninstall AVG. 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.

    Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

    • Double click to open it.
    • Click this button only:
    • If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

    Some problems are there in the display driver, too. It is also failing.
    Code:
    fffff880`0b3636a8  fffff880`079a7df0Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
     nvlddmkm+0x758df0
    And teh driver in use is known to be buggy.
    Code:
    fffff880`0724f000 fffff880`07cf6000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Fri Jan 18 18:52:15 2013 (50F94C87)
        CheckSum:         00A92B69
        ImageSize:        00AA7000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Install the 314.22 WHQL only.

    • Uninstall All nvidia items in Control Panel > Programs and features
      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


    But you have to pay attention to update Nforce at first. At the same time, plan to update the BIOS too, if possible.

    Code:
    BIOS Version/Date    Award Software International, Inc. F9, 25/06/2007
    I would request northernsoul55 to add his suggestions too; as he has deeper insight about nforce.



    Let us know about your tries.
      My Computer


  3. Posts : 6
    Microsoft Windows 7 Ultimate X86
    Thread Starter
       #3

    Thanks a lot for the detailed answer.
    1. About NVIDIA nForce Serial ATA Controller, I found this:
    Should I install this? The date is even earlier than what you stated as installed currently.
    Also, tried updating from device manager but as I thought it said it's the latest driver.
    2. About the graphics driver, I will update.
    3. About bios, I found this:
    Should I update to F11C? It says beta, but it's from 2009 and I can't find newer version.
    Mine is F7 as you said, from 2007. Which one you think is safer? F11C or F10?

      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    You may apply the BIOS, but not the storage controller, as it is older than that is already installed.

    See if the BIOS update changes anything; otherwise we have to plan to omit nvstor from there.
      My Computer


  5. Posts : 6
    Microsoft Windows 7 Ultimate X86
    Thread Starter
       #5

    By the way, is there any explanation for why to uncheck all those features in the nvidia installation?
    (3d vision contoller, 3d vision driver, hd audio driver, nvidia update)
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Mostly we dont use those stuff. What you need there in the display driver is the display driver itself and the physX. So it is better to not include the unnecessary and problematic parts.
      My Computer


 

  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 18:40.
Find Us