Eddy: Hardware / Software Engineer am I, please make no assumptions about my level of skill. 640x480 STILL exists as a failsafe in even windows 8, you just haven’t encountered it yet. And yes, can’t scroll the screen because the avast maintenance program is a full desktop application with no scrollbars and assuming a certain minimum screen size, thus, it’s a fail period regardless of actual screen real estate available.
The problem is that I permitted Avast to update, and on reboot, it was coughing up a blue screen with the following module at fault:
c:\program files\alwil software\avast5\ASWENGLDR.DLL
After several attempts at restarting the machine in different debugging modes, I figured that I needed to hit up safe mode, uninstall Avast, and see if I could get to desktop.
Hence the rant, the Avast update was causing the blue screen, but I couldn’t uninstall it to ensure that it was at fault and not something else.
Blue Screen Rule 1 was out the door: If an update is causing you boot problems, try uninstalling the update and see if you can boot.
I did manage to disable the avast engine while in safe mode, and rebooted again, and got another blue screen, this time from:
C:\WINNT\system32\drivers\sbhips.sys
That’s not part of Avast, that’s part of my firewall, what, why?
Regardless of whether or not Avast is tampering with my firewall, this particular module will not disable from the services module, so the only way I could get this to become “disabled” was to rename it while in safe mode. Which, after doing so, I was able to boot to the desktop.
Successful recovery from bad software update accomplished.
Step 2: Re-enable Avast and see if the blue screen caused by Avast went away.
Rude shock, can’t ENABLE Avast from services because of the protection scheme. Rather than booting into safe mode again, the Avast repair mode fixed that.
Scary time, reboot.
No blue screens.
Next step, enable firewall, nothing went boom, except while the firewall part of the firewall is working, it’s missing a component, however, it’s not a critical component because it’s part of the “Host Intrusion & Prevention System”:
“HIPS prevents attacks that reach vulnerable applications from succeeding by blocking any illegitimate behavior attempted by the affected applications.”
But that’s disabled because I’m on a router, so inbound packets only reach machines based on what port they’re on and so on, …