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

Random crashes on my PC (Win XP)


  • Please log in to reply

#1
The Fury

The Fury

    Member

  • Member
  • PipPip
  • 14 posts
First of all, hello.

So here's the thing. My PC random crashes, it can be after 20 min or after 2h. Best of all, I am just surfing or doing nothing special. Screen frezzes foe 2 seconds and it restart. Sometimes is normal boot, but sometimes it has corrupted data (strange letters). No error information.

My conf: Win XP SP2
AMD Athlon 64 X2 6000+
Gigabyte MA790X-DS4
Saphhire Ati HD 4850 Toxic
Corsair VX 550W
G-skill 4 gb ram

Recently I've changed my screen, because my old one broke down, and now I am using old CRT. Can that be a issue?

Also, I've done few tests with OCCT and temp seems fine to me.
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Hello The Fury.... Welcome to GeeksToGo, :) :) :)

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.

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
  • 0

#3
The Fury

The Fury

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
That was super fast reply :)

Here ya go:

On Mon 31.8.2009 17:44:23 your computer crashed
This was likely caused by the following module: bdfndisf.sys
Bugcheck code: 0x1000007F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\drivers\bdfndisf.sys
product: BitDefender 12
company: BitDefender LLC
description: BitDefender Firewall NDIS Filter Driver



On Mon 31.8.2009 9:07:41 your computer crashed
This was likely caused by the following module: bdfndisf.sys
Bugcheck code: 0x1000007F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\drivers\bdfndisf.sys
product: BitDefender 12
company: BitDefender LLC
description: BitDefender Firewall NDIS Filter Driver



On Sun 30.8.2009 9:10:22 your computer crashed
This was likely caused by the following module: bdfndisf.sys
Bugcheck code: 0x100000D1 (0x8, 0x2, 0x0, 0xB9E1D848)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\bdfndisf.sys
product: BitDefender 12
company: BitDefender LLC
description: BitDefender Firewall NDIS Filter Driver

BitDefender is causing all this trouble?! I was using BD for bout 6 months and all of sudden started to crash.

Edited by The Fury, 01 September 2009 - 08:44 AM.

  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
All your crashes are due to Bit Defender
Uninstall it and see if the issue resolves itself.
  • 0

#5
The Fury

The Fury

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
I uninstalled BitDefender and installed Avira, just in case to have some antivirus program. My comp was on for bout 3 hours, when I heard strange beep sound. I was like :) After 10 min or less there was another beep beep, so I decided to turn off comp.

Now is on again and I will try find out where that sound came from. Any advices or tips to check it out? :)
  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
I see you already checked the temps but another program results will not hurt to verify the settings.
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

#7
diabillic

diabillic

    Member 1K

  • Member
  • PipPipPipPip
  • 1,370 posts
Kernel Mode traps are usually caused by bad memory. Run memtest86+
  • 0

#8
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Since no instructions were included with Diabillic's post I will supply them for you.


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

#9
The Fury

The Fury

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
Okay here it is.
I have also put OCCT with it.

Attached Thumbnails

  • pic.JPG

Edited by The Fury, 01 September 2009 - 11:42 AM.

  • 0

#10
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK not sure what Temp 3 is but it is very hot.
Could be GPU
  • 0

Advertisements


#11
The Fury

The Fury

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts

OK not sure what Temp 3 is but it is very hot.
Could be GPU


Catalyst Control Center says that GPU temp is about 47-50C
  • 0

#12
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK then that is not the issue.
Please do the Memtest86 test and let us know.
  • 0

#13
The Fury

The Fury

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
Ive done the memtest and it passed, no errors. We have one problem less.

After restart, it was corrupted letters an stuff and there were some horizontal lines across the screen.
GPU temp is now from 50-54 in idle state. Maybe the graphic card is overheating?

I am ready for new tests. :)

Edited by The Fury, 01 September 2009 - 01:43 PM.

  • 0

#14
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
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.

Let me know if this fixes the problem
  • 0

#15
The Fury

The Fury

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
Okay, so this what happens:
after restart screen was corrupted, as I mentioned before and after a while BSOD appeared.

It was really hard to read, (letters were screwed) it mentioned some drivers and loop, and also ati2vg (not sure) :)

It seems that GPU is the problem, what next?
  • 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