[Lady Jag]

My Avast anti-virus caught siszyd32.exe and ejozeleqayisado.dll,startup yesterday.

It took care of the dll right off and led me disable siszyd32.

Somehow siszyd32 kept re-enabling itself and I knew that because Win Patrol Plus (Scottie) kept asking me if I would allow siszyd32 access my computer, repeatedly I said no.

That's when I began running other utilities, anti-virus, anti-malware, registry cleaner, everything got blocked in progress, usually when its process was coming to an end. Some had also detected the virus but the virus terminated them before action could be taken.

[derekr44]

Somehow siszyd32 kept re-enabling itself and I knew that because Win Patrol Plus (Scottie) kept asking me if I would allow siszyd32 access my computer, repeatedly I said no.

Yes, it will continue to do so because the rootkit code has embedded itself into valid Windows system files. On the Avast forum example I linked, the virus attached itself to the atapi.sys file (which is a harddisk controller). That could explain why you can't get very far when you boot it up now.

[Gorzaloon]

everything got blocked in progress, usually when its process was coming to an end. Some had also detected the virus but the virus terminated them before action could be taken.

More likely it was the begiining of your HD Failure that was causing things to blackscreen.

Here is the summary: HD only reads the first few blocks on POST (Power On Self Test) then stops. HD cannot be autodeteced by BIOS. The HD is 9 years old, and ran every day for 12 hours. That's 38,000 hours. Not much at all for today's HD's with an MBTF of multiples of that. But it's pining for the fjiords..

Data can be recovered by getting an identical drive and under cleanroom conditions, switching the platter stack. Software recovery and repair programs like Spinrite will not work if the HD will not run.