Last gasp, sorta...
by Willy - 5/18/13 1:41 AM
In Reply to: Re: WAG here - New! by Big Steve
Sometimes, you have to clean house in order to reduce the drag the system has to support from system resources. That could be an issue for a Vista-32bit and probably only 2gb of ram. I have no idea what is on your laptop but if too much is installed or preloaded during boot-up it can be overcomed. I have a similar laptop and found i touched on BSOD when I know nothing is at fault as in malware. I found that the system resources were being sucked too quickly for the pgms. to work effectively. In my case, I simply removed/deleted anything that wasn't needed or desired anymore. I went over everything as best as possible and it settled. I know the problem comes back when I installed yet newer pgms. to try but leave them installed until I reach a "tipping point" and the BSOD comes back, I have to clean again. Now, that's my issue but it may reflect yours. That BSOD should display some error, what is it? -OR- check the event log entries some failure.
I say that, because already I see you using Avast, SaS, Malabytes, etc. and while these are helpful they shouldn't be left installed, pick one and stick with it. You may just want to use a "restore point" to a day where no problems were had. Once done and it seems OK, then start cleaning the system of any pgms., toolbars, games, anything that can be removed. I use the REVO uninstaller for such removal and its better IMHO than the plain add/remove feature of Vista, unless you want that or the pgm. itself only allows its removable under it own de-install method, like Avast. Once all that is done, REBOOT and go into safe mode w/networking and run whatever AV(after updating it) you got or have, install or follow their instructions and run scans. Its important to reboot, because after de-installing the registry has better tracking of what going on, etc.. Now, you know why any malware or similar scans take so long as a time-consuming tasks and no short cuts. Scanning repeatedly is necessary to prove everything is OK.
What, I have done in the past when nothing can be done or too much gets in the way, I remove the laptop HD. Place in test setup(adapter) on another PC. That PC has all the testing s/w and AV, etc. to check with. I then allow my test PC to scan or test the questionable HD directly(it alone) and check results. On your laptop, if you make a "bootable Hiren's CD disc" which runs under the Linux live version and use its test/scan s/w to check the laptop. Verify the laptop boots from CD/DVD and/or select from boot menu the disc(CD/DVD) drive and thus load the Hiren's rescue disc. This is another approach, but it takes some learning but its easily done. Also, if you made a Vista repair disc, it should when booted, provide a memory checker, run that as well. You can even run the "repair mode" and see if it finds something to correct in relation to the BSOD or Vista itself.
Sorry, for being all over the fix issue but if uncorrectable, you may need to decide to totally reload from scratch. Upon saving whatever data you deem critical, etc.. I hope you have the restore/recovery discs and/or your restore partition on HD is intact and well. Doing this is when all else fails provided you don't have some h/w fault or similar. Sometimes, you have to bite the bullet and go this route.
Was this reply helpful? (0) (0)