Search the Community
Showing results for tags 'boot loop'.
-
My computer has collected some malware over the years. Most notably I accidently downloaded a fake anti-virus browser. Also, my Google was redirecting to Yahoo! and other searches. It got to the point I had to download Malware Bytes. Upon scanning there was around 90 Viruses/Malware Mostly Trojan. Everything in the scan was quarantined and I saved a log to my home screen. I then marked them for deletion using MalwareBytes and it promoted me to restart. So I restarted it and everything was working and no redirects were happening. I turned off my computer using normal startup menu. I come back in the menu and I kept getting no signal error on my monitor. I tried multiple steps to fix this but then just turned off the computer and unplugged it from its wall socket. I waited for 30 seconds and then plugged it back in. After that the usual boot screen came up but then came up with "Inaccessible Boot System" Error. I tried multiple methods to fix this. I tried 3 Different boot up methods from the Windows boot screen. I then did a pre boot diagnostic test which said that there was no hard drive connected. I opened up my PC And everything looked fine. I cannot get past this pre boot screen please help. I will provide extra details if I can.
-
OS: Windows 10 - 64 bit I installed Malwarebytes fresh today on an external drive (FAT32 file format if that's important). After the install it said it needed to restart, so I clicked ok. After I booted back in, I tried to login. However, after inputting my password, the "Welcome" text changed to "Restarting..." and the computer restarted. It continued to do this until I unplugged the drive which I installed Malwarebytes on. I saw someone with a similar issue in this thread, but the keys in the solution do not exist for me. Is there anyway I can still have Malwarebytes on my PC without this happening?
-
My PC was recently stricken down whilst watching youtube videos, resulting in my PC (windows 7) becoming trapped in a never ending nor successful boot or repair loop. After trying the automatic repair, system restore (no restore points) and booting in safe mode all unsuccessfully, my PC then simply started showing me a "windows failed to load" screen with mbamswissarmy.sys being the alleged perpetrator. I've been looking into this a lot the last couple of days, so I went ahead and used FRST on my broken pc via flash drive. Literally any morsel of help would be YUGELY appreciated, and my frst log is attached. FRST.txt
- 1 reply
-
- mbamswissarmy.sys
- boot loop
-
(and 6 more)
Tagged with:
-
I was wondering if anyone can walk me through restoring quarantined items that Malwarebytes removes via command line. I looked through the FAQ, but can't seem to figure it out. Here's my situation: I have a laptop running Windows 7 64-bit Home Premium SP1 and it got infected with the 2012 fake antivirus and the TDSS trojan. I was able to install and update Malwarebytes without an issue, turned off System Restore, downloaded Kaspersky's TDSSKiller, rebooted into Safe Mode, and scanned for malware. Malwarebytes removed about 12 things or so and TDSSKiller found about 2 or 3 instances which it removed. Now after the removal, I can't boot back up into Windows. I've tried booting normally, into safe mode, safe mode w/ networking, last known good configuration, disable auto restart on BSOD, etc. Every option still kicks over into a boot loop. I have also tried running Windows 7 Startup Repair from both the F8 screen and from booting from my Windows 7 disk and it can't find anything to repair. I've also tried booting into my Windows 7 disk and running "sfc /scannow /offbootdir=d: /offwindir=d:\windows" and that comes back with "Windows Resource Protection did not find any integrity violations." I would like to try a Windows repair installation (or in-place upgrade if you may), but can't start this without first booting into Windows. Is there any way I can use the command line utility from the Windows disk to run Malwarebytes to restore what it had removed? Thanks, Justin