BSOD seemingly caused by hardware fault

Hi Guys,

Been battling with a BSOD for a while that according to blue screen viewer is being caused by hal.dll. Traced this to mean some sort of hardware error so have tried cleaning out PC to eliminate and heat issues and run memory tests a couple of times which have always come back fine.

It doesnt seem to be caused by me doing anything in particular and seems to happen fairly randomly, often a few times in an hour and then run fine for a while.

My next plan was to do a BIOS update but figured I should check in and see if I was missing anything obvious before hand (plus to make sure I was applying the right update!) Could potentially do with some driver updates if that might be the cause?

The dump files should be attached.

Any help would be great, thanks!

axe0 said:

All dumps are similar, a read error with core 3.
Have BSOD occured from the beginning?

Code:

===============================================================================
Common Platform Error Record @ ffffc00bb5fe2028
-------------------------------------------------------------------------------
Record Id     : 01d29b6c0319a61f
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/13/2017 19:23:17 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffc00bb5fe20a8
Section       @ ffffc00bb5fe2180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Data Read
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000100f43
Processor ID  : 0x0000000000000003

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffc00bb5fe20f0
Section       @ ffffc00bb5fe2240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000003
CPU Id        : 43 0f 10 00 00 08 04 03 - 09 20 80 00 ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffffc00bb5fe2240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffc00bb5fe2138
Section       @ ffffc00bb5fe22c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL1_DRD_ERR (Proc 3 Bank 0)
  Status      : 0xb633200062000135
  Address     : 0x00000001f4185a00
  Misc.       : 0x0000000000000000

I want to say no, but its a 6 year old build(with a few changes but same cpu) so difficult to remember.

Definitely had a bsod problem for a long while, with varying severity. Usually, when it got bad I could clean out my pc and it would fix it so I have always just attributed it to heat.

Could be overheating:

Diagnostic Test

 CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

Hi Shuff,

As BSODHunter stated this could be an overheating issue so I recommend running prime95 and reporting your temps.

I would also recommend resetting your Cmos and updating your BIOS.

BSODHunter said:

Could be overheating:

Diagnostic Test

 CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

Crashed after about 30 secs, HWMonitor said it was at 67oC. Have seen it at 71 when streaming video and playing games.

axe0 said:

A couple of questions:
What is your case, PSU and cooler?
When was the last time that you replaced the thermal paste?
Have you in those years kept an eye on the temps of the CPU?
What changes have you made?

Case - Cooler Master: Scout

PSU - Cant remember exactly but its 700W cooler master psu that came with case

CPU Cooler - ARCTIC Freezer 7 Pro Rev 2 - 150 Watt Multicompatible Low Noise CPU Cooler for AMD and Intel Sockets: Amazon.co.uk: Computers & Accessories

Last time I replace thermal paste was when I bought the heat sink, which was apparantly 2014....

Since the pc was first built - new heat sink, new gpu, new HDD and new SSD.

Have tried to keep an eye on it and it has always run hot, originally when it became too much of a problem I replaced the stock cooler with the above. More recently, now the crashes have been getting worse ive been paying more attention and seen it get over 70oC

BSODHunter said:

Could be overheating:

Diagnostic Test

 CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

Forgot to attach dump, 17/03/17 at around 6pm

DeclanT said:

Hi Shuff,

As BSODHunter stated this could be an overheating issue so I recommend running prime95 and reporting your temps.

I would also recommend resetting your Cmos and updating your BIOS.

Hi, yea have thought about doing both of those but just wanted to see if I was missing anything first. Definitley think it is a heat problem, this cpu has always run a little hot (IIRC it is stock over clocked (AMD Phenom II X4 980 3.7ghz))