2 beeps during post.

[tsunme]

I was trying to update my bios, thinking it would fix the problem I had, but my computer froze mid update and now when i try to boot, I'm getting 2 beeps post. I looked up the beeps and it says memory parity. I'm not sure what this is or how to fix this.

Edit:
OS - Win 7 Ultimate
CPU - AMD FX-8350 Vishera 4.0 GHz
Mobo - GA-970A-UD3 rev 1.2
GPU - XFX Radeon R9 270X
RAM - Crosair VengeanceLP 8GB DDR3 1866
HDD - 1TB WD Blue 7200rpm 64mb cache
PSU - Rosewill Hive-650

 

[Chicano]

Your case looks well constructed and though I cant tell for the images, the price suggests it.. the lowest priced of the nzxt phantom line is a bit high so I imagine it's well constructed and price is an indication of that... but you still have to breadboard the system, so disreguard what I said before and go through with it if you still haven't done so. Keep it running for a reasonable time and if it doesn't lock up, you can safely assume something was wrong with the case or you had some installation error. And if it DOES lock up you can assume the motherboard has issues since you have tested everything else.

Check these threads on the subject fo better and different descriptions of the possibility and causes.
http://www.tomshardware.com/forum/268832-31-breadboarding
http://www.tomshardware.com/forum/307187-30-motherboard-shorting-case
http://slickdeals.net/f/3130372-can-some-pc-cases-short-circuit-motherboards

 

[tsunme]

So i breadborded and i locked up.

 

[Chicano]

You apparently have tested everything so it must be the motherboard. You said you had replaced the motherboard and this was the one you removed?

 

[tsunme]

Yes, this is my original motherboard, it's only about 2 years old. Could it be the motherboard isn't getting enough power? I only have a 4-pin to it (since thats all my psu has).

 

[Chicano]

You have a 4 pin connector on the CPU, and the motherboard is for 8 pins? If so, it's supposed to serve the purpose and only be inadequate for overclocking the CPU... but it's obvious that if the mobo has a 8 pin connector, the PSU should have a 8 pin connector... so, see if a 4 to 8 adapter helps.

http://www.aliexpress.com/item/Motherboard-cpu-adapter-cable-p4-p8-4pin-8pin-4pin-8pin-power-adapter-cable/1200197631.html

 

[tsunme]

btw, i'm running a dual monitor setup, does that change anything about the situation?
ALSO, could it somehow be a bad cpu? idk if its possible, but i do have 8 cores, can 1 somehow fail and make the system freeze?

 

[Chicano]

A dual monitor issue would be more related to the GPU, but any video card... even the onboard chip can handle two monitors.

A bad CPU is very rare. The only possible causes that can kill a CPU may be:
1. Overheating
2. Bad voltage
3. Wrong CPU TDP for motherboard or viceversa (EG: a motherboard with 95W TDP can but should not run a 125W CPU specially not with stock cooling)
4. Abusive Overclocking with inadequate cooling... but the CPU would show signs of issues by slowing down and will even shutdown the computer before suffering damage.

 

[tsunme]

mmk, well i'll try the 8pin option first and then go from there.

 

[tsunme]

So I got a new psu, hooked it up. Still freezing, so I don't know what could be the problem anymore.

 

[Chicano]

By process of elimination: the Motheboard...
You have tested everything and you had removed the motherboard before... for a good reason I imagine.

 

[tsunme]

That's the thing though I've tried a different one, it was brand new, and I still had it freeze on me.
So the question is, if it's the motherboard, what is causing this to happen, and how, and why is did it happen also on a brand new one as well.

 

[Chicano]

I believe everything has been considered and you have apparently done everything suggested(?).. So it's not easy to say what has been the cause... sometimes issues happen that can not be identified. I have read users making fun on their issues refering to them as supernatural possesion.. other times problems that persist and will not be solved after considering and testing everything,.. suddenly one day normalize and solve on their own... that how electronics act up sometimes and there is no way to identify the cause by regular means. There must be an explanation but it may need electronic tools to find the cause, and since everything has been considered and apparently checked, tested and found normal, the only thing that comes to mind is the use of a Motherboard tester... they come in different types and prices from low to considerable, so that would be my last suggestion... buy one and connect it to the motherboard either in a USB port or a expansion slot... it should analize the motherboard when you start it up, and come up with a code you can search the net for to identify the issue or the gadjet may come with a code leaflet.

Buy something like these Motherboard diagnose tools
http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&DEPA=0&Order=BESTMATCH&Description=motherboard+tester&N=-1&isNodeId=1

 

[tsunme]

so, just got my tester is, hooked it up via usb, restarted my computer and its giving me an FF error code. looking it up it says 'int. 19 boot attempt - flash rom programming was successful. next, restarting bios.' not sure what this mean. also, should i just run my computer until it freezes and see what the tester says?

 

[Chicano]

19 boot attempt doesn't make sense. Restarting BIOS probably means exactly what it says.. Successfull BIOS restart and Post.

If you looked up the codes for your tool and not just for any tool, it may mean the HDD has failed to boot 19 consecutive times(?). Does that coincide with failed boots?. Check your HDD connections to HDD and motherboard. And keep the computer running... see what happens. Don't leave the tool connected unless the instructions say it's ok to do so.

 

[tsunme]

I was reading the meaning behind the code straight from its manual.

 

[Chicano]

Apparently FF means all is OK

Display “00” or “FF” at the end of POST.
Boot the operating system.
Good
End

Page 3
http://web.impakt.com.pl/Z10476_7731.pdf

The issues you've been having are probably caused by the Hard Drive, bad SATA cable, or Bad SATA port.

Options: Run a disk check, replace the SATA cable, move the HDD SATA cable to another SATA port, try a different hard drive.

 

[tsunme]

Ok So I know it's been a while, thats because I haven't had a freeze since i was last on here. But I just had 1 again. and this time i plugged my tester right into my motherboard and restarted. It ran through some of the digits and it stopped on 53, which i looked up and says "Initialize Time Value 40h: Bios Area". I've googled this in all sorts of ways but it just keeps giving the code and the description, i can't find anything about what it means or how to fix it.

 

[Selenog]

What mobo are you running now? If it's the GA-970A-UD3 rev 1,2 one you might want to try using it's second bios chip, it has dual bios. Not sure how gigabyte implements this but look in the manual, it's probably a switch on your mobo. Just an idea to try. Other than that I have no idea at all what you or Chicano missed.

 

[tsunme]

I was reading it and the dual bios is just for 3tb hdd support i think.

 

[Chicano]

The dual bios should automatically repair the main and commonly used bios chip, at least on Gigabyte motherboards.

 

[tsunme]

Would either of you know what this error means that I'm getting on my tester. Its error 53 and its description is "Initialize Time Value 40h: Bios Area"

 

[tsunme]

So I just came across this. I decided to go back and do some more memtest'ing and I noticed that I 1 error on test 7. So I decided to test the individual modules to see which had the errors. Both past a full test without any errors, so I thought, hmm must be that ram slot then. So I decided to put them in the other dual channel slots and then run it again. Same test gave me an error. So I'm thinking that somehow, dual channel is giving me errors with my ram.

 

[Chicano]

So I just came across this. I decided to go back and do some more memtest'ing and I noticed that I 1 error on test 7. So I decided to test the individual modules to see which had the errors. Both past a full test without any errors, so I thought, hmm must be that ram slot then. So I decided to put them in the other dual channel slots and then run it again. Same test gave me an error. So I'm thinking that somehow, dual channel is giving me errors with my ram.

If both modules passed the single channel test on all 4 RAM slots... and not in dual channel,... if both RAM modules are the same model and speed, even from a kit,.. It's possible some chip... (the memory controller hub) is causing the "2 beeps = Memory Parity error" . The error result from the post tester ("Initialize Time Value 40h: Bios Area") may be a result of the same issue.

 

[tsunme]

The 2 beep problem is long since gone. That hasn't happened since I went to my old motherboard. The only thing thats been happening is the freezing.

 

[Chicano]

Well, if it's not the mobo, it has to be the RAM, RAM socket, maybe only dust in the socket... a very small amount can cause memory errors.

You should try finding what the "Initialize Time Value 40h: Bios Area" exactly means... that can probably be answered by experts on BIOS language, post codes, etc.

Search: "bios code forum"
https://www.google.com/?gfe_rd=cr&ei=eNUEVIujJ8KS8QeW0YH4AQ&gws_rd=ssl#q=bios+forum+support

Search: "bios post code forum"
https://www.google.com/?gfe_rd=cr&ei=eNUEVIujJ8KS8QeW0YH4AQ&gws_rd=ssl#q=bios+post+code+forum+