Sign in with
Sign up | Sign in
Your question
Solved

New CPU; Blue screen stop code error 124 & 101

Tags:
  • Blue Screen
  • CPUs
  • Hand
Last response: in CPUs
Share
August 1, 2014 3:21:51 AM

Hi, I have bought a second-hand fx-6300 and have come across some problems which have baffled me. I have upgraded from a Athlon II x3 455, of which I had no problems with the existing components.

I have a ASUS m5a78l-m lx motherboard which should support this processor & have updated it to the latest BIOS. I have now flashed to the earliest BIOS version which supports the fx-6300.

Shortly after booting up into desktop, I get blue screen errors of either stop code 101 or 124.
However, after disabling two cores in the BIOS, I have no issues with it at all - It works perfectly. It does not matter which two I disable.

Additionally, the CPU works fine with six cores in safe mode, and was fine for a hour long stress test in prime95 where I encountered no issues.

On one occasion I managed to boot up fine for several minutes, where I ran a prime95 stress test for 12 minutes while observing HWmonitor. Package temperature did not exceed 55 degrees celsius. I received a blue screen seconds after stopping that test.

Since it works perfectly in safe mode, I would presume that this is a driver issue, but I am not sure which drivers to fiddle with.

Thanks,
Chris

More about : cpu blue screen stop code error 124 101

a b à CPUs
August 1, 2014 3:54:50 AM

You might need to reinstall windows after a change of your cpu.
m
0
l
August 10, 2014 10:31:51 AM

So - My new HDD finally arrived and I installed fresh copy of windows 7 on it, still getting blue screens when all cores are enabled.
m
0
l
Related resources

Best solution

a b à CPUs
August 10, 2014 10:53:03 AM

Mh, I'm not too familiar with AMD cpu's, but on haswell, those errors are often related to voltage issues.
Share
August 10, 2014 11:00:28 AM

Mm, it does seem to be a power issue, since I turned the clock speed down to 1.4ghz, and it hasn't bluescreened yet,so if this remains stable, i'll see if I can increase the voltage bit by bit until it stops blue screening @ 3.5ghz.

Not sure why it wouldn't blue screen in safe mode if its a voltage issue?
m
0
l
a b à CPUs
August 10, 2014 11:19:01 AM

What PSU do you have?
m
0
l
a b à CPUs
August 10, 2014 11:19:50 AM

on windows the bugcheck is called directly by the CPU. Most often because of the memory controller detecting a Cache memory error.
one of the bugcheck can be cause because of a Hung core.

These can be caused by overclocking, overheating, incorrect voltages and clock frequencies applied to the CPU.

Basically errors not detected by the memory controller result in the CPU core crashing and windows detects the hung core and bugchecks.
errors detected by the CPU memory controller causes the CPU to call the other bugcheck.

(also check for heating issues, thermal paste and fan)
m
0
l
August 10, 2014 11:35:55 AM

DubbleClick said:
What PSU do you have?


I have a vp450p - a 450W Antec PSU.
I'm sure its not an issue with this - everything works fine with only 4 cores and a r9 270x, which is a 180W GPU, while gaming.



m
0
l
a b à CPUs
August 10, 2014 12:05:25 PM

you can use the windows debugger command
!errrec on the address pointed to in the bugcheck info
and it will dump the info that the CPU called the bugcheck for.
Sometimes if it is always the same memory bank, you can have a bad core or cache bank.
it it shows different banks on each bugcheck, it is often a incorrect voltage applied to the CPU.
(bios info incorrect)

also, make sure you have your chipset updateds installed on windows. They will fix known bugs in the CPU electronics.

Chris5 said:
DubbleClick said:
What PSU do you have?


I have a vp450p - a 450W Antec PSU.
I'm sure its not an issue with this - everything works fine with only 4 cores and a r9 270x, which is a 180W GPU, while gaming.





m
0
l
a b à CPUs
August 10, 2014 12:50:32 PM

450W is might get problems with the 8350 and a 270x. Try it with a very low consumption GPU (like 15W). If the error still persists, check your BIOS and update it to the lastest version. If that doesn't help, play with voltages. Else I have no idea.
m
0
l
August 10, 2014 1:38:58 PM

Seems it was the voltage, I bumped it up to 1.37V and had no blue screens as of yet, can probably drop it down and see how it goes since I bumped it up significantly - still within safe levels though.

Thanks for your help!
m
0
l
a b à CPUs
August 10, 2014 1:42:43 PM

Glad I could help you.
m
0
l
!