Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Slow Vista Laptop

Started by Karawr , Sep 16 2009 08:26 PM

  • Please log in to reply

#1
Karawr
Posted 16 September 2009 - 08:26 PM

Karawr

    New Member

  • Member
  • Pip
  • 9 posts
Dell Inspiron 1420
Intel® Core™2 Duo CPU T5450 @ 1.66GHz 1.67 GHz
Memory: 2GB
32-bit operating system
Windows Vista Home Premium (service pack 2)

tl;dr Problems:
- Freezing
- Running slow
- Wireless signal goes out for one second (enough to cut out my online games or MSN)

For the past month it has been running really slowly and freezing. I've been trying to fix it for awhile with no luck. At one point, I disabled most of my visual effects and that seemed to help for a couple of days. Now, the freezing/slowness is back. I'm also having the 'stuttering' another user posted: I'll be watching a movie and it keeps stuttering, or I call it lagging. I have done scans using CCleaner, Malwarebytes, Hijackthis and Advanced SystemCare. I removed a couple of things hijackthis.de told me to, but otherwise CCleaner and Malwarebytes didn't find anything. I've also done these scans in safemode.

Edited by Karawr, 17 September 2009 - 07:14 AM.

  • 0

Advertisements

#2
Broni
Posted 16 September 2009 - 08:46 PM

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
You should make separate post about 2nd laptop.
So, let's focus on the first one.

How big is a hard drive/free space?


Download Autoruns for Windows: http://technet.micro...s/bb963902.aspx
No installation required.
Simply unzip Autoruns.zip file, and double click on autoruns.exe file to run the program.
Go File>Export As, and save AutoRuns.txt file to know location.
Attach the file to your next reply.


Please download VEW and save it to your Desktop: http://images.malwar...om/vino/VEW.exe

Double-click VEW.exe then under Select log to query, select:
Application
System

Under Select type to list, select:
Critical (Vista only)
Error

Click the radio button for Number of events
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.

In Notepad, click Edit > Select all then Edit > Copy
Reply to this post, click in the reply window and press Ctrl+V on your keyboard to paste the log.


Download Process Explorer: http://technet.micro...s/bb896653.aspx
Unzip ProcessExplorer.zip, and double click on procexp.exe to run the program.
Click on View > Select Colunms.
In addition to already pre-selected options, make sure, the Command Line is selected, and press OK.
Go File>Save As, and save the report as Procexp.txt.
Attach the file to your next reply.
  • 0

#3
Karawr
Posted 17 September 2009 - 07:13 AM

Karawr

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
54.2GB free of 220GB

Vino's Event Viewer v01c run on Windows Vista in English
Report run at 17/09/2009 9:06:25 AM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 16/09/2009 9:39:02 PM
Type: Error Category: 3
Event: 3024 Source: Microsoft-Windows-Search
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

Context: Application, SystemIndex Catalog


Log: 'Application' Date/Time: 16/09/2009 11:49:57 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application WeatherEye.exe, version 2.6.1.3, time stamp 0x2a425e19, faulting module kernel32.dll, version 6.0.6002.18005, time stamp 0x49e037dd, exception code 0xc0000005, fault offset 0x000bf9cd, process id 0x1119c, application start time 0x01ca36c3cfcd2090.

Log: 'Application' Date/Time: 16/09/2009 11:49:37 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application WeatherEye.exe, version 2.6.1.3, time stamp 0x2a425e19, faulting module kernel32.dll, version 6.0.6002.18005, time stamp 0x49e037dd, exception code 0xc0000005, fault offset 0x000bf9cd, process id 0x11330, application start time 0x01ca36c3c23cd650.

Log: 'Application' Date/Time: 16/09/2009 11:10:10 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application SoftwareUpdate.exe, version 2.1.1.116, time stamp 0x488a4f1f, faulting module SoftwareUpdate.exe, version 2.1.1.116, time stamp 0x488a4f1f, exception code 0xc0000005, fault offset 0x00004f9c, process id 0x10148, application start time 0x01ca36be36d49cb0.

Log: 'Application' Date/Time: 15/09/2009 12:36:41 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application svchost.exe_wudfsvc, version 6.0.6001.18000, time stamp 0x47918b89, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e03821, exception code 0xc0000005, fault offset 0x0003e13d, process id 0x488, application start time 0x01ca359c9625d87a.

Log: 'Application' Date/Time: 13/09/2009 8:53:15 PM
Type: Error Category: 0
Event: 0 Source: is360srv.exe
The event description cannot be found.

Log: 'Application' Date/Time: 11/09/2009 3:32:18 PM
Type: Error Category: 0
Event: 8194 Source: VSS
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {40d3d1ed-1e15-4890-af46-329e7ee8b29c}

Log: 'Application' Date/Time: 11/09/2009 11:51:12 AM
Type: Error Category: 16
Event: 4609 Source: Microsoft-Windows-EventSystem
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043c from line 45 of d:\longhorn\com\complus\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.

Log: 'Application' Date/Time: 03/09/2009 2:49:01 AM
Type: Error Category: 0
Event: 0 Source: Lavasoft Ad-Aware Service
The event description cannot be found.

Log: 'Application' Date/Time: 02/09/2009 2:32:14 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application RebirthRO Patcher.exe, version 1.0.0.1, time stamp 0x492cbcd6, faulting module composer.dll, version 0.0.0.0, time stamp 0x49e52336, exception code 0xc0000417, fault offset 0x00005a57, process id 0x1144, application start time 0x01ca2b7571c0a8e0.

Log: 'Application' Date/Time: 31/08/2009 6:16:23 PM
Type: Error Category: 16
Event: 4609 Source: Microsoft-Windows-EventSystem
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043c from line 45 of d:\longhorn\com\complus\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.

Log: 'Application' Date/Time: 26/08/2009 11:39:26 PM
Type: Error Category: 3
Event: 3013 Source: Microsoft-Windows-Search
The entry <C:\USERS\KARA\MUSIC\ITUNES\ITUNES LIBRARY.ITL> in the hash map cannot be updated.

Context: Application, SystemIndex Catalog

Details:
A device attached to the system is not functioning. (0x8007001f)


Log: 'Application' Date/Time: 25/08/2009 12:16:15 AM
Type: Error Category: 3
Event: 3013 Source: Microsoft-Windows-Search
The entry <MAPI://{S-1-5-21-1153907619-3369133187-4063755601-1000}/PERSONAL FOLDERS($DEC3FF7A)/X/INBOX/????????????????????????> in the hash map cannot be updated.

Context: Application, SystemIndex Catalog

Details:
A device attached to the system is not functioning. (0x8007001f)


Log: 'Application' Date/Time: 24/08/2009 4:04:22 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program Photoshop.exe version 11.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Problem Reports and Solutions control panel. Process ID: 5b4 Start Time: 01ca246fcfe0e280 Termination Time: 16

Log: 'Application' Date/Time: 21/08/2009 6:56:00 PM
Type: Error Category: 3
Event: 3013 Source: Microsoft-Windows-Search
The entry <MAPI://{S-1-5-21-1153907619-3369133187-4063755601-1000}/PERSONAL FOLDERS($DEC3FF7A)/X/OUTBOX/????????????????????????> in the hash map cannot be updated.

Context: Application, SystemIndex Catalog

Details:
A device attached to the system is not functioning. (0x8007001f)


Log: 'Application' Date/Time: 21/08/2009 6:56:00 PM
Type: Error Category: 3
Event: 3013 Source: Microsoft-Windows-Search
The entry <MAPI://{S-1-5-21-1153907619-3369133187-4063755601-1000}/PERSONAL FOLDERS($DEC3FF7A)/X/OUTBOX/????????????????????????> in the hash map cannot be updated.

Context: Application, SystemIndex Catalog

Details:
A device attached to the system is not functioning. (0x8007001f)


Log: 'Application' Date/Time: 21/08/2009 6:45:50 PM
Type: Error Category: 3
Event: 3013 Source: Microsoft-Windows-Search
The entry <C:\USERS\KARA\APPDATA\ROAMING\MICROSOFT\WINDOWS\START MENU\PROGRAMS\PAINTTOOL SAI ENGLISH PACK\UNINSTALL.LNK> in the hash map cannot be updated.

Context: Application, SystemIndex Catalog

Details:
A device attached to the system is not functioning. (0x8007001f)


Log: 'Application' Date/Time: 21/08/2009 6:45:50 PM
Type: Error Category: 3
Event: 3013 Source: Microsoft-Windows-Search
The entry <C:\USERS\KARA\APPDATA\ROAMING\MICROSOFT\WINDOWS\START MENU\PROGRAMS\PAINTTOOL SAI ENGLISH PACK\PAINTTOOL SAI.LNK> in the hash map cannot be updated.

Context: Application, SystemIndex Catalog

Details:
A device attached to the system is not functioning. (0x8007001f)


Log: 'Application' Date/Time: 19/08/2009 5:06:53 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application msnmsgr.exe, version 14.0.8064.206, time stamp 0x498cf586, faulting module UXCore.dll, version 14.0.8064.206, time stamp 0x498cdee0, exception code 0xc0000005, fault offset 0x00069bda, process id 0x18ac, application start time 0x01ca20e846c7c840.

Log: 'Application' Date/Time: 13/08/2009 6:14:17 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application OUTLOOK.EXE, version 11.0.8217.0, time stamp 0x480f95d9, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e03821, exception code 0xc0000005, fault offset 0x0003e13d, process id 0x14c4, application start time 0x01ca1c3576558528.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 16/09/2009 1:31:55 PM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 15/09/2009 2:11:01 PM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 14/09/2009 12:08:55 AM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 11/09/2009 6:53:58 PM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 11/09/2009 11:50:27 AM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 09/09/2009 8:20:07 PM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 09/09/2009 1:21:21 PM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 08/09/2009 1:48:40 PM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 08/09/2009 1:34:10 PM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 08/09/2009 12:38:36 AM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 03/09/2009 2:28:26 AM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 31/08/2009 6:15:36 PM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 31/08/2009 4:08:06 PM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 31/08/2009 3:54:49 AM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 21/08/2009 4:28:37 AM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 05/08/2009 10:50:07 PM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 01/08/2009 7:45:49 AM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 01/08/2009 12:01:58 AM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 24/07/2009 6:23:51 PM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

Log: 'System' Date/Time: 22/07/2009 10:57:02 AM
Type: Critical Category: 0
Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 17/09/2009 12:59:35 PM
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.

Log: 'System' Date/Time: 17/09/2009 11:56:52 AM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 17/09/2009 11:56:44 AM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 17/09/2009 2:32:51 AM
Type: Error Category: 0
Event: 7043 Source: Service Control Manager
The Windows Update service did not shut down properly after receiving a preshutdown control.

Log: 'System' Date/Time: 17/09/2009 2:31:35 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {6295DF2D-35EE-11D1-8707-00C04FD93327} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 16/09/2009 4:56:45 PM
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Wlansvc service.

Log: 'System' Date/Time: 16/09/2009 1:31:55 PM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 16/09/2009 1:31:47 PM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 16/09/2009 1:32:01 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 9:31:10 AM on 16/09/2009 was unexpected.

Log: 'System' Date/Time: 16/09/2009 12:30:42 PM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 16/09/2009 12:30:34 PM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 15/09/2009 4:23:22 PM
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.

Log: 'System' Date/Time: 15/09/2009 2:11:09 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 10:10:10 AM on 15/09/2009 was unexpected.

Log: 'System' Date/Time: 15/09/2009 2:11:02 PM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 15/09/2009 2:10:54 PM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 15/09/2009 12:38:17 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Windows Driver Foundation - User-mode Driver Framework service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

Log: 'System' Date/Time: 15/09/2009 12:38:17 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The WLAN AutoConfig service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

Log: 'System' Date/Time: 15/09/2009 12:38:17 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Desktop Window Manager Session Manager service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

Log: 'System' Date/Time: 15/09/2009 12:38:17 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Tablet PC Input Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

Log: 'System' Date/Time: 15/09/2009 12:38:17 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Windows Audio Endpoint Builder service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

Attached Files


  • 0

#4
Broni
Posted 17 September 2009 - 03:31 PM

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Start wit disabling all Windows power saving features. There is a lot of errors coming from that department.
  • 0

#5
Karawr
Posted 17 September 2009 - 03:33 PM

Karawr

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
I'm guessing I do that through power properties?

Hm, I'm in power options but I really don't know where to go from there, sorry...

Edit: I took a 'guide' from here but I am already on high performance so I don't know what to change...

Edited by Karawr, 17 September 2009 - 03:57 PM.

  • 0

#6
Broni
Posted 17 September 2009 - 04:55 PM

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Uner "High performance" click on "Change plan settings".
There is number of options there. Make sure, nothing like "sleep", "hibernate", etc. is enabled.
  • 0

#7
Karawr
Posted 17 September 2009 - 06:17 PM

Karawr

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Checked it and there is nothing like that enabled. :)
  • 0

#8
Broni
Posted 17 September 2009 - 06:36 PM

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Well, you have numerous errors, which say:

Event: 41 Source: Microsoft-Windows-Kernel-Power
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.


  • 0

#9
Karawr
Posted 17 September 2009 - 06:37 PM

Karawr

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
I put my computer to sleep a lot but it doesn't do it automatically...
  • 0

#10
Broni
Posted 17 September 2009 - 07:09 PM

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
I suggest that you start a new topic in the Malware Removal and Spyware Removal area.

Before you start a new topic click on this link --> Malware and Spyware Cleaning Guide, Please read before starting a new topic. This will give you a few preparations to make, as well as instruction for posting your OTListIt2 log.

If you are still having problems after being given a clean bill of health from the malware expert, then please return to THIS thread and we will pursue other options to help you solve your current problem(s).
  • 0

Advertisements

#11
Karawr
Posted 18 September 2009 - 08:29 PM

Karawr

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
I've done scans and nothing has been found; I don't see how this can be a virus problem.
Either way, I have posted a thread... thanks for the help so far. :)
  • 0

#12
Broni
Posted 18 September 2009 - 09:06 PM

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
You never answered:

How big is a hard drive/free space?


Download Autoruns for Windows: http://technet.micro...s/bb963902.aspx
No installation required.
Simply unzip Autoruns.zip file, and double click on autoruns.exe file to run the program.
Go File>Export As, and save AutoRuns.txt file to know location.
Attach the file to your next reply.
  • 0

#13
Karawr
Posted 19 September 2009 - 12:00 PM

Karawr

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Actually, I did. It's in the post with the log; I bolded it so that you would see it.
Once again: 54.2GB free of 220GB

I also did the autoruns attachment, but I guess I'll do it again...

Attached Files


  • 0

#14
Broni
Posted 19 September 2009 - 03:58 PM

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
I don't see much here, either.

Next step...

Go Start>Run ("Start Search" in Vista), type in:
sfc /scannow
Click OK (hold CTRL, and SHIFT, hit Enter in Vista).
Have Windows CD/DVD handy (with Vista, most likely, you won't need it).
If System File Checker (sfc) will find any errors, it may ask you for the CD/DVD (rarely in Vista case).
If sfc won't find any errors in Windows XP, it'll simply quit, without any message.
In Vista you will receive the following message: "Windows resource protection did not find any integrity violations".
  • 0

#15
Karawr
Posted 19 September 2009 - 09:42 PM

Karawr

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
It simply closed; no errors were found.
  • 0
Back to Windows Vista and Windows 7 · Next Unread Topic →




Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

  1. Geeks to Go Community
  2. → Retired Forums
  3. → Windows Vista and Windows 7

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP