Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

PC #2 Pretty Sure its Infected- Help Please


  • Please log in to reply
45 replies to this topic

#1 SenorSySoP

SenorSySoP

  • Members
  • 42 posts
  • OFFLINE
  •  
  • Local time:08:40 AM

Posted 25 October 2017 - 11:26 PM

Hello kind folks.  We have four computers and all were screwed up with malware/virus.  You all helped me fix the first one and its working great.   Here is the second PC.  I hope you can help.  Note:  I can not boot this machine to windows.   If I try I get an elam sys error.  If I press on, I get a black screen where the windows desktop would be.  Nonetheless, here is the farbar log for your guidance.  I redacted my pc name for privacy reasons  Thanks SS

 

 

Scan result of Farbar Recovery Scan Tool (FRST) (x64) Version: 16-10-2017
Ran by SYSTEM on MININT-6B1KDQN (25-10-2017 22:08:46)
Running from E:\
Platform: Windows 10 Home Version 1703 170317-1834 (X64) Language: English (United States)
Internet Explorer Version 11
Boot Mode: Recovery
Default: ControlSet001
ATTENTION!:=====> If the system is bootable FRST must be run from normal or Safe mode to create a complete log.
==================== Registry (Whitelisted) ===========================
(If an entry is included in the fixlist, the registry item will be restored to default or removed. The file will not be moved.)
HKLM\...\Run: [SecurityHealth] => C:\Program Files\Windows Defender\MSASCuiL.exe [629152 2017-03-18] (Microsoft Corporation)
HKLM\...\Run: [RTHDVCPL] => C:\Program Files\Realtek\Audio\HDA\RtkNGUI64.exe [8492800 2015-06-24] (Realtek Semiconductor)
HKLM\...\Run: [iTunesHelper] => C:\Program Files\iTunes\iTunesHelper.exe [303928 2017-05-09] (Apple Inc.)
HKLM\...\Run: [Malwarebytes TrayApp] => C:\PROGRAM FILES\MALWAREBYTES\ANTI-MALWARE\mbamtray.exe [3146704 2017-05-09] (Malwarebytes)
HKLM-x32\...\Run: [StartCCC] => C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\amd64\CLIStart.exe [767176 2015-11-04] (Advanced Micro Devices, Inc.)
HKLM-x32\...\Run: [ASUSWebStorage] => C:\Program Files (x86)\ASUS\WebStorage Sync Agent\1.1.10.123\AsusWSPanel.exe [3423104 2012-08-30] (ASUS Cloud Corporation)
HKLM-x32\...\Run: [ASUS AiChargerPlus Execute] => C:\Program Files (x86)\InstallShield Installation Information\{E6931688-DA2B-4E16-8539-3D323D69C677}\AiChargerPlus.exe [550272 2012-08-20] (ASUSTek Computer Inc.)
HKLM-x32\...\Run: [ASUSPRP] => C:\Program Files (x86)\ASUS\APRP\APRP.EXE [3187360 2013-01-17] (ASUSTek Computer Inc.)
HKLM-x32\...\Run: [RemoteControl10] => C:\Program Files (x86)\CyberLink\PowerDVD10\PDVD10Serv.exe [91432 2012-03-28] (CyberLink Corp.)
HKLM-x32\...\Run: [APSDaemon] => C:\Program Files (x86)\Common Files\Apple\Apple Application Support\APSDaemon.exe [67896 2017-05-08] (Apple Inc.)
HKLM-x32\...\Run: [BlueStacks Agent] => C:\Program Files (x86)\BlueStacks\HD-Agent.exe [601928 2013-08-07] (BlueStack Systems, Inc.)
HKLM-x32\...\Run: [Wondershare Helper Compact.exe] => C:\Program Files (x86)\Common Files\Wondershare\Wondershare Helper Compact\WSHelper.exe [2131344 2016-06-20] (Wondershare)
HKLM-x32\...\Run: [QuickTime Task] => C:\Program Files (x86)\QuickTime\QTTask.exe [421888 2013-05-01] (Apple Inc.)
HKLM-x32\...\Run: [BrowserPlugInHelper] => C:\Program Files (x86)\Wondershare\Video Converter Ultimate\BrowserPlugInHelper.exe [1962896 2013-12-09] ()
HKLM-x32\...\Run: [HP Software Update] => C:\Program Files (x86)\Hp\HP Software Update\HPWuSchd2.exe [96056 2013-05-30] (Hewlett-Packard)
HKLM-x32\...\Run: [Adobe Acrobat Speed Launcher] => C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\Acrobat_sl.exe [41360 2015-09-24] (Adobe Systems Incorporated)
HKLM-x32\...\Run: [Acrobat Assistant 8.0] => C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\Acrotray.exe [840592 2015-09-24] (Adobe Systems Inc.)
HKLM-x32\...\Run: [SunJavaUpdateSched] => C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe [587288 2017-07-21] (Oracle Corporation)
HKLM\...\Policies\Explorer: [NoSetActiveDesktop] 0
GroupPolicy: Restriction <==== ATTENTION
==================== Services (Whitelisted) ====================
(If an entry is included in the fixlist, it will be removed from the registry. The file will not be moved unless listed separately.)
S2 Agent; C:\Windows\VPDAgent_x64.exe [148480 2013-06-25] (Two Pilots)
S2 AMD FUEL Service; C:\Program Files\ATI Technologies\ATI.ACE\Fuel\Fuel.Service.exe [351944 2015-11-04] (Advanced Micro Devices, Inc.)
S2 Apple Mobile Device Service; C:\Program Files\Common Files\Apple\Mobile Device Support\AppleMobileDeviceService.exe [83768 2017-04-03] (Apple Inc.)
S2 asComSvc; C:\Program Files (x86)\ASUS\AXSP\1.00.19\atkexComSvc.exe [920736 2012-06-01] ()
S2 asHmComSvc; C:\Program Files (x86)\ASUS\AAHM\1.00.20\aaHMSvc.exe [951936 2012-06-01] (ASUSTeK Computer Inc.)
S2 AsSysCtrlService; C:\Program Files (x86)\ASUS\AsSysCtrlService\1.00.13\AsSysCtrlService.exe [149120 2012-02-16] (ASUSTeK Computer Inc.)
S2 BstHdAndroidSvc; C:\Program Files (x86)\BlueStacks\HD-Service.exe [393032 2013-08-07] (BlueStack Systems, Inc.)
S2 BstHdLogRotatorSvc; C:\Program Files (x86)\BlueStacks\HD-LogRotatorService.exe [384840 2013-08-07] (BlueStack Systems, Inc.)
S2 DirMngr; C:\Program Files (x86)\GNU\GnuPG\dirmngr.exe [218112 2013-10-07] ()
S2 DymoPnpService; C:\Program Files (x86)\DYMO\DYMO Label Software\DymoPnpService.exe [33072 2013-03-04] (Sanford, L.P.)
S2 HitmanProScheduler; C:\Program Files\HitmanPro\hmpsched.exe [135488 2017-05-18] (SurfRight B.V.)
S2 MBAMService; C:\Program Files\Malwarebytes\Anti-Malware\mbamservice.exe [4470736 2017-05-09] (Malwarebytes)
S2 N360; C:\Program Files (x86)\Norton Security Suite\Engine\22.10.0.85\N360.exe [326144 2017-07-14] (Symantec Corporation)
S2 Neat Startup Service; C:\Program Files (x86)\Neat\exec\NeatStartupService.exe [6144 2014-08-06] (The Neat Company)
S2 SbieSvc; C:\Program Files\Sandboxie\SbieSvc.exe [187592 2014-01-17] (Sandboxie Holdings, LLC)
S2 TiMiniService; C:\Program Files\Trend Micro\Titanium\TiMiniService.exe [248640 2012-07-25] (Trend Micro Inc.)
S3 WdNisSvc; C:\Program Files\Windows Defender\NisSrv.exe [342264 2017-03-18] (Microsoft Corporation)
S3 WinDefend; C:\Program Files\Windows Defender\MsMpEng.exe [102816 2017-07-10] (Microsoft Corporation)
===================== Drivers (Whitelisted) ======================
(If an entry is included in the fixlist, it will be removed from the registry. The file will not be moved unless listed separately.)
S3 AiChargerPlus; C:\Windows\SysWow64\drivers\AiChargerPlus.sys [14848 2012-04-19] (ASUSTek Computer Inc.)
S2 AODDriver4.3; C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys [59616 2014-02-11] (Advanced Micro Devices)
S1 AsIO; C:\Windows\SysWow64\drivers\AsIO.sys [15232 2012-08-22] ()
S1 AsUpIO; C:\Windows\SysWow64\drivers\AsUpIO.sys [14464 2010-08-02] ()
S3 AtiHDAudioService; C:\Windows\system32\drivers\AtihdWT6.sys [102912 2015-05-28] (Advanced Micro Devices)
S3 AU8168; C:\Windows\system32\DRIVERS\au630x64.sys [792648 2013-09-23] (Realtek )
S1 BHDrvx64; C:\Program Files (x86)\Norton Security Suite\NortonData\22.10.0.85\Definitions\BASHDefs\20170813.001\BHDrvx64.sys [1862816 2017-08-02] (Symantec Corporation)
S2 BstHdDrv; C:\Program Files (x86)\BlueStacks\HD-Hypervisor-amd64.sys [70984 2013-08-07] (BlueStack Systems)
S1 ccSet_N360; C:\Windows\system32\drivers\N360x64\160A000.055\ccSetx64.sys [187520 2017-07-14] (Symantec Corporation)
S1 eeCtrl; C:\Program Files (x86)\Common Files\Symantec Shared\EENGINE\eeCtrl64.sys [508032 2017-06-16] (Symantec Corporation)
S1 ESProtectionDriver; C:\WINDOWS\system32\drivers\mbae64.sys [77376 2017-06-27] ()
S1 IDSVia64; C:\Program Files (x86)\Norton Security Suite\NortonData\22.10.0.85\Definitions\IPSDefs\20170816.001\IDSvia64.sys [1056920 2017-08-03] (Symantec Corporation)
S1 MBAMChameleon; C:\Windows\system32\drivers\MBAMChameleon.sys [188352 2017-08-16] (Malwarebytes)
S3 MBAMFarflt; C:\WINDOWS\system32\drivers\farflt.sys [101784 2017-10-25] (Malwarebytes)
S3 MBAMProtection; C:\WINDOWS\system32\drivers\mbam.sys [45472 2017-10-25] (Malwarebytes)
S0 MBAMSwissArmy; C:\Windows\System32\drivers\MBAMSwissArmy.sys [253856 2017-10-25] (Malwarebytes)
S3 MBAMWebProtection; C:\WINDOWS\system32\drivers\mwac.sys [93600 2017-10-25] (Malwarebytes)
S3 rt640x64; C:\Windows\System32\drivers\rt640x64.sys [888064 2015-09-10] (Realtek )
S3 SbieDrv; C:\Program Files\Sandboxie\SbieDrv.sys [202600 2014-01-17] (Sandboxie Holdings, LLC)
S3 SDFRd; C:\Windows\System32\drivers\SDFRd.sys [31128 2017-03-18] ()
S3 SRTSP; C:\Windows\system32\drivers\N360x64\160A000.055\SRTSP64.SYS [810136 2017-07-14] (Symantec Corporation)
S1 SRTSPX; C:\Windows\system32\drivers\N360x64\160A000.055\SRTSPX64.SYS [49304 2017-07-14] (Symantec Corporation)
S0 SymEFASI; C:\Windows\System32\drivers\N360x64\160A000.055\SYMEFASI64.SYS [1868416 2017-07-14] (Symantec Corporation)
S4 SymELAM; C:\Windows\system32\drivers\N360x64\160A000.055\SymELAM.sys [24608 2017-07-14] (Symantec Corporation)
S3 SymEvent; C:\WINDOWS\system32\Drivers\SYMEVENT64x86.SYS [102568 2017-08-03] (Symantec Corporation)
S1 SymIRON; C:\Windows\system32\drivers\N360x64\160A000.055\Ironx64.SYS [301288 2017-07-14] (Symantec Corporation)
S1 SymNetS; C:\Windows\system32\drivers\N360x64\160A000.055\SYMNETS.SYS [566912 2017-07-14] (Symantec Corporation)
S3 WdBoot; C:\Windows\system32\drivers\WdBoot.sys [44632 2017-03-18] (Microsoft Corporation)
S3 WdFilter; C:\Windows\system32\drivers\WdFilter.sys [294816 2017-03-18] (Microsoft Corporation)
S3 WdNisDrv; C:\Windows\System32\Drivers\WdNisDrv.sys [121248 2017-03-18] (Microsoft Corporation)
========================== Drivers MD5 =======================
C:\Windows\System32\drivers\1394ohci.sys AAB860A5E606B9621E130D8C29D3F305
C:\Windows\System32\drivers\3ware.sys 4140B14929C555E9513D59A2EEB5C471
C:\Windows\System32\drivers\ACPI.sys D3DB4E3C096EFF74FB6E73E37CB66DD7
C:\Windows\System32\drivers\AcpiDev.sys 3E5E5DAE5CAEC0209C93D3AD8128D8A0
C:\Windows\System32\Drivers\acpiex.sys F72D7CC7E7A97A09757313F3B4C7E17A
C:\Windows\System32\drivers\acpipagr.sys F04B6F53FBDB2B6B0451AE53DE19F0C9
C:\Windows\System32\drivers\acpipmi.sys C347A6095F3BE417D24F1E1349F4AF0F
C:\Windows\System32\drivers\acpitime.sys 686BFFC47454DD2F58795C2EE891CA9F
C:\Windows\System32\drivers\ADP80XX.SYS FBDA59118E59B3722248C66BAD89CAA9
C:\Windows\system32\drivers\afd.sys AC1928C2F7505BD556C552F153B062AB
C:\Windows\System32\DRIVERS\ahcache.sys 1D914C996F2C3134E2344BB74F79BCF6
C:\Windows\SysWow64\drivers\AiChargerPlus.sys 4BFB41025FA1C37205EDEEFDE36F7771
C:\Windows\System32\drivers\amdk8.sys 9C39FBA94FFEF04561D13ED0D1B50DD0
C:\Windows\system32\DRIVERS\atikmdag.sys F992CE57F4D2A2F988135A1F87337EBC
C:\Windows\system32\DRIVERS\atikmpag.sys 17BA5C907E14947574CBB788F4CEB85F
C:\Windows\System32\drivers\amdppm.sys 395D56FA2E22A10AE4774440D086F559
C:\Windows\System32\drivers\amdsata.sys EB729A9ADCB9F9C406B533F95E2F67D4
C:\Windows\System32\drivers\amdsbs.sys 3B5C5C696F33FE61F1922533B03B9316
C:\Windows\System32\drivers\amdxata.sys A7D45A303FF8A9493C96C4B804051E6E
C:\Windows\System32\drivers\amd_sata.sys A2EFE3869B976296E097DEF368280F95
C:\Windows\System32\drivers\amd_xata.sys 625396421C29FB305C6C6235D01130B8
C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys C3D487827E48CC5EC17994FEC5BDFF87
C:\Windows\System32\drivers\appid.sys 5180537517C27375B1F2CB37ED599FAF
C:\Windows\System32\drivers\applockerfltr.sys EAF36A714E16A69B8B4ED7591CBA77B6
C:\Windows\System32\drivers\arcsas.sys 6E456A94B9BD7F6B4758729BCEDE40C3
C:\Windows\SysWow64\drivers\AsIO.sys 798DE15F187C1F013095BBBEB6FB6197
C:\Windows\SysWow64\drivers\AsUpIO.sys 1392B92179B07B672720763D9B1028A5
C:\Windows\System32\drivers\asyncmac.sys 766F3A7E42AFCF74265FAC78987D1665
C:\Windows\System32\drivers\atapi.sys 01733BEEE02E51F712330D5909BD701C
C:\Windows\system32\drivers\AtihdWT6.sys 0966FD5BAB1F9BE200875E9EED0A0A13
C:\Windows\system32\DRIVERS\au630x64.sys D278B7C0205249398F434856F5329FC9
C:\Windows\System32\drivers\bxvbda.sys 0914A5E66C0775CE11960452A6434FEC
C:\Windows\System32\drivers\BasicDisplay.sys F8129321B1874D4386F7FEB754BC3380
C:\Windows\System32\drivers\BasicRender.sys E2BFD01BD0ECF2BDE9420022147952A4
C:\Windows\System32\drivers\bcmfn2.sys 739D089777D2B66DBE7201E5EA4BA2D7
C:\Windows\System32\Drivers\Beep.sys ED03D2ACE378C9EB8BB957ABBD85B951
C:\Program Files (x86)\Norton Security Suite\NortonData\22.10.0.85\Definitions\BASHDefs\20170813.001\BHDrvx64.sys 24286C109C3D4C7C5814E8A315680CBF
C:\Windows\System32\DRIVERS\bowser.sys 2342B8619193B0D9FAC0D02C69DCE74A
C:\Program Files (x86)\BlueStacks\HD-Hypervisor-amd64.sys A4402EAF43656E38065BE74B87EDC111
C:\Windows\System32\drivers\BthAvrcpTg.sys AF57F0B0E284BE06860A7B701341324D
C:\Windows\System32\drivers\bthhfenum.sys 729CC10B1658178F0F009FE0E9159281
C:\Windows\System32\drivers\BthHFHid.sys 336A9C0254A0178ED50281B6EDF5B836
C:\Windows\System32\drivers\bthmodem.sys 5428242193611BF91DDBF4F58900A55A
C:\Windows\System32\drivers\buttonconverter.sys 102CAA11BA89290D48FBFD2E04274BA0
C:\Windows\System32\drivers\CAD.sys 029434AC0A3935F9125ABBD08BF7C30B
C:\Windows\System32\drivers\capimg.sys 307AE8BC9B45772DA02FB952A1D86C35
C:\Windows\system32\drivers\N360x64\160A000.055\ccSetx64.sys C407C0279B86DA6C36741B4AF80BF630
C:\Windows\System32\DRIVERS\cdfs.sys B6E5AD7C83A5254DEE9D86023C0E5A81
C:\Windows\System32\drivers\cdrom.sys ABE77AD954BC3D72F559CF0C381E50BC
C:\Windows\System32\drivers\cht4sx64.sys 05EA22CFC40EDE05BF6E3BC782E5204C
C:\Windows\System32\drivers\cht4vx64.sys 863E1C9F6750446DFB9EDCAEC3531367
C:\Windows\System32\drivers\circlass.sys 3E416539352B007AD0610BF34AC15D31
C:\Windows\System32\drivers\cldflt.sys 616E1ED94FA7F96D429D985FDB203D2E
C:\Windows\System32\drivers\CLFS.sys 1BF9D74451B8AF166105E28F1D7A5C27
C:\Windows\System32\drivers\registry.sys 5118CFC33BBB51C7E3ED441B7085AD26
C:\Windows\System32\drivers\CmBatt.sys 232F3A3AC3A2FB32C5C46503A6517073
C:\Windows\System32\Drivers\cng.sys 3413CE81E02C091F33C4C3DD3071630F
C:\Windows\System32\DRIVERS\cnghwassist.sys E1BFF774FF67CA951A5DFF0E104FB132
C:\Windows\System32\DriverStore\FileRepository\compositebus.inf_amd64_de4c68ea4fb1be53\CompositeBus.sys DFDAEDB857BC18764F0D8ECDCC3C1499
C:\Windows\System32\drivers\condrv.sys 04532711732BE9DBC364E88E4A9EC18A
C:\Windows\System32\drivers\dam.sys F51953EC4B9AACD92A3B3CE66E05CEF4
C:\Windows\System32\Drivers\dfsc.sys 185A4519B7764F4DEF714D890A7A9FD2
C:\Windows\system32\DRIVERS\ssudbus.sys 73BDD44A6088916964945886F9025409
C:\Windows\System32\drivers\disk.sys 1203EA16F36C5BEB2509FB7CC03DC178
C:\Windows\System32\drivers\dmvsc.sys 038B8B76284BC291EC75B005BB3EB13F
C:\Windows\system32\DRIVERS\drmkaud.sys 3D934A1C02EB6979CF45C70A71F580EC
C:\Windows\System32\drivers\dxgkrnl.sys D2D4095909DD26445139EC9B7C86DA5D
C:\Windows\System32\drivers\evbda.sys D64CD3AE93125EDA383190C2AF607E70
C:\Program Files (x86)\Common Files\Symantec Shared\EENGINE\eeCtrl64.sys 282FE3162E399EA7A86A268FD05C8868
C:\Windows\System32\drivers\EhStorClass.sys FFBB37982E6D24AEC7A2E5459098EAC9
C:\Windows\System32\drivers\EhStorTcgDrv.sys ABF38D02E01D6ED87AE1DF65FC5DF62D
C:\Windows\System32\drivers\errdev.sys B9A59B4AD516E38C39FA416398B96CCB
C:\WINDOWS\system32\drivers\mbae64.sys 5C9CA030C451CB3553DB9094C68EE6E9
C:\Windows\System32\Drivers\exfat.sys 9C4D88E8614487AD85A6F18A71A7298F
C:\Windows\System32\Drivers\fastfat.sys C61014A176ECAAF97589E6FC979CE786
C:\Windows\System32\drivers\fdc.sys 853081957BA148F38FD8DE4390CFCF4A
C:\Windows\System32\drivers\filecrypt.sys 27E764D6460504B7271AFECE7A59FB76
C:\Windows\System32\drivers\fileinfo.sys 3D6087F51110F3CC0DA89385354F8C5E
C:\Windows\System32\drivers\filetrace.sys 057E95E53C38260C4EF49B3A077770CD
C:\Windows\System32\drivers\flpydisk.sys 90B2983D8495C26345A1DC5F0C3BB07B
C:\Windows\System32\drivers\fltmgr.sys A84261F75F490E45CFEDBA77EFE4F67E
C:\Windows\System32\drivers\FsDepends.sys D2814848206DFC18EB8D3D069FAE703E
C:\Windows\System32\Drivers\Fs_Rec.sys AE7EDF845F41ACA3B74567C3CE20E987
C:\Windows\System32\DRIVERS\fvevol.sys FF0699483185CE3B4E1144DF19AC5E97
C:\Windows\system32\DRIVERS\GEARAspiWDM.sys 8E98D21EE06192492A5671A6144D092F
C:\Windows\System32\drivers\vmgencounter.sys 4616F61E24B3AEA6E0E4EA7D69531EF4
C:\Windows\System32\drivers\genericusbfn.sys 23174BB6937459B924BB8EF667FB28EF
C:\Windows\System32\Drivers\msgpioclx.sys 4B11CFBE1D9B73A9D865F6AB26F800BA
C:\Windows\System32\drivers\gpuenergydrv.sys 3FC3FCF557D0BE3D724EA10642E1F6FF
C:\Windows\System32\drivers\HDAudBus.sys 02B9639D9997E95CDF2F4C4F3BDCC73D
C:\Windows\System32\drivers\HidBatt.sys 9F90819E301C70A3A042FC05D3E41B5F
C:\Windows\System32\drivers\hidbth.sys 3CA3244C45B25F3B3ED9445C195E40EB
C:\Windows\System32\drivers\hidi2c.sys 55DAF856F9633DD2519BA4E942870F02
C:\Windows\System32\drivers\hidinterrupt.sys E34216A190D9BF8EAA666F6903BCD0EF
C:\Windows\System32\drivers\hidir.sys 852DBB5185996AD8C73872A43A453729
C:\Windows\System32\drivers\hidusb.sys C1A608120DE0DF52E51B8BAF86AF19F9
C:\Windows\System32\drivers\HpSAMD.sys 8ADD9CA3E0F18CEA11EA6FAED794A228
C:\Windows\System32\drivers\HTTP.sys BB1AE72906564A6E81B79D73A05AE21F
C:\Windows\System32\drivers\hvservice.sys F60F8390B635156593F7493AE898AFB0
C:\Windows\System32\drivers\hwpolicy.sys 563F5FC3B46A70A91AB6C8822AC8BF25
C:\Windows\System32\drivers\hyperkbd.sys C082249BC3E972C8A132D9EC6AD9EAD5
C:\Windows\System32\drivers\i8042prt.sys C6C8315E3262FAE460529C6DA2951682
C:\Windows\System32\drivers\iagpio.sys C6B8743B213F06AA60943D8366FE968F
C:\Windows\System32\drivers\iai2c.sys 9A2A2F3C69B9A30B6E78536F6D258BAD
C:\Windows\System32\drivers\iaLPSS2i_GPIO2.sys 42962355A7911407026E920E7252E3E5
C:\Windows\System32\drivers\iaLPSS2i_GPIO2_BXT_P.sys BD47B2FEABFA48C6224D43EE9EA9BC06
C:\Windows\System32\drivers\iaLPSS2i_I2C.sys 2184CB3A65888F446FCD6DBA9F073F4C
C:\Windows\System32\drivers\iaLPSS2i_I2C_BXT_P.sys 4126F8DA08CE7924A3AE6F7235F85D5F
C:\Windows\System32\drivers\iaLPSSi_GPIO.sys 16A10CCEDCF5AC4CAAE43DC9FC40392F
C:\Windows\System32\drivers\iaLPSSi_I2C.sys EB82A11613326691508D9ED9A4FE29E7
C:\Windows\System32\drivers\iaStorAV.sys D820075D3395BED28FC57AEF8FBA666F
C:\Windows\System32\drivers\iaStorV.sys A243E0CE8644378C9A9D015ABC3EDA27
C:\Windows\System32\drivers\ibbus.sys E16E4FC9F250E48CB2CAD93E59D010E2
C:\Program Files (x86)\Norton Security Suite\NortonData\22.10.0.85\Definitions\IPSDefs\20170816.001\IDSvia64.sys 1A3BC089C14E1263DE75E780A5914527
C:\Windows\System32\drivers\IndirectKmd.sys 0E33BC018502E7FDE77C343055D9C626
C:\Windows\system32\drivers\RTKVHD64.sys 622868E4BAE8FBCD22CB1A5901A2C824
C:\Windows\System32\drivers\intelide.sys 4B7F8A1AAC7172DB6918A0E10E1D78A3
C:\Windows\System32\drivers\intelpep.sys 0A3DBE89C965FFB7C0D0E38834E77B90
C:\Windows\System32\drivers\intelppm.sys 64EC687A811DC4F69DF3816F073352AA
C:\Windows\System32\drivers\iorate.sys 549C278119FF539C3B219C55B98B0E87
C:\Windows\System32\DRIVERS\ipfltdrv.sys A0F9F2E87F0C751FE164D90EB44A9B63
C:\Windows\System32\drivers\IPMIDrv.sys 656DDB34996A96539BA6E2843B5F2A77
C:\Windows\System32\drivers\ipnat.sys DCC05E5EAA580C97F13B434FAFACED85
C:\Windows\system32\drivers\irda.sys 9035C10C7EB8CF7C87CEA82A62EBB43A
C:\Windows\System32\drivers\irenum.sys E7FD479E3298F3C8852A0D2F092BDB35
C:\Windows\System32\drivers\isapnp.sys 7FE3B3A30FA20F27AF7022A01C2266BA
C:\Windows\System32\drivers\msiscsi.sys B6BA01EA6B2CCCB90A6FDCFF68F4A992
C:\Windows\System32\drivers\kbdclass.sys D36B404BF979297C6572AEF98B2594F2
C:\Windows\System32\drivers\kbdhid.sys 7E2036A846789D6D6A2EE21915017EE1
C:\Windows\System32\drivers\kdnic.sys 4C054B8E901F41F5743DADE8A29FF256
C:\Windows\System32\Drivers\ksecdd.sys BA7A5838866618A4E82FBC05B8923605
C:\Windows\System32\Drivers\ksecpkg.sys 6629CAA1F157088B9EDD1EAD24C6D753
C:\Windows\system32\drivers\ksthunk.sys 9778205F28DC4F2EFFCC146647FE5CF0
C:\Windows\System32\drivers\lltdio.sys FC37745959DFA4871759E4DCC836227A
C:\Windows\System32\drivers\lsi_sas.sys 16C9D4D822CCA795A72DC88B25A577CC
C:\Windows\System32\drivers\lsi_sas2i.sys 920F0CFCED5F28A31B79F1C470649D11
C:\Windows\System32\drivers\lsi_sas3i.sys 0FE63316F1C70A0F759A449FAC64C24B
C:\Windows\System32\drivers\lsi_sss.sys 80E82C46B27A923A3744531069B63857
C:\Windows\system32\drivers\luafv.sys 88F5570C04766EE561FF129B2F93030C
C:\Windows\system32\DRIVERS\lvrs64.sys A0A527569856B9814E8920F52EBB67F5
C:\Windows\system32\DRIVERS\lvuvc64.sys 415E344294D1C0D04627B29146F68481
C:\Windows\System32\drivers\mausbhost.sys C3EED732789052C98A2613A7E1C37CDA
C:\Windows\System32\drivers\mausbip.sys 4DCE65116A28488593FF5A6A18B03DB0
C:\Windows\system32\drivers\MBAMChameleon.sys 0C847B9BD2D1F1E97037F8C3DA6D5A1B
C:\WINDOWS\system32\drivers\farflt.sys 19956478146DC7884812C24B74D7132E
C:\WINDOWS\system32\drivers\mbam.sys 149E252142950594695178971748D056
C:\Windows\System32\drivers\MBAMSwissArmy.sys C3549BE8C1FE4ECBEE21DAD3378F6CD0
C:\WINDOWS\system32\drivers\mwac.sys 56D97EB1ACE0B76D500E7E1F1AB72023
C:\Windows\System32\drivers\megasas.sys 0609BF877A2F4DEECC62EEE220AB6242
C:\Windows\System32\drivers\MegaSas2i.sys EEC64C8D498D121607C7615FDFBEE4D0
C:\Windows\System32\drivers\megasr.sys 2B7D3B206833D769218A1F4BE2D73B97
C:\Windows\System32\drivers\mlx4_bus.sys 89257B8D3826B5629CF7F73F97DA44F9
C:\Windows\system32\drivers\mmcss.sys 9AE3C0CC0865B1618A3C97744A6A9E9B
C:\Windows\System32\drivers\modem.sys 0CD29540C32C2E2E0E3D7E9832752AF3
C:\Windows\System32\drivers\monitor.sys 534477FCAFDFCA6B841BFA06BD26BCC5
C:\Windows\System32\drivers\mouclass.sys F5D4E18A70BA069D479154442CDEB60D
C:\Windows\System32\drivers\mouhid.sys 5C09868963B0C076AC3BC7759A46B7B1
C:\Windows\System32\drivers\mountmgr.sys 8BF7039787036529B98E50AE86A0E46B
C:\Windows\System32\drivers\mpsdrv.sys AD118EC95E9EF4D5223D681D8F183567
C:\Windows\system32\drivers\mrxdav.sys D14C297933C82B8CB0B5CBBA4DDC830B
C:\Windows\System32\DRIVERS\mrxsmb.sys F2AD1B72C5A6475FB5FF332E1980DF88
C:\Windows\System32\DRIVERS\mrxsmb10.sys 84700F40C0E41AEA91F8F3D6218A8A68
C:\Windows\System32\DRIVERS\mrxsmb20.sys B855479BA6A74349CEF8061808C90201
C:\Windows\System32\drivers\bridge.sys 670E6CFDA70C106342C0D63D014B6822
C:\Windows\System32\Drivers\Msfs.sys 92C00BD9616F353CA59A755C33269757
C:\Windows\System32\drivers\msgpiowin32.sys F27EC8F7A0A779276E5DA2E70C2B01EE
C:\Windows\System32\drivers\mshidkmdf.sys CBA955A54C9446CAAD28C76789D3B071
C:\Windows\System32\drivers\mshidumdf.sys E8E568EF60677E4534F387C53EE1B35F
C:\Windows\System32\drivers\msisadrv.sys 16376B7B0730C04DD1A2C0CC8E09E420
C:\Windows\system32\DRIVERS\MSKSSRV.sys C2939119A17E52D74191EFC1E4CDEE09
C:\Windows\System32\drivers\mslldp.sys E40B960078A15D4901265D32E071C42D
C:\Windows\system32\DRIVERS\MSPCLOCK.sys B4860AB91DC4E73936F0FF504D6B4B07
C:\Windows\system32\DRIVERS\MSPQM.sys 8EDC45C3F7F64A51C98B59E24648F74B
C:\Windows\System32\Drivers\MsRPC.sys 7DA5FAC2A49D30CA5B7B96B8B26281AC
C:\Windows\System32\drivers\mssmbios.sys 7E3365C8BC83DCE88D6226BB5C7170C4
C:\Windows\system32\DRIVERS\MSTEE.sys 09D51564E49181E9928910D6B91C920E
C:\Windows\System32\drivers\MTConfig.sys 793AE56A3946EAD5F906C28D294FEFE6
C:\Windows\System32\Drivers\mup.sys E35F51C7474A26680627477462715206
C:\Windows\System32\drivers\mvumis.sys 74BD1149BF50F1E24934042A3BD17C90
C:\Windows\System32\DRIVERS\nwifi.sys 39C772E20B8C61858F969E4D60699D89
C:\Windows\System32\drivers\ndfltr.sys 0FFE8AF1B94C5FD54E6ACC6DAE990D31
C:\Windows\System32\drivers\ndis.sys 59F3D5FEF4A24871C07C279762DA8624
C:\Windows\System32\drivers\ndiscap.sys 4EA73CFDEE4A628D387D95464A131F29
C:\Windows\System32\drivers\NdisImPlatform.sys EB127689AF6F24091AB73538A556257F
C:\Windows\System32\DRIVERS\ndistapi.sys 73B4C72FB6170A08C64BDA92DE93ECF7
C:\Windows\System32\drivers\ndisuio.sys 6704F27EB15A5B30AA7FA5A4F4D1FD47
C:\Windows\System32\drivers\NdisVirtualBus.sys FE87CCAA89433FC306A80F15E848F4B2
C:\Windows\System32\drivers\ndiswan.sys 94517BC9F29A1B73D377F1BF1C3DCA34
C:\Windows\System32\DRIVERS\ndiswan.sys 94517BC9F29A1B73D377F1BF1C3DCA34
C:\Windows\System32\DRIVERS\NDProxy.sys AC6AC99075732F5C29DB0004DD5B1AC6
C:\Windows\System32\drivers\Ndu.sys 9AC090451D92E6081EB89CDA83D74189
C:\Windows\System32\drivers\NetAdapterCx.sys A115DDB2C7805C41EEC9A5276FF5764E
C:\Windows\System32\drivers\netbios.sys F420B6CAB5151A38E4DBBFFB500C11DA
C:\Windows\System32\DRIVERS\netbt.sys 30C2F67EC84EB11B22011620107E0325
C:\Windows\System32\drivers\netvsc.sys 8C03F2F5A9E93AEB08B3AEE51552394A
C:\Windows\System32\Drivers\Npfs.sys 6D8F6A9C53CFB0C49E8251A442B7283F
C:\Windows\System32\drivers\npsvctrig.sys BABF7E1757D6908941C9F9CBD66A5EF0
C:\Windows\System32\drivers\nsiproxy.sys 7A6BA778B48DF9FB7AC231D4FF6E3248
C:\Windows\System32\Drivers\NTFS.sys 8D72D5038C5F91AFEF1B160FE524C2D9
C:\Windows\System32\Drivers\Null.sys 4FFB2D5655D10700D5B8E205C4DB86BD
C:\Windows\System32\drivers\nvdimmn.sys 99EB6376EC2C03CE5F668577651E3454
C:\Windows\System32\drivers\nvraid.sys 3DB2E9E207358BFBD09B77B5119ECA5B
C:\Windows\System32\drivers\nvstor.sys 4C04BFBD4DB2EECCC47F5FA39D65BB6E
C:\Windows\System32\drivers\parport.sys 2CC6C325B271C7CA60F374F8F868CB45
C:\Windows\System32\drivers\partmgr.sys 664B7DDEE982ADF5EAB480C75B9F6218
C:\Windows\System32\drivers\pci.sys C5B74C6D87E77BC64DEBD1BF57DEB375
C:\Windows\System32\drivers\pciide.sys CFB85CB7A6F6926EA0EB96EDFB3C8A91
C:\Windows\System32\drivers\pcmcia.sys 13B7D84B397A90E82682C47A15C3A98D
C:\Windows\System32\drivers\pcw.sys 76EA512FD9D4673CF7A57775EE8922E2
C:\Windows\System32\drivers\pdc.sys 10E48E45A03A7F4C2B7C11738BE87816
C:\Windows\System32\drivers\peauth.sys 4F190BA3C9BD2F0277BCBF480F396091
C:\Windows\System32\drivers\percsas2i.sys FE52FF97A094609429FEF098EDC6FB08
C:\Windows\System32\drivers\percsas3i.sys FCA143274792F12383C35902E801E83A
C:\Windows\System32\drivers\pmem.sys 414CA4DCC31D795882B25ADC1DACE779
C:\Windows\System32\drivers\raspptp.sys D292D7FADCEE481CC64A9DE8FE9C3347
C:\Windows\System32\drivers\processr.sys D57CF871B3977731A91FE9611A54C7C1
C:\Windows\System32\drivers\pacer.sys B60431D2A046AD97F8427F6E568370F5
C:\Windows\system32\drivers\qwavedrv.sys A2B0F46FBA2521E7E732BDBDB1238515
C:\Windows\System32\DRIVERS\rasacd.sys EA9EB06EFC325CD2ACF5DF2F26A4894E
C:\Windows\System32\drivers\AgileVpn.sys 4E9379389D0A851DD19D130C8FAEFBD0
C:\Windows\System32\drivers\rasl2tp.sys 5279EC98F6218D29EADDFECCC0D80E9A
C:\Windows\System32\DRIVERS\raspppoe.sys D7FF75ED7A48FD60A573C9E959CF4DB5
C:\Windows\System32\drivers\rassstp.sys 6A4E45A7F17FA0B4B1B48C550E311944
C:\Windows\System32\DRIVERS\rdbss.sys F2C575A9657F7B2E027C6CE7BC8F1A2D
C:\Windows\System32\drivers\rdpbus.sys 9414B22E093243636D362BF8C8C12A67
C:\Windows\System32\drivers\rdpdr.sys 53A01D3FDB701AC5D9DDE4140227E3D9
C:\Windows\System32\drivers\rdpvideominiport.sys DF32ED51DC0C3F6F3B1C4CEF71B8B426
C:\Windows\System32\drivers\rdyboost.sys 2369A5B651308E0C3458143976E9B03B
C:\Windows\System32\Drivers\ReFS.sys 3581FB9529035F8EC6DB681664CA70B1
C:\Windows\System32\Drivers\ReFSv1.sys 79E1ADE19D8B7C56EF29D098EAF57AD0
C:\Windows\System32\drivers\rspndr.sys E87EECED9287C275B6CF30EB598B1D77
C:\Windows\System32\drivers\rt640x64.sys 841ECEC8C2F1FB61F0FF518B288649B7
C:\Windows\System32\drivers\vms3cap.sys 6308366D3CDEA5F427CFF4BCF0081B4E
C:\Program Files\Sandboxie\SbieDrv.sys E20128053F3F4641A2627ECFA7149ECA
C:\Windows\System32\drivers\sbp2port.sys 33B2DC5C2F19DA89F862484E23D9833D
C:\Windows\System32\DRIVERS\scfilter.sys 5CFEEFCC6FAD1FD09ACCFBD652DDD85B
C:\Windows\System32\drivers\scmbus.sys 5C8620FAC0E3C1658C8EF7AD7BB7EA5F
C:\Windows\System32\drivers\sdbus.sys 71A494A502F24465317E88E80F6C0C2C
C:\Windows\System32\drivers\SDFRd.sys 464B615872981015AC4FEEBDEA83A063
C:\Windows\System32\drivers\sdstor.sys 6BC219F1D9CDE08CEB9084ADB41FBA01
C:\Windows\System32\drivers\SerCx.sys 585329F62195A4B7AAD0A95F6EC89751
C:\Windows\System32\drivers\SerCx2.sys C8F4FDA8B3D039D7947344614FF5BFB2
C:\Windows\System32\drivers\serenum.sys E5B450E4E0DC1591254BF9CCF6C57B40
C:\Windows\System32\drivers\serial.sys 628D8DD136F92316BFEB58FA005338B7
C:\Windows\System32\drivers\sermouse.sys E5BA0B7353ADC5C95AB466D2E4DC89B1
C:\Windows\System32\drivers\sfloppy.sys 15CFCC4692DA8887B977CE5FC5181084
C:\Windows\System32\drivers\SiSRaid2.sys 2339F6B45E1D863B1D327F3AFD75A675
C:\Windows\System32\drivers\sisraid4.sys F520D50AD7266ED31D25DF4C8EA6BC2D
C:\Windows\System32\drivers\spaceport.sys 2334ED0B61CAE7E7B1B454674206CDAC
C:\Windows\System32\drivers\SpatialGraphFilter.sys F3F0B8CAC1F3E6C3382EAFCE762475AD
C:\Windows\System32\drivers\SpbCx.sys 83E82B0E292DCDE4C75B9241BF0FB300
C:\Windows\system32\drivers\N360x64\160A000.055\SRTSP64.SYS 9225E5323704993E6C557F8ABCEF2A66
C:\Windows\system32\drivers\N360x64\160A000.055\SRTSPX64.SYS 96E5695385228F99509DD505EA4F1F37
C:\Windows\System32\DRIVERS\srv.sys 36EAC4FE629FC036632F13EC14788FD1
C:\Windows\System32\DRIVERS\srv2.sys A84B05C7C2A233497BE1D518A662C326
C:\Windows\System32\DRIVERS\srvnet.sys 0351B28EEDFBD6C8CC69A7224A098CFA
C:\Windows\system32\DRIVERS\ssudmdm.sys 5252D7BC56E5E0ED715AEA8FE173A455
C:\Windows\System32\drivers\stexstor.sys D40C589F80EB1C511263D0547C0259AE
C:\Windows\system32\DRIVERS\serscan.sys 01726E4BD1D1A5AF1F23833C79528555
C:\Windows\System32\drivers\storahci.sys 576A818562069B1E091CC719C143AED2
C:\Windows\System32\drivers\vmstorfl.sys E5F703788DFA05411F1469E96838F438
C:\Windows\System32\drivers\stornvme.sys 0D0128244FF55EAD3F878D3FE542DBA5
C:\Windows\System32\drivers\storqosflt.sys 3A62FF78619258E6126C5C4B4CC82C8E
C:\Windows\System32\drivers\storufs.sys C6097966F8EA3B288070CDF7C3C8C3E8
C:\Windows\System32\drivers\storvsc.sys 3DC3B17E92DA02E36B4138733DF6C1AC
C:\Windows\System32\drivers\swenum.sys 2BC4D0EBC2467FE90302AE0AFAF23768
C:\Windows\System32\drivers\N360x64\160A000.055\SYMEFASI64.SYS 204B80C2C5B2E87E9558CC2D1C2D8BB5
C:\Windows\system32\drivers\N360x64\160A000.055\SymELAM.sys 3123BDBFE5CF061035D79CB3F3075F82
C:\WINDOWS\system32\Drivers\SYMEVENT64x86.SYS 674908D3CE54EE5336DC545CB2A39702
C:\Windows\system32\drivers\N360x64\160A000.055\Ironx64.SYS EF84A42B86BCBDCB88F3C8849170492D
C:\Windows\system32\drivers\N360x64\160A000.055\SYMNETS.SYS 8CF934DF2A8C1BDFA766D3E137A11986
C:\Windows\System32\drivers\Synth3dVsc.sys 572F81CF08972D53BAFFC2A110A2A586
C:\Windows\System32\drivers\tcpip.sys DC0D1B5284152315F81894DAABBB2AF3
C:\Windows\System32\drivers\tcpip.sys DC0D1B5284152315F81894DAABBB2AF3
C:\Windows\System32\drivers\tcpipreg.sys 1C35A5C62D110346379C55E39A3D547C
C:\Windows\system32\DRIVERS\tdx.sys 892AB2637603A5E9507C39E61101C3C3
C:\Windows\System32\drivers\terminpt.sys 96A35CDBA661D41C5A3914257CA1D200
C:\Windows\System32\drivers\tpm.sys F76A92975340DAA99939DA297D677EA8
C:\Windows\System32\drivers\tsusbflt.sys 9856BCCD1CD5DE4D17E8DBBA7CEFC688
C:\Windows\System32\drivers\TsUsbGD.sys 837AD2B941E721BCCEB7EF137E2DEE18
C:\Windows\System32\drivers\uaspstor.sys B4C846ABD462558D45CA578C855759C3
C:\Windows\System32\Drivers\UcmCx.sys 5C2C0296D9EE7DC92A3F14642FBE656D
C:\Windows\System32\Drivers\UcmTcpciCx.sys 8BB64E04CD97AD8C68543181D93E2AFC
C:\Windows\System32\drivers\UcmUcsi.sys 5A7CE114C8DA9060F32633F81A5625E5
C:\Windows\System32\drivers\ucx01000.sys 5D4EAF3D0911338CB8FDB088386D6DCA
C:\Windows\System32\drivers\udecx.sys 384E1F0D84B465820416338E52FE7C2B
C:\Windows\System32\DRIVERS\udfs.sys C82BE75239D412057C9E3DB1785680C6
C:\Windows\System32\drivers\UEFI.sys CCDF6EFF952BF3BF34DC17600F479397
C:\Windows\System32\drivers\ufx01000.sys 00BEF71C45FD6B06E7525E7B31EFA88C
C:\Windows\System32\drivers\UfxChipidea.sys 9450AB15C30CF7D1F23C8A42E778C3A2
C:\Windows\System32\drivers\ufxsynopsys.sys CEE12C7A689BDF448715024A7E0EB9C3
C:\Windows\System32\drivers\umbus.sys F39ED750EDF5948FA8CD99D1F4EC9372
C:\Windows\System32\drivers\umpass.sys 55984D4E64C2F8E4223542CBCC15EDEB
C:\Windows\System32\drivers\urschipidea.sys 4D23214CB8B1C36B82061280EB8FDAB3
C:\Windows\System32\drivers\urscx01000.sys 4329D880DB96B504F0DDC991A7374CCD
C:\Windows\System32\drivers\urssynopsys.sys 93FAD0AC5879F274FA248A49E3F3EA33
C:\Windows\System32\Drivers\usbaapl64.sys F957092C63CD71D85903CA0D8370F473
C:\Windows\System32\drivers\usbccgp.sys 6B09AA6A04C8261E787B6523229E7159
C:\Windows\System32\drivers\usbcir.sys ECE3AD18B4C22ED0C4AB1A2AD9AC32C8
C:\Windows\System32\drivers\usbehci.sys F8BCB536866474C6D8008F4C69B778A1
C:\Windows\system32\DRIVERS\usbfilter.sys 4875DC63E548812C75D4FDEF84970C89
C:\Windows\System32\drivers\usbhub.sys 1F723DA014062DBF3288B408A7611845
C:\Windows\System32\drivers\UsbHub3.sys B9651548CE196186A72CE8C6D0C094FC
C:\Windows\System32\drivers\usbohci.sys BE6ED98FD0D3FE5FB11762AD7CCD6C96
C:\Windows\System32\drivers\usbprint.sys CEE43CD5357DB8786CE6E2C430841AE4
C:\Windows\System32\drivers\usbser.sys 99F0738B320B7A8D11351A32F68AA5F1
C:\Windows\System32\drivers\USBSTOR.SYS 67E26F56CF7EACCBD9C9F75343A3D7C2
C:\Windows\System32\drivers\usbuhci.sys 7BA802C9F73A84B75BB22538ADA495BE
C:\Windows\System32\drivers\USBXHCI.SYS 50E70B3A95138AA4A30B095270EE0DE6
C:\Windows\System32\drivers\vdrvroot.sys C1EC9211C7759D2487FD30934AA3EE96
C:\Windows\System32\drivers\VerifierExt.sys C83F3BC00651448DB127D497CF955089
C:\Windows\System32\drivers\vhdmp.sys 0E12F5F6B1C813D17AFDA197C4394423
C:\Windows\System32\drivers\vhf.sys 1AD096A5C00E522398D0092D875A8CB6
C:\Windows\System32\drivers\vmbus.sys EE9A22CFD9AEDD7B52F98B0272494609
C:\Windows\System32\drivers\VMBusHID.sys BFBD0895926FD98A03AD6BB845B569B7
C:\Windows\System32\drivers\vmgid.sys C123C97D351C56C75FE5335AB18255EE
C:\Windows\System32\drivers\volmgr.sys 0AB9C264F13E2A070A8CF10EDD099ED2
C:\Windows\System32\drivers\volmgrx.sys 6EE608257C1137A25B402EF8FC77E83A
C:\Windows\System32\drivers\volsnap.sys E3429DBBEA3965BB96E24B16EF4A2551
C:\Windows\System32\drivers\volume.sys 86E790B503C771E674C7DF8FFCBFEFDB
C:\Windows\System32\drivers\vpci.sys B25589A0892E6DF8CC07E5CB48BFC954
C:\Windows\System32\drivers\vsmraid.sys AA4466A47D2CA7ECE3DCF5256017DCC3
C:\Windows\System32\drivers\vstxraid.sys 98BB6C9AD39D8F2E883093F28282FAEC
C:\Windows\System32\drivers\vwifibus.sys B47026E109828102266CBE2F5F9AD113
C:\Windows\System32\drivers\vwififlt.sys 799ECD541A9B2764B36A22A095885365
C:\Windows\System32\drivers\wacompen.sys F0F477541F7AF67CC05DA1CF4921A500
C:\Windows\System32\DRIVERS\wanarp.sys FDD16EF9177A8A2EF08A7FA3D3EFAA13
C:\Windows\System32\DRIVERS\wanarp.sys FDD16EF9177A8A2EF08A7FA3D3EFAA13
C:\Windows\system32\drivers\wcifs.sys 923200B78F5284D674A3712204D0FEFA
C:\Windows\system32\drivers\wcnfs.sys 1737BEF60CA384423CE4B32AF1C2BFFC
C:\Windows\system32\drivers\WdBoot.sys 38130C1C5FE0E08820EE57E1B087B659
C:\Windows\System32\drivers\wdcsam64.sys D0335A55E5C3F812548E18300C2ACB62
C:\Windows\System32\drivers\Wdf01000.sys 0C6CBF3490EE5F0D62B5820568CA30B8
C:\Windows\system32\drivers\WdFilter.sys F7B6CB0F9ECD28848E2BDACEAB0D9204
C:\Windows\System32\DRIVERS\wdiwifi.sys BF45B43BA47D0FA769CE5AFBF7104F01
C:\Windows\System32\Drivers\WdNisDrv.sys 82A4F22C884B4BAE8B531640859F9871
C:\Windows\System32\drivers\wfplwfs.sys 3C8F0ABD00E197101DCF43FEF8FB0D76
C:\Windows\System32\drivers\wimmount.sys 75014BF6510D4C6C69EEE5B7743A52AF
C:\Windows\System32\drivers\WindowsTrustedRT.sys C8EBCFED8FD2CDF725E44AF93016621E
C:\Windows\System32\drivers\WindowsTrustedRTProxy.sys D318557F9D7CA3836104F0B8ECB1F32E
C:\Windows\System32\drivers\winmad.sys 31DDF1D001336B2DCE7DF24E99EF1D04
C:\Windows\System32\drivers\winnat.sys 2E1A614EFB0523E20860AE7978DDA0A4
C:\Windows\System32\drivers\WinUSB.SYS 03858B18BB6DF6A400D9FC5153FD28A8
C:\Windows\System32\drivers\winverbs.sys 0BF4A43CF1F3A4D50AFA4561C3B4628D
C:\Windows\System32\drivers\wmiacpi.sys 0D6E1347A891607759340B1E55BA2A77
C:\Windows\System32\Drivers\Wof.sys 1AE1076034392218EE89D2744EC2A071
C:\Windows\System32\drivers\WpdUpFltr.sys 1FD80CBB192A20375F3664639DEB57B5
C:\Windows\system32\drivers\ws2ifsl.sys DAF4451760B46CB383D287C4FAFFE97D
C:\Windows\System32\drivers\WudfPf.sys 455609BF60DA3B57EEAB863DEFCCF14D
C:\Windows\System32\drivers\WUDFRd.sys 5068DAA8F67A62E964C9C9F88B159EA9
C:\Windows\system32\DRIVERS\WUDFRd.sys 5068DAA8F67A62E964C9C9F88B159EA9
C:\Windows\System32\drivers\xboxgip.sys B10655A4C2EFDC25483D670EF52A4854
C:\Windows\System32\drivers\xinputhid.sys 2E50A379A8E4F6C5D85E87C26C08D329
==================== NetSvcs (Whitelisted) ===================
(If an entry is included in the fixlist, it will be removed from the registry. The file will not be moved unless listed separately.)

==================== Three Months Created files and folders ========
(If an entry is included in the fixlist, the file/folder will be moved.)
2017-10-25 22:07 - 2017-10-25 22:07 - 000000000 ____D C:\FRST
2017-10-25 20:48 - 2017-10-25 20:49 - 000000000 ____D C:\farbar
2017-10-25 18:14 - 2017-10-25 18:24 - 000000214 _____ C:\Windows\Tasks\CreateExplorerShellUnelevatedTask.job
2017-10-25 17:59 - 2017-10-25 19:04 - 000000022 _____ C:\Windows\S.dirmngr
2017-08-28 23:39 - 2017-08-28 23:39 - 000000000 _____ C:\Windows\System32\list
2017-08-28 23:38 - 2017-08-28 23:38 - 000000000 _____ C:\Windows\System32\diskpart
2017-08-28 23:37 - 2017-08-28 23:37 - 000000000 _____ C:\list
2017-08-28 23:37 - 2017-08-28 23:37 - 000000000 _____ C:\diskpart
2017-08-27 18:25 - 2017-08-27 18:25 - 000000000 ____D C:\Users\My Name Was Here\AppData\Local\DBG
2017-08-27 18:05 - 2017-08-27 18:05 - 000000020 ___SH C:\Users\My Name Was Here\ntuser.ini
2017-08-27 12:06 - 2017-08-27 12:06 - 000000000 ____D C:\Windows.old
2017-08-27 12:05 - 2017-08-27 12:05 - 000008192 _____ C:\Windows\System32\config\userdiff
2017-08-27 12:05 - 2017-08-27 09:11 - 000000000 ____D C:\Windows\ServiceProfiles
2017-08-27 12:03 - 2017-08-27 12:03 - 000000000 ____D C:\Program Files\Reference Assemblies
2017-08-27 12:03 - 2017-08-27 12:03 - 000000000 ____D C:\Program Files\MSBuild
2017-08-27 12:03 - 2017-08-27 12:03 - 000000000 ____D C:\Program Files (x86)\Reference Assemblies
2017-08-27 12:03 - 2017-08-27 12:03 - 000000000 ____D C:\Program Files (x86)\MSBuild
2017-08-27 12:03 - 2017-02-10 11:26 - 001166520 _____ (Microsoft Corporation) C:\Windows\System32\PresentationNative_v0300.dll
2017-08-27 12:03 - 2017-02-10 11:26 - 000124624 _____ (Microsoft Corporation) C:\Windows\System32\PresentationCFFRasterizerNative_v0300.dll
2017-08-27 12:03 - 2017-02-10 11:26 - 000035480 _____ (Microsoft Corporation) C:\Windows\System32\TsWpfWrp.exe
2017-08-27 12:03 - 2017-02-10 11:21 - 000778936 _____ (Microsoft Corporation) C:\Windows\SysWOW64\PresentationNative_v0300.dll
2017-08-27 12:03 - 2017-02-10 11:21 - 000103120 _____ (Microsoft Corporation) C:\Windows\SysWOW64\PresentationCFFRasterizerNative_v0300.dll
2017-08-27 12:03 - 2017-02-10 11:21 - 000035480 _____ (Microsoft Corporation) C:\Windows\SysWOW64\TsWpfWrp.exe
2017-08-27 09:55 - 2017-08-27 09:57 - 000007623 _____ C:\Windows\diagwrn.xml
2017-08-27 09:55 - 2017-08-27 09:57 - 000007623 _____ C:\Windows\diagerr.xml
2017-08-27 09:52 - 2017-10-25 18:24 - 000960550 _____ C:\Windows\System32\PerfStringBackup.INI
2017-08-27 09:50 - 2017-10-25 18:05 - 000000000 ____D C:\Windows\System32\Tasks\Norton 360
2017-08-27 09:46 - 2017-10-25 19:05 - 000000006 ____H C:\Windows\Tasks\SA.DAT
2017-08-27 09:23 - 2017-08-27 09:42 - 000000000 ____D C:\Windows\System32\config\bbimigrate
2017-08-27 09:21 - 2017-08-27 09:21 - 000000000 ____D C:\ProgramData\USOShared
2017-08-27 09:20 - 2017-08-28 19:28 - 000000000 ____D C:\users\My Name Was Here
2017-08-27 09:19 - 2017-08-27 09:19 - 000000000 ____H C:\ProgramData\DP45977C.lfl
2017-08-27 09:19 - 2017-08-27 09:19 - 000000000 ____D C:\Windows\SysWOW64\RTCOM
2017-08-27 09:19 - 2017-08-27 09:19 - 000000000 ____D C:\Windows\System32\DAX2
2017-08-27 09:19 - 2017-08-27 09:19 - 000000000 ____D C:\Program Files\Realtek
2017-08-27 09:14 - 2017-08-27 09:14 - 000000000 ____D C:\Program Files\Common Files\ATI Technologies
2017-08-27 09:14 - 2017-08-27 09:14 - 000000000 ____D C:\Program Files\AMD
2017-08-27 09:14 - 2017-08-27 09:14 - 000000000 _____ C:\Windows\ativpsrm.bin
2017-08-27 09:13 - 2017-03-18 12:56 - 002233344 _____ (Microsoft Corporation) C:\Windows\SysWOW64\PrintConfig.dll
2017-08-27 09:12 - 2017-08-27 09:12 - 000000000 ____H C:\Windows\System32\Drivers\Msft_User_WpdFs_01_11_00.Wdf
2017-08-27 09:11 - 2017-10-25 18:08 - 000000000 ____D C:\Windows\System32\SleepStudy
2017-08-27 09:11 - 2017-08-28 18:43 - 000489640 _____ C:\Windows\System32\FNTCACHE.DAT
2017-08-27 07:55 - 2017-08-27 07:55 - 000000000 ____D C:\Users\My Name Was Here\AppData\Local\CrashDumps
2017-08-27 06:10 - 2017-10-25 19:04 - 000101784 _____ (Malwarebytes) C:\Windows\System32\Drivers\farflt.sys
2017-08-27 06:10 - 2017-10-25 19:04 - 000093600 _____ (Malwarebytes) C:\Windows\System32\Drivers\mwac.sys
2017-08-16 06:36 - 2017-08-27 08:42 - 000023364 _____ C:\Windows\ntbtlog.txt
2017-08-16 06:35 - 2017-08-16 06:35 - 000000000 ____D C:\ProgramData\SMR501
2017-08-16 04:32 - 2017-08-16 04:32 - 000000832 _____ C:\Windows\System32\Drivers\etc\hosts.txt
2017-08-16 04:08 - 2017-10-25 19:04 - 000045472 _____ (Malwarebytes) C:\Windows\System32\Drivers\mbam.sys
2017-08-16 04:08 - 2017-08-16 06:37 - 000188352 _____ (Malwarebytes) C:\Windows\System32\Drivers\MBAMChameleon.sys
2017-08-16 04:08 - 2017-08-16 04:08 - 001192400 _____ C:\Windows\isRS-000.tmp
2017-08-16 04:08 - 2017-08-16 04:08 - 000253856 _____ (Malwarebytes) C:\Windows\System32\Drivers\772C72F7.sys
2017-08-16 04:08 - 2017-08-16 04:08 - 000001919 _____ C:\Users\Public\Desktop\Malwarebytes.lnk
2017-08-16 04:08 - 2017-08-16 04:08 - 000000000 ____D C:\Program Files\Malwarebytes
2017-08-16 04:08 - 2017-06-27 09:06 - 000077376 _____ C:\Windows\System32\Drivers\mbae64.sys
2017-08-16 04:00 - 2017-08-16 04:06 - 000000000 ____D C:\ProgramData\UCheck
2017-08-16 03:59 - 2017-08-16 03:59 - 020843008 _____ (Adlice Software ) C:\Users\My Name Was Here\Downloads\UCheck_setup.exe
2017-08-16 03:59 - 2017-08-16 03:59 - 000000844 _____ C:\Users\Public\Desktop\UCheck.lnk
2017-08-16 03:59 - 2017-08-16 03:59 - 000000000 ____D C:\Program Files\UCheck
2017-08-16 03:52 - 2017-08-16 03:52 - 000000000 ____D C:\Users\My Name Was Here\AppData\Roaming\Sun
2017-08-16 03:50 - 2017-08-16 03:50 - 000738880 _____ (Oracle Corporation) C:\Users\My Name Was Here\Downloads\JavaSetup8u144.exe
2017-08-16 03:28 - 2017-08-16 03:28 - 000050426 _____ C:\Users\My Name Was Here\Downloads\Tcpview.zip
2017-08-16 03:15 - 2017-08-16 03:15 - 000000194 _____ C:\Users\My Name Was Here\Downloads\hosts-perm.bat
2017-08-16 03:01 - 2017-08-27 09:59 - 000000000 ___DC C:\Windows\Panther
2017-08-16 02:44 - 2017-08-16 04:44 - 000002072 _____ C:\Users\My Name Was Here\Desktop\Rkill.txt
2017-08-16 02:43 - 2017-08-16 02:43 - 001792640 _____ (Bleeping Computer, LLC) C:\Users\My Name Was Here\Downloads\rkill.exe
2017-08-03 20:48 - 2017-08-03 20:48 - 000000000 ____D C:\Program Files\Common Files\AV
2017-08-03 20:19 - 2017-08-08 22:34 - 000001282 _____ C:\Windows\ntbtlog.txt.bak
2017-08-03 19:44 - 2017-08-16 06:46 - 000000000 ____D C:\NPE
2017-08-03 19:42 - 2017-08-16 06:49 - 000000000 ____D C:\Users\My Name Was Here\AppData\Local\NPE
2017-08-03 19:07 - 2017-08-03 19:07 - 000102568 _____ (Symantec Corporation) C:\Windows\System32\Drivers\SYMEVENT64x86.SYS
2017-08-03 19:07 - 2017-08-03 19:07 - 000008309 _____ C:\Windows\System32\Drivers\SYMEVENT64x86.CAT
2017-08-03 19:07 - 2017-08-03 19:07 - 000002495 _____ C:\Users\Public\Desktop\Norton 360.lnk
2017-08-03 19:07 - 2017-08-03 19:07 - 000000000 ____D C:\Program Files\Common Files\Symantec Shared
2017-08-03 19:06 - 2017-08-16 03:34 - 000001369 _____ C:\Users\My Name Was Here\Desktop\Norton Installation Files.lnk
2017-08-03 19:06 - 2017-08-03 19:06 - 000000000 ____D C:\Windows\System32\Drivers\N360x64
2017-08-03 19:06 - 2017-08-03 19:06 - 000000000 ____D C:\ProgramData\NortonInstaller
2017-08-03 19:06 - 2017-08-03 19:06 - 000000000 ____D C:\Program Files (x86)\NortonInstaller
2017-08-03 19:06 - 2017-08-03 19:06 - 000000000 ____D C:\Program Files (x86)\Norton Security Suite
2017-08-03 19:05 - 2017-08-16 03:35 - 000000000 ____D C:\ProgramData\Norton
2017-08-03 19:05 - 2017-08-03 19:05 - 001113088 _____ (Symantec Corporation) C:\Users\My Name Was Here\Downloads\Norton_Download_Manager.exe
2017-08-03 19:05 - 2017-08-03 19:05 - 000000000 ____D C:\Users\Public\Downloads\Norton
==================== Three Months Modified files and folders ========
(If an entry is included in the fixlist, the file/folder will be moved.)
2017-10-25 19:04 - 2014-07-15 08:44 - 000253856 _____ (Malwarebytes) C:\Windows\System32\Drivers\MBAMSwissArmy.sys
2017-10-25 18:24 - 2017-03-18 03:40 - 000524288 _____ C:\Windows\System32\config\BBI
2017-10-25 17:56 - 2017-03-18 03:40 - 000008192 _____ C:\Windows\System32\config\ELAM
==================== Known DLLs (Whitelisted) =========================

==================== Bamital & volsnap ======================
(There is no automatic fix for files that do not pass verification.)
C:\Windows\System32\winlogon.exe
[2017-07-10 21:40] - [2017-07-10 21:40] - 000706560 _____ (Microsoft Corporation) 31E3287EF6D97C5864A301CEA75BBBA1
C:\Windows\System32\wininit.exe
[2017-07-10 21:40] - [2017-07-10 21:40] - 000318232 _____ (Microsoft Corporation) B2DB5876B6F68D32E470F691C7088F3F
C:\Windows\explorer.exe
[2017-07-10 21:40] - [2017-07-10 21:40] - 004847424 _____ (Microsoft Corporation) CA3BF0F15BA4F24D511BFEE725CC89BD
C:\Windows\SysWOW64\explorer.exe
[2017-07-10 21:40] - [2017-07-10 21:40] - 004469840 _____ (Microsoft Corporation) FC1145751AC6E4FF1656381BB09A5AA3
C:\Windows\System32\svchost.exe => MD5 is legit
C:\Windows\SysWOW64\svchost.exe => MD5 is legit
C:\Windows\System32\services.exe => MD5 is legit
C:\Windows\System32\User32.dll => MD5 is legit
C:\Windows\SysWOW64\User32.dll => MD5 is legit
C:\Windows\System32\userinit.exe => MD5 is legit
C:\Windows\SysWOW64\userinit.exe => MD5 is legit
C:\Windows\System32\rpcss.dll
[2017-07-10 21:40] - [2017-07-10 21:40] - 001085440 _____ (Microsoft Corporation) 0E79A4C76CAAA0CFE9CA42C13E5AA086
C:\Windows\System32\dnsapi.dll => MD5 is legit
C:\Windows\SysWOW64\dnsapi.dll => MD5 is legit
C:\Windows\System32\Drivers\volsnap.sys
[2017-03-18 12:57] - [2017-03-18 12:57] - 000397216 _____ (Microsoft Corporation) E3429DBBEA3965BB96E24B16EF4A2551

==================== Association (Whitelisted) =============

==================== Restore Points  =========================

==================== BCD ================================
Firmware Boot Manager
---------------------
identifier              {fwbootmgr}
displayorder            {bootmgr}
                        {d4bf540f-ba07-11e7-869e-806e6f6e6963}
                        {8532a074-0633-11e4-bf16-806e6f6e6963}
                        {8532a073-0633-11e4-bf16-806e6f6e6963}
timeout                 2
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {default}
resumeobject            {c5a4328b-dfa6-11e2-a548-eaa61bb64673}
displayorder            {default}
                        {c5a4328f-dfa6-11e2-a548-eaa61bb64673}
toolsdisplayorder       {memdiag}
timeout                 30
Firmware Application (101fffff)
-------------------------------
identifier              {8532a073-0633-11e4-bf16-806e6f6e6963}
description             CD/DVD Drive
Firmware Application (101fffff)
-------------------------------
identifier              {8532a074-0633-11e4-bf16-806e6f6e6963}
description             Hard Drive
Firmware Application (101fffff)
-------------------------------
identifier              {d4bf540f-ba07-11e7-869e-806e6f6e6963}
device                  partition=E:
description             UEFI: Lexar USB Flash Drive 1100
Windows Setup
-------------
identifier              {7254a080-1510-4e85-ac0f-e7fb3d444736}
device                  ramdisk=[C:]\$WINDOWS.~BT\Sources\SafeOS\winre.wim,{c5a4328a-dfa6-11e2-a548-eaa61bb64673}
custom:11000043         partition=C:
path                    \windows\system32\winload.efi
description             Windows Rollback
locale                  en-US
custom:12000044         \$WINDOWS.~BT\Sources\Panther\bootstat.dat
inherit                 {bootloadersettings}
osdevice                ramdisk=[C:]\$WINDOWS.~BT\Sources\SafeOS\winre.wim,{c5a4328a-dfa6-11e2-a548-eaa61bb64673}
custom:21000152         partition=C:
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes
Windows Boot Loader
-------------------
identifier              {c5a43279-dfa6-11e2-a548-eaa61bb64673}
device                  ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{c5a4327a-dfa6-11e2-a548-eaa61bb64673}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{c5a4327a-dfa6-11e2-a548-eaa61bb64673}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes
Windows Boot Loader
-------------------
identifier              {c5a4327e-dfa6-11e2-a548-eaa61bb64673}
device                  ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{c5a4327f-dfa6-11e2-a548-eaa61bb64673}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{c5a4327f-dfa6-11e2-a548-eaa61bb64673}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes
Windows Boot Loader
-------------------
identifier              {c5a43283-dfa6-11e2-a548-eaa61bb64673}
device                  ramdisk=[K:]\Recovery\WindowsRE\Winre.wim,{c5a43284-dfa6-11e2-a548-eaa61bb64673}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[K:]\Recovery\WindowsRE\Winre.wim,{c5a43284-dfa6-11e2-a548-eaa61bb64673}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes
Windows Boot Loader
-------------------
identifier              {c5a43288-dfa6-11e2-a548-eaa61bb64673}
device                  ramdisk=[K:]\Recovery\WindowsRE\Winre.wim,{c5a43289-dfa6-11e2-a548-eaa61bb64673}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[K:]\Recovery\WindowsRE\Winre.wim,{c5a43289-dfa6-11e2-a548-eaa61bb64673}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes
Windows Boot Loader
-------------------
identifier              {default}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {current}
displaymessageoverride  StartupRepair
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {c5a4328b-dfa6-11e2-a548-eaa61bb64673}
nx                      OptIn
bootmenupolicy          Standard
useplatformclock        Yes
Windows Boot Loader
-------------------
identifier              {current}
device                  ramdisk=[K:]\Recovery\WindowsRE\Winre.wim,{c5a4328e-dfa6-11e2-a548-eaa61bb64673}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[K:]\Recovery\WindowsRE\Winre.wim,{c5a4328e-dfa6-11e2-a548-eaa61bb64673}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes
Windows Boot Loader
-------------------
identifier              {c5a4328f-dfa6-11e2-a548-eaa61bb64673}
device                  partition=C:
path                    \Windows.old\WINDOWS\system32\winload.efi
description             Windows 10 Home
locale                  en-US
osdevice                partition=C:
systemroot              \Windows.old\WINDOWS
bootmenupolicy          Standard
Resume from Hibernate
---------------------
identifier              {c5a43277-dfa6-11e2-a548-eaa61bb64673}
device                  partition=C:
path                    \Windows\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
recoverysequence        {c5a43279-dfa6-11e2-a548-eaa61bb64673}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No
Resume from Hibernate
---------------------
identifier              {c5a4327c-dfa6-11e2-a548-eaa61bb64673}
device                  partition=C:
path                    \WINDOWS\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
recoverysequence        {c5a4327e-dfa6-11e2-a548-eaa61bb64673}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No
Resume from Hibernate
---------------------
identifier              {c5a43281-dfa6-11e2-a548-eaa61bb64673}
device                  partition=C:
path                    \WINDOWS\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
recoverysequence        {c5a43283-dfa6-11e2-a548-eaa61bb64673}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No
Resume from Hibernate
---------------------
identifier              {c5a43286-dfa6-11e2-a548-eaa61bb64673}
device                  partition=C:
path                    \WINDOWS\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
recoverysequence        {c5a43288-dfa6-11e2-a548-eaa61bb64673}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No
Resume from Hibernate
---------------------
identifier              {c5a4328b-dfa6-11e2-a548-eaa61bb64673}
device                  partition=C:
path                    \WINDOWS\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
recoverysequence        {current}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No
Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\Microsoft\Boot\memtest.efi
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes
EMS Settings
------------
identifier              {emssettings}
bootems                 No
Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200
RAM Defects
-----------
identifier              {badmemory}
Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}
Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}
Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200
Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}
Device options
--------------
identifier              {c5a4327a-dfa6-11e2-a548-eaa61bb64673}
description             Windows Recovery
ramdisksdidevice        partition=\Device\HarddiskVolume1
ramdisksdipath          \Recovery\WindowsRE\boot.sdi
Device options
--------------
identifier              {c5a4327b-dfa6-11e2-a548-eaa61bb64673}
description             Windows Setup
ramdisksdidevice        partition=C:
ramdisksdipath          \$WINDOWS.~BT\Sources\SafeOS\boot.sdi
Device options
--------------
identifier              {c5a4327f-dfa6-11e2-a548-eaa61bb64673}
description             Windows Recovery
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\WindowsRE\boot.sdi
Device options
--------------
identifier              {c5a43280-dfa6-11e2-a548-eaa61bb64673}
description             Windows Setup
ramdisksdidevice        partition=C:
ramdisksdipath          \$WINDOWS.~BT\Sources\SafeOS\boot.sdi
Device options
--------------
identifier              {c5a43284-dfa6-11e2-a548-eaa61bb64673}
description             Windows Recovery
ramdisksdidevice        partition=K:
ramdisksdipath          \Recovery\WindowsRE\boot.sdi
Device options
--------------
identifier              {c5a43285-dfa6-11e2-a548-eaa61bb64673}
description             Windows Setup
ramdisksdidevice        partition=C:
ramdisksdipath          \$WINDOWS.~BT\Sources\SafeOS\boot.sdi
Device options
--------------
identifier              {c5a43289-dfa6-11e2-a548-eaa61bb64673}
description             Windows Recovery
ramdisksdidevice        partition=K:
ramdisksdipath          \Recovery\WindowsRE\boot.sdi
Device options
--------------
identifier              {c5a4328a-dfa6-11e2-a548-eaa61bb64673}
description             Windows Setup
ramdisksdidevice        partition=C:
ramdisksdipath          \$WINDOWS.~BT\Sources\SafeOS\boot.sdi
Device options
--------------
identifier              {c5a4328e-dfa6-11e2-a548-eaa61bb64673}
description             Windows Recovery
ramdisksdidevice        partition=K:
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

==================== Memory info ===========================
Percentage of memory in use: 12%
Total physical RAM: 8112.54 MB
Available physical RAM: 7089.37 MB
Total Virtual: 8112.54 MB
Available Virtual: 7125.96 MB
==================== Drives ================================
Drive c: (Windows) (Fixed) (Total:150 GB) (Free:3.33 GB) NTFS
Drive d: (Data Drive) (Fixed) (Total:764.35 GB) (Free:19.68 GB) NTFS
Drive e: (BACARD) (Removable) (Total:2.43 GB) (Free:2.43 GB) FAT32
Drive k: (Recovery image) (Fixed) (Total:16 GB) (Free:1.74 GB) NTFS
Drive x: (Boot) (Fixed) (Total:0.5 GB) (Free:0.5 GB) NTFS
==================== MBR & Partition Table ==================
========================================================
Disk: 0 (Size: 931.5 GB) (Disk ID: 06D2A332)
Partition: GPT.
========================================================
Disk: 1 (Size: 3.7 GB) (Disk ID: 00000000)
Partition: GPT.
LastRegBack: 2017-08-27 09:10
==================== End of FRST.txt ============================

 

 

 


BC AdBot (Login to Remove)

 


m

#2 HelpBot

HelpBot

    Bleepin' Binary Bot


  • Bots
  • 12,510 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:40 PM

Posted 30 October 2017 - 11:30 PM

Hello and welcome to Bleeping Computer!

I am HelpBot: an automated program designed to help the Bleeping Computer Staff better assist you! This message contains very important information, so please read through all of it before doing anything.

We apologize for the delay in responding to your request for help. Here at Bleeping Computer we get overwhelmed at times, and we are trying our best to keep up. Please note that your topic was not intentionally overlooked. Our mission is to help everyone in need, but sometimes it takes just a little longer to get to every request for help. No one is ignored here.

To help Bleeping Computer better assist you please perform the following steps:

***************************************************

step1.gif In order to continue receiving help at BleepingComputer.com, YOU MUST tell me if you still need help or if your issue has already been resolved on your own or through another resource! To tell me this, please click on the following link and follow the instructions there.

CLICK THIS LINK >>> https://www.bleepingcomputer.com/logreply/661118 <<< CLICK THIS LINK



If you no longer need help, then all you needed to do was the previous instructions of telling me so. You can skip the rest of this post. If you do need help please continue with Step 2 below.

***************************************************

step2.gifIf you still need help, I would like you to post a Reply to this topic (click the "Add Reply" button in the lower right hand of this page). In that reply, please include the following information:

  • If you have not done so already, include a clear description of the problems you're having, along with any steps you may have performed so far.
  • A new FRST log. For your convenience, you will find the instructions for generating these logs repeated at the bottom of this post.
    • Please do this even if you have previously posted logs for us.
    • If you were unable to produce the logs originally please try once more.
    • If you are unable to create a log please provide detailed information about your installed Windows Operating System including the Version, Edition and if it is a 32bit or a 64bit system.
    • If you are unsure about any of these characteristics just post what you can and we will guide you.
  • Please tell us if you have your original Windows CD/DVD available.
  • Upon completing the above steps and posting a reply, another staff member will review your topic and do their best to resolve your issues.

Thank you for your patience, and again sorry for the delay.

***************************************************

We need to see some information about what is happening in your machine. Please perform the following scan again:

  • Download FRST by Farbar from the following link if you no longer have it available and save it to your destop.

    FRST Download Link

  • When you go to the above page, there will be 32-bit and 64-bit downloads available. Please click on the appropriate one for your version of Windows. If you are unsure as to whether your Windows is 32-bit or 64-bit, please see this tutorial.
  • Double click on the FRST icon and allow it to run.
  • Agree to the usage agreement and FRST will open. Do not make any changes and click on the Scan button.
  • Notepad will open with the results.
  • Post the new logs as explained in the prep guide.
  • Close the program window, and delete the program from your desktop.


As I am just a silly little program running on the BleepingComputer.com servers, please do not send me private messages as I do not know how to read and reply to them! Thanks!

#3 SenorSySoP

SenorSySoP
  • Topic Starter

  • Members
  • 42 posts
  • OFFLINE
  •  
  • Local time:08:40 AM

Posted 01 November 2017 - 01:14 AM

Hello,  Yes, I still need help.   I  believe we downloaded some malware disguised as an anti malware program.  Now computer wont reboot.  Shows a drive X and if I try to repair I get an elam sys error and it wont boot.   The FRST scans are the most recent as computer as been unplugged waiting your advice.  I do have my windows CD but hope to try and clean without formatting and starting over.

 

Thanks



#4 Oh My!

Oh My!

    Adware and Spyware and Malware.....


  • Malware Response Instructor
  • 34,561 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:California
  • Local time:08:40 AM

Posted 01 November 2017 - 09:24 PM

Greetings SenorSySoP and :welcome: to BleepingComputer's Virus/Trojan/Spyware/Malware Removal forum.

My name is Oh My! and I am here to help you! Now that we are "friends" please call me Gary.

If you would allow me to call you by your first name I would prefer to do that.

===================================================

Ground Rules:
  • First, I would like to inform you that most of us here at Bleeping Computer offer our expert assistance out of the goodness of our hearts. Please try to match our commitment to you with your patience toward us. If this was easy we would never have met.
  • Please do not run any tools or take any steps other than those I will provide for you while we work on your computer together. I need to be certain about the state of your computer in order to provide appropriate and effective steps for you to take. Most often "well intentioned" (and usually panic driven!) independent efforts can make things much worse for both of us. If at any point you would prefer to take your own steps please let me know, I will not be offended. I would be happy to focus on the many others who are waiting in line for assistance.
  • Please perform all steps in the order they are listed in each set of instructions. Some steps may be a bit complicated. If things are not clear, be sure to stop and let me know. We need to work on this together with confidence.
  • Please copy and paste all logs into your post unless directed otherwise. Please do not re-run any programs I suggest. If you encounter problems simply stop and tell me.
  • If you do not reply to your topic after 5 days we assume it has been abandoned and I will close it.
  • When your computer is clean I will alert you of such. I will also provide for you detailed information about how you can combat future infections.
  • I would like to remind you to make no further changes to your computer unless I direct you to do so.
===================================================

Now that I am assisting you, you can expect that I will be very responsive to your situation. If you are able, I would request you check this thread at least once per day so that we can try to resolve your issues effectively and efficiently. If you are going to be delayed please be considerate and post that information so that I know you are still with me. Unfortunately, there are many people waiting to be assisted and not enough of us at BleepingComputer to go around. I appreciate your understanding and diligence.

Thank you for your patience thus far.

Please do this.

===================================================

Farbar's Recovery Scan Tool - Run Fix

--------------------
  • From a clean computer press the at the same time
  • Type notepad and press Enter
  • Copy and paste the contents of the below code box into the open notepad and save it on the flashdrive as fixlist.txt
cmd: bcdedit /set {current} disableelamdrivers yes
  • Insert the USB device into your infected computer
  • Enter the Recovery Command Prompt as you previously did
  • Run FRST as you did the first time and press Fix
  • A Fixlog.txt document will be saved on your USB device
  • Copy and paste that information in your reply.
  • Attempt to boot your computer into Normal Mode or, if not, Safe Mode
===================================================

Things I would like to see in your next reply. Please be sure to copy and paste any requested log information unless you are asked to attach it. :thumbsup2:
  • Fixlog
  • Does your computer boot properly?

Gary
 
If I do not reply within 24 hours please send me a Personal Message.

"Lord, to whom shall we go? You have the words that give eternal life. We believe, and know that you are the Holy One of God."

#5 Oh My!

Oh My!

    Adware and Spyware and Malware.....


  • Malware Response Instructor
  • 34,561 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:California
  • Local time:08:40 AM

Posted 04 November 2017 - 07:33 AM

Greetings,

===================================================

Do You Still Need Help?

It has been 3 days since my last post.
  • Do you still need help with this?
  • If you have not replied within 48 hours I will assume you have abandoned the Topic and it will be closed.

Gary
 
If I do not reply within 24 hours please send me a Personal Message.

"Lord, to whom shall we go? You have the words that give eternal life. We believe, and know that you are the Holy One of God."

#6 Oh My!

Oh My!

    Adware and Spyware and Malware.....


  • Malware Response Instructor
  • 34,561 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:California
  • Local time:08:40 AM

Posted 06 November 2017 - 09:55 AM

Due to the lack of feedback, this topic is now closed.

In the event you still have problems, please send me or any Moderator a Private Message and ask them to reopen this topic within the next 5 days.

Please include a link to your topic in the Private Message. Thank you.
Gary
 
If I do not reply within 24 hours please send me a Personal Message.

"Lord, to whom shall we go? You have the words that give eternal life. We believe, and know that you are the Holy One of God."

#7 Oh My!

Oh My!

    Adware and Spyware and Malware.....


  • Malware Response Instructor
  • 34,561 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:California
  • Local time:08:40 AM

Posted 06 November 2017 - 10:23 PM

This topic has been re-opened at the request of the person who originally posted.
Gary
 
If I do not reply within 24 hours please send me a Personal Message.

"Lord, to whom shall we go? You have the words that give eternal life. We believe, and know that you are the Holy One of God."

#8 SenorSySoP

SenorSySoP
  • Topic Starter

  • Members
  • 42 posts
  • OFFLINE
  •  
  • Local time:08:40 AM

Posted 06 November 2017 - 11:04 PM

thank you for reopening.  I ran the fix and the log is below.
 
fix result of Farbar Recovery Scan Tool (x64) Version: 16-10-2017
Ran by SYSTEM (06-11-2017 22:19:59) Run:1
Running from E:\
Boot Mode: Recovery
==============================================
fixlist content:
*****************
cmd: bcdedit /set {current} disableelamdrivers yes
*****************

========= bcdedit /set {current} disableelamdrivers yes =========
The operation completed successfully.
========= End of CMD: =========

==== End of Fixlog 22:19:59 ====
 
 
I then attempted to reboot and PC immediately went into automatic repair which was unsuccessful.
I then attempted to boot into safe mode without networking, option 4.   It did not work either and instead gave this message
"Your PC ran into a problem and needs to restart.  We will restart for you (I hear the fan running full speed but it never reboots though I let it run for 5 minutes before cutting off power to reboot manually)
Should I have let it run for longer to see if it will reboot?   I will try this since i guess I dont have anything to loose since its not connected to internet, what is the risk?  Update:  so far 30 minutes and it hasn't rebooted although I can hear the hard drive and fan spinning as though its trying to do something,.   I will let it run until I hear back from you.
 
Here is the error code:
 
For more info yada yada....
Stop Code:   System thread Exception not handled.
What failed: SymELAM.sys
Let me know next steps, please know it may be a few days to get back with you as I will be traveling for work this week
but I will not abandon this thread and really do appreciate your help. 
FWIW, if you have an opening in the Malware academy, I'd like to participate, learn, and hopefully give back.


#9 Oh My!

Oh My!

    Adware and Spyware and Malware.....


  • Malware Response Instructor
  • 34,561 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:California
  • Local time:08:40 AM

Posted 07 November 2017 - 09:04 AM

Greetings,

Welcome back and thank you for letting me know of your delays. It does help a lot.

We can chat about the Training Program once we finish up here, hopefully with positive results.

Please do this.

===================================================

Farbar's Recovery Scan Tool - Run Fix

--------------------
  • From a clean computer press the at the same time
  • Type notepad and press Enter
  • Copy and paste the contents of the below code box into the open notepad and save it on the flashdrive as fixlist.txt
S4 SymELAM; C:\Windows\system32\drivers\N360x64\160A000.055\SymELAM.sys [24608 2017-07-14] (Symantec Corporation)
  • Insert the USB device into your infected computer
  • Enter the Recovery Command Prompt as you previously did
  • Run FRST as you did the first time and press Fix
  • A Fixlog.txt document will be saved on your USB device
  • Copy and paste that information in your reply.
  • Attempt to boot your computer into Normal Mode or, if not, Safe Mode
===================================================

Things I would like to see in your next reply. Please be sure to copy and paste any requested log information unless you are asked to attach it. :thumbsup2:
  • Fixlog
  • Does your computer boot properly?

Edited by Oh My!, 07 November 2017 - 09:47 AM.
Added FRST Fixlist

Gary
 
If I do not reply within 24 hours please send me a Personal Message.

"Lord, to whom shall we go? You have the words that give eternal life. We believe, and know that you are the Holy One of God."

#10 SenorSySoP

SenorSySoP
  • Topic Starter

  • Members
  • 42 posts
  • OFFLINE
  •  
  • Local time:08:40 AM

Posted 07 November 2017 - 10:47 PM

Fix result of Farbar Recovery Scan Tool (x64) Version: 16-10-2017
Ran by SYSTEM (07-11-2017 18:40:16) Run:2
Running from E:\
Boot Mode: Recovery
==============================================
fixlist content:
*****************
S4 SymELAM; C:\Windows\system32\drivers\N360x64\160A000.055\SymELAM.sys [24608 2017-07-14] (Symantec Corporation)
*****************
HKLM\System\ControlSet001\Services\SymELAM => key removed successfully
SymELAM => service removed successfully
==== End of Fixlog 18:40:16 ====

 

 

Reboot was not successful.  The stop code was "security initialization failed"

 

I then tried in safe mode option 4 and it went to automatic repair which did not work either.

 

Standing by for next steps.  Thanks.



#11 Oh My!

Oh My!

    Adware and Spyware and Malware.....


  • Malware Response Instructor
  • 34,561 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:California
  • Local time:08:40 AM

Posted 08 November 2017 - 11:57 AM

Greetings.

Changing the post in order to run this step.

===================================================

Farbar's Recovery Scan Tool - Run Fix

--------------------
  • From a clean computer press the at the same time
  • Type notepad and press Enter
  • Copy and paste the contents of the below code box into the open notepad and save it on the flashdrive as fixlist.txt
LastRegBack: 2017-08-27 09:10
  • Insert the USB device into your infected computer
  • Enter the Recovery Command Prompt as you previously did
  • Run FRST as you did the first time and press Fix
  • A Fixlog.txt document will be saved on your USB device
  • Copy and paste that information in your reply.
  • Attempt to boot your computer into Normal Mode or, if not, Safe Mode
===================================================

Things I would like to see in your next reply. Please be sure to copy and paste any requested log information unless you are asked to attach it. :thumbsup2:
  • Fixlog
  • Does your computer boot properly?

Edited by Oh My!, 08 November 2017 - 07:09 PM.

Gary
 
If I do not reply within 24 hours please send me a Personal Message.

"Lord, to whom shall we go? You have the words that give eternal life. We believe, and know that you are the Holy One of God."

#12 Oh My!

Oh My!

    Adware and Spyware and Malware.....


  • Malware Response Instructor
  • 34,561 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:California
  • Local time:08:40 AM

Posted 10 November 2017 - 10:09 AM

Greetings,

===================================================

Do You Still Need Help?

It has been 3 days since my last post.
  • Do you still need help with this?
  • If you have not replied within 48 hours I will assume you have abandoned the Topic and it will be closed.

Gary
 
If I do not reply within 24 hours please send me a Personal Message.

"Lord, to whom shall we go? You have the words that give eternal life. We believe, and know that you are the Holy One of God."

#13 SenorSySoP

SenorSySoP
  • Topic Starter

  • Members
  • 42 posts
  • OFFLINE
  •  
  • Local time:08:40 AM

Posted 11 November 2017 - 01:38 AM

Here is the scan log;    Also, the pc boot was not successful.  automatic repair cannot repair your pc

 

 

 

 

Fix result of Farbar Recovery Scan Tool (x64) Version: 16-10-2017
Ran by SYSTEM (11-11-2017 00:46:09) Run:1
Running from E:\
Boot Mode: Recovery
==============================================
fixlist content:
*****************
LastRegBack: 2017-08-27 09:10
*****************
DEFAULT => copied successfully to System32\config\HiveBackup
DEFAULT => restored successfully from registry back up
SAM => copied successfully to System32\config\HiveBackup
SAM => restored successfully from registry back up
SECURITY => copied successfully to System32\config\HiveBackup
SECURITY => restored successfully from registry back up
SOFTWARE => copied successfully to System32\config\HiveBackup
SOFTWARE => restored successfully from registry back up
SYSTEM => copied successfully to System32\config\HiveBackup
SYSTEM => restored successfully from registry back up
==== End of Fixlog 00:46:11 ====

Edited by SenorSySoP, 11 November 2017 - 02:56 AM.


#14 Oh My!

Oh My!

    Adware and Spyware and Malware.....


  • Malware Response Instructor
  • 34,561 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:California
  • Local time:08:40 AM

Posted 11 November 2017 - 09:23 AM

Thank you for the information.

Can you tell me which Stop Code your received? Was it something different?
 

The stop code was "security initialization failed"

-----

Stop Code: System thread Exception not handled.
What failed: SymELAM.sys


Gary
 
If I do not reply within 24 hours please send me a Personal Message.

"Lord, to whom shall we go? You have the words that give eternal life. We believe, and know that you are the Holy One of God."

#15 SenorSySoP

SenorSySoP
  • Topic Starter

  • Members
  • 42 posts
  • OFFLINE
  •  
  • Local time:08:40 AM

Posted 11 November 2017 - 05:33 PM

thats all it said.   It didnt give me a code.  I will  try right now and reboot regularly and see what happens.  Stand by

 

OK when I reboot Automatic Repair fails and the I get Your PC did not start correctly.    Later I  got a message that a log is located in windows, sys32, loggiles srt trail or something like that.

 

Do we need these files?  Has there been any indication of a virus or root kit?   Seems like we are getting closer as it booting faster than ever but wont get there.

 

On a chance, I tried to reboot in safe mode and its start automatic repair again, the diagnosing pc, then the same You PC did not start correctly..

 

 


Edited by SenorSySoP, 11 November 2017 - 06:00 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users