If you are transferring programs to the infected computer, you can transfer MBAM's log and then copy/paste it back here for review.
Scanning with Malwarebytes Anti-Malware in safe or normal mode will work but removal functions are not as powerful in safe mode. MBAM is designed to be at full power when malware is running so safe mode is not necessary when using it. In fact, it loses some effectiveness
for detection & removal when used in safe mode because the program includes a special driver which does not work in safe mode. Further, scanning in safe mode prevents some types of malware from running so it may be missed during the detection process. For optimal removal, normal mode is recommended
so it does not limit the abilities of MBAM. Doing a safe mode scan should only
be done when a regular mode scan fails or you cannot boot up normally.
Rescan again with Malwarebytes Anti-Malware but this time perform a Full Scan
in normal mode and check all items found for removal. Don't forgot to check for database definition updates
through the program's interface (preferable method
) before scanning and to reboot afterwards. Failure to reboot normally
(not into safe mode) will prevent MBAM from removing all the malware. When done, click the Logs
tab and copy/paste the contents of the new report in your next reply.
If you cannot update through the program's interface and have already manually downloaded the latest definitions (mbam-rules.exe) shown on this page
, be aware that mbam-rules.exe is not
updated daily. Another way to get the most current database definitions if you're having problems updating, is to install MBAM on a clean computer, launch the program, update through MBAM's interface, copy the definitions (rules.ref
) to a USB stick or CD and transfer that file to the infected machine. Copy rules.ref to the location indicated for your operating system. If you cannot see the folder, then you may have to Reconfigure Windows
to show it.
- XP: C:\Documents and Settings\All Users\Application Data\Malwarebytes\Malwarebytes' Anti-Malware
- Vista: C:\Documents and Settings\Users\All Users\Malwarebytes\Malwarebytes' Anti-Malware
Note: bowser.sys is a part of Windows Vista
Explanation: This Stop message indicates that the requested page of kernel data from the paging file could not be read into memory. It might have been caused by a bad block (sector) in a paging file, a disk controller error, a defective motherboard, failing RAM, or because the stack signature in the kernel stack was not found. In extremely rare cases, it is caused when nonpaged pool resources run out.
Also see: Troubleshooting KERNEL_DATA_INPAGE_ERROR in Vista