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

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

Thanks for the welcome.

Here is SF diagnostic results.

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?

I chose: "create standard settings", next, "Automatically select all drivers installed on this computer".

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.