PerfectDisk 11 Boot Time Defrag BSOD caused by mbamservice.exe

[siliconman01]

Users of PerfectDisk 11 and MBAM realtime on Windows 7 x64 and x86 may encounter a BSOD at the time PerfectDisk 11 begins a Boot Time defrag on system reboot. There is a conflict between PerfectDisk 11 Boot Time defrag and mbamservice.exe.

To correct this issue, a manual registry modification needs to be made. At HKLM\SYSTEM\CurrentControlSet\services\DefragFS\Parameters, add mbamservice.exe to the BlockedFileList Multi-SZ list.

Raxco has been contacted and is updating their expanding list of blocked files. Note that this blocks the service from loading at the time the Boot Time defrag is being performed. Once the Boot Time defrag is completed, PerfectDisk restarts the Windows load and mbamservice.exe will start up as needed.

[AdvancedSetup]

I've ran this with version 10 and did not have this issue. I will see if I can get an update and test with version 11

[siliconman01]

I've ran this with version 10 and did not have this issue. I will see if I can get an update and test with version 11

On my Windows 7 x86 Professional system with PerfectDisk 11 Professional and MBAM V1.44, the system will BSOD on every boot time defrag unless this BlockedFileList fix is applied. Raxco acknowledged the issue as well.

[AdvancedSetup]

I'm running x64 - I will try to run and confirm tonight or tomorrow if I have time.

Thank you for reporting it.

[jackbrennan2008]

I'm running the Perfect disk 11 beta on windows 7 X64 and i have not encountered the same problem. I ran a boot time defrag on both my wife and my own PC last night and they both completed successfully.

[AdvancedSetup]

Well that actually could be a dangerous BSOD. There should be a copy of the MFT - but if it was corrupt or other disk problems and you got a BSOD during a file move operation (though its not supposed to be completed until it gets a commit call) its quite possible that you could then corrupt the MFT and make repair quite difficult.

If true then Raxco needs to do something to fix it or make a work-around that is part of an update. Looking at their site I didn't see an obvious post about this but did see quite a few with hangs, etc, but that's not the same as a BSOD

[siliconman01]

You can see other files that PerfectDisk boot time defrag blocks at the knowledge base article below.

http://www.perfectdisk.com/support/kb/823

I had this same issue with PD 10, Vista x64 Professional, and with SuperAntiSpyware Pro prior to upgrading to Windows 7 x64. You will see SAS in the list of blocked programs in the article above for PD 10. In PD 10, this BlockedFileList had to be user installed. In PD 11, the PD installer automatically adds this list to the registry.

With PD 11 and MBAM real-time, it did not occur on my Windows 7 x64 Professional computer but did on my Windows 7 x86 Professional computer.

Note that until 08-March-2010, I was running the free MBAM on both systems. No issues occurred between PD 11 and MBAM. I licensed both computers on 08-March-2010 and activated MBAM protection. That's when the PD 11 Pro boot time BSOD started occurring on the Win 7 x86 system. The BSOD occurs (100% repeatable) at the very beginning of the boot time defrag before PD 11 starts any file moving.

From everything I have heard/read, this is an unpredictable event. It occurs on some computers and not on others.

[jackbrennan2008]

If you untick the box (Forget the name at work at the moment) 'to automaticly restart the PC after a blue screen' under advanced system options it could be valuable to know exaclt what the BSOD is saying.

I only have Mbam resident protection enabled and SAS is just scheduled to run a scan every now and again. Do you have both Mbam and SAS resident protection enabled?

Have you E-mailed Raxco about this? or if you were in the beta lodged a Bug report with them?

As Advancedsetup pointed out we could have alot of people with unbootable PC's because of this bug !

[siliconman01]

If you untick the box (Forget the name at work at the moment) 'to automaticly restart the PC after a blue screen' under advanced system options it could be valuable to know exaclt what the BSOD is saying.

I only have Mbam resident protection enabled and SAS is just scheduled to run a scan every now and again. Do you have both Mbam and SAS resident protection enabled?

Have you E-mailed Raxco about this? or if you were in the beta lodged a Bug report with them?

As Advancedsetup pointed out we could have alot of people with unbootable PC's because of this bug !

I do not have SAS realtime protection enabled along side MBAM realtime. On my Windows 7 x86 Pro computer, only NIS 2010 is active with MBAM Pro; on my Win 7 x64 only Avira Premium Security Suite V9.0 is active with MBAM Pro.

Raxco was notified and confirmed the issue. They are adding mbamservice.exe to the BlockedFileList of files. My PD 11 Professional is not beta. I got an early final release because I have Raxco's extended support service. PD 11 is suppose to be released 09-Mar-10 to the general public.

[jackbrennan2008]

I think it is being released in a few hours or at least it should be. I live in Norway so i would guess it has to be the 9th in America some time soon. It is here .

Anyhow is that blocklist something i have to download in addition to the PD 11 software? I might as well install it right off the bat to save any conflict that might arise with the Mbam software!

[siliconman01]

As I said, in PD 11 the BlockedFileList is installed automatically when you install PD 11. HOWEVER, it may not contain mbamservice.exe yet because Raxco just learned of this yesterday.

[AdvancedSetup]

I can see why it happens but it should not be creating a BSOD (ie.. an unexpected hard crash) from what I see in that article it typically either shows a conflict or just hangs which is a lot safer and very unlikely to cause any real booting issues. There are many products that can load before the PD11 driver can get loaded to lock the drive and that is where the potential issue comes from.

I would not expect too much fallout from this as it appears to have been going on for a while now and has been known by Raxco.

Thank you though for reporting it.