Your question

New build, Gigabyte GA-990FXA-UD3 and AMD 8320fx Issues

  • Unlock
  • CPUs
  • AMD
Last response: in Off-Topic / General Discussion
September 10, 2013 5:58:31 PM

Alright, So after a week of 3 new motherboards and 2 new cpus, I have decided to finally ask the gurus for help. My issue and has been since day 1 of this machine is that My comp freezes up after event 19 errors in the event viewer. I have done some research and heard that I have to enable the am3+ compatiablity but the drivers that I have downloaded from Gigabytes site is not compatible with windows 7 64 bit (which is legit!) I am at a lost right now... and all I want to do is get back on to ffxiv and join my friends smashing ladybugs and squirrels, any help will be greatly appreciated.

Also I have been running the computer in safe mode with no issues for over an hour, my mobo is rev 3.0, and I am rocking 8gbs of ram with an sli with 2x asus 660 gti?? Gtx??? lol... dont know off the top of my head... lol

More about : build gigabyte 990fxa ud3 amd 8320fx issues

a c 242 à CPUs
a b À AMD
September 10, 2013 6:04:32 PM

Did u attempt to use only a single gpu, a single stick of ram? and do the normal troubleshooting for bad hardware? also could be a hdd, as i have a hdd made all my games corrupt with missing files.

What is event 19 error coming from? ur board doesnt have the led display so is the error a bsod or wat?
Related resources
Can't find your answer ? Ask !
September 10, 2013 6:08:16 PM

Yeah, I did the typical KISS, (Keep it Simple, Stupid), and everything seemed to work out, the error is from Windows event error log,

[ Name] Microsoft-Windows-WHEA-Logger
[ Guid] {C26C4F3C-3F66-4E99-8F8A-39405CFED220}

EventID 19

Version 0

Level 3

Task 0

Opcode 0

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2013-09-11T14:51:58.728036700Z

EventRecordID 767

- Correlation

[ ActivityID] {9CB23C1B-CEFD-435C-A2C2-4291B00B07E1}

- Execution

[ ProcessID] 1444
[ ThreadID] 2004

Channel System

Computer watts-PC

- Security

[ UserID] S-1-5-19

- EventData

ErrorSource 1
ApicId 0
MCABank 2
MciStat 0xdc2340500010010a
MciAddr 0x12d00
MciMisc 0xc00a0fff00000000
ErrorType 9
TransactionType 2
Participation 256
RequestType 0
MemorIO 256
MemHierarchyLvl 2
Timeout 256
OperationType 256
Channel 256
Length 928
RawData 435045521002FFFFFFFF03000200000002000000A00300000F330E000B090D140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F890C81B4638FEAECE0100000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000800000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000098020000080100000102000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000200000000000000000000000000000000000000000000007F010000000000000002010000020000200F60000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000200F6000000808000B329836FFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F00822000000000002D01000000000000000000000000000000000000000000000000000000000001000000020000008100C55DFEAECE010000000000000000000000000000000000000000020000000A011000504023DC002D01000000000000000000FF0F0AC00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

Then hangs and does not crash, but nothing short from flipping the psu power toggle will restart it.
a c 306 à CPUs
a c 136 À AMD
September 10, 2013 6:10:22 PM

sounds like high temps, bad ram or a bad psu... first check the temps, an fx cpu shouldn't be breaking 65C. take the side of your case off and stick a room fan in the openning, see if you get the freeze ups. if you don't then you have a temp issue.

i'd play with the ram next. take out one stick and see if the problem comes back. if it doesn't then the problem is the 2nd stick of ram. if it does, then swap ram and see what happens. it's possible it's 2 bad sticks of ram, but unlikely.

next i'd check the psu. try it with a different psu and see if the problem goes away.

September 10, 2013 6:12:51 PM

Oh totally forgot my PSU is an XFX 650 watt XXX edition, I have tried the psu in another system and worked just fine. I have read that Gigabyte doesnt come am3+ installed, if this is true would I not be able to see the processor in my device manager?

Best solution

a b à CPUs
September 10, 2013 6:15:10 PM

It's most likely RAM but could also be very bad airflow resulting in the CPU getting too hot and starting to cause exceptions. Run Memtest and then try operating the system with one stick at a time and see what happens.
a c 306 à CPUs
a c 136 À AMD
September 10, 2013 6:18:05 PM

michaelwattsphd said:
Oh totally forgot my PSU is an XFX 650 watt XXX edition, I have tried the psu in another system and worked just fine. I have read that Gigabyte doesnt come am3+ installed, if this is true would I not be able to see the processor in my device manager?

that bolded part doesn't read right.

The GA-990FXA-UD3 was MADE for the fx lineup of chips. It IS an AM3+ motherboard. there is no incompatibility between the motherboard and chip. your problem is ram, temps or psu. just because the psu works on another pc, doesn't mean it will work with yours. try another psu in this computer before ruling the psu out as a cause.
a c 1208 à CPUs
a c 508 À AMD
September 10, 2013 6:26:46 PM

As stated above most likely it is your ram. Event ID 19 has to do with CPU but is most likely created with bad ram it is valid for win 7 as well.
April 20, 2014 9:00:30 PM

did you ever figure this problem out?

Tom’s guide in the world
  • Germany
  • France
  • Italy
  • Ireland
  • UK
Follow Tom’s guide
Subscribe to our newsletter
  • add to twitter
  • add to facebook
  • ajouter un flux RSS