Bootvis - blank screen after windows loading screen

[Force Flow]

I figured I'd give bootvis a try on my gaming rig since I don't have it on all the time, and only fire it up if I want to play something.

So, according to this quick guide: http://articles.techrepublic.com.com...1-5034622.html

It suggested a File > New > Next Boot + Drivers Trace

After asking for a reboot, the rig rebooted, and went all the way up to the point where hit hit the windows loading screen. As normal, it sat there for a while with the bar going, then went blank. So, I left it alone for about 40 minutes or so before I went back to check on it.

It was still sitting there blank.

I had to reboot and do an F8 to get it to load the last known good configuration before I could get back into windows.

So, I went ahead and tried it again, except this time, with an autologin. Same result, and I had to go hit F8 again.

So...have any of you had success with bootvis and/or have you see this issue? The suggestions I've found related to this issue imply that there is a hardware/software issue, however, this does not appear to be the case, since bootvis is the only new factor here. I'd like to see if we can get a confirmation about whether or not this should be added to the toolbox of accepted utilities, or added to the banned list.

[Negeva]

Bootivs was removed from the M$ site due to these sort of problems. I stopped using it after a few failed attempts.

If possible, try booting into Safe Mode and do a System Restore. Last good config just replaces the registry and not any system files - which bootivs will no doubt have messed up.

[Force Flow]

There were no adverse affects after bypassing what bootvis loaded in the startup procedure. The machine worked fine after booting with the last known working settings, so no need for safe mode or system restore.