Hello. I'm having trouble recently with my laptop. I am getting Blue Screen of death multiple times per day on my laptop. I believe that the issue stems from the Qualcomm Atheros driver which could be infected.
So far I've tried:
-aswMBR: I cannot run a full scan with this program because I get a BSOD every single time at the same point during the middle of the scan.
-Farbar Recovery Scan Tool. See the attached log.
Here is the OSR Online Log for the info on the latest system crash
Here is the log from OSR:
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.comfor more information
Windows 8 Kernel Version 17134 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff803`f8e1c000 PsLoadedModuleList = 0xfffff803`f91ca150
Debug session time: Thu Jan 10 00:50:07.319 2019 (UTC - 5:00)
System Uptime: 0 days 11:30:57.550
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Remove this program if present in bold via the Control Panel > Programs > Programs and Features. App Explorer (HKU\S-1-5-19\…\Host App Service) (Version: 0.272.1.295 - SweetLabs)
Start Farbar Recovery Scan Tool with Administrator privileges (Right click on the FRST icon and select Run as administrator)
highlight on the text below and select Copy. beginning with Start:: and finishing with End:: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Highlight the entire content of the quote box below and select Copy.
Start FRST (FRST64) with Administrator privileges Press the Fix button. FRST will process the lines copied above from the clipboard. When finished, a log file Fixlog.txt will pop up and saved in the same location the tool was ran from.
Please copy and paste its contents in your next reply. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Right-click on AdwCleaner.exe and select [external image: Spcusrh.png]Run as Administrator (for Windows Vista, 7, 8, 8.1 and 10 users)
Accept the EULA (I accept), then click on Scan
Let the scan complete. Once it's done, make sure that every item listed in the different tabs is checked and click on the Clean & Repair button. This will kill all the active processes
Once the cleaning process is complete, AdwCleaner will ask to restart your computer, do it
After the restart, a log will open when logging in. Please copy/paste the content of that log in your next reply
Download the right version of RogueKiller for your Windows version (32 or 64-bit)
Once done, move the executable file to your Desktop, right-click on it and select [external image: Spcusrh.png]Run as Administrator (for Windows Vista, 7, 8, 8.1 and 10 users)
Click on the Start Scan button in the right panel, which will bring you to another tab, and click on it again (this time it'll be in the bottom right corner)
Wait for the scan to complete
On completion, the results will be displayed
Check every single entry (threat found), and click on the Remove Selected button
On completion, the results will be displayed. Click on the Open Report button in the bottom left corner, followed by the Open TXT button (also in the bottom left corner)
This will open the report in Notepad. Copy/paste its content in your next reply
you're already running Malwarebytes 3, open Malwarebytes and check for updates. Then click on the Scan tab and select Threat Scan and click on Start Scan button. If you don't have Malwarebytes 3 installed yet please download it from Malwarebytes Anti-Malware and install it.
If threats are detected, click the Apply Actions button. You will now be prompted to reboot. Click Yes. Upon completion of the scan (or after the reboot), click the Reports tab. Double-click the Scan Log. At the bottom click Export and choose Text file.
Save the file to your desktop and include its content in your next reply.
You can access the logs by going in the "Reports" tab, clicking on the latest "Scan" entry (the one with detections), then clicking on the "Export" button in the bottom-left corner and select "Copy to clipboard". After that, all you have to do is paste it here
Then click on POST
Exit Malwarebytes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
[external image: G0tu5D9.png]Emsisoft Emergency Kit - Fix Mode Follow the instructions below to run a scan using the Emsisoft Emergency Kit.
Download the Emsisoft Emergency Kit and execute it. From there, click on the Install button to extract the program in the EEK folder;
Once the extraction is complete, the EEK folder will open. Right-click on [external image: G0tu5D9.png]start emergency kit scanner.exe and select [external image: Spcusrh.png]Run as Administrator (for Windows Vista, 7, 8, 8.1 and 10 users);
EEK will suggest that you run an online update before using the program. Click on Yes to launch it.
After the update, click on Malware Scan under 2. Scan and accept to let EEK detect PUPs (click on Yes).
Once the scan is complete, make sure that every item in the list is checked, and click on the Quarantine selected button;
If it asks you for a reboot to delete some items, click on Ok to reboot automatically;
After the restart, open EEK again (in the C:\EEK folder);
This time, click on Logs;
From there, go under the Quarantine Log tab, and click on the Export button;
Save the log on your desktop, then open it, and copy/paste its content in your next reply;
Here are the 2 logs. They seem to indicate that nothing is wrong. I still get the crashes on my computer.
I googled "Blue screen of death. WFP_Invalid Operation" and it seems like most of the people who had that issue was because of their Qualcomm Atheros Driver.
*****************************
check the laptop manufacturers website and look for your model and look for updates related to your version.
if you use a usb wireless device you have to update the motherboard bios, cpu chipset drivers, any usb 3.x chipset driver as well as the driver for the actual usb device. (since usb devices depend on all of these components, you never know where the error comes from)