[Wayzofthedozer]

the one i ran tdsskiller in has the options of startup repair system restore system image recovery windows memory diagnostic and command promt it says its running from Operating System: Unknown on (unknown) local disk

[Advertisements]

to get to that repair screen i had to boot from usb selct the box that says "restore your computer using a system image that you created earlier." then close out of the re-image your computer screen. then it has the system recovery screen with the options listed above

[Wayzofthedozer]

to get to that repair screen i had to boot from usb selct the box that says "restore your computer using a system image that you created earlier." then close out of the re-image your computer screen. then it has the system recovery screen with the options listed above

[Buddierdl]

That's right, choose command prompt and follow the rest of the instructions:

Run tdsskiller in the same way as you ran FRST before, using this line at the command prompt (remember to replace F: with the correct drive letter for the flash drive as before):

F:\TDSSKiller.exe -l report.txt

Then follow these instructions:

• 
• Check all boxes except "Loaded modules" then click OK.
  
• Click the Start Scan button.
  
• The scan should take no longer than 2 minutes.
• If a suspicious object is detected, the default action will be Skip, click on Continue.
  
• If malicious objects are found, they will show in the Scan results - Select action for found objects and offer three options.
  Ensure Cure (default) is selected, then click Continue > Reboot now to finish the cleaning process.
  
  Note: If Cure is not available, please choose Skip instead, do not choose Delete unless instructed.
• A report will be created in your root of the flash drive named "report.txt". Please copy and paste the contents of that file here.

[Wayzofthedozer]

i ran the tdss killer 3 times and it didn't save a .txt any of the times when the scan completes i clicked details and the screen was empty it says 117 processes checked 0 threats 0 neutralized 0 suspicious

[Buddierdl]

Well, it usually doesn't disappoint me when a scan comes back clean...

Let's run a system file scan and another disk check with this fixlist. If this doesn't fix the boot, please download an updated FRST from here and get a fresh scan. Also, see if it is still sticking on the same line in Safe Mode.

[Wayzofthedozer]

it is still sticking on the same line in safemode. i didnt see a fix lixst so i just download the updated frst and got a fresh scan


Scan result of Farbar Recovery Scan Tool (FRST.txt) (x64) Version: 14-01-2014 01
Ran by SYSTEM on MININT-C4HT9OE on 14-01-2014 11:49:06
Running from F:\
Windows 7 Home Premium (X64) OS Language: English(US)
Internet Explorer Version 10
Boot Mode: Recovery

The current controlset is ControlSet003
ATTENTION!:=====> If the system is bootable FRST could be run from normal or Safe mode to create a complete log.


==================== Registry (Whitelisted) ==================

HKLM-x32\...\Run: [Adobe ARM] - C:\Program Files (x86)\Common Files\Adobe\ARM\1.0\AdobeARM.exe [958576 2013-04-04] (Adobe Systems Incorporated)
Winlogon\Notify\igfxcui: C:\Windows\system32\igfxdev.dll (Intel Corporation)
HKU\Owner\...\Run: [swg] - "C:\Program Files (x86)\Google\GoogleToolbarNotifier\GoogleToolbarNotifier.exe"

==================== Services (Whitelisted) =================

S2 vToolbarUpdater13.2.0; C:\Program Files (x86)\Common Files\AVG Secure Search\vToolbarUpdater\13.2.0\ToolbarUpdater.exe [711112 2012-11-09] ()
S2 avast! Antivirus; "C:\Program Files\AVAST Software\Avast\AvastSvc.exe" [x]
S3 gusvc; "C:\Program Files (x86)\Google\Common\Google Updater\GoogleUpdaterService.exe" [x]
S2 vToolbarUpdater17.0.12; C:\Program Files (x86)\Common Files\AVG Secure Search\vToolbarUpdater\17.0.12\ToolbarUpdater.exe [x]
S2 WebCake Desktop Updater; "C:\Program Files (x86)\WebCake\WebCakeDesktop.Updater.exe" "C:\Users\Owner\AppData\Roaming\WebCake\WebCakeDesktop.exe"
S3 WebClient; %SystemRoot%\System32\webclnt.dll [x]
S2 Winmgmt; C:\PROGRA~3\37tlblfb.pzz [x]

==================== Drivers (Whitelisted) ====================

S2 aswFsBlk; No ImagePath
S0 aswRvrt; No ImagePath
S1 aswSnx; No ImagePath
S1 aswSP; No ImagePath
S1 aswTdi; No ImagePath
S0 aswVmm; No ImagePath
S2 aswMonFlt; \??\C:\Windows\system32\drivers\aswMonFlt.sys [x]
S1 aswRdr; \SystemRoot\System32\Drivers\aswrdr2.sys [x]
S1 avgtp; \??\C:\Windows\system32\drivers\avgtpx64.sys [x]

========================== Drivers MD5 =======================

C:\Windows\system32\drivers\1394ohci.sys ==> MD5 is legit
C:\Windows\System32\drivers\ACPI.sys ==> MD5 is legit
C:\Windows\system32\drivers\acpipmi.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\adp94xx.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\adpahci.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\adpu320.sys ==> MD5 is legit
C:\Windows\system32\drivers\afd.sys 79059559E89D06E8B80CE2944BE20228
C:\Windows\system32\drivers\agp440.sys ==> MD5 is legit
C:\Windows\system32\drivers\aliide.sys ==> MD5 is legit
C:\Windows\system32\drivers\amdide.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\amdk8.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\amdppm.sys ==> MD5 is legit
C:\Windows\system32\drivers\amdsata.sys D4121AE6D0C0E7E13AA221AA57EF2D49
C:\Windows\system32\DRIVERS\amdsbs.sys ==> MD5 is legit
C:\Windows\System32\drivers\amdxata.sys 540DAF1CEA6094886D72126FD7C33048
C:\Windows\system32\drivers\appid.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\arc.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\arcsas.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\asyncmac.sys ==> MD5 is legit
C:\Windows\System32\drivers\atapi.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\bxvbda.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\b57nd60a.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\bcmwl664.sys 9E84A931DBEE0292E38ED672F6293A99
C:\Windows\System32\Drivers\Beep.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\blbdrive.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\bowser.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\BrFiltLo.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\BrFiltUp.sys ==> MD5 is legit
C:\Windows\System32\Drivers\Brserid.sys ==> MD5 is legit
C:\Windows\System32\Drivers\BrSerWdm.sys ==> MD5 is legit
C:\Windows\System32\Drivers\BrUsbMdm.sys ==> MD5 is legit
C:\Windows\System32\Drivers\BrUsbSer.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\bthmodem.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\cdfs.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\cdrom.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\circlass.sys ==> MD5 is legit
C:\Windows\System32\CLFS.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\CmBatt.sys ==> MD5 is legit
C:\Windows\system32\drivers\cmdide.sys ==> MD5 is legit
C:\Windows\System32\Drivers\cng.sys EBF28856F69CF094A902F884CF989706
C:\Windows\System32\DRIVERS\compbatt.sys ==> MD5 is legit
C:\Windows\system32\drivers\CompositeBus.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\crcdisk.sys ==> MD5 is legit
C:\Windows\System32\Drivers\dfsc.sys ==> MD5 is legit
C:\Windows\System32\drivers\discache.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\disk.sys ==> MD5 is legit
C:\Windows\System32\drivers\drmkaud.sys ==> MD5 is legit
C:\Windows\System32\drivers\dxgkrnl.sys 88612F1CE3BF42256913BF6E61C70D52
C:\Windows\system32\DRIVERS\evbda.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\elxstor.sys ==> MD5 is legit
C:\Windows\system32\drivers\errdev.sys ==> MD5 is legit
C:\Windows\System32\Drivers\exfat.sys ==> MD5 is legit
C:\Windows\System32\Drivers\fastfat.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\fdc.sys ==> MD5 is legit
C:\Windows\System32\drivers\fileinfo.sys ==> MD5 is legit
C:\Windows\System32\drivers\filetrace.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\flpydisk.sys ==> MD5 is legit
C:\Windows\System32\drivers\fltmgr.sys ==> MD5 is legit
C:\Windows\System32\drivers\FsDepends.sys ==> MD5 is legit
C:\Windows\System32\Drivers\Fs_Rec.sys 6BD9295CC032DD3077C671FCCF579A7B
C:\Windows\System32\DRIVERS\fvevol.sys 8F6322049018354F45F05A2FD2D4E5E0
C:\Windows\system32\DRIVERS\gagp30kx.sys ==> MD5 is legit
C:\Windows\system32\drivers\hcw85cir.sys ==> MD5 is legit
C:\Windows\system32\drivers\HdAudio.sys 975761C778E33CD22498059B91E7373A
C:\Windows\system32\drivers\HDAudBus.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\HidBatt.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\hidbth.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\hidir.sys ==> MD5 is legit
C:\Windows\system32\drivers\hidusb.sys ==> MD5 is legit
C:\Windows\system32\drivers\HpSAMD.sys ==> MD5 is legit
C:\Windows\System32\drivers\HTTP.sys ==> MD5 is legit
C:\Windows\System32\drivers\hwpolicy.sys ==> MD5 is legit
C:\Windows\system32\drivers\i8042prt.sys ==> MD5 is legit
C:\Windows\system32\drivers\iaStorV.sys AAAF44DB3BD0B9D1FB6969B23ECC8366
C:\Windows\System32\DRIVERS\igdkmd64.sys 677AA5991026A65ADA128C4B59CF2BAD
C:\Windows\system32\DRIVERS\iirsp.sys ==> MD5 is legit
C:\Windows\system32\drivers\intelide.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\intelppm.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\ipfltdrv.sys ==> MD5 is legit
C:\Windows\system32\drivers\IPMIDrv.sys ==> MD5 is legit
C:\Windows\System32\drivers\ipnat.sys ==> MD5 is legit
C:\Windows\System32\drivers\irenum.sys ==> MD5 is legit
C:\Windows\system32\drivers\isapnp.sys ==> MD5 is legit
C:\Windows\system32\drivers\msiscsi.sys ==> MD5 is legit
C:\Windows\system32\drivers\kbdclass.sys ==> MD5 is legit
C:\Windows\system32\drivers\kbdhid.sys ==> MD5 is legit
C:\Windows\System32\Drivers\ksecdd.sys 8F489706472F7E9A06BAAA198703FA64
C:\Windows\System32\Drivers\ksecpkg.sys 868A2CAAB12EFC7A021682BCA0EEC54C
C:\Windows\system32\drivers\ksthunk.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\lltdio.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\lsi_fc.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\lsi_sas.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\lsi_sas2.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\lsi_scsi.sys ==> MD5 is legit
C:\Windows\system32\drivers\luafv.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\megasas.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\MegaSR.sys ==> MD5 is legit
C:\Windows\System32\drivers\modem.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\monitor.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\mouclass.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\mouhid.sys ==> MD5 is legit
C:\Windows\System32\drivers\mountmgr.sys ==> MD5 is legit
C:\Windows\system32\drivers\mpio.sys ==> MD5 is legit
C:\Windows\System32\drivers\mpsdrv.sys ==> MD5 is legit
C:\Windows\system32\drivers\mrxdav.sys 1A4F75E63C9FB84B85DFFC6B63FD5404
C:\Windows\System32\DRIVERS\mrxsmb.sys A5D9106A73DC88564C825D317CAC68AC
C:\Windows\System32\DRIVERS\mrxsmb10.sys D711B3C1D5F42C0C2415687BE09FC163
C:\Windows\System32\DRIVERS\mrxsmb20.sys 9423E9D355C8D303E76B8CFBD8A5C30C
C:\Windows\System32\drivers\msahci.sys ==> MD5 is legit
C:\Windows\system32\drivers\msdsm.sys ==> MD5 is legit
C:\Windows\System32\Drivers\Msfs.sys ==> MD5 is legit
C:\Windows\System32\drivers\mshidkmdf.sys ==> MD5 is legit
C:\Windows\System32\drivers\msisadrv.sys ==> MD5 is legit
C:\Windows\System32\drivers\MSKSSRV.sys ==> MD5 is legit
C:\Windows\System32\drivers\MSPCLOCK.sys ==> MD5 is legit
C:\Windows\System32\drivers\MSPQM.sys ==> MD5 is legit
C:\Windows\System32\Drivers\MsRPC.sys ==> MD5 is legit
C:\Windows\system32\drivers\mssmbios.sys ==> MD5 is legit
C:\Windows\System32\drivers\MSTEE.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\MTConfig.sys ==> MD5 is legit
C:\Windows\System32\Drivers\mup.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\nwifi.sys ==> MD5 is legit
C:\Windows\System32\drivers\ndis.sys 760E38053BF56E501D562B70AD796B88
C:\Windows\System32\DRIVERS\ndiscap.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\ndistapi.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\ndisuio.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\ndiswan.sys ==> MD5 is legit
C:\Windows\System32\Drivers\NDProxy.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\netbios.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\netbt.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\nfrd960.sys ==> MD5 is legit
C:\Windows\System32\Drivers\Npfs.sys ==> MD5 is legit
C:\Windows\System32\drivers\nsiproxy.sys ==> MD5 is legit
C:\Windows\System32\Drivers\Ntfs.sys B98F8C6E31CD07B2E6F71F7F648E38C0
C:\Windows\System32\Drivers\Null.sys ==> MD5 is legit
C:\Windows\system32\drivers\nvraid.sys 0A92CB65770442ED0DC44834632F66AD
C:\Windows\system32\drivers\nvstor.sys DAB0E87525C10052BF65F06152F37E4A
C:\Windows\system32\drivers\nv_agp.sys ==> MD5 is legit
C:\Windows\system32\drivers\ohci1394.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\parport.sys ==> MD5 is legit
C:\Windows\System32\drivers\partmgr.sys E9766131EEADE40A27DC27D2D68FBA9C
C:\Windows\System32\drivers\pci.sys ==> MD5 is legit
C:\Windows\system32\drivers\pciide.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\pcmcia.sys ==> MD5 is legit
C:\Windows\System32\drivers\pcw.sys ==> MD5 is legit
C:\Windows\System32\drivers\peauth.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\raspptp.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\processr.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\pacer.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\ql2300.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\ql40xx.sys ==> MD5 is legit
C:\Windows\system32\drivers\qwavedrv.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\rasacd.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\AgileVpn.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\rasl2tp.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\raspppoe.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\rassstp.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\rdbss.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\rdpbus.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\RDPCDD.sys ==> MD5 is legit
C:\Windows\System32\drivers\rdpencdd.sys ==> MD5 is legit
C:\Windows\System32\drivers\rdprefmp.sys ==> MD5 is legit
C:\Windows\System32\Drivers\RDPWD.sys E61608AA35E98999AF9AAEEEA6114B0A
C:\Windows\System32\drivers\rdyboost.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\rspndr.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\Rt64win7.sys BAEFEE35D27A5440D35092CE10267BEC
C:\Windows\system32\drivers\sbp2port.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\scfilter.sys ==> MD5 is legit
C:\Windows\System32\Drivers\secdrv.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\serenum.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\serial.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\sermouse.sys ==> MD5 is legit
C:\Windows\system32\drivers\sffdisk.sys ==> MD5 is legit
C:\Windows\system32\drivers\sffp_mmc.sys ==> MD5 is legit
C:\Windows\system32\drivers\sffp_sd.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\sfloppy.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\SiSRaid2.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\sisraid4.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\smb.sys ==> MD5 is legit
C:\Windows\System32\Drivers\spldr.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\srv.sys 441FBA48BFF01FDB9D5969EBC1838F0B
C:\Windows\System32\DRIVERS\srv2.sys B4ADEBBF5E3677CCE9651E0F01F7CC28
C:\Windows\System32\DRIVERS\srvnet.sys 27E461F0BE5BFF5FC737328F749538C3
C:\Windows\system32\DRIVERS\stexstor.sys ==> MD5 is legit
C:\Windows\system32\drivers\swenum.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\taphss.sys F33FDC72298DF4BF9813A55D21F4EB31
C:\Windows\System32\drivers\tcpip.sys 40AF23633D197905F03AB5628C558C51
C:\Windows\System32\DRIVERS\tcpip.sys 40AF23633D197905F03AB5628C558C51
C:\Windows\System32\drivers\tcpipreg.sys 1B16D0BD9841794A6E0CDE0CEF744ABC
C:\Windows\System32\drivers\tdpipe.sys ==> MD5 is legit
C:\Windows\System32\drivers\tdtcp.sys 51C5ECEB1CDEE2468A1748BE550CFBC8
C:\Windows\System32\DRIVERS\tdx.sys ==> MD5 is legit
C:\Windows\system32\drivers\termdd.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\tssecsrv.sys 4CE278FC9671BA81A138D70823FCAA09
C:\Windows\System32\drivers\tsusbflt.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\tunnel.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\uagp35.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\udfs.sys ==> MD5 is legit
C:\Windows\system32\drivers\uliagpkx.sys ==> MD5 is legit
C:\Windows\system32\drivers\umbus.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\umpass.sys ==> MD5 is legit
C:\Windows\System32\Drivers\usbaapl64.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\usbccgp.sys 6F1A3157A1C89435352CEB543CDB359C
C:\Windows\system32\drivers\usbcir.sys 80B0F7D5CCF86CEB5D402EAAF61FEC31
C:\Windows\System32\DRIVERS\usbehci.sys C025055FE7B87701EB042095DF1A2D7B
C:\Windows\System32\DRIVERS\usbhub.sys 287C6C9410B111B68B52CA298F7B8C24
C:\Windows\system32\drivers\usbohci.sys 9840FC418B4CBD632D3D0A667A725C31
C:\Windows\System32\DRIVERS\usbprint.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\usbscan.sys 9661DA76B4531B2DA272ECCE25A8AF24
C:\Windows\System32\DRIVERS\USBSTOR.SYS FED648B01349A3C8395A5169DB5FB7D6
C:\Windows\System32\DRIVERS\usbuhci.sys 62069A34518BCF9C1FD9E74B3F6DB7CD
C:\Windows\System32\Drivers\usbvideo.sys 1F775DA4CF1A3A1834207E975A72E9D7
C:\Windows\system32\drivers\usb8023x.sys 7B28E2FBE75115660FAB31079C0A9F29
C:\Windows\System32\drivers\vdrvroot.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\vgapnp.sys ==> MD5 is legit
C:\Windows\System32\drivers\vga.sys ==> MD5 is legit
C:\Windows\system32\drivers\vhdmp.sys ==> MD5 is legit
C:\Windows\system32\drivers\viaide.sys ==> MD5 is legit
C:\Windows\System32\drivers\volmgr.sys ==> MD5 is legit
C:\Windows\System32\drivers\volmgrx.sys ==> MD5 is legit
C:\Windows\System32\drivers\volsnap.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\vsmraid.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\vwifibus.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\vwififlt.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\wacompen.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\wanarp.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\wanarp.sys ==> MD5 is legit
C:\Windows\system32\DRIVERS\wd.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\wdcsam64.sys ==> MD5 is legit
C:\Windows\System32\drivers\Wdf01000.sys 442783E2CB0DA19873B7A63833FF4CB4
C:\Windows\System32\DRIVERS\wfplwf.sys ==> MD5 is legit
C:\Windows\System32\drivers\wimmount.sys ==> MD5 is legit
C:\Windows\SysWOW64\drivers\wimmount.sys ==> MD5 is legit
C:\Windows\System32\DRIVERS\WinUsb.sys FE88B288356E7B47B74B13372ADD906D
C:\Windows\system32\drivers\wmiacpi.sys ==> MD5 is legit
C:\Windows\system32\drivers\ws2ifsl.sys ==> MD5 is legit
C:\Windows\System32\drivers\WudfPf.sys AB886378EEB55C6C75B4F2D14B6C869F
C:\Windows\System32\DRIVERS\WUDFRd.sys DDA4CAF29D8C0A297F886BFE561E6659

==================== NetSvcs (Whitelisted) ===================


==================== One Month Created Files and Folders ========

2013-12-24 12:24 - 2013-12-24 12:24 - 00000000 ____D C:\Windows\System32\config\HiveBackup
2013-12-20 15:40 - 2009-07-13 17:41 - 00041984 _____ (Microsoft Corporation) C:\Windows\System32\LPK.dll
2013-12-20 15:40 - 2009-07-13 17:11 - 00025600 _____ (Microsoft Corporation) C:\Windows\SysWOW64\LPK.dll
2013-12-19 15:20 - 2013-12-19 15:20 - 00000000 ____D C:\FRST

==================== One Month Modified Files and Folders =======

2013-12-24 12:24 - 2013-12-24 12:24 - 00000000 ____D C:\Windows\System32\config\HiveBackup
2013-12-19 15:20 - 2013-12-19 15:20 - 00000000 ____D C:\FRST

Some content of TEMP:
====================
C:\Users\Owner\AppData\Local\Temp\rootsupd.exe


==================== Known DLLs (Whitelisted) ================


==================== Bamital & volsnap Check =================

C:\Windows\System32\winlogon.exe => MD5 is legit
C:\Windows\System32\wininit.exe => MD5 is legit
C:\Windows\SysWOW64\wininit.exe => MD5 is legit
C:\Windows\explorer.exe => MD5 is legit
C:\Windows\SysWOW64\explorer.exe => MD5 is legit
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 => MD5 is legit
C:\Windows\System32\Drivers\volsnap.sys => MD5 is legit


nointegritychecks: ==> Integrity Checks is disabled <===== ATTENTION!

==================== EXE ASSOCIATION =====================

HKLM\...\.exe: exefile => OK
HKLM\...\exefile\DefaultIcon: %1 => OK
HKLM\...\exefile\open\command: "%1" %* => OK

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


==================== BCD ================================

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=Y:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {0c78aec3-3d33-11e0-983b-ab6063c8ba2c}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {default}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {current}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {0c78aec3-3d33-11e0-983b-ab6063c8ba2c}
nx OptIn

Windows Boot Loader
-------------------
identifier {current}
device ramdisk=[C:]\Recovery\0c78aec5-3d33-11e0-983b-ab6063c8ba2c\Winre.wim,{0c78aec6-3d33-11e0-983b-ab6063c8ba2c}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
nointegritychecks Yes
osdevice ramdisk=[C:]\Recovery\0c78aec5-3d33-11e0-983b-ab6063c8ba2c\Winre.wim,{0c78aec6-3d33-11e0-983b-ab6063c8ba2c}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {0c78aec3-3d33-11e0-983b-ab6063c8ba2c}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=Y:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems Yes

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 {0c78aec6-3d33-11e0-983b-ab6063c8ba2c}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\0c78aec5-3d33-11e0-983b-ab6063c8ba2c\boot.sdi


==================== Memory info ===========================

Percentage of memory in use: 25%
Total physical RAM: 3034.36 MB
Available physical RAM: 2256.93 MB
Total Pagefile: 3032.51 MB
Available Pagefile: 2249.09 MB
Total Virtual: 8192 MB
Available Virtual: 8191.89 MB

==================== Drives ================================

Drive c: () (Fixed) (Total:232.79 GB) (Free:198.81 GB) NTFS
Drive f: () (Removable) (Total:7.53 GB) (Free:7.52 GB) FAT32
Drive x: (Boot) (Fixed) (Total:0.03 GB) (Free:0.03 GB) NTFS
Drive y: (System Reserved) (Fixed) (Total:0.1 GB) (Free:0.07 GB) NTFS ==>[System with boot components (obtained from reading drive)]

==================== MBR & Partition Table ==================

========================================================
Disk: 0 (MBR Code: Windows 7 or 8) (Size: 233 GB) (Disk ID: 086F8F0B)
Partition 1: (Active) - (Size=100 MB) - (Type=07 NTFS)
Partition 2: (Not Active) - (Size=233 GB) - (Type=07 NTFS)

========================================================
Disk: 1 (Size: 8 GB) (Disk ID: 6F20736B)
No partition Table on disk 1.
Disk 1 is a removable device.


LastRegBack: 2013-11-09 23:49

==================== End Of Log ============================

Attached Files

•  FRST.txt   22.83KB   301 downloads

[Buddierdl]

Sorry, try this fixlist.

Attached Files

•  fixlist.txt   965bytes   328 downloads

[Wayzofthedozer]

the fix log is attached it still wont boot. starup repair cant repair automaticaly and its still freezeing on the same line in safe mode Loaded: \Windows\system32\DRIVER\CLASSPNP.SYS

Attached Files

•  Fixlog.txt   2.02KB   303 downloads

[Buddierdl]

Okay, now let's try this one: (may take a little while to run)

Attached Files

•  fixlist.txt   115bytes   295 downloads

[Wayzofthedozer]

I ran the fix list heres the log. still wont boot.


Fix result of Farbar Recovery Tool (FRST written by Farbar) (x64) Version: 14-01-2014 01
Ran by SYSTEM at 2014-01-14 22:53:39 Run:10
Running from F:\
Boot Mode: Recovery
==============================================

Content of fixlist:
*****************
CMD: bcdedit /set nointegritychecks OFF
CMD: CHKDSK C: /F
CMD: sfc /scannow /offbootdir=y:\ /offwindir=c:\windows

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


========= bcdedit /set nointegritychecks OFF =========

The operation completed successfully.

========= End of CMD: =========


========= CHKDSK C: /F =========

The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) Y
Volume dismounted. All opened handles to this volume are now invalid.

CHKDSK is verifying files (stage 1 of 3)...
0 percent complete. (0 of 163328 file records processed)
0 percent complete. (14593 of 163328 file records processed)
1 percent complete. (16333 of 163328 file records processed)
1 percent complete. (24140 of 163328 file records processed)
2 percent complete. (32666 of 163328 file records processed)
2 percent complete. (36340 of 163328 file records processed)
3 percent complete. (48999 of 163328 file records processed)
4 percent complete. (65332 of 163328 file records processed)
5 percent complete. (81664 of 163328 file records processed)
5 percent complete. (97614 of 163328 file records processed)
6 percent complete. (97997 of 163328 file records processed)
7 percent complete. (114330 of 163328 file records processed)
8 percent complete. (130663 of 163328 file records processed)
9 percent complete. (146996 of 163328 file records processed)
163328 file records processed.

File verification completed.
1700 large file records processed.

0 bad file records processed.

6 EA records processed.

45 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
11 percent complete. (7917 of 207932 index entries processed)
12 percent complete. (16417 of 207932 index entries processed)
13 percent complete. (24918 of 207932 index entries processed)
14 percent complete. (33418 of 207932 index entries processed)
15 percent complete. (41918 of 207932 index entries processed)
16 percent complete. (50419 of 207932 index entries processed)
17 percent complete. (58919 of 207932 index entries processed)
18 percent complete. (67419 of 207932 index entries processed)
19 percent complete. (75920 of 207932 index entries processed)
20 percent complete. (84420 of 207932 index entries processed)
21 percent complete. (92920 of 207932 index entries processed)
22 percent complete. (101421 of 207932 index entries processed)
23 percent complete. (109921 of 207932 index entries processed)
24 percent complete. (118421 of 207932 index entries processed)
25 percent complete. (126922 of 207932 index entries processed)
26 percent complete. (135422 of 207932 index entries processed)
27 percent complete. (143922 of 207932 index entries processed)
28 percent complete. (152423 of 207932 index entries processed)
29 percent complete. (160923 of 207932 index entries processed)
29 percent complete. (164483 of 207932 index entries processed)
29 percent complete. (165213 of 207932 index entries processed)
29 percent complete. (166048 of 207932 index entries processed)
29 percent complete. (166472 of 207932 index entries processed)
29 percent complete. (167885 of 207932 index entries processed)
29 percent complete. (168960 of 207932 index entries processed)
30 percent complete. (169423 of 207932 index entries processed)
30 percent complete. (170372 of 207932 index entries processed)
30 percent complete. (171143 of 207932 index entries processed)
30 percent complete. (171620 of 207932 index entries processed)
30 percent complete. (172246 of 207932 index entries processed)
30 percent complete. (173383 of 207932 index entries processed)
30 percent complete. (174514 of 207932 index entries processed)
30 percent complete. (175214 of 207932 index entries processed)
30 percent complete. (175890 of 207932 index entries processed)
30 percent complete. (176292 of 207932 index entries processed)
30 percent complete. (176681 of 207932 index entries processed)
30 percent complete. (177709 of 207932 index entries processed)
31 percent complete. (177924 of 207932 index entries processed)
31 percent complete. (179026 of 207932 index entries processed)
31 percent complete. (179360 of 207932 index entries processed)
31 percent complete. (180533 of 207932 index entries processed)
31 percent complete. (181594 of 207932 index entries processed)
31 percent complete. (182036 of 207932 index entries processed)
31 percent complete. (183171 of 207932 index entries processed)
31 percent complete. (183839 of 207932 index entries processed)
31 percent complete. (184184 of 207932 index entries processed)
31 percent complete. (184429 of 207932 index entries processed)
31 percent complete. (185140 of 207932 index entries processed)
207932 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
35 percent complete. (11978 of 163328 file SDs/SIDs processed)
36 percent complete. (37479 of 163328 file SDs/SIDs processed)
37 percent complete. (62980 of 163328 file SDs/SIDs processed)
38 percent complete. (88481 of 163328 file SDs/SIDs processed)
39 percent complete. (113982 of 163328 file SDs/SIDs processed)
40 percent complete. (139483 of 163328 file SDs/SIDs processed)
163328 file SDs/SIDs processed.

Security descriptor verification completed.
22303 data files processed.

CHKDSK is verifying Usn Journal...
99 percent complete. (0 of 3538240 USN bytes processed)
100 percent complete. (3530752 of 3538240 USN bytes processed)
3538240 USN bytes processed.

Usn Journal verification completed.
Windows has checked the file system and found no problems.

244093951 KB total disk space.
35252048 KB in 108347 files.
79776 KB in 22304 indexes.
4 KB in bad sectors.
243703 KB in use by the system.
65536 KB occupied by the log file.
208518420 KB available on disk.

4096 bytes in each allocation unit.
61023487 total allocation units on disk.
52129605 allocation units available on disk.
Failed to transfer logged messages to the event log with status 50.

========= End of CMD: =========


========= sfc /scannow /offbootdir=y:\ /offwindir=c:\windows =========



Beginning system scan. This process will take some time.




There is a system repair pending which requires reboot to complete. Restart

Windows and run sfc again.


========= End of CMD: =========


==== End of Fixlog ====

Attached Files

•  Fixlog.txt   7.48KB   319 downloads

Edited by Buddierdl, 15 January 2014 - 02:13 PM.

[Buddierdl]

Can you reboot and then go the command prompt in the recovery environment as before, and try this command:

sfc /scannow /offbootdir=y:\ /offwindir=c:\windows

Let me know what it says.

Also, have you backed up your data? We may need to try something more radical.

[Wayzofthedozer]

no i wasnt able too when i loaded the linix it said it could only run ntf read only on the harddrive.

[Buddierdl]

Have you tried the sfc command mentioned in my last post yet?

[Wayzofthedozer]

i tried it in the regular command promt and when i run the command line it says windows resource protection could not start the repair service so im gonna try it after booting from the usb repair you gave me i said the same thing there

Edited by Wayzofthedozer, 15 January 2014 - 02:01 PM.

[Buddierdl]

Okay, could you please try this fixlist.

Also, let's get your data backed up so it is safe. Is the error occurring when you try to mount the hard drive? To copy files off of it onto an external drive, you only need to open it read-only.

Have we tried a restore point?

Attached Files

•  fixlist.txt   56bytes   291 downloads