New
#11
Do:
chkdsk/f c:
any errors? if so do it again. No errors now?
So BIOS is in AHCI mode. Do you know if it always was?
Do this in recovery environment ->"command prompt" (whre you did diskpart and chkdsk as well)
Is value of SELECT 1?Code:reg load hklm\win7sys C:\windows\system32\config\system reg query hklm\win7sys\select /v default reg query hklm\win7sys\controlset001\services\msahci /v start reg query hklm\win7sys\controlset001\services\pciide /v start reg query hklm\win7sys\controlset001\services\atapi /v start reg query hklm\win7sys\controlset001\services\iastor /v start reg query hklm\win7sys\controlset001\services\iastorv /v start reg unload hklm\win7sys
Which have start value 0?
Last edited by Kaktussoft; 03 Nov 2012 at 05:37.
I have no reason to belive that BIOS has changed however in my war with the rootkit it may have been changed. I personaly have not touched anything in the bios and dont think have have updated it recently>
chkdsk/f c: came up with no bad sectors and found no problems. However it "failed to transfer logged messages to the event log with status 50"
Will try those lines now.
Found it!! No need to do all the stuff I asked you to do !
how many files startin with avg? If not too mmany.. post the names pleaseCode:c: cd \Windows\System32\Drivers dir avg* dir/ah avg* dir/as avg*
When i punch in "cd \Windows\System32\Drivers " it cant find the specified path
Yea i did that the line reads "C:\>cd \Windows\System32\Drivers" and the response is "The system cannot find the path specified"
c:
cd \
cd windows
cd system32
cd drivers
where it says "The system cannot find the path specified" ?
Just relised why this may not be working im runing this off the windows cd i will try this again through the built in recovery cmd