Rig in trouble :(

**singhaxn** · 28-06-09, 11:43 AM

Hi,

I got some good suggestions here when I was buying a new PC. So I'm hoping you guys can now help me figure out what's wrong with my machine...

Here's my configuration:

Processor: Intel Q8200

Mobo: Gigabyte GA-EP45C-DS3R

RAM: Transcend DDR3 1333MHz 2 x 2GB

HD: Western Digital Caviar Green WD10EADS

Graphics card: Palit Radeon HD4850 512MB

PSU: Corsair VX450W

UPS: APC Back-UPS 650VA

Cabinet: Coolermaster Elite 335

OS: Dual boot Windows Vista / Fedora 10 x86_64

Peripherals connected (may not matter):

Logitech PS/2 keyboard

Logitech MX518 USB mouse

Altec Lansing VS4121 speakers

ViewSonic 19" Widescreen connected using analog cable

I've had this system for about 2 months now.

The problem is that, over the last week or so, my system freezes every now and then and the only way out is a hard reset. I haven't really been able to pinpoint a pattern to these freezes.

I don't think this is a software issue because this happens on Windows as well as Linux.

From what info I discovered on the net, common causes are RAM and HD malfunction and heat. So I've tested my RAM using memtest86+ and HD with WD Data Lifeguard Diagnostic for Windows and HDTune but no problems were detected. I've been monitoring my temperatures using HWMonitor on windows and the Sensors applet in Gnome. The temperatures all (system, cores, GPU, HD) seem to remain in the 40 - 50 range at most times. If I run some processor intensive task, the core temperatures tend to go up to 65 at most. I've tried playing Burnout Paradise but it doesn't always freeze while playing the game.

Something new happened today. While I was working on my machine, the screen went blank, there were 9 beeps from the cabinet. I looked it up. Apparently that indicates a BIOS error? But I thought such errors were meant to be detected at boot time. Am I wrong?

Is it a BIOS problem? What else can the problem be? What else can I try?

Any help will be greatly appreciated.

Thanks,

Akshay

**DevinWolf** · 28-06-09, 02:52 PM

It might be an overheating issue.

**antonieo** · 28-06-09, 02:56 PM

is there any particular thing when u are working it is happening or it doesnt matters

**antonieo** · 28-06-09, 02:57 PM

if bios is a problem i think that is not the type of error u will get

**DevinWolf** · 28-06-09, 03:00 PM

please don't double post. and singhaxn monitor your temps. tell us the result.

**hatter** · 28-06-09, 07:16 PM

See what Google threw up:

9 Beeps: ROM BIOS checksum failure

Explanation: The read-only memory (ROM) containing the BIOS program (which is what is running when you turn on the PC and what generates this error) uses a checksum value as a double-check that the ROM code is correct. This checksum is compared against the values in the ROM each time the PC is booted and if there is a mismatch, this code is generated.

Note: This error is not the same as a CMOS Checksum Error, which refers to corrupted values of the CMOS settings, the ones you set through the BIOS setup program. This error means the contents of the BIOS code itself are damaged.

Diagnosis: The BIOS ROM chip on the motherboard is probably faulty. It could also be another component on the motherboard.

Recommendation: Troubleshoot the motherboard. It is possible to replace just the BIOS ROM chip but often replacing the motherboard will make more sense for cost and simplicity reasons.

9 Beeps: ROM BIOS checksum failure

I think either it's RAM or BIOS ROM. You can try and use your PC with one RAM stick at a time and see what happens. Or else, I think you need to RMA the mobo.

**prandi** · 28-06-09, 11:09 PM

check with one stick of ram at a time,,,beeps are given during post,,here his comp restarts in b/w indicating ram failure,dont think wd will ditch him so early!!!,,,did u overclock ne thing?the only thing im missing how did ur comp give beep after windows booted??i think when ur screen went blank ur comp restarted and then gave beeps...or the worst thing that can happen is mem controller failure ie mobo dead!!!i heard that mobo got sme problem dont exactly remember wat it was,,google it