Can AMD Northbridge cause BSOD 124

[powerpurple]

So I was getting BSOD from past weeks. I don't the reason behind it, but today I saw a note was created of BSOD 124 which states that

Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 1/3/2016 11:01:38 PM
Event ID: 20
Task Category: None
Level: Error
Keywords:
User: LOCAL SERVICE
Computer: Circle
Description:
A fatal hardware error has occurred.

Component: AMD Northbridge
Error Source: Machine Check Exception
Error Type: HyperTransport Watchdog Timeout Error
Processor APIC ID: 0

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>20</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2016-01-04T07:01:38.388681500Z" />
<EventRecordID>3977</EventRecordID>
<Correlation ActivityID="{E81C1D5B-E0FD-4993-BA94-43F4A08CB62C}" />
<Execution ProcessID="1284" ThreadID="2296" />
<Channel>System</Channel>
<Computer>Circle</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="ErrorSource">3</Data>
<Data Name="ApicId">0</Data>
<Data Name="MCABank">4</Data>
<Data Name="MciStat">0xfe00000000070f0f</Data>
<Data Name="MciAddr">0xfb000000</Data>
<Data Name="MciMisc">0xc00a0fff01000000</Data>
<Data Name="ErrorType">7</Data>
<Data Name="Length">928</Data>
<Data Name="RawData">435045521002FFFFFFFF03000100000002000000A00300000D010700040110140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB03181CB0BD46D10102000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000080100000102000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002040000030000200F60000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000200F6000000804000B32983EFFFB8B170000000000000000000000000000000000000000000000000000000000000000B3F8F31CB1C5A249AA595EEF92FFA63C03000000000000009E07C0E607000000000000FB000000000000000000000000000000000000000000000000000000000100000002000000585CA9B2BD46D1010000000000000000000000000000000000000000040000000F0F0700000000FE000000FB0000000000000001FF0F0AC00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 1/3/2016 11:01:25 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Circle
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe001867fb8f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\010316-14125-01.dmp. Report Id: 010316-14125-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-01-04T07:01:25.000000000Z" />
<EventRecordID>3972</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>Circle</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x00000124 (0x0000000000000000, 0xffffe001867fb8f8, 0x0000000000000000, 0x0000000000000000)</Data>
<Data Name="param2">C:\Windows\Minidump\010316-14125-01.dmp</Data>
<Data Name="param3">010316-14125-01</Data>
</EventData>
</Event>

So I actually want to confirm that AMD Northbridge can cause such thing.
Except the CPU 1year old, Motherboard and GPU are just 2 Months old.
" http://fs1.d-h.st/view/naGY/00208/cpuid3.png ">>>>> SPECS
" http://fs1.d-h.st/view/c90m/00208/case1.png " >>>>> TEMPS
PSU : iBall Marathon 500W Peak
In the screen show you can see the specs,
I tried Updating my BIOS but it last for 2 days safely. After 2 days I was getting BSOD 124 again.
Please help me to slove the BSOD 124 problem

 

[pug_s]

I would try to update the system devices drivers. You might also want to make sure that you are not overclocking your computer. Here's a thread on someone who has the similiar situation as yours as your CPU might be overheating and causing this problem.

http://www.techsupportforum.com/forums/f299/solved-windows-7-random-restarts-and-the-odd-bsod-598152.html

 

[johnbl]

error is often caused by hardware issues, (voltage fluctuations, incorrect overclocking, overheating,...)

the memory dump contains some info that will help figure out the problem.
Mostly the system up timer, see how long the windows thinks it has been booted.
if it is under 15 seconds your CPU reset. if it is over 15 mins, you have a overheating problem (in general)

------
yes

a error from any chip directly connected to the CPU can lead the CPU to shutdown the machine with a bugcheck 0x124.

for example a overclocked external memory controller that overheats and produces a error.

 

[powerpurple]

yes

a error from any chip directly connected to the CPU can lead the CPU to shutdown the machine with a bugcheck 0x124.

for example a overclocked external memory controller that overheats and produces a error.

What should i do now. Replace the Motherboard? What do you think seeing the error report

 

[johnbl]

reset the BIOS to defaults, remove overclocking drivers, confirm the various fans are working correctly. Make sure your GPU is not using too much power.

put the memory dump on a server and post a link, I can check the system up timer for you.

yes

a error from any chip directly connected to the CPU can lead the CPU to shutdown the machine with a bugcheck 0x124.

for example a overclocked external memory controller that overheats and produces a error.

What should i do now. Replace the Motherboard? What do you think seeing the error report

 

[powerpurple]

I would try to update the system devices drivers. You might also want to make sure that you are not overclocking your computer. Here's a thread on someone who has the similiar situation as yours as your CPU might be overheating and causing this problem.

http://www.techsupportforum.com/forums/f299/solved-windows-7-random-restarts-and-the-odd-bsod-598152.html

Thanks for the reply.
Will try, the best I could do now.
The information I got from the link is updating drivers and cleaning the heatsink and reapply the thermal paste.
Drives are Up-to date running Windows 10
Cleaning the heatsink will be done soon

 

[johnbl]

- the only drivers that could cause this would be overclocking drivers.
- new paste assumes this is a overheating issue of the actual CPU.

the system up timer in the memory dump may save time.
IE did the machine reboot and you should be looking for a electrical problem. It is very common for a GPU to pull too much
power and the CPU to be reset, then the power supply lets the CPU start before the power is stable, this causes the CPU to get
cache memory errors and it calls a bugcheck 0x124. The real problem is why the CPU reset not the bugcheck because the PSU
has a hard wired power ok signal.

 

[powerpurple]

Minidump Files http://www.datafilehost.com/get.php?file=ee174ec0

 

[powerpurple]

- the only drivers that could cause this would be overclocking drivers.
- new paste assumes this is a overheating issue of the actual CPU.

the system up timer in the memory dump may save time.
IE did the machine reboot and you should be looking for a electrical problem. It is very common for a GPU to pull too much
power and the CPU to be reset, then the power supply lets the CPU start before the power is stable, this causes the CPU to get
cache memory errors and it calls a bugcheck 0x124. The real problem is why the CPU reset not the bugcheck because the PSU
has a hard wired power ok signal.

The CPU boots within seconds after the bluescreen.
I had already tried resetting BIOS it helped me for 2 days but it started again.
The Maxximum Temperature I had Noticed is
CPU Core : 60 C
GPU : 52 C
TMPIN 1: 34 C
TMPIN 2: 45 C
TMPIN 3: 70 C <<<<<< is this the Northbridge Temp?
All temperature are recorded by H/W Monitor


Minidump Files http://www.datafilehost.com/get.php?file=ee174ec0

 

[johnbl]

I don't see any overclock driver, and only one really old driver
MiniTool Partition Wizard
pwdrvio.sys Mon Jun 15 18:43:45 2009

there was only a partial debug dump and I could not read your BIOS info to see if the BIOS was doing overclocking.


System Uptime: 0 days 0:00:03.892

your system was up for 3 seconds, most likely your CPU was reset and your machine rebooted while the power was not stable.

Minidump Files http://www.datafilehost.com/d/ee174ec0

 

[johnbl]

I looked at 4 of the memory dumps, each showed a system up time under 4 seconds. your cpu was reset and restarted when the power was unstable


i would update the BIOS to clear the settings.
I would check the power to the GPU, check the power connections from the PSU to the GPU. Make sure the GPU fans
are working. confirm the GPU is getting proper power from your power supply. Remove any overclock to the GPU.

 

[powerpurple]

I looked at 4 of the memory dumps, each showed a system up time under 4 seconds. your cpu was reset and restarted when the power was unstable


i would update the BIOS to clear the settings.
I would check the power to the GPU, check the power connections from the PSU to the GPU. Make sure the GPU fans
are working. confirm the GPU is getting proper power from your power supply. Remove any overclock to the GPU.

http://postimg.org/image/v7l00te77/ < Check this screenshot
On Idle I'm slightly or equal to the minimum power consumption

 

[powerpurple]

System Information .NFO file >http://www.datafilehost.com/d/33292152