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

Computer running slow, freezing and rebooting...


  • Please log in to reply

#1
Solar energy

Solar energy

    Member

  • Member
  • PipPip
  • 25 posts
Hi,
appreciate some help with slow running computer. It also freezes (3 or 4 time per week) and reboots itself from time to time.

Problems appear worse when more than one user logged in (usually only 2). Reboot seems to happen when a second user logs on. 'Serious error' messages when system comes back up.

Freezing seems to be random.

Have had problems with a virus or two recently, but these were resolved elsewhere on this forum.

I am in the UK.
System running Windows XP home edition.

I suspect it may be something to do with AVG security.

What else do you need to know?

Cheers

Graham
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Hello welcome to GeeksToGo, We will be happy to help you.

We will need some more information

If this is a name brand system:
Make
Model
Operating System
Age of the computer
Memory Total
Hard Drive Size, How much free space



If this is custom then We will need the following:

The CPU brand and model
The Motherboard brand and model
Ram amount and speed
Cd\Dvd rom interface IDE/
Hard Drive size and free space
Any cards in PCI slots

In Addition please supply:

Any software installed\updated and driver updates done just before problem started.
Any hardware installed\updated prior to problem starting.

All this will help in determining a course of action to best correct the problem you are experiencing.
  • 0

#3
Solar energy

Solar energy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 25 posts
I thought you would ask that. Lets see if I can find the answers:

Make (Brand - Tiny)
Model ?
Operating System Windows XP Home version 2002 SP3
Age of the computer 6 years
Memory Total?
Hard Drive Size, How much free space Capacity (76) 70.9 Gb available 28GB used 42.8gb

Processor: AMD Sempron 2400+ 1.67GHz 512 MB ram

I couldn't point to any 'recently installed' software that might be causing the problem, other than AVG (installed a year ago). Problem has been getting worse over the last month.

Today I powered up and logged in. AVG scan started running automatically and a few seconds sytem logged me out and went into reboot mode (I managed to stop it powering down, by logging in again B4 it shut down). It then logged a 'serious error' before I could use it.

Cheers
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Edit: Reason for edit. Double Post

Edited by rshaffer61, 27 April 2009 - 07:27 AM.

  • 0

#5
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
First let's see if we can see what the error you got was. Reboot the system and at the second black post screen tap F8.
You will get a text filled screen with boot options
Scroll down using keyboard down arrow to the line that says
Automatic Restart On Error
Highlight it and click the enter key
Then the system should reboot on its own.
This will result in whenever you get whats called a BSOD (Blue Screen Of Death) the system will stop and let you write down the error message it gives. Write down everything it says and paste put it in your next reply.

If you can get into windows then follow these instructions step by step:

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...you have to scroll down to see it
Copy and paste it into your next reply...


Please follow the steps below to enter the Event Viewer program in XP. This will give me more information into what is causing your issue.

Go to
Start and then click on Run and 2: Type in eventvwr.msc
Press Enter
On left side click on Applications On right side look for any RED X about the time of a incident
On left side click on System. On right side look for any Red X about the same time of a incident
Also look for any yellow exclamation mark at the same time in either of the above
If you find any double click on one at a time and take a screenshot.
Include as a attachment in your next reply



Please follow the steps below to enter the Event Viewer program in Vista. This will give me more information into what is causing your issue. You can get to Event viewer two ways and I will post both for you.

Method One

• Go to
• Start
• In the Search box type in Event Viewer in the search box and press Enter
• From this point you can follow from step four from the below method as they will be the same.

Method Two

• Go to Start
• Right click on the Computer Icon and select Manage
• Navigate to the Event Viewer, You will be prompted to accept the action you are going to perform. Click continue
• On the left window pane click on Local and then expand the Windows entry. This will allow you to see every error for the past 24 hours as well as the last 7 days in the right window pane.
• Look for the ones that correspond to the times that your issue occurred.
• If any are found please double click and expand the error. This will open and give you more information on the error.
• Please include that in your next reply.

If your attachment is to big to attach then go to Mediafire . Register and upload your file. Then reply with the link located to the right of your now uploaded file on Mediafire

Edited by rshaffer61, 13 June 2009 - 01:19 PM.

  • 0

#6
Solar energy

Solar energy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 25 posts
Whocrashed results: a bit repititive, but consistent and perhaps points to something happening around 4th October (1st ? occurence)

Looking at event viewer next. I think the Auto restart was already set - when I got the 'serious error' message I have kept the info (couple of lines of code). Do you want this?

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


Too many crashes have been detected. Only the latest 40 crashes will be displayed.

On Mon 27/04/2009 12:29:17 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE3D46000, 0x0, 0x8299E798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 20/04/2009 09:01:20 your computer crashed
This was likely caused by the following module: classpnp.sys
Bugcheck code: 0x1000000A (0x6DFF25C3, 0x2, 0x0, 0x804E469A)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 19/04/2009 06:36:13 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE2C56000, 0x0, 0x82A75798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 18/04/2009 18:37:46 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE2C45000, 0x0, 0x82A6E798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 15/04/2009 17:45:24 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE2C70000, 0x0, 0x82992798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 15/04/2009 17:39:33 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE2CB1000, 0x0, 0x82A6E798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 11/04/2009 09:02:05 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE4150000, 0x0, 0x82A4B798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 04/04/2009 11:06:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE1A4A000, 0x0, 0x82977798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 03/04/2009 15:10:56 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE4125000, 0x0, 0x829C9798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 24/03/2009 18:03:57 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE171D000, 0x0, 0x82A48798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 20/03/2009 09:19:10 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE2B51000, 0x0, 0x8298B798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 12/03/2009 10:59:54 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE29CF000, 0x0, 0x829AA798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 28/02/2009 10:33:54 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE4811000, 0x0, 0x82DF3798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 22/02/2009 21:59:47 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE2C9A000, 0x0, 0x82DAF798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 16/02/2009 17:55:32 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE416B000, 0x0, 0x82DBB798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 09/02/2009 22:16:56 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE305E000, 0x0, 0x82DD2798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 06/02/2009 19:00:15 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE4D0C000, 0x0, 0x82DC3798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 28/01/2009 19:28:35 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE36BF000, 0x0, 0x82DC3798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 23/01/2009 13:31:29 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE3E54000, 0x0, 0x82D94798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 21/01/2009 16:07:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE39C8000, 0x0, 0x82E62798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 19/01/2009 20:09:12 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE39F9000, 0x0, 0x82E07798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 09/01/2009 20:24:25 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE598F000, 0x0, 0x82DBB798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 30/12/2008 12:53:39 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE2CEC000, 0x0, 0x82DC3798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 27/12/2008 16:16:05 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE432B000, 0x0, 0x82DD7798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 19/12/2008 20:35:49 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE2829000, 0x0, 0x82DC3798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 13/12/2008 10:36:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE3347000, 0x0, 0x82DE1798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 11/12/2008 20:18:47 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE1CB6000, 0x0, 0x82DC9798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 02/12/2008 20:28:06 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE428E000, 0x0, 0x82DDF798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 30/11/2008 20:21:04 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE1A8A000, 0x0, 0x82DCA798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 30/11/2008 20:15:54 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE3E72000, 0x0, 0x82DBE798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 24/11/2008 10:01:20 your computer crashed
This was likely caused by the following module: atapi.sys
Bugcheck code: 0x1000000A (0x2EA83008, 0x2, 0x0, 0x804EA78A)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 31/10/2008 18:30:50 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE427C000, 0x0, 0x82DEC798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 14/10/2008 14:33:35 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE3B58000, 0x0, 0x82606798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 13/10/2008 14:07:33 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE28E7000, 0x0, 0x82608798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 13/10/2008 13:55:28 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE5036000, 0x0, 0x825E1798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 05/10/2008 17:07:56 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE2A79000, 0x0, 0x82649798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 04/10/2008 09:53:45 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE2926000, 0x0, 0x82654798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 04/10/2008 09:48:02 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE297F000, 0x0, 0x82646798, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 24/09/2008 08:30:22 your computer crashed
This was likely caused by the following module: ati2mtag.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xF65DEEB0, 0xF89B5558, 0xF89B5254)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\ati2mtag.sys
product: ATI Radeon WindowsNT Miniport Driver
company: ATI Technologies Inc.
description: ATI Radeon WindowsNT Miniport Driver



On Wed 24/09/2008 08:25:19 your computer crashed
This was likely caused by the following module: ati2mtag.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xF667EEB0, 0xF89B9558, 0xF89B9254)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\ati2mtag.sys
product: ATI Radeon WindowsNT Miniport Driver
company: ATI Technologies Inc.
description: ATI Radeon WindowsNT Miniport Driver




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

53 crash dumps have been found on your computer. Only 40 have been analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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

#7
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Let's check your memory and make sure there is no issue with it.Donwload memtest86 from the link in my signature below.


Get the file that is named Download - The one you want is "Download - Pre-compiled Bootable ISO (.zip). When it downloads, it will be labeled memtest86+2.11.iso.zip
Unzip the file once you download it. You should have a .iso file in the unzipped directory. It will look like a zip file in some cases but the file name will now be memtest86+2.11.iso

if you don't have a burning program that will burn .ISO files get burncdcc in my signature below.

NOTE...do not put a blank cd in until burncdcc opens the tray for you
1. Start BurnCDCC
2. Browse to the ISO file you want to burn on cd/dvd ....in this case its memtest86.iso
3. Select the ISO file
4. click on Start

Make sure the bios is set for the cd drive as the first boot device
Put the cd in the cd drive and then boot your computer.

Running the Diagnostic Program:

The basic diagnostic screen has five main sections of relevant information. Three at the top which are labeled, PASS %, TEST %, and TEST #. This will basically show you the total progress of the current test, the overall progress of the diagnostic test, and the test number is currently performing.

On the middle left hand side of the of the program interface there is a “Wall Time” section that will keep track of how long the diagnostic test has been running for. This just gives you an idea if you are not attending the testing process.

The main section to look for is the lower half of the screen which is usually blank. As long as the memory testing is going ok with no errors this section of the screen should remain blank. If the diagnostic program finds any serious faults in the memory you will see it display a memory dump of address’s in this section. This is similar to what is displayed on your screen when you encounter a blue screen of death.

You now have most everything you need to know about setting up and testing your memory with diagnostic programs. This guide should help you get to the source of any intermittent problems related to your memory.


Run memtest for at least 2 hours
If it starts showing any errors during that time then you will have to replace the memory
If there are no errors after 2 hours press Esc and that will end the tests
We will then try other options
  • 0

#8
Solar energy

Solar energy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 25 posts
There are lots of red on the event log. Very laborious time checking them.

Most red Applications refer to Google Updater.

All kinds of events listed under INFO that I know nothing about. I assume that as they are 'Info' I need not worry?

i have taken a few screenshots - attached in separate posts, though I can not guarantee that they match up with system crash events.

Attached Files


  • 0

#9
Solar energy

Solar energy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 25 posts
Event viewer page 2

Attached Files


  • 0

#10
Solar energy

Solar energy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 25 posts
Event viewer page 3

Attached Files


  • 0

Advertisements


#11
Solar energy

Solar energy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 25 posts
Event viewer page 4 (final)

Attached Files


  • 0

#12
Solar energy

Solar energy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 25 posts
Sorry, I need to check bios set to CD - not sure how to do this.

'Make sure the bios is set for the cd drive as the first boot device
Put the cd in the cd drive and then boot your computer.'

Cheers
  • 0

#13
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
To set the boot sequence do the following in order:

Reboot the system and at the first post screen(where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click enter
Look for Boot Sequence or Boot Options and highlight that click enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.
Hopefully you have already put the XP cd in the drive before all this. If everything is setup correctly you will get a black screen with the following message in the upper left corner "Push Any Key To Boot To Cd". When you see this then push any key and the cd will take over. Follow then with the instructions in post 7 to run memtest86
  • 0

#14
Solar energy

Solar energy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 25 posts
memory test run through a couple of times. Went cleanly. Wife wants me to run it on her!!
  • 0

#15
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Lets see what you have in your startup

Please click on
Start and then to Run
Type in msconfig and press enter
Now click on Startups
Then uncheck everything and restart.
If system boots correctly and is running smoothly and faster then we have a startup problem
Try going back into msconfig and check one item and reboot
Keep doing that till you have found the problem or all are finally checked.
Post back with the results

If this doesn't fix the problem the continue with the next step


Lets see what you have in your startup

Please click on
Start and then to Run
Type in msconfig and press enter
Now click on Startups
Then uncheck everything and restart.
If system boots correctly and is running smoothly and faster then we have a startup problem
Try going back into msconfig and check one item and reboot
Keep doing that till you have found the problem or all are finally checked.
Post back with the results
  • 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