Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Newbie Troubleshooting advice


  • Please log in to reply

#1
Lake Camelot

Lake Camelot

    Member

  • Member
  • PipPip
  • 47 posts
About three weeks ago my computer started freezing when I was in Google Chrome. The mouse would freeze in place, CTL ALT DEL wouldn't work. I had to power off the computer and restart it. Then it progressed to all programs and online or off. I have AVG and it showed no virus. It the started crashing within 15 seconds of windows login. I ran CHKDSK and it said it found 2 orphaned files and repaired them. I ran disc defragmenter just for the heck of it. Then no floppy disc error (40) started appearing during startup. I swapped out my RAM, What should I look at now? Drivers, hard drive failing (Why doesn't that show up?),overheating CPU (The fan is working fine from what I can see.

PS I have no floppy drive. Just a DVD Drive.

Running XP
512 RAM
Any suggestions would be appreciated.

By the way I downloaded DRIVERMAX to try to update drivers, but the computer crashes before I can finish anything. If I knew it was the hard drive I have no problem getting a new one, but from test I run it doesn't show that is it.
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Hello Lake Camellot.... Welcome to
GeeksToGo, :yes:
:) :unsure:

I'm sorry to hear about your issue. We will try to help you resolve this as soon as possible.
  • Please understand we are all volunteers and we are not here all the time.
  • Sometimes it may be a extended amount of time to get back to you. If it has been
    more then 3 days please shoot me a PM and I will try to get back to you quickly
    then.
  • Please do the following and supply the requested information as needed. If you
    don't understand my instructions please ask and I will try to explain them
    clearer for you.
  • Do not attempt any steps unless instructed or ask before to
    make sure they will not cause any further issues.



Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply







  • Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
  • Double-click VEW.exe
  • Under 'Select log to query', select (as appropriate):
    • Application
    • System
  • Under 'Select type to list', select (as appropriate):
    • Error
    • Information
    • Warning
Then use the 'Date of events' or 'Number of events' as follows:

Either:
  • Click the radio button for 'Number of events'
    Type 3 in the 1 to 20 box (or any number from 1 to 20)
    Then click the Run button.
    Notepad will open with the output log.

  • Click the radio button for 'Date of events'
    In the From: boxes type today's date (presuming the crash happened today) 17 05 2011
    In the To: boxes type today's date (presuming the crash happened today) 18 05 2011
    Then click the Run button.
    Notepad will open with the output log.
Please post the Output log in your next reply






Download Speedfan (The download link is to the right), and install it. Once it's installed, run the program and post here the information it shows.
The information I want you to post is the stuff that is circled in the example picture I have attached.
To make sure we are getting all the correct information it would help us if you were to attach a screenshot like the one below of your Speedfan results.

To do a screenshot please have click on your Print Screen on your keyboard.
  • It is normally the key above your number pad between the F12 key and the Scroll Lock key
  • Now go to Start and then to All Programs
  • Scroll to Accessories and then click on Paint
  • In the Empty White Area click and hold the CTRL key and then click the V
  • Go to the File option at the top and click on Save as
  • Save as file type JPEG and save it to your Desktop
  • Attach it to your next reply

Posted Image
  • 0

#3
Lake Camelot

Lake Camelot

    Member

  • Topic Starter
  • Member
  • PipPip
  • 47 posts
Not sure you wanted all this or not but thanks.


--------------------------------------------------------------------------------
Welcome to WhoCrashed HOME EDITION v 3.01
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.


To obtain technical support visit www.resplendence.com/support

To check if an update of this program is available, click here.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should ge the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.



--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: OWNER-Z9Y9FSH9P
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: AuthenticAMD AMD Sempron™ Processor 2800+ AMD586, level: 15
1 logical processors, active mask: 1
RAM: 736608256 total
VM: 2147352576, free: 2033381376



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Thu 5/19/2011 9:20:21 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051911-17.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x9DCC)
Bugcheck code: 0x1A (0x41284, 0x5A52001, 0xAAC, 0xFFFFFFFFC0883000)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software MEMORY_MANAGEMENT




On Thu 5/19/2011 8:23:55 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051911-16.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C6AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFE6484948, 0x0, 0xFFFFFFFF805036AE, 0x2)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/19/2011 7:31:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051911-15.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C6AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFF84887E0, 0x0, 0xFFFFFFFF805036AE, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/19/2011 6:33:22 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051911-14.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C6AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFC0C84C2C, 0x0, 0xFFFFFFFF805036AE, 0x2)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/19/2011 6:30:57 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051911-13.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C6AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFC0DA997C, 0x0, 0xFFFFFFFF805036AE, 0x2)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/19/2011 5:34:14 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051911-12.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C6AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFFC8834F8, 0x0, 0xFFFFFFFF805036AE, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/19/2011 5:29:16 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051911-11.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C6AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFC10CCD7C, 0x0, 0xFFFFFFFF805036AE, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/19/2011 5:23:39 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051911-10.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x9DCC)
Bugcheck code: 0x1A (0x41284, 0x719F001, 0xC107BAF, 0xFFFFFFFFC0883000)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software MEMORY_MANAGEMENT




On Thu 5/19/2011 5:19:47 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051911-09.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x4E (0x2, 0x67, 0x2BEEF, 0x1)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/19/2011 4:21:30 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051911-08.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C6AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFC1093838, 0x0, 0xFFFFFFFF805036AE, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/19/2011 4:01:04 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051911-07.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C6AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFC1AC297C, 0x0, 0xFFFFFFFF805036AE, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/19/2011 3:16:03 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051911-06.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C6AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFCFD7A388, 0x0, 0xFFFFFFFF805036AE, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/19/2011 2:27:10 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051911-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x41078)
Bugcheck code: 0x1000000A (0x7A7132E0, 0x2, 0x0, 0xFFFFFFFF80518078)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/19/2011 2:11:31 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051911-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C6AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFF97BE0C0, 0x0, 0xFFFFFFFF805036AE, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/19/2011 2:02:05 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051911-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C6AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFE48909D0, 0x0, 0xFFFFFFFF805036AE, 0x2)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

31 crash dumps have been found and analyzed. Only 15 are included in this report. 10 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

vtdisp.dll (VIA/S3G Graphics Driver, VIA/S3 Graphics Co, Ltd.)

aswsp.sys (avast! self protection module, AVAST Software)

aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
  • 0

#4
Lake Camelot

Lake Camelot

    Member

  • Topic Starter
  • Member
  • PipPip
  • 47 posts
Vino's Event Viewer v01c run on Windows XP in English
Report run at 19/05/2011 5:29:39 PM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 19/05/2011 1:37:19 PM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application teatimer.exe, version 1.6.6.32, faulting module teatimer.exe, version 1.6.6.32, fault address 0x00025e0c.

Log: 'Application' Date/Time: 19/05/2011 11:21:09 AM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application chrome.exe, version 0.0.0.0, faulting module chrome.dll, version 11.0.696.60, fault address 0x004d7e94.

Log: 'Application' Date/Time: 19/05/2011 11:00:53 AM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application toolbarsvr.exe, version 4.1.0.4230, faulting module unknown, version 0.0.0.0, fault address 0x3e8e3231.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 19/05/2011 5:12:51 PM
Type: information Category: 0
Event: 1042 Source: MsiInstaller
Ending a Windows Installer transaction: C:\DOCUME~1\Owner\LOCALS~1\Temp\dbg_x86_6.11.1.404.msi. Client Process Id: 2644.

Log: 'Application' Date/Time: 19/05/2011 5:12:51 PM
Type: information Category: 0
Event: 1033 Source: MsiInstaller
Windows Installer installed the product. Product Name: Debugging Tools for Windows (x86). Product Version: 6.11.1.404. Product Language: 1033. Installation success or error status: 0.

Log: 'Application' Date/Time: 19/05/2011 5:12:51 PM
Type: information Category: 0
Event: 11707 Source: MsiInstaller
Product: Debugging Tools for Windows (x86) -- Installation completed successfully.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 19/05/2011 4:21:41 PM
Type: warning Category: 0
Event: 0 Source: LeapFrog Connect Device Service
The event description cannot be found.

Log: 'Application' Date/Time: 19/05/2011 3:34:43 PM
Type: warning Category: 0
Event: 0 Source: LeapFrog Connect Device Service
The event description cannot be found.

Log: 'Application' Date/Time: 19/05/2011 2:32:47 PM
Type: warning Category: 0
Event: 0 Source: LeapFrog Connect Device Service
The event description cannot be found.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 19/05/2011 12:28:34 PM
Type: error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Workstation service which failed to start because of the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 19/05/2011 12:28:34 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Workstation service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 19/05/2011 12:28:34 PM
Type: error Category: 0
Event: 7011 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for a transaction response from the lanmanworkstation service.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 19/05/2011 5:22:51 PM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The Windows Installer service entered the stopped state.

Log: 'System' Date/Time: 19/05/2011 5:12:39 PM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The Windows Installer service entered the running state.

Log: 'System' Date/Time: 19/05/2011 5:12:39 PM
Type: information Category: 0
Event: 7035 Source: Service Control Manager
The Windows Installer service was successfully sent a start control.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  • 0

#5
Lake Camelot

Lake Camelot

    Member

  • Topic Starter
  • Member
  • PipPip
  • 47 posts
Speedfan.JPG Vino's Event Viewer v01c run on Windows XP in English
Report run at 19/05/2011 5:29:39 PM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 19/05/2011 1:37:19 PM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application teatimer.exe, version 1.6.6.32, faulting module teatimer.exe, version 1.6.6.32, fault address 0x00025e0c.

Log: 'Application' Date/Time: 19/05/2011 11:21:09 AM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application chrome.exe, version 0.0.0.0, faulting module chrome.dll, version 11.0.696.60, fault address 0x004d7e94.

Log: 'Application' Date/Time: 19/05/2011 11:00:53 AM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application toolbarsvr.exe, version 4.1.0.4230, faulting module unknown, version 0.0.0.0, fault address 0x3e8e3231.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 19/05/2011 5:12:51 PM
Type: information Category: 0
Event: 1042 Source: MsiInstaller
Ending a Windows Installer transaction: C:\DOCUME~1\Owner\LOCALS~1\Temp\dbg_x86_6.11.1.404.msi. Client Process Id: 2644.

Log: 'Application' Date/Time: 19/05/2011 5:12:51 PM
Type: information Category: 0
Event: 1033 Source: MsiInstaller
Windows Installer installed the product. Product Name: Debugging Tools for Windows (x86). Product Version: 6.11.1.404. Product Language: 1033. Installation success or error status: 0.

Log: 'Application' Date/Time: 19/05/2011 5:12:51 PM
Type: information Category: 0
Event: 11707 Source: MsiInstaller
Product: Debugging Tools for Windows (x86) -- Installation completed successfully.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 19/05/2011 4:21:41 PM
Type: warning Category: 0
Event: 0 Source: LeapFrog Connect Device Service
The event description cannot be found.

Log: 'Application' Date/Time: 19/05/2011 3:34:43 PM
Type: warning Category: 0
Event: 0 Source: LeapFrog Connect Device Service
The event description cannot be found.

Log: 'Application' Date/Time: 19/05/2011 2:32:47 PM
Type: warning Category: 0
Event: 0 Source: LeapFrog Connect Device Service
The event description cannot be found.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 19/05/2011 12:28:34 PM
Type: error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Workstation service which failed to start because of the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 19/05/2011 12:28:34 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Workstation service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 19/05/2011 12:28:34 PM
Type: error Category: 0
Event: 7011 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for a transaction response from the lanmanworkstation service.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 19/05/2011 5:22:51 PM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The Windows Installer service entered the stopped state.

Log: 'System' Date/Time: 19/05/2011 5:12:39 PM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The Windows Installer service entered the running state.

Log: 'System' Date/Time: 19/05/2011 5:12:39 PM
Type: information Category: 0
Event: 7035 Source: Service Control Manager
The Windows Installer service was successfully sent a start control.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  • 0

#6
Lake Camelot

Lake Camelot

    Member

  • Topic Starter
  • Member
  • PipPip
  • 47 posts
Speedfan.JPG Vino's Event Viewer v01c run on Windows XP in English
Report run at 19/05/2011 5:29:39 PM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 19/05/2011 1:37:19 PM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application teatimer.exe, version 1.6.6.32, faulting module teatimer.exe, version 1.6.6.32, fault address 0x00025e0c.

Log: 'Application' Date/Time: 19/05/2011 11:21:09 AM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application chrome.exe, version 0.0.0.0, faulting module chrome.dll, version 11.0.696.60, fault address 0x004d7e94.

Log: 'Application' Date/Time: 19/05/2011 11:00:53 AM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application toolbarsvr.exe, version 4.1.0.4230, faulting module unknown, version 0.0.0.0, fault address 0x3e8e3231.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 19/05/2011 5:12:51 PM
Type: information Category: 0
Event: 1042 Source: MsiInstaller
Ending a Windows Installer transaction: C:\DOCUME~1\Owner\LOCALS~1\Temp\dbg_x86_6.11.1.404.msi. Client Process Id: 2644.

Log: 'Application' Date/Time: 19/05/2011 5:12:51 PM
Type: information Category: 0
Event: 1033 Source: MsiInstaller
Windows Installer installed the product. Product Name: Debugging Tools for Windows (x86). Product Version: 6.11.1.404. Product Language: 1033. Installation success or error status: 0.

Log: 'Application' Date/Time: 19/05/2011 5:12:51 PM
Type: information Category: 0
Event: 11707 Source: MsiInstaller
Product: Debugging Tools for Windows (x86) -- Installation completed successfully.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 19/05/2011 4:21:41 PM
Type: warning Category: 0
Event: 0 Source: LeapFrog Connect Device Service
The event description cannot be found.

Log: 'Application' Date/Time: 19/05/2011 3:34:43 PM
Type: warning Category: 0
Event: 0 Source: LeapFrog Connect Device Service
The event description cannot be found.

Log: 'Application' Date/Time: 19/05/2011 2:32:47 PM
Type: warning Category: 0
Event: 0 Source: LeapFrog Connect Device Service
The event description cannot be found.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 19/05/2011 12:28:34 PM
Type: error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Workstation service which failed to start because of the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 19/05/2011 12:28:34 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Workstation service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 19/05/2011 12:28:34 PM
Type: error Category: 0
Event: 7011 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for a transaction response from the lanmanworkstation service.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 19/05/2011 5:22:51 PM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The Windows Installer service entered the stopped state.

Log: 'System' Date/Time: 19/05/2011 5:12:39 PM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The Windows Installer service entered the running state.

Log: 'System' Date/Time: 19/05/2011 5:12:39 PM
Type: information Category: 0
Event: 7035 Source: Service Control Manager
The Windows Installer service was successfully sent a start control.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  • 0

#7
Lake Camelot

Lake Camelot

    Member

  • Topic Starter
  • Member
  • PipPip
  • 47 posts
Gotta Love having my kids screen saver on here. Anyway there it is thanks. I didn't crashh the whole time I did this.
  • 0

#8
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

vtdisp.dll (VIA/S3G Graphics Driver, VIA/S3 Graphics Co, Ltd.)

aswsp.sys (avast! self protection module, AVAST Software)

aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software)

3 main culprits.
Have you updated the Avast engine lately?
Video seems to have a issue also. Possibly a driver update on it also.



Please Run the PCPitstop.com OverDrive Full Tests

Here's how:

You must use your Internet Explorer for this procedure. (doesn't work so well in Firefox or others). If your machine is running Vista or Windows 7, you must Select IE to “Run as Administrator”. After completing PCPitstop OverDrive you can close your IE browser and re-open it Normally so that you are no longer running as administrator.

Go to: http://www.pcpitstop.com
Click on "Free Computer Check-up" listed below PC Pitstop OverDrive
In the User Login - Click on "Sign up FREE!"
You'll need to submit a valid email address and create your own password, then click - Create Account(button)

Now enter your email address and password to Log in, Select - Scan this system Now!(button)
You will then be asked to download an ActiveX component and allow it to install.
It is safe and does not compromise your privacy.
Follow the on-screen prompts to install the ActiveX and to allow the Full Tests to be run on your machine.

The Full Tests take about 2 1/2 - 3 minutes on most machines.
When complete, a Results - Summary - Recommended Fixes will be displayed.

Please post the URL internet address, from your Results, back here into this Topic Thread so that we can review the configuration and present performance levels of your machine.

Note: During the graphics 2D and graphics 3D testing, your screen will display some rapidly moving objects.
If you are sensitive to visual flashing, it may cause dizziness. Therefore, look away from the screen during that portion of the testing.

After reviewing the results we will be more informed and may be able to provide better recommendations for you to work towards improving your machine's performance.

While PCPitstop does offer a variety of Paid Products, the PCPitstop OverDrive testing is FREE. Please ignore the references to Paid Products. We prefer to provide manual solution instructions that you can apply directly to your machine.

Best Regards
  • 0

#9
Lake Camelot

Lake Camelot

    Member

  • Topic Starter
  • Member
  • PipPip
  • 47 posts
http://www.pcpitstop...?conid=24372377
  • 0

#10
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Do you know how to manually update avast?
  • 0

Advertisements


#11
Lake Camelot

Lake Camelot

    Member

  • Topic Starter
  • Member
  • PipPip
  • 47 posts
I am not sure I know if manually is different than just checking for new updates? If I go under update It says I have current definitions and the most recent program. Should I uninstall under add/remove programs and re-install it?
  • 0

#12
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Nope you are good then.
Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Reboot after your done running chkdsk /r...
then Go to Start...Run and type: eventvwr.msc press Enter
When Event Viewer opens, click on Applications... then scroll down to [b]Winlogon]/b] and double-click on it. This is the log created after running Checkdisk...copy and paste the log back here


We will advise after studying the log.
  • 0

#13
Lake Camelot

Lake Camelot

    Member

  • Topic Starter
  • Member
  • PipPip
  • 47 posts
My wife is runnung the CHKDSK /r
and will post the log.
I am not sure though, are you saying also run CHKDSK /f or was that a typo for r ?

Edited by Lake Camelot, 20 May 2011 - 10:25 AM.

  • 0

#14
Lake Camelot

Lake Camelot

    Member

  • Topic Starter
  • Member
  • PipPip
  • 47 posts
Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 5/20/2011
Time: 11:50:32 AM
User: N/A
Computer: OWNER-Z9Y9FSH9P
Description:
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up 1 unused index entries from index $SII of file 0x9.
Cleaning up 1 unused index entries from index $SDH of file 0x9.
Cleaning up 1 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

156280288 KB total disk space.
55963644 KB in 175509 files.
77712 KB in 10387 indexes.
0 KB in bad sectors.
539412 KB in use by the system.
65536 KB occupied by the log file.
99699520 KB available on disk.

4096 bytes in each allocation unit.
39070072 total allocation units on disk.
24924880 allocation units available on disk.

Internal Info:
70 2e 03 00 33 d6 02 00 b1 a2 04 00 00 00 00 00 p...3...........
9f 17 00 00 07 00 00 00 c5 05 00 00 00 00 00 00 ................
9e cf c3 05 00 00 00 00 ce eb 18 5f 00 00 00 00 ..........._....
d8 da d4 22 00 00 00 00 0c 18 a1 81 04 00 00 00 ..."............
b4 33 3f 39 04 00 00 00 98 60 88 52 09 00 00 00 .3?9.....`.R....
99 9e 36 00 00 00 00 00 98 38 07 00 95 ad 02 00 ..6......8......
00 00 00 00 00 f0 bf 57 0d 00 00 00 93 28 00 00 .......W.....(..

Windows has finished checking your disk.
Please wait while your computer restarts.


For more information, see Help and Support Center at http://go.microsoft....ink/events.asp.
  • 0

#15
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Rerun it to make sure it got everything..
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP