Indetrucks
Posts: 16 +0
Been a long time since I posted here fellas but it looks like I need your professional help once again...
Did a quick search and didn't find anything
(Flame suit on)
I made the boneheaded mistake of ending a process in the Windows Task Manager called svchost.exe. Immediately following, I noticed that my sound went dead. Naturally I tried to restart the computer and yep, you guessed it...now it won't boot.
It gets just about to the Windows boot screen and then a blue screen flickers on and it restarts over again. There is some writing at the top of the blue screen but it literally flickers for a split second making it ineligible.
From the brief searching I did on the net, it looks like this is what can happen when you eliminate the svchost process. I am not familiar with any sort of recovery process and the only disk I have is the Windows XP O/S install disk.
I have tried starting it in Safe Mode and (last known good configuration) with no avail.
The last thing I want to do is a new/clean install of XP, is there anyway to avoid this?
I promise to stay out of the Task Manager if I get this fixed
Did a quick search and didn't find anything
(Flame suit on)
I made the boneheaded mistake of ending a process in the Windows Task Manager called svchost.exe. Immediately following, I noticed that my sound went dead. Naturally I tried to restart the computer and yep, you guessed it...now it won't boot.
It gets just about to the Windows boot screen and then a blue screen flickers on and it restarts over again. There is some writing at the top of the blue screen but it literally flickers for a split second making it ineligible.
From the brief searching I did on the net, it looks like this is what can happen when you eliminate the svchost process. I am not familiar with any sort of recovery process and the only disk I have is the Windows XP O/S install disk.
I have tried starting it in Safe Mode and (last known good configuration) with no avail.
The last thing I want to do is a new/clean install of XP, is there anyway to avoid this?
I promise to stay out of the Task Manager if I get this fixed