Unsolved
This post is more than 5 years old
2 Intern
•
161 Posts
0
3205
February 10th, 2011 21:00
Is my recycle bin corrupted?
Hi, everyone, thanks in advance for any assistance, again :). Just lately in the last few days, I have been seeing this msg from my recycle bin. First when I notice something in my bin, I always delete it. Sometimes, I think it is already cleared but it will show papers, then when I choose empty bin, I get a msg that asks if I want to delete Windows y/n. I say yes and then I get a msg saying Cannot delete Dc1, access is denied. I restart and it empties. Also, when I open it before restart there will be nothing in the bin. I have checked around, in 2007 there was a post in the OS forum for the same thing, sent me to kelly's tweaks line 64, but when I ran this fix, msg said windows cannot open this file restorerecyclebin [1].reg. I have looked through windows files to find a recycle bin folder, could not find. I used search companion to find, no results. Another option suggested to install recovery console, but that is too advanced for me. Another said use the following cmds in the cmd.exe prompt first : rd/s c:\recycler - nothing found, second: rd/s/q C:\$Recycle:bin - no such program exists, third: attrib -s -h recycler del recycler - nothing found. Spyware blaster- all protected, Malwarebytes-Antimalwarebytes- nothing found, MS security essentials nothing found, Malicious software removal tool, nothing found, Live one care free scanner, nothing found. CHKDSK - not sure what was found, a UDN? Journal was up but before I could read it the machine rebooted, ran again and still could not read it. This does not occur all the time, I would say that it has happened about ten times in the last few days. I had Winpatrol installed, but uninstalled it because it keep freezing up. Everything seems to be working ok, except for this one issue right now. I am running winxp pro, ie8, I do have firefox installed just don't use it. Dell Dimension 3000. Any suggestions? Where is my recycle bin folder located? Another thread said to delete this folder and windows would create a new one on restart. Thanks, again.
kevin27_b3d29f
2 Intern
•
1.5K Posts
0
February 12th, 2011 08:00
Hi,
Is there a file is the Recycle bin that will not delete or is the recycle bin empty but the trash can icon looks full?
Give CCleaner a run, reboot the system, create some files using Notepad and save them to the desktop, they don't have to contain anything special, just type some jibberish into them and save them. Once you have three or four files saved to the desktop, delete them and then empty the recycle bin.
Are you still getting the same error message?
liz1954
2 Intern
•
161 Posts
0
February 12th, 2011 08:00
K27, Hi, there is nothing in the recycle bin, but the trash icon looks full. I made up some notepads and deleted them after running cleaner. No problems. But the error msgs still appear intermittently. Last night I got one for cannot delete dc1, today I got one for dc2. When I get the one for d c1 it usually asks if I want to delet windows. When I get this msg, I reboot and my recycle bin is clear again. Then I have no problems deleting things for a while. It is intermittent. My computer went crazy last night and I had to call Dell. The operator told me I had a virus and cleaned out two infections that were on my machine despite all the stuff I had to check for problems. I paid for the service and we signed off with no inspections. As of this moment I still have malwarebytes-antimalwarebytes and a trial version of Kaspersky (do not want to buy until I can talk with someone in their office.) Both checked out today after complete scans. No issues. Therefore this might be a OS forum issue. What do you suggest? Thanks, Liz.
Bugbatter
4 Apprentice
•
20.5K Posts
0
February 12th, 2011 09:00
1. Which "infections" were cleaned and by what program?
2. Is this the computer that we just fixed on this forum and why are you using a trial version of Kaspersky? I thought you were using Microsoft Security Essentials. Or is this a different computer? We worked with Malwarebytes Anti-Malware not "antimalwarebytes" <-- That is a rogue program.
3. Why did you call and pay for tech support when you could have come back to this forum and have a trained security analyst re-check for malware?
If this is the same computer, considering all the various problems and your history with multiple scanners and registry cleaners, if I were you I would reformat/reinstall the operating system to start fresh.
liz1954
2 Intern
•
161 Posts
0
February 12th, 2011 15:00
Bugbatter, Hi, yes this is the same machine. Dell went into some hidded files and remover to files and said they were infections. He used Kaspersky TDDS, I think those were the initials, removal tool. I still have Malwarebytes-antimalware bytes downloaded from cnet, I must have just mistyped the name. The computer was running fine, then I started to get the recycle bin errors. Last night I had to call Dell because I could do nothing with my computer, my desktop changed and I could not get system restore to work. I am using the trial Kapersky for now until I can talk with their office and get my questions answered and then I will probably purchase it. Evidently MS security essentials did not catch this infection nor, Malwarebytes, nor any other scanner I used. I would have gone to your forums again, but I needed to have a working computer for the morning 12 Feb. I was ready to just reinstall my system, but Dell said that the infection would still be there and he could remove it now. Right now my machine is ok except for the intermittent error msg listed earlier. I also still have secunia and WOT. I have removed everything else. I believe that MS security essentials must have let the infection in. Do you still think a clean install would be a good idea? Please advise me, again. I apologize if you believe that I wasted your time, but the computer was okay then. Thank You, Liz.
Bugbatter
4 Apprentice
•
20.5K Posts
0
February 12th, 2011 16:00
Between the time we cleaned your computer and when you called Dell, where did you go to get infected?
When you reformat/reinstall an operating system the infection will be gone. You must have misunderstood the tech.When we worked on your computer on this forum, you did NOT have symptoms of a TDSS infection. TDSS is a rootkit. If you had that, you would have been having major problems, in addition to having it reported by DDS. Neither happened.
I would be interested in seeing the TDSSKiller report. Assuming the tech had you save it, it may still here: C:\ folder) in the form of "TDSSKiller.___log.txt". Please copy and paste the contents of that file here.
I don't believe that I wasted my time, but I do believe you may have wasted your money.
Thanks.
liz1954
2 Intern
•
161 Posts
0
February 12th, 2011 20:00
2011/02/11 23:56:37.0437 3440 TDSS rootkit removing tool 2.4.17.0 Feb 10 2011 11:07:20
2011/02/11 23:56:37.0765 3440 ================================================================================
2011/02/11 23:56:37.0765 3440 SystemInfo:
2011/02/11 23:56:37.0765 3440
2011/02/11 23:56:37.0765 3440 OS Version: 5.1.2600 ServicePack: 3.0
2011/02/11 23:56:37.0765 3440 Product type: Workstation
2011/02/11 23:56:37.0765 3440 ComputerName: ELIZABETH
2011/02/11 23:56:37.0765 3440 UserName: Administrator
2011/02/11 23:56:37.0765 3440 Windows directory: C:\WINDOWS
2011/02/11 23:56:37.0765 3440 System windows directory: C:\WINDOWS
2011/02/11 23:56:37.0765 3440 Processor architecture: Intel x86
2011/02/11 23:56:37.0765 3440 Number of processors: 1
2011/02/11 23:56:37.0765 3440 Page size: 0x1000
2011/02/11 23:56:37.0765 3440 Boot type: Safe boot with network
2011/02/11 23:56:37.0765 3440 ================================================================================
2011/02/11 23:56:38.0015 3440 Initialize success
2011/02/11 23:56:40.0796 3464 ================================================================================
2011/02/11 23:56:40.0796 3464 Scan started
2011/02/11 23:56:40.0796 3464 Mode: Manual;
2011/02/11 23:56:40.0796 3464 ================================================================================
2011/02/11 23:56:42.0125 3464 ACPI (8fd99680a539792a30e97944fdaecf17) C:\WINDOWS\system32\DRIVERS\ACPI.sys
2011/02/11 23:56:42.0234 3464 ACPIEC (9859c0f6936e723e4892d7141b1327d5) C:\WINDOWS\system32\drivers\ACPIEC.sys
2011/02/11 23:56:42.0421 3464 aec (8bed39e3c35d6a489438b8141717a557) C:\WINDOWS\system32\drivers\aec.sys
2011/02/11 23:56:42.0562 3464 Afc (a7b8a3a79d35215d798a300df49ed23f) C:\WINDOWS\system32\drivers\Afc.sys
2011/02/11 23:56:42.0687 3464 AFD (7e775010ef291da96ad17ca4b17137d7) C:\WINDOWS\System32\drivers\afd.sys
2011/02/11 23:56:43.0281 3464 AsyncMac (b153affac761e7f5fcfa822b9c4e97bc) C:\WINDOWS\system32\DRIVERS\asyncmac.sys
2011/02/11 23:56:43.0484 3464 atapi (9f3a2f5aa6875c72bf062c712cfa2674) C:\WINDOWS\system32\DRIVERS\atapi.sys
2011/02/11 23:56:43.0750 3464 Atmarpc (9916c1225104ba14794209cfa8012159) C:\WINDOWS\system32\DRIVERS\atmarpc.sys
2011/02/11 23:56:43.0937 3464 audstub (d9f724aa26c010a217c97606b160ed68) C:\WINDOWS\system32\DRIVERS\audstub.sys
2011/02/11 23:56:44.0093 3464 Beep (da1f27d85e0d1525f6621372e7b685e9) C:\WINDOWS\system32\drivers\Beep.sys
2011/02/11 23:56:44.0265 3464 cbidf2k (90a673fc8e12a79afbed2576f6a7aaf9) C:\WINDOWS\system32\drivers\cbidf2k.sys
2011/02/11 23:56:44.0515 3464 Cdaudio (c1b486a7658353d33a10cc15211a873b) C:\WINDOWS\system32\drivers\Cdaudio.sys
2011/02/11 23:56:44.0609 3464 Cdfs (c885b02847f5d2fd45a24e219ed93b32) C:\WINDOWS\system32\drivers\Cdfs.sys
2011/02/11 23:56:44.0718 3464 Cdrom (1f4260cc5b42272d71f79e570a27a4fe) C:\WINDOWS\system32\DRIVERS\cdrom.sys
2011/02/11 23:56:45.0453 3464 Disk (044452051f3e02e7963599fc8f4f3e25) C:\WINDOWS\system32\DRIVERS\disk.sys
2011/02/11 23:56:45.0578 3464 dmboot (d992fe1274bde0f84ad826acae022a41) C:\WINDOWS\system32\drivers\dmboot.sys
2011/02/11 23:56:45.0750 3464 dmio (7c824cf7bbde77d95c08005717a95f6f) C:\WINDOWS\system32\drivers\dmio.sys
2011/02/11 23:56:45.0906 3464 dmload (e9317282a63ca4d188c0df5e09c6ac5f) C:\WINDOWS\system32\drivers\dmload.sys
2011/02/11 23:56:46.0046 3464 DMusic (8a208dfcf89792a484e76c40e5f50b45) C:\WINDOWS\system32\drivers\DMusic.sys
2011/02/11 23:56:46.0312 3464 drmkaud (8f5fcff8e8848afac920905fbd9d33c8) C:\WINDOWS\system32\drivers\drmkaud.sys
2011/02/11 23:56:46.0500 3464 Fastfat (38d332a6d56af32635675f132548343e) C:\WINDOWS\system32\drivers\Fastfat.sys
2011/02/11 23:56:46.0656 3464 Fdc (92cdd60b6730b9f50f6a1a0c1f8cdc81) C:\WINDOWS\system32\DRIVERS\fdc.sys
2011/02/11 23:56:46.0843 3464 Fips (d45926117eb9fa946a6af572fbe1caa3) C:\WINDOWS\system32\drivers\Fips.sys
2011/02/11 23:56:47.0015 3464 Flpydisk (9d27e7b80bfcdf1cdd9b555862d5e7f0) C:\WINDOWS\system32\DRIVERS\flpydisk.sys
2011/02/11 23:56:47.0218 3464 FltMgr (b2cf4b0786f8212cb92ed2b50c6db6b0) C:\WINDOWS\system32\drivers\fltmgr.sys
2011/02/11 23:56:47.0437 3464 fssfltr (e0087225b137e57239ff40f8ae82059b) C:\WINDOWS\system32\DRIVERS\fssfltr_tdi.sys
2011/02/11 23:56:47.0578 3464 Fs_Rec (3e1e2bd4f39b0e2b7dc4f4d2bcc2779a) C:\WINDOWS\system32\drivers\Fs_Rec.sys
2011/02/11 23:56:47.0718 3464 Ftdisk (6ac26732762483366c3969c9e4d2259d) C:\WINDOWS\system32\DRIVERS\ftdisk.sys
2011/02/11 23:56:47.0859 3464 Gpc (0a02c63c8b144bd8c86b103dee7c86a2) C:\WINDOWS\system32\DRIVERS\msgpc.sys
2011/02/11 23:56:48.0015 3464 HidUsb (ccf82c5ec8a7326c3066de870c06daf1) C:\WINDOWS\system32\DRIVERS\hidusb.sys
2011/02/11 23:56:48.0250 3464 HTTP (f80a415ef82cd06ffaf0d971528ead38) C:\WINDOWS\system32\Drivers\HTTP.sys
2011/02/11 23:56:48.0531 3464 i8042prt (4a0b06aa8943c1e332520f7440c0aa30) C:\WINDOWS\system32\DRIVERS\i8042prt.sys
2011/02/11 23:56:48.0734 3464 ialm (9a883c3c4d91292c0d09de7c728e781c) C:\WINDOWS\system32\DRIVERS\ialmnt5.sys
2011/02/11 23:56:48.0921 3464 Imapi (083a052659f5310dd8b6a6cb05edcf8e) C:\WINDOWS\system32\DRIVERS\imapi.sys
2011/02/11 23:56:49.0187 3464 IntelIde (b5466a9250342a7aa0cd1fba13420678) C:\WINDOWS\system32\DRIVERS\intelide.sys
2011/02/11 23:56:49.0296 3464 intelppm (8c953733d8f36eb2133f5bb58808b66b) C:\WINDOWS\system32\DRIVERS\intelppm.sys
2011/02/11 23:56:49.0421 3464 Ip6Fw (3bb22519a194418d5fec05d800a19ad0) C:\WINDOWS\system32\drivers\ip6fw.sys
2011/02/11 23:56:49.0546 3464 IpFilterDriver (731f22ba402ee4b62748adaf6363c182) C:\WINDOWS\system32\DRIVERS\ipfltdrv.sys
2011/02/11 23:56:49.0656 3464 IpInIp (b87ab476dcf76e72010632b5550955f5) C:\WINDOWS\system32\DRIVERS\ipinip.sys
2011/02/11 23:56:49.0796 3464 IpNat (cc748ea12c6effde940ee98098bf96bb) C:\WINDOWS\system32\DRIVERS\ipnat.sys
2011/02/11 23:56:49.0921 3464 IPSec (23c74d75e36e7158768dd63d92789a91) C:\WINDOWS\system32\DRIVERS\ipsec.sys
2011/02/11 23:56:50.0015 3464 IRENUM (c93c9ff7b04d772627a3646d89f7bf89) C:\WINDOWS\system32\DRIVERS\irenum.sys
2011/02/11 23:56:50.0125 3464 isapnp (05a299ec56e52649b1cf2fc52d20f2d7) C:\WINDOWS\system32\DRIVERS\isapnp.sys
2011/02/11 23:56:50.0234 3464 Kbdclass (463c1ec80cd17420a542b7f36a36f128) C:\WINDOWS\system32\DRIVERS\kbdclass.sys
2011/02/11 23:56:50.0359 3464 kmixer (692bcf44383d056aed41b045a323d378) C:\WINDOWS\system32\drivers\kmixer.sys
2011/02/11 23:56:50.0453 3464 KSecDD (b467646c54cc746128904e1654c750c1) C:\WINDOWS\system32\drivers\KSecDD.sys
2011/02/11 23:56:50.0718 3464 MASPINT (a2ae666cee860babe7fa6f1662b71737) C:\WINDOWS\system32\drivers\MASPINT.sys
2011/02/11 23:56:50.0953 3464 mnmdd (4ae068242760a1fb6e1a44bf4e16afa6) C:\WINDOWS\system32\drivers\mnmdd.sys
2011/02/11 23:56:51.0109 3464 Modem (dfcbad3cec1c5f964962ae10e0bcc8e1) C:\WINDOWS\system32\drivers\Modem.sys
2011/02/11 23:56:51.0250 3464 Mouclass (35c9e97194c8cfb8430125f8dbc34d04) C:\WINDOWS\system32\DRIVERS\mouclass.sys
2011/02/11 23:56:51.0390 3464 mouhid (b1c303e17fb9d46e87a98e4ba6769685) C:\WINDOWS\system32\DRIVERS\mouhid.sys
2011/02/11 23:56:51.0500 3464 MountMgr (a80b9a0bad1b73637dbcbba7df72d3fd) C:\WINDOWS\system32\drivers\MountMgr.sys
2011/02/11 23:56:51.0671 3464 MpFilter (7e34bfa1a7b60bba1da03d677f16cd63) C:\WINDOWS\system32\DRIVERS\MpFilter.sys
2011/02/11 23:56:52.0750 3464 MRxDAV (11d42bb6206f33fbb3ba0288d3ef81bd) C:\WINDOWS\system32\DRIVERS\mrxdav.sys
2011/02/11 23:56:52.0968 3464 MRxSmb (f3aefb11abc521122b67095044169e98) C:\WINDOWS\system32\DRIVERS\mrxsmb.sys
2011/02/11 23:56:53.0156 3464 Msfs (c941ea2454ba8350021d774daf0f1027) C:\WINDOWS\system32\drivers\Msfs.sys
2011/02/11 23:56:53.0296 3464 MSKSSRV (d1575e71568f4d9e14ca56b7b0453bf1) C:\WINDOWS\system32\drivers\MSKSSRV.sys
2011/02/11 23:56:53.0437 3464 MSPCLOCK (325bb26842fc7ccc1fcce2c457317f3e) C:\WINDOWS\system32\drivers\MSPCLOCK.sys
2011/02/11 23:56:53.0562 3464 MSPQM (bad59648ba099da4a17680b39730cb3d) C:\WINDOWS\system32\drivers\MSPQM.sys
2011/02/11 23:56:53.0687 3464 mssmbios (af5f4f3f14a8ea2c26de30f7a1e17136) C:\WINDOWS\system32\DRIVERS\mssmbios.sys
2011/02/11 23:56:53.0875 3464 Mup (2f625d11385b1a94360bfc70aaefdee1) C:\WINDOWS\system32\drivers\Mup.sys
2011/02/11 23:56:54.0015 3464 NDIS (1df7f42665c94b825322fae71721130d) C:\WINDOWS\system32\drivers\NDIS.sys
2011/02/11 23:56:54.0140 3464 NdisTapi (1ab3d00c991ab086e69db84b6c0ed78f) C:\WINDOWS\system32\DRIVERS\ndistapi.sys
2011/02/11 23:56:54.0218 3464 Ndisuio (f927a4434c5028758a842943ef1a3849) C:\WINDOWS\system32\DRIVERS\ndisuio.sys
2011/02/11 23:56:54.0328 3464 NdisWan (edc1531a49c80614b2cfda43ca8659ab) C:\WINDOWS\system32\DRIVERS\ndiswan.sys
2011/02/11 23:56:54.0453 3464 NDProxy (9282bd12dfb069d3889eb3fcc1000a9b) C:\WINDOWS\system32\drivers\NDProxy.sys
2011/02/11 23:56:54.0578 3464 NetBIOS (5d81cf9a2f1a3a756b66cf684911cdf0) C:\WINDOWS\system32\DRIVERS\netbios.sys
2011/02/11 23:56:54.0687 3464 NetBT (74b2b2f5bea5e9a3dc021d685551bd3d) C:\WINDOWS\system32\DRIVERS\netbt.sys
2011/02/11 23:56:54.0921 3464 Npfs (3182d64ae053d6fb034f44b6def8034a) C:\WINDOWS\system32\drivers\Npfs.sys
2011/02/11 23:56:55.0031 3464 Ntfs (78a08dd6a8d65e697c18e1db01c5cdca) C:\WINDOWS\system32\drivers\Ntfs.sys
2011/02/11 23:56:55.0281 3464 Null (73c1e1f395918bc2c6dd67af7591a3ad) C:\WINDOWS\system32\drivers\Null.sys
2011/02/11 23:56:55.0375 3464 NwlnkFlt (b305f3fad35083837ef46a0bbce2fc57) C:\WINDOWS\system32\DRIVERS\nwlnkflt.sys
2011/02/11 23:56:55.0468 3464 NwlnkFwd (c99b3415198d1aab7227f2c88fd664b9) C:\WINDOWS\system32\DRIVERS\nwlnkfwd.sys
2011/02/11 23:56:55.0578 3464 OMCI (cec7e2c6c1fa00c7ab2f5434f848ae51) C:\WINDOWS\SYSTEM32\DRIVERS\OMCI.SYS
2011/02/11 23:56:55.0765 3464 Parport (5575faf8f97ce5e713d108c2a58d7c7c) C:\WINDOWS\system32\DRIVERS\parport.sys
2011/02/11 23:56:55.0921 3464 PartMgr (beb3ba25197665d82ec7065b724171c6) C:\WINDOWS\system32\drivers\PartMgr.sys
2011/02/11 23:56:56.0078 3464 ParVdm (70e98b3fd8e963a6a46a2e6247e0bea1) C:\WINDOWS\system32\drivers\ParVdm.sys
2011/02/11 23:56:56.0203 3464 PCI (a219903ccf74233761d92bef471a07b1) C:\WINDOWS\system32\DRIVERS\pci.sys
2011/02/11 23:56:56.0406 3464 PCIIde (ccf5f451bb1a5a2a522a76e670000ff0) C:\WINDOWS\system32\DRIVERS\pciide.sys
2011/02/11 23:56:56.0562 3464 Pcmcia (9e89ef60e9ee05e3f2eef2da7397f1c1) C:\WINDOWS\system32\drivers\Pcmcia.sys
2011/02/11 23:56:57.0046 3464 PptpMiniport (efeec01b1d3cf84f16ddd24d9d9d8f99) C:\WINDOWS\system32\DRIVERS\raspptp.sys
2011/02/11 23:56:57.0140 3464 PSched (09298ec810b07e5d582cb3a3f9255424) C:\WINDOWS\system32\DRIVERS\psched.sys
2011/02/11 23:56:57.0296 3464 PSI (d24dfd16a1e2a76034df5aa18125c35d) C:\WINDOWS\system32\DRIVERS\psi_mf.sys
2011/02/11 23:56:57.0437 3464 Ptilink (80d317bd1c3dbc5d4fe7b1678c60cadd) C:\WINDOWS\system32\DRIVERS\ptilink.sys
2011/02/11 23:56:58.0062 3464 RasAcd (fe0d99d6f31e4fad8159f690d68ded9c) C:\WINDOWS\system32\DRIVERS\rasacd.sys
2011/02/11 23:56:58.0234 3464 Rasl2tp (11b4a627bc9614b885c4969bfa5ff8a6) C:\WINDOWS\system32\DRIVERS\rasl2tp.sys
2011/02/11 23:56:58.0343 3464 RasPppoe (5bc962f2654137c9909c3d4603587dee) C:\WINDOWS\system32\DRIVERS\raspppoe.sys
2011/02/11 23:56:58.0437 3464 Raspti (fdbb1d60066fcfbb7452fd8f9829b242) C:\WINDOWS\system32\DRIVERS\raspti.sys
2011/02/11 23:56:58.0593 3464 Rdbss (7ad224ad1a1437fe28d89cf22b17780a) C:\WINDOWS\system32\DRIVERS\rdbss.sys
2011/02/11 23:56:58.0734 3464 RDPCDD (4912d5b403614ce99c28420f75353332) C:\WINDOWS\system32\DRIVERS\RDPCDD.sys
2011/02/11 23:56:58.0921 3464 rdpdr (15cabd0f7c00c47c70124907916af3f1) C:\WINDOWS\system32\DRIVERS\rdpdr.sys
2011/02/11 23:56:59.0046 3464 RDPWD (6728e45b66f93c08f11de2e316fc70dd) C:\WINDOWS\system32\drivers\RDPWD.sys
2011/02/11 23:56:59.0156 3464 redbook (f828dd7e1419b6653894a8f97a0094c5) C:\WINDOWS\system32\DRIVERS\redbook.sys
2011/02/11 23:56:59.0312 3464 RTL8023xp (b4a166449464a4bf4a8ba0ccc0c00e16) C:\WINDOWS\system32\DRIVERS\Rtnicxp.sys
2011/02/11 23:56:59.0500 3464 Secdrv (90a3935d05b494a5a39d37e71f09a677) C:\WINDOWS\system32\DRIVERS\secdrv.sys
2011/02/11 23:56:59.0703 3464 senfilt (b9c7617c1e8ab6fdff75d3c8dafcb4c8) C:\WINDOWS\system32\drivers\senfilt.sys
2011/02/11 23:56:59.0890 3464 serenum (0f29512ccd6bead730039fb4bd2c85ce) C:\WINDOWS\system32\DRIVERS\serenum.sys
2011/02/11 23:57:00.0000 3464 Serial (cca207a8896d4c6a0c9ce29a4ae411a7) C:\WINDOWS\system32\DRIVERS\serial.sys
2011/02/11 23:57:00.0203 3464 Sfloppy (8e6b8c671615d126fdc553d1e2de5562) C:\WINDOWS\system32\drivers\Sfloppy.sys
2011/02/11 23:57:00.0437 3464 smwdm (c6d9959e493682f872a639b6ec1b4a08) C:\WINDOWS\system32\drivers\smwdm.sys
2011/02/11 23:57:00.0640 3464 splitter (ab8b92451ecb048a4d1de7c3ffcb4a9f) C:\WINDOWS\system32\drivers\splitter.sys
2011/02/11 23:57:00.0750 3464 sr (76bb022c2fb6902fd5bdd4f78fc13a5d) C:\WINDOWS\system32\DRIVERS\sr.sys
2011/02/11 23:57:00.0937 3464 Srv (0f6aefad3641a657e18081f52d0c15af) C:\WINDOWS\system32\DRIVERS\srv.sys
2011/02/11 23:57:01.0109 3464 swenum (3941d127aef12e93addf6fe6ee027e0f) C:\WINDOWS\system32\DRIVERS\swenum.sys
2011/02/11 23:57:01.0218 3464 swmidi (8ce882bcc6cf8a62f2b2323d95cb3d01) C:\WINDOWS\system32\drivers\swmidi.sys
2011/02/11 23:57:01.0562 3464 sysaudio (8b83f3ed0f1688b4958f77cd6d2bf290) C:\WINDOWS\system32\drivers\sysaudio.sys
2011/02/11 23:57:01.0718 3464 Tcpip (9aefa14bd6b182d61e3119fa5f436d3d) C:\WINDOWS\system32\DRIVERS\tcpip.sys
2011/02/11 23:57:01.0906 3464 TDPIPE (6471a66807f5e104e4885f5b67349397) C:\WINDOWS\system32\drivers\TDPIPE.sys
2011/02/11 23:57:02.0031 3464 TDTCP (c56b6d0402371cf3700eb322ef3aaf61) C:\WINDOWS\system32\drivers\TDTCP.sys
2011/02/11 23:57:02.0171 3464 TermDD (88155247177638048422893737429d9e) C:\WINDOWS\system32\DRIVERS\termdd.sys
2011/02/11 23:57:02.0343 3464 Udfs (5787b80c2e3c5e2f56c2a233d91fa2c9) C:\WINDOWS\system32\drivers\Udfs.sys
2011/02/11 23:57:02.0593 3464 Update (402ddc88356b1bac0ee3dd1580c76a31) C:\WINDOWS\system32\DRIVERS\update.sys
2011/02/11 23:57:02.0781 3464 usbccgp (173f317ce0db8e21322e71b7e60a27e8) C:\WINDOWS\system32\DRIVERS\usbccgp.sys
2011/02/11 23:57:02.0921 3464 usbehci (65dcf09d0e37d4c6b11b5b0b76d470a7) C:\WINDOWS\system32\DRIVERS\usbehci.sys
2011/02/11 23:57:03.0062 3464 usbhub (1ab3cdde553b6e064d2e754efe20285c) C:\WINDOWS\system32\DRIVERS\usbhub.sys
2011/02/11 23:57:03.0171 3464 usbprint (a717c8721046828520c9edf31288fc00) C:\WINDOWS\system32\DRIVERS\usbprint.sys
2011/02/11 23:57:03.0312 3464 usbscan (a0b8cf9deb1184fbdd20784a58fa75d4) C:\WINDOWS\system32\DRIVERS\usbscan.sys
2011/02/11 23:57:03.0375 3464 usbstor (a32426d9b14a089eaa1d922e0c5801a9) C:\WINDOWS\system32\DRIVERS\USBSTOR.SYS
2011/02/11 23:57:03.0531 3464 usbuhci (26496f9dee2d787fc3e61ad54821ffe6) C:\WINDOWS\system32\DRIVERS\usbuhci.sys
2011/02/11 23:57:03.0656 3464 VgaSave (0d3a8fafceacd8b7625cd549757a7df1) C:\WINDOWS\System32\drivers\vga.sys
2011/02/11 23:57:03.0812 3464 VolSnap (4c8fcb5cc53aab716d810740fe59d025) C:\WINDOWS\system32\drivers\VolSnap.sys
2011/02/11 23:57:03.0953 3464 Wanarp (e20b95baedb550f32dd489265c1da1f6) C:\WINDOWS\system32\DRIVERS\wanarp.sys
2011/02/11 23:57:04.0187 3464 wdmaud (6768acf64b18196494413695f0c3a00f) C:\WINDOWS\system32\drivers\wdmaud.sys
2011/02/11 23:57:04.0546 3464 WudfPf (f15feafffbb3644ccc80c5da584e6311) C:\WINDOWS\system32\DRIVERS\WudfPf.sys
2011/02/11 23:57:04.0656 3464 WudfRd (28b524262bce6de1f7ef9f510ba3985b) C:\WINDOWS\system32\DRIVERS\wudfrd.sys
2011/02/11 23:57:04.0937 3464 ================================================================================
2011/02/11 23:57:04.0937 3464 Scan finished
2011/02/11 23:57:04.0937 3464 ================================================================================
2011/02/11 23:57:12.0625 3436 Deinitialize success
Bugbatter, this is the log , found it on my local disk when I looked in my computer. Sorry for the small type, this is a lot of pages. I did not think that the operator would lie but he did say that if I reformatted and did a clean install that my infection would be there. That is why I said go ahead when he said he would remove them. Thank You.
Bugbatter
4 Apprentice
•
20.5K Posts
0
February 13th, 2011 05:00
That log is clean. There was no TDSS infection removed. There was no TDSS infection to begin with.
I don't know if Tech Support lied or whether there was a misunderstanding somewhere along the the way. He should not have left the log on your computer either. You can delete it now if you want to. Considering that you communicated with him via phone, I supposed there is no way to find out who handled the call. It is a shame that happened.
Microsoft Security Essentials did not miss anything. There was nothing to miss. Whose idea was it to get Kaspersky? Kaspersky is okay, but if you want to use a paid anti-virus, rather than a free one. I would suggest NOD32 by Eset. You will need to remove MSSE before installing another one.
liz1954
2 Intern
•
161 Posts
0
February 13th, 2011 12:00
Bugbatter, Hi, thank you for your assistance, I can not remember the name of the operator. We used go to assist and I looked in my computer but there was no log of the action taken. I am sorry I wasted my money also. I decided on Kaspersky because that was the one he used to remove the supposed infection. I can pay for a antivirus service, I just want a good one. Is MS security essentials as good as NOD32 or which one is better? And I still have the recycle bin problem. I have deleted to file as suggested.
Bugbatter
4 Apprentice
•
20.5K Posts
0
February 13th, 2011 13:00
K27 was helping you before rudely intervened, so I will be brief in answering your questions. He can post if he has anything to add.
1. The Dell Tech used TDSSKiller which is a rootkit detection tool created to target a specific infection (that according to your log did not exist). It is different from Kaspersky Anti-virus which may incorporate TDSS scanning, but when choosing an anti-virus you need to look at the overall picture. NOD32 is better rated than Kaspersky AV. Microsoft Security Essentials is fine, and also has done well in independent tests. It updates automatically and when you do your monthly Windows Updates, Microsoft checks to be sure MSSE is running and staying updated. It also has the advantage of playing nicely with Microsoft's operating system and firewall. Microsoft actually has a write-up on one variant of TDSS and suggests using Microsoft Security Essentials.
2. If rebuilding your Recycle Bin did not work, it is not worth wasting time trying to troubleshoot that problem. You have run registry cleaners on there and have had a couple of anti-virus programs over the years. One did not have such a great reputation if I recall. All that has made changes to the system .
liz1954
2 Intern
•
161 Posts
0
February 13th, 2011 14:00
K27 and Bugbatter, Thanks, I will do a clean install. after I will install ms security and get rid of Kapersky.. Only one question should I install MSSE before I get all my updates or after? Best wishes for you both. liz
kevin27_b3d29f
2 Intern
•
1.5K Posts
0
February 13th, 2011 14:00
Hi,
Just to pipe in. I agree with Bugbatter on this, trouble shooting things like the Recycle bin after what you have already done are going to take a lot of time,, I think the best and fastest option that you have at the moment is to back up all your important data and then Reinstall Windows. Registry cleaners are far more trouble than they are worth and I feel it will be one thing after the other until a reinstall is carried out.
You can find info for reinstalling XP HERE DO NOT follow the instructions for option 1, it is option 2 or 3 that you are going to need to do.
Thanks.
kevin27_b3d29f
2 Intern
•
1.5K Posts
0
February 13th, 2011 16:00
Hi,
You are going to need to install an Anti-Virus program first. Then install all the Windows updates and then restore the data that you backed up.
Thanks.
Bugbatter
4 Apprentice
•
20.5K Posts
0
February 15th, 2011 06:00
Liz, I sent you a message. Click on your Inbox link near the top of this page, and send the information to the name I gave you. Do not post it on this forum. Thanks.
liz1954
2 Intern
•
161 Posts
0
February 15th, 2011 10:00
K27, I tried to do a complete reinstall but was not able to boot from cd, I did go into bios and change the boot sequence to cd first in line. So I just put cd in and at the welcome screen chose a complete reinstall, but was not given the option to format, I just chose the largest partition and it would be overwritten. While installing I had to choose to quit or skip the oembios.bin not being installed, so I skipped it. I had to choose option 4 of your choices as the pc restore was used once already 1 year ago, when I was given this machine. Approx. aroun Nov. I had to reinstall my os because I was using one of the tools on the Dell pc tune up that searched for duplicate files and found 17000, so I deleted them and lost windows. I called Dell and paid for an extended svc contract with 4 major incidents and it took all four to get my computer working again. So, now I have reinstalled it again. It took 13 hours to download 150 updates from windows update. I had to load several updates before I could install MSSE, so I was about 2 hours without protection. I now have loaded Malwarebytes Anti-Malwarebytes from cnet (free version) ran a scan 1.5 hours, no objects found. I ran and hour and a half scan from MS security essentials and they found one problem, action taken listed it as removed but then there was another line that told me to remove it immediatly. I looked for it in the hklm but could not find it so I assume it was removed. I have run and installed cccleaner (from piriform, free version) I have reinstalled Dell pc tune up and run that, they found lots of errors and I just clicked on repair them all. I do not know what they all were. I have secunia installed and my system is 100% with them, Except for Cyberlink which I put in the ignore list. I have WOT reinstalled. I have firefox browser installed, but I still use IE8 just because I am used to it. On timing Windows xp screen after Dell logl runs 20 seconds before welcome screen comes on, welcome screen runs 43 seconds. To connect to internet takes 8 seconds. Are all these good times? If they could be less fine, if not I am more or less ok with them. Do I need to worry about the oembios.bin file? Any questions you would like to ask me? Thanks, Liz.
kevin27_b3d29f
2 Intern
•
1.5K Posts
0
February 16th, 2011 05:00
Hi Liz,
The recovery partition can be used as many time as you like as long as access to the partition in the startup procedure has not been damaged.
Is everything running OK now?