BSOD - the 1st FLTMGR.sys

[Firedoc]

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

 

[FredeGail]

Hello Firedoc and welcome to Sevenforums.

BSOD Analyse

Have you installed any new software, hardware or drivers recently? Plugged in any device such as a webcam, keyboard etc.?

Problem Devices

Officejet 6000 E609a    ROOT\MULTIFUNCTION\0000    This device is disabled.

This device is disabled.

Troubleshooting

Looking at your bugcheck it's likely that a memory corruption event was triggered. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors.

   Warning

:info: Note that the below instructions may break your WARRANTY rules. If you're unsure check manuals, separated warranty papers, stickers on computer for secure permission.

To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

BCCode APC_INDEX_MISMATCH

This bugcheck is quite new to me, a broken Windows 7 or drivers are being pointed.

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them.  A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: fffff8800124beb0, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 0000000000000002, Thread->KernelApcDisable
Arg4: 0000000000000001, Previous KernelApcDisable

SFC /scannow

We usually ask people to do this command to check if Windows is corrupted. It's the most common used one to check if the Windows files are corrupted. If it'll find errors, it'll restore them.

   Tip

If you're having a custom customization layer on your Aero, it's likely to get restored to default.

Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Best Regards,
Frederik.

 

[Firedoc]

Hi FredeGail and thanks, as I mentioned in my original post "Acer is a yr old, no hardware added or removed, as OEM as possible." The "Officejet 6000 E609a" is wireless, so yes to its drivers being installed, however that Printer has been connect since I booted the Acer for the first time when it was new.

And I did perform the Memtest86+ with no errors. I also run Chkdsk /f or SFC /scannow nothing found (CMD Run As Administrator) I also have 29 years experience using PC's, Windows, DOS, etc...and for some reason 3 other PC's running XP & Vista also received different BSOD. I also run Norton Security Suite, regular daily updates & scans, also Window's is set to Auto Update.

I even perform a Deeper Scan using Norton Power Eraser Tool. I have not placed this Acer in Sleep as before when this happened the 1st and only time. So fingers are crossed that it was a Glitch never to repeat itself. I do have connected an APC, PowerChute with most current update. I am very Security aware and conscious of all my 6 PC's I run, which are networked using Linksys E3000, also Firmware current.

Have I left anything out? Thank you, Doc

 

[FredeGail]

Hello again Doc. No, I believed you covered everything.
Therefore, I think it's time for a new procedure.

Driver Verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature) - and create a System Repair Disc (Win7) if you don't have a full installation DVD.
You can do this by going to Start...All Programs...Maintenance...Create a System Repair Disc (don't forget to test the disc to make sure it works).

For Vista, you can download the repair discs from different websites. If unable to locate them, shoot me a PM and I'll point you to them.
For Win8, BSOD's are different - and we'll have to adjust how we do this with them.

Also, to ensure that you can recover, here's another couple of additional steps:
- Get to the Safe Mode menu (rapidly tap F8 just before the Windows splash screen comes up). Scroll down to and select "Disable automatic restart on System Failure"
- Get the RED information from this picture (in particular we will need the name of the file that the error occurred in):
Picture of a BSOD

Then, here's the procedure to run Driver Verifier:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Best Regards,
Frederik.

 

[Firedoc]

Thanks FredeGail/ Frederik, I have your instructions copied and saved. I have not encountered the BSOD for [FONT=&quot]1st FLTMGR.sys [/FONT][FONT=&quot]as I have not placed this Acer PC in sleep mode since the first time this occurred.

I appreciate your quick response, knowledge and experience...as with most all new PC's, they do not come with any Installation Disks, and yes I create a System Recovery Disk for each PC. Any time I make changes, add hardware or install software, if not automatically done, I create a Restore point by date & time.

As with the following, I have had nothing but problems with this Officejet 6000, as I installed it as a wireless printer. And on occasion, it may not wake and then when I try to connect, I power it off and back on or re-boot my PC. And when I run Norton's Diagnostic Report or HP Printer Diagnostic Tools, is when I learn that the HP Officejet 6000 shows up as [/FONT][FONT=&quot]
[/FONT]Officejet 6000 E609a ROOT\MULTIFUNCTION\0000 This device is disabled.[FONT=&quot]
Diagnostic Tool Option follows

HP Print and Scan Doctor : Diagnoses and resolves many printing, scanning, and connectivity problems.

HP Windows 7 Printer Install Wizard : Automatically finds and installs the best Windows 7 printer driver for your product.

HP Hardware Diagnostic Utility : Helps resolve common hardware-related issues.
[/FONT]
And now I am not getting the Disabled message, as the Printer woke up.

Again, thank you for the great in depth procedures, Doc