PC HELP TOO!

Superman · Post by **Superman** » 2003-05-10 09:29am

Ok, my computer keeps doing that restart thing, and this is the error code I am getting. I think there is a hardware problem.

BCCode : be BCP1 : F7021816 BCP2 : 08BCE121 BCP3 : 8053BC68
BCP4 : 0000000A OSVer : 5_1_2600 SP : 0_0 Product : 768_1

Any idea what that means?

Rye · Post by **Rye** » 2003-05-10 09:33am

I would hazard a guess at a hard drive, or the socket where the hd cables meet the mobo, or the IDE cables.

Just a guess like, but it sounds familiar to a problem i had a while ago. Fixed mine by replacing cables and formatting the hard drive.

Superman · Post by **Superman** » 2003-05-10 09:37am

Fucking Bill Gates. When will Windows be advanced enough to run a diagnostic and tell us EXACTLY what the problem is. Instead, we get some overly ambiguous code that means jack shit.

Ok, how do I replace the cables? You mean all of my cables? I reformatted the HD tonight and it's still doing this. The cables that connect the power source, monitor, etc?

Batman · Post by **Batman** » 2003-05-10 09:46am

1. Reconnect the IDE cables, i.e. the ones from the HDD/CDROM/whatever to the motherboard (I'm assunming you've got an IDE system). If you have spare cables, try those, but a reconnect might do the trick if it's a bad connection.

2.Ditto to the power cables.You'll propably not be able to replace them (the ones from the power supply are usually not unpluggable), but again the problem might be a bad connection.

3.Reset all cards.Make sure they're firmly in their slots.

4. If this doesn't help, try starting with the BIOSes DEFAULT or SAFETY values. This resets all components to their mosr conservative specs.

5. Disconnect all components but the boot HDD. One of them may be faulty.

6. If you have another HDD to try, do so, allthough a faulty HDD should have balked at the reformat.

7. Don't get mad at me because half of those options require components you don't have. I guess I just come from a techie background...

Rye · Post by **Rye** » 2003-05-10 11:03am

There's an old tactic gained from consoles in the past, when something doesnt work, remove what you think doesnt work and blow on all the connecting bits, then put them back together, making sure IDE cables and the like are all in as much as possible without breaking somerthing.

Also make sure no pins or anything are bent on the sockets.

TrailerParkJawa · Post by **TrailerParkJawa** » 2003-05-10 11:06am

Where are you seeing this error? While the computer boots up and it is being reported by BIOS?

BrYaN19kc · Post by **BrYaN19kc** » 2003-05-10 11:20am

This could very well be a driver problem. We have had similar experiences in our lab computers. Microsoft suggests the following, if you have added any new hardware ---------- Hope it helps.

"Click Start, right-click My Computer, and then click Properties.
In the System Properties dialog box, click the Hardware tab, and then click Device Manager.
For each device, use the following steps to verify that it is using a Windows XP-compatible driver.NOTE: To narrow down the search, begin with devices that have been disabled. A disabled device has its icon overlaid with a red X.

Double-click the device name to open the device Properties dialog box, and then click the Driver tab.
Examine the driver version. All Windows XP drivers should be version 5.1.2600 or later.
If you are not sure about the displayed version, examine the driver date. Drivers created before the year 2001 may not be compatible with Windows XP.
After you identify an outdated device driver that may be causing the problem, follow these steps to update the driver:
Insert your Windows XP CD into the CD-ROM drive. If Setup starts automatically, quit it.
In the device Properties dialog box, click Update Driver to start the Hardware Update Wizard.
Click Install from a list or specific location (Advanced), and then click Next.
Click to select the Include this location in the search box, and then type your CD-ROM drive letter in the space below. For example, type D:.
Click Next.
Follow the on-screen instructions to finish updating the driver.
Restart your computer if prompted."

Batman · Post by **Batman** » 2003-05-10 01:10pm

TrailerParkJawa wrote:Where are you seeing this error? While the computer boots up and it is being reported by BIOS?

The error message gives an OS version and service pack level number, definitely a Windows message.

And BrYaN19kc brings up a valid question:any changes to your system before the problem arose, Supes? New hardware, driver update, new SW in general?

phongn · Post by **phongn** » 2003-05-10 01:38pm

Superman wrote:Fucking Bill Gates. When will Windows be advanced enough to run a diagnostic and tell us EXACTLY what the problem is. Instead, we get some overly ambiguous code that means jack shit.

And pray tell how would you do that?

Vertigo1 · Post by **Vertigo1** » 2003-05-10 03:21pm

Superman: What exactly have you done to your machine within the last couple of days? Don't leave anything out. Even the most trivial thing might tell us what you did wrong.

Superman · Post by **Superman** » 2003-05-11 06:28am

Ok, all I have added to this machine is a 256 RAM chip, a video camera, a Ge Force 2 card (I know, pretty sad) and... I guess that is it.

You know, it may have started doing this after I added that memory chip. Should I remove it and try running to see what happens?

Xon · Post by **Xon** » 2003-05-11 11:18am

Bad ram chips will bring almost any OS to its knees. So remove it and see if that helps. If it doesnt, try removing the Ge Force 2 card(uninstall the drivers before you remove the card, then physically remove the card. Rebooting as required), the video camera probable wouldnt be an issue so try that last.

Superman · Post by **Superman** » 2003-05-11 11:33am

Dammnit, I was going to buy a 512 card, but the stupid salesman convinced me to buy this 256 for 40 bucks. It had a 20 dollar rebate too. I guess you get what you pay for... If it is the chip, that is.

I have a strange feeling it is that chip...

phongn · Post by **phongn** » 2003-05-11 02:17pm

Take that RAM chip out and see if the computer works. Also, run Memtest86 which will diagnose your RAM.

TrailerParkJawa · Post by **TrailerParkJawa** » 2003-05-11 11:54pm

I hate when RAM conflicts with your PC. Its annoying enough that I purchase my RAM through Crucial.com and suck up the premium price in exchange for getting the right ram and a good delivery time.