Malware Bytes crashes when attempting update

[Chelsey]

I recently tried to scan My computer and MalwareBytes tried to do an automatic update...after initializing the update process it completely crashed and closed before I could update. I'm afraid I have a bug that won't let me run the program. I also tried to run MalwareBytes Chameleon-that didn't work either...it tried to update the program through Chameleon and it just did the same thing and crashed. PLEASE HELP!!!

[1PW]

Hello Chelsey and

Malwarebytes staffers may be urgently looking for data on this particular type of failure.

Please make no changes in your computer's software but do obtain these Diagnostic Logs and attach those 3 log text files in a reply to this topic.

Hopefully you will then be contacted by a Malwarebytes staffer very soon after your reply.

Thank you.

[Maurice Naggar]

Hi Chelsey,

Beyond the diagnostic logs ( that is in addition to those ).....

What version did you have before?

At what point ( and How ) was the "crash" happening?

 

I suspect though that you can start the program again and do Scans.

 

I would also like to know How you did the Chameleon steps ( whether started from mbam folder or if you actually went to a download)  and why you chose Chameleon route.

Looking forward to having the details from you , and to get your MBAM good to go again.

[Chelsey]

Attached are the Diagnostic Logs requested.

 

 

In response to this: 

 

"Hi Chelsey,

Beyond the diagnostic logs ( that is in addition to those ).....

What version did you have before?

At what point ( and How ) was the "crash" happening?

 

I suspect though that you can start the program again and do Scans.

 

I would also like to know How you did the Chameleon steps ( whether started from mbam folder or if you actually went to a download)  and why you chose Chameleon route.

Looking forward to having the details from you , and to get your MBAM good to go again."

 

 

-I don't know what version I had before for sure, but in my Downloads folder there is the version I initially downloaded along with the most recent version. The initially downloaded version is titled "mbam-setup-1.75.0.1300" and the most recent version is "mbam-setup-2.0.2.1012" which is supposedly out of date now as well. So if my previous version wasn't "mbam-setup-1.75.0.1300" then I don't know what it was. 

 

Every time I would start my computer Mbam would start up and either update itself or scan the computer for threats. One day about a couple weeks ago, I started up my computer and Mbam just crashed instead of doing its routine thing. I got a dialogue box saying Mbam could not update.

 

I can not start the program and do Scans. I can start the program and let it just sit there doing nothing. It says "your databases are out of date" at the top and there is a "FIX NOW" button to the right...when you push "Fix Now" the program crashes and instantly closes saying it can not update. The database version listed when you have the program open is "v2014.03.04.09" and there is a tab right next to it saying "Update Now"...press that and the same thing happens-the program crashes and closes.

 

Mbam Chameleon was already on my computer from the initial installation of Mbam. I used it because that's what the program says it's designed for-to scan Mbam for threats under a different name in case there is a virus or something blocking "Mbam" tagged scans or processes. The Chameleon was useless...it started doing its thing and then wanted to check for an update to Mbam...again crash just like every other attempt.

 

I am also a premium member, I paid to get this software and I can not get the direct tech support I paid for because it is asking me for an order number I don't have in order to submit a ticket and get direct support from the website instead of the forum. That is also very frustrating too that I have to use a forum to get help now. I want to submit a ticket and get the service I paid for. This has been extremely frustrating. Thanks for your help. 

 

FRST.txt

Addition.txt

CheckResults.txt

[Maurice Naggar]

Hi Chelsey,

 

I am moving this thread to the Malware removal forum and will be replying again to you.

[Maurice Naggar]

Hello Chelsey,

 

A few points ( of moderate consequence) and mentioning only just so you know.
a) "mbam-setup-1.75.0.1300" is the old ( now outdated) setup-installer utility.   You should delete it.
That was for version 1.75 but the very latest version is now 2.0.2.1012

b)  "mbam-setup-2.0.2.1012"  is the installer for the current version.  You may keep it.  But just put it safely aside  ( wherever you have it).

c) Glad to know that you tried the built in Chameleon instead of doing a download of it.  I just wanted to know what you did & how you tried.

d) While the Dashboard screen may not be fully responding as expected, your program does start and is able to be used ---- i.e., you can click the Scan icon at the top bar and could run Scans.

e) I moved your topic to the Malware removal help sub-forum since I see a sign of a trace of a Zero Access rootkit infection.
I also see a really pesky adwares infestation, that is multi-pronged. Some by Conduit pest and a few by xvildly.
xvidly3 Toolbar - a Conduit "Community Toolbar" - redirects searches to search.conduit.com.
Conduit toolbars are also reputed to have a certain trackware functionality and will often come bundled with various third party software.


Next action items for you, please:
Step A
Save the attached file Fixlist.txt    to the same location where you have FRST.exe   ---- the Desktop

It needs to be saved Next to the "Farbar Recovery Scan Tool" (FRST) program (If asked to overwrite an existing one please allow)


Close all internet browser programs before starting FRST so that they are not running.   ( includes Internet Explorer, Chrome, Firefox, etc.)
Run FRST again but this time press the "Fix" button just once and wait.

When finished, it will make a log (fixlog.txt) next to FRST.
Please attach the Fixlog.txt  into a reply.


Step B
With the conslusion of the FRST cleanup, then do this next.



Please download Malwarebytes Anti-Rootkit (MBAR)  and save it to your desktop,
from here   
http://downloads.malwarebytes.org/file/mbar

•Be sure to print out ( if possible) and follow the instructions provided on that same page.

•Doubleclick on the MBAR file you downloaded and approve the UAC prompt in Vista and newer operating systems.
•Click **OK** on the next screen, to allow the package to extract the contents of the file to its own folder, mbar.
•mbar.exe will launch automatically. On some systems, this may take a few extra seconds. Please be patient and wait for the program to open.
•After reading the Introduction, click '**Next**' if you agree.
•On the Update Database screen, click on the '**Update**' button.
•Once you see 'Success: Database was successfully updated' click on 'Next'.
•Click the '**Scan**' button.

With some infections, you may see two messages boxes.
  1.'Could not load protection driver'. Click 'OK'.
  2.'Could not load DDA driver'. Click 'Yes' to this message, to allow the driver to load after a restart. Allow the computer to restart. Continue with the rest of these instructions.
 

 

When the Scan has completed =>, click the 'CleanUp' button

and allow the reboot if prompted.


Please attach the most recent mbar-log-2014 <date and time>.txt in your next reply.

Perform another scan with Malwarebytes Anti-Rootkit to verify that no threats remain.

 

 

Then, please send the following logs as attachments to your reply. These logs are located in the mbar folder on your desktop where the tool extracted itself to.

**mbar-log-2014-06-xx(xx-xx-xx).txt** (where xx-xx(xx-xx-xx) is the date and time of the scan)
+ also
**system-log.txt**

I need to have both of those files attached in your next reply.  Thanks.  **Send even if nothing is reported as detected. Always send these.**

Fixlist.txt

[Chelsey]

Hello again, just wanted to let you know, so you know what is happening...in response to:

 

"d) While the Dashboard screen may not be fully responding as expected, your program does start and is able to be used ---- i.e., you can click the Scan icon at the top bar and could run Scans."

 

-No, I actually still can not perform scans. I can open the program and let it sit there running, but when I click the scan button, it immediately tries to update itself and crashes. Strangely though, a few days ago, I think did see Malwarebytes do an automatic scan out of nowhere, maybe that's what you saw if there was a log that said I had recently scanned? But that was the only time I have seen that happen since this whole mess started, and I can not perform scans when I try, period-it always wants to automatically update and then crashes. 

 

I am wondering-would you be able to let me know what part of the script from the logs I sent you let you know that I have a zero-access rootkit infection and several "multi pronged" adwares? I'm just curious, because I do remember Xvidly being a problem for quite some time now, and I never even remembered installing it in the first place. I first noticed it I'm pretty sure months ago...Every time I would open the Google browser, (which is my default browser and search engine) it would redirect me to the conduit search...and this would be in the URL box: "http://search.conduit.com/?ctid=CT3322287&octid=EB_ORIGINAL_CTID&SearchSource=55&CUI=&UM=2&UP=SP21D801BE-6BAD-4AF9-B926-A8195B9D3C66&SSPV=" That has been happening for a while now, longer than Malwarebytes has been non-functioning. I noticed recently a program named Xvidly running in my task bar, (and i always have that up and running), so I get used to seeing the same processes every day...well I noticed Xvidly and I would end its process. Only about a week ago, (before I started this thread), I had uninstalled it from my comuter, because it said it was a toolbar, and I don't need a toolbar app. I thought nothing of it, but if that is part of the virus...then I've been noticing its presence for months now. I would very much like to know the tag that was found in my diagnostics that is showing this rootkit and adware if possible.

 

On the topic of the zero access rootkit-I found out after some research last night that the 0-ring rootkit that I might have is the worst of the several types of the rootkits that exist, because they can fool the system by making it think it's processes are systems own processes-making it near untracable. That is very upsetting to me, so I really want to tackle this disgusting beast asap! This is very disturbing news to me.

 

So now on to what was requested of me to do, I deleted the old version "mbam-setup-1.75.0.1300" from my downloads folder and ran the fix log, but when I ran the Anti-Rootkit program it completed the scan saying there was no threat detected and there was no log that popped up for me to be able to attach here. The program simply had a "back" and an "exit" button...so I pushed "exit" thinking it would pop up a Notepad window with the text like the FRST program did...well-nothing happened. So I'm going to need further instruction on how to get that file for you. Anyway, here is the Fixlog, and I truly appreciate all your detailed help! 

 

 

 

Fixlog.txt

[Chelsey]

I do apologize, I just saw your instructions on how to find the file-here it is, sorry about that!1

mbar-log-2014-06-17 (20-29-54).txt

system-log.txt

[Maurice Naggar]

Hello,

 

The mention of a trace of Zero access was from the FRST log, this part

ZeroAccess:
C:\$Recycle.Bin\S-1-5-21-1870535305-4293684592-1831110953-1001\$47b07254d9868e1784f06bd9398844c6

 

 

There is not a need for you to be worried about that.  It was removed as part of the Fix run of FRST which you completed.

The result from the antirootkit run is also very encouraging.   There is no rootkit malware.

 

From your description of the Google Chrome issue, it sounds like you need to run this next tool.

Download and SAVE Shortcut Cleaner to your Desktop from http://www.bleepingcomputer.com/download/shortcut-cleaner/dl/172/
On Windows 7 / 8 / Vista, do a Right-click on it and select Run as Administrator.
On Windows XP, double-click to start.

When all done, Copy & Paste the contents of "sc-cleaner.txt"into a reply.

 

Step B

 

Shutdown Windows.

Turn off your pc. Wait about a minute.
Restart your pc.  And right away, tap & retap the F8 Function-key on your keyboard.
You should see Windows Advanced Options menu.
Select Safe Mode with Networking

NOTE: if the F8 function key-method did not prove useable, some systems may use F5 instead.   
And on some systems you may need to press the F2 function key to get hardware boot options.

 

Start the Anti-Malware program.
on the Dashboard, click the **Scan Now >>** ( link)  button.
If an update is available, click the Update Now button.
A Threat Scan will begin.
When the scan is complete, if there have been detections, click **Apply Actions** to allow MBAM to clean what was detected.
In some cases, a restart will be required.
Wait for the prompt to restart the computer to appear, then click on Yes.



Click on the **History tab** > Application Logs.
Double click on the scan log which shows the Date and time of the scan just performed.
Click **'Copy to Clipboard'**
Paste the contents of the clipboard into your reply.

 

 

 

Step C

Restart Windows back into normal mode.

 

Look for and send me as attachments the last two protection logs from the Anti-Malware that would be in this folder C:\ProgramData\Malwarebytes\Malwarebytes Anti-Malware\Logs.

 

protection-log-2014-06-17.xml  
protection-log-2014-06-18.xml

 

Step D

Please make these settings inside your settings in the Scheduler.

 

Take a look inside the program. Start the Anti-Malware. Click on the Settings icon at the top bar up at top.
Then click the **Advanced Settings** button at the left.
Be sure all top 3 lines on that window are check-marked ( selected ).

Now a couple of changes for each of the Update task & the Threat scan task in the Scheduler.
Click on **Automated Scheduling** button.

Locate and click once on **Check for Updates** line and press Edit. Then press the Advanced button at bottom left.
Slide the window up so you can see all of it. {press the mouse on the very top bar and slide UP }
A few changes are needed.
Look at the "starting time" of the task and use some good time when you know that your computer will be on & powered & that Windows would be on at that time.
Look at the line in Schedule Options. UN-check "Show notification after successful update".

In the Frequency and Settings. Select Hourly and I suggest using the Recurrence at 4 hours.
In the Recovery Options put a check-mark on "Recover missed tasks" and select 1 hour
When done, press the OK button.

Locate and click once on the Threat Scan line and press Edit.Then press the Advanced button at bottom left.
Slide the window up so you can see all of it. {press the mouse on the very top bar and slide UP }

In the Schedule Options, put a check-mark on the line Terminate program when no threats are found
{when no malwares are detected you want the scheduled task to close}.

In the Frequency and Settings block.
You should have Daily and the recurrence set to 1 day.
now UN-check the line Check for updates before scanning {{that line should be always off otherwise the task may not run at the time set. It maybe run +/- 15 minutes of that period.}

In the Recovery Options put a check-mark on "Recover missed tasks" and select 1 hour
When done, press the OK button.

When completely done, close the window.

A fresh Windows start would be good to do at this point. Use Logoff and Restart Windows.
 

 

 

[Chelsey]

Here are the results from Sc-Cleaner. Since my original problem with MBAM has not been taken care of yet, I still can not perform scans, therefore can not complete Step B. Even in safe networking mode MBAM still wants to update-and crashes. As a result Step C can not be performed. In the instructions for Step D-when I click "check for updates" the "Edit" button is greyed out. I can not edit it. 

sc-cleaner results.txt

[Maurice Naggar]

Hello Chelsey,

 

Next, ( but only if the program is running) let's shutdown the realtime Malwarebytes Anti-Malware. Go to the desktop Taskbar. See the blue-color MBAM icon in the notification area.
Do a Right-click on it with your mouse, and select EXIT.
{ if you are only running the Free mode program, you will not see that, so in that case you can ignore that step.}.

Download & Save to your system a zip file named REF_Replace.zip from this link https://malwarebytes.box.com/s/l0q4533c7kcqxnpp8ldc

Once saved, unzip **REF_Replace.zip**  to extract all contents.   which will be 4 files.
Next, double-click on **Ref-Replace.bat** file.
It should run fairly quickly in a command-prompt window.

I would suggest then a Logoff >> Shutdown >> Restart so that your pc is then in a new Windows session.

Once that is done, restart the Anti-Malware and let me know if it works normally.

[Chelsey]

I am so frustrated right now. I followed the instructions exactly and now Mbam won't even open. It did not start up by itself, so I tried to open it myself. I opened it from the Start menu and the window opened for me to "okay" that I want Mbam to make changes to my computer and I clicked "yes" and nothing happens. I opened the task manager and tried to open Mbam several more times-I would see Mbam in the task manager when the window came up for me to confirm I wanted it to run...then when I approve-NOTHING. It disappears. I paid for this program and I am really starting to feel like it was a waste of hard earned money..

[Maurice Naggar]

Hello,

 

The message/prompt  <<to "okay" that I want Mbam to make changes to my computer and I clicked "yes">> is from Windows' User Account Control and is very normal.

 

It has been a long saga, and you should have lots of patience.  Your money was not wasted.  There is just something on this system and its total configuration that is the source of the issue.  It is just harder to pin down here.

So if we are to continue, you need to make regular daily replies and not let time elapse in between, as your helper here will "forget" all the various unique things here.

 

So now, it seems we may need to do a new ( another ) clean removal and new install.

 

But first, please do this so I can have fresh reports for review.

 

 

Set Windows 7 to Show all files by doing this :
Press and hold Windows-key+E key on keyboard to start Windows Explorer.
From the Windows Explorer menu options, Select Tools, then Folder Options.
Next click the View tab.
Locate and uncheck "Hide protected operating system files (Recommended).

Locate and click "Show hidden files and folders and drives. "
Click Apply > OK.
 

 

NEXT:

Download DDS and save it to your desktop from here http://download.bleepingcomputer.com/sUBs/dds.com
or http://download.bleepingcomputer.com/sUBs/dds.scr

Double click dds to run the tool.  

DDS will run in a command prompt window and will take 3 to 4 minutes or so.
Follow and answer the prompts as appropriate.

When done, DDS will open two (2) logs: DDS.txt & Attach.txt
Save both reports to your desktop.
Please attach following logs in your next reply:  DDS.txt  +  Attach.txt

 

NEXT:

Please read carefully and follow these steps.

If you have Tdsskiller from a prior use, Delete the prior copies of TDSSKILLER.zip  & TDSSKILLER.exe that you may have.....if any.

Download TDSSKiller and save it to your Desktop.
http://support.kaspersky.com/downloads/utils/tdsskiller.exe   

Temporarily disable (turn off) your antivirus app so that it does not interfere:
How To Temporarily Disable Your Anti-virus, Firewall And Anti-malware Programs
http://www.bleepingcomputer.com/forums/index.php?showtopic=114351

If on Windows 7 or 8 or Vista, RIGHT-Click on TDSSKiller.exe and select Run As Administrator to run the application.
If on Windows XP, double-click on TDSSKiller.exe to start.

Click on "Change parameters" and place a checkmark next to Verify Driver Digital Signature and Detect TDLFS file system, then click OK
Then press Start Scan

If a suspicious file is detected, the default action will be "Skip", click on "Continue."

If you get the warning about a file UnsignedFile.Multi.Generic or LockedFile.Multi.Generic please choose
Skip and click on Continue

It may ask you to reboot the computer to complete the process. Click on "Reboot Now".

When the scan is done, it will display a summary screen.

If no reboot is require, click on Report. A log file should appear. Please copy and paste the contents of that file here.
If a reboot is required, the report can also be found in your root directory, (usually C:\ folder) in the form of "TDSSKiller.[Version]_[Date]_[Time]_log.txt".

Please Attach that log file into a reply.

Now, re-enable your antivirus app.
 

 

[Chelsey]

Hello, I have followed the instructions and attached the two files "DDS.txt  +  Attach.txt". I was unable to find the file to attach for the TDSSKILLER log, so I copied and pasted it below. Also, the webpage said my text was too long to post, so I cut the TDSKILLER results in half and posted the second half in its own responce. If that is going to be a problem, please help me find the file to attach. There was no TDSS folder in my C: Program Files

 

Should I uninstall Malwarebytes, Chameleon, and the other programs I have installed since the start of this including: Fixlist, Malwarebytes Anti-Rootkit (MBAR), Shortcut Cleaner,  **REF_Replace.zip**, DDS and TDSSKILLER?

 

14:17:08.0430 0x21d4  TDSS rootkit removing tool 3.0.0.39 Jun  5 2014 20:35:54

14:17:30.0002 0x21d4  ============================================================

14:17:30.0003 0x21d4  Current date / time: 2014/07/01 14:17:30.0002

14:17:30.0003 0x21d4  SystemInfo:

14:17:30.0003 0x21d4  

14:17:30.0003 0x21d4  OS Version: 6.1.7601 ServicePack: 1.0

14:17:30.0003 0x21d4  Product type: Workstation

14:17:30.0003 0x21d4  ComputerName: CHELSEY-MSI

14:17:30.0004 0x21d4  UserName: Chelsey

14:17:30.0004 0x21d4  Windows directory: C:\windows

14:17:30.0004 0x21d4  System windows directory: C:\windows

14:17:30.0004 0x21d4  Running under WOW64

14:17:30.0004 0x21d4  Processor architecture: Intel x64

14:17:30.0004 0x21d4  Number of processors: 8

14:17:30.0004 0x21d4  Page size: 0x1000

14:17:30.0004 0x21d4  Boot type: Normal boot

14:17:30.0004 0x21d4  ============================================================

14:17:30.0290 0x21d4  KLMD registered as C:\windows\system32\drivers\21438891.sys

14:17:30.0845 0x21d4  System UUID: {1C14527C-133D-1AF9-3CB9-8A0A56AE702D}

14:17:31.0441 0x21d4  Drive \Device\Harddisk0\DR0 - Size: 0x15D51500000 ( 1397.27 Gb ), SectorSize: 0x200, Cylinders: 0x2C882, SectorsPerTrack: 0x3F, TracksPerCylinder: 0xFF, Type 'K0', Flags 0x00000040

14:17:31.0444 0x21d4  ============================================================

14:17:31.0444 0x21d4  \Device\Harddisk0\DR0:

14:17:31.0444 0x21d4  MBR partitions:

14:17:31.0444 0x21d4  \Device\Harddisk0\DR0\Partition1: MBR, Type 0x7, StartLBA 0x13B5800, BlocksNum 0xAD6D4000

14:17:31.0444 0x21d4  ============================================================

14:17:31.0445 0x21d4  C: <-> \Device\Harddisk0\DR0\Partition1

14:17:31.0445 0x21d4  ============================================================

14:17:31.0445 0x21d4  Initialize success

14:17:31.0445 0x21d4  ============================================================

14:18:02.0513 0x204c  ============================================================

14:18:02.0513 0x204c  Scan started

14:18:02.0513 0x204c  Mode: Manual; SigCheck; TDLFS; 

14:18:02.0514 0x204c  ============================================================

14:18:02.0514 0x204c  KSN ping started

14:18:16.0339 0x204c  KSN ping finished: true

14:18:17.0085 0x204c  ================ Scan system memory ========================

14:18:17.0085 0x204c  System memory - ok

14:18:17.0087 0x204c  ================ Scan services =============================

14:18:17.0192 0x204c  [ A87D604AEA360176311474C87A63BB88, B1507868C382CD5D2DBC0D62114FCFBF7A780904A2E3CA7C7C1DD0844ADA9A8F ] 1394ohci        C:\windows\system32\drivers\1394ohci.sys

14:18:17.0350 0x204c  1394ohci - ok

14:18:17.0386 0x204c  [ D81D9E70B8A6DD14D42D7B4EFA65D5F2, FDAAB7E23012B4D31537C5BDEF245BB0A12FA060A072C250E21C68E18B22E002 ] ACPI            C:\windows\system32\drivers\ACPI.sys

14:18:17.0400 0x204c  ACPI - ok

14:18:17.0423 0x204c  [ 99F8E788246D495CE3794D7E7821D2CA, F91615463270AD2601F882CAED43B88E7EDA115B9FD03FC56320E48119F15F76 ] AcpiPmi         C:\windows\system32\drivers\acpipmi.sys

14:18:17.0488 0x204c  AcpiPmi - ok

14:18:17.0582 0x204c  [ 4451CC2275B04043EC2BCC757AF97291, A07781C5C9AD344BF2B5F8E7ED0ACD804113B6BC02D082717E493768E6ABC393 ] AdobeActiveFileMonitor8.0 C:\Program Files (x86)\Adobe\Elements Organizer 8.0\PhotoshopElementsFileAgent.exe

14:18:17.0605 0x204c  AdobeActiveFileMonitor8.0 - ok

14:18:17.0700 0x204c  [ ADDA5E1951B90D3D23C56D3CF0622ADC, E85E7BFD29F00ED34BF5BE8BD4DA93CBB14278E16809BB55406875F0DA88551E ] AdobeARMservice C:\Program Files (x86)\Common Files\Adobe\ARM\1.0\armsvc.exe

14:18:17.0728 0x204c  AdobeARMservice - ok

14:18:17.0854 0x204c  [ 09E7C37DF4A911C8A9AA8BF88ACD10AA, E881E0BBDCED58F28E0BA8DC27372EDFFFF2C57EE31CD13A032FDC9F7C831B5A ] AdobeFlashPlayerUpdateSvc C:\windows\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe

14:18:17.0878 0x204c  AdobeFlashPlayerUpdateSvc - ok

14:18:17.0903 0x204c  [ 2F6B34B83843F0C5118B63AC634F5BF4, 43E3F5FBFB5D33981AC503DEE476868EC029815D459E7C36C4ABC2D2F75B5735 ] adp94xx         C:\windows\system32\drivers\adp94xx.sys

14:18:17.0926 0x204c  adp94xx - ok

14:18:17.0935 0x204c  [ 597F78224EE9224EA1A13D6350CED962, DA7FD99BE5E3B7B98605BF5C13BF3F1A286C0DE1240617570B46FE4605E59BDC ] adpahci         C:\windows\system32\drivers\adpahci.sys

14:18:17.0949 0x204c  adpahci - ok

14:18:17.0964 0x204c  [ E109549C90F62FB570B9540C4B148E54, E804563735153EA00A00641814244BC8A347B578E7D63A16F43FB17566EE5559 ] adpu320         C:\windows\system32\drivers\adpu320.sys

14:18:17.0975 0x204c  adpu320 - ok

14:18:17.0993 0x204c  [ 4B78B431F225FD8624C5655CB1DE7B61, 198A5AF2125C7C41F531A652D200C083A55A97DC541E3C0B5B253C7329949156 ] AeLookupSvc     C:\windows\System32\aelupsvc.dll

14:18:18.0027 0x204c  AeLookupSvc - ok

14:18:18.0069 0x204c  [ 79059559E89D06E8B80CE2944BE20228, 6E041D2FED2D0C3D8E16E56CB61D3245F9144EA92F5BDC9A4AA30598D1C8E6EE ] AFD             C:\windows\system32\drivers\afd.sys

14:18:18.0129 0x204c  AFD - ok

14:18:18.0144 0x204c  [ 608C14DBA7299D8CB6ED035A68A15799, 45360F89640BF1127C82A32393BD76205E4FA067889C40C491602F370C09282A ] agp440          C:\windows\system32\drivers\agp440.sys

14:18:18.0159 0x204c  agp440 - ok

14:18:18.0187 0x204c  [ 3290D6946B5E30E70414990574883DDB, 0E9294E1991572256B3CDA6B031DB9F39CA601385515EE59F1F601725B889663 ] ALG             C:\windows\System32\alg.exe

14:18:18.0252 0x204c  ALG - ok

14:18:18.0295 0x204c  [ 5812713A477A3AD7363C7438CA2EE038, A7316299470D2E57A11499C752A711BF4A71EB11C9CBA731ED0945FF6A966721 ] aliide          C:\windows\system32\drivers\aliide.sys

14:18:18.0306 0x204c  aliide - ok

14:18:18.0318 0x204c  [ 1FF8B4431C353CE385C875F194924C0C, 3EA3A7F426B0FFC2461EDF4FDB4B58ACC9D0730EDA5B728D1EA1346EA0A02720 ] amdide          C:\windows\system32\drivers\amdide.sys

14:18:18.0326 0x204c  amdide - ok

14:18:18.0329 0x204c  [ 7024F087CFF1833A806193EF9D22CDA9, E7F27E488C38338388103D3B7EEDD61D05E14FB140992AEE6F492FFC821BF529 ] AmdK8           C:\windows\system32\drivers\amdk8.sys

14:18:18.0361 0x204c  AmdK8 - ok

14:18:18.0364 0x204c  [ 1E56388B3FE0D031C44144EB8C4D6217, E88CA76FD47BA0EB427D59CB9BE040DE133D89D4E62D03A8D622624531D27487 ] AmdPPM          C:\windows\system32\drivers\amdppm.sys

14:18:18.0377 0x204c  AmdPPM - ok

14:18:18.0388 0x204c  [ D4121AE6D0C0E7E13AA221AA57EF2D49, 626F43C099BD197BE56648C367B711143C2BCCE96496BBDEF19F391D52FA01D0 ] amdsata         C:\windows\system32\drivers\amdsata.sys

14:18:18.0399 0x204c  amdsata - ok

14:18:18.0422 0x204c  [ F67F933E79241ED32FF46A4F29B5120B, D6EF539058F159CC4DD14CA9B1FD924998FEAC9D325C823C7A2DD21FEF1DC1A8 ] amdsbs          C:\windows\system32\drivers\amdsbs.sys

14:18:18.0433 0x204c  amdsbs - ok

14:18:18.0442 0x204c  [ 540DAF1CEA6094886D72126FD7C33048, 296578572A93F5B74E1AD443E000B79DC99D1CBD25082E02704800F886A3065F ] amdxata         C:\windows\system32\drivers\amdxata.sys

14:18:18.0450 0x204c  amdxata - ok

14:18:18.0463 0x204c  [ 89A69C3F2F319B43379399547526D952, 8ABDB4B8E106F96EBBA0D4D04C4F432296516E107E7BA5644ED2E50CF9BB491A ] AppID           C:\windows\system32\drivers\appid.sys

14:18:18.0497 0x204c  AppID - ok

14:18:18.0510 0x204c  [ 0BC381A15355A3982216F7172F545DE1, C33AF13CB218F7BF52E967452573DF2ADD20A95C6BF99229794FEF07C4BBE725 ] AppIDSvc        C:\windows\System32\appidsvc.dll

14:18:18.0578 0x204c  AppIDSvc - ok

14:18:18.0616 0x204c  [ 9D2A2369AB4B08A4905FE72DB104498F, D6FA1705018BABABFA2362E05691A0D6408D14DE7B76129B16D0A1DAD6378E58 ] Appinfo         C:\windows\System32\appinfo.dll

14:18:18.0673 0x204c  Appinfo - ok

14:18:18.0692 0x204c  [ C484F8CEB1717C540242531DB7845C4E, C507CE26716EB923B864ED85E8FA0B24591E2784A2F4F0E78AEED7E9953311F6 ] arc             C:\windows\system32\drivers\arc.sys

14:18:18.0712 0x204c  arc - ok

14:18:18.0720 0x204c  [ 019AF6924AEFE7839F61C830227FE79C, 5926B9DDFC9198043CDD6EA0B384C83B001EC225A8125628C4A45A3E6C42C72A ] arcsas          C:\windows\system32\drivers\arcsas.sys

14:18:18.0740 0x204c  arcsas - ok

14:18:18.0850 0x204c  [ 9A262EDD17F8473B91B333D6B031A901, 05DFBD3A7D83FDE1D062EA719ACA9EC48CB7FD42D17DDD88B82E5D25469ADD23 ] aspnet_state    C:\windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_state.exe

14:18:18.0883 0x204c  aspnet_state - ok

14:18:18.0897 0x204c  [ 769765CE2CC62867468CEA93969B2242, 0D8F19D49869DF93A3876B4C2E249D12E83F9CE11DAE8917D368E292043D4D26 ] AsyncMac        C:\windows\system32\DRIVERS\asyncmac.sys

14:18:18.0940 0x204c  AsyncMac - ok

14:18:18.0978 0x204c  [ 02062C0B390B7729EDC9E69C680A6F3C, 0261683C6DC2706DCE491A1CDC954AC9C9E649376EC30760BB4E225E18DC5273 ] atapi           C:\windows\system32\drivers\atapi.sys

14:18:19.0005 0x204c  atapi - ok

14:18:19.0058 0x204c  [ E857EEE6B92AAA473EBB3465ADD8F7E7, 1C7E4737E649A025B3C4974A4F7D1353EAB85561FC8ED54E5C22A777E1A189B3 ] athr            C:\windows\system32\DRIVERS\athrx.sys

14:18:19.0124 0x204c  athr - ok

14:18:19.0191 0x204c  [ F23FEF6D569FCE88671949894A8BECF1, FCE7B156ED663471CF9A736915F00302E93B50FC647563D235313A37FCE8F0F6 ] AudioEndpointBuilder C:\windows\System32\Audiosrv.dll

14:18:19.0265 0x204c  AudioEndpointBuilder - ok

14:18:19.0277 0x204c  [ F23FEF6D569FCE88671949894A8BECF1, FCE7B156ED663471CF9A736915F00302E93B50FC647563D235313A37FCE8F0F6 ] AudioSrv        C:\windows\System32\Audiosrv.dll

14:18:19.0323 0x204c  AudioSrv - ok

14:18:19.0350 0x204c  [ A6BF31A71B409DFA8CAC83159E1E2AFF, CBB83F73FFD3C3FB4F96605067739F8F7A4A40B2B05417FA49E575E95628753F ] AxInstSV        C:\windows\System32\AxInstSV.dll

14:18:19.0375 0x204c  AxInstSV - ok

14:18:19.0400 0x204c  [ 3E5B191307609F7514148C6832BB0842, DE011CB7AA4A2405FAF21575182E0793A1D83DFFC44E9A7864D59F3D51D8D580 ] b06bdrv         C:\windows\system32\drivers\bxvbda.sys

14:18:19.0442 0x204c  b06bdrv - ok

14:18:19.0455 0x204c  [ B5ACE6968304A3900EEB1EBFD9622DF2, 1DAA118D8CA3F97B34DF3D3CDA1C78EAB2ED225699FEABE89D331AE0CB7679FA ] b57nd60a        C:\windows\system32\DRIVERS\b57nd60a.sys

14:18:19.0499 0x204c  b57nd60a - ok

14:18:19.0517 0x204c  [ FDE360167101B4E45A96F939F388AEB0, 8D1457E866BBD645C4B9710DFBFF93405CC1193BF9AE42326F2382500B713B82 ] BDESVC          C:\windows\System32\bdesvc.dll

14:18:19.0558 0x204c  BDESVC - ok

14:18:19.0588 0x204c  [ 16A47CE2DECC9B099349A5F840654746, 77C008AEDB07FAC66413841D65C952DDB56FE7DCA5E9EF9C8F4130336B838024 ] Beep            C:\windows\system32\drivers\Beep.sys

14:18:19.0669 0x204c  Beep - ok

14:18:19.0737 0x204c  [ 82974D6A2FD19445CC5171FC378668A4, 075D25F47C0D2277E40AF8615571DAA5EB16B1824563632A9A7EC62505C29A4A ] BFE             C:\windows\System32\bfe.dll

14:18:19.0782 0x204c  BFE - ok

14:18:19.0818 0x204c  [ 1EA7969E3271CBC59E1730697DC74682, D511A34D63A6E0E6E7D1879068E2CD3D87ABEAF4936B2EA8CDDAD9F79D60FA04 ] BITS            C:\windows\System32\qmgr.dll

14:18:19.0875 0x204c  BITS - ok

14:18:19.0887 0x204c  [ 61583EE3C3A17003C4ACD0475646B4D3, 17E4BECC309C450E7E44F59A9C0BBC24D21BDC66DFBA65B8F198A00BB47A9811 ] blbdrive        C:\windows\system32\drivers\blbdrive.sys

14:18:19.0926 0x204c  blbdrive - ok

14:18:20.0085 0x204c  [ C620C59D46F43BEECC556F65E801312B, A42EB2894CF009AE5326A95821462157BEDABEB80B33E4E48DE0531D9FE3B76F ] Bluetooth Device Monitor C:\Program Files (x86)\Intel\Bluetooth\devmonsrv.exe

14:18:20.0123 0x204c  Bluetooth Device Monitor - detected UnsignedFile.Multi.Generic ( 1 )

14:18:23.0038 0x204c  Detect skipped due to KSN trusted

14:18:23.0039 0x204c  Bluetooth Device Monitor - ok

14:18:23.0199 0x204c  [ 5E5EDCCEEA4FA3FDF3A907AC204B5828, 4BB2F219E271A7E05828DEA1AF8AB3EE24B9D4149FD1DBA1DDF36EC749C2A298 ] Bluetooth Media Service C:\Program Files (x86)\Intel\Bluetooth\mediasrv.exe

14:18:23.0239 0x204c  Bluetooth Media Service - detected UnsignedFile.Multi.Generic ( 1 )

14:18:26.0415 0x204c  Detect skipped due to KSN trusted

14:18:26.0415 0x204c  Bluetooth Media Service - ok

14:18:26.0522 0x204c  [ 826E65C945738CBD64F89EAE4406687F, 78AA909C39F609CA8F50CECD6AA9C012FCEB747AB5AE0D0760D74A472F54F615 ] Bluetooth OBEX Service C:\Program Files (x86)\Intel\Bluetooth\obexsrv.exe

14:18:26.0572 0x204c  Bluetooth OBEX Service - detected UnsignedFile.Multi.Generic ( 1 )

14:18:30.0120 0x204c  Detect skipped due to KSN trusted

14:18:30.0121 0x204c  Bluetooth OBEX Service - ok

14:18:30.0147 0x204c  [ 6C02A83164F5CC0A262F4199F0871CF5, AD4632A6A203CB40970D848315D8ADB9C898349E20D8DF4107C2AE2703A2CF28 ] bowser          C:\windows\system32\DRIVERS\bowser.sys

14:18:30.0198 0x204c  bowser - ok

14:18:30.0205 0x204c  [ F09EEE9EDC320B5E1501F749FDE686C8, 66691114C42E12F4CC6DC4078D4D2FA4029759ACDAF1B59D17383487180E84E3 ] BrFiltLo        C:\windows\system32\drivers\BrFiltLo.sys

14:18:30.0258 0x204c  BrFiltLo - ok

14:18:30.0262 0x204c  [ B114D3098E9BDB8BEA8B053685831BE6, 0ED23C1897F35FA00B9C2848DE4ED200E18688AA7825674888054BBC3A3EB92C ] BrFiltUp        C:\windows\system32\drivers\BrFiltUp.sys

14:18:30.0279 0x204c  BrFiltUp - ok

14:18:30.0313 0x204c  [ 05F5A0D14A2EE1D8255C2AA0E9E8E694, 40011138869F5496A3E78D38C9900B466B6F3877526AC22952DCD528173F4645 ] Browser         C:\windows\System32\browser.dll

14:18:30.0370 0x204c  Browser - ok

14:18:30.0395 0x204c  [ 43BEA8D483BF1870F018E2D02E06A5BD, 4E6F5A5FD8C796A110B0DC9FF29E31EA78C04518FC1C840EF61BABD58AB10272 ] Brserid         C:\windows\System32\Drivers\Brserid.sys

14:18:30.0465 0x204c  Brserid - ok

14:18:30.0472 0x204c  [ A6ECA2151B08A09CACECA35C07F05B42, E2875BB7768ABAF38C3377007AA0A3C281503474D1831E396FB6599721586B0C ] BrSerWdm        C:\windows\System32\Drivers\BrSerWdm.sys

14:18:30.0493 0x204c  BrSerWdm - ok

14:18:30.0497 0x204c  [ B79968002C277E869CF38BD22CD61524, 50631836502237AF4893ECDCEA43B9031C3DE97433F594D46AF7C3C77F331983 ] BrUsbMdm        C:\windows\System32\Drivers\BrUsbMdm.sys

14:18:30.0556 0x204c  BrUsbMdm - ok

14:18:30.0561 0x204c  [ A87528880231C54E75EA7A44943B38BF, 4C8BBB29FDA76A96840AA47A8613C15D4466F9273A13941C19507008629709C9 ] BrUsbSer        C:\windows\System32\Drivers\BrUsbSer.sys

14:18:30.0613 0x204c  BrUsbSer - ok

14:18:30.0659 0x204c  [ CF98190A94F62E405C8CB255018B2315, E1B2540023C4FE9FD588E4B6AE6347DFA565EB3898F21E5360882BF3E8B5E781 ] BthEnum         C:\windows\system32\drivers\BthEnum.sys

14:18:30.0713 0x204c  BthEnum - ok

14:18:30.0720 0x204c  [ 9DA669F11D1F894AB4EB69BF546A42E8, B498B8B6CEF957B73179D1ADAF084BBB57BB3735D810F9BE2C7B1D58A4FD25A4 ] BTHMODEM        C:\windows\system32\drivers\bthmodem.sys

14:18:30.0742 0x204c  BTHMODEM - ok

14:18:30.0752 0x204c  [ 02DD601B708DD0667E1331FA8518E9FF, 7DE6CC4DBB621CD03B01D9CE6CF66EAFE31D39030A391562CD0E278E1D70ADE1 ] BthPan          C:\windows\system32\DRIVERS\bthpan.sys

14:18:30.0765 0x204c  BthPan - ok

14:18:30.0794 0x204c  [ 738D0E9272F59EB7A1449C3EC118E6C4, FE3D32C2A5E4DC21376A0F89C0B2EE024ECF1A3FB99213CC9BBC986ADF7AF080 ] BTHPORT         C:\windows\System32\Drivers\BTHport.sys

14:18:30.0827 0x204c  BTHPORT - ok

14:18:30.0851 0x204c  [ 95F9C2976059462CBBF227F7AAB10DE9, 2797AE919FF7606B070FB039CECDB0707CD2131DCAC09C5DF14F443D881C9F34 ] bthserv         C:\windows\system32\bthserv.dll

14:18:30.0909 0x204c  bthserv - ok

14:18:30.0927 0x204c  [ F188B7394D81010767B6DF3178519A37, 576304E92FD94908F093A6AB5F4D328F25829BE32EC3CA0D29EBFDF5DE83539B ] BTHUSB          C:\windows\System32\Drivers\BTHUSB.sys

14:18:30.0937 0x204c  BTHUSB - ok

14:18:30.0965 0x204c  [ 962BD3689E2C85F0BA97F3D7E7BA540B, F49642A334DB38DCCD8061463A11AC6988D563E124489DD9F36AEABA4B936A09 ] btmaux          C:\windows\system32\DRIVERS\btmaux.sys

14:18:30.0972 0x204c  btmaux - ok

14:18:30.0988 0x204c  [ EC1220B647F0D995DA5CAD4153454779, 6080DC5CC4652360C8A292F2C1AC79504045CD34A5280EC5EBD1B3122740448B ] btmhsf          C:\windows\system32\DRIVERS\btmhsf.sys

14:18:31.0031 0x204c  btmhsf - ok

14:18:31.0047 0x204c  [ B8BD2BB284668C84865658C77574381A, 6C55BA288B626DF172FDFEA0BD7027FAEBA1F44EF20AB55160D7C7DC6E717D65 ] cdfs            C:\windows\system32\DRIVERS\cdfs.sys

14:18:31.0098 0x204c  cdfs - ok

14:18:31.0125 0x204c  [ F036CE71586E93D94DAB220D7BDF4416, BD07AAD9E20CEAF9FC84E4977C55EA2C45604A2C682AC70B9B9A2199B6713D5B ] cdrom           C:\windows\system32\DRIVERS\cdrom.sys

14:18:31.0162 0x204c  cdrom - ok

14:18:31.0188 0x204c  [ F17D1D393BBC69C5322FBFAFACA28C7F, 62A1A92B3C52ADFD0B808D7F69DD50238B5F202421F1786F7EAEAA63F274B3E8 ] CertPropSvc     C:\windows\System32\certprop.dll

14:18:31.0258 0x204c  CertPropSvc - ok

14:18:31.0269 0x204c  [ D7CD5C4E1B71FA62050515314CFB52CF, 513B5A849899F379F0BC6AB3A8A05C3493C2393C95F036612B96EC6E252E1C64 ] circlass        C:\windows\system32\drivers\circlass.sys

14:18:31.0287 0x204c  circlass - ok

14:18:31.0307 0x204c  [ FE1EC06F2253F691FE36217C592A0206, B9F122DB5E665ECDF29A5CB8BB6B531236F31A54A95769D6C5C1924C87FE70CE ] CLFS            C:\windows\system32\CLFS.sys

14:18:31.0327 0x204c  CLFS - ok

14:18:31.0384 0x204c  [ D88040F816FDA31C3B466F0FA0918F29, 39D3630E623DA25B8444B6D3AAAB16B98E7E289C5619E19A85D47B74C71449F3 ] clr_optimization_v2.0.50727_32 C:\windows\Microsoft.NET\Framework\v2.0.50727\mscorsvw.exe

14:18:31.0411 0x204c  clr_optimization_v2.0.50727_32 - ok

14:18:31.0447 0x204c  [ D1CEEA2B47CB998321C579651CE3E4F8, 654013B8FD229A50017B08DEC6CA19C7DDA8CE0771260E057A92625201D539B1 ] clr_optimization_v2.0.50727_64 C:\windows\Microsoft.NET\Framework64\v2.0.50727\mscorsvw.exe

14:18:31.0463 0x204c  clr_optimization_v2.0.50727_64 - ok

14:18:31.0544 0x204c  [ E87213F37A13E2B54391E40934F071D0, 7EB221127EFB5BF158FB03D18EFDA2C55FB6CE3D1A1FE69C01D70DBED02C87E5 ] clr_optimization_v4.0.30319_32 C:\windows\Microsoft.NET\Framework\v4.0.30319\mscorsvw.exe

14:18:31.0576 0x204c  clr_optimization_v4.0.30319_32 - ok

14:18:31.0609 0x204c  [ 4AEDAB50F83580D0B4D6CF78191F92AA, D113C47013B018B45161911B96E93AF96A2F3B34FA47061BF6E7A71FBA03194A ] clr_optimization_v4.0.30319_64 C:\windows\Microsoft.NET\Framework64\v4.0.30319\mscorsvw.exe

14:18:31.0643 0x204c  clr_optimization_v4.0.30319_64 - ok

14:18:31.0652 0x204c  [ 0840155D0BDDF1190F84A663C284BD33, 696039FA63CFEB33487FAA8FD7BBDB220141E9C6E529355D768DFC87999A9C3A ] CmBatt          C:\windows\system32\drivers\CmBatt.sys

14:18:31.0686 0x204c  CmBatt - ok

14:18:31.0703 0x204c  [ E19D3F095812725D88F9001985B94EDD, 46243C5CCC4981CAC6FA6452FFCEC33329BF172448F1852D52592C9342E0E18B ] cmdide          C:\windows\system32\drivers\cmdide.sys

14:18:31.0721 0x204c  cmdide - ok

14:18:31.0760 0x204c  [ EBF28856F69CF094A902F884CF989706, AD6C9F0BC20AA49EEE5478DA0F856F0EA2B414B63208C5FFB03C9D7F5B59765F ] CNG             C:\windows\system32\Drivers\cng.sys

14:18:31.0806 0x204c  CNG - ok

14:18:31.0832 0x204c  [ 102DE219C3F61415F964C88E9085AD14, CD74CB703381F1382C32CF892FF2F908F4C9412E1BC77234F8FEA5D4666E1BF1 ] Compbatt        C:\windows\system32\drivers\compbatt.sys

14:18:31.0844 0x204c  Compbatt - ok

14:18:31.0856 0x204c  [ 03EDB043586CCEBA243D689BDDA370A8, 0E4523AA332E242D5C2C61C5717DBA5AB6E42DADB5A7E512505FC2B6CC224959 ] CompositeBus    C:\windows\system32\drivers\CompositeBus.sys

14:18:31.0885 0x204c  CompositeBus - ok

14:18:31.0889 0x204c  COMSysApp - ok

14:18:31.0902 0x204c  [ 1C827878A998C18847245FE1F34EE597, 41EF7443D8B2733AA35CAC64B4F5F74FAC8BB0DA7D3936B69EC38E2DC3972E60 ] crcdisk         C:\windows\system32\drivers\crcdisk.sys

14:18:31.0920 0x204c  crcdisk - ok

14:18:31.0964 0x204c  [ 6B400F211BEE880A37A1ED0368776BF4, 2F27C6FA96A1C8CBDA467846DA57E63949A7EA37DB094B13397DDD30114295BD ] CryptSvc        C:\windows\system32\cryptsvc.dll

14:18:32.0041 0x204c  CryptSvc - ok

14:18:32.0178 0x204c  [ FD557A50A65E44041CD2FCEF4BEB04DB, 746D5958F7198895D35A23566D3736D993D57726BF59D91421D8091C48926A26 ] cvhsvc          C:\Program Files (x86)\Common Files\Microsoft Shared\Virtualization Handler\CVHSVC.EXE

14:18:32.0199 0x204c  cvhsvc - ok

14:18:32.0229 0x204c  [ 5C627D1B1138676C0A7AB2C2C190D123, C5003F2C912C5CA990E634818D3B4FD72F871900AF2948BD6C4D6400B354B401 ] DcomLaunch      C:\windows\system32\rpcss.dll

14:18:32.0297 0x204c  DcomLaunch - ok

14:18:32.0324 0x204c  [ 3CEC7631A84943677AA8FA8EE5B6B43D, 32061DAC9ED6C1EBA3B367B18D0E965AEEC2DF635DCF794EC39D086D32503AC5 ] defragsvc       C:\windows\System32\defragsvc.dll

14:18:32.0372 0x204c  defragsvc - ok

14:18:32.0382 0x204c  [ 9BB2EF44EAA163B29C4A4587887A0FE4, 03667BC3EA5003F4236929C10F23D8F108AFCB29DB5559E751FB26DFB318636F ] DfsC            C:\windows\system32\Drivers\dfsc.sys

14:18:32.0415 0x204c  DfsC - ok

14:18:32.0445 0x204c  [ 43D808F5D9E1A18E5EEB5EBC83969E4E, C10D1155D71EABE4ED44C656A8F13078A8A4E850C4A8FBB92D52D173430972B8 ] Dhcp            C:\windows\system32\dhcpcore.dll

14:18:32.0493 0x204c  Dhcp - ok

14:18:32.0514 0x204c  [ 13096B05847EC78F0977F2C0F79E9AB3, 1E44981B684F3E56F5D2439BB7FA78BD1BC876BB2265AE089AEC68F241B05B26 ] discache        C:\windows\system32\drivers\discache.sys

14:18:32.0554 0x204c  discache - ok

14:18:32.0589 0x204c  [ 9819EEE8B5EA3784EC4AF3B137A5244C, 571BC886E87C888DA96282E381A746D273B58B9074E84D4CA91275E26056D427 ] Disk            C:\windows\system32\drivers\disk.sys

14:18:32.0598 0x204c  Disk - ok

14:18:32.0610 0x204c  [ 16835866AAA693C7D7FCEBA8FFF706E4, 15891558F7C1F2BB57A98769601D447ED0D952354A8BB347312D034DC03E0242 ] Dnscache        C:\windows\System32\dnsrslvr.dll

14:18:32.0648 0x204c  Dnscache - ok

14:18:32.0669 0x204c  [ B1FB3DDCA0FDF408750D5843591AFBC6, AB6AD9C5E7BA2E3646D0115B67C4800D1CB43B4B12716397657C7ADEEE807304 ] dot3svc         C:\windows\System32\dot3svc.dll

14:18:32.0711 0x204c  dot3svc - ok

14:18:32.0729 0x204c  [ B26F4F737E8F9DF4F31AF6CF31D05820, 394BBBED4EC7FAD4110F62A43BFE0801D4AC56FFAC6C741C69407B26402311C7 ] DPS             C:\windows\system32\dps.dll

14:18:32.0773 0x204c  DPS - ok

14:18:32.0825 0x204c  [ 9B19F34400D24DF84C858A421C205754, 967AF267B4124BADA8F507CEBF25F2192D146A4D63BE71B45BFC03C5DA7F21A7 ] drmkaud         C:\windows\system32\drivers\drmkaud.sys

14:18:32.0876 0x204c  drmkaud - ok

14:18:32.0965 0x204c  [ 88612F1CE3BF42256913BF6E61C70D52, 7CF190F83FA8F15C33008EB381D3E345CEF37CBC046227DED26B36799EF4D9A7 ] DXGKrnl         C:\windows\System32\drivers\dxgkrnl.sys

14:18:33.0008 0x204c  DXGKrnl - ok

14:18:33.0036 0x204c  [ E2DDA8726DA9CB5B2C4000C9018A9633, 0C967DBC3636A76A696997192A158AA92A1AF19F01E3C66D5BF91818A8FAEA76 ] EapHost         C:\windows\System32\eapsvc.dll

14:18:33.0079 0x204c  EapHost - ok

14:18:33.0178 0x204c  [ DC5D737F51BE844D8C82C695EB17372F, 6D4022D9A46EDE89CEF0FAEADCC94C903234DFC460C0180D24FF9E38E8853017 ] ebdrv           C:\windows\system32\drivers\evbda.sys

14:18:33.0266 0x204c  ebdrv - ok

14:18:33.0300 0x204c  [ 204F3F58212B3E422C90BD9691A2DF28, D748A8CEE4D59B4248C9B1ACA5155D0FF6635A29564B4391B7FAC6261F93FE99 ] EFS             C:\windows\System32\lsass.exe

14:18:33.0364 0x204c  EFS - ok

14:18:33.0476 0x204c  [ C4002B6B41975F057D98C439030CEA07, 3D2484FBB832EFB90504DD406ED1CF3065139B1FE1646471811F3A5679EF75F1 ] ehRecvr         C:\windows\ehome\ehRecvr.exe

14:18:33.0550 0x204c  ehRecvr - ok

14:18:33.0573 0x204c  [ 4705E8EF9934482C5BB488CE28AFC681, 359E9EC5693CE0BE89082E1D5D8F5C5439A5B985010FF0CB45C11E3CFE30637D ] ehSched         C:\windows\ehome\ehsched.exe

14:18:33.0599 0x204c  ehSched - ok

14:18:33.0635 0x204c  [ 0E5DA5369A0FCAEA12456DD852545184, 9A64AC5396F978C3B92794EDCE84DCA938E4662868250F8C18FA7C2C172233F8 ] elxstor         C:\windows\system32\drivers\elxstor.sys

14:18:33.0669 0x204c  elxstor - ok

14:18:33.0672 0x204c  [ 34A3C54752046E79A126E15C51DB409B, 7D5B5E150C7C73666F99CBAFF759029716C86F16B927E0078D77F8A696616D75 ] ErrDev          C:\windows\system32\drivers\errdev.sys

14:18:33.0695 0x204c  ErrDev - ok

14:18:33.0723 0x204c  [ 4166F82BE4D24938977DD1746BE9B8A0, 24121751B7306225AD1C808442D7B030DEF377E9316AA0A3C5C7460E87317881 ] EventSystem     C:\windows\system32\es.dll

14:18:33.0769 0x204c  EventSystem - ok

14:18:33.0780 0x204c  [ A510C654EC00C1E9BDD91EEB3A59823B, 76CD277730F7B08D375770CD373D786160F34D1481AF0536BA1A5D2727E255F5 ] exfat           C:\windows\system32\drivers\exfat.sys

14:18:33.0815 0x204c  exfat - ok

14:18:33.0836 0x204c  [ 0ADC83218B66A6DB380C330836F3E36D, 798D6F83B5DBCC1656595E0A96CF12087FCCBE19D1982890D0CE5F629B328B29 ] fastfat         C:\windows\system32\drivers\fastfat.sys

14:18:33.0881 0x204c  fastfat - ok

14:18:33.0950 0x204c  [ DBEFD454F8318A0EF691FDD2EAAB44EB, 7F52AE222FF28503B6FC4A5852BD0CAEAF187BE69AF4B577D3DE474C24366099 ] Fax             C:\windows\system32\fxssvc.exe

14:18:34.0001 0x204c  Fax - ok

14:18:34.0004 0x204c  [ D765D19CD8EF61F650C384F62FAC00AB, 9F0A483A043D3BA873232AD3BA5F7BF9173832550A27AF3E8BD433905BD2A0EE ] fdc             C:\windows\system32\drivers\fdc.sys

14:18:34.0026 0x204c  fdc - ok

14:18:34.0049 0x204c  [ 0438CAB2E03F4FB61455A7956026FE86, 6D4DDC2973DB25CE0C7646BC85EFBCC004EBE35EA683F62162AE317C6F1D8DFE ] fdPHost         C:\windows\system32\fdPHost.dll

14:18:34.0110 0x204c  fdPHost - ok

14:18:34.0122 0x204c  [ 802496CB59A30349F9A6DD22D6947644, 52D59D3D628D5661F83F090F33F744F6916E0CC1F76E5A33983E06EB66AE19F8 ] FDResPub        C:\windows\system32\fdrespub.dll

14:18:34.0151 0x204c  FDResPub - ok

14:18:34.0165 0x204c  [ 655661BE46B5F5F3FD454E2C3095B930, 549C8E2A2A37757E560D55FFA6BFDD838205F17E40561E67F0124C934272CD1A ] FileInfo        C:\windows\system32\drivers\fileinfo.sys

14:18:34.0174 0x204c  FileInfo - ok

14:18:34.0184 0x204c  [ 5F671AB5BC87EEA04EC38A6CD5962A47, 6B61D3363FF3F9C439BD51102C284972EAE96ACC0683B9DC7E12D25D0ADC51B6 ] Filetrace       C:\windows\system32\drivers\filetrace.sys

14:18:34.0223 0x204c  Filetrace - ok

14:18:34.0254 0x204c  [ ABEDFD48AC042C6AAAD32452E77217A1, BC45A1C36BDBC20EF4E7D3CFB5368912382D964CB34D050ED255F56307F4C910 ] FLEXnet Licensing Service C:\Program Files (x86)\Common Files\Macrovision Shared\FLEXnet Publisher\FNPLicensingService.exe

14:18:34.0286 0x204c  FLEXnet Licensing Service - ok

14:18:34.0290 0x204c  [ C172A0F53008EAEB8EA33FE10E177AF5, 9175A95B323696D1B35C9EFEB7790DD64E6EE0B7021E6C18E2F81009B169D77B ] flpydisk        C:\windows\system32\drivers\flpydisk.sys

14:18:34.0299 0x204c  flpydisk - ok

14:18:34.0320 0x204c  [ DA6B67270FD9DB3697B20FCE94950741, F621A4462C9F2904063578C427FAF22D7D66AE9967605C11C798099817CE5331 ] FltMgr          C:\windows\system32\drivers\fltmgr.sys

14:18:34.0333 0x204c  FltMgr - ok

14:18:34.0374 0x204c  [ C4C183E6551084039EC862DA1C945E3D, 0874A2ACDD24D64965AA9A76E9C818E216880AE4C9A2E07ED932EE404585CEE6 ] FontCache       C:\windows\system32\FntCache.dll

14:18:34.0436 0x204c  FontCache - ok

14:18:34.0474 0x204c  [ A8B7F3818AB65695E3A0BB3279F6DCE6, 89FCF10F599767E67A1E011753E34DA44EAA311F105DBF69549009ED932A60F0 ] FontCache3.0.0.0 C:\windows\Microsoft.Net\Framework64\v3.0\WPF\PresentationFontCache.exe

14:18:34.0481 0x204c  FontCache3.0.0.0 - ok

14:18:34.0488 0x204c  [ D43703496149971890703B4B1B723EAC, F06397B2EDCA61629249D2EF1CBB7827A8BEAB8488246BD85EF6AE1363C0DA6E ] FsDepends       C:\windows\system32\drivers\FsDepends.sys

14:18:34.0497 0x204c  FsDepends - ok

14:18:34.0516 0x204c  [ 6BD9295CC032DD3077C671FCCF579A7B, 83622FBB0CB923798E7E584BF53CAAF75B8C016E3FF7F0FA35880FF34D1DFE33 ] Fs_Rec          C:\windows\system32\drivers\Fs_Rec.sys

14:18:34.0523 0x204c  Fs_Rec - ok

14:18:34.0561 0x204c  [ 8F6322049018354F45F05A2FD2D4E5E0, 73BF0FB4EBD7887E992DDEBB79E906958D6678F8D1107E8C368F5A0514D80359 ] fvevol          C:\windows\system32\DRIVERS\fvevol.sys

14:18:34.0575 0x204c  fvevol - ok

14:18:34.0590 0x204c  [ 8C778D335C9D272CFD3298AB02ABE3B6, 85F0B13926B0F693FA9E70AA58DE47100E4B6F893772EBE4300C37D9A36E6005 ] gagp30kx        C:\windows\system32\drivers\gagp30kx.sys

14:18:34.0598 0x204c  gagp30kx - ok

14:18:34.0630 0x204c  [ 277BBC7E1AA1EE957F573A10ECA7EF3A, 2EE60B924E583E847CC24E78B401EF95C69DB777A5B74E1EC963E18D47B94D24 ] gpsvc           C:\windows\System32\gpsvc.dll

14:18:34.0676 0x204c  gpsvc - ok

14:18:34.0775 0x204c  [ 506708142BC63DABA64F2D3AD1DCD5BF, 9C36A08D9E7932FF4DA7B5F24E6B42C92F28685B8ABE964C870E8D7670FD531A ] gupdate         C:\Program Files (x86)\Google\Update\GoogleUpdate.exe

14:18:34.0797 0x204c  gupdate - ok

14:18:34.0804 0x204c  [ 506708142BC63DABA64F2D3AD1DCD5BF, 9C36A08D9E7932FF4DA7B5F24E6B42C92F28685B8ABE964C870E8D7670FD531A ] gupdatem        C:\Program Files (x86)\Google\Update\GoogleUpdate.exe

14:18:34.0819 0x204c  gupdatem - ok

14:18:34.0877 0x204c  [ 5D4BC124FAAE6730AC002CDB67BF1A1C, 00294F4DC7D17F6DD2A22B9C3299BED40146BA45C972367154D20DB502472551 ] gusvc           C:\Program Files (x86)\Google\Common\Google Updater\GoogleUpdaterService.exe

14:18:34.0918 0x204c  gusvc - ok

14:18:34.0933 0x204c  [ F2523EF6460FC42405B12248338AB2F0, B2F3DE8DE1F512D871BC2BC2E8D0E33AB03335BFBC07627C5F88B65024928E19 ] hcw85cir        C:\windows\system32\drivers\hcw85cir.sys

14:18:34.0969 0x204c  hcw85cir - ok

14:18:34.0992 0x204c  [ 975761C778E33CD22498059B91E7373A, 8304E15FBE6876BE57263A03621365DA8C88005EAC532A770303C06799D915D9 ] HdAudAddService C:\windows\system32\drivers\HdAudio.sys

14:18:35.0034 0x204c  HdAudAddService - ok

14:18:35.0056 0x204c  [ 97BFED39B6B79EB12CDDBFEED51F56BB, 3CF981D668FB2381E52AF2E51E296C6CFB47B0D62249645278479D0111A47955 ] HDAudBus        C:\windows\system32\drivers\HDAudBus.sys

14:18:35.0088 0x204c  HDAudBus - ok

14:18:35.0121 0x204c  [ 78E86380454A7B10A5EB255DC44A355F, 11F3ED7ACFFA3024B9BD504F81AC39F5B4CED5A8A425E8BADF7132EFEDB9BD64 ] HidBatt         C:\windows\system32\drivers\HidBatt.sys

14:18:35.0203 0x204c  HidBatt - ok

14:18:35.0211 0x204c  [ 7FD2A313F7AFE5C4DAB14798C48DD104, 94CBFD4506CBDE4162CEB3367BAB042D19ACA6785954DC0B554D4164B9FCD0D4 ] HidBth          C:\windows\system32\drivers\hidbth.sys

14:18:35.0235 0x204c  HidBth - ok

14:18:35.0238 0x204c  [ 0A77D29F311B88CFAE3B13F9C1A73825, 8615DC6CEFB591505CE16E054A71A4F371B827DDFD5E980777AB4233DCFDA01D ] HidIr           C:\windows\system32\drivers\hidir.sys

14:18:35.0250 0x204c  HidIr - ok

14:18:35.0297 0x204c  [ 949900BBF7015CCD877D20DB6C2628BE, 7D39DFF56FD17A3054324F2BC260F72DC8C3AD5063AA5056A2FCA52F3AAF880E ] hidkmdf         C:\windows\system32\DRIVERS\hidkmdf.sys

14:18:35.0316 0x204c  hidkmdf - ok

14:18:35.0340 0x204c  [ BD9EB3958F213F96B97B1D897DEE006D, 4D01CBF898B528B3A4E5A683DF2177300AFABD7D4CB51F1A7891B1B545499631 ] hidserv         C:\windows\system32\hidserv.dll

14:18:35.0394 0x204c  hidserv - ok

14:18:35.0427 0x204c  [ 9592090A7E2B61CD582B612B6DF70536, FD11D5E02C32D658B28FCC35688AB66CCB5D3A0A0D74C82AE0F0B6C67B568A0F ] HidUsb          C:\windows\system32\DRIVERS\hidusb.sys

14:18:35.0449 0x204c  HidUsb - ok

14:18:35.0472 0x204c  [ 387E72E739E15E3D37907A86D9FF98E2, 9935BE2E58788E79328293AF2F202CB0F6042441B176F75ACC5AEA93C8E05531 ] hkmsvc          C:\windows\system32\kmsvc.dll

14:18:35.0543 0x204c  hkmsvc - ok

14:18:35.0569 0x204c  [ EFDFB3DD38A4376F93E7985173813ABD, 70402FA73A5A2A8BB557AAC8F531E373077D28DE5F40A1F3F14B940BE01CD2E1 ] HomeGroupListener C:\windows\system32\ListSvc.dll

14:18:35.0610 0x204c  HomeGroupListener - ok

14:18:35.0630 0x204c  [ 908ACB1F594274965A53926B10C81E89, 7D34A742AC486294D82676F8465A3EF26C8AC3317C32B63F62031CB007CFC208 ] HomeGroupProvider C:\windows\system32\provsvc.dll

14:18:35.0651 0x204c  HomeGroupProvider - ok

14:18:35.0661 0x204c  [ 39D2ABCD392F3D8A6DCE7B60AE7B8EFC, E9E6A1665740CFBC2DD321010007EF42ABA2102AEB9772EE8AA3354664B1E205 ] HpSAMD          C:\windows\system32\drivers\HpSAMD.sys

14:18:35.0670 0x204c  HpSAMD - ok

14:18:35.0703 0x204c  [ 0EA7DE1ACB728DD5A369FD742D6EEE28, 21C489412EB33A12B22290EB701C19BA57006E8702E76F730954F0784DDE9779 ] HTTP            C:\windows\system32\drivers\HTTP.sys

14:18:35.0763 0x204c  HTTP - ok

14:18:35.0779 0x204c  [ A5462BD6884960C9DC85ED49D34FF392, 53E65841AF5B06A2844D0BB6FC4DD3923A323FFA0E4BFC89B3B5CAFB592A3D53 ] hwpolicy        C:\windows\system32\drivers\hwpolicy.sys

14:18:35.0786 0x204c  hwpolicy - ok

14:18:35.0808 0x204c  [ FA55C73D4AFFA7EE23AC4BE53B4592D3, 65CDDC62B89A60E942C5642C9D8B539EFB69DA8069B4A2E54978154B314531CD ] i8042prt        C:\windows\system32\drivers\i8042prt.sys

14:18:35.0820 0x204c  i8042prt - ok

14:18:35.0840 0x204c  [ D469B77687E12FE43E344806740B624D, DFDD486FD040813BF4E5DDB504CF9E0BFBF6D4E540DDDA4829F9B675ACF63E89 ] iaStor          C:\windows\system32\drivers\iaStor.sys

14:18:35.0856 0x204c  iaStor - ok

14:18:35.0898 0x204c  [ 983FC69644DDF0486C8DFEA262948D1A, 329EC95117C31E61F6D22D79CFF339D70A70522710E7DC0CED06EC95E6D4B34F ] IAStorDataMgrSvc C:\Program Files (x86)\Intel\Intel® Rapid Storage Technology\IAStorDataMgrSvc.exe

14:18:35.0920 0x204c  IAStorDataMgrSvc - ok

14:18:35.0946 0x204c  [ AAAF44DB3BD0B9D1FB6969B23ECC8366, 805AA4A9464002D1AB3832E4106B2AAA1331F4281367E75956062AAE99699385 ] iaStorV         C:\windows\system32\drivers\iaStorV.sys

14:18:35.0961 0x204c  iaStorV - ok

14:18:35.0975 0x204c  [ E44F0B4DC753C14930B8DC48BB7A1644, F2094F8A0D4220F829E186BDEDC559D7125634C1938C6E2CFA7E2B91E41C7C72 ] iBtFltCoex      C:\windows\system32\DRIVERS\iBtFltCoex.sys

14:18:35.0985 0x204c  iBtFltCoex - ok

14:18:36.0059 0x204c  [ 5988FC40F8DB5B0739CD1E3A5D0D78BD, 2B9512324DBA4A97F6AC34E8067EE08E3B6874CD60F6CB4209AFC22A34D2BE99 ] idsvc           C:\windows\Microsoft.NET\Framework64\v3.0\Windows Communication Foundation\infocard.exe

14:18:36.0101 0x204c  idsvc - ok

14:18:36.0118 0x204c  IEEtwCollectorService - ok

14:18:36.0133 0x204c  [ 5C18831C61933628F5BB0EA2675B9D21, 5CD9DE2F8C0256623A417B5C55BF55BB2562BD7AB2C3C83BB3D9886C2FBDA4E4 ] iirsp           C:\windows\system32\drivers\iirsp.sys

14:18:36.0144 0x204c  iirsp - ok

14:18:36.0202 0x204c  [ 344789398EC3EE5A4E00C52B31847946, 3DA5F08E4B46F4E63456AA588D49E39A6A09A97D0509880C00F327623DB6122D ] IKEEXT          C:\windows\System32\ikeext.dll

14:18:36.0243 0x204c  IKEEXT - ok

14:18:36.0367 0x204c  [ 1B491F385EE96F9D9EE4CB430C8CD29E, 06CA97FC494F3B3FE422F1242856B643EE210959DCB6E8298254306145B688AF ] IntcAzAudAddService C:\windows\system32\drivers\RTKVHD64.sys

14:18:36.0449 0x204c  IntcAzAudAddService - ok

14:18:36.0488 0x204c  [ F00F20E70C6EC3AA366910083A0518AA, E2F3E9FFD82C802C8BAC309893A3664ACF16A279959C0FDECCA64C3D3C60FD22 ] intelide        C:\windows\system32\drivers\intelide.sys

14:18:36.0499 0x204c  intelide - ok

14:18:36.0532 0x204c  [ ADA036632C664CAA754079041CF1F8C1, F2386CC09AC6DE4C54189154F7D91C1DB7AA120B13FAE8BA5B579ACF99FCC610 ] intelppm        C:\windows\system32\DRIVERS\intelppm.sys

14:18:36.0567 0x204c  intelppm - ok

14:18:36.0602 0x204c  [ 098A91C54546A3B878DAD6A7E90A455B, 044CCE2A0DF56EBE1EFD99B4F6F0A5B9EE12498CA358CF4B2E3A1CFD872823AA ] IPBusEnum       C:\windows\system32\ipbusenum.dll

14:18:36.0654 0x204c  IPBusEnum - ok

14:18:36.0679 0x204c  [ C9F0E1BD74365A8771590E9008D22AB6, 728BC5A6AAE499FDC50EB01577AF16D83C2A9F3B09936DD2A89C01E074BA8E51 ] IpFilterDriver  C:\windows\system32\DRIVERS\ipfltdrv.sys

14:18:36.0704 0x204c  IpFilterDriver - ok

14:18:36.0770 0x204c  [ 08C2957BB30058E663720C5606885653, E13EDF6701512E2A9977A531454932CA5023087CB50E1D2F416B8BCDD92B67BE ] iphlpsvc        C:\windows\System32\iphlpsvc.dll

14:18:36.0823 0x204c  iphlpsvc - ok

14:18:36.0826 0x204c  [ 0FC1AEA580957AA8817B8F305D18CA3A, 7161E4DE91AAFC3FA8BF24FAE4636390C2627DB931505247C0D52C75A31473D9 ] IPMIDRV         C:\windows\system32\drivers\IPMIDrv.sys

14:18:36.0836 0x204c  IPMIDRV - ok

14:18:36.0840 0x204c  [ AF9B39A7E7B6CAA203B3862582E9F2D0, 67128BE7EADBE6BD0205B050F96E268948E8660C4BAB259FB0BE03935153D04E ] IPNAT           C:\windows\system32\drivers\ipnat.sys

14:18:36.0872 0x204c  IPNAT - ok

14:18:36.0880 0x204c  [ 3ABF5E7213EB28966D55D58B515D5CE9, A352BCC5B6B9A28805B15CAFB235676F1FAFF0D2394F88C03089EB157D6188AE ] IRENUM          C:\windows\system32\drivers\irenum.sys

14:18:36.0893 0x204c  IRENUM - ok

14:18:36.0895 0x204c  [ 2F7B28DC3E1183E5EB418DF55C204F38, D40410A760965925D6F10959B2043F7BD4F68EAFCF5E743AF11AD860BD136548 ] isapnp          C:\windows\system32\drivers\isapnp.sys

14:18:36.0903 0x204c  isapnp - ok

14:18:36.0950 0x204c  [ 96BB922A0981BC7432C8CF52B5410FE6, 236C05509B1040059B15021CBBDBDAF3B9C0F00910142BE5887B2C7561BAAFBA ] iScsiPrt        C:\windows\system32\drivers\msiscsi.sys

14:18:36.0983 0x204c  iScsiPrt - ok

14:18:37.0025 0x204c  [ F415A88162D23977B5EDAE4F0410E903, B86FD88B4285ED96BFDB9430E4DB134AC1B09DBB541929C4D6C1EEAF792D444D ] IviRegMgr       C:\Program Files (x86)\Common Files\InterVideo\RegMgr\iviRegMgr.exe

14:18:37.0034 0x204c  IviRegMgr - ok

14:18:37.0041 0x204c  [ BC02336F1CBA7DCC7D1213BB588A68A5, 450C5BAD54CCE2AFCDFF1B6E7F8E1A8446D9D3255DF9D36C29A8F848048AAD93 ] kbdclass        C:\windows\system32\DRIVERS\kbdclass.sys

14:18:37.0049 0x204c  kbdclass - ok

14:18:37.0067 0x204c  [ 0705EFF5B42A9DB58548EEC3B26BB484, 86C6824ED7ED6FA8F306DB6319A0FD688AA91295AE571262F9D8E96A32225E99 ] kbdhid          C:\windows\system32\DRIVERS\kbdhid.sys

14:18:37.0088 0x204c  kbdhid - ok

14:18:37.0099 0x204c  [ 204F3F58212B3E422C90BD9691A2DF28, D748A8CEE4D59B4248C9B1ACA5155D0FF6635A29564B4391B7FAC6261F93FE99 ] KeyIso          C:\windows\system32\lsass.exe

14:18:37.0108 0x204c  KeyIso - ok

14:18:37.0184 0x204c  [ 372DF3081424F493D47A1A4C067642C9, 7D1E2800FCD76CCE1BD1230228676824D40E7D1228439725ACBADCC2515D2C97 ] KodakSvc        C:\Program Files (x86)\Kodak\printer\center\KodakSvc.exe

14:18:37.0192 0x204c  KodakSvc - detected UnsignedFile.Multi.Generic ( 1 )

14:18:40.0284 0x204c  Detect skipped due to KSN trusted

14:18:40.0285 0x204c  KodakSvc - ok

14:18:40.0330 0x204c  [ 353009DEDF918B2A51414F330CF72DEC, BF157D6E329F26E02FA16271B751B421396040DBB1D7BF9B2E0A21BC569672E2 ] KSecDD          C:\windows\system32\Drivers\ksecdd.sys

14:18:40.0362 0x204c  KSecDD - ok

14:18:40.0382 0x204c  [ 1C2D8E18AA8FD50CD04C15CC27F7F5AB, 4BA3B0F9F01BD47D66091D3AD86B69A523981D61DFB4D677F2CD39405B2DA989 ] KSecPkg         C:\windows\system32\Drivers\ksecpkg.sys

14:18:40.0399 0x204c  KSecPkg - ok

14:18:40.0410 0x204c  [ 6869281E78CB31A43E969F06B57347C4, 866A23E69B32A78D378D6CB3B3DA3695FFDFF0FEC3C9F68C8C3F988DF417044B ] ksthunk         C:\windows\system32\drivers\ksthunk.sys

14:18:40.0435 0x204c  ksthunk - ok

14:18:40.0459 0x204c  [ 6AB66E16AA859232F64DEB66887A8C9C, 5F2B579BEA8098A2994B0DECECDAE7B396E7B5DC5F09645737B9F28BEEA77FFF ] KtmRm           C:\windows\system32\msdtckrm.dll

14:18:40.0509 0x204c  KtmRm - ok

14:18:40.0570 0x204c  [ D9F42719019740BAA6D1C6D536CBDAA6, 8757599D0AE5302C4CE50861BEBA3A8DD14D7B0DBD916FD5404133688CDFCC40 ] LanmanServer    C:\windows\system32\srvsvc.dll

14:18:40.0644 0x204c  LanmanServer - ok

14:18:40.0671 0x204c  [ 851A1382EED3E3A7476DB004F4EE3E1A, B1C67F47DD594D092E6E258F01DF5E7150227CE3131A908A244DEE9F8A1FABF9 ] LanmanWorkstation C:\windows\System32\wkssvc.dll

14:18:40.0713 0x204c  LanmanWorkstation - ok

14:18:40.0740 0x204c  [ 1538831CF8AD2979A04C423779465827, E1729B0CC4CEEE494A0B8817A8E98FF232E3A32FB023566EF0BC71A090262C0C ] lltdio          C:\windows\system32\DRIVERS\lltdio.sys

14:18:40.0774 0x204c  lltdio - ok

14:18:40.0797 0x204c  [ C1185803384AB3FEED115F79F109427F, 0414FE73532DCAB17E906438A14711E928CECCD5F579255410C62984DD652700 ] lltdsvc         C:\windows\System32\lltdsvc.dll

14:18:40.0845 0x204c  lltdsvc - ok

14:18:40.0859 0x204c  [ F993A32249B66C9D622EA5592A8B76B8, EE64672A990C6145DC5601E2B8CDBE089272A72732F59AF9865DCBA8B1717E70 ] lmhosts         C:\windows\System32\lmhsvc.dll

14:18:40.0891 0x204c  lmhosts - ok

14:18:40.0917 0x204c  [ 1A93E54EB0ECE102495A51266DCDB6A6, DB6AA86AA36C3A7988BE96E87B5D3251BE7617C54EE8F894D9DC2E267FE3255B ] LSI_FC          C:\windows\system32\drivers\lsi_fc.sys

14:18:40.0936 0x204c  LSI_FC - ok

14:18:40.0940 0x204c  [ 1047184A9FDC8BDBFF857175875EE810, F2251EDB7736A26D388A0C5CC2FE5FB9C5E109CBB1E3800993554CB21D81AE4B ] LSI_SAS         C:\windows\system32\drivers\lsi_sas.sys

14:18:40.0950 0x204c  LSI_SAS - ok

14:18:40.0953 0x204c  [ 30F5C0DE1EE8B5BC9306C1F0E4A75F93, 88D5740A4E9CC3FA80FA18035DAB441BDC5A039622D666BFDAA525CC9686BD06 ] LSI_SAS2        C:\windows\system32\drivers\lsi_sas2.sys

14:18:40.0961 0x204c  LSI_SAS2 - ok

14:18:40.0966 0x204c  [ 0504EACAFF0D3C8AED161C4B0D369D4A, 4D272237C189646F5C80822FD3CBA7C2728E482E2DAAF7A09C8AEF811C89C54D ] LSI_SCSI        C:\windows\system32\drivers\lsi_scsi.sys

14:18:40.0976 0x204c  LSI_SCSI - ok

14:18:40.0990 0x204c  [ 43D0F98E1D56CCDDB0D5254CFF7B356E, 5BA498183B5C4996C694CB0A9A6B66CE6C7A460F6C91BEB9F305486FCC3B7B22 ] luafv           C:\windows\system32\drivers\luafv.sys

14:18:41.0017 0x204c  luafv - ok

14:18:41.0107 0x204c  [ F92B0E478C0FAA6D6661E6E977247E60, 8B26B57C2C60C98CD6273ACA126B2CD0356ADB13A59FEC12882357A6B973123C ] MBAMProtector   C:\windows\system32\drivers\mbam.sys

14:18:41.0118 0x204c  MBAMProtector - ok

14:18:41.0249 0x204c  [ D84AEA3F3329D622DFC1297DDDF6163B, 316FE56CC30ED1473A917253F46B79EAA12F4ABD5B4B1ADB03929DFEE940F577 ] MBAMScheduler   C:\Program Files (x86)\Malwarebytes Anti-Malware\mbamscheduler.exe

14:18:41.0312 0x204c  MBAMScheduler - ok

14:18:41.0360 0x204c  [ 4F45ED469906494F9BF754E476390DBD, D8FF6AFD73D8C191F5732DF9737E6F83B2B52B06A3A6CD4CC6EAC9464CBB2772 ] MBAMService     C:\Program Files (x86)\Malwarebytes Anti-Malware\mbamservice.exe

14:18:41.0397 0x204c  MBAMService - ok

14:18:41.0445 0x204c  [ 8A50D5304E6AE48664CF5838EC32F647, C76943FABEE1B5E1B641AA610668CCD4227E2C4B191DD30B79D3AB31A9E8B5BE ] MBAMSwissArmy   C:\windows\system32\drivers\MBAMSwissArmy.sys

14:18:41.0453 0x204c  MBAMSwissArmy - ok

14:18:41.0473 0x204c  [ 15E8ABC06843672955CE26A009533BAD, E7221B7DE9DB45447C68E79C6BFD064713C5974F7E79925BD7DEEF71F73F3E83 ] MBAMWebAccessControl C:\windows\system32\drivers\mwac.sys

14:18:41.0480 0x204c  MBAMWebAccessControl - ok

14:18:41.0507 0x204c  [ 8FF2D95CBA49B405C5DE27039FF0BF35, 03BF7FC7F1C2C76EDB583BA342EA1C325DB8058517744EF2A78529D3938F4DC1 ] MBfilt          C:\windows\system32\drivers\MBfilt64.sys

14:18:41.0538 0x204c  MBfilt - ok

14:18:41.0564 0x204c  [ 0BE09CD858ABF9DF6ED259D57A1A1663, 2FD28889B93C8E801F74C1D0769673A461671E0189D0A22C94509E3F0EEB7428 ] Mcx2Svc         C:\windows\system32\Mcx2Svc.dll

14:18:41.0596 0x204c  Mcx2Svc - ok

14:18:41.0601 0x204c  [ A55805F747C6EDB6A9080D7C633BD0F4, 2DA0E83BF3C8ADEF6F551B6CC1C0A3F6149CDBE6EC60413BA1767C4DE425A728 ] megasas         C:\windows\system32\drivers\megasas.sys

14:18:41.0614 0x204c  megasas - ok

14:18:41.0641 0x204c  [ BAF74CE0072480C3B6B7C13B2A94D6B3, 85CBB4949C090A904464F79713A3418338753D20D7FB811E68F287FDAC1DD834 ] MegaSR          C:\windows\system32\drivers\MegaSR.sys

14:18:41.0661 0x204c  MegaSR - ok

14:18:41.0677 0x204c  [ A6518DCC42F7A6E999BB3BEA8FD87567, 8A9AE992F93F37E0723761EA271A7E1AA8172702C471041A17324474FC96B9BC ] MEIx64          C:\windows\system32\drivers\HECIx64.sys

14:18:41.0691 0x204c  MEIx64 - ok

14:18:41.0727 0x204c  MGHwCtrl - ok

14:18:41.0810 0x204c  [ 71C6748EE8DE938532057EF10B4B7E44, 455175332156939B3CDA4511A2A6C213ABBFDB85EEECA98B6AB014C994F532C4 ] Micro Star SCM  C:\windows\SysWOW64\MSIService.exe

14:18:41.0845 0x204c  Micro Star SCM - detected UnsignedFile.Multi.Generic ( 1 )

14:18:44.0766 0x204c  Detect skipped due to KSN trusted

14:18:44.0766 0x204c  Micro Star SCM - ok

14:18:44.0825 0x204c  [ E40E80D0304A73E8D269F7141D77250B, 0DB4AC13A264F19A84DC0BCED54E8E404014CC09C993B172002B1561EC7E265A ] MMCSS           C:\windows\system32\mmcss.dll

14:18:44.0905 0x204c  MMCSS - ok

14:18:44.0962 0x204c  [ 800BA92F7010378B09F9ED9270F07137, 94F9AF9E1BE80AE6AC39A2A74EF9FAB115DCAACC011D07DFA8D6A1DDC8A93342 ] Modem           C:\windows\system32\drivers\modem.sys

14:18:45.0032 0x204c  Modem - ok

14:18:45.0073 0x204c  [ B03D591DC7DA45ECE20B3B467E6AADAA, 701FB0CAD8138C58507BE28845D3E24CE269A040737C29885944A0D851238732 ] monitor         C:\windows\system32\DRIVERS\monitor.sys

14:18:45.0103 0x204c  monitor - ok

14:18:45.0134 0x204c  [ 7D27EA49F3C1F687D357E77A470AEA99, 7FE7CAF95959F127C6D932C01D539C06D80273C49A09761F6E8331C05B1A7EE7 ] mouclass        C:\windows\system32\DRIVERS\mouclass.sys

14:18:45.0155 0x204c  mouclass - ok

14:18:45.0195 0x204c  [ D3BF052C40B0C4166D9FD86A4288C1E6, 5E65264354CD94E844BF1838CA1B8E49080EFA34605A32CF2F6A47A2B97FC183 ] mouhid          C:\windows\system32\DRIVERS\mouhid.sys

14:18:45.0238 0x204c  mouhid - ok

14:18:45.0270 0x204c  [ 32E7A3D591D671A6DF2DB515A5CBE0FA, 47CED0B9067AE8BF5EEF60B17ADEE5906BEDCC56E4CB460B7BFBC12BB9A69E63 ] mountmgr        C:\windows\system32\drivers\mountmgr.sys

14:18:45.0290 0x204c  mountmgr - ok

14:18:45.0345 0x204c  [ 9EB89625A82AC961F25E7C865947BF9A, 91DB9530CDE883DC60BE621AC4210ACD069631D9466E37411D9D6AEE587098D9 ] MpFilter        C:\windows\system32\DRIVERS\MpFilter.sys

14:18:45.0370 0x204c  MpFilter - ok

14:18:45.0390 0x204c  [ A44B420D30BD56E145D6A2BC8768EC58, B1E4DCA5A1008FA7A0492DC091FB2B820406AE13FD3D44F124E89B1037AF09B8 ] mpio            C:\windows\system32\drivers\mpio.sys

14:18:45.0405 0x204c  mpio - ok

14:18:45.0421 0x204c  [ 6C38C9E45AE0EA2FA5E551F2ED5E978F, 5A3FA2F110029CB4CC4384998EDB59203FDD65EC45E01B897FB684F8956EAD20 ] mpsdrv          C:\windows\system32\drivers\mpsdrv.sys

14:18:45.0447 0x204c  mpsdrv - ok

14:18:45.0482 0x204c  [ 54FFC9C8898113ACE189D4AA7199D2C1, 65F585C87F3F710FD5793FDFA96B740AD8D4317B0C120F4435CCF777300EA4F2 ] MpsSvc          C:\windows\system32\mpssvc.dll

14:18:45.0541 0x204c  MpsSvc - ok

14:18:45.0582 0x204c  [ 9BD4DCB5412921864A7AACDEDFBD1923, 46DEE9B9414D26203B62F0D6CAEBF37A3CEFD118556129547B2C5FC7B6FDBA05 ] MREMP50         C:\PROGRA~2\COMMON~1\Motive\MREMP50.SYS

14:18:45.0599 0x204c  MREMP50 - detected UnsignedFile.Multi.Generic ( 1 )

14:18:48.0752 0x204c  Detect skipped due to KSN trusted

14:18:48.0752 0x204c  MREMP50 - ok

14:18:48.0894 0x204c  [ C2758DF79C83A0D12A5599A040CA1818, 236641D2AD596CDC53AE8407F7A7AA02719764CCC7E6D5C547F41FE7C1D67BB5 ] MREMP50a64      C:\PROGRA~1\COMMON~1\Motive\MREMP50a64.SYS

14:18:48.0918 0x204c  MREMP50a64 - ok

14:18:48.0921 0x204c  MREMPR5 - ok

14:18:48.0924 0x204c  MRENDIS5 - ok

14:18:48.0938 0x204c  [ 07C02C892E8E1A72D6BF35004F0E9C5E, 09ECD59AADF08E2AA0C1BAF5D3D7CBB0948153E531E1F82ECACD43F14F88106B ] MRESP50         C:\PROGRA~2\COMMON~1\Motive\MRESP50.SYS

14:18:48.0958 0x204c  MRESP50 - detected UnsignedFile.Multi.Generic ( 1 )

14:18:52.0035 0x204c  Detect skipped due to KSN trusted

14:18:52.0035 0x204c  MRESP50 - ok

14:18:52.0100 0x204c  [ 38BD5B32E0722752BE8465D2A6DA43D9, EE009F141D77A858C84B4294F4FF51ECA400D48B3AD735FAC99EEF4E3E00E9EE ] MRESP50a64      C:\PROGRA~1\COMMON~1\Motive\MRESP50a64.SYS

14:18:52.0118 0x204c  MRESP50a64 - ok

14:18:52.0193 0x204c  [ 1A4F75E63C9FB84B85DFFC6B63FD5404, 01AFA6DBB4CDE55FE4EA05BBE8F753A4266F8D072EA1EE01DB79F5126780C21F ] MRxDAV          C:\windows\system32\drivers\mrxdav.sys

14:18:52.0232 0x204c  MRxDAV - ok

14:18:52.0268 0x204c  [ A5D9106A73DC88564C825D317CAC68AC, 0457B2AEA4E05A91D0E43F317894A614434D8CEBE35020785387F307E231FBE4 ] mrxsmb          C:\windows\system32\DRIVERS\mrxsmb.sys

14:18:52.0321 0x204c  mrxsmb - ok

14:18:52.0341 0x204c  [ D711B3C1D5F42C0C2415687BE09FC163, 9B3013AC60BD2D0FF52086658BA5FF486ADE15954A552D7DD590580E8BAE3EFF ] mrxsmb10        C:\windows\system32\DRIVERS\mrxsmb10.sys

14:18:52.0365 0x204c  mrxsmb10 - ok

14:18:52.0397 0x204c  [ 9423E9D355C8D303E76B8CFBD8A5C30C, 220B33F120C2DD937FE4D5664F4B581DC0ACF78D62EB56B7720888F67B9644CC ] mrxsmb20        C:\windows\system32\DRIVERS\mrxsmb20.sys

14:18:52.0439 0x204c  mrxsmb20 - ok

14:18:52.0457 0x204c  [ C25F0BAFA182CBCA2DD3C851C2E75796, 643E158A0948DF331807AEAA391F23960362E46C0A0CF6D22A99020EAE7B10F8 ] msahci          C:\windows\system32\drivers\msahci.sys

14:18:52.0477 0x204c  msahci - ok

14:18:52.0507 0x204c  [ DB801A638D011B9633829EB6F663C900, B34FD33A215ACCF2905F4B7D061686CDB1CB9C652147AF56AE14686C1F6E3C74 ] msdsm           C:\windows\system32\drivers\msdsm.sys

14:18:52.0520 0x204c  msdsm - ok

14:18:52.0535 0x204c  [ DE0ECE52236CFA3ED2DBFC03F28253A8, 2FBBEC4CACB5161F68D7C2935852A5888945CA0F107CF8A1C01F4528CE407DE3 ] MSDTC           C:\windows\System32\msdtc.exe

14:18:52.0563 0x204c  MSDTC - ok

14:18:52.0591 0x204c  [ AA3FB40E17CE1388FA1BEDAB50EA8F96, 69F93E15536644C8FD679A20190CFE577F4985D3B1B4A4AA250A168615AE1E99 ] Msfs            C:\windows\system32\drivers\Msfs.sys

14:18:52.0620 0x204c  Msfs - ok

14:18:52.0631 0x204c  [ F9D215A46A8B9753F61767FA72A20326, 6F76642B45E0A7EF6BCAB8B37D55CCE2EAA310ED07B76D43FCB88987C2174141 ] mshidkmdf       C:\windows\System32\drivers\mshidkmdf.sys

14:18:52.0668 0x204c  mshidkmdf - ok

14:18:52.0704 0x204c  [ 87B9DAF6D123EC06C19B41D5295441AD, 2066EA70D85B9F17CA3121D69DB25E2E17C4AFAECB68CC97FFF4A3062099FF0C ] MSI Foundation Service C:\Program Files (x86)\MSI\MSI HOUSE\MSIFoundationService.exe

14:18:52.0731 0x204c  MSI Foundation Service - detected UnsignedFile.Multi.Generic ( 1 )

14:18:59.0596 0x204c  Detect skipped due to KSN trusted

14:18:59.0596 0x204c  MSI Foundation Service - ok

14:18:59.0658 0x204c  [ D916874BBD4F8B07BFB7FA9B3CCAE29D, B229DA150713DEDBC4F05386C9D9DC3BC095A74F44F3081E88311AB73BC992A1 ] msisadrv        C:\windows\system32\drivers\msisadrv.sys

14:18:59.0690 0x204c  msisadrv - ok

14:18:59.0774 0x204c  [ 808E98FF49B155C522E6400953177B08, F873F5BFF0984C5165DF67E92874D3F6EB8D86F9B5AD17013A0091CA33A1A3D5 ] MSiSCSI         C:\windows\system32\iscsiexe.dll

14:18:59.0870 0x204c  MSiSCSI - ok

14:18:59.0872 0x204c  msiserver - ok

14:18:59.0884 0x204c  [ 49CCF2C4FEA34FFAD8B1B59D49439366, E5752EA57C7BDAD5F53E3BC441A415E909AC602CAE56234684FB8789A20396C7 ] MSKSSRV         C:\windows\system32\drivers\MSKSSRV.sys

14:18:59.0909 0x204c  MSKSSRV - ok

14:18:59.0987 0x204c  [ 89F2AEDC2788696702141AB82C3E7866, E166CBD8D3C708737C37172221945D8E56C25C2CC750889C3CE14AA2DE750F33 ] MsMpSvc         c:\Program Files\Microsoft Security Client\MsMpEng.exe

14:19:00.0008 0x204c  MsMpSvc - ok

14:19:00.0013 0x204c  [ BDD71ACE35A232104DDD349EE70E1AB3, 27464A66868513BE6A01B75D7FC5B0D6B71842E4E20CE3F76B15C071A0618BBB ] MSPCLOCK        C:\windows\system32\drivers\MSPCLOCK.sys

14:19:00.0049 0x204c  MSPCLOCK - ok

14:19:00.0052 0x204c  [ 4ED981241DB27C3383D72092B618A1D0, E12F121E641249DB3491141851B59E1496F4413EDF58E863388F1C229838DFCC ] MSPQM           C:\windows\system32\drivers\MSPQM.sys

14:19:00.0085 0x204c  MSPQM - ok

14:19:00.0111 0x204c  [ 759A9EEB0FA9ED79DA1FB7D4EF78866D, 64E3BC613EC4872B1B344CBF71EE15BE195592E3244C1EE099C6F8B95A40F133 ] MsRPC           C:\windows\system32\drivers\MsRPC.sys

14:19:00.0131 0x204c  MsRPC - ok

14:19:00.0141 0x204c  [ 0EED230E37515A0EAEE3C2E1BC97B288, B1D8F8A75006B6E99214CA36D27A8594EF8D952F315BEB201E9BAC9DE3E64D42 ] mssmbios        C:\windows\system32\drivers\mssmbios.sys

14:19:00.0149 0x204c  mssmbios - ok

14:19:00.0152 0x204c  [ 2E66F9ECB30B4221A318C92AC2250779, DF175E1AB6962303E57F26DAE5C5C1E40B8640333F3E352A64F6A5F1301586CD ] MSTEE           C:\windows\system32\drivers\MSTEE.sys

14:19:00.0192 0x204c  MSTEE - ok

14:19:00.0194 0x204c  [ 7EA404308934E675BFFDE8EDF0757BCD, 306CD02D89CFCFE576242360ED5F9EEEDCAFC43CD43B7D2977AE960F9AEC3232 ] MTConfig       

dds.txt

attach.txt

[Chelsey]

 C:\windows\system32\drivers\MTConfig.sys

14:19:00.0214 0x204c  MTConfig - ok

14:19:00.0232 0x204c  [ F9A18612FD3526FE473C1BDA678D61C8, 32F7975B5BAA447917F832D9E3499B4B6D3E90D73F478375D0B70B36C524693A ] Mup             C:\windows\system32\Drivers\mup.sys

14:19:00.0247 0x204c  Mup - ok

14:19:00.0276 0x204c  [ 582AC6D9873E31DFA28A4547270862DD, BD540499F74E8F59A020D935D18E36A3A97C1A6EC59C8208436469A31B16B260 ] napagent        C:\windows\system32\qagentRT.dll

14:19:00.0315 0x204c  napagent - ok

14:19:00.0335 0x204c  [ 1EA3749C4114DB3E3161156FFFFA6B33, 54C2E77BCE1037711A11313AC25B8706109098C10A31AA03AEB7A185E97800D7 ] NativeWifiP     C:\windows\system32\DRIVERS\nwifi.sys

14:19:00.0367 0x204c  NativeWifiP - ok

14:19:00.0434 0x204c  [ 760E38053BF56E501D562B70AD796B88, F856E81A975D44F8684A6F2466549CEEDFAEB3950191698555A93A1206E0A42D ] NDIS            C:\windows\system32\drivers\ndis.sys

14:19:00.0467 0x204c  NDIS - ok

14:19:00.0487 0x204c  [ 9F9A1F53AAD7DA4D6FEF5BB73AB811AC, D7E5446E83909AE25506BB98FBDD878A529C87963E3C1125C4ABAB25823572BC ] NdisCap         C:\windows\system32\DRIVERS\ndiscap.sys

14:19:00.0543 0x204c  NdisCap - ok

14:19:00.0563 0x204c  [ 30639C932D9FEF22B31268FE25A1B6E5, 32873D95339600F6EEFA51847D12C563FF01F320DC59055B242FA2887C99F9D6 ] NdisTapi        C:\windows\system32\DRIVERS\ndistapi.sys

14:19:00.0588 0x204c  NdisTapi - ok

14:19:00.0591 0x204c  [ 136185F9FB2CC61E573E676AA5402356, BA3AD0A33416DA913B4242C6BE8C3E5812AD2B20BA6C11DD3094F2E8EB56E683 ] Ndisuio         C:\windows\system32\DRIVERS\ndisuio.sys

14:19:00.0616 0x204c  Ndisuio - ok

14:19:00.0631 0x204c  [ 53F7305169863F0A2BDDC49E116C2E11, 881E9346D3C02405B7850ADC37E720990712EC9C666A0CE96E252A487FD2CE77 ] NdisWan         C:\windows\system32\DRIVERS\ndiswan.sys

14:19:00.0673 0x204c  NdisWan - ok

14:19:00.0691 0x204c  [ 015C0D8E0E0421B4CFD48CFFE2825879, 4242E2D42CCFC859B2C0275C5331798BC0BDA68E51CF4650B6E64B1332071023 ] NDProxy         C:\windows\system32\drivers\NDProxy.sys

14:19:00.0725 0x204c  NDProxy - ok

14:19:00.0734 0x204c  [ 86743D9F5D2B1048062B14B1D84501C4, DBF6D6A60AB774FCB0F464FF2D285A7521D0A24006687B243AB46B17D8032062 ] NetBIOS         C:\windows\system32\DRIVERS\netbios.sys

14:19:00.0769 0x204c  NetBIOS - ok

14:19:00.0791 0x204c  [ 09594D1089C523423B32A4229263F068, 7426A9B8BA27D3225928DDEFBD399650ABB90798212F56B7D12158AC22CCCE37 ] NetBT           C:\windows\system32\DRIVERS\netbt.sys

14:19:00.0844 0x204c  NetBT - ok

14:19:00.0846 0x204c  [ 204F3F58212B3E422C90BD9691A2DF28, D748A8CEE4D59B4248C9B1ACA5155D0FF6635A29564B4391B7FAC6261F93FE99 ] Netlogon        C:\windows\system32\lsass.exe

14:19:00.0855 0x204c  Netlogon - ok

14:19:00.0909 0x204c  [ 847D3AE376C0817161A14A82C8922A9E, 37AE692B3481323134125EF58F2C3CBC20177371AF2F5874F53DD32A827CB936 ] Netman          C:\windows\System32\netman.dll

14:19:00.0986 0x204c  Netman - ok

14:19:01.0079 0x204c  [ 21318671BCAD3ACF16638F98D4D00973, CEA6E3B6BCB4B74A9ACACBEEA12EEA967BBC2240398E2EBC04D7910109CACA11 ] NetMsmqActivator C:\windows\Microsoft.NET\Framework64\v4.0.30319\SMSvcHost.exe

14:19:01.0105 0x204c  NetMsmqActivator - ok

14:19:01.0109 0x204c  [ 21318671BCAD3ACF16638F98D4D00973, CEA6E3B6BCB4B74A9ACACBEEA12EEA967BBC2240398E2EBC04D7910109CACA11 ] NetPipeActivator C:\windows\Microsoft.NET\Framework64\v4.0.30319\SMSvcHost.exe

14:19:01.0119 0x204c  NetPipeActivator - ok

14:19:01.0153 0x204c  [ 5F28111C648F1E24F7DBC87CDEB091B8, 2E8645285921EDB98BB2173E11E57459C888D52E80D85791D169C869DE8813B9 ] netprofm        C:\windows\System32\netprofm.dll

14:19:01.0194 0x204c  netprofm - ok

14:19:01.0198 0x204c  [ 21318671BCAD3ACF16638F98D4D00973, CEA6E3B6BCB4B74A9ACACBEEA12EEA967BBC2240398E2EBC04D7910109CACA11 ] NetTcpActivator C:\windows\Microsoft.NET\Framework64\v4.0.30319\SMSvcHost.exe

14:19:01.0208 0x204c  NetTcpActivator - ok

14:19:01.0212 0x204c  [ 21318671BCAD3ACF16638F98D4D00973, CEA6E3B6BCB4B74A9ACACBEEA12EEA967BBC2240398E2EBC04D7910109CACA11 ] NetTcpPortSharing C:\windows\Microsoft.NET\Framework64\v4.0.30319\SMSvcHost.exe

14:19:01.0222 0x204c  NetTcpPortSharing - ok

14:19:01.0458 0x204c  [ B9C587BDAA61A689883439D5AE6FE7F3, 4AA75BFDD18E0F7D250D1726556FA4F1B0CFE93EA1C38BA43F0EBE046B566E4F ] NETwNs64        C:\windows\system32\DRIVERS\NETwNs64.sys

14:19:01.0727 0x204c  NETwNs64 - ok

14:19:01.0747 0x204c  [ 77889813BE4D166CDAB78DDBA990DA92, 2EF531AE502B943632EEC66A309A8BFCDD36120A5E1473F4AAF3C2393AD0E6A3 ] nfrd960         C:\windows\system32\drivers\nfrd960.sys

14:19:01.0756 0x204c  nfrd960 - ok

14:19:01.0817 0x204c  [ C3E0696C3B42F694C5822776AA6FFFDF, 80C3DEC2C48500F96C9E677450EFC1ADA9FE9FBB70F4CC2D7D9244B1A515418B ] NisDrv          C:\windows\system32\DRIVERS\NisDrvWFP.sys

14:19:01.0841 0x204c  NisDrv - ok

14:19:01.0919 0x204c  [ DCEE3592299B2229A0DB98CB415059A2, 709AAA095DF44DDCB6159CE1635AB05EC666D845445790E569F56B297DC64AC3 ] NisSrv          c:\Program Files\Microsoft Security Client\NisSrv.exe

14:19:01.0956 0x204c  NisSrv - ok

14:19:01.0975 0x204c  [ 8AD77806D336673F270DB31645267293, E23F324913554A23CD043DD27D4305AF62F48C0561A0FC7B7811E55B74B1BE79 ] NlaSvc          C:\windows\System32\nlasvc.dll

14:19:02.0007 0x204c  NlaSvc - ok

14:19:02.0022 0x204c  [ 1E4C4AB5C9B8DD13179BBDC75A2A01F7, D8957EF7060A69DBB3CD6B2C45B1E4143592AB8D018471E17AC04668157DC67F ] Npfs            C:\windows\system32\drivers\Npfs.sys

14:19:02.0048 0x204c  Npfs - ok

14:19:02.0061 0x204c  [ D54BFDF3E0C953F823B3D0BFE4732528, 497A1DCC5646EC22119273216DF10D5442D16F83E4363770F507518CF6EAA53A ] nsi             C:\windows\system32\nsisvc.dll

14:19:02.0099 0x204c  nsi - ok

14:19:02.0131 0x204c  [ E7F5AE18AF4168178A642A9247C63001, 133023B7E4BA8049C4CAED3282BDD25571D1CC25FAC3B820C7F981D292689D76 ] nsiproxy        C:\windows\system32\drivers\nsiproxy.sys

14:19:02.0167 0x204c  nsiproxy - ok

14:19:02.0266 0x204c  [ 1A29A59A4C5BA6F8C85062A613B7E2B2, CC137F499A12C724D4166C2D85E9F447413419A0683DAC6F1A802B7F210C77F1 ] Ntfs            C:\windows\system32\drivers\Ntfs.sys

14:19:02.0317 0x204c  Ntfs - ok

14:19:02.0330 0x204c  [ 9899284589F75FA8724FF3D16AED75C1, 181188599FD5D4DE33B97010D9E0CAEABAB9A3EF50712FE7F9AA0735CD0666D6 ] Null            C:\windows\system32\drivers\Null.sys

14:19:02.0373 0x204c  Null - ok

14:19:02.0409 0x204c  [ 158AD24745BD85BA9BE3C51C38F48C32, B053A3B5A5CAE2CBC47E2C19E636AD70F376334EFFBB391A76562E67CBF3AC86 ] nusb3hub        C:\windows\system32\drivers\nusb3hub.sys

14:19:02.0429 0x204c  nusb3hub - ok

14:19:02.0470 0x204c  [ D40A13B2C0891E218F9523B376955DB6, 9A2AAAF960868B860A65579EAD507B35C64CFD6C3581F8D731ADF975F778D10E ] nusb3xhc        C:\windows\system32\drivers\nusb3xhc.sys

14:19:02.0494 0x204c  nusb3xhc - ok

14:19:02.0539 0x204c  [ 960E39A54E525DF58CB29193147DFFA1, E4620FD0E1E76FA9EBE9C641517D22B82458B62998711C74CA4FC60D55678582 ] NVHDA           C:\windows\system32\drivers\nvhda64v.sys

14:19:02.0574 0x204c  NVHDA - ok

14:19:02.0914 0x204c  [ 9D0FE265EE77296E072BFCB3A2B99DA5, F5CB5EC410FDAE7E612078F5DCDB928174A194E5AACA55CA544DBE8CEBD694B6 ] nvlddmkm        C:\windows\system32\DRIVERS\nvlddmkm.sys

14:19:03.0229 0x204c  nvlddmkm - ok

14:19:03.0259 0x204c  [ 0A92CB65770442ED0DC44834632F66AD, 581327F07A68DBD5CC749214BE5F1211FC2CE41C7A4F0656B680AFB51A35ACE7 ] nvraid          C:\windows\system32\drivers\nvraid.sys

14:19:03.0270 0x204c  nvraid - ok

14:19:03.0275 0x204c  [ DAB0E87525C10052BF65F06152F37E4A, AD9BFF0D5FD3FFB95C758B478E1F6A9FE45E7B37AEC71EB5070D292FEAAEDF37 ] nvstor          C:\windows\system32\drivers\nvstor.sys

14:19:03.0285 0x204c  nvstor - ok

14:19:03.0389 0x204c  [ 074F4B8E6CA3DA78B75A7BD7344E57EA, 32D91F4817FD9CBB81DCC5761118D8154A6E6C11C9F6C973A194FEF84396FCB4 ] NVSvc           C:\windows\system32\nvvsvc.exe

14:19:03.0434 0x204c  NVSvc - ok

14:19:03.0442 0x204c  [ 270D7CD42D6E3979F6DD0146650F0E05, 752489E54C9004EDCBE1F1F208FFD864DA5C83E59A2DDE6B3E0D63ECA996F76F ] nv_agp          C:\windows\system32\drivers\nv_agp.sys

14:19:03.0452 0x204c  nv_agp - ok

14:19:03.0460 0x204c  [ 3589478E4B22CE21B41FA1BFC0B8B8A0, AD2469FC753FE552CB809FF405A9AB23E7561292FE89117E3B3B62057EFF0203 ] ohci1394        C:\windows\system32\drivers\ohci1394.sys

14:19:03.0470 0x204c  ohci1394 - ok

14:19:03.0518 0x204c  [ 9D10F99A6712E28F8ACD5641E3A7EA6B, 70964A0ED9011EA94044E15FA77EDD9CF535CC79ED8E03A3721FF007E69595CC ] ose             C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE

14:19:03.0541 0x204c  ose - ok

14:19:03.0720 0x204c  [ 61BFFB5F57AD12F83AB64B7181829B34, 1DD0DD35E4158F95765EE6639F217DF03A0A19E624E020DBA609268C08A13846 ] osppsvc         C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\OSPPSVC.EXE

14:19:03.0832 0x204c  osppsvc - ok

14:19:03.0871 0x204c  [ 3EAC4455472CC2C97107B5291E0DCAFE, E51F373F2DBEAEE516B42BAE8C1B5BB68D00B881323E842CB6EDEC0A183CFFC3 ] p2pimsvc        C:\windows\system32\pnrpsvc.dll

14:19:03.0905 0x204c  p2pimsvc - ok

14:19:03.0939 0x204c  [ 927463ECB02179F88E4B9A17568C63C3, FEFD3447692C277D59EEC7BF218552C8BB6B8C98C26E973675549628408B94CE ] p2psvc          C:\windows\system32\p2psvc.dll

14:19:03.0984 0x204c  p2psvc - ok

14:19:03.0988 0x204c  [ 0086431C29C35BE1DBC43F52CC273887, 0D116D49EF9ABB57DA005764F25E692622210627FC2048F06A989B12FA8D0A80 ] Parport         C:\windows\system32\drivers\parport.sys

14:19:03.0999 0x204c  Parport - ok

14:19:04.0037 0x204c  [ E9766131EEADE40A27DC27D2D68FBA9C, 63C295EC96DBD25F1A8B908295CCB86B54F2A77A02AAA11E5D9160C2C1A492B6 ] partmgr         C:\windows\system32\drivers\partmgr.sys

14:19:04.0070 0x204c  partmgr - ok

14:19:04.0096 0x204c  [ 3AEAA8B561E63452C655DC0584922257, 04C072969B58657602EB0C21CEDF24FCEE14E61B90A0F758F93925EF2C9FC32D ] PcaSvc          C:\windows\System32\pcasvc.dll

14:19:04.0122 0x204c  PcaSvc - ok

14:19:04.0181 0x204c  [ BAE04007A679893E975A2B75E9E001E9, 53E425F714BB8196B59E7250F87E0D3FAE6650262EDF02F37BC4F9563F673B82 ] pcCMService     C:\Program Files (x86)\Common Files\Motive\pcCMService.exe

14:19:04.0217 0x204c  pcCMService - detected UnsignedFile.Multi.Generic ( 1 )

14:19:07.0130 0x204c  Detect skipped due to KSN trusted

14:19:07.0130 0x204c  pcCMService - ok

14:19:07.0273 0x204c  [ 3BEA1D461531D1D26F5695BB9CA97A18, 0A8C742DA85CF598F2E6130F450E55933951D9B1F7BB1E8FAB2E9E2668483EF1 ] pcCMService64   C:\Program Files\Common Files\Motive\pcCMService.exe

14:19:07.0325 0x204c  pcCMService64 - detected UnsignedFile.Multi.Generic ( 1 )

14:19:10.0403 0x204c  Detect skipped due to KSN trusted

14:19:10.0403 0x204c  pcCMService64 - ok

14:19:10.0477 0x204c  [ 94575C0571D1462A0F70BDE6BD6EE6B3, 7139BAC653EA94A3DD3821CAB35FC5E22F4CCA5ACC2BAABDAA27E4C3C8B27FC9 ] pci             C:\windows\system32\drivers\pci.sys

14:19:10.0504 0x204c  pci - ok

14:19:10.0536 0x204c  [ B5B8B5EF2E5CB34DF8DCF8831E3534FA, F2A7CC645B96946CC65BF60E14E70DC09C848D27C7943CE5DEA0C01A6B863480 ] pciide          C:\windows\system32\drivers\pciide.sys

14:19:10.0544 0x204c  pciide - ok

14:19:10.0566 0x204c  [ B2E81D4E87CE48589F98CB8C05B01F2F, 6763BEE7270A4873B3E131BFB92313E2750FCBD0AD73C23D1C4F98F7DF73DE14 ] pcmcia          C:\windows\system32\drivers\pcmcia.sys

14:19:10.0656 0x204c  pcmcia - ok

14:19:10.0693 0x204c  [ A792405E6C84C3DEBC02B1CF29A928F0, A9B5830D68BE1D00927D600D7A06FDDACBEB1DA03817CD486714B3F8CFAF36B7 ] pcServiceHost   C:\Program Files (x86)\Common Files\Motive\pcServiceHost.exe

14:19:10.0720 0x204c  pcServiceHost - detected UnsignedFile.Multi.Generic ( 1 )

14:19:13.0903 0x204c  Detect skipped due to KSN trusted

14:19:13.0903 0x204c  pcServiceHost - ok

14:19:13.0963 0x204c  [ D6B9C2E1A11A3A4B26A182FFEF18F603, BBA5FE08B1DDD6243118E11358FD61B10E850F090F061711C3CB207CE5FBBD36 ] pcw             C:\windows\system32\drivers\pcw.sys

14:19:13.0987 0x204c  pcw - ok

14:19:14.0076 0x204c  [ 68769C3356B3BE5D1C732C97B9A80D6E, FB2D61145980A2899D1B7729184C54070315B0E63C9A22400A76CCD39E00029C ] PEAUTH          C:\windows\system32\drivers\peauth.sys

14:19:14.0147 0x204c  PEAUTH - ok

14:19:14.0178 0x204c  [ E495E408C93141E8FC72DC0C6046DDFA, 489B957DADA0DC128A09468F1AD082DCC657E86053208EA06A12937BE86FB919 ] PerfHost        C:\windows\SysWow64\perfhost.exe

14:19:14.0224 0x204c  PerfHost - ok

14:19:14.0314 0x204c  [ C7CF6A6E137463219E1259E3F0F0DD6C, 08D7244F52AA17DD669AA6F77C291DAC88E7B2D1887DE422509C1F83EC85F3DD ] pla             C:\windows\system32\pla.dll

14:19:14.0412 0x204c  pla - ok

14:19:14.0487 0x204c  [ 25FBDEF06C4D92815B353F6E792C8129, 57D9764AE6BCE33B242C399CDFC10DD405975BD6411CA8C75FBCD06EEB8442A9 ] PlugPlay        C:\windows\system32\umpnpmgr.dll

14:19:14.0538 0x204c  PlugPlay - ok

14:19:14.0549 0x204c  [ 7195581CEC9BB7D12ABE54036ACC2E38, 9C4E5D6EA984148F2663DC529083408B2248DFF6DAAC85D9195F80A722782315 ] PNRPAutoReg     C:\windows\system32\pnrpauto.dll

14:19:14.0558 0x204c  PNRPAutoReg - ok

14:19:14.0577 0x204c  [ 3EAC4455472CC2C97107B5291E0DCAFE, E51F373F2DBEAEE516B42BAE8C1B5BB68D00B881323E842CB6EDEC0A183CFFC3 ] PNRPsvc         C:\windows\system32\pnrpsvc.dll

14:19:14.0593 0x204c  PNRPsvc - ok

14:19:14.0640 0x204c  [ 4F15D75ADF6156BF56ECED6D4A55C389, 2ADA3EA69A5D7EC2A4D2DD89178DB94EAFDDF95F07B0070D654D9F7A5C12A044 ] PolicyAgent     C:\windows\System32\ipsecsvc.dll

14:19:14.0707 0x204c  PolicyAgent - ok

14:19:14.0734 0x204c  [ 6BA9D927DDED70BD1A9CADED45F8B184, 66203CE70A5EDE053929A940F38924C6792239CCCE10DD2C1D90D5B4D6748B55 ] Power           C:\windows\system32\umpo.dll

14:19:14.0791 0x204c  Power - ok

14:19:14.0817 0x204c  [ F92A2C41117A11A00BE01CA01A7FCDE9, 38ADC6052696D110CA5F393BC586791920663F5DA66934C2A824DDA9CD89C763 ] PptpMiniport    C:\windows\system32\DRIVERS\raspptp.sys

14:19:14.0867 0x204c  PptpMiniport - ok

14:19:14.0877 0x204c  [ 0D922E23C041EFB1C3FAC2A6F943C9BF, 855418A6A58DCAFB181A1A68613B3E203AFB0A9B3D9D26D0C521F9F613B4EAD5 ] Processor       C:\windows\system32\drivers\processr.sys

14:19:14.0911 0x204c  Processor - ok

14:19:14.0960 0x204c  [ 53E83F1F6CF9D62F32801CF66D8352A8, 1225FED810BE8E0729EEAE5B340035CCBB9BACD3EF247834400F9B72D05ACE48 ] ProfSvc         C:\windows\system32\profsvc.dll

14:19:15.0002 0x204c  ProfSvc - ok

14:19:15.0015 0x204c  [ 204F3F58212B3E422C90BD9691A2DF28, D748A8CEE4D59B4248C9B1ACA5155D0FF6635A29564B4391B7FAC6261F93FE99 ] ProtectedStorage C:\windows\system32\lsass.exe

14:19:15.0030 0x204c  ProtectedStorage - ok

14:19:15.0046 0x204c  [ 0557CF5A2556BD58E26384169D72438D, F6F83A616B1F1C6C0DF6D2EC2513E6C23FD4FAA6D36518B8676C619AB74957B4 ] Psched          C:\windows\system32\DRIVERS\pacer.sys

14:19:15.0104 0x204c  Psched - ok

14:19:15.0181 0x204c  [ 543A4EF0923BF70D126625B034EF25AF, 9CC82C5221F11850419A796D48D5452B3DEE0C8E8E85A818F4AAA869673F9740 ] PSI_SVC_2       C:\Program Files (x86)\Common Files\Protexis\License Service\PsiService_2.exe

14:19:15.0208 0x204c  PSI_SVC_2 - ok

14:19:15.0283 0x204c  [ 788CB65D49D1162C5EE6814AFE5B0A70, 74072698692C8237F5041BB111C4E24B6583456FDA084895EA00B677B6FF64FC ] PSI_SVC_2_x64   c:\Program Files\Common Files\Protexis\License Service\PsiService_2.exe

14:19:15.0305 0x204c  PSI_SVC_2_x64 - ok

14:19:15.0321 0x204c  [ BC08F7F3C53CBEE68670ED1314E290FD, EC683DDE60AFED297D28BC7570BB6DA27A94F52417AD6DE1FBE265255F4051DD ] PxHlpa64        C:\windows\system32\Drivers\PxHlpa64.sys

14:19:15.0329 0x204c  PxHlpa64 - ok

14:19:15.0376 0x204c  [ A53A15A11EBFD21077463EE2C7AFEEF0, 6002B012A75045DEA62640A864A8721EADE2F8B65BEB5F5BA76D8CD819774489 ] ql2300          C:\windows\system32\drivers\ql2300.sys

14:19:15.0423 0x204c  ql2300 - ok

14:19:15.0441 0x204c  [ 4F6D12B51DE1AAEFF7DC58C4D75423C8, FB6ABAB741CED66A79E31A45111649F2FA3E26CEE77209B5296F789F6F7D08DE ] ql40xx          C:\windows\system32\drivers\ql40xx.sys

14:19:15.0452 0x204c  ql40xx - ok

14:19:15.0474 0x204c  [ 906191634E99AEA92C4816150BDA3732, A0305436384104C3B559F9C73902DA19B96B518413379E397C5CDAB0B2B9418F ] QWAVE           C:\windows\system32\qwave.dll

14:19:15.0508 0x204c  QWAVE - ok

14:19:15.0513 0x204c  [ 76707BB36430888D9CE9D705398ADB6C, 35C1D1D05F98AC29A33D3781F497A0B40A3CB9CDF25FE1F28F574E40DDF70535 ] QWAVEdrv        C:\windows\system32\drivers\qwavedrv.sys

14:19:15.0534 0x204c  QWAVEdrv - ok

14:19:15.0536 0x204c  [ 5A0DA8AD5762FA2D91678A8A01311704, 8A64EB5DBAB7048A9E42A21CEB62CCD5B007A80C199892D7F8C69B48E8A255EF ] RasAcd          C:\windows\system32\DRIVERS\rasacd.sys

14:19:15.0566 0x204c  RasAcd - ok

14:19:15.0592 0x204c  [ 7ECFF9B22276B73F43A99A15A6094E90, 62C70DA127F48F796F8897BBFA23AB6EB080CC923F0F091DFA384A93F5C90CA1 ] RasAgileVpn     C:\windows\system32\DRIVERS\AgileVpn.sys

14:19:15.0618 0x204c  RasAgileVpn - ok

14:19:15.0636 0x204c  [ 8F26510C5383B8DBE976DE1CD00FC8C7, 60E618C010E8A723960636415573FA17EA0BBEF79647196B3BC0B8DEE680E090 ] RasAuto         C:\windows\System32\rasauto.dll

14:19:15.0675 0x204c  RasAuto - ok

14:19:15.0699 0x204c  [ 471815800AE33E6F1C32FB1B97C490CA, 27307265F743DE3A3A3EC1B2C472A3D85FDD0AEC458E0B1177593141EE072698 ] Rasl2tp         C:\windows\system32\DRIVERS\rasl2tp.sys

14:19:15.0747 0x204c  Rasl2tp - ok

14:19:15.0790 0x204c  [ EE867A0870FC9E4972BA9EAAD35651E2, 1B848D81705081FD2E18AC762DA7F51455657DAF860BF363DC15925A148BCADA ] RasMan          C:\windows\System32\rasmans.dll

14:19:15.0828 0x204c  RasMan - ok

14:19:15.0841 0x204c  [ 855C9B1CD4756C5E9A2AA58A15F58C25, A514F8A9C304D54BDA8DC60F5A64259B057EC83A1CAAF6D2B58CFD55E9561F72 ] RasPppoe        C:\windows\system32\DRIVERS\raspppoe.sys

14:19:15.0878 0x204c  RasPppoe - ok

14:19:15.0919 0x204c  [ E8B1E447B008D07FF47D016C2B0EEECB, FEC789F82B912F3E14E49524D40FEAA4373B221156F14045E645D7C37859258C ] RasSstp         C:\windows\system32\DRIVERS\rassstp.sys

14:19:15.0976 0x204c  RasSstp - ok

14:19:15.0990 0x204c  [ 77F665941019A1594D887A74F301FA2F, 1FDC6F6853400190C086042933F157814D915C54F26793CAD36CD2607D8810DA ] rdbss           C:\windows\system32\DRIVERS\rdbss.sys

14:19:16.0037 0x204c  rdbss - ok

14:19:16.0058 0x204c  [ 302DA2A0539F2CF54D7C6CC30C1F2D8D, 1DF3501BBFFB56C3ECC39DBCC4287D3302216C2208CE22428B8C4967E5DE9D17 ] rdpbus          C:\windows\system32\drivers\rdpbus.sys

14:19:16.0095 0x204c  rdpbus - ok

14:19:16.0103 0x204c  [ CEA6CC257FC9B7715F1C2B4849286D24, A78144D18352EA802C39D9D42921CF97A3E0211766B2169B6755C6FC2D77A804 ] RDPCDD          C:\windows\system32\DRIVERS\RDPCDD.sys

14:19:16.0133 0x204c  RDPCDD - ok

14:19:16.0158 0x204c  [ BB5971A4F00659529A5C44831AF22365, 9AAA5C0D448E821FD85589505D99DF7749715A046BBD211F139E4E652ADDE41F ] RDPENCDD        C:\windows\system32\drivers\rdpencdd.sys

14:19:16.0181 0x204c  RDPENCDD - ok

14:19:16.0187 0x204c  [ 216F3FA57533D98E1F74DED70113177A, 60C126A1409D1E9C39F1C9E95F70115BF4AF07780AB499F6E10A612540F173F4 ] RDPREFMP        C:\windows\system32\drivers\rdprefmp.sys

14:19:16.0212 0x204c  RDPREFMP - ok

14:19:16.0252 0x204c  [ E61608AA35E98999AF9AAEEEA6114B0A, F754CDE89DC96786D2A3C4D19EE2AEF1008E634E4DE3C0CBF927436DE90C04A6 ] RDPWD           C:\windows\system32\drivers\RDPWD.sys

14:19:16.0294 0x204c  RDPWD - ok

14:19:16.0313 0x204c  [ 34ED295FA0121C241BFEF24764FC4520, AAEE5F00CAA763A5BA51CF56BD7262C03409CD72BD5601490E3EC3FFF929BB5F ] rdyboost        C:\windows\system32\drivers\rdyboost.sys

14:19:16.0330 0x204c  rdyboost - ok

14:19:16.0359 0x204c  [ 4D9AFDDDA0EFE97CDBFD3B5FA48B05F6, A0E808EA9A58FC99D694A9EBF1F7248B79CAA44D9E6E30A07CDEDBC72A8F3610 ] regi            C:\windows\system32\drivers\regi.sys

14:19:16.0366 0x204c  regi - ok

14:19:16.0388 0x204c  [ 254FB7A22D74E5511C73A3F6D802F192, 3D0FB5840364200DE394F8CC28DA0E334C2B5FA8FF28A41656EE72287F3D3836 ] RemoteAccess    C:\windows\System32\mprdim.dll

14:19:16.0427 0x204c  RemoteAccess - ok

14:19:16.0446 0x204c  [ E4D94F24081440B5FC5AA556C7C62702, 147CAA03568DC480F9506E30B84891AB7E433B5EBC05F34FF10F72B00E1C6B22 ] RemoteRegistry  C:\windows\system32\regsvc.dll

14:19:16.0474 0x204c  RemoteRegistry - ok

14:19:16.0492 0x204c  [ 3DD798846E2C28102B922C56E71B7932, 30B111615D74CB2213997A5C08DD9C8613ADE441D9423CC1C49A753D13CE524D ] RFCOMM          C:\windows\system32\DRIVERS\rfcomm.sys

14:19:16.0521 0x204c  RFCOMM - ok

14:19:16.0536 0x204c  [ E4DC58CF7B3EA515AE917FF0D402A7BB, 665B5CD9FE905B0EE3F59A7B1A94760F5393EBEE729877D8584349754C2867E8 ] RpcEptMapper    C:\windows\System32\RpcEpMap.dll

14:19:16.0582 0x204c  RpcEptMapper - ok

14:19:16.0593 0x204c  [ D5BA242D4CF8E384DB90E6A8ED850B8C, CB4CB2608B5E31B55FB1A2CF4051E6D08A0C2A5FB231B2116F95938D7577334E ] RpcLocator      C:\windows\system32\locator.exe

14:19:16.0615 0x204c  RpcLocator - ok

14:19:16.0643 0x204c  [ 5C627D1B1138676C0A7AB2C2C190D123, C5003F2C912C5CA990E634818D3B4FD72F871900AF2948BD6C4D6400B354B401 ] RpcSs           C:\windows\system32\rpcss.dll

14:19:16.0677 0x204c  RpcSs - ok

14:19:16.0686 0x204c  [ DDC86E4F8E7456261E637E3552E804FF, D250C69CCC75F2D88E7E624FCC51300E75637333317D53908CCA7E0F117173DD ] rspndr          C:\windows\system32\DRIVERS\rspndr.sys

14:19:16.0713 0x204c  rspndr - ok

14:19:16.0747 0x204c  [ E54A5586A28D0630A79A68BBAB84BFCF, F6FBF1E4C64351CEB205DDCD17C35EA26439E98F3528F96AE326959A7C26B488 ] RSUSBVSTOR      C:\windows\System32\Drivers\RtsUVStor.sys

14:19:16.0758 0x204c  RSUSBVSTOR - ok

14:19:16.0788 0x204c  [ A73ED14670220307874AD6BC2F279349, 0AAAB96BD5CCE5AE6334D0D43BE9AEB1EB2C8EFA6996289595FB7D394E11B444 ] RTL8167         C:\windows\system32\DRIVERS\Rt64win7.sys

14:19:16.0807 0x204c  RTL8167 - ok

14:19:16.0810 0x204c  [ 204F3F58212B3E422C90BD9691A2DF28, D748A8CEE4D59B4248C9B1ACA5155D0FF6635A29564B4391B7FAC6261F93FE99 ] SamSs           C:\windows\system32\lsass.exe

14:19:16.0819 0x204c  SamSs - ok

14:19:16.0832 0x204c  [ AC03AF3329579FFFB455AA2DAABBE22B, 7AD3B62ADFEC166F9E256F9FF8BAA0568B2ED7308142BF8F5269E6EAA5E0A656 ] sbp2port        C:\windows\system32\drivers\sbp2port.sys

14:19:16.0842 0x204c  sbp2port - ok

14:19:16.0871 0x204c  [ 9B7395789E3791A3B6D000FE6F8B131E, E5F067F3F212BF5481668BE1779CBEF053F511F8967589BE2E865ACB9A620024 ] SCardSvr        C:\windows\System32\SCardSvr.dll

14:19:16.0914 0x204c  SCardSvr - ok

14:19:16.0924 0x204c  [ 253F38D0D7074C02FF8DEB9836C97D2B, CB5CAFCB8628BB22877F74ACF1DED0BBAED8F4573A74DA7FE94BBBA584889116 ] scfilter        C:\windows\system32\DRIVERS\scfilter.sys

14:19:16.0965 0x204c  scfilter - ok

14:19:17.0005 0x204c  [ 262F6592C3299C005FD6BEC90FC4463A, 54095E37F0B6CC677A3E9BDD40F4647C713273D197DB341063AA7F342A60C4A7 ] Schedule        C:\windows\system32\schedsvc.dll

14:19:17.0074 0x204c  Schedule - ok

14:19:17.0103 0x204c  [ F17D1D393BBC69C5322FBFAFACA28C7F, 62A1A92B3C52ADFD0B808D7F69DD50238B5F202421F1786F7EAEAA63F274B3E8 ] SCPolicySvc     C:\windows\System32\certprop.dll

14:19:17.0128 0x204c  SCPolicySvc - ok

14:19:17.0145 0x204c  [ 6EA4234DC55346E0709560FE7C2C1972, 64011E044C16E2F92689E5F7E4666A075E27BBFA61F3264E5D51CE1656C1D5B8 ] SDRSVC          C:\windows\System32\SDRSVC.dll

14:19:17.0163 0x204c  SDRSVC - ok

14:19:17.0178 0x204c  [ 3EA8A16169C26AFBEB544E0E48421186, 34BBB0459C96B3DE94CCB0D73461562935C583D7BF93828DA4E20A6BC9B7301D ] secdrv          C:\windows\system32\drivers\secdrv.sys

14:19:17.0220 0x204c  secdrv - ok

14:19:17.0237 0x204c  [ BC617A4E1B4FA8DF523A061739A0BD87, 10C4057F6B321EB5237FF619747B74F5401BC17D15A8C7060829E8204A2297F9 ] seclogon        C:\windows\system32\seclogon.dll

14:19:17.0281 0x204c  seclogon - ok

14:19:17.0291 0x204c  [ C32AB8FA018EF34C0F113BD501436D21, E0EB8E80B51E45CA7EB061E705DA0BC07878759418A8519AE6E12326FE79E7C7 ] SENS            C:\windows\System32\sens.dll

14:19:17.0331 0x204c  SENS - ok

14:19:17.0347 0x204c  [ 0336CFFAFAAB87A11541F1CF1594B2B2, 8B8A6A33E78A12FB05E29B2E2775850626574AFD2EF88748D65E690A07B10B8D ] SensrSvc        C:\windows\system32\sensrsvc.dll

14:19:17.0386 0x204c  SensrSvc - ok

14:19:17.0390 0x204c  [ CB624C0035412AF0DEBEC78C41F5CA1B, A4D937F11E06CAE914347CA1362F4C98EC5EE0C0C80321E360EA1ABD6726F8D4 ] Serenum         C:\windows\system32\drivers\serenum.sys

14:19:17.0417 0x204c  Serenum - ok

14:19:17.0441 0x204c  [ C1D8E28B2C2ADFAEC4BA89E9FDA69BD6, 8F9776FB84C5D11068EAF1FF1D1A46466C655D64D256A8B1E31DC0C23B5DD22D ] Serial          C:\windows\system32\drivers\serial.sys

14:19:17.0479 0x204c  Serial - ok

14:19:17.0491 0x204c  [ 1C545A7D0691CC4A027396535691C3E3, 065C30BE598FF4DC55C37E0BBE0CEDF10A370AE2BF5404B42EBBB867A3FFED6D ] sermouse        C:\windows\system32\drivers\sermouse.sys

14:19:17.0513 0x204c  sermouse - ok

14:19:17.0540 0x204c  [ 0B6231BF38174A1628C4AC812CC75804, E569BF1F7F5689E2E917FA6516DB53388A5B8B1C6699DEE030147E853218811D ] SessionEnv      C:\windows\system32\sessenv.dll

14:19:17.0582 0x204c  SessionEnv - ok

14:19:17.0586 0x204c  [ A554811BCD09279536440C964AE35BBF, DA8F893722F803E189D7D4D6C6232ED34505B63A64ED3A0132A5BB7A2BABDE55 ] sffdisk         C:\windows\system32\drivers\sffdisk.sys

14:19:17.0600 0x204c  sffdisk - ok

14:19:17.0603 0x204c  [ FF414F0BAEFEBA59BC6C04B3DB0B87BF, B81EF5D26AEB572CAB590F7AD7CA8C89F296420089EF5E6148E972F2DBCA1042 ] sffp_mmc        C:\windows\system32\drivers\sffp_mmc.sys

14:19:17.0614 0x204c  sffp_mmc - ok

14:19:17.0616 0x204c  [ DD85B78243A19B59F0637DCF284DA63C, 6730D4F2BAE7E24615746ACC41B42D01DB6068D6504982008ADA1890DE900197 ] sffp_sd         C:\windows\system32\drivers\sffp_sd.sys

14:19:17.0628 0x204c  sffp_sd - ok

14:19:17.0638 0x204c  [ A9D601643A1647211A1EE2EC4E433FF4, 7AC60B4AB48D4BBF1F9681C12EC2A75C72E6E12D30FABC564A24394310E9A5F9 ] sfloppy         C:\windows\system32\drivers\sfloppy.sys

14:19:17.0648 0x204c  sfloppy - ok

14:19:17.0694 0x204c  [ 2046AA7491DE7EFA4D70E615D9BC9D09, A8763D059AD68D5842C407FA9644E0B129BEF0F63CD87E62B80B05441EDC3489 ] Sftfs           C:\windows\system32\DRIVERS\Sftfslh.sys

14:19:17.0728 0x204c  Sftfs - ok

14:19:17.0815 0x204c  [ 77C5A741A7452812F278EF2C18478862, 0B763679EB7EFB8ED9DCE7B429706E939BB65BA6BCF1BAE0E0426D4E87074B8C ] sftlist         C:\Program Files (x86)\Microsoft Application Virtualization Client\sftlist.exe

14:19:17.0853 0x204c  sftlist - ok

14:19:17.0875 0x204c  [ 0E0446BC4D51BE4263ACB7E33491191C, 2AD039FB440560658C4E06F67CC192EF71577EF3FF789A43C08430CE5EAE5A70 ] Sftplay         C:\windows\system32\DRIVERS\Sftplaylh.sys

14:19:17.0895 0x204c  Sftplay - ok

14:19:17.0909 0x204c  [ C5FB982CD266E604ED3142102C26D62C, A6BC0D72E98F924274ECAD49C85F0775D1CD45B97CD43F53DF3992B560835FC5 ] Sftredir        C:\windows\system32\DRIVERS\Sftredirlh.sys

14:19:17.0924 0x204c  Sftredir - ok

14:19:17.0945 0x204c  [ 2575511AF67AA1FA068CCC4918E2C2A3, 3152FF5AC2CF6FE966DA59B1B33E22F9BD9B6BB4310441870528364BA9501A4D ] Sftvol          C:\windows\system32\DRIVERS\Sftvollh.sys

14:19:17.0953 0x204c  Sftvol - ok

14:19:17.0985 0x204c  [ 39B1D0A636A400304565D4521FAD6D77, 1F01DB35B5A477AA7A77585C9304E6B5F3E67807531305BCA93A7F494CED8F59 ] sftvsa          C:\Program Files (x86)\Microsoft Application Virtualization Client\sftvsa.exe

14:19:18.0021 0x204c  sftvsa - ok

14:19:18.0039 0x204c  [ B95F6501A2F8B2E78C697FEC401970CE, 758B73A32902299A313348CE7EC189B20EB4CB398D0180E4EE24B84DAD55F291 ] SharedAccess    C:\windows\System32\ipnathlp.dll

14:19:18.0073 0x204c  SharedAccess - ok

14:19:18.0103 0x204c  [ AAF932B4011D14052955D4B212A4DA8D, 2A3BFD0FA9569288E91AE3E72CA1EC39E1450D01E6473CE51157E0F138257923 ] ShellHWDetection C:\windows\System32\shsvcs.dll

14:19:18.0157 0x204c  ShellHWDetection - ok

14:19:18.0164 0x204c  [ 843CAF1E5FDE1FFD5FF768F23A51E2E1, 89CA9F516E42A6B905474D738CDA2C121020A07DBD4E66CFE569DD77D79D7820 ] SiSRaid2        C:\windows\system32\drivers\SiSRaid2.sys

14:19:18.0173 0x204c  SiSRaid2 - ok

14:19:18.0176 0x204c  [ 6A6C106D42E9FFFF8B9FCB4F754F6DA4, 87B85C66DF7EB6FDB8A2341D05FAA5261FF68A90CCFC63F0E4A03824F1E33E5E ] SiSRaid4        C:\windows\system32\drivers\sisraid4.sys

14:19:18.0185 0x204c  SiSRaid4 - ok

14:19:18.0190 0x204c  [ 548260A7B8654E024DC30BF8A7C5BAA4, 4A7E58331D7765A12F53DC2371739DC9A463940B13E16157CE10DB80E958D740 ] Smb             C:\windows\system32\DRIVERS\smb.sys

14:19:18.0216 0x204c  Smb - ok

14:19:18.0237 0x204c  [ 6313F223E817CC09AA41811DAA7F541D, D787061043BEEDB9386B048CB9E680E6A88A1CBAE9BD4A8C0209155BFB76C630 ] SNMPTRAP        C:\windows\System32\snmptrap.exe

14:19:18.0256 0x204c  SNMPTRAP - ok

14:19:18.0263 0x204c  [ B9E31E5CACDFE584F34F730A677803F9, 21A5130BD00089C609522A372018A719F8E37103D2DD22C59EACB393BE35A063 ] spldr           C:\windows\system32\drivers\spldr.sys

14:19:18.0271 0x204c  spldr - ok

14:19:18.0299 0x204c  [ 85DAA09A98C9286D4EA2BA8D0E644377, F9C324E2EF81193FE831C7EECC44A100CA06F82FA731BF555D9EA4D91DA13329 ] Spooler         C:\windows\System32\spoolsv.exe

14:19:18.0332 0x204c  Spooler - ok

14:19:18.0418 0x204c  [ E17E0188BB90FAE42D83E98707EFA59C, FC075F7B39E86CC8EF6DA4E339FE946917E319C347AC70FB0C50AAF36F97E27F ] sppsvc          C:\windows\system32\sppsvc.exe

14:19:18.0547 0x204c  sppsvc - ok

14:19:18.0563 0x204c  [ 93D7D61317F3D4BC4F4E9F8A96A7DE45, 36D48B23B8243BE5229707375FCD11C2DCAC96983199345365F065A0CBF33314 ] sppuinotify     C:\windows\system32\sppuinotify.dll

14:19:18.0602 0x204c  sppuinotify - ok

14:19:18.0643 0x204c  [ 441FBA48BFF01FDB9D5969EBC1838F0B, 306128F1AD489F87161A089D1BDC1542A4CB742D91A0C12A7CD1863FDB8932C0 ] srv             C:\windows\system32\DRIVERS\srv.sys

14:19:18.0679 0x204c  srv - ok

14:19:18.0699 0x204c  [ B4ADEBBF5E3677CCE9651E0F01F7CC28, 726DB2283113AB2A9681E8E9F61132303D6D86E9CD034C40EE4A8C9DB29E87F7 ] srv2            C:\windows\system32\DRIVERS\srv2.sys

14:19:18.0723 0x204c  srv2 - ok

14:19:18.0736 0x204c  [ 27E461F0BE5BFF5FC737328F749538C3, AFA4704ED8FFC1A0BAB40DFB81D3AE3F3D933A3C9BF54DDAF39FF9AF3646D9E6 ] srvnet          C:\windows\system32\DRIVERS\srvnet.sys

14:19:18.0760 0x204c  srvnet - ok

14:19:18.0793 0x204c  [ 51B52FBD583CDE8AA9BA62B8B4298F33, 2E2403F8AA39E79D1281CA006B51B43139C32A5FDD64BD34DAA4B935338BD740 ] SSDPSRV         C:\windows\System32\ssdpsrv.dll

14:19:18.0859 0x204c  SSDPSRV - ok

14:19:18.0878 0x204c  [ AB7AEBF58DAD8DAAB7A6C45E6A8885CB, D21CDBC4C2AA0DB5B4455D5108B0CAF4282A2E664B9035708F212CC094569D9D ] SstpSvc         C:\windows\system32\sstpsvc.dll

14:19:18.0905 0x204c  SstpSvc - ok

14:19:18.0948 0x204c  [ 6E1A473DD2A4714EAF7D11E2315DF794, 4460546191072C7DF8B2E5A00577BA8E4FF5A1B2EA399DDF65EBE1AE4A5A5C84 ] Steam Client Service C:\Program Files (x86)\Common Files\Steam\SteamService.exe

14:19:18.0963 0x204c  Steam Client Service - ok

14:19:18.0977 0x204c  [ F3817967ED533D08327DC73BC4D5542A, 1B204454408A690C0A86447F3E4AA9E7C58A9CFB567C94C17C21920BA648B4D5 ] stexstor        C:\windows\system32\drivers\stexstor.sys

14:19:18.0985 0x204c  stexstor - ok

14:19:19.0025 0x204c  [ 8DD52E8E6128F4B2DA92CE27402871C1, 1101C38BE8FC383B5F2F9FA402F9652B23B88A764DE2B584DFE62B88B11DEF92 ] stisvc          C:\windows\System32\wiaservc.dll

14:19:19.0050 0x204c  stisvc - ok

14:19:19.0062 0x204c  [ D01EC09B6711A5F8E7E6564A4D0FBC90, 3CB922291DBADC92B46B9E28CCB6810CD8CCDA3E74518EC9522B58B998E1F969 ] swenum          C:\windows\system32\drivers\swenum.sys

14:19:19.0069 0x204c  swenum - ok

14:19:19.0159 0x204c  [ F577910A133A592234EBAAD3F3AFA258, 36F514740EE2D2B2F7ABFFFA13D575233EC4CE774EB58BF889C09930FEF1F443 ] SwitchBoard     C:\Program Files (x86)\Common Files\Adobe\SwitchBoard\SwitchBoard.exe

14:19:19.0197 0x204c  SwitchBoard - detected UnsignedFile.Multi.Generic ( 1 )

14:19:29.0298 0x204c  SwitchBoard ( UnsignedFile.Multi.Generic ) - warning

14:19:34.0289 0x204c  [ E08E46FDD841B7184194011CA1955A0B, 9C3725BB1F08F92744C980A22ED5C874007D3B5863C7E1F140F50061052AC418 ] swprv           C:\windows\System32\swprv.dll

14:19:34.0331 0x204c  swprv - ok

14:19:34.0388 0x204c  [ BF9CCC0BF39B418C8D0AE8B05CF95B7D, 3C13217548BE61F2BDB8BD41F77345CDDA1F97BF0AE17241C335B9807EB3DBB8 ] SysMain         C:\windows\system32\sysmain.dll

14:19:34.0466 0x204c  SysMain - ok

14:19:34.0484 0x204c  [ E3C61FD7B7C2557E1F1B0B4CEC713585, 01F0E116606D185BF93B540868075BFB1A398197F6AABD994983DBFF56B3A8A0 ] TabletInputService C:\windows\System32\TabSvc.dll

14:19:34.0504 0x204c  TabletInputService - ok

14:19:34.0521 0x204c  [ 40F0849F65D13EE87B9A9AE3C1DD6823, E251A7EF3D0FD2973AF33A62FC457A7E8D5E8694208F811F52455F7C2426121F ] TapiSrv         C:\windows\System32\tapisrv.dll

14:19:34.0563 0x204c  TapiSrv - ok

14:19:34.0579 0x204c  [ 1BE03AC720F4D302EA01D40F588162F6, AB644862BF1D2E824FD846180DEC4E2C0FAFCC517451486DE5A92E5E78A952E4 ] TBS             C:\windows\System32\tbssvc.dll

14:19:34.0618 0x204c  TBS - ok

14:19:34.0719 0x204c  [ 04ADD18EE5CC9FBEDAEC1DD1CD0CB45E, F05C0C4CA3DD234AD5D60CF1EF763C9A1D9EC3C157E180C2D75CC07E6B02A611 ] Tcpip           C:\windows\system32\drivers\tcpip.sys

14:19:34.0790 0x204c  Tcpip - ok

14:19:34.0841 0x204c  [ 04ADD18EE5CC9FBEDAEC1DD1CD0CB45E, F05C0C4CA3DD234AD5D60CF1EF763C9A1D9EC3C157E180C2D75CC07E6B02A611 ] TCPIP6          C:\windows\system32\DRIVERS\tcpip.sys

14:19:34.0880 0x204c  TCPIP6 - ok

14:19:34.0911 0x204c  [ 1B16D0BD9841794A6E0CDE0CEF744ABC, 7EB8BA97339199EEE7F2B09DA2DA6279DA64A510D4598D42CF86415D67CD674C ] tcpipreg        C:\windows\system32\drivers\tcpipreg.sys

14:19:34.0938 0x204c  tcpipreg - ok

14:19:34.0957 0x204c  [ 3371D21011695B16333A3934340C4E7C, 7416F9BBFC1BA9D875EA7D1C7A0D912FC6977B49A865D67E3F9C4E18A965082D ] TDPIPE          C:\windows\system32\drivers\tdpipe.sys

14:19:34.0981 0x204c  TDPIPE - ok

14:19:35.0002 0x204c  [ 51C5ECEB1CDEE2468A1748BE550CFBC8, 4E8F83877330B421F7B5D8393D34BC44C6450E69209DAA95B29CB298166A5DF9 ] TDTCP           C:\windows\system32\drivers\tdtcp.sys

14:19:35.0011 0x204c  TDTCP - ok

14:19:35.0026 0x204c  [ DDAD5A7AB24D8B65F8D724F5C20FD806, B71F2967A4EE7395E4416C1526CB85368AEA988BDD1F2C9719C48B08FAFA9661 ] tdx             C:\windows\system32\DRIVERS\tdx.sys

14:19:35.0053 0x204c  tdx - ok

14:19:35.0064 0x204c  [ 561E7E1F06895D78DE991E01DD0FB6E5, 83BFA50A528762EC52A011302AC3874636FB7E26628CD7ACFBF2BDC9FAA8110D ] TermDD          C:\windows\system32\drivers\termdd.sys

14:19:35.0074 0x204c  TermDD - ok

14:19:35.0103 0x204c  [ 2E648163254233755035B46DD7B89123, 6FA0D07CE18A3A69D82EE49D875F141E39406E92C34EAC76AC4EB052E6EBCBCD ] TermService     C:\windows\System32\termsrv.dll

14:19:35.0149 0x204c  TermService - ok

14:19:35.0153 0x204c  [ F0344071948D1A1FA732231785A0664C, DB9886C2C858FAF45AEA15F8E42860343F73EB8685C53EC2E8CCC10586CB0832 ] Themes          C:\windows\system32\themeservice.dll

14:19:35.0178 0x204c  Themes - ok

14:19:35.0195 0x204c  [ E40E80D0304A73E8D269F7141D77250B, 0DB4AC13A264F19A84DC0BCED54E8E404014CC09C993B172002B1561EC7E265A ] THREADORDER     C:\windows\system32\mmcss.dll

14:19:35.0220 0x204c  THREADORDER - ok

14:19:35.0291 0x204c  [ E4FAD21646088D79F8889B6531396ACF, D0C8F0E3293D423245FD2233F283A1FE2463E15F8B9F4ED6AC96C2164EC51F75 ] TomTomHOMEService C:\Program Files (x86)\TomTom HOME 2\TomTomHOMEService.exe

14:19:35.0320 0x204c  TomTomHOMEService - ok

14:19:35.0341 0x204c  [ 7E7AFD841694F6AC397E99D75CEAD49D, DE87F203FD8E6BDCCFCA1860A85F283301A365846FB703D9BB86278D8AC96B07 ] TrkWks          C:\windows\System32\trkwks.dll

14:19:35.0395 0x204c  TrkWks - ok

14:19:35.0430 0x204c  [ 773212B2AAA24C1E31F10246B15B276C, F2EF85F5ABA307976D9C649D710B408952089458DDE97D4DEF321DF14E46A046 ] TrustedInstaller C:\windows\servicing\TrustedInstaller.exe

14:19:35.0458 0x204c  TrustedInstaller - ok

14:19:35.0473 0x204c  [ 4CE278FC9671BA81A138D70823FCAA09, CBE501436696E32A3701B9F377B823AC36647B6626595F76CC63E2396AD7D300 ] tssecsrv        C:\windows\system32\DRIVERS\tssecsrv.sys

14:19:35.0507 0x204c  tssecsrv - ok

14:19:35.0530 0x204c  [ D11C783E3EF9A3C52C0EBE83CC5000E9, A136C355D4C8945729163D15801364A614E23217B15F9313C85BA45BB71A74EB ] TsUsbFlt        C:\windows\system32\drivers\tsusbflt.sys

14:19:35.0544 0x204c  TsUsbFlt - ok

14:19:35.0547 0x204c  [ 9CC2CCAE8A84820EAECB886D477CBCB8, 50D8AA2D7477A6618A0C31BB4D1C4887B457865FB1105E2E7B984EEFA337B804 ] TsUsbGD         C:\windows\system32\drivers\TsUsbGD.sys

14:19:35.0571 0x204c  TsUsbGD - ok

14:19:35.0612 0x204c  [ 3566A8DAAFA27AF944F5D705EAA64894, AE9D8B648DA08AF667B9456C3FE315489859C157510A258559F18238F2CC92B8 ] tunnel          C:\windows\system32\DRIVERS\tunnel.sys

14:19:35.0656 0x204c  tunnel - ok

14:19:35.0704 0x204c  [ 20155CF5FB9F7902178D7D5CDC7C0F90, 151043D6F1D7D3419FB4AA8D76229CFF99ECAA89297421C2137DE609E5A2B368 ] TurboB          C:\windows\system32\DRIVERS\TurboB.sys

14:19:35.0725 0x204c  TurboB - ok

14:19:35.0793 0x204c  [ E00FC2B80837C29817A3A082717B8C48, 8028C16FB0579EADAAA092B5F197125C716AF1C64C43F9FADF725D3E1109F1BD ] TurboBoost      C:\Program Files\Intel\TurboBoost\TurboBoost.exe

14:19:35.0853 0x204c  TurboBoost - ok

14:19:35.0872 0x204c  [ B4DD609BD7E282BFC683CEC7EAAAAD67, EF131DB6F6411CAD36A989A421AF93F89DD61601AC524D2FF11C10FF6E3E9123 ] uagp35          C:\windows\system32\drivers\uagp35.sys

14:19:35.0893 0x204c  uagp35 - ok

14:19:35.0918 0x204c  [ FF4232A1A64012BAA1FD97C7B67DF593, D8591B4EB056899C7B604E4DD852D82D4D9809F508ABCED4A03E1BE6D5D456E3 ] udfs            C:\windows\system32\DRIVERS\udfs.sys

14:19:35.0960 0x204c  udfs - ok

14:19:35.0989 0x204c  [ 3CBDEC8D06B9968ABA702EBA076364A1, B8DAB8AA804FC23021BFEBD7AE4D40FBE648D6C6BA21CC008E26D1C084972F9B ] UI0Detect       C:\windows\system32\UI0Detect.exe

14:19:36.0006 0x204c  UI0Detect - ok

14:19:36.0015 0x204c  [ 4BFE1BC28391222894CBF1E7D0E42320, 5918B1ED2030600DF77BDACF1C808DF6EADDD8BF3E7003AF1D72050D8B102B3A ] uliagpkx        C:\windows\system32\drivers\uliagpkx.sys

14:19:36.0024 0x204c  uliagpkx - ok

14:19:36.0081 0x204c  [ DC54A574663A895C8763AF0FA1FF7561, 09A3F3597E91CBEB2F38E96E75134312B60CAE5574B2AD4606C2D3E992AEDDFE ] umbus           C:\windows\system32\DRIVERS\umbus.sys

14:19:36.0134 0x204c  umbus - ok

14:19:36.0148 0x204c  [ B2E8E8CB557B156DA5493BBDDCC1474D, F547509A08C0679ACB843E20C9C0CF51BED1B06530BBC529DFB0944504564A43 ] UmPass          C:\windows\system32\drivers\umpass.sys

14:19:36.0172 0x204c  UmPass - ok

14:19:36.0197 0x204c  [ D47EC6A8E81633DD18D2436B19BAF6DE, 0FB461E2D5E0B75BB5958F6362F4880BFA4C36AD930542609BCAF574941AA7AE ] upnphost        C:\windows\System32\upnphost.dll

14:19:36.0268 0x204c  upnphost - ok

14:19:36.0326 0x204c  [ B0435098C81D04CAFFF80DDB746CD3A2, A17B207740382E38729571F0B0BC98FF874E856A7C7CE9EB930328A2AD88F52A ] usbaudio        C:\windows\system32\drivers\usbaudio.sys

14:19:36.0392 0x204c  usbaudio - ok

14:19:36.0444 0x204c  [ DCA68B0943D6FA415F0C56C92158A83A, BEE5A5B33B22D1DF50B884D46D89FC3B8286EB16E38AD5A20F0A49E5C6766C57 ] usbccgp         C:\windows\system32\DRIVERS\usbccgp.sys

14:19:36.0494 0x204c  usbccgp - ok

14:19:36.0534 0x204c  [ 80B0F7D5CCF86CEB5D402EAAF61FEC31, 140C62116A425DEAD25FE8D82DE283BC92C482A9F643658D512F9F67061F28AD ] usbcir          C:\windows\system32\drivers\usbcir.sys

14:19:36.0587 0x204c  usbcir - ok

14:19:36.0622 0x204c  [ 18A85013A3E0F7E1755365D287443965, 811C5EDF38C765BCF71BCE25CB6626FF6988C3699F5EF1846240EA0052F34C33 ] usbehci         C:\windows\system32\drivers\usbehci.sys

14:19:36.0653 0x204c  usbehci - ok

14:19:36.0691 0x204c  [ 8D1196CFBB223621F2C67D45710F25BA, B5D7AFE51833B24FC9576F3AED3D8A2B290E5846060E73F9FFFAC1890A8B6003 ] usbhub          C:\windows\system32\DRIVERS\usbhub.sys

14:19:36.0750 0x204c  usbhub - ok

14:19:36.0787 0x204c  [ 765A92D428A8DB88B960DA5A8D6089DC, 56DE8A2ED58E53B202C399CA7BACB1551136303C2EE0AB426BDBBF880E3C542C ] usbohci         C:\windows\system32\drivers\usbohci.sys

14:19:36.0825 0x204c  usbohci - ok

14:19:36.0861 0x204c  [ 73188F58FB384E75C4063D29413CEE3D, B485463933306036B1D490722CB1674DC85670753D79FA0EF7EBCA7BBAAD9F7C ] usbprint        C:\windows\system32\DRIVERS\usbprint.sys

14:19:36.0914 0x204c  usbprint - ok

14:19:36.0958 0x204c  [ 9661DA76B4531B2DA272ECCE25A8AF24, FEA93254A21E71A7EB8AD35FCCAD2C1E41F7329EC33B1734F5B41307A34D8637 ] usbscan         C:\windows\system32\drivers\usbscan.sys

14:19:37.0015 0x204c  usbscan - ok

14:19:37.0038 0x204c  [ FED648B01349A3C8395A5169DB5FB7D6, DC4D7594C24ADD076927B9347F1B50B91CF03A4ABDB284248D5711D9C19DEB96 ] USBSTOR         C:\windows\system32\DRIVERS\USBSTOR.SYS

14:19:37.0093 0x204c  USBSTOR - ok

14:19:37.0120 0x204c  [ DD253AFC3BC6CBA412342DE60C3647F3, 146F8613F1057AC054DC3593E84BC52899DA27EA33B0E72ACFB78C3699ADCDE7 ] usbuhci         C:\windows\system32\drivers\usbuhci.sys

14:19:37.0134 0x204c  usbuhci - ok

14:19:37.0196 0x204c  [ 1F775DA4CF1A3A1834207E975A72E9D7, 6D3DE5BD3EF3A76E997E5BAF900C51D25308F5A9682D1F62017F577A24095B90 ] usbvideo        C:\windows\System32\Drivers\usbvideo.sys

14:19:37.0247 0x204c  usbvideo - ok

14:19:37.0266 0x204c  [ EDBB23CBCF2CDF727D64FF9B51A6070E, 7202484C8E1BFB2AFD64D8C81668F3EDE0E3BF5EB27572877A0A7B337AE5AE42 ] UxSms           C:\windows\System32\uxsms.dll

14:19:37.0319 0x204c  UxSms - ok

14:19:37.0332 0x204c  [ 204F3F58212B3E422C90BD9691A2DF28, D748A8CEE4D59B4248C9B1ACA5155D0FF6635A29564B4391B7FAC6261F93FE99 ] VaultSvc        C:\windows\system32\lsass.exe

14:19:37.0341 0x204c  VaultSvc - ok

14:19:37.0373 0x204c  [ C5C876CCFC083FF3B128F933823E87BD, 6FE0FBB6C3207E09300E0789E2168F76668D87C317FE9F263E733827ADCFBE0D ] vdrvroot        C:\windows\system32\drivers\vdrvroot.sys

14:19:37.0396 0x204c  vdrvroot - ok

14:19:37.0420 0x204c  [ 8D6B481601D01A456E75C3210F1830BE, A2CEF483F4231367138EEF7E67FD5BE5364FC0780C44CA1368E36CE4AA3D0633 ] vds             C:\windows\System32\vds.exe

14:19:37.0491 0x204c  vds - ok

14:19:37.0501 0x204c  [ DA4DA3F5E02943C2DC8C6ED875DE68DD, EDE604536DB78C512D68C92B26DA77C8811AC109D1F0A473673F0A82D15A2838 ] vga             C:\windows\system32\DRIVERS\vgapnp.sys

14:19:37.0512 0x204c  vga - ok

14:19:37.0529 0x204c  [ 53E92A310193CB3C03BEA963DE7D9CFC, 45898604375B42EB1246C17A22D91C2440F11C746FF6459AD38027C1BC2E3125 ] VgaSave         C:\windows\System32\drivers\vga.sys

14:19:37.0562 0x204c  VgaSave - ok

14:19:37.0574 0x204c  [ 2CE2DF28C83AEAF30084E1B1EB253CBB, D1946816A1CB89F825CBEA58F94A4C9D0CE7249355CD3915563F54054EE564BF ] vhdmp           C:\windows\system32\drivers\vhdmp.sys

14:19:37.0585 0x204c  vhdmp - ok

14:19:37.0615 0x204c  [ E5689D93FFE4E5D66C0178761240DD54, 6D35CED80681B12AAF63BFA0DA1C386E71D3838839B68A686990AA8031949D27 ] viaide          C:\windows\system32\drivers\viaide.sys

14:19:37.0630 0x204c  viaide - ok

14:19:37.0658 0x204c  [ D2AAFD421940F640B407AEFAAEBD91B0, 31EF342A60AF04F4108759A71F8FB7B8C8819216CF3D16A95B2BA0E33A8A9161 ] volmgr          C:\windows\system32\drivers\volmgr.sys

14:19:37.0673 0x204c  volmgr - ok

14:19:37.0691 0x204c  [ A255814907C89BE58B79EF2F189B843B, 463DB771851352185B6AC323BD93B9084D47291E53C1F7B628B65D6918B2E28F ] volmgrx         C:\windows\system32\drivers\volmgrx.sys

14:19:37.0705 0x204c  volmgrx - ok

14:19:37.0714 0x204c  [ 0D08D2F3B3FF84E433346669B5E0F639, 3D6716CEC95B8861A7CC5778E91F310528DC6BEE0E57A3C8757FC675154EBDEC ] volsnap         C:\windows\system32\drivers\volsnap.sys

14:19:37.0727 0x204c  volsnap - ok

14:19:37.0744 0x204c  [ 5E2016EA6EBACA03C04FEAC5F330D997, 53106EB877459FE55A459111F7AB0EE320BB3B4C954D3DB6FA1642396001F2AC ] vsmraid         C:\windows\system32\drivers\vsmraid.sys

14:19:37.0756 0x204c  vsmraid - ok

14:19:37.0806 0x204c  [ B60BA0BC31B0CB414593E169F6F21CC2, 47B801E623254CF0202B3591CB5C019CABFB52F123C7D47E29D19B32F1F2B915 ] VSS             C:\windows\system32\vssvc.exe

14:19:37.0872 0x204c  VSS - ok

14:19:37.0884 0x204c  [ 36D4720B72B5C5D9CB2B9C29E9DF67A1, 3254523C85C70EBA2DBAC05DB2DBA89EDF8E9195F390F7C21F96458FB6B2E3D7 ] vwifibus        C:\windows\system32\DRIVERS\vwifibus.sys

14:19:37.0907 0x204c  vwifibus - ok

14:19:37.0927 0x204c  [ 6A3D66263414FF0D6FA754C646612F3F, 30F6BA594B0D3B94113064015A16D97811CD989DF1715CCE21CEAB9894C1B4FB ] vwififlt        C:\windows\system32\DRIVERS\vwififlt.sys

14:19:37.0947 0x204c  vwififlt - ok

14:19:37.0955 0x204c  [ 6A638FC4BFDDC4D9B186C28C91BD1A01, 5521F1DC515586777EC4837E0AEAA3E613CC178AF1074031C4D0D0C695A93168 ] vwifimp         C:\windows\system32\DRIVERS\vwifimp.sys

14:19:37.0967 0x204c  vwifimp - ok

14:19:37.0984 0x204c  [ 1C9D80CC3849B3788048078C26486E1A, 34A89F31E53F6B6C209B286F580CC2257AE6D057E4E20741F241C9C167947962 ] W32Time         C:\windows\system32\w32time.dll

14:19:38.0018 0x204c  W32Time - ok

14:19:38.0044 0x204c  [ 5E5704A38928D8452246867D94AEDC39, 7430301107C05785F197EDFF165CF0884C425F74609CB2EA23516B255D9F29FE ] WacHidRouter    C:\windows\system32\DRIVERS\wachidrouter.sys

14:19:38.0052 0x204c  WacHidRouter - ok

14:19:38.0055 0x204c  [ 4E9440F4F152A7B944CB1663D3935A3E, 8FE04EBD3BC612EE943A21A3E56F37E5C9B578CDACA6044048181DAD81816D53 ] WacomPen        C:\windows\system32\drivers\wacompen.sys

14:19:38.0074 0x204c  WacomPen - ok

14:19:38.0095 0x204c  [ 056891AD9FB65EEE3A927C9FB5131FC7, 5CEC0E460A7A247672357E04E1B6B11A6F22FBB65DE533E0216CE3B2A33EF438 ] wacomrouterfilter C:\windows\system32\DRIVERS\wacomrouterfilter.sys

14:19:38.0103 0x204c  wacomrouterfilter - ok

14:19:38.0125 0x204c  [ 356AFD78A6ED4457169241AC3965230C, CE4D1EE3525C10AC658B20776C3E444DE44874C837713DC5311386EDFCB18399 ] WANARP          C:\windows\system32\DRIVERS\wanarp.sys

14:19:38.0189 0x204c  WANARP - ok

14:19:38.0193 0x204c  [ 356AFD78A6ED4457169241AC3965230C, CE4D1EE3525C10AC658B20776C3E444DE44874C837713DC5311386EDFCB18399 ] Wanarpv6        C:\windows\system32\DRIVERS\wanarp.sys

14:19:38.0217 0x204c  Wanarpv6 - ok

14:19:38.0282 0x204c  [ 3CEC96DE223E49EAAE3651FCF8FAEA6C, 4150DAB33E8D61076F1D4767BCAFC9B4ECCCCBD58FD4FB3CFE5B8D27DCDCAB61 ] WatAdminSvc     C:\windows\system32\Wat\WatAdminSvc.exe

14:19:38.0331 0x204c  WatAdminSvc - ok

14:19:38.0388 0x204c  [ 78F4E7F5C56CB9716238EB57DA4B6A75, 46A4E78CE5F2A4B26F4E9C3FF04A99D9B727A82AC2E390A82A1611C3F6E0C9AF ] wbengine        C:\windows\system32\wbengine.exe

14:19:38.0466 0x204c  wbengine - ok

14:19:38.0485 0x204c  [ 3AA101E8EDAB2DB4131333F4325C76A3, 4F7BD3DA5E58B18BFF106CFF7B45E75FD13EE556D433C695BA23EC80827E49DE ] WbioSrvc        C:\windows\System32\wbiosrvc.dll

14:19:38.0505 0x204c  WbioSrvc - ok

14:19:38.0514 0x204c  [ 7368A2AFD46E5A4481D1DE9D14848EDD, 8039C478FC2D9F095F5883A4FA47F9E6EDF57CC88A4AA74F07C88445F90DED57 ] wcncsvc         C:\windows\System32\wcncsvc.dll

14:19:38.0552 0x204c  wcncsvc - ok

14:19:38.0568 0x204c  [ 20F7441334B18CEE52027661DF4A6129, 7B8E0247234B740FED2BE9B833E9CE8DD7453340123AB43F6B495A7E6A27B0DD ] WcsPlugInService C:\windows\System32\WcsPlugInService.dll

14:19:38.0588 0x204c  WcsPlugInService - ok

14:19:38.0590 0x204c  [ 72889E16FF12BA0F235467D6091B17DC, F2FD0BBD075E33608D93F350D216F97442AB89ABD540513C2D568C78096E12A8 ] Wd              C:\windows\system32\drivers\wd.sys

14:19:38.0598 0x204c  Wd - ok

14:19:38.0677 0x204c  [ E2C933EDBC389386EBE6D2BA953F43D8, AF1DEADD5F1267CCEBD226E8EEB971D1946EA6A5A9645A36F5D111F758AF2F07 ] Wdf01000        C:\windows\system32\drivers\Wdf01000.sys

14:19:38.0722 0x204c  Wdf01000 - ok

14:19:38.0741 0x204c  [ BF1FC3F79B863C914687A737C2F3D681, B2DF47AC4931ACFB243775767B77065CC0D98778FC0243C793A3E219EB961209 ] WdiServiceHost  C:\windows\system32\wdi.dll

14:19:38.0842 0x204c  WdiServiceHost - ok

14:19:38.0854 0x204c  [ BF1FC3F79B863C914687A737C2F3D681, B2DF47AC4931ACFB243775767B77065CC0D98778FC0243C793A3E219EB961209 ] WdiSystemHost   C:\windows\system32\wdi.dll

14:19:38.0887 0x204c  WdiSystemHost - ok

14:19:38.0919 0x204c  [ 0EB0E5D22B1760F2DBCE632F2DD7A54D, B8A4CC62F88768947FB0A161CF9564DB28FD9C1C037B5475DF192982DE035C22 ] WebClient       C:\windows\System32\webclnt.dll

14:19:38.0951 0x204c  WebClient - ok

14:19:38.0974 0x204c  [ C749025A679C5103E575E3B48E092C43, B71171D07EE7AB085A24BF3A1072FF2CE7EA021AAE695F6A90640E6EE8EB55C1 ] Wecsvc          C:\windows\system32\wecsvc.dll

14:19:39.0034 0x204c  Wecsvc - ok

14:19:39.0048 0x204c  [ 7E591867422DC788B9E5BD337A669A08, 484E6BCCDF7ADCE9A1AACAD1BC7C7D7694B9E40FA90D94B14D80C607784F6C75 ] wercplsupport   C:\windows\System32\wercplsupport.dll

14:19:39.0080 0x204c  wercplsupport - ok

14:19:39.0091 0x204c  [ 6D137963730144698CBD10F202E9F251, A9F522A125158D94F540544CCD4DBF47B9DCE2EA878C33675AFE40F80E8F4979 ] WerSvc          C:\windows\System32\WerSvc.dll

14:19:39.0118 0x204c  WerSvc - ok

14:19:39.0136 0x204c  [ 611B23304BF067451A9FDEE01FBDD725, 0AF2734B978165FC6FD22B64862132CCE32528A21C698A49D176129446E099C8 ] WfpLwf          C:\windows\system32\DRIVERS\wfplwf.sys

14:19:39.0161 0x204c  WfpLwf - ok

14:19:39.0174 0x204c  [ 05ECAEC3E4529A7153B3136CEB49F0EC, 9995CB2CEC70A633EA33CBB0DEAD2BB28CB67132B41E9444BDAB9E75744C9A50 ] WIMMount        C:\windows\system32\drivers\wimmount.sys

14:19:39.0182 0x204c  WIMMount - ok

14:19:39.0199 0x204c  WinDefend - ok

14:19:39.0208 0x204c  WinHttpAutoProxySvc - ok

14:19:39.0273 0x204c  [ 19B07E7E8915D701225DA41CB3877306, D6555E8D276DBB11358246E0FE215F76F1FB358791C76B88D82C2A66A42DA19F ] Winmgmt         C:\windows\system32\wbem\WMIsvc.dll

14:19:39.0341 0x204c  Winmgmt - ok

14:19:39.0399 0x204c  [ BCB1310604AA415C4508708975B3931E, 9D943F086D454345153A0DD426B4432532A44FD87950386B186E1CAD2AC70565 ] WinRM           C:\windows\system32\WsmSvc.dll

14:19:39.0491 0x204c  WinRM - ok

14:19:39.0526 0x204c  [ FE88B288356E7B47B74B13372ADD906D, A16B166F6BB32EF9D2A142F27B9EC54CBC7B3AC915799783CF4C40E525BC9E03 ] WinUsb          C:\windows\system32\DRIVERS\WinUsb.sys

14:19:39.0547 0x204c  WinUsb - ok

14:19:39.0587 0x204c  [ 4FADA86E62F18A1B2F42BA18AE24E6AA, CE1683386886BF34862681A46199EA7E7FB4232A186047DA7FBD8EC240AF6726 ] Wlansvc         C:\windows\System32\wlansvc.dll

14:19:39.0639 0x204c  Wlansvc - ok

14:19:39.0685 0x204c  [ 06C8FA1CF39DE6A735B54D906BA791C6, D8FEC7DE227781CDA876904701B2AA995268F74DCD6CB34AA0296C557FC283B6 ] wlcrasvc        C:\Program Files\Windows Live\Mesh\wlcrasvc.exe

14:19:39.0710 0x204c  wlcrasvc - ok

14:19:39.0864 0x204c  [ 2BACD71123F42CEA603F4E205E1AE337, 1FEF20554110371D738F462ECFFA999158EFEED02062414C58C1B61C422BF0B9 ] wlidsvc         C:\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE

14:19:39.0933 0x204c  wlidsvc - ok

14:19:39.0949 0x204c  [ F6FF8944478594D0E414D3F048F0D778, 6F75E0AE6127B33A92A88E59D4B048FD4C15F997807BE7BF0EFE76F95235B1D9 ] WmiAcpi         C:\windows\system32\drivers\wmiacpi.sys

14:19:39.0958 0x204c  WmiAcpi - ok

14:19:39.0977 0x204c  [ 38B84C94C5A8AF291ADFEA478AE54F93, 1AC267AC73670BEA5F3785C9AD9DB146F8E993A862C843742B21FDB90D102B2A ] wmiApSrv        C:\windows\system32\wbem\WmiApSrv.exe

14:19:40.0010 0x204c  wmiApSrv - ok

14:19:40.0026 0x204c  WMPNetworkSvc - ok

14:19:40.0033 0x204c  [ 96C6E7100D724C69FCF9E7BF590D1DCA, 2E63C9B0893B4FC03B7A71BAEA6202D3D3DB1B52F3643467829B5A573FD7655B ] WPCSvc          C:\windows\System32\wpcsvc.dll

14:19:40.0060 0x204c  WPCSvc - ok

14:19:40.0075 0x204c  [ 93221146D4EBBF314C29B23CD6CC391D, C0750858A65BF51E210CD244C825C121D67E025CD2D2455139991AAC289A90FE ] WPDBusEnum      C:\windows\system32\wpdbusenum.dll

14:19:40.0115 0x204c  WPDBusEnum - ok

14:19:40.0133 0x204c  [ 6BCC1D7D2FD2453957C5479A32364E52, E48554D31FBDCF8F985C1C72524CAA9106F5B7CC2B79064F8F5E2562D517F090 ] ws2ifsl         C:\windows\system32\drivers\ws2ifsl.sys

14:19:40.0174 0x204c  ws2ifsl - ok

14:19:40.0194 0x204c  [ E8B1FE6669397D1772D8196DF0E57A9E, 39FE0819360719F756BD31A1884A0508A1E2371ACC723E25E005CBEC0A7B02FA ] wscsvc          C:\windows\System32\wscsvc.dll

14:19:40.0214 0x204c  wscsvc - ok

14:19:40.0217 0x204c  WSearch - ok

14:19:40.0316 0x204c  [ 772473A9ADE89E21331AF0B24928C0A6, 84C9E65CACDC457383060B5DE53EAB88E6BAC7260246E9C3533C34EDB5CB1681 ] WTabletServicePro C:\Program Files\Tablet\Wacom\WTabletServicePro.exe

14:19:40.0357 0x204c  WTabletServicePro - ok

14:19:40.0485 0x204c  [ D9EF901DCA379CFE914E9FA13B73B4C4, 3BE9693B7B2AFEE23D72AF5DA211379724D752F0EC18ACB7D3DE3DDFC5AE0004 ] wuauserv        C:\windows\system32\wuaueng.dll

14:19:40.0545 0x204c  wuauserv - ok

14:19:40.0587 0x204c  [ AB886378EEB55C6C75B4F2D14B6C869F, D6C4602EB8F291DADEDF3CD211013D4AC752DDE7E799C2D8D74AA4F5477CAED6 ] WudfPf          C:\windows\system32\drivers\WudfPf.sys

14:19:40.0622 0x204c  WudfPf - ok

14:19:40.0659 0x204c  [ DDA4CAF29D8C0A297F886BFE561E6659, 94E5DD649B5D86FA1A7C7D30FCF9644D0EE048D312E626111458ADF66BFBE978 ] WUDFRd          C:\windows\system32\DRIVERS\WUDFRd.sys

14:19:40.0680 0x204c  WUDFRd - ok

14:19:40.0718 0x204c  [ B20F051B03A966392364C83F009F7D17, 88ECEB55AE91F58F592B96EBC10B572747D5A2F9B7629E8F371761E4F7408A65 ] wudfsvc         C:\windows\System32\WUDFSvc.dll

14:19:40.0751 0x204c  wudfsvc - ok

14:19:40.0800 0x204c  [ 04F82965C09CBDF646B487E145060301, 2CD8533EDBE24C3E42EB7550E20F8A2EB9E5E345B165DEF543163A6BC1FDD18B ] WwanSvc         C:\windows\System32\wwansvc.dll

14:19:40.0862 0x204c  WwanSvc - ok

14:19:40.0922 0x204c  [ 2EE48CFCE7CA8E0DB4C44C7476C0943B, 2C324592F3F2D50BABA7123B6F9FC922667CC132777E019FF615F2D6F273A45E ] xusb21          C:\windows\system32\DRIVERS\xusb21.sys

14:19:40.0969 0x204c  xusb21 - ok

14:19:41.0006 0x204c  ================ Scan global ===============================

14:19:41.0026 0x204c  [ BA0CD8C393E8C9F83354106093832C7B, 18D8A4780A2BAA6CEF7FBBBDA0EF6BF2DADF146E1E578A618DD5859E8ADBF1A8 ] C:\windows\system32\basesrv.dll

14:19:41.0056 0x204c  [ 88EDD0B34EED542745931E581AD21A32, DC2B93E1CEF5B0BCEE08D72669BB0F3AD0E8E6E75BDC08858407ED92F6FFA031 ] C:\windows\system32\winsrv.dll

14:19:41.0075 0x204c  [ 88EDD0B34EED542745931E581AD21A32, DC2B93E1CEF5B0BCEE08D72669BB0F3AD0E8E6E75BDC08858407ED92F6FFA031 ] C:\windows\system32\winsrv.dll

14:19:41.0118 0x204c  [ D6160F9D869BA3AF0B787F971DB56368, 0033E6212DD8683E4EE611B290931FDB227B4795F0B17C309DC686C696790529 ] C:\windows\system32\sxssrv.dll

14:19:41.0164 0x204c  [ 24ACB7E5BE595468E3B9AA488B9B4FCB, 63541E3432FCE953F266AE553E7A394978D6EE3DB52388D885F668CF42C5E7E2 ] C:\windows\system32\services.exe

14:19:41.0178 0x204c  [ Global ] - ok

14:19:41.0178 0x204c  ================ Scan MBR ==================================

14:19:41.0206 0x204c  [ A36C5E4F47E84449FF07ED3517B43A31 ] \Device\Harddisk0\DR0

14:19:41.0425 0x204c  \Device\Harddisk0\DR0 - ok

14:19:41.0426 0x204c  ================ Scan VBR ==================================

14:19:41.0431 0x204c  [ 9CD3B264BCFD9CEF73389C6378DEAAD7 ] \Device\Harddisk0\DR0\Partition1

14:19:41.0507 0x204c  \Device\Harddisk0\DR0\Partition1 - ok

14:19:41.0508 0x204c  ================ Scan generic autorun ======================

14:19:41.0855 0x204c  [ 8BB9E0F47808FE4F973C4A281CC7A413, 6860774878156B58C6043AF97C6441667E3C15C28BBC0C06F99CDC9DA19908A4 ] C:\Program Files\Realtek\Audio\HDA\RAVCpl64.exe

14:19:42.0144 0x204c  RTHDVCPL - ok

14:19:42.0152 0x204c  BTMTrayAgent - ok

14:19:42.0166 0x204c  [ DD81D91FF3B0763C392422865C9AC12E, F5691B8F200E3196E6808E932630E862F8F26F31CD949981373F23C9D87DB8B9 ] C:\windows\system32\RunDLL32.exe

14:19:42.0176 0x204c  THXCfg64 - ok

14:19:42.0292 0x204c  [ C0E76667478E06BE6C384D323A6FEB8E, DE176CBD57F379C9FAF30D31F70F771F0E5703161904CFDB25F87C85263585B1 ] C:\Program Files\ATT-SST\pcTrayApp.exe

14:19:42.0371 0x204c  ATT-SST_McciTrayApp - detected UnsignedFile.Multi.Generic ( 1 )

14:19:45.0450 0x204c  Detect skipped due to KSN trusted

14:19:45.0450 0x204c  ATT-SST_McciTrayApp - ok

14:19:45.0611 0x204c  [ 1315C5C5C54CE2AA37A155F97027DB59, 70CDA6AE7FF4FD08FAD931477C524957952EDC89985696FD988B9786A349C565 ] C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\UWA\UpdaterStartupUtility.exe

14:19:45.0641 0x204c  AdobeAAMUpdater-1.0 - ok

14:19:45.0644 0x204c  IntelTBRunOnce - ok

14:19:45.0772 0x204c  [ 3895C05252E7EC7EE65973775B4548B0, 5F397496D01CF77202BC44A9AF1A82142257698F18E8FF0CC4358A3406F86C79 ] C:\windows\system32\spool\DRIVERS\x64\3\EKIJ5000MUI.exe

14:19:45.0841 0x204c  EKIJ5000StatusMonitor - ok

14:19:45.0930 0x204c  [ 569AC1376B12D4083FC66CC7A304F234, DD209F09573F10A77D710E30EF3D0461D2E8F4E5F18106B18EFB587C88393460 ] c:\Program Files\Microsoft Security Client\msseces.exe

14:19:45.0971 0x204c  MSC - ok

14:19:46.0016 0x204c  [ 9D51EA92A612B37E76E5E4621650C50A, 00BD61C8527A80C0F684882379A0AC2E5A54E8BBECC797087B960CDC8454C373 ] C:\Program Files (x86)\Renesas Electronics\USB 3.0 Host Controller Driver\Application\nusb3mon.exe

14:19:46.0041 0x204c  NUSB3MON - ok

14:19:46.0086 0x204c  [ 41D1214B86A06FD29423A797EBDA17E4, ABC79107DDD5890C54B844CD5C69747121083DA69A77C02068D2B9C349FB1614 ] C:\Program Files (x86)\Intel\Intel® Rapid Storage Technology\IAStorIcon.exe

14:19:46.0119 0x204c  IAStorIcon - ok

14:19:46.0185 0x204c  [ E3384F7FCB5FD30B0AA3717296FBA6E3, 3DADEF9692A4F5C386873303D92C1DF5A03B37436993CB3A071306B7EC7A4D97 ] C:\Program Files (x86)\MSI\KLM\KLM.exe

14:19:46.0238 0x204c  KLM - detected UnsignedFile.Multi.Generic ( 1 )

14:19:49.0145 0x204c  Detect skipped due to KSN trusted

14:19:49.0145 0x204c  KLM - ok

14:19:49.0266 0x204c  [ AC87232BD9C0B414CF4AC94197DD0691, F286AEB2AEFA9BB1A85065912AF27C3731E96C0988435EA1126CC61EECF1F5E3 ] C:\Program Files (x86)\MSI\Cinema ProII\CinemaProII.exe

14:19:49.0304 0x204c  Cinema ProII AP - detected UnsignedFile.Multi.Generic ( 1 )

14:19:52.0514 0x204c  Detect skipped due to KSN trusted

14:19:52.0514 0x204c  Cinema ProII AP - ok

14:19:52.0644 0x204c  [ 9871051748647566F74A326711C0C288, F3CAE8CAE20B25DC590F912D343DCA09489F2E073B094B99C7EF4431E8E14F20 ] C:\Program Files (x86)\MSI\Cinema ProII\Cinema ProII Controler.exe

14:19:52.0701 0x204c  Cinema ProII Controler - detected UnsignedFile.Multi.Generic ( 1 )

14:19:55.0608 0x204c  Detect skipped due to KSN trusted

14:19:55.0608 0x204c  Cinema ProII Controler - ok

14:19:55.0691 0x204c  [ 4529E92CC74B82B917509FFF9E232E13, 52F51DA95E89B256181561F50C5D268E3519A808CC64F6B8F196C77F8B1E458C ] C:\Program Files (x86)\Creative\THX TruStudio Pro\THXAudioCP\THXAudio.exe

14:19:55.0736 0x204c  THX Audio Control Panel - detected UnsignedFile.Multi.Generic ( 1 )

14:19:58.0619 0x204c  Detect skipped due to KSN trusted

14:19:58.0619 0x204c  THX Audio Control Panel - ok

14:19:58.0677 0x204c  [ DB414E4AEA9BAACE6F9670A420A59F52, 653879F138C1F396AAD420E5F263795B63C11E4527B679E632BDF88058795BA1 ] C:\Program Files (x86)\MSI\NVIDIA Overclock Tool\NVIDIAOCAP.exe

14:19:58.0696 0x204c  NVIDIAOCAP - detected UnsignedFile.Multi.Generic ( 1 )

14:20:01.0876 0x204c  Detect skipped due to KSN trusted

14:20:01.0876 0x204c  NVIDIAOCAP - ok

14:20:02.0011 0x204c  [ 757A595F75E7840A7132EC11E6E6188A, 95085E8B5432F76E0C50D79F74DECAD54662BB32FFDD575BC8CBAC2C79B1C069 ] C:\Program Files (x86)\Nuance\PDF Reader\Ereg\Ereg.exe

14:20:02.0042 0x204c  Nuance PDF Reader-reminder - ok

14:20:02.0063 0x204c  [ F577910A133A592234EBAAD3F3AFA258, 36F514740EE2D2B2F7ABFFFA13D575233EC4CE774EB58BF889C09930FEF1F443 ] C:\Program Files (x86)\Common Files\Adobe\SwitchBoard\SwitchBoard.exe

14:20:02.0080 0x204c  SwitchBoard - detected UnsignedFile.Multi.Generic ( 1 )

14:20:02.0080 0x204c  Detect skipped due to KSN trusted

14:20:02.0080 0x204c  SwitchBoard - ok

14:20:02.0161 0x204c  [ 8FE651ACBA3344E645CFEB6286FFF6B8, ECE4DFFEB7EB0B19B6790FD0F619A5C4B23CA0BA9CC3F25924925F8EA07264B6 ] C:\Program Files (x86)\Common Files\Adobe\CS6ServiceManager\CS6ServiceManager.exe

14:20:02.0192 0x204c  AdobeCS6ServiceManager - ok

14:20:02.0280 0x204c  [ 48BE298F7FD1BEF4D8FBACB04D8D95C4, D375B3F6E850E4B0EC81BAA0E554C356BE2248AA77C6C56F5267CA05460FE4EB ] C:\Program Files (x86)\Common Files\Adobe\ARM\1.0\AdobeARM.exe

14:20:02.0330 0x204c  Adobe ARM - ok

14:20:02.0479 0x204c  [ 57AF9F47253E53E94D22C790FA5D6024, 70505CBDE8F8614DE1203A7544F373DF6DCF1E542A6E4ACA8FAA60A65E22B10D ] C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\Acrotray.exe

14:20:02.0517 0x204c  Acrobat Assistant 8.0 - ok

14:20:02.0545 0x204c  [ 5B6E8E09BE6401A7E022F52FDFCB2FF8, 471C556CF9405BBB380A8CEFE945C126B954B7C94F79CC72441B51F80141FC5E ] C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe

14:20:02.0556 0x204c  SunJavaUpdateSched - ok

14:20:02.0779 0x204c  [ 8A38C0A5CBA7AEEC1B567035C00D0B15, BB8368E5910B4642B1869410149CED38FA17AF58E85EC80C44C6D4ADD684AE80 ] C:\Program Files (x86)\S-Bar\S-Bar.exe

14:20:02.0926 0x204c  S-Bar - detected UnsignedFile.Multi.Generic ( 1 )

14:20:09.0679 0x204c  Detect skipped due to KSN trusted

14:20:09.0679 0x204c  S-Bar - ok

14:20:09.0828 0x204c  [ 916A2C4EB028604783FD5EA169236C1D, C97DAA1BE5C912DDCEDBA7619631BB98F4A9B32B1E40C5374A64E25305E0A1C4 ] C:\Program Files (x86)\QuickTime\qttask.exe

14:20:09.0881 0x204c  QuickTime Task - detected UnsignedFile.Multi.Generic ( 1 )

14:20:13.0057 0x204c  Detect skipped due to KSN trusted

14:20:13.0057 0x204c  QuickTime Task - ok

14:20:13.0252 0x204c  [ DCCA4B04AF87E52EF9EAA2190E06CBAC, 8858CFD159BB32AE9FCCA1A79EA83C876D481A286E914071D48F42FCA5B343D8 ] C:\Program Files (x86)\Windows Sidebar\Sidebar.exe

14:20:13.0329 0x204c  Sidebar - ok

14:20:13.0350 0x204c  [ 0FA760BF380B08D0B67B5507CD8B32AA, 0F73A7F64C4FDAB98CD3A865CC54B3A7195761530FCB115B725CC5A9FB738739 ] C:\Windows\System32\mctadmin.exe

14:20:13.0366 0x204c  mctadmin - ok

14:20:13.0386 0x204c  [ DCCA4B04AF87E52EF9EAA2190E06CBAC, 8858CFD159BB32AE9FCCA1A79EA83C876D481A286E914071D48F42FCA5B343D8 ] C:\Program Files (x86)\Windows Sidebar\Sidebar.exe

14:20:13.0418 0x204c  Sidebar - ok

14:20:13.0422 0x204c  [ 0FA760BF380B08D0B67B5507CD8B32AA, 0F73A7F64C4FDAB98CD3A865CC54B3A7195761530FCB115B725CC5A9FB738739 ] C:\Windows\System32\mctadmin.exe

14:20:13.0435 0x204c  mctadmin - ok

14:20:13.0540 0x204c  [ 1C10324F2D829B2820B8E626F5CA9445, 37BE9A93E1F2D46557567EED9F3BE6B4ED3C74A0C7F75FFAA72685426FAD50BB ] C:\Program Files (x86)\Steam\steam.exe

14:20:13.0585 0x204c  Steam - ok

14:20:13.0599 0x204c  EA Core - ok

14:20:13.0674 0x204c  [ 16DEFCB5F3FAC44D5EB35B19DA337FE5, CE8531B8FBA4896D4A1AB0C5CCEFC5DF0C74063D717EC9BA386B4E25D7F93651 ] C:\Program Files (x86)\Adobe\Elements Organizer 8.0\CAHeadless\ElementsAutoAnalyzer.exe

14:20:13.0702 0x204c  CAHeadless - ok

14:20:13.0759 0x204c  [ 5D61BE7DB55B026A5D61A3EED09D0EAD, D32CC7B31A6F98C60ABC313ABC7D1143681F72DE2BB2604711A0BA20710CAAAE ] C:\Program Files (x86)\Google\GoogleToolbarNotifier\GoogleToolbarNotifier.exe

14:20:13.0787 0x204c  swg - ok

14:20:13.0890 0x204c  [ 506708142BC63DABA64F2D3AD1DCD5BF, 9C36A08D9E7932FF4DA7B5F24E6B42C92F28685B8ABE964C870E8D7670FD531A ] C:\Users\Chelsey\AppData\Local\Google\Update\GoogleUpdate.exe

14:20:13.0913 0x204c  Google Update - ok

14:20:13.0941 0x204c  [ 7E6ACA6B6C89B7CD098944A9159DAED3, 31AAF03FEC04021D9A4BE249815DDD485BDEBE0BF3C9311B10E954BDE9A5EA13 ] C:\Program Files (x86)\TomTom HOME 2\TomTomHOMERunner.exe

14:20:13.0965 0x204c  TomTomHOME.exe - ok

14:20:13.0966 0x204c  Waiting for KSN requests completion. In queue: 8

14:20:14.0966 0x204c  Waiting for KSN requests completion. In queue: 8

14:20:15.0966 0x204c  Waiting for KSN requests completion. In queue: 8

14:20:16.0995 0x204c  AV detected via SS2: Microsoft Security Essentials, C:\Program Files\Microsoft Security Client\msseces.exe ( 4.5.216.0 ), 0x61000 ( enabled : updated )

14:20:17.0052 0x204c  Win FW state via NFP2: disabled

14:20:19.0997 0x204c  ============================================================

14:20:19.0997 0x204c  Scan finished

14:20:19.0997 0x204c  ============================================================

14:20:20.0018 0x2bc4  Detected object count: 1

14:20:20.0018 0x2bc4  Actual detected object count: 1

14:20:57.0979 0x2bc4  SwitchBoard ( UnsignedFile.Multi.Generic ) - skipped by user

14:20:57.0979 0x2bc4  SwitchBoard ( UnsignedFile.Multi.Generic ) - User select action: Skip 

[Chelsey]

I am just realizing now that I forgot to disable Microsoft Security Essentials before the TDSSKILLER scan...I did disable my Firewall. Should I do the scan again with Microsoft Security Essentials off? I am sorry for this.

[Maurice Naggar]

Hello Chelsey,

 

You must always have on the Windows firewall.   Job 1, please.

 

That is ok about the MS Security Essentials.   Stay tuned for later reply.

[Maurice Naggar]

Hello Chelsey,

 

Are you ready to go forward?   This should fix your lack of Update issue in the Anti-Malware program.

 

To get the latest database updates please do these steps.
NOTE: SAVE the tool-downloads here to your system first. Do not "run" them while in the browser program.
When presented with the option to Run or Save, you must select Save.

Download and Save a zip file from this link http://downloads.malwarebytes.org/file/mbam_rules
The name is mbam-rules-YYYY-MM-DD.zip

Unzip the file ( extracting all content) to your system.  Once done, turn off the realtime protections of the Anti-Malware program ( temporarily) by doing this:
Go to the desktop Taskbar. See the blue-color MBAM icon in the notification area.
Do a Right-click on it with your mouse, and select EXIT.
{ if you are only running the Free mode program, you will not see that, so in that case you can ignore that step.}.

Double click Mbam2-rules.exe
That will automatically place the database files into the Anti-Malware.

Once this is all done, you need to do a windows LOGOFF >> Shutdown >> Restart for a new session in windows.

Note: _Disregard and do not use the file named mbam-rules.exe._

Please tell me the result. If there is a problem, please provide all details about it and the exact text of the error message.

NOTE:
If you are unsure how to extract the contents of the .zip folder, please see this tutorial from Microsoft:
http://windows.microsoft.com/en-us/windows/compress-uncompress-files-zip-files
 

 

P.S. Do not uninstall anything of the tools I had you use before.  I will be guiding you at the end about how to clean up after those tools.

 

[Chelsey]

Hello Chelsey,

 

You must always have on the Windows firewall.   Job 1, please.

 

That is ok about the MS Security Essentials.   Stay tuned for later reply.

 Just to let you know, I was just trying to following the instructions provided to me in your last post on June 30th. I thought I was to disable all listed in the quote below. Normally I would never disable my Firewall, I haven't before and it was off for less than one minute while that TDSSKILLER ran. Then I put it immediately back on.

 

"Temporarily disable (turn off) your antivirus app so that it does not interfere:

How To Temporarily Disable Your Anti-virus, Firewall And Anti-malware Programs

http://www.bleepingc...howtopic=114351"

 

Now, moving on to the new instructions-I saved the Mbam Rules file to my desktop and extracted the files, but the next step that says to exit Mbam from the taskbar...it doesn't even show up in the taskbar anymore after the last Ref Replace file I added when that download of that file completely stopped Mbam from opening at all. So since the program won't even start now, is this still going to work/still the step we should take? Should I still proceed with the Mbam Rules.exe step? I Just want to make sure to let you know that the problem is not only that Mbam will not update anymore, but now it will not even start at all. Thank you for your help, and I will continue to reply within 24 hours as you asked...I am checking my email frequently now to stay fresh on this topic. Please just reassure me that I am to continue on with the Mbam Rule.exe step now even though the program will now not start, as well as the original problem-that it wouldn't update. Thank you!

[Chelsey]

And just to make sure, I should not just uninstall and re-install Mbam Antivirus since it won't even open now? Thanks again

[Maurice Naggar]

That title only has "firewall" as part of the article title.  I am sorry that you took that literally.

The intent was Only to "temporarily" turn off only the antivirus.

 

We never ( hardly ever) ask you to turn off a firewall !!

 

Now then, just go ahead and do what I outlined.  Which was to get the zip file with the "rules" and do all I listed in my last reply.

 

OK.  Thanks.

[Chelsey]

Okay, I double clicked the Mbam 2 .exe and it pronpted me to install the Anti Malware Rules...I finished that and then closed the window, shut down and restarted the computer, logged on and Mbam still does not start or show up (if it was supposed to). Otherwise, there was no error or anything with the download.

[Maurice Naggar]

Please explain the How and the what of  <<Mbam still does not start or show up>>

 

Is there not a blue-icon on the Desktop for Malwarebytes?    ( a shortcut link )

 

what happens when you double-click on it?

[Chelsey]

Yes, that's what I was bringing up before I went ahead with the Mbam 2.exe. Initially, the problem I was having with Mbam was the fact that it would not update-and that I could not scan without it prompting to update, and when it tried to update it crashed. But the program would still start up automatically whenever I booted up my computer. And I could open the program and let it sit there open. 

 

After I downloaded the Ref Replace file, the program stopped even starting up at all and if I tried to manually open it-it would not open. So now it will not even start up on its own and can not be started manually either. Thats why I was asking about uninstalling the program and re-installing it. What do you think I should do next?

[Maurice Naggar]

Hello Chelsey,

 

In that case, I would recommend a new try with a clean removal and new setup for the Anti-Malware.

**Please always tell me the exact error message you get and the conditions of how it appears / how it happens.**
It is so important to get details from you each and every time  { and not just "error" or, <same as before> }.


If you have recently installed Malwarebytes Anti-Malware and are experiencing problems, then please follow the steps below. If you have purchased a Premium license, at the end of this process you will need to reactivate your license to enable the Premium features. Please have your ID and Key readily available. If you do not have your ID and Key, you may retrieve them from this webpage:

http://www.cleverbridge.com/342/?scope=cusecolp

Please note you will only be able to retrieve your ID and Key if you purchased Malwarebytes directly from our website or through an authorized reseller / affiliate. If you purchased a physical copy or from anywhere else, we will not have any record of your sale and cannot retrieve your ID and Key if lost.


NOTE: SAVE the downloads to your system first. Do not "run" them while in the browser program.
When presented with the option to Run or Save, you must select Save.


1: Please perform a clean uninstall before reinstalling the latest version.  Do not use Windows Add/Remove Programs.  Instead, please download and run "mbam-clean.exe" from the link below:

http://downloads.malwarebytes.org/file/mbam_clean

2: After running the program, it will ask to restart your computer.  Please allow it to do so (this is very important).

After the computer restarts, temporarily disable your Anti-Virus
If you need how-to guidance, see => How To Temporarily Disable Your Anti-virus, Firewall And Anti-malware Programs
 http://www.bleepingcomputer.com/forums/index.php?showtopic=114351


3: Download and SAVE to your system  the latest version of Malwarebytes Anti-Malware from the link below:

https://www.malwarebytes.org/getmbam

Now run the setup:
IF your Windows is Vista / Windows 7 / 8, then do a Right-click on **mbam-setup.exe-2.0.2.1012.exe**  and select Run as Administrator and allow to run.
Answer YES _when prompted_ by User Account Control ( Windows ).


4: After Malwarebytes has finished installing, launch the application.

5: Click Activate in the upper right corner

6: Copy your ID into the ID field

7: Copy your Key into the Key field

8: Click the Activate button to activate your Malwarebytes Anti-Malware Premium license


**When all finished, turn back ON your antivirus program.**


If this did not resolve your issue, please download and save our diagnostic tool, mbam-check.exe, to your desktop from this link.

http://downloads.malwarebytes.org/file/mbam_check

Double-click mbam-check.exe to launch the tool. A black command prompt window will briefly appear, and then a log file will open. The log which opens will be saved to your desktop as CheckResults.txt.  Please attach that log file to your next reply so that we may troubleshoot the issue further.

If you'd like to view a how-to video on how to uninstall, install, or activate Malwarebytes, please see below:

How to uninstall - https://helpdesk.malwarebytes.org/entries/25291497
How to install - https://helpdesk.malwarebytes.org/entries/20840058
How to activate - https://helpdesk.malwarebytes.org/entries/20839618