Blackout Weirdness: FDISR Possible Source?

Has anyone experienced the following:

My PC generally takes 1 minute 10 seconds to fully boot.

However, some weird things have been happening since installing FDISR. Upon bootup, and only once in a while, after the initial black microsoft screen opens up, but BEFORE the light blue XP "welcome to windows" screen come on, there is an extended 2 or 3 minute black out on my monitor before that light blue welcome screen comes on.

It may have happened the next reboot after each time I did a snapshot or archive. But it's not limited to that. It happened the other day right after a BSOD (my first ever).

Any ideas? Any diagnostic recommendations?

 

Acronis True Image 11
SpySweeper 5.5.7.103
NOD32 2.70.32
Comodo Pro Firewall 2.4.18.184
Spybot 1.5 (though I don't know why as I don't run it)
PerfectDisk 8.0
And I have something called Recuva, a file recovery utility I've never used.

 

I had similar but more permanent problem here:
https://www.wilderssecurity.com/showthread.php?p=1099282#post1099282

Never did figure out why it happened. Good luck.

Acadia

 

are you using the freeze function ? The way FD-ISR works with freeze is slower than many other freeze programs - I believe that it has to check back with the frozen copy to restore the working snapshot. Following a session of great activity a re-boot might need more time ?

 

No Freeze. Still using build 205 with no Freeze function.

 

Freeze can cause a boot delay, but FDISR shows a popup menu that it is still busy, not an entire black screen. This is something else. I never had any of these problems, published at this forum. If FDISR was in trouble, it was caused by myself. A simple image restore and it was fixed.

 

Peter, Acadia, will check those links out and report back. Just found the "event viewer" and am reviewing all the "warnings" and "errors" in the System list. I'll post a screen shot later when back from meetings.

 

??
HDS version issues after changes ??

Looking forward to it

 

Just had what I THINK is a BSOD. For about 1/2 second, there was a blue screen with a lot of white text (like a DOS screen), but I couldn't read it because it immediately rebooted the system.

I've attached the system event viewer log...but it doesn't show any abnormality at the time of the "BSOD event" (6:46pm).

 

Attached is a screenshot of that Advanced Tab. Am I right in that you are suggesting to uncheck the "System Failure" / Automatically Restart setting? That would allow me to read the blue screen?

And if so, (inexperience about to show) would I just manually restart the computer with the button on the box?

 

Well fellas, it's been several days and no BSOD, but I can tell the system is still not right by that extended black screen pause at start up.

IF I was to uninstall FDISR to see if that changes the problem, do you recommend that I just use the standard Control Panel add/remove programs function? Or should I then ferret out FDISR folders, etc.

I have full intention of reinstalling the program. I've got my archived snapshot on the external hard drive, but I'm guessing that if the uninstall/reinstall fixes the problem, I would be doing new snapshots of the properly functioning drive.

Thanks,
Bruce

 

BSOD arrived on SATURDAY and this time I have it's message:

BAD_POOL_CALLER

---Make sure new hardware or software is properly installed
---Disable or remove new hardware or software

---Technical info:
xxx STOP: 0x000000c2 (0x00000007, 0x00000cd4, 0x00000000, 0x8a108c20)

End of blue screen writing
---------------------------------------------------------------------
Key points:

A. After my hard reboot on Saturday, the system booted just fine, taking its usual 1 minute to boot up. System worked fine.
B. However, the one anomaly that has sporadically shown up is a message that a USB device is not recognized, but I can't tell which one it is.
C. On today's boot up (Sunday), I got the long black screen delay. No message yet about a USB device not being recognized.

---------------------------------------------------------------------
Questions/advice needed on action steps:

1. My primary, secondary, and archived snapshots to my knowledge are identical. I can see the wisdom of backing them all up before uninstalling FDISR. How to I back up the primary and secondary to my external drive? Just do the same that I did to create the archived snapshot? And wouldn't that just give me the same archive?

2. What next step makes the most sense?
--- a. Leave FDISR uninstalled for a week or two and see if I get another BSOD or "device not recognized" issue without FDISR?
--- b. Reboot, defrag, then reinstall FDISR immediately and see if that cures my poor little PC's malady?
--- c. Other: _____________ (please explain)

3. Will my archive snapshot remember how I set up FDISR originally, including any preferences, what my exclusions are? How do I handle that when reinstalling?

Thanks for all the assistance! Is there any other info you need from me that would help with diagnosing the situation?

Peace,
Bruce

 

Been getting the BSOD's with a reference to Comodo v2.4 as the culprit. Comodo 3 is said to fix this but the Comodo forum is wrought with nightmares at this point on v3.

Rock and a hard place. Persistent BSODs or risk worse. Or dump Comodo but that isn't my preference. So I currently wait for a more stable v3 before installing.

Current, consistent, persistent BSOD (no longer getting Bad Pool):
DRIVER_IRQL_NOT_LESS_OR_EQUAL
0x000000D1 (0x0000001C, 0x00000002, 0x00000000, 0xB62043BB)
cmdmon.sys - address B62043BB base at B61FE000, Date Stamp 45bc9111

 

Chamlin, did you try this:

http://www.raxco.com/support/windows/kb_details.cfm?kbid=600

Good luck,
Acadia

 

Acadia, thanks for the link. Very important info (immediately below):


Article Title:Comodo firewall prevents FirstDefense from creating/updating snapshots correctly.
Article Details:Comodo firewall prevents its files from being copied by the FirstDefense-ISR copy process. The copy process will report errors with Comodo files. Snapshots are not bootable if the Comodo files fail to copy.

As a workaround, launch the Comodo application; go to the security tab and select advanced. Under the miscellaneous option, click configure and uncheck the option to "protect own registry keys and files from unauthorized modifications".

After this option is applied the Comodo files can be copied by the FirstDefense-ISR copy process safely and you will be able to boot into alternate snapshots.

Just did a snapshot last night without "unprotecting the registry keys" in Comodo, and the snapshot ran. But there were no errors that I know of.

How would I know if there were errors?

 

You can go into the FirstDefense Log, it will tell you EVERYTHING! Good luck.

Acadia

 

Log was clean. Thanks!

Still, have to deal with Comodo itself as it Blue Screens my PC every other day.

 

In the end, I ditched Comodo Firewall. Whatever I did, I couldn't get it work properly after following all the advices.
Any software that doesn't work together with FDISR is doomed and considered as good malware.