Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Stumped on Blue Screens of Death


  • Please log in to reply
1 reply to this topic

#1 s_hax

s_hax

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:04:58 PM

Posted 24 August 2009 - 09:42 AM

Hi everybody. I'm having some serious trouble trying to isolate the cause of some random blue screens of death (and possibly software crashes), so I was hoping perhaps you could weigh in on the matter.

---------------------------

My system:

Motherboard: Asus M3A78-CM
CPU: AMD Athlon X2 64 6000+
CPU Cooler: Stock
Memory: 2GB DDR2 stick (not sure what brand, but probably cheapo value ram or something)
Video Card: Gigabyte GeForce 9800 GT 1GB (GV-98TOC-1GI)
Video Card Cooler: Stock
Video Driver: 186.18 (the latest one certified by Gigabyte, and yes I tried the more recent one)
Hard Drive: Western Digital Caviar Blue 640GB SATA (WD6400AAKS)
PSU: 600 watts (will have to check model later)
Airflow: One lower front 120mm intake fan (purchased later), one rear 120mm exhaust fan, one side CPU intake funnel, one empty side intake grill under the video card
Optical: Crappy IDE CD-RW drive I ripped out of an old HP Pavilion
OS: Windows XP Pro SP3 32-bit
DirectX version: 9.0c
Antivirus: Avira (free version)
Primary use: Second Life (yeah yeah, ha ha, point and laugh)


The problem:

I purchased this system back in June. At first I experienced nothing unusual. But then I started to get BSOD's randomly while playing Second Life (which I shall henceforth refer to as SL for the sake of brevity). These BSOD's seemed to increase in frequency as the summer wore on. The error messages they produced were all over the map and never consistent from BSOD to BSOD. No I am not an overclocker.


Things I've tried:

* Buying a front intake fan
* Malware scan (which revealed that I was infected with Delphi, I'm ashamed to admit)
* Reinstalling Windows and downloading all critical updates
* Making sure all system drivers are correct and up to date
* Trying different versions of the nVidia driver, using Driver Cleaner before each install
* Flushing out the system with CCleaner
* Examining minidumps (which was pointless given the randomness of the BSOD errors)
* Installing AMD Dual Core Optimizer
* Installing AMD Cool n' Quiet driver (yes I set Windows power management to minimal)
* Installing Asus PC Probe (the temperature readings were normal, CPU spiked at 67 celcius before adding front intake fan, now spikes around 57)
* Installing Gigabyte Gamer HUD (GPU temperature spiked in the mid forties, no I didn't touch the voltage slider)
* Flashing the BIOS of my board to the latest version (2003)
* Using different versions of the SL viewer
* Lowering the graphics settings on SL
* Setting the graphics to performance mode in nVidia control panel
* Running the system with the side panel off and a giant desk fan pointed inside
* Tightening all screws and reseating all components and cables (with a wrist strap, of course)
* Putting the 2 gig memory stick in another memory slot
* Running Memtest overnight (no errors)
* Running Prime95 overnight (no errors, and the CPU thermals were way higher than anything SL could ever hope to generate)
* Running Data Lifeguard Diagnostics extended scan on the hard drive (no errors)
* Running CHKDSK (no errors)
* Running 3dMark06 free edition (no errors, and everything displayed beautifully with the exception of the CPU test, in which framerates slowed to a crawl)
* Moving cables aside to maximize airflow
* Moving the computer to the floor with the front pointed at a floor air con vent


Things I've thought of but haven't tried yet:

* Stress testing the video card with Furmark (renders highly detailed fur, very hard on GPU, will do this in the evening)
* Cleaning all the contacts with isopropyl alcohol
* Replacing components one at a time to see if anything stops the problems (I don't have the resources for that)
* Running professional hardware diagnostics (ditto)
* Installing Windows 7 (I've preordered a copy for October)
* Dusting (no way dust is a problem this early on)
* Buying a side intake fan for the vent under the video card
* Adjusting memory voltages in the motherboard BIOS setup (that might be a bit dangerous given my lack of experience doing such things)
* Yelling at it until it bows to my iron-fisted rule
* Throwing cream pies at the motherboard and then spraying it with seltzer
* Taking it out to dinner and telling it how much I love it


Other notes:

* It seems as if when I bought the front intake fan that the BSODs pretty much stopped, although SL and Firefox crashes seemed to increase in frequency as if in place of the BSODs. However, yesterday I got another blue screen (in a particularly complex simulation in SL) after a week without seeing any BSODs.
* The BSODs and SL viewer crashes seem to generally occur when a large volume of textures and objects tries to render all at once (particularly in crowded areas). Firefox crashes seem to occur at random.

-----------------------------

So there you have it. A fairly exhaustive summary of the whole unfortunate business. If you have any suggestions or questions, feel free to chime in. I'm running out of ideas.

Edited by s_hax, 24 August 2009 - 10:04 AM.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,102 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:58 PM

Posted 24 August 2009 - 12:54 PM

Hello :thumbsup:.

Although your summary is good...the content of the various BSOD error messages would be more useful.

If you take a look at http://www.aumha.org/a/stop.htm, you'll get an idea of the number and types of different STOP errors/BSODs which can be inflicted on a system. Not all are listed but the more common ones are.

I will also point out that many error messages have correspondingly analyses/explanations that are very general in nature. Many will cite "possible driver" or "possible RAM" as being the seemingly decisive factor. In reality, it's often the RAM where the error shows up...not necessarily the RAM being responsible for creation of the error.

To eliminate/diagnose the likelihood of RAM being an actual cause, you can run Memtest86+, following the directions guideline provided in the links I will add.

Memtest86+ - Advanced Memory Diagnostic Tool - http://www.memtest.org/#downiso

Icrontic Diagnose with Memtest86+ - http://icrontic.com/articles/diagnose_with_memtest86

MemTest Manual - http://hcidesign.com/memtest/manual.html

Driver situations are a bit more difficult to pinpoint...which is why the exact content of the error message or an analysis of the .dmp file produced...can be a better provider of clues.

Help Diagnosing BSODs And Crashes (BC) - http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/

The phrase "drivers" are not restricted to hardware items. Your AV program, firewall, music editors, graphics editors, etc. all have drivers. So, if one can trace it to "a driver", we still need to dig a bit deeper. The steps in the link directly above this line will assist in doing that.

Louis

Edited by hamluis, 24 August 2009 - 12:54 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users