Windows 10: Windows 10 crashes when gaming, caused by hal.dll and ntoskrnl.exe?

Hi.
I'm facing huge issues when trying to play FIFA 18. Game crashes almost every time when playing. Sometimes in 10 minutes or sometimes in 30 minutes. Computer freezes totally and after a while it restarts. After restart I've used WhoCrashed to inspect what happened. I'm using latest windows build(1809) and all drivers are up to date. Memory modules should be ok, or at least they've passed memtest fully.

System specs:


System Information report written at: 10/10/18 20:44:13
System Name: WINDMILL
System summary

OS Name Microsoft Windows 10 Pro
Version 10.0.17763 Build 17763
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name WINDMILL
System Manufacturer System manufacturer
System Model System Product Name
System Type x64-based PC
System SKU SKU
Processor Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz, 3696 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 1002, 02/07/2018
SMBIOS Version 3.0
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Product ROG STRIX Z370-F GAMING
BaseBoard Version Rev X.0x
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale Finland
Hardware Abstraction Layer Version = "10.0.17763.1"
Username WINDMILL\ville
Time Zone FLE Summer Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.9 GB
Available Physical Memory 12.8 GB
Total Virtual Memory 20.6 GB
Available Virtual Memory 15.5 GB
Page File Space 4.69 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualisation-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not InstantGo, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualisation Enabled in Firmware No
Hyper-V - Data Execution Protection Yes

[Display]

Item Value
Name NVIDIA GeForce GTX 1080 Ti
PNP Device ID PCI\VEN_10DE&DEV_1B06&SUBSYS_85E41043&REV_A1\4&2D78AB8F&0&0008
Adapter Type GeForce GTX 1080 Ti, NVIDIA compatible
Adapter Description NVIDIA GeForce GTX 1080 Ti
Adapter RAM (1,048,576) bytes
Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_54bd1f10ac116cd5\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_54bd1f10ac116cd5\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_54bd1f10ac116cd5\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_54bd1f10ac116cd5\nvldumdx.dll
Driver Version 25.21.14.1616
INF File oem1.inf (Section108 section)
Colour Planes Not Available
Colour Table Entries 4294967296
Resolution 2560 x 1440 x 143 hertz
Bits/Pixel 32
Memory Address 0xF6000000-0xF6FFFFFF
Memory Address 0xE0000000-0xEFFFFFFF
Memory Address 0xF0000000-0xF1FFFFFF
I/O Port 0x0000E000-0x0000E07F
IRQ Channel IRQ 16
I/O Port 0x000003B0-0x000003BB
I/O Port 0x000003C0-0x000003DF
Memory Address 0xA0000-0xBFFFF
Driver c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_54bd1f10ac116cd5\nvlddmkm.sys (25.21.14.1616, 19.65 MB (20,605,496 bytes), 09/10/2018 17:46)



One WhoCrashed report:

On Wed 10/10/2018 19:39:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\101018-4828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B0F30)
Bugcheck code: 0x1A (0x1233, 0xB7DE0, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred. A driver tried to map a physical memory page that was not locked. This is illegal because the contents or attributes of the page can change at any time. This is a bug in the code that made the mapping call.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 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.


Help, pls.

:)

 

WHEA_UNCORRECTABLE_ERROR 0x00000124 [hal.dll] [ntoskrnl.exe]


Hello zbook and thank you!

1). My system successfully created another dump file (usually it would hang): Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

2). I uninstalled all AMD related software and gpu drivers using Display Driver Uninstaller. I was able to reinstall just the AMD gpu driver by extracting the software package and obtaining the driver folder with 7zip.

3). I ran both sfc /scannow and dism /online /cleanup-image /restorehealth. No errors found on either scan. I could not post a picture because the command prompt window would immediately close after the test was finished.

4). Bios is up to date.

5). I reset Bios.

6). Prime95 would freeze my pc everytime between 20-30min into test. CPU temps topped out at 70c average.




7). Ran memtest86+ for 15 hours and made 11 passes with no errors.




8). HD Sentinel results were good:







9). chkdsk results:




10). Typical temps for my PC.

• A). Idle Temps:
  
  
  
• B). Temps after 20 min of gaming:
  
  
  

11). I will be running FurMark tonight and will monitor temps.

12). Updated my personal Ten Forums System Specs as well.

 

WHEA_UNCORRECTABLE_ERROR 0x00000124 [hal.dll] [ntoskrnl.exe]


1). New DM Log: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

2). sfc /scannow and dism /online /cleanup-image /restorehealth:




3). HD Sentinel Surface Scans:

 

HAL DLLs error on XP

' Load needed DLLs for HAL '

http://www.annoyances.org/exec/forum/winxp/t1138501952

Bad ram was the problem.