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

 

[tsunme]

So I was checking one of the sites, and I found the error code written slightly different "Set time value for address 40 of BIOS" and I started looking for this and then on the same site I found 40h and it says "Floppy disk drive motor time-out". I'm not sure if thats correct (since i don't have a floppy disk drive).

 

[Chicano]

Now we seem to be getting somewhere.. You may not have a floppy drive, but you may have one enabled in the BIOS?.. floppy drive motor time-out means the BIOS waited for the motor to start and it did not. I don't think this would cause Windows freezes but who knows... anything is possible.

Check from Windows if you have the A: drive in Computer / Explorer, you may need to disable the drive letter to make sure it can't cause BIOS and/or Windows issues..
IF the system has A: drive enabled, everything about the floppy drive would have to be disabled, letter, drivers, even registry values deleted, etc. running a registry cleaner may do it... Glary Utilities or CCleaner. This may not do a thing but better make sure.

 

[tsunme]

I checked my device manager and my computer for anything related to A: or floppy drive and nothing showed up.

 

[Chicano]

What about in the BIOS, any setting on floppy drive enabled?

 

[tsunme]

From what I could see, there was no sign of floppy drive in the bios.

 

[Chicano]

And I'd suppose the motherboard doesnt even have a Floppy Disk Drive data port either?... then I don't get whey the BIOS would report a FDD motor issue. Can't recall if you have updated the BIOS? if not, you may want to do that. Also keep researchng in BIOS related websites/forums for clues.

 

[tsunme]

I do have updated bios, hasn't been a new 1 in like 2 years (only a beta one). Also, I was able to get my memory to go to its actual speed of 1866. Had to manually adjust everything for it.

 

[Chicano]

I do have updated bios, hasn't been a new 1 in like 2 years (only a beta one).

What do you mean? that you updated the BIOS 2 years ago to a beta update? and it's been that beta all along?

 

[tsunme]

NO no no. I have their stable version (f7) which was last updated 2 years ago. Their only newer one (f8) is a beta version, which, also, is 2 years old.

Also. I just noticed that the tester is giving me a different code now (code 10), which it says "Test DMA Controller 1".

 

[Chicano]

Sorry, but I couldn't make out what you meant.. guess I haven't been sleeping much lately.
The DMA Controller makes a lot of sense... but this problem isn't supposed to happen on modern Intel systems. Anyway, check in the Device manager... Right click on Computer / Manage / Device Manager / IDE ATA/ATAPI Controllers / ATA Channel 0 / right click / Properties / Advanced Settings / Enable DMA.... See if the box it's checked

 

[tsunme]

It is. (also i'm running amd)

 

[Chicano]

Yeah, I forgot it's AMD so it shouldn't be having this type of problem and much less with DMA enabled... I'm suspecting you may have a bad SATA HD connection, incorrect BIOS SATA Controller setting... lose RAM module/s, etc. Apparently something is slowing down memory access. As you can tell by the article, DMA refers to general system memory and it covers every hardware component that has memory, HD, RAM, chips, CPU, GPU, etc. But DMA Controller 1 is usually the Optical drive, DMA Controller 0 would referr to the hard drive controller, so unless the issue happens when the CD/DVD drive is running, it doesn't make any sense. And as the message was about the Floppy drive before, and it keeps changing, I'm suspecting the whole problem may be a virus is causing this. I suppose you have already scanned for every type of bug; Virus, malware/trojans, rootkits, etc.?

DMA is Direct Memory Access
http://en.wikipedia.org/wiki/Direct_memory_access

 

[tsunme]

Yes, I've scan multiple times. Usually once a week.

 

[tsunme]

Ok, so I just froze again its back to saying 53.

 

[Chicano]

Run a system self diagnosis test typing "perfmon /report" in Start / Run... if you don't have the run command enabled, see if it works from the search bar or enable the Run command from: Right click on the Taskbar / Properties / Settings / look for Run command and mark to enable it.

The results of Perfmon /Report may indicate if hardware issues are the cause.

 

[tsunme]

Ok, so I was looking in my computer, making sure things were full connected/clean. And when I was looking at the MB tester, it dawned on me that it might not be saying 53, it might E5, so I looked for it and all it says for that is "E5 - Setup Page E5", and I can't find anything on this either.

Just did the perfmon /report, and it had come with a legacy driver causing an error. Went and unintsalled it and deleted it from the registry.

 

[Chicano]

Check this PDF with description of all error codes. I could not find E5, maybe you can.
http://www.scribd.com/doc/135123622/Motherboard-Diagnostic-Card-and-Error-Codes-With-complete-Explanation

OK, something here describing E5. Quote: "E5" error is trying to report a problem with the MBR on the boot drive
http://forums.techguy.org/hardware/1015015-question-about-phoenix-award-bios.html

Restore Master Boot Record in Windows 7
http://www.sevenforums.com/tutorials/20864-mbr-restore-windows-7-master-boot-record.html
(seems a bit complicated... will look for another method)

Better try this method
http://www.inteligentcomp.com/2013/06/how-to-repair-fix-mbr-windows-7-8.html

 

[tsunme]

So would i do the fix for damaged, missing, or compressed?

 

[Chicano]

For damaged MBR.

The MBR is code located in the first sector of the HD that has instructions on the boot information. I don't see how it would cause freezes but if the BIOS reports a problem, it has to be repaired.

Master boot record
http://en.wikipedia.org/wiki/Master_boot_record

This might describe it in better to understand language.
http://www.differencebetween.net/technology/software-technology/difference-between-mbr-and-partition-table/

Quote: "The MBR is actually a low level executable program that contains the appropriate instructions on booting the computer".. Read more: Difference Between MBR and Partition Table | Difference Between | MBR vs Partition Table http://www.differencebetween.net/technology/software-technology/difference-between-mbr-and-partition-table/#ixzz3CJnSo4fk

 

[tsunme]

Ok, well I did that yesterday and I still froze today. Could it possibly be a bad cpu core or something like that? I remember trying to run Prime95 a while back and it would freeze on me and I tried it again today and it froze again. I did see it saying a core failed.

 

[Chicano]

Could be.. the only way to know is trying another AM3+ or AM3.. maybe even a AM2+ CPU depending on the mobo specifications

Well, specifications info says only AM3+ CPU but I'd bet at least a AM3 would work on your mobo.

 

[tsunme]

I do have an old amd Phenom II x2 550, you think that might work?

 

[Chicano]

Right... the Phenom should work. And help diagnose if the FX-8350 is causing the lockups.

 

[tsunme]

Ok, so I put it in and I got past the post screen, but everytime it tried to go past the windows screen it would restart.

 

[Chicano]

Did you refresh the thermal paste?... If it posts it's working, whatever is causing the restarts is related to Windows, overheating, a BIOS reset would't hurt. If nothing after a BIOS reset and it's not overheating, see if a Windows startup repair helps.