• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

CPU, Ram or Motherboard Going Bad?

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Stoneysilence

Registered
Joined
Sep 22, 2015
I have a slight OC on my system, I haven't had much time to really push it. I posted about it here: http://www.overclockers.com/forums/showthread.php/764490-Newb-to-OC-ing-and-Watercooling

So anyway, I settled at a low OC of 4.5ghz and have been running that fine without issue until this week. All of a sudden I am getting Memory read errors and BSOD's complaining about Thread's, Memory and other general errors. When I look up the errors after they occur they all point to CPU or RAM issues.

Also in my Event Viewer I got a few of these starting to pop up:
Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 12/12/2015 11:18:52 AM
Event ID: 19
Task Category: None
Level: Warning
Keywords:
User: LOCAL SERVICE
Computer: *******
Description:
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Cache Hierarchy Error
Processor APIC ID: 1

The details view of this entry contains further information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{C26C4F3C-3F66-4E99-8F8A-39405CFED220}" />
<EventID>19</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2015-12-12T19:18:52.186855200Z" />
<EventRecordID>2808</EventRecordID>
<Correlation ActivityID="{291D1600-995B-44C7-92FD-1F18405B5A0F}" />
<Execution ProcessID="1428" ThreadID="1036" />
<Channel>System</Channel>
<Computer>Eric-Desktop</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="ErrorSource">1</Data>
<Data Name="ApicId">1</Data>
<Data Name="MCABank">2</Data>
<Data Name="MciStat">0xdc25405000040136</Data>
<Data Name="MciAddr">0x2c9112078</Data>
<Data Name="MciMisc">0xc00a0fff00000000</Data>
<Data Name="ErrorType">9</Data>
<Data Name="TransactionType">1</Data>
<Data Name="Participation">256</Data>
<Data Name="RequestType">3</Data>
<Data Name="MemorIO">256</Data>
<Data Name="MemHierarchyLvl">2</Data>
<Data Name="Timeout">256</Data>
<Data Name="OperationType">256</Data>
<Data Name="Channel">256</Data>
<Data Name="Length">928</Data>
<Data Name="RawData">435045521002FFFFFFFF03000200000002000000A0030000331213000C0C0F140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F890B20D7E3A0435D10100000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000800000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000098020000080100000102000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000200000000000000000000000000000000000000000000007F010000000000000002010100020000200F60000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000100000000000000200F6000000808010B32983EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F008D2000000000782011C9020000000000000000000000000000000000000000000000000000000100000002000000FDA10BEF1135D10101000000000000000000000000000000000000000200000036010400504025DC782011C90200000000000000FF0F0AC00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
</EventData>
</Event>

So I find it hard to believe that both the CPU and RAM would go bad at the same time. So what I am thinking is the motherboard is actually the one going out?

Event Viewer isn't giving me the exact BSOD error messages otherwise I would post those. But most of them were basically Ram issues. One was a Thread CPU issue.

I will reset my OC back to factory today and then run Memtest and Prime95 and post my results later.
 
It's probably just not stable...You left the last thread not stable (didn't follow up with us anyway).

Please cpuz screenshots of first tab, memory and SPD. Please host here at the site.
 
It's probably just not stable...You left the last thread not stable (didn't follow up with us anyway).

Please cpuz screenshots of first tab, memory and SPD. Please host here at the site.
I dropped the system to 4.5ghz and didn't have a single bsod or error since my last post until this week. Got busy with work and haven't had a lot of time to work on oc'ing again. Can a stable oc to become unstable over time? I already dropped the oc to defaults and am running prime95 right now.
 
I dropped the system to 4.5ghz and didn't have a single bsod or error since my last post until this week. Got busy with work and haven't had a lot of time to work on oc'ing again. Can a stable oc to become unstable over time? I already dropped the oc to defaults and am running prime95 right now.
Did you get the errors when overclocked or at default? If it was at 4.5 and you were overclocking using the FSB, in the previous thread you had your DDR3 1600 Mhz ram running overclocked to 1800 Mhz. Dropping the Oc back to 4.5 does not mean it's stable just because you can game on it. Pass 2 hours of prime blend at an Oc then you will not have issues. You may want to reread the previous thread, some of the best AMD overclockers in this forum gave some solid advice on how to go about Ocing the Fx.
 
Did you get the errors when overclocked or at default? If it was at 4.5 and you were overclocking using the FSB, in the previous thread you had your DDR3 1600 Mhz ram running overclocked to 1800 Mhz. Dropping the Oc back to 4.5 does not mean it's stable just because you can game on it. Pass 2 hours of prime blend at an Oc then you will not have issues. You may want to reread the previous thread, some of the best AMD overclockers in this forum gave some solid advice on how to go about Ocing the Fx.

I changed the way I OC'ed to the way they suggested I do so in that thread so the ram wasn't OC'ed (CPU multiplier). At 4.5ghz it ran 24/7 without issues running BOINC until last week.

So far back at the defaults (4ghz, everything set at Auto) Prime95 has been running since I started this thread till now without any issues. So maybe it was a OC issue...

Weird that it would be "stable" for a month or so then start showing issues. Could be that BOINC is using more ram or something differently with the current batches of work which are pushing it harder than before so the errors are starting to show up?

Thanks for the advice, will keep an eye on it. May try to bump it up to 4.5ghz again and up the voltage and run Prime some more this evening.
 
Probably not really "weird" that it would be stable for a month and then become unstable using the same overclock settings. When an overclock is marginally stable this is exactly what we usually see.
 
Probably not really "weird" that it would be stable for a month and then become unstable using the same overclock settings. When an overclock is marginally stable this is exactly what we usually see.

Gotcha. That was probably the case then (at least I hope and not hardware failure).
 
If it was hardware failure, chances are you would show the same problems at stock, and it appears you are not. :)
 
If it was hardware failure, chances are you would show the same problems at stock, and it appears you are not. :)

Here's hoping. I think the issue was my voltage was too low. I upped it and returned my OC to 4.5ghz and things were stable in Prime for over an hour. Then I bumped my OC to 4.6ghz and again ran prime for an hour and no issues. Left it at 4.6 overnight running BOINC and no issues as of yet. Will run some more Prime this evening to make sure it is stable. Temps are higher than before but within reason 48C CPU and 55C MB.
 
Back