As I explained here
, there is no need for you to worry about the SmitFraudFix
bug fix that you linked to above, as you haven't mentioned running SmitFraudFix
or being unable to boot. BSOD's are a different issue and much easier to troublehoot.
Altho a BSOD is mentioned, it is not the main problem, not being able to boot into windows is. The BSOD is just the start of it, probably because most systems are set to automatically restart when there is a serious error. That is to protect the system, but in the cases of the buggy SmitFraudFix
it backfired. And BTW, the setting to reboot when a BSOD occurs can be changed, and makes it easier to troubleshoot as the error message will stay onscreen til you manually resart the system. See our mini-guide here.
And FYI, other related mini-guides:How To Find Bsod Error MessagesHow To Use Event Viewer
Except for maybe disabling auto-restart, I don't suggest you try to troubleshoot the BSOD's for now. Looking at your other thread
, your system is terribly infected and it is likely that they are caused by infections remaining on your system. We hope to get that taken care of in your HJT session that often clears up such BSOD's.
Spybot just found some element of a Smitfraud infection (also known as Zlob) on your system. I believe you were calling an infection a bug, whereas we were calling a fault in the program a bug. It was just a matter of leaving out a single bracket character in the code that caused that problem.
Since you have another thread on basically the same problem, I will be closing this one now.