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

Same PC, 1 WinXP user account slower than the other


  • Please log in to reply
2 replies to this topic

#1 Miotkem

Miotkem

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:11:50 AM

Posted 11 September 2011 - 06:06 PM

My wife and I share the same PC, it is running Win XP Pro 32-bit w/ SP3.

We have separate user logins.

For whatever reason, her's is significantly slower than mine. Running programs, surfing the web, even the desktop image reloading.

She has a family photo as the desktop wallpaper, and when I close a window while logged in with her, I can actually watch the desktop image loading top to bottom, it takes roughly 0.5 seconds. I assumed it was the size of the photo or the number of icons she has... but when I use the same exact photo as my desktop and have the same # of desktop icons, my desktop loads almost instantly when I close or minimize a window.

So far while logged in has her, I have updated and scanned with the following programs:
AVG Anti-virus free edition 2011
Ad-Aware
Spybot S&D 1.6.2
Malware Bytes' Anti-Malware
CCleaner (Including a registry scan)

Finally, I have run the Windows Disk Defragmenter.

It's still slow, so I'm turning to your advice. Admittedly, I did not do any of the above scans in Safe Mode yet. That will be my next step, but I thought I would ask here first, in case I'm barking up the wrong tree altogether with all of these scans.

Thank you.

BC AdBot (Login to Remove)

 


#2 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:07:50 PM

Posted 15 September 2011 - 12:53 PM

Can you post the log for Malwarebytes and Spybot?

Also with regards to CCleaner:
Bleeping Computer DOES NOT recommend the use of registry cleaners/optimizers for several reasons:

Registry cleaners are extremely powerful applications that can damage the registry by using aggressive cleaning routines and cause your computer to become unbootable.

The Windows registry is a central repository (database) for storing configuration data, user settings and machine-dependent settings, and options for the operating system. It contains information and settings for all hardware, software, users, and preferences. Whenever a user makes changes to settings, file associations, system policies, or installed software, the changes are reflected and stored in this repository. The registry is a crucial component because it is where Windows "remembers" all this information, how it works together, how Windows boots the system and what files it uses when it does. The registry is also a vulnerable subsystem, in that relatively small changes done incorrectly can render the system inoperable. For a more detailed explanation, read Understanding The Registry.

Not all registry cleaners are created equal. There are a number of them available but they do not all work entirely the same way. Each vendor uses different criteria as to what constitutes a "bad entry". One cleaner may find entries on your system that will not cause problems when removed, another may not find the same entries, and still another may want to remove entries required for a program to work.

Not all registry cleaners create a backup of the registry before making changes. If the changes prevent the system from booting up, then there is no backup available to restore it in order to regain functionality. A backup of the registry is essential BEFORE making any changes to the registry.

Improperly removing registry entries can hamper malware disinfection and make the removal process more difficult if your computer becomes infected. For example, removing malware related registry entries before the infection is properly identified can contribute to system instability and even make the malware undetectable to removal tools.

The usefulness of cleaning the registry is highly overrated and can be dangerous. In most cases, using a cleaner to remove obsolete, invalid, and erroneous entries does not affect system performance but it can result in "unpredictable results".

Unless you have a particular problem that requires a registry edit to correct it, I would suggest you leave the registry alone. Using registry cleaning tools unnecessarily or incorrectly could lead to disastrous effects on your operating system such as preventing it from ever starting again. For routine use, the benefits to your computer are negligible while the potential risks are great.

#3 Miotkem

Miotkem
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:11:50 AM

Posted 15 September 2011 - 03:32 PM

Thank you for the registry cleaner information, I'll refrain from now on.

I know I'm slow anyway, but I was unable to locate an option to attach files, so I'm pasting the information from the log files.

MBAM Log, filename = "C:\Documents and Settings\<Wife's account>\Application Data\Malwarebytes\Malwarebytes' Anti-Malware\Logs\mbam-log-2011-09-11 (18-11-10).txt":

Malwarebytes' Anti-Malware 1.51.1.1800
www.malwarebytes.org

Database version: 7697

Windows 5.1.2600 Service Pack 3 (Safe Mode)
Internet Explorer 8.0.6001.18702

9/11/2011 6:11:10 PM
mbam-log-2011-09-11 (18-11-10).txt

Scan type: Full scan (C:\|)
Objects scanned: 251038
Time elapsed: 23 minute(s), 10 second(s)

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

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
(No malicious items detected)


Spybot S&D Checks Log, filename = "C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy\Logs\Checks.110915-1311.log":

15.09.2011 13:11:26 - ##### check started #####
15.09.2011 13:11:26 - ### Version: 1.6.2
15.09.2011 13:11:26 - ### Date: 9/15/2011 1:11:26 PM
15.09.2011 13:11:28 - ##### checking bots #####


Spybot S&D Checks Log, filename = "C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy\Logs\Checks.110915-1321.log":

--- Report generated: 2011-09-15 13:21 ---


--- Spybot - Search & Destroy version: 1.6.2 (build: 20090126) ---

2009-01-26 blindman.exe (1.0.0.8)
2009-01-26 SDFiles.exe (1.6.1.7)
2009-01-26 SDMain.exe (1.0.0.6)
2009-01-26 SDShred.exe (1.0.2.5)
2009-01-26 SDUpdate.exe (1.6.0.12)
2009-01-26 SpybotSD.exe (1.6.2.46)
2009-03-05 TeaTimer.exe (1.6.6.32)
2011-09-03 unins000.exe (51.49.0.0)
2009-01-26 Update.exe (1.6.0.7)
2009-11-04 advcheck.dll (1.6.5.20)
2007-04-02 aports.dll (2.1.0.0)
2008-06-14 DelZip179.dll (1.79.11.1)
2009-01-26 SDHelper.dll (1.6.2.14)
2008-06-19 sqlite3.dll
2009-01-26 Tools.dll (2.1.6.10)
2009-01-16 UninsSrv.dll (1.0.0.0)
2011-03-18 Includes\Adware.sbi (*)
2011-08-29 Includes\AdwareC.sbi (*)
2010-08-13 Includes\Cookies.sbi (*)
2010-12-14 Includes\Dialer.sbi (*)
2011-03-08 Includes\DialerC.sbi (*)
2011-02-24 Includes\HeavyDuty.sbi (*)
2011-03-29 Includes\Hijackers.sbi (*)
2011-05-16 Includes\HijackersC.sbi (*)
2010-09-15 Includes\iPhone.sbi (*)
2010-12-14 Includes\Keyloggers.sbi (*)
2011-03-08 Includes\KeyloggersC.sbi (*)
2004-11-29 Includes\LSP.sbi (*)
2011-08-31 Includes\Malware.sbi (*)
2011-09-06 Includes\MalwareC.sbi (*)
2011-02-24 Includes\PUPS.sbi (*)
2011-05-24 Includes\PUPSC.sbi (*)
2010-01-25 Includes\Revision.sbi (*)
2011-02-24 Includes\Security.sbi (*)
2011-05-03 Includes\SecurityC.sbi (*)
2008-06-03 Includes\Spybots.sbi (*)
2008-06-03 Includes\SpybotsC.sbi (*)
2011-02-24 Includes\Spyware.sbi (*)
2011-06-14 Includes\SpywareC.sbi (*)
2010-03-08 Includes\Tracks.uti
2011-06-20 Includes\Trojans.sbi (*)
2011-09-06 Includes\TrojansC-02.sbi (*)
2011-08-09 Includes\TrojansC-03.sbi (*)
2011-09-05 Includes\TrojansC-04.sbi (*)
2011-09-07 Includes\TrojansC-05.sbi (*)
2011-08-23 Includes\TrojansC.sbi (*)
2008-03-04 Plugins\Chai.dll
2008-03-05 Plugins\Fennel.dll
2008-02-26 Plugins\Mate.dll
2007-12-24 Plugins\TCPIPAddress.dll


Spybot S&D Resident Log, filename = "C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy\Logs\Resident.log":

9/11/2011 6:24:49 PM Allowed (based on user decision) value "NvCplDaemon" (new data: "RUNDLL32.EXE C:\WINDOWS\system32\NvCpl.dll,NvStartup") added in System Startup global entry!
9/15/2011 8:49:00 AM Allowed (based on user decision) value "BootExecute" (new data: "autocheck autochk *
lsdelete
C:\PROGRA~1\AVG\AVG10\avgchsvx.exe /sync
C:\PROGRA~1\AVG\AVG10\avgrsx.exe /sync /restart
") changed in Session manager!


Edited by Miotkem, 15 September 2011 - 11:10 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users