hi stumppen,
Use of System Restore without first disabling the self-protection module within avast! can cause a similar issue. Reason is, avast! wakes up and finds itself in a different and new environment after restore is successful and complete and will not start because of that.
Did you use System Restore without disabling the self-protection module first?
In addition to running chkdsk (drive letter): /f/v using cmd within the Run box, run sfc /scannow from the Run box as well. You must allow sfc to complete the scan to repair broken system files or risk further corruption of the operating system. Do not cancel this scan once it begins. This sfc process will take a bit of time to finish; in XP you will need your installation cd disk for your cd drive when prompted to do so. EDIT: Please reboot your system after running sfc /scannow to activate and register repaired system files.
Running sfc /scannow will also repair any other corruption issues in operating system files caused by force-shutting (quit) your system down as you described you did due to the black monitor issues.
Avast had been working till this started happening 1-2 days ago. I have not had other anti-virus programs in my computer.
My 3d-card's fan recently went haywire and I've been experiencing alot of blackouts on my monitor. I'm guessing Avast might have somehow gotten screwed up during one of the boots, when I resetted the computer during a monitor's blackout which happened when Windows was booting. That's the only thing I can think of.
I installed Microsoft Visual C++ Express 2010 when I read from another same type of thread that it could solve the problem. It didn't.
Issue with your video card hardware may also be relevant to this, as in overheating issues.