SuperAntiVirus Blue Screen issue

Hello,
For some time, I've been using SuperAntiSpyware without any problems and with great success. However, a few weeks ago, I started getting a blue screen mid scan with a warning "Kernal Stack Input Error." After reading some of the posts on this site, I discovered a suggestion was to uncheck "Kernal Direct File Access" as well as "Kernal Direct Registry Access." I tried that, to no avail. The screen goes absolutely blank. Last weekend, I had the TDL4, Google redirect virus and finally was able to remove it with aswMBR from Avast. I thought "hey, maybe that was the problem all along" and tried SuperAntiSpyware again afterward. Same problem. Any suggestions on how to correct this issue? I love SAS and can't use it anymore.

 

Thank you for the response, Chaslang.
Okay, I uninstalled, reinstalled and followed the directions in the link you provided. I'm getting the same result each time, a blue screen with the message "Kernal Stack Inpage Error." There are no logs showing up on the SAS log page. And while I'm no expert, I don't think this is a malware issue. My guess is a software conflict or an SAS issue. Do you have any other ideas? Would a HijackThis log help?

On another note, do you know anything about Google Voice Installation error 1603?

Thanks for your help!

 

Thanks for the response. I apologize for the delay. It took some time to have that much free time available.
Unfortunately, I completed all the steps in the READ & RUN ME section (including running the anti malware programs) and when I ran SAS portable (just to be safe) in quick scan mode, I got the same blue screen error and message "Kernal Stack Inpage Error." Is it possible the error I'm getting is NOT being caused by malware, but instead is a problem with SAS and/or my computer? Either way, do you have any other suggestions?

Incidentally, one suggestion about READ & RUN ME: where it says to go to msconfig and change to "Normal Startup Mode", it would have been helpful for it to say "first make note of current settings in startup" so that after the process, one can easily uncheck the unnecessary programs. Unfortunately, I did not do this and when I was done, I had a ton of crap running when I booted my computer. I had to research to discover what to check and what to uncheck (some programs I want and some I don't, however not all have names revealing what program they represent).

 

Sorry, I'm confused. The directions said to open msconfig and check "normal startup mode." I did that. Then I got a message saying "reboot to take effect" and I rebooted. Was I not supposed to?

Also, in the Malware Removal/Cleaning Procedure, the first program to run is SAS. I ran it and I got the blue screen and so, no log is produced. That is where I stopped. Please explain what you'd like me to do differently.

Thanks.

 

If I were supposed to go into msconfig and check "normal startup mode" then I have no idea what this means: " don't use MSconfig to control startups which is what the READ & RUN ME said" nor do I understand why you'd tell me not to keep track of what programs are running through start up and what programs aren't. After I checked normal startup mode, a ton of programs that normally don't start, did. I don't want that to remain that way, so after I'm done with all the scanning, I would have to go back and turn them off. Without keep a list of which ones were off, I wouldn't be able to easily do this. If there is another way to prevent programs from running in startup, I'm not unfamiliar. Perhaps I'm not as technically savvy as you might think. Please clarify.

Finally, since my issue was SAS bluescreen, it seemed pointless to me to go through all the previous steps, end up right where I was and continue on. It made more sense to me to think that the instructions given were guidelines for malware removal and NOT fixing SAS. Had it been for fixing SAS I would have expected SAS to be run AFTER all other anti malware programs. I did not expect that procedure to be tailor made to my situation, but rather a general guideline for malware problems. Nevertheless, I'd be happy to continue provided I know what you mean in the msconfig section.
Thanks.