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 keeps crashing


  • Please log in to reply

#16
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Open Autoruns, click on "Logon" tab, and UN-check:

+ iTunesHelper
+ QuickTime Task
+ SunJavaUpdateSched
+ Adobe Reader Speed Launch.lnk
+ Microsoft Office.lnk
+ MSMSGS Windows Messenger
+ QuickTime Task....There are two of these running so make sure both are shutdown
+ ctfmon.exe



To turn off just ctfmon.exe go to:


Control Panel then to Regional and Language Options

Click on the Languages Tab then click the Details button

Click on the Advanced tab

Check the box that says Turn off advanced text services option

Click A and then OK





When done restart computer and then:


Download Temp File Cleaner (TFC)
Double click on TFC.exe to run the program.
Click on Start button to begin cleaning process.
TFC will close all running programs, and it may ask you to restart computer.


Download Auslogics Defrag from the link in my signature below. Auslogics Defrag in my opinion is better because:

It does a more comprehensive job at Defragging
It will actually show you what it is doing
At the end of working it will show you how much speed you picked up
You can view a online log of the files that Auslogics defragged


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

Edited by rshaffer61, 01 July 2009 - 09:05 AM.

  • 0

Advertisements


#17
sil3nton3

sil3nton3

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are disabled for your computer.


On Fri 6/5/2009 8:52:22 PM your computer crashed
This was likely caused by the following module: saskutil.sys
Bugcheck code: 0x10000050 (0xF1B01434, 0x0, 0x82F1EF51, 0x0)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on saskutil.sys





On Fri 6/5/2009 5:50:10 AM your computer crashed
This was likely caused by the following module: saskutil.sys
Bugcheck code: 0x10000050 (0xF06277EC, 0x0, 0x82F20F51, 0x0)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on saskutil.sys





On Fri 6/5/2009 1:36:35 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x10000050 (0xF0A3B9DC, 0x0, 0x82F20F51, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 6/4/2009 5:34:18 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x10000050 (0xF115A5C4, 0x0, 0x82F89F51, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 6/4/2009 3:29:19 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x10000050 (0xF176B73C, 0x0, 0x82F8BF51, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 6/4/2009 3:03:28 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x10000050 (0xF14524D4, 0x0, 0x82F8BF51, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 6/4/2009 2:52:23 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D1 (0xE194D000, 0x2, 0x0, 0xF6779B00)
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 6/4/2009 12:17:58 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D1 (0xE1902000, 0x2, 0x0, 0xF677DB00)
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 6/4/2009 12:02:16 AM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x82DF9538, 0x82DF96AC, 0x805FB046)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 6/3/2009 11:52:18 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x82DBD9A8, 0x82DBDB1C, 0x805FB046)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 6/3/2009 11:16:04 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x82BA0270, 0x82BA03E4, 0x805FB046)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 5/28/2009 4:36:50 AM your computer crashed
This was likely caused by the following module: rtccpxxoqoufnlqb.sys
Bugcheck code: 0x1000007E (0xC0000005, 0x82416C0D, 0xF8A44A10, 0xF8A4470C)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on rtccpxxoqoufnlqb.sys





On Sat 5/9/2009 12:10:48 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D1 (0xE1953000, 0x2, 0x0, 0xF67D1CF1)
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 5/7/2009 6:30:07 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D1 (0xE1956000, 0x2, 0x0, 0xF6734CF1)
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 5/4/2009 5:16:00 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D1 (0xE1958000, 0x2, 0x0, 0xF6788CF1)
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 5/1/2009 12:52:16 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D1 (0xE18FC000, 0x2, 0x0, 0xF679ACF1)
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 7/11/2007 7:04:23 AM your computer crashed
This was likely caused by the following module: nv4_disp.dll
Bugcheck code: 0x1000008E (0xC0000005, 0xBFA20D85, 0xF16391A0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 30.82
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 30.82




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

17 crash dumps have been found and 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

#18
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Last reported crash was

"On Fri 6/5/2009 8:52:22 PM"

Has there been a crash since following my previous instructions?
  • 0

#19
sil3nton3

sil3nton3

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
There were about 3 or 4 crashes 3 days ago. My computer crashed once or twice yesterday. Today, it hasn't crashed yet. I think it crashes when the temperature 2 on speedfan goes around 65 C. So I think my computer is overheating. After cleaning up my computer a little bit, I think it will only happen when I watch a few videos on youtube or something.

The crashes posted up above were from viruses. I made a thread about that a few weeks ago and the viruses were cleared. The recent crashes are from something else.

Edited by sil3nton3, 01 July 2009 - 02:17 PM.

  • 0

#20
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK so nothing new as far as crashes from WhoCrashed then?
Did you do the TFC and Auslogics Defrag?

IF there is a overheating problem then the fan on the cpu may be slowing down.
Is this a desktop or a laptop?
Is it under warranty still?
Do you have your original OS disk?
  • 0

#21
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Let's check your memory and make sure there is no issue with it. Download 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

#22
sil3nton3

sil3nton3

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts

OK so nothing new as far as crashes from WhoCrashed then?
Did you do the TFC and Auslogics Defrag?

IF there is a overheating problem then the fan on the cpu may be slowing down.
Is this a desktop or a laptop?
Is it under warranty still?
Do you have your original OS disk?


It is a desktop.
I don't think it's under warranty anymore.
I don't have the original OS disk.

I'll try what you said in your latest post.
  • 0

#23
diabillic

diabillic

    Member 1K

  • Member
  • PipPipPipPip
  • 1,370 posts
On Thu 5/28/2009 4:36:50 AM your computer crashed
This was likely caused by the following module: rtccpxxoqoufnlqb.sys
Bugcheck code: 0x1000007E (0xC0000005, 0x82416C0D, 0xF8A44A10, 0xF8A4470C)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on rtccpxxoqoufnlqb.sys

That is tied in with malware. Although it may not be causing the shutdowns, I would recommend going to the Malware forums once were done here to remove it.

Also, I would check for bulging capacitors on your board as suggested before. They will be obviously bigger then the others surrounding it and usually are leaking as well. If this is the case, the board needs to be replaced.
  • 0

#24
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
You also should think about increasing memory
512 megs is bare minimum for XP to run.

Go HERE and run the Crucial online scanner.
This will give you the exact memory configuration for your system. You do not have to buy the memory from there, but write down the information and if you need assistance in purchasing the upgrade memory GTG can assist with suggestions also.
  • 0

#25
sil3nton3

sil3nton3

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
I think the problem is gone. I just started a few HD videos at the same time for the past twenty minutes and the temperature maxed at 68 C on the speedfan thing for temperature 2. Thanks for your help everybody. I think the auslogics thing and the other cleaners stopped it.
  • 0

Advertisements


#26
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Please take notice of the last post numbers 23 and 24.
I suggest that you increase your memory to at least a gig.

I suggest you go to the Malware Forum and run all the steps located in the START HERE. These self-help tools will help you clean up 70% of problems on your own. If you are still having problems after doing the steps, then please post the reguested logs in THAT forum. If you are unable to run any of the tools then start a new topic in the malware forum and put this in the subject line...I am unable to run any malware tools

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).

Add a link to this topic so that malware tech can see what steps have been taken here
  • 0

#27
123Runner

123Runner

    Member 4k

  • Member
  • PipPipPipPipPipPipPip
  • 4,307 posts
I have to agree with Rshaffer61 that it most likely is not heat related since it runs in safe mode. But it will not hurt to clean the fans. Without reading the entire post again, did you clean the dust from all the fans? That also includes the fan and heatsink on the CPU. Also check the fan and heatsink (if any) on the GPU (video card).
Also make sure the fan on the power supply is clean. People tend to forget that one.

It was brought up about possible bad capacitors (and yes it is capacitors and not condensors). I have not seen nor heard of this issue for many years. To verify on your board, it is an easy step. You need to open the case to clean the fans, so take a look at the capacitors.
Info and pictures of bad capacitors. Click on the pictures on the right for better viewing.
  • 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