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 not booting up normally - Safe Mode ok, gives me "problem event name BlueScreen". Using Vista.


  • Please log in to reply
15 replies to this topic

#1 wheelie

wheelie

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:34 AM

Posted 09 March 2011 - 04:36 AM

Hi Guys,

I'm really hoping that someone can help me, or at least point me in the right direction.

A few days ago I had an Apple software update which I downloaded, but when I next restarted my PC it entered a seemingly endless loop of failing to start up and running diagnostics. I went back to a previous restore point, and it started, so since then I have run Super Anti Spyware, Malwarebytes, Adaware, Avast and Spybot Search and Destroy. They have all turned up some things which I got rid of immediately. Every time I restart after running a scan I have problems, but it has worked eventually. I have also noticed a flickering blue pattern for a couple of seconds on the black screen during the startup process. Yesterday evening, however, I just could not get the machine to finish the start up process at all. Today I have started it in Safe Mode and copied the error message I received:

Windows has recovered from an unexpected shutdown
Windows can check online for a solution to the problem

Problem details as follows:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.2
Locale ID: 2057

Additional information about the problem:
BCCode: 1
BCP1: 82844626
BCP2: 00000000
BCP3: 0000FFFE
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini030911-01.dmp
C:\Users\Bronwen and Neil\AppData\Local\Temp\WER-64506-0.sysdata.xml
C:\Users\Bronwen and Neil\AppData\Local\Temp\WERF2A7.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409


I then restarted in Safe Mode With Networking, to enable me to post this.

I had a problem a couple of years ago which you guys helped me with brilliantly, but I suspect something has sneaked through again!

Thank you very much for looking at this for me.

BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,404 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:34 AM

Posted 11 March 2011 - 09:24 PM

Hello, let;s run these and see what they show. I may move this for you after this.

Please download the TDSS Rootkit Removing Tool (TDSSKiller.exe) and save it to your Desktop. <-Important!!!
Be sure to download TDSSKiller.exe (v2.4.0.0) from Kaspersky's website and not TDSSKiller.zip which appears to be an older version 2.3.2.2 of the tool.
  • Double-click on TDSSKiller.exe to run the tool for known TDSS variants.
    Vista/Windows 7 users right-click and select Run As Administrator.
  • If TDSSKiller does not run, try renaming it.
  • To do this, right-click on TDSSKiller.exe, select Rename and give it a random name with the .com file extension (i.e. 123abc.com). If you do not see the file extension, please refer to How to change the file extension.
  • Click the Start Scan button.
  • Do not use the computer during the scan
  • If the scan completes with nothing found, click Close to exit.
  • 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.
  • A log file named TDSSKiller_version_date_time_log.txt (i.e. TDSSKiller.2.4.0.0_27.07.2010_09.o7.26_log.txt) will be created and saved to the root directory (usually Local Disk C:).
  • Copy and paste the contents of that file in your next reply.


Rerun MBAM (MalwareBytes) like this:

Open MBAM in normal/regular mode and click Update tab, select Check for Updates,when done
click Scanner tab,select Quick scan and scan (normal mode).
After scan click Remove Selected, Post new scan log and Reboot into normal mode.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#3 wheelie

wheelie
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:34 AM

Posted 12 March 2011 - 01:05 PM

Hi, and thanks for the response. Sorry it's taken so long but we have had a few issues.
I downloaded and ran TDSSKiller (log pasted at bottom)and re-booted in normal mode. I then tried to update MBAM and received an error message:

"An error occurred, please report the following error code to the MBAM team - Error code:732(0,0)"

I ran a quick scan anyway which turned up nothing.

Later I tried to update MBAM again and this time it was successful, it then stated that I needed to re-boot to finish the update. Whilst the re-boot was taking place I received some messages from Spybot relating to Malwarebytes, which I clicked "allow change". Spybot then tried to launch but got hung for about an hour. I clicked "cancel scan" which appeared to have no effect. After about another hour I started Task manager to end the Spybot task. When re-boot had then completed MBAM would not run.I then tried to reinstall MBAM (from MajorGeeks site), when this was finished the message stated a re-boot was required to complete installation. At this point I had the same booting problems as described in original post and cannot start in normal mode. I have now started in safe mode with networking to write this. Hope you can make sense of this. Please find below TDSSKiller log.

2011/03/12 10:26:16.0559 1188 TDSS rootkit removing tool 2.4.21.0 Mar 10 2011 12:26:28
2011/03/12 10:26:16.0918 1188 ================================================================================
2011/03/12 10:26:16.0918 1188 SystemInfo:
2011/03/12 10:26:16.0918 1188
2011/03/12 10:26:16.0918 1188 OS Version: 6.0.6002 ServicePack: 2.0
2011/03/12 10:26:16.0918 1188 Product type: Workstation
2011/03/12 10:26:16.0918 1188 ComputerName: BRONWEN-NEIL
2011/03/12 10:26:16.0918 1188 UserName: Bronwen and Neil
2011/03/12 10:26:16.0918 1188 Windows directory: C:\Windows
2011/03/12 10:26:16.0918 1188 System windows directory: C:\Windows
2011/03/12 10:26:16.0918 1188 Processor architecture: Intel x86
2011/03/12 10:26:16.0918 1188 Number of processors: 1
2011/03/12 10:26:16.0918 1188 Page size: 0x1000
2011/03/12 10:26:16.0918 1188 Boot type: Safe boot with network
2011/03/12 10:26:16.0918 1188 ================================================================================
2011/03/12 10:26:17.0683 1188 Initialize success
2011/03/12 10:26:48.0805 0644 ================================================================================
2011/03/12 10:26:48.0805 0644 Scan started
2011/03/12 10:26:48.0805 0644 Mode: Manual;
2011/03/12 10:26:48.0805 0644 ================================================================================
2011/03/12 10:26:50.0458 0644 ACPI (82b296ae1892fe3dbee00c9cf92f8ac7) C:\Windows\system32\drivers\acpi.sys
2011/03/12 10:26:50.0630 0644 adp94xx (2edc5bbac6c651ece337bde8ed97c9fb) C:\Windows\system32\drivers\adp94xx.sys
2011/03/12 10:26:50.0770 0644 adpahci (b84088ca3cdca97da44a984c6ce1ccad) C:\Windows\system32\drivers\adpahci.sys
2011/03/12 10:26:50.0942 0644 adpu160m (7880c67bccc27c86fd05aa2afb5ea469) C:\Windows\system32\drivers\adpu160m.sys
2011/03/12 10:26:51.0082 0644 adpu320 (9ae713f8e30efc2abccd84904333df4d) C:\Windows\system32\drivers\adpu320.sys
2011/03/12 10:26:51.0285 0644 AFD (a201207363aa900abf1a388468688570) C:\Windows\system32\drivers\afd.sys
2011/03/12 10:26:51.0457 0644 aic78xx (ae1fdf7bf7bb6c6a70f67699d880592a) C:\Windows\system32\drivers\djsvs.sys
2011/03/12 10:26:51.0597 0644 aliide (90395b64600ebb4552e26e178c94b2e4) C:\Windows\system32\drivers\aliide.sys
2011/03/12 10:26:51.0753 0644 amdagp (2b13e304c9dfdfa5eb582f6a149fa2c7) C:\Windows\system32\drivers\amdagp.sys
2011/03/12 10:26:51.0862 0644 amdide (0577df1d323fe75a739c787893d300ea) C:\Windows\system32\drivers\amdide.sys
2011/03/12 10:26:52.0049 0644 AmdK7 (dc487885bcef9f28eece6fac0e5ddfc5) C:\Windows\system32\drivers\amdk7.sys
2011/03/12 10:26:52.0221 0644 AmdK8 (0ca0071da4315b00fc1328ca86b425da) C:\Windows\system32\drivers\amdk8.sys
2011/03/12 10:26:52.0424 0644 arc (5f673180268bb1fdb69c99b6619fe379) C:\Windows\system32\drivers\arc.sys
2011/03/12 10:26:52.0580 0644 arcsas (957f7540b5e7f602e44648c7de5a1c05) C:\Windows\system32\drivers\arcsas.sys
2011/03/12 10:26:52.0751 0644 aswFsBlk (cba53c5e29ae0a0ce76f9a2be3a40d9e) C:\Windows\system32\drivers\aswFsBlk.sys
2011/03/12 10:26:52.0923 0644 aswMonFlt (317f85fb68a3be507e9ccede5e6d9ee0) C:\Windows\system32\drivers\aswMonFlt.sys
2011/03/12 10:26:53.0079 0644 aswRdr (b6e8c5874377a42756c282fac2e20836) C:\Windows\system32\drivers\aswRdr.sys
2011/03/12 10:26:53.0251 0644 aswSP (b93a553c9b0f14263c8f016a44c3258c) C:\Windows\system32\drivers\aswSP.sys
2011/03/12 10:26:53.0438 0644 aswTdi (1408421505257846eb336feeef33352d) C:\Windows\system32\drivers\aswTdi.sys
2011/03/12 10:26:53.0578 0644 AsyncMac (53b202abee6455406254444303e87be1) C:\Windows\system32\DRIVERS\asyncmac.sys
2011/03/12 10:26:53.0656 0644 atapi (1f05b78ab91c9075565a9d8a4b880bc4) C:\Windows\system32\drivers\atapi.sys
2011/03/12 10:26:53.0906 0644 Beep (67e506b75bd5326a3ec7b70bd014dfb6) C:\Windows\system32\drivers\Beep.sys
2011/03/12 10:26:54.0265 0644 bowser (74b442b2be1260b7588c136177ceac66) C:\Windows\system32\DRIVERS\bowser.sys
2011/03/12 10:26:54.0421 0644 BrFiltLo (9f9acc7f7ccde8a15c282d3f88b43309) C:\Windows\system32\drivers\brfiltlo.sys
2011/03/12 10:26:54.0545 0644 BrFiltUp (56801ad62213a41f6497f96dee83755a) C:\Windows\system32\drivers\brfiltup.sys
2011/03/12 10:26:54.0701 0644 Brserid (b304e75cff293029eddf094246747113) C:\Windows\system32\drivers\brserid.sys
2011/03/12 10:26:54.0842 0644 BrSerWdm (203f0b1e73adadbbb7b7b1fabd901f6b) C:\Windows\system32\drivers\brserwdm.sys
2011/03/12 10:26:54.0951 0644 BrUsbMdm (bd456606156ba17e60a04e18016ae54b) C:\Windows\system32\drivers\brusbmdm.sys
2011/03/12 10:26:55.0029 0644 BrUsbSer (af72ed54503f717a43268b3cc5faec2e) C:\Windows\system32\drivers\brusbser.sys
2011/03/12 10:26:55.0169 0644 BTHMODEM (ad07c1ec6665b8b35741ab91200c6b68) C:\Windows\system32\drivers\bthmodem.sys
2011/03/12 10:26:55.0357 0644 cdfs (7add03e75beb9e6dd102c3081d29840a) C:\Windows\system32\DRIVERS\cdfs.sys
2011/03/12 10:26:55.0513 0644 cdrom (6b4bffb9becd728097024276430db314) C:\Windows\system32\DRIVERS\cdrom.sys
2011/03/12 10:26:55.0700 0644 circlass (da8e0afc7baa226c538ef53ac2f90897) C:\Windows\system32\drivers\circlass.sys
2011/03/12 10:26:55.0825 0644 CLFS (d7659d3b5b92c31e84e53c1431f35132) C:\Windows\system32\CLFS.sys
2011/03/12 10:26:56.0074 0644 CmBatt (0fed59edb4a83ff17f1778827b88ab1a) C:\Windows\system32\DRIVERS\CmBatt.sys
2011/03/12 10:26:56.0230 0644 cmdide (45201046c776ffdaf3fc8a0029c581c8) C:\Windows\system32\drivers\cmdide.sys
2011/03/12 10:26:56.0386 0644 Compbatt (6afef0b60fa25de07c0968983ee4f60a) C:\Windows\system32\DRIVERS\compbatt.sys
2011/03/12 10:26:56.0558 0644 crcdisk (2a213ae086bbec5e937553c7d9a2b22c) C:\Windows\system32\drivers\crcdisk.sys
2011/03/12 10:26:56.0714 0644 Crusoe (22a7f883508176489f559ee745b5bf5d) C:\Windows\system32\drivers\crusoe.sys
2011/03/12 10:26:56.0932 0644 DfsC (218d8ae46c88e82014f5d73d0236d9b2) C:\Windows\system32\Drivers\dfsc.sys
2011/03/12 10:26:57.0135 0644 disk (5d4aefc3386920236a548271f8f1af6a) C:\Windows\system32\drivers\disk.sys
2011/03/12 10:26:57.0322 0644 Dot4 (4f59c172c094e1a1d46463a8dc061cbd) C:\Windows\system32\DRIVERS\Dot4.sys
2011/03/12 10:26:57.0478 0644 Dot4Print (80bf3ba09f6f2523c8f6b7cc6dbf7bd5) C:\Windows\system32\DRIVERS\Dot4Prt.sys
2011/03/12 10:26:57.0603 0644 dot4usb (c55004ca6b419b6695970dfe849b122f) C:\Windows\system32\DRIVERS\dot4usb.sys
2011/03/12 10:26:57.0775 0644 drmkaud (97fef831ab90bee128c9af390e243f80) C:\Windows\system32\drivers\drmkaud.sys
2011/03/12 10:26:57.0884 0644 DXGKrnl (c68ac676b0ef30cfbb1080adce49eb1f) C:\Windows\System32\drivers\dxgkrnl.sys
2011/03/12 10:26:58.0040 0644 E1G60 (f88fb26547fd2ce6d0a5af2985892c48) C:\Windows\system32\DRIVERS\E1G60I32.sys
2011/03/12 10:26:58.0196 0644 Ecache (7f64ea048dcfac7acf8b4d7b4e6fe371) C:\Windows\system32\drivers\ecache.sys
2011/03/12 10:26:58.0399 0644 elxstor (e8f3f21a71720c84bcf423b80028359f) C:\Windows\system32\drivers\elxstor.sys
2011/03/12 10:26:58.0461 0644 Suspicious service (NoAccess): ESQULserv.sys
2011/03/12 10:26:58.0601 0644 ESQULserv.sys - detected Rootkit.Win32.TDSS.tdl2 (0)
2011/03/12 10:26:58.0898 0644 exfat (22b408651f9123527bcee54b4f6c5cae) C:\Windows\system32\drivers\exfat.sys
2011/03/12 10:26:59.0038 0644 fastfat (1e9b9a70d332103c52995e957dc09ef8) C:\Windows\system32\drivers\fastfat.sys
2011/03/12 10:26:59.0241 0644 fdc (afe1e8b9782a0dd7fb46bbd88e43f89a) C:\Windows\system32\DRIVERS\fdc.sys
2011/03/12 10:26:59.0413 0644 FileInfo (a8c0139a884861e3aae9cfe73b208a9f) C:\Windows\system32\drivers\fileinfo.sys
2011/03/12 10:26:59.0584 0644 Filetrace (0ae429a696aecbc5970e3cf2c62635ae) C:\Windows\system32\drivers\filetrace.sys
2011/03/12 10:26:59.0725 0644 flpydisk (6603957eff5ec62d25075ea8ac27de68) C:\Windows\system32\DRIVERS\flpydisk.sys
2011/03/12 10:26:59.0896 0644 FltMgr (01334f9ea68e6877c4ef05d3ea8abb05) C:\Windows\system32\drivers\fltmgr.sys
2011/03/12 10:27:00.0083 0644 fssfltr (d909075fa72c090f27aa926c32cb4612) C:\Windows\system32\DRIVERS\fssfltr.sys
2011/03/12 10:27:00.0224 0644 FsUsbExDisk (790a4ca68f44be35967b3df61f3e4675) C:\Windows\system32\FsUsbExDisk.SYS
2011/03/12 10:27:00.0458 0644 Fs_Rec (65ea8b77b5851854f0c55c43fa51a198) C:\Windows\system32\drivers\Fs_Rec.sys
2011/03/12 10:27:00.0629 0644 gagp30kx (4e1cd0a45c50a8882616cae5bf82f3c5) C:\Windows\system32\drivers\gagp30kx.sys
2011/03/12 10:27:00.0770 0644 GEARAspiWDM (8182ff89c65e4d38b2de4bb0fb18564e) C:\Windows\system32\DRIVERS\GEARAspiWDM.sys
2011/03/12 10:27:00.0973 0644 HdAudAddService (cb04c744be0a61b1d648faed182c3b59) C:\Windows\system32\drivers\HdAudio.sys
2011/03/12 10:27:01.0144 0644 HDAudBus (062452b7ffd68c8c042a6261fe8dff4a) C:\Windows\system32\DRIVERS\HDAudBus.sys
2011/03/12 10:27:01.0300 0644 HidBth (1338520e78d90154ed6be8f84de5fceb) C:\Windows\system32\drivers\hidbth.sys
2011/03/12 10:27:01.0425 0644 HidIr (ff3160c3a2445128c5a6d9b076da519e) C:\Windows\system32\drivers\hidir.sys
2011/03/12 10:27:01.0550 0644 HidUsb (cca4b519b17e23a00b826c55716809cc) C:\Windows\system32\DRIVERS\hidusb.sys
2011/03/12 10:27:01.0690 0644 HpCISSs (df353b401001246853763c4b7aaa6f50) C:\Windows\system32\drivers\hpcisss.sys
2011/03/12 10:27:01.0893 0644 HTTP (0eeeca26c8d4bde2a4664db058a81937) C:\Windows\system32\drivers\HTTP.sys
2011/03/12 10:27:02.0049 0644 i2omp (324c2152ff2c61abae92d09f3cca4d63) C:\Windows\system32\drivers\i2omp.sys
2011/03/12 10:27:02.0221 0644 i8042prt (22d56c8184586b7a1f6fa60be5f5a2bd) C:\Windows\system32\DRIVERS\i8042prt.sys
2011/03/12 10:27:02.0392 0644 ialm (496db78e6a0c4c44023d9a92b4a7ac31) C:\Windows\system32\DRIVERS\igdkmd32.sys
2011/03/12 10:27:02.0564 0644 iaStorV (c957bf4b5d80b46c5017bf0101e6c906) C:\Windows\system32\drivers\iastorv.sys
2011/03/12 10:27:02.0704 0644 iirsp (2d077bf86e843f901d8db709c95b49a5) C:\Windows\system32\drivers\iirsp.sys
2011/03/12 10:27:02.0907 0644 IntcAzAudAddService (67e40fa2e4f2b70e8b3c8597a38f3a49) C:\Windows\system32\drivers\RTKVHDA.sys
2011/03/12 10:27:03.0110 0644 intelide (97469037714070e45194ed318d636401) C:\Windows\system32\drivers\intelide.sys
2011/03/12 10:27:03.0219 0644 intelppm (224191001e78c89dfa78924c3ea595ff) C:\Windows\system32\DRIVERS\intelppm.sys
2011/03/12 10:27:03.0422 0644 IpFilterDriver (62c265c38769b864cb25b4bcf62df6c3) C:\Windows\system32\DRIVERS\ipfltdrv.sys
2011/03/12 10:27:03.0656 0644 IPMIDRV (40f34f8aba2a015d780e4b09138b6c17) C:\Windows\system32\drivers\ipmidrv.sys
2011/03/12 10:27:03.0781 0644 IPNAT (8793643a67b42cec66490b2a0cf92d68) C:\Windows\system32\DRIVERS\ipnat.sys
2011/03/12 10:27:03.0968 0644 IRENUM (109c0dfb82c3632fbd11949b73aeeac9) C:\Windows\system32\drivers\irenum.sys
2011/03/12 10:27:04.0077 0644 isapnp (350fca7e73cf65bcef43fae1e4e91293) C:\Windows\system32\drivers\isapnp.sys
2011/03/12 10:27:04.0202 0644 iScsiPrt (232fa340531d940aac623b121a595034) C:\Windows\system32\DRIVERS\msiscsi.sys
2011/03/12 10:27:04.0327 0644 iteatapi (bced60d16156e428f8df8cf27b0df150) C:\Windows\system32\drivers\iteatapi.sys
2011/03/12 10:27:04.0467 0644 iteraid (06fa654504a498c30adca8bec4e87e7e) C:\Windows\system32\drivers\iteraid.sys
2011/03/12 10:27:04.0607 0644 kbdclass (37605e0a8cf00cbba538e753e4344c6e) C:\Windows\system32\DRIVERS\kbdclass.sys
2011/03/12 10:27:04.0763 0644 kbdhid (d2600cb17b7408b4a83f231dc9a11ac3) C:\Windows\system32\drivers\kbdhid.sys
2011/03/12 10:27:04.0888 0644 KSecDD (86165728af9bf72d6442a894fdfb4f8b) C:\Windows\system32\Drivers\ksecdd.sys
2011/03/12 10:27:05.0091 0644 Lavasoft Kernexplorer (6c4a3804510ad8e0f0c07b5be3d44ddb) C:\Program Files\Lavasoft\Ad-Aware\KernExplorer.sys
2011/03/12 10:27:05.0263 0644 Lbd (b7c19ec8b0dd7efa58ad41ffeb8b8cda) C:\Windows\system32\DRIVERS\Lbd.sys
2011/03/12 10:27:05.0403 0644 lltdio (d1c5883087a0c3f1344d9d55a44901f6) C:\Windows\system32\DRIVERS\lltdio.sys
2011/03/12 10:27:05.0543 0644 LSI_FC (a2262fb9f28935e862b4db46438c80d2) C:\Windows\system32\drivers\lsi_fc.sys
2011/03/12 10:27:05.0668 0644 LSI_SAS (30d73327d390f72a62f32c103daf1d6d) C:\Windows\system32\drivers\lsi_sas.sys
2011/03/12 10:27:05.0762 0644 LSI_SCSI (e1e36fefd45849a95f1ab81de0159fe3) C:\Windows\system32\drivers\lsi_scsi.sys
2011/03/12 10:27:05.0902 0644 luafv (8f5c7426567798e62a3b3614965d62cc) C:\Windows\system32\drivers\luafv.sys
2011/03/12 10:27:06.0058 0644 megasas (d153b14fc6598eae8422a2037553adce) C:\Windows\system32\drivers\megasas.sys
2011/03/12 10:27:06.0183 0644 Modem (e13b5ea0f51ba5b1512ec671393d09ba) C:\Windows\system32\drivers\modem.sys
2011/03/12 10:27:06.0339 0644 monitor (0a9bb33b56e294f686abb7c1e4e2d8a8) C:\Windows\system32\DRIVERS\monitor.sys
2011/03/12 10:27:06.0479 0644 mouclass (5bf6a1326a335c5298477754a506d263) C:\Windows\system32\DRIVERS\mouclass.sys
2011/03/12 10:27:06.0620 0644 mouhid (93b8d4869e12cfbe663915502900876f) C:\Windows\system32\DRIVERS\mouhid.sys
2011/03/12 10:27:06.0745 0644 MountMgr (bdafc88aa6b92f7842416ea6a48e1600) C:\Windows\system32\drivers\mountmgr.sys
2011/03/12 10:27:06.0916 0644 mpio (583a41f26278d9e0ea548163d6139397) C:\Windows\system32\drivers\mpio.sys
2011/03/12 10:27:07.0057 0644 mpsdrv (22241feba9b2defa669c8cb0a8dd7d2e) C:\Windows\system32\drivers\mpsdrv.sys
2011/03/12 10:27:07.0197 0644 Mraid35x (4fbbb70d30fd20ec51f80061703b001e) C:\Windows\system32\drivers\mraid35x.sys
2011/03/12 10:27:07.0275 0644 MREMP50 (9bd4dcb5412921864a7aacdedfbd1923) C:\PROGRA~1\COMMON~1\Motive\MREMP50.SYS
2011/03/12 10:27:07.0447 0644 MRESP50 (07c02c892e8e1a72d6bf35004f0e9c5e) C:\PROGRA~1\COMMON~1\Motive\MRESP50.SYS
2011/03/12 10:27:07.0571 0644 MRxDAV (82cea0395524aacfeb58ba1448e8325c) C:\Windows\system32\drivers\mrxdav.sys
2011/03/12 10:27:07.0681 0644 mrxsmb (454341e652bdf5e01b0f2140232b073e) C:\Windows\system32\DRIVERS\mrxsmb.sys
2011/03/12 10:27:07.0821 0644 mrxsmb10 (2a4901aff069944fa945ed5bbf4dcde3) C:\Windows\system32\DRIVERS\mrxsmb10.sys
2011/03/12 10:27:08.0008 0644 mrxsmb20 (28b3f1ab44bdd4432c041581412f17d9) C:\Windows\system32\DRIVERS\mrxsmb20.sys
2011/03/12 10:27:08.0195 0644 msahci (742aed7939e734c36b7e8d6228ce26b7) C:\Windows\system32\drivers\msahci.sys
2011/03/12 10:27:08.0367 0644 msdsm (3fc82a2ae4cc149165a94699183d3028) C:\Windows\system32\drivers\msdsm.sys
2011/03/12 10:27:08.0523 0644 Msfs (a9927f4a46b816c92f461acb90cf8515) C:\Windows\system32\drivers\Msfs.sys
2011/03/12 10:27:08.0679 0644 msisadrv (0f400e306f385c56317357d6dea56f62) C:\Windows\system32\drivers\msisadrv.sys
2011/03/12 10:27:08.0851 0644 MSKSSRV (d8c63d34d9c9e56c059e24ec7185cc07) C:\Windows\system32\drivers\MSKSSRV.sys
2011/03/12 10:27:08.0975 0644 MSPCLOCK (1d373c90d62ddb641d50e55b9e78d65e) C:\Windows\system32\drivers\MSPCLOCK.sys
2011/03/12 10:27:09.0100 0644 MSPQM (b572da05bf4e098d4bba3a4734fb505b) C:\Windows\system32\drivers\MSPQM.sys
2011/03/12 10:27:09.0225 0644 MsRPC (b49456d70555de905c311bcda6ec6adb) C:\Windows\system32\drivers\MsRPC.sys
2011/03/12 10:27:09.0365 0644 mssmbios (e384487cb84be41d09711c30ca79646c) C:\Windows\system32\DRIVERS\mssmbios.sys
2011/03/12 10:27:09.0475 0644 MSTEE (7199c1eec1e4993caf96b8c0a26bd58a) C:\Windows\system32\drivers\MSTEE.sys
2011/03/12 10:27:09.0615 0644 Mup (6a57b5733d4cb702c8ea4542e836b96c) C:\Windows\system32\Drivers\mup.sys
2011/03/12 10:27:09.0755 0644 NativeWifiP (85c44fdff9cf7e72a40dcb7ec06a4416) C:\Windows\system32\DRIVERS\nwifi.sys
2011/03/12 10:27:09.0927 0644 NDIS (1357274d1883f68300aeadd15d7bbb42) C:\Windows\system32\drivers\ndis.sys
2011/03/12 10:27:10.0067 0644 NdisTapi (0e186e90404980569fb449ba7519ae61) C:\Windows\system32\DRIVERS\ndistapi.sys
2011/03/12 10:27:10.0192 0644 Ndisuio (d6973aa34c4d5d76c0430b181c3cd389) C:\Windows\system32\DRIVERS\ndisuio.sys
2011/03/12 10:27:10.0317 0644 NdisWan (818f648618ae34f729fdb47ec68345c3) C:\Windows\system32\DRIVERS\ndiswan.sys
2011/03/12 10:27:10.0457 0644 NDProxy (71dab552b41936358f3b541ae5997fb3) C:\Windows\system32\drivers\NDProxy.sys
2011/03/12 10:27:10.0629 0644 NetBIOS (bcd093a5a6777cf626434568dc7dba78) C:\Windows\system32\DRIVERS\netbios.sys
2011/03/12 10:27:10.0738 0644 netbt (ecd64230a59cbd93c85f1cd1cab9f3f6) C:\Windows\system32\DRIVERS\netbt.sys
2011/03/12 10:27:10.0988 0644 NETw3v32 (a15f219208843a5a210c8cb391384453) C:\Windows\system32\DRIVERS\NETw3v32.sys
2011/03/12 10:27:11.0144 0644 nfrd960 (2e7fb731d4790a1bc6270accefacb36e) C:\Windows\system32\drivers\nfrd960.sys
2011/03/12 10:27:11.0331 0644 nmwcd (48fb907b069524f2dc7ba62a0762850c) C:\Windows\system32\drivers\ccdcmb.sys
2011/03/12 10:27:11.0440 0644 Npfs (d36f239d7cce1931598e8fb90a0dbc26) C:\Windows\system32\drivers\Npfs.sys
2011/03/12 10:27:11.0627 0644 nsiproxy (609773e344a97410ce4ebf74a8914fcf) C:\Windows\system32\drivers\nsiproxy.sys
2011/03/12 10:27:11.0768 0644 Ntfs (6a4a98cee84cf9e99564510dda4baa47) C:\Windows\system32\drivers\Ntfs.sys
2011/03/12 10:27:11.0939 0644 ntrigdigi (e875c093aec0c978a90f30c9e0dfbb72) C:\Windows\system32\drivers\ntrigdigi.sys
2011/03/12 10:27:12.0049 0644 Null (c5dbbcda07d780bda9b685df333bb41e) C:\Windows\system32\drivers\Null.sys
2011/03/12 10:27:12.0220 0644 nvraid (e69e946f80c1c31c53003bfbf50cbb7c) C:\Windows\system32\drivers\nvraid.sys
2011/03/12 10:27:12.0376 0644 nvstor (9e0ba19a28c498a6d323d065db76dffc) C:\Windows\system32\drivers\nvstor.sys
2011/03/12 10:27:12.0517 0644 nv_agp (07c186427eb8fcc3d8d7927187f260f7) C:\Windows\system32\drivers\nv_agp.sys
2011/03/12 10:27:12.0875 0644 ohci1394 (be32da025a0be1878f0ee8d6d9386cd5) C:\Windows\system32\DRIVERS\ohci1394.sys
2011/03/12 10:27:13.0063 0644 Parport (8a79fdf04a73428597e2caf9d0d67850) C:\Windows\system32\DRIVERS\parport.sys
2011/03/12 10:27:13.0234 0644 partmgr (57389fa59a36d96b3eb09d0cb91e9cdc) C:\Windows\system32\drivers\partmgr.sys
2011/03/12 10:27:13.0390 0644 Parvdm (6c580025c81caf3ae9e3617c22cad00e) C:\Windows\system32\DRIVERS\parvdm.sys
2011/03/12 10:27:13.0593 0644 pccsmcfd (fd2041e9ba03db7764b2248f02475079) C:\Windows\system32\DRIVERS\pccsmcfd.sys
2011/03/12 10:27:13.0749 0644 pci (941dc1d19e7e8620f40bbc206981efdb) C:\Windows\system32\drivers\pci.sys
2011/03/12 10:27:13.0921 0644 pciide (3b1901e401473e03eb8c874271e50c26) C:\Windows\system32\drivers\pciide.sys
2011/03/12 10:27:14.0061 0644 pcmcia (e6f3fb1b86aa519e7698ad05e58b04e5) C:\Windows\system32\drivers\pcmcia.sys
2011/03/12 10:27:14.0264 0644 PEAUTH (6349f6ed9c623b44b52ea3c63c831a92) C:\Windows\system32\drivers\peauth.sys
2011/03/12 10:27:14.0576 0644 PptpMiniport (ecfffaec0c1ecd8dbc77f39070ea1db1) C:\Windows\system32\DRIVERS\raspptp.sys
2011/03/12 10:27:14.0732 0644 Processor (0e3cef5d28b40cf273281d620c50700a) C:\Windows\system32\drivers\processr.sys
2011/03/12 10:27:14.0888 0644 PSched (99514faa8df93d34b5589187db3aa0ba) C:\Windows\system32\DRIVERS\pacer.sys
2011/03/12 10:27:15.0075 0644 ql2300 (ccdac889326317792480c0a67156a1ec) C:\Windows\system32\drivers\ql2300.sys
2011/03/12 10:27:15.0215 0644 ql40xx (81a7e5c076e59995d54bc1ed3a16e60b) C:\Windows\system32\drivers\ql40xx.sys
2011/03/12 10:27:15.0371 0644 QWAVEdrv (9f5e0e1926014d17486901c88eca2db7) C:\Windows\system32\drivers\qwavedrv.sys
2011/03/12 10:27:15.0465 0644 RapportCerberus_23945 (d9569c76a4e3fbae2cfe7ebf444ece4d) C:\ProgramData\Trusteer\Rapport\store\exts\RapportCerberus\baseline\RapportCerberus_23945.sys
2011/03/12 10:27:15.0574 0644 RapportEI (18b4e096825a1fc9863685afc292921c) C:\Program Files\Trusteer\Rapport\bin\RapportEI.sys
2011/03/12 10:27:15.0715 0644 RapportKELL (9d0683e95c55541d8453f2f6822d2ea4) C:\Windows\system32\Drivers\RapportKELL.sys
2011/03/12 10:27:15.0824 0644 RapportPG (64137ac58787a53eeb150dae1ee0312c) C:\Program Files\Trusteer\Rapport\bin\RapportPG.sys
2011/03/12 10:27:15.0995 0644 RasAcd (147d7f9c556d259924351feb0de606c3) C:\Windows\system32\DRIVERS\rasacd.sys
2011/03/12 10:27:16.0105 0644 Rasl2tp (a214adbaf4cb47dd2728859ef31f26b0) C:\Windows\system32\DRIVERS\rasl2tp.sys
2011/03/12 10:27:16.0292 0644 RasPppoe (509a98dd18af4375e1fc40bc175f1def) C:\Windows\system32\DRIVERS\raspppoe.sys
2011/03/12 10:27:16.0432 0644 RasSstp (2005f4a1e05fa09389ac85840f0a9e4d) C:\Windows\system32\DRIVERS\rassstp.sys
2011/03/12 10:27:16.0588 0644 rdbss (b14c9d5b9add2f84f70570bbbfaa7935) C:\Windows\system32\DRIVERS\rdbss.sys
2011/03/12 10:27:16.0744 0644 RDPCDD (89e59be9a564262a3fb6c4f4f1cd9899) C:\Windows\system32\DRIVERS\RDPCDD.sys
2011/03/12 10:27:16.0900 0644 rdpdr (e8bd98d46f2ed77132ba927fccb47d8b) C:\Windows\system32\drivers\rdpdr.sys
2011/03/12 10:27:17.0041 0644 RDPENCDD (9d91fe5286f748862ecffa05f8a0710c) C:\Windows\system32\drivers\rdpencdd.sys
2011/03/12 10:27:17.0181 0644 RDPWD (30bfbdfb7f95559ede971f9ddb9a00ba) C:\Windows\system32\drivers\RDPWD.sys
2011/03/12 10:27:17.0477 0644 rspndr (9c508f4074a39e8b4b31d27198146fad) C:\Windows\system32\DRIVERS\rspndr.sys
2011/03/12 10:27:17.0633 0644 RT25USBAP (d3b4872de758efa9e0740694c4461421) C:\Windows\system32\DRIVERS\rt25usbap.sys
2011/03/12 10:27:17.0789 0644 RTL8023xp (5e01ab8ab1acf8850b2d64a6fd068e46) C:\Windows\system32\DRIVERS\Rtnicxp.sys
2011/03/12 10:27:17.0930 0644 S3G700 (6e2f8ce7778315b3ffade9cf871da636) C:\Windows\system32\DRIVERS\VTGKModeDX32.sys
2011/03/12 10:27:18.0070 0644 SASDIFSV (a3281aec37e0720a2bc28034c2df2a56) C:\Program Files\SUPERAntiSpyware\SASDIFSV.SYS
2011/03/12 10:27:18.0133 0644 SASENUM (7ce61c25c159f50f9eaf6d77fc83fa35) C:\Program Files\SUPERAntiSpyware\SASENUM.SYS
2011/03/12 10:27:18.0242 0644 SASKUTIL (61db0d0756a99506207fd724e3692b25) C:\Program Files\SUPERAntiSpyware\SASKUTIL.sys
2011/03/12 10:27:18.0382 0644 sbp2port (3ce8f073a557e172b330109436984e30) C:\Windows\system32\drivers\sbp2port.sys
2011/03/12 10:27:18.0601 0644 sdbus (4339a2585708c7d9b0c0ce5aad3dd6ff) C:\Windows\system32\DRIVERS\sdbus.sys
2011/03/12 10:27:18.0757 0644 secdrv (90a3935d05b494a5a39d37e71f09a677) C:\Windows\system32\drivers\secdrv.sys
2011/03/12 10:27:18.0928 0644 Serenum (ce9ec966638ef0b10b864ddedf62a099) C:\Windows\system32\DRIVERS\serenum.sys
2011/03/12 10:27:19.0053 0644 Serial (6d663022db3e7058907784ae14b69898) C:\Windows\system32\DRIVERS\serial.sys
2011/03/12 10:27:19.0209 0644 sermouse (8af3d28a879bf75db53a0ee7a4289624) C:\Windows\system32\drivers\sermouse.sys
2011/03/12 10:27:19.0427 0644 sffdisk (103b79418da647736ee95645f305f68a) C:\Windows\system32\drivers\sffdisk.sys
2011/03/12 10:27:19.0537 0644 sffp_mmc (8fd08a310645fe872eeec6e08c6bf3ee) C:\Windows\system32\drivers\sffp_mmc.sys
2011/03/12 10:27:19.0693 0644 sffp_sd (9cfa05fcfcb7124e69cfc812b72f9614) C:\Windows\system32\drivers\sffp_sd.sys
2011/03/12 10:27:19.0849 0644 sfloppy (46ed8e91793b2e6f848015445a0ac188) C:\Windows\system32\drivers\sfloppy.sys
2011/03/12 10:27:20.0036 0644 SiSRaid2 (cedd6f4e7d84e9f98b34b3fe988373aa) C:\Windows\system32\drivers\sisraid2.sys
2011/03/12 10:27:20.0192 0644 SiSRaid4 (df843c528c4f69d12ce41ce462e973a7) C:\Windows\system32\drivers\sisraid4.sys
2011/03/12 10:27:20.0363 0644 Smb (7b75299a4d201d6a6533603d6914ab04) C:\Windows\system32\DRIVERS\smb.sys
2011/03/12 10:27:20.0551 0644 smserial (c8a58fc905c9184fa70e37f71060c64d) C:\Windows\system32\DRIVERS\smserial.sys
2011/03/12 10:27:20.0738 0644 spldr (7aebdeef071fe28b0eef2cdd69102bff) C:\Windows\system32\drivers\spldr.sys
2011/03/12 10:27:20.0863 0644 srv (ff3cbc13db84d81f56931bc922cc37c4) C:\Windows\system32\DRIVERS\srv.sys
2011/03/12 10:27:21.0050 0644 srv2 (d15959d9f69f0d39a0153e9c244f20dd) C:\Windows\system32\DRIVERS\srv2.sys
2011/03/12 10:27:21.0159 0644 srvnet (faa0d553a49e85008c6bb3781987c574) C:\Windows\system32\DRIVERS\srvnet.sys
2011/03/12 10:27:21.0362 0644 ss_bbus (7d5d8db6196e6b32277553dcd1648f2e) C:\Windows\system32\DRIVERS\ss_bbus.sys
2011/03/12 10:27:21.0487 0644 ss_bmdfl (56e2f50d93012799d6fd0328c7e0d105) C:\Windows\system32\DRIVERS\ss_bmdfl.sys
2011/03/12 10:27:21.0611 0644 ss_bmdm (578f256d5297be0ea0bbd8d5a3f500f9) C:\Windows\system32\DRIVERS\ss_bmdm.sys
2011/03/12 10:27:21.0752 0644 ss_bus (62cc4d1e21d686f940bc4df3b3af6b21) C:\Windows\system32\DRIVERS\ss_bus.sys
2011/03/12 10:27:21.0923 0644 ss_mdfl (c0806188d54b0952c0d2ef40e1348d0d) C:\Windows\system32\DRIVERS\ss_mdfl.sys
2011/03/12 10:27:22.0033 0644 ss_mdm (3a4c5d75f23202ceaf9b0ebdf3a413c0) C:\Windows\system32\DRIVERS\ss_mdm.sys
2011/03/12 10:27:22.0204 0644 StarOpen (306521935042fc0a6988d528643619b3) C:\Windows\system32\drivers\StarOpen.sys
2011/03/12 10:27:22.0376 0644 swenum (7ba58ecf0c0a9a69d44b3dca62becf56) C:\Windows\system32\DRIVERS\swenum.sys
2011/03/12 10:27:22.0547 0644 Symc8xx (192aa3ac01df071b541094f251deed10) C:\Windows\system32\drivers\symc8xx.sys
2011/03/12 10:27:22.0672 0644 Sym_hi (8c8eb8c76736ebaf3b13b633b2e64125) C:\Windows\system32\drivers\sym_hi.sys
2011/03/12 10:27:22.0766 0644 Sym_u3 (8072af52b5fd103bbba387a1e49f62cb) C:\Windows\system32\drivers\sym_u3.sys
2011/03/12 10:27:22.0969 0644 Tcpip (a474879afa4a596b3a531f3e69730dbf) C:\Windows\system32\drivers\tcpip.sys
2011/03/12 10:27:23.0171 0644 Tcpip6 (a474879afa4a596b3a531f3e69730dbf) C:\Windows\system32\DRIVERS\tcpip.sys
2011/03/12 10:27:23.0296 0644 tcpipreg (608c345a255d82a6289c2d468eb41fd7) C:\Windows\system32\drivers\tcpipreg.sys
2011/03/12 10:27:23.0421 0644 TDPIPE (5dcf5e267be67a1ae926f2df77fbcc56) C:\Windows\system32\drivers\tdpipe.sys
2011/03/12 10:27:23.0499 0644 TDTCP (389c63e32b3cefed425b61ed92d3f021) C:\Windows\system32\drivers\tdtcp.sys
2011/03/12 10:27:23.0639 0644 tdx (76b06eb8a01fc8624d699e7045303e54) C:\Windows\system32\DRIVERS\tdx.sys
2011/03/12 10:27:23.0764 0644 TermDD (3cad38910468eab9a6479e2f01db43c7) C:\Windows\system32\DRIVERS\termdd.sys
2011/03/12 10:27:23.0920 0644 tssecsrv (dcf0f056a2e4f52287264f5ab29cf206) C:\Windows\system32\DRIVERS\tssecsrv.sys
2011/03/12 10:27:24.0107 0644 tunmp (caecc0120ac49e3d2f758b9169872d38) C:\Windows\system32\DRIVERS\tunmp.sys
2011/03/12 10:27:24.0248 0644 tunnel (300db877ac094feab0be7688c3454a9c) C:\Windows\system32\DRIVERS\tunnel.sys
2011/03/12 10:27:24.0404 0644 uagp35 (7d33c4db2ce363c8518d2dfcf533941f) C:\Windows\system32\DRIVERS\uagp35.sys
2011/03/12 10:27:24.0560 0644 udfs (d9728af68c4c7693cb100b8441cbdec6) C:\Windows\system32\DRIVERS\udfs.sys
2011/03/12 10:27:24.0778 0644 uliagpkx (75e6890ebfce0841d3291b02e7a8bdb0) C:\Windows\system32\drivers\uliagpkx.sys
2011/03/12 10:27:24.0934 0644 uliahci (3cd4ea35a6221b85dcc25daa46313f8d) C:\Windows\system32\drivers\uliahci.sys
2011/03/12 10:27:25.0090 0644 UlSata (8514d0e5cd0534467c5fc61be94a569f) C:\Windows\system32\drivers\ulsata.sys
2011/03/12 10:27:25.0246 0644 ulsata2 (38c3c6e62b157a6bc46594fada45c62b) C:\Windows\system32\drivers\ulsata2.sys
2011/03/12 10:27:25.0402 0644 umbus (32cff9f809ae9aed85464492bf3e32d2) C:\Windows\system32\DRIVERS\umbus.sys
2011/03/12 10:27:25.0589 0644 USBAAPL (5c2bdc152bbab34f36473deaf7713f22) C:\Windows\system32\Drivers\usbaapl.sys
2011/03/12 10:27:25.0745 0644 usbaudio (32db9517628ff0d070682aab61e688f0) C:\Windows\system32\drivers\usbaudio.sys
2011/03/12 10:27:25.0886 0644 usbccgp (caf811ae4c147ffcd5b51750c7f09142) C:\Windows\system32\DRIVERS\usbccgp.sys
2011/03/12 10:27:26.0011 0644 usbcir (e9476e6c486e76bc4898074768fb7131) C:\Windows\system32\drivers\usbcir.sys
2011/03/12 10:27:26.0182 0644 usbehci (79e96c23a97ce7b8f14d310da2db0c9b) C:\Windows\system32\DRIVERS\usbehci.sys
2011/03/12 10:27:26.0307 0644 usbhub (4673bbcb006af60e7abddbe7a130ba42) C:\Windows\system32\DRIVERS\usbhub.sys
2011/03/12 10:27:26.0463 0644 usbohci (38dbc7dd6cc5a72011f187425384388b) C:\Windows\system32\drivers\usbohci.sys
2011/03/12 10:27:26.0541 0644 usbprint (e75c4b5269091d15a2e7dc0b6d35f2f5) C:\Windows\system32\DRIVERS\usbprint.sys
2011/03/12 10:27:26.0713 0644 usbscan (a508c9bd8724980512136b039bba65e9) C:\Windows\system32\DRIVERS\usbscan.sys
2011/03/12 10:27:26.0837 0644 USBSTOR (be3da31c191bc222d9ad503c5224f2ad) C:\Windows\system32\DRIVERS\USBSTOR.SYS
2011/03/12 10:27:26.0978 0644 usbuhci (814d653efc4d48be3b04a307eceff56f) C:\Windows\system32\DRIVERS\usbuhci.sys
2011/03/12 10:27:27.0134 0644 vga (7d92be0028ecdedec74617009084b5ef) C:\Windows\system32\DRIVERS\vgapnp.sys
2011/03/12 10:27:27.0243 0644 VgaSave (2e93ac0a1d8c79d019db6c51f036636c) C:\Windows\System32\drivers\vga.sys
2011/03/12 10:27:27.0383 0644 viaagp (045d9961e591cf0674a920b6ba3ba5cb) C:\Windows\system32\drivers\viaagp.sys
2011/03/12 10:27:27.0477 0644 ViaC7 (56a4de5f02f2e88182b0981119b4dd98) C:\Windows\system32\drivers\viac7.sys
2011/03/12 10:27:27.0586 0644 viaide (aadf5587a4063f52c2c3fed7887426fc) C:\Windows\system32\drivers\viaide.sys
2011/03/12 10:27:27.0711 0644 volmgr (69503668ac66c77c6cd7af86fbdf8c43) C:\Windows\system32\drivers\volmgr.sys
2011/03/12 10:27:27.0867 0644 volmgrx (23e41b834759917bfd6b9a0d625d0c28) C:\Windows\system32\drivers\volmgrx.sys
2011/03/12 10:27:28.0039 0644 volsnap (147281c01fcb1df9252de2a10d5e7093) C:\Windows\system32\drivers\volsnap.sys
2011/03/12 10:27:28.0210 0644 vsmraid (d984439746d42b30fc65a4c3546c6829) C:\Windows\system32\drivers\vsmraid.sys
2011/03/12 10:27:28.0460 0644 VX1000 (2fbf9e882fc28a315a86aa1f831c144e) C:\Windows\system32\DRIVERS\VX1000.sys
2011/03/12 10:27:28.0631 0644 WacomPen (48dfee8f1af7c8235d4e626f0c4fe031) C:\Windows\system32\drivers\wacompen.sys
2011/03/12 10:27:28.0756 0644 Wanarp (55201897378cca7af8b5efd874374a26) C:\Windows\system32\DRIVERS\wanarp.sys
2011/03/12 10:27:28.0834 0644 Wanarpv6 (55201897378cca7af8b5efd874374a26) C:\Windows\system32\DRIVERS\wanarp.sys
2011/03/12 10:27:28.0990 0644 Wd (afc5ad65b991c1e205cf25cfdbf7a6f4) C:\Windows\system32\drivers\wd.sys
2011/03/12 10:27:29.0115 0644 Wdf01000 (9950e3d0f08141c7e89e64456ae7dc73) C:\Windows\system32\drivers\Wdf01000.sys
2011/03/12 10:27:29.0489 0644 WmiAcpi (701a9f884a294327e9141d73746ee279) C:\Windows\system32\DRIVERS\wmiacpi.sys
2011/03/12 10:27:29.0723 0644 WpdUsb (de9d36f91a4df3d911626643debf11ea) C:\Windows\system32\DRIVERS\wpdusb.sys
2011/03/12 10:27:29.0864 0644 ws2ifsl (e3a3cb253c0ec2494d4a61f5e43a389c) C:\Windows\system32\drivers\ws2ifsl.sys
2011/03/12 10:27:30.0082 0644 WUDFRd (ac13cb789d93412106b0fb6c7eb2bcb6) C:\Windows\system32\DRIVERS\WUDFRd.sys
2011/03/12 10:27:30.0207 0644 ================================================================================
2011/03/12 10:27:30.0207 0644 Scan finished
2011/03/12 10:27:30.0207 0644 ================================================================================
2011/03/12 10:27:30.0238 2000 Detected object count: 1
2011/03/12 10:28:13.0513 2000 HKLM\SYSTEM\ControlSet001\services\ESQULserv.sys - will be deleted after reboot
2011/03/12 10:28:13.0544 2000 HKLM\SYSTEM\ControlSet002\services\ESQULserv.sys - will be deleted after reboot
2011/03/12 10:28:13.0575 2000 C:\Windows\system32\drivers\ESQULrwmvfwjpypmsfxerprqcurerulpvyvso.sys - will be deleted after reboot
2011/03/12 10:28:13.0575 2000 Rootkit.Win32.TDSS.tdl2(ESQULserv.sys) - User select action: Delete
2011/03/12 10:28:44.0401 1224 Deinitialize success

#4 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,404 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:34 AM

Posted 12 March 2011 - 07:20 PM

MBAM 732 error
Try this--from your browser open Tools, Internet Options, Connections tab, Lan settings, uncheck the box next to "use proxy...."

This routine will confirm that Internet Explorer is set to the Online mode.
Click on START - RUN and Copy/Paste the following into the run line (On Vista you can use the Search line) and click OK

REG ADD "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v GlobalUserOffline /t REG_DWORD /d 0 /f

OR
1. Uninstall Malwarebytes' Anti-Malware using Add/Remove programs in the control panel.
2. Restart your computer (very important).
3. Download and run this utility. Mbam clean
4. It will ask to restart your computer (please allow it to).
5. After the computer restarts, install the latest version from here. http://www.malwarebytes.org/mbam-download.php
Note: You will need to reactivate the program using the license you were sent.
Note: If using Free version, ignore the part about putting in your license key and activating.
Launch the program and set the Protection and Registration.
Then go to the UPDATE tab if not done during installation and check for updates.
Restart the computer again and verify that MBAM is in the task tray and run a Quick Scan and post that log.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#5 wheelie

wheelie
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:34 AM

Posted 13 March 2011 - 11:31 AM

Hi,

Thought it best to detail exactly what I've done:

The box next to "use proxy ..." was already unchecked, so I clicked Start, posted your line into the search box and hit enter (there was no OK to click). Nothing at all happened.

So, I used your OR instructions instead.
1. Uninstalled MBAM in safe mode with networking.
2. Restarted PC in normal mode(during boot-up Spybot launched so I left it running and the scan took 3 hours but found nothing) I clicked "allow" in the spybot pop-up concerning the MBAM registry entry.
3. I re-booted and downloaded MBAM Clean and thought I'd turn Spybot off then run MBAM Clean which worked fine.
4. I reinstalled MBAM version 1.50.1.1100 21/12/2010 then restarted and ran MBAM as administrator to do a Quick Scan. Spybot started scanning again so I stopped it (trying to turn it off earlier obviously didn't work).

The MBAM log is below.

Malwarebytes' Anti-Malware 1.50.1.1100
www.malwarebytes.org

Database version: 6042

Windows 6.0.6002 Service Pack 2
Internet Explorer 8.0.6001.19019

13/03/2011 16:09:56
mbam-log-2011-03-13 (16-09-55).txt

Scan type: Quick scan
Objects scanned: 154824
Time elapsed: 28 minute(s), 49 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 2
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 1
Files Infected: 5

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersi

on\Ext\PreApproved\{69725738-CD68-4f36-8D02-8C43722EE5DA}

(Adware.Hotbar) -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Window

s MSI (Trojan.Downloader) -> Quarantined and deleted successfully.

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
c:\programdata\microsoft\Windows\start menu\Programs\Hotbar

(Adware.Hotbar) -> Quarantined and deleted successfully.

Files Infected:
c:\Users\bronwen and neil\Desktop\my

documents\documents\downloads\setup (1).exe (Rogue.Installer) ->

Quarantined and deleted successfully.
c:\downloads\cueclub-dm[1].exe (Adware.TryMedia) -> Quarantined

and deleted successfully.
c:\programdata\microsoft\Windows\start

menu\Programs\Hotbar\hotbar uninstall instructions.lnk

(Adware.Hotbar) -> Quarantined and deleted successfully.
c:\programdata\microsoft\Windows\start menu\Programs\Hotbar\reset

cursor.lnk (Adware.Hotbar) -> Quarantined and deleted successfully.
c:\programdata\microsoft\Windows\start

menu\Programs\Hotbar\Weather.lnk (Adware.Hotbar) -> Quarantined

and deleted successfully.

Hope this gives you what you need.

Thanks.

#6 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,404 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:34 AM

Posted 13 March 2011 - 07:17 PM

Let's do an online scan and tell me how it is after.

ESET Online Scan
I'd like us to scan your machine with ESET OnlineScan
  • Hold down Control and click on the following link to open ESET OnlineScan in a new window.
    ESET OnlineScan
  • Click the Posted Image button.
  • For alternate browsers only: (Microsoft Internet Explorer users can skip these steps)
    • Click on Posted Image to download the ESET Smart Installer. Save it to your desktop.
    • Double click on the Posted Image icon on your desktop.
  • Check Posted Image
  • Click the Posted Image button.
  • Accept any security warnings from your browser.
  • Under scan settings, check Posted Image and check Remove found threats
  • Click Advanced settings and select the following:
    • Scan potentially unwanted applications
    • Scan for potentially unsafe applications
    • Enable Anti-Stealth technology
  • ESET will then download updates for itself, install itself, and begin scanning your computer. Please be patient as this can take some time.
  • When the scan completes, push Posted Image
  • Push Posted Image, and save the file to your desktop using a unique name, such as ESETScan. Include the contents of this report in your next reply.
  • Push the Posted Image button.
  • Push Posted Image


NOTE: In some instances if no malware is found there will be no log produced.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#7 wheelie

wheelie
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:34 AM

Posted 13 March 2011 - 08:43 PM

Hi, I have held "control" and clicked on link, and got message "ESET:404 page not found" tried clicking "ESETSmartinstaller_env.exe" but got no response. Any ideas?

#8 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,404 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:34 AM

Posted 13 March 2011 - 09:26 PM

http://www.eset.com/us/online-scanner
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#9 wheelie

wheelie
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:34 AM

Posted 14 March 2011 - 07:54 AM

Hi,

Here's the ESETScan log:

C:\Applications\Tools\AOL\stdnet_updater.exe probably a variant of Win32/StartPage.LWOOMNQ trojan deleted - quarantined
C:\Applications\Tools\AOL\comps\acs\acssetup.exe probably a variant of Win32/StartPage.LWOOMNQ trojan deleted - quarantined
C:\ProgramData\Spybot - Search & Destroy\Recovery\SweetIM39.zip Win32/Bagle.gen.zip worm cleaned by deleting - quarantined
C:\ProgramData\Spybot - Search & Destroy\Recovery\SweetIM47.zip Win32/Bagle.gen.zip worm cleaned by deleting - quarantined
C:\Users\Bronwen and Neil\AppData\LocalLow\Sony Online Entertainment\Installed Games\Free Realms\FreeRealms.exe.part a variant of Win32/Kryptik.BXZ trojan cleaned by deleting - quarantined
C:\Users\Bronwen and Neil\Downloads\mediacoder.uk02.exe a variant of Win32/Adware.DoubleD.AF application deleted - quarantined

#10 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,404 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:34 AM

Posted 14 March 2011 - 08:17 PM

Hello,TrojanDownloader:Win32/Bagle.gen!A is the generic detection for trojans that download worms from the Win32/Bagle family. They are usually distributed as attachments of spammed e-mail messages. They may also change certain system settings.

It appears there was an ESET issue that was fixed

How is it running now??

Let's dump your Temp files and do a last Safe mode scan with SAS.


Please download and scan with SUPERAntiSpyware Free
  • Double-click SUPERAntiSypware.exe and use the default settings for installation.
  • An icon will be created on your desktop. Double-click that icon to launch the program.
  • If it will not start, go to Start > All Prgrams > SUPERAntiSpyware and click on Alternate Start.
  • If asked to update the program definitions, click "Yes". If not, update the definitions before scanning by selecting "Check for Updates". (If you encounter any problems while downloading the updates, manually download them from here. Double-click on the hyperlink for Download Installer and save SASDEFINITIONS.EXE to your desktop. Then double-click on SASDEFINITIONS.EXE to install the definitions.)
  • In the Main Menu, click the Preferences... button.
  • Click the "General and Startup" tab, and under Start-up Options, make sure "Start SUPERAntiSpyware when Windows starts" box is unchecked.
  • Click the "Scanning Control" tab, and under Scanner Options, make sure the following are checked (leave all others unchecked):
    • Close browsers before scanning.
    • Scan for tracking cookies.
    • Terminate memory threats before quarantining.
  • Click the "Close" button to leave the control center screen and exit the program.
  • Do not run a scan just yet.
Reboot your computer in "Safe Mode" using the F8 method. To do this, restart your computer and after hearing your computer beep once during startup (but before the Windows icon appears) press the F8 key repeatedly. A menu will appear with several options. Use the arrow keys to navigate and select the option to run Windows in "Safe Mode".

Scan with SUPERAntiSpyware as follows:
  • Launch the program and back on the main screen, under "Scan for Harmful Software" click Scan your computer.
  • On the left, make sure you check C:\Fixed Drive.
  • On the right, under "Complete Scan", choose Perform Complete Scan and click "Next".
  • After the scan is complete, a Scan Summary box will appear with potentially harmful items that were detected. Click "OK".
  • Make sure everything has a checkmark next to it and click "Next".
  • A notification will appear that "Quarantine and Removal is Complete". Click "OK" and then click the "Finish" button to return to the main menu.
  • If asked if you want to reboot, click "Yes" and reboot normally.
  • To retrieve the removal information after reboot, launch SUPERAntispyware again.
    • Click Preferences, then click the Statistics/Logs tab.
    • Under Scanner Logs, double-click SUPERAntiSpyware Scan Log.
    • If there are several logs, click the current dated log and press View log. A text file will open in your default text editor.
    • Please copy and paste the Scan Log results in your next reply.
  • Click Close to exit the program.
If you have a problem downloading, installing or getting SAS to run, try downloading and using the SUPERAntiSpyware Portable Scanner instead. Save the randomly named file (i.e. SAS_1710895.COM) to a usb drive or CD and transfer to the infected computer. Then double-click on it to launch and scan. The file is randomly named to help keep malware from blocking the scanner.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#11 wheelie

wheelie
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:34 AM

Posted 15 March 2011 - 10:09 AM

Hi. After ESET fix and re-boot things seem to be back to normal (we can run Chrome etc, and surfing is back to usual speed). Ran SAS in safe mode, log below:

SUPERAntiSpyware Scan Log
http://www.superantispyware.com

Generated 03/15/2011 at 01:07 PM

Application Version : 4.49.1000

Core Rules Database Version : 6596
Trace Rules Database Version: 4408

Scan type : Complete Scan
Total Scan Time : 01:53:51

Memory items scanned : 320
Memory threats detected : 0
Registry items scanned : 9066
Registry threats detected : 0
File items scanned : 146121
File threats detected : 52

Adware.Tracking Cookie
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@ru4[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@imrworldwide[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@specificclick[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@doubleclick[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@content.yieldmanager[3].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@fifteensquared[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@apmebf[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@www.googleadservices[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@tribalfusion[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@server.cpmstar[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@user.lucidmedia[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@ads.telegraph.co[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@xiti[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@ad.yieldmanager[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@mediaplex[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@collective-media[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@fastclick[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@yieldmanager[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@fr.sitestat[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@adbrite[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@kantarmedia[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@adxpose[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@eset.122.2o7[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@invitemedia[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@adtech[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@ads.pubmatic[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@fr.sitestat[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@at.atwola[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@serving-sys[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@media6degrees[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@int.sitestat[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@content.yieldmanager[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@atdmt[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@ads.cnn[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@mediabrandsww[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@tacoda.at.atwola[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@bs.serving-sys[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@adviva[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@pro-market[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@msnportal.112.2o7[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@revsci[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@advertising[2].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@adserver.adtechus[1].txt
C:\Users\Bronwen and Neil\AppData\Roaming\Microsoft\Windows\Cookies\bronwen_and_neil@www.fifteensquared[1].txt
.atdmt.com [ C:\Users\Bronwen and Neil\AppData\Local\Google\Chrome\User Data\Default\Cookies ]
.atdmt.com [ C:\Users\Bronwen and Neil\AppData\Local\Google\Chrome\User Data\Default\Cookies ]
.atdmt.com [ C:\Users\Bronwen and Neil\AppData\Local\Google\Chrome\User Data\Default\Cookies ]
.atdmt.com [ C:\Users\Bronwen and Neil\AppData\Local\Google\Chrome\User Data\Default\Cookies ]
.doubleclick.net [ C:\Users\Bronwen and Neil\AppData\Local\Google\Chrome\User Data\Default\Cookies ]
games.mochimedia.com [ C:\Users\Bronwen and Neil\AppData\Roaming\Macromedia\Flash Player\#SharedObjects\P6XTGM59 ]
ia.media-imdb.com [ C:\Users\Bronwen and Neil\AppData\Roaming\Macromedia\Flash Player\#SharedObjects\P6XTGM59 ]
s0.2mdn.net [ C:\Users\Bronwen and Neil\AppData\Roaming\Macromedia\Flash Player\#SharedObjects\P6XTGM59 ]

#12 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,404 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:34 AM

Posted 15 March 2011 - 02:27 PM

OK< looks good here. Lets do this bit of mop up and get a bit of junk offf free up a little space and you should be running nicely. Check and see if your Hard drive needs Defragmenting.

If there are no more problems or signs of infection, you should Create a New Restore Point to prevent possible reinfection from an old one. Some of the malware you picked up could have been saved in System Restore. Since this is a protected directory your tools cannot access to delete these files, they sometimes can reinfect your system if you accidentally use an old restore point. Setting a new restore point AFTER cleaning your system will help prevent this and enable your computer to "roll-back" to a clean working state.

The easiest and safest way to do this is:
  • Go to Start > Programs > Accessories > System Tools and click "System Restore".
  • Choose the radio button marked "Create a Restore Point" on the first screen then click "Next". Give the R.P. a name, then click "Create". The new point will be stamped with the current date and time. Keep a log of this so you can find it easily should you need to use System Restore.
  • Then use Disk Cleanup to remove all but the most recently created Restore Point.
  • Go to Start > Run and type: Cleanmgr
  • Click "Ok". Disk Cleanup will scan your files for several minutes, then open.
  • Click the "More Options" tab, then click the "Clean up" button under System Restore.
  • Click Ok. You will be prompted with "Are you sure you want to delete all but the most recent restore point?"
  • Click Yes, then click Ok.
  • Click Yes again when prompted with "Are you sure you want to perform these actions?"
  • Disk Cleanup will remove the files and close automatically.
Vista Users can refer to these links: Create a New Restore Point and Disk Cleanup.

Tips to protect yourself against malware and reduce the potential for re-infection:Avoid gaming sites, pirated software, cracking tools, keygens, and peer-to-peer (P2P) file sharing programs. They are a security risk which can make your computer susceptible to a smörgåsbord of malware infections, remote attacks, exposure of personal information, and identity theft. Many malicious worms and Trojans spread across P2P file sharing networks, gaming and underground sites. Users visiting such pages may see innocuous-looking banner ads containing code which can trigger pop-up ads and malicious Flash ads that install viruses, Trojans and spyware. Ads are a target for hackers because they offer a stealthy way to distribute malware to a wide range of Internet users. The best way to reduce the risk of infection is to avoid these types of web sites and not use any P2P applications. Read P2P Software User Advisories and Risks of File-Sharing Technology.

Keeping Autorun enabled on USB and other removable drives has become a significant security risk due to the increasing number of malware variants that can infect them and transfer the infection to your computer. To learn more about this risk, please read:
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#13 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,404 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:34 AM

Posted 15 March 2011 - 02:37 PM

You look good.. I want no money,the thank you is fine.
You can see what programs may need updating by running ...

How to detect vulnerable and out-dated programs using Secunia Personal Software Inspector
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#14 wheelie

wheelie
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:34 AM

Posted 15 March 2011 - 06:35 PM

Hi. I dont think the last reply was for me was it? Although obviously I'm thankful!
I have created a new restore point and run the clean up. This all seemed to take a very long time and I'm only just getting back to you now because of this. It's hard to explain, when IE or Chrome is up and running it seems ok, but it takes 35 mins to restart the pc(it was 5-10 mins previously). Maybe we have too much rubbish going on at start-up but something is still not right - the screen at the moment is not keeping up with my typing and I'm certainly no expert. I haven't run a defrag yet (I'll do it now).I wanted to reply to you first and I don't know how long the defrag will take.

#15 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,404 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:34 AM

Posted 15 March 2011 - 08:03 PM

OK, well i had thought you were done as it's clean.. But I would say that yes you may have too many items at start up and did you originally make your first post in the Vista forum? AS thar BBCode issue could definately be it.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users