Hi Kiko4564 welcome to SF
.
The bugchecks are not very recent so they don't portray the very current condition of the system.
View attachment 302184
What I feel the need to debunk is the
myth that ntoskrnl or hal.dll are the source of
the crashes which they are definitely not. They are often
being blamed for the problems
caused by a different culprit because they are such centric components of Windows
(to put the simplest way possible).
Now the latest bugcheck is a
0x124 which is a hardware fault so I would like you to run some tests.
Code:
BugCheck 124, {0, fffffa8006a48038, b0800000, 60151}
Probably caused by : AuthenticAMD
---------
0: kd> !errrec fffffa8006a48038\
===============================================================================
Common Platform Error Record @ fffffa8006a48038
-------------------------------------------------------------------------------
Record Id : 01ceedfa61d19888
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 12/9/2013 2:26:23 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa8006a480b8
Section @ fffffa8006a48190
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
[COLOR=Red]Error Type : Cache error
Operation : Instruction Execute
[/COLOR] Flags : 0x00
Level : 1
CPU Version : 0x0000000000610f01
Processor ID : 0x0000000000000000
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa8006a48148
Section @ fffffa8006a482d0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
[COLOR=Red]Error : ICACHEL1_IRD_ERR (Proc 0 Bank 1)[/COLOR]
Status : 0xb080000000060151
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. -
H2SO4
The generic nature of the
0x124 (Arg1=0) stop code means we would have to take
the trail & error approach.
Do you have any spare parts (or another PC) to test with?
The usual suspect of this kind of BCCode is the CPU but it's often not the the case which is why we need
to test other components to rule them out as the cause.
How old are your components?
:ar:
Test for thermals and stability:
- Download HWinfo and post a Screenshot of the sensors window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
- Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).
Note
It is not mandatory to run both tests simultaneously, although possible as long as the temperatures are under constant monitoring.
Good places to read more:
rb:Start → Run → type MSINFO32 then hit Enter.