Random BSOD - hal dll 12a3b ntoskrnl exe+18dc33

I get a random bsod, most times when the computer is idle.

bluescreenview shows it getting hal dll 12a3b ntoskrnl exe+18dc33 errors

Things i have tried and still getting blue screens
-Put one RAM stick at a time, in the different slots
-I dl'ed Speccy and my temps are in the 40s
-Cleared CMOS
-Updated my BIOS software to latest
-Updated my SSD to latest hardware

Build
CPU: Intel Pentium G3258 3.2GHz Dual-Core Processor
CPU Cooler: Arctic Cooling Freezer 7 Pro Rev.2 45.0 CFM Fluid Dynamic Bearing CPU Cooler
Motherboard: Gigabyte GA-Z97-HD3 ATX LGA1150 Motherboard
Memory: Corsair Vengeance 8GB (2 x 4GB) DDR3-1600 Memory
Storage: Crucial MX100 128GB 2.5" Solid State Drive
Storage: Western Digital Caviar Blue 1TB 3.5" 7200RPM Internal Hard Drive
Video Card: MSI Radeon R9 290 4GB TWIN FROZR Video Card
Case: Corsair SPEC-03 Red ATX Mid Tower Case
Power Supply: Enermax 600W 80+ Platinum Certified Semi-Modular ATX Power Supply
DRW-24B1ST/BLK/B/AS

Hey there! That's an awesome PC you've got there. Anyways lets get to troubleshooting. Also never use BlueScreenView, it's always inaccurate.

Code:

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Hmm, run IntelBurnTest. If the temps go to far then shut IntelBurnTest down. This might be two things, the CPU is failing or the cooler is bad.

Thank you for the reply!

I am running the intelburntest for stress level standard - 1024 mb - 10 times to run

looking at Speccy, the CPU got as high as 51 degrees that I noticed, but stayed in the high 40s most the time.

Going to run the test in High next.

running intelburntest for stress level high - 2048 mb - 10 times

watching speccy, the CPU sat in the low 50s for most the time, the highest being 53 degrees

i will continue more testing this afternoon.

Hmm, i'm almost certain that it's the CPU. The CPU is failing but not heavy, but it is still causing BSODs. I would say go to replace the CPU.

whats your opinion on prime95? i started running it last night and did get an error with one of the watchers, but didnt investigate since i closed it and ran intelburntest per your suggestion

This is a CPU problem. I would say replace the CPU.

shall i marked this resolved as i get another cpu? it might take a few weeks

No, buy another CPU and report back.

I havent gotten a blue screen in about a week. Im going to close this for now