Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD on fltmgr.sys

10 Jun 2010   #1

windows 7 64bit
BSOD on fltmgr.sys

Hiii guys
im getting strange problem here,
im getting blue screen and it come also with very strange noise from the pc,
and the strange thing that it happened when i play battlefield.
i tried to play with other games (not multiplayer) and its good

i searched on log and found the problem but i didnt find the answer to fix that :\

 bug check code: 0x00000101
caused by driver: fltmgr.sys
caused by address: fltmgr.sys+fd5a
i already tried to update all drivers,
changed the bios,
run checks on memory, hardisk and video card >>> all seemed to be good
disabled my anti-virus and firewall (bitdefender total security)

 System info:
OS: windows 7 ultimate retail  x64 (64 bit)
cpu: I7 920  @ 2.67 GHz
Video Card: HD 5770 Radeon 1 gig memory ddr 5
Memory: 6 GB 1600 GHz
Motherboard: X58A-UD3R  (Gigabyte)
Power Supply: Chieftec 650 W
the pc is brand new and i have him less than a month

My System SpecsSystem Spec
10 Jun 2010   #2

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install

Follow these instructions and you will be helped.

Based upon what you have said there is a conflict with the game and the OS. If that is true the remedy will be not to play the game. But post the dump and we shall see.
My System SpecsSystem Spec
10 Jun 2010   #3

windows 7 64bit

My System SpecsSystem Spec

10 Jun 2010   #4

64-bit Windows 8.1 Pro

The analysis of your .dmp file was inconclusive, however, it shows that Battle Field Bad Company was the process that was running at the time of the crash. Does you system crash only when playing this game?? If so try uninstalling it, then do a fresh install and see if your crashes stop.. Sorry that we cant be more conclusive than that..

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\060810-139683-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e4ae50
Debug session time: Tue Jun  8 06:03:08.190 2010 (UTC - 4:00)
System Uptime: 0 days 13:53:33.140
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff88003163180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner

0: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003163180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

Debugging Details:






fffff880`0b5518b8 fffff800`02c2b443 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`03163180 : nt!KeBugCheckEx
fffff880`0b5518c0 fffff800`02c85cf7 : fffff880`00000000 fffff800`00000002 00000000`00002711 fffff880`0b551b60 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff880`0b551950 fffff800`031f3895 : fffff800`03218460 fffff880`0b551b00 fffff800`03218460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0b551a50 fffff800`02c79af3 : fffff880`009b1180 fffffa80`050b8060 fffff880`0b552040 fffff880`014c4764 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0b551a80 fffff800`02c825d0 : 00000000`00000002 fffffa80`06020f20 00000000`506c305d fffff800`02ca0a3d : nt!KiInterruptDispatchNoLock+0x163
fffff880`0b551c10 fffff800`02c5ccf9 : 00000000`00004e0e 00000000`00000001 00000000`00000000 fffffa80`050da420 : nt!KiDeferredReadyThread+0x7f9
fffff880`0b551c90 fffff800`02c5cf02 : fffff800`02df7e80 00000000`00000000 00000000`00000001 fffffa80`00000001 : nt!KiExitDispatcher+0xc5
fffff880`0b551d00 fffff800`02c8045b : fffffa80`050db330 00000000`a000000c 00000000`00000000 00000000`00000000 : nt!KeInsertQueueApc+0xa2
fffff880`0b551d60 fffff880`01418f30 : fffffa80`0b55b580 00000000`00000001 fffffa80`46068b10 00000000`00000000 : nt!IopfCompleteRequest+0xbdb
fffff880`0b551e40 fffff880`014cf913 : 00000000`00000000 fffffa80`46068e68 00000000`00000000 00000000`00000000 : Ntfs!NtfsExtendedCompleteRequestInternal+0x110
fffff880`0b551e80 fffff880`014d0408 : fffff880`0b552730 fffffa80`46068b10 00000000`7646744e 00000000`ffffff01 : Ntfs!NtfsReadUsnJournal+0xb52
fffff880`0b551ff0 fffff880`014aa5fa : fffff880`0b552730 fffff8a0`000ac6f0 00000000`506c3000 fffff880`00000101 : Ntfs!NtOfsPostNewLength+0xc8
fffff880`0b552080 fffff880`014bca07 : fffff880`0b552730 fffff880`0b552980 fffff880`0b552730 fffff8a0`09bad4e0 : Ntfs!NtfsCommitCurrentTransaction+0x22a
fffff880`0b552110 fffff880`014ab98b : fffff8a0`09bad3b0 fffff8a0`0b86dee0 fffff8a0`000ac6f0 fffff8a0`09bad3b0 : Ntfs!NtfsCheckpointCurrentTransaction+0x27
fffff880`0b552140 fffff880`01419aa9 : fffff880`0b552648 fffff880`00d8032e fffff880`0b552690 fffff880`0b541000 : Ntfs!NtfsCommonCleanup+0x135b
fffff880`0b552550 fffff800`02c8cd4a : fffff880`0b552690 fffffa80`078d7888 fffffa80`08ac9b00 fffffa80`08ac9020 : Ntfs!NtfsCommonCleanupCallout+0x19
fffff880`0b552580 fffff880`01419662 : fffff880`01419a90 fffff880`0b552690 fffff880`0b552900 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`0b552660 fffff880`014bb244 : fffff880`0b552730 fffff880`0b552730 fffff880`0b552730 fffffa80`05fd8c60 : Ntfs!NtfsCommonCleanupOnNewStack+0x42
fffff880`0b5526d0 fffff880`00d7f23f : fffff880`0b552730 fffffa80`054f5480 fffffa80`054f57d8 fffffa80`5a336af0 : Ntfs!NtfsFsdCleanup+0x144
fffff880`0b552940 fffff880`00d7d6df : fffffa80`05fa0890 00000000`00000000 fffffa80`05e17e00 fffffa80`054f5480 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0b5529d0 fffff800`02f949af : fffffa80`054f5480 fffffa80`42b14b30 00000000`00000000 fffffa80`090aef20 : fltmgr!FltpDispatch+0xcf
fffff880`0b552a30 fffff800`02f7a604 : 00000000`00000000 fffffa80`42b14b30 fffff880`0b552ca0 fffff800`02ef247c : nt!IopCloseFile+0x11f
fffff880`0b552ac0 fffff800`02f944a1 : fffffa80`42b14b30 fffffa80`00000001 fffff8a0`03581920 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`0b552b40 fffff800`02f943b4 : 00000000`00000d18 fffffa80`42b14b30 fffff8a0`03581920 00000000`00000d18 : nt!ObpCloseHandleTableEntry+0xb1
fffff880`0b552bd0 fffff800`02c7c853 : fffffa80`7f160b60 fffff880`0b552ca0 00000000`ffeaa000 00000000`00008000 : nt!ObpCloseHandle+0x94
fffff880`0b552c20 00000000`77b0ffaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0743e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b0ffaa



FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image




Followup: MachineOwner
My System SpecsSystem Spec
10 Jun 2010   #5

Win 8 Release candidate 8400

This bugcheck (101) is Usually caused by: Device driver, BIOS bug, hardware defect (see Significant Posts section below)..

For driver I would suggest driver verifier

For BIOS I would only update BIOS as a last resort.

For hardware you can use these to check what it means and what to try

Let us know if you need help

My System SpecsSystem Spec
10 Jun 2010   #6

windows 7 64bit

  1. Hii m8
    from what i saw its happened only in battlefield for now
    and i already tried to reinstall it again fresh and didnt work:\

    but what make the crash? the game dont support good on 64 bit?? and what i can try elsewhere
My System SpecsSystem Spec
10 Jun 2010   #7

windows 7 64bit

TNX ZigZag ill try what you suggested and will let you know the result
My System SpecsSystem Spec
10 Jun 2010   #8

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install

Go to windows compatibilty center, see what is said bout the game.
My System SpecsSystem Spec
24 Nov 2011   #9

Windows 7 Ultimate 64bit
BSOD flymgr.sys Playing Battlefield 3

I'm having the same issue with Battlefield 3. There must be a conflict with the Battlefield series games and something we are using.

Windows 7 Ultimate 64bit
Intel G620 2.6ghz
Gigabyte H67M-D2-B3
8GB Razor G.Skill 1333mhz RAM
120GB Seagate Barracuda SATA
XFX 6870 1GB Video
XFX 750 Core Edition PSU
NZXT Vulcan MicroATX Case
My System SpecsSystem Spec
05 May 2012   #10

Windows 7 Proffesional 64bit

I have a feeling i know the conflict i recently changed from ESET to bitdefender played battlefield and it started BSODing on me i did everything from reset button to chkdsk . so ill uninstall bitdefender and tell you if it works
My System SpecsSystem Spec

 BSOD on fltmgr.sys

Thread Tools

Similar help and support threads
Thread Forum
BSOD for fltmgr.sys
I have only had 3 BSODs in recent memory, but they have all been in the last month. Two of them happened when the computer was unattended, but the last one briefly flashed on screen and I could read that it was related to fltmgr.sys. 2 out of the 3 crashes occurred in the last 3 days. The only...
BSOD Help and Support
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...
BSOD Help and Support
BSOD ntoskrnl.exe (nt+0x75C40) & fltmgr.sys (fltmgr+0x22751)
The BSODs do not seem to happen at any specific time. The computer is an HP with a Pegatron 2A86 Mobo. I plan on running MemTest86 and will have images uploaded tonight. For now, here are my WhoCrashed logs and (attached) is the SF files. Thank you in advance for any help. My...
BSOD Help and Support
BSOD - the 1st FLTMGR.sys
Acer Aspire AM3970-U5022 - 64-bit, I was not doing anything at the time, put the PC to Sleep, about 2 hours later, awakened the PC, and BSOD occurred coming out of sleep, this is the 1st time. Acer is a yr old, no hardware added or removed, as OEM as possible. Thanks, Doc
BSOD Help and Support
WIN 7 64 Pro FLTMGR.sys BSOD
Hello, I joined these forums because I have grown extremely tired of the BSOD's The problem didnt start Until after a windows update 2 weeks ago, 1 update failed but still installed causing a BSOD, prior to this I had System Restore on after however it was off with all restores wiped. since then I...
BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 20:53.
Twitter Facebook Google+