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 running Verifier: FLTMGR.sys Stop error 0x000000D3 and more

13 Nov 2013   #1
MrSnuff

Windows 7 Professional x64
 
 
BSOD running Verifier: FLTMGR.sys Stop error 0x000000D3 and more

Hello SF

While I always get BSOD running verifier; and it usually stalls on fltmgr.sys with error code 0x000000D3, this is not the only issue.

I was getting about 3 BSOD a day for various reasons so I finally decided it was time to get serious. Up till then I had done some of the usual things like clean boot, running ccleaner, doing complete antivirus, antimalware, antispyware scans.

I found various topics here and so tried running verifier. It always stalled on fltmgr.sys.

I could not believe it would be my RAM since it is fairly new and I was having similar problems before I replaced all my RAM and reformatted my hard drive. I ran windows memtest with no errors.

So here is what has changed since this all began about 6 months ago:

1. New ssd hard drive

2. clean load of win7 on ssd. HD used for files only.

3. New RAM

4. Working fine till I updated Nvidia for graphics card.

5. Tried to roll it back; didn't work. Kept up with updates over a period of months having read of others having issues and figuring they might come out with a fix that might help me. No joy so far. I found that disabling nvidia services lets the drivers continue to work and slows down the BSODs. I also tried putting in a Radeon card poached from another computer to see if that would make a difference. It didn't.

6. Read somewhere it was Nvidia audio drivers. Removed them, but they always came back even when I thought I had completely removed them. So I disabled them instead and updated realtek drivers. They are now gone but nothing is fixed.

7. better but still regular BSOD.

8. tried (again) a clean boot; slowly introduced start up and services over a period of days. Not too many issues till I tried to play CoD Ghosts. Played around with settings (way below what they should have been) and it worked for a while. Now it stalls on load every time and gives a fatal error.

9. I figured it had to be hardware. The only new piece is a Rosewell USB/SD Card/DVI box. I unplugged it all. No joy. However when I plugged it and the old pre-installed FUSB box back in after a few days I was getting a USB device not recognized. tried disabling, but that did nothing. So I unplugged the old one and since then the unrecognized USB message has gone. Has not fixed the other issues though.

10. Found my way here again. Ran verifier. Stalled every time on fltmgr.sys. Had to safe boot to reset.

11. Bit the bullet and ran memtest86. 17 hours later and over 3M errors I stopped it because I saw a pattern emerging on the errors. Always on the same two GB ranges. Pulled all but one stick. Ran memtest86. Multiple errors. Changed slots. Same thing. Changed slot, same thing. Ok most likely the RAM. Tried the second stick. Same thing again! I expected the errors to be either stick one and two or slot one and two, so I am not too worried. Sure enough, the third stick worked fine in slot three. So now I know i have one good stick and one good slot for sure. Tried it in all four slots and error free. Repeated with stick 4.

12. So the result is two bad sticks of RAM. I was pleased because I thought I had isolated the problem. Put the two good sticks into slot 1 and 3 and powered up into Win7. All good. Ran verifier; reboot: stalled again with BSOD on fltmgr.sys. I couldn't believe it.

13. Tried switching RAM slots to 2 and 4. Same thing again.

14. Tried setting it up for clean boot and running verifier; same thing again.

I have searched in vain for advice on causes or fixes of flytsys.mgr.

The actual error is: "mistakenly marked a part of its image pageable instead of non-pageable" and the stop code is 0x000000D3.

I ran the SF diagnostic tool and have attached the zip.

If any body has any suggestions short of another reformatting, I would really appreciate your input.

Thanks,

Dave


My System SpecsSystem Spec
.
14 Nov 2013   #2
MrSnuff

Windows 7 Professional x64
 
 

So I tried re-installing windows. Not a clean install but an 'upgrade'. I am not sure anything was even installed since obviously the updated version is newer than the original disk.

Verifier still blue screens on fltmgr.sys.

No random BSOD during normal operation so far, so that's good.

Still stalls loading CoD Ghosts.

Any ideas welcomed.

Thanks
Dave
My System SpecsSystem Spec
14 Nov 2013   #3
YoYo155

Windows 10
 
 

Welcome to SF .

Seeing that you formatted and reinstalled Windows the previous file uploaded is irrelevant.
Please follow the Blue Screen of Death (BSOD) Posting Instructions and upload an updated version.
My System SpecsSystem Spec
.

14 Nov 2013   #4
MrSnuff

Windows 7 Professional x64
 
 

Thanks for the welcome.

Here is SF diagnostic results.
My System SpecsSystem Spec
15 Nov 2013   #5
YoYo155

Windows 10
 
 

Thanks for the files . No dump files are present in the folder, have you experienced any?
You can manually check the minidump folder.
Code:
C:\Windows\minidump
If dump files are present in that folder copy them to the Desktop, zip and upload in your next post.
My System SpecsSystem Spec
15 Nov 2013   #6
MrSnuff

Windows 7 Professional x64
 
 

I have not had an actual BSOD since I removed the duff RAM and 'upgraded' windows. However when I run Verifier I do get BSOD on fltmgr.sys. This happens every time until I do a verifier reset.

Is this anything I need to worry about?
My System SpecsSystem Spec
15 Nov 2013   #7
YoYo155

Windows 10
 
 

Yes, a healthy system should be able to sustain DV enabled with any major issues.
What settings did you enable and which drivers did you choose for DV to checkup on? - This is important.
My System SpecsSystem Spec
15 Nov 2013   #8
MrSnuff

Windows 7 Professional x64
 
 

I chose: "create standard settings", next, "Automatically select all drivers installed on this computer".
My System SpecsSystem Spec
15 Nov 2013   #9
YoYo155

Windows 10
 
 

That is the problem.
To enable Driver Verifier the most efficient (system resources wise) and least prone to false positives
way the settings needs to be different. I can link you to a tutorial on how to do just that
but I don't think you need to.
Seeing that you're only getting BSOD's when enabling Driver Verifier on a Windows component,
which you don't need to do.

Work with the PC for a week or so and if you're continue getting BSOD's report back .
My System SpecsSystem Spec
15 Nov 2013   #10
MrSnuff

Windows 7 Professional x64
 
 

sure thing. I will let you know re the BSOD. So far so good, though I have not stressed my rig much. Also I will reinstall the nvidia package rather than simply the drivers. That seemed to cause issues (ie BSOD) before so it will be interesting to see if that is solved.

Do you think any of this is related to the fact I can no longer play CoD Ghosts without a hang and "Fatal Error" message? Clearly there is something still not right.
My System SpecsSystem Spec
Reply

 BSOD running Verifier: FLTMGR.sys Stop error 0x000000D3 and more




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD from nvlddmkm (running verifier) when trying to open GeForce Exp
Hi all, Sorry in advance for the long and rambling post, but I've tried a few different sets of settings with driver verifier in an effort to pinpoint the problem, but I'm not at all experienced in the nitty gritty aspects of debugging BSODs. I'll try to explain the origin of all of my earlier...
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, computer idling with driver verifier running
Have had problems with bluescreens and whocrashed told me it was most likely caused by some driver. Turned on verifier after your guide and it crashed after I went to bed..
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 after running driver verifier.
My laptop is ASUS x42j series and has been used for more than 2 years. It did ran just fine up until 2 days ago when it started freezing with color dots and patterns on the screen. I did a Regcure Pro scan and fix most of the errors as well as trying the driver verifier run to detect the failure....
BSOD Help and Support
BSOD: stop error while running specific programs, I moved recently?
Consistently happens when running Hold Em Manager 2 + Pokerstars. Without using those two programs it appears to never crash and I can leave it running constantly. But I need those two programs for my life!!! They are not graphical games but HM2 can be very processor intensive. It often happens...
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 14:03.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App