BSOD caused by hal.dll ntoskrnl.exe and atikmdag.sys

Toggle sidebar Toggle sidebar
D

duckmyaimsux

Prominent
Feb 12, 2018
3
0
510
Hello, I'm making a thread because I've had a problem with my PC randomly restarting for 2 years now, without me knowing why.
I suspected it was overheating for a while, then bad hardware, and now i found out I'm getting BSODs.

I've sent my pc on warrenty but they said they weren't having any restarts when they plugged their system in, but I'm pretty sure they just left it running without any programs that could cause anything for 5 minutes and called it a day...

After playing some games like CS:GO, my pc randomly crashes (and I've had blue screen pop up only once, but every crash is there in BlueScreenView).

I've reinstalled the windows a couple of time, updated all drivers and bios, but the problem persists.

The problem with atikmdag happens once per 20ish crashes and I haven't had it since I reinstalled my bios.

PC Specs:
GPU R7 360
CPU AMD Fx 6100 6 Core 3.3GHZ
8GB "Other", 400MHz Ram
Windows 10 64bit

These are the informations I'm getting for BSODs:

021218-15109-01.dmp 2/12/2018 9:59:25 PM 0x00000124 00000000`00000000 ffffe001`f053f8f8 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+6f2ea9 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.10240.17443 (th1.170602-2340) x64 ntoskrnl.exe+6f2ea9 C:\Windows\Minidump\021218-15109-01.dmp 6 15 10240 262,144 2/12/2018 9:59:30 PM

021218-15390-01.dmp 2/12/2018 7:45:27 PM 0x00000124 00000000`00000000 ffffe001`acffd8f8 00000000`00000000 00000000`00000000 hal.dll hal.dll+246b Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 10.0.10240.16392 (th1_st1.150716-1608) x64 ntoskrnl.exe+6f2ea9 C:\Windows\Minidump\021218-15390-01.dmp 6 15 10240 262,144 2/12/2018 7:45:31 PM


Edit: After running sfx /scannow, I got "Windows Resource Protection did not find any integrity violations"
 
Solution
J
bugcheck 0x124 with parmater 1=0 means the CPU called the bugcheck the reason is stored at location
ffffe001`f053f8f8 in the memory dump. Most of the time it will be a internal cpu error detected by the cpu cache memory controller.


this error would be caused by power related source. for example, bad overclocking in bios, bad overclock applied by overclocking drivers, GPU overheating and taking too much power from the PCI/E bus causing the motherboard protection ciruits to trip and reset the CPU.
CPU overheating.

in general, blow out the dust, update the BIOS or reset it to defaults, remove any GPU or CPU overclock.
monitor temps and power supply voltages. if your GPU is overclocked, set it to the default clock rate for the...
Sort by date Sort by votes
hang-the-9

hang-the-9

Titan
Mar 25, 2010
60,387
1,081
152,940
Could be a lot of things, failing video card, bad RAM, bad power supply. You said you were suspecting it was overheating, did you actually check the reported temps with a utility like HWMonitor? Was it overheating? Or maybe it sill is.

Did you try a clean Windows setup? Do any testing of any hardware with different parts?

What is the power supply brand and model?
 
Upvote 0 Downvote
D

duckmyaimsux

Prominent
Feb 12, 2018
3
0
510
My PC just restarted, and HWMonitor is showing 50C for CPU and 44C for GPU, so I guess I'm guessing that's not the problem.

I've done a clean Windows reinstall, and I'll run some stress tests now and post the results.

My PSU is Power - LC600H-12 V2.31 - Active PFC

Edit: I've been running stress test for CPU and GPU at the same time for 30 minutes (not sure if that's enough for CPU) without a crash, and their max temps have gone up to 68C and 58C respectively.
 
Upvote 0 Downvote
D

duckmyaimsux

Prominent
Feb 12, 2018
3
0
510
I ran stress test for 7 hours while I was in college today and I didn't encounter a BSOD.

This is becoming very annoying as I don't know what else I could do apart from upgrading my parts one by one until the problem goes away...
 
Upvote 0 Downvote
hang-the-9

hang-the-9

Titan
Mar 25, 2010
60,387
1,081
152,940
With a clean Windows system I'd start with the video card or power supply as the cause, test the card in another system or another card with similar power use in yours. Power supply could be the cause, your model is not horrible but not what would be a good one.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
bugcheck 0x124 with parmater 1=0 means the CPU called the bugcheck the reason is stored at location
ffffe001`f053f8f8 in the memory dump. Most of the time it will be a internal cpu error detected by the cpu cache memory controller.


this error would be caused by power related source. for example, bad overclocking in bios, bad overclock applied by overclocking drivers, GPU overheating and taking too much power from the PCI/E bus causing the motherboard protection ciruits to trip and reset the CPU.
CPU overheating.

in general, blow out the dust, update the BIOS or reset it to defaults, remove any GPU or CPU overclock.
monitor temps and power supply voltages. if your GPU is overclocked, set it to the default clock rate for the GPU model.

You would never get this error code from external RAM if your machine was made in the last 10 years.
looking at the memory dump can help, if the system uptime is under 15 seconds then most likely the motherboard logic rebooted the CPU. Someone would have to look at the memory dump in the windows debugger. to look for common causes of this bugcheck.



 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom