BleepingComputer.com: BSOD errors

OK, I'll play around with the memory and see if I can isolate what the problem is.

Thanks and I'l let you know, MrC

Memtest proved that it wasnt the RAM, BSOD's can be caused by bad and/or outdated drivers. Proceed with the easiest less costly steps first then escalate to more expensive troubleshooting techniques.

Did you get these issues on XP Home?

cryptodan, on Mar 24 2010, 05:47 PM, said:

Hi, I don't want to use the shotgun approach.

A step at a time works best for me.
After the memory checks out I'll move on to something else, right now I'm going to play around with the memory to see if I can find a problem with it.

Thanks, MrC

This is my troubleshooting process when it comes to BSOD's:

1) Check for driver updates, and perform them. If the BSOD still occurs then I test the hardware in another machine if it checks out in that machine, then I replace the cables connecting that hardware.

If the issue is still present, I look at expansion cards and remove them until the issue stops then slowly reinstall each card until the issue appears. If the issue is not present in either of the afforementioned steps I then look at the RAM, CPU, and motherboard and lastly the power supply. I leave all the most sensitive pieces of hardware alone until I verify that it is in fact hardware related such as bad ram, bad drives, bad CPU, damaged power supply, and what not. If all my hardware checks out I will perform a low level format and reinstall the OS.

If any of the hardware indicates that it is the issue I replace it.

If go about messing with RAM you could inadvertently damage some other components. I try not to be inside my case as much as possible to avoid the accidental discharge of static electricity.

Also part of my troubleshooting removes the case as a possible culprit bad grounding can cause weird and unforeseen issues such as random BSOD's and what not.

I remove all the components and lay it on a rubber mat or a piece of cardboard and hook it all up, and test it out of the case.

Sorry Bleepin Madman I missed this post:

Quote

Memtest proved that it wasnt the RAM, BSOD's can be caused by bad and/or outdated drivers. Proceed with the easiest less costly steps first then escalate to more expensive troubleshooting techniques.

Did you get these issues on XP Home?

Yes I got them with XP home.
It was fully updated with SP2 and the lastest drivers I could fine.

I loaded up XP pro and got the same thing.
XP pro has SP3 and all the latest Windows updates but I didn't update any drivers yet.

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

Last night and today I tested ram.....one stick at a time and it test OK.....no errors.

I appreciate everyones help.

Computer has been disassembled and put back together with the same results.
Updating drivers doesn't seem to make a difference.

I'm thinking it's a more a hardware problem or configuration problem.

Right now I'm just running it with one stick of memory.


Thanks......MrC

This post has been edited by MrCharlie: 25 March 2010 - 05:34 PM

Has it blue screened yet with the 1 stick of RAM?

cryptodan, on Mar 25 2010, 08:36 PM, said:

Yes it crashed yesterday with one stick in it, I'm now running it with the other stick.

I'll post back and let you know, Thanks MrC

Try upgrading all your drivers.

cryptodan, on Mar 27 2010, 03:44 PM, said:

OK, got BSOD with the other stick of ram, I update all the drivers now....lets see if that does it.


MrC

Sorry to say I'm still getting BSOD after updating drivers.

MrC

Then its a hardware issue.

It's been around 5 or 6 days now without any crashes, here's what I did so far.

I couldn't find another AGP video card that would fit this motherboard but I did have an old PCI Sound Blaster video card, popped it in and it's been OK ever since.

Looking through my stock of parts I finally did find a couple of AGP cards that will work, I'll put one in and see how it is ASAP.

It's either a bad a bad video card, bad motherboard or I have something configured wrong (I don't think so though).

I'll post back and let you know, MrC

This post has been edited by MrCharlie: 07 April 2010 - 05:28 PM

Well I finally found the problem, though it didn't take me all this time to find it.....I just put up with the BSOD until it got so bad I had to finally fix it.
I was convinced it wasn't anything to do with the operating system or drivers, so I started swapping out parts until I got down to either the mother board or processor.
I put in a new processor (a little bigger 3500) and it's been fine ever since, no more errors or BSOD screens.

Thanks.......MrC

thanks for posting your resolution happy computing.