Blue screen while playing games

elias.lip96

Prominent
Nov 6, 2017
5
0
510
Hi

Im having an issue lately, its only been around for 2 weeks. Ive been getting blue screen and i checked my temps, they are fine. So are my drivers. I do have 2 power strips running to my pc, could this be a problem? if so, how come it wasnt a problem 4 months ago and only starting now?

Hope you can help!
 

elias.lip96

Prominent
Nov 6, 2017
5
0
510


Hi Satan-IR

These are my specs:

Intel i7-4790k @ 4.00GHz
8 GB RAM
GTX 970
250 SSD

Hope thats what u need.

The code im getting is "hal.dl"l which i read was about something with my harddrive.. but i dont get blue screen when i play League of Legends or using Adobe programs nor any other for that matter. Only CS:GO, PUBG & Fortnite.
 

Satan-IR

Splendid
Ambassador
Well I means specs like motherboard, VGA and PSU brand and model.

hal.dll is Windows component. Many things might drive Windows components and services to fault including driver conflicts.

What makes you think it's HDD related. Assuming you have HDDs as well or is it just the SSD?

If the BSODs happen under certain apps/games and not under others it makes hardware issue a little less likely.

To make sure you can run HD Tune portable or HD Sentinel and check HDD/SSD health in the S.M.A.R.T tab. Drive problems can in theory cause BSODs but when it happen only during certain games it can be driver conflict, GPU or PSU issues.

What is the brand model of PSU?

Also you can enable small memory dumps and upload the crash dump files (around 300KB) so maybe we can narrow it down what's causing the BSOD.
 

elias.lip96

Prominent
Nov 6, 2017
5
0
510


It's something i read, it could be harddrive, but now i understand its windows components..

Update: I just crashed again with another BSoD. This time it said "WHEA UNCORRECTABLE_ERROR"..

My PSU is an 'Cooler Master RS-700 acab d3, 700 W'

Could you send me a link or a guide for small memory dumps? Im not really sure how to do that.
 

elias.lip96

Prominent
Nov 6, 2017
5
0
510
Hmm, never knew, but had it for almost 2 years, how come this problem accur now? You think the PSU is getting 'old'?

Im running windows 10.

Do you think the overall experience is better with a bigger PSU?
 

elias.lip96

Prominent
Nov 6, 2017
5
0
510
Hi, i changed my RAM sticks and updated my SSD, still experiencing blue screens. Here are my report

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 27-11-2017 17:20:02 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112717-3953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x124 (0x0, 0xFFFFC2063792C028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 27-11-2017 17:12:46 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112717-3984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x124 (0x0, 0xFFFF9706E392C028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.