Windows 10 crashes when i play demanding games, such as PUBG/DESTINY 2.
---------------------------------------------------------------------------------------------------------------------------Windows 10 home 64 bit (Version 1709)
GTX: 1080 (8GB) Rog Strix
CPU: i7 8700k 3,7 Ghz 6 cores
RAM: G-Skill Trident 2x8GB 3200Mhz
SSD: Samsung 960 EVO 250 GB
MOB: Z370-F
---------------------------------------------------------------------------------------------------------------------------
System Information (local)
Computer name: DESKTOP-3D1I6EF
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., ROG STRIX Z370-F GAMING
CPU: GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 17100603392 bytes total
---------------------------------------------------------------------------------------------------------------------------
PAGE_FAULT_IN_NONPAGED_AREA
IRQL_not_less_or_equal
---------------------------------------------------------------------------------------------------------------------------
Done sofar:
1.
sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth
Result: Nothing
2.
Reinstall windows 10
Result: Nothing
3.
Updating drivers:
GPU: GeForce Game Ready Driver: Version: 388.71 - 12/20/2017.
Result: Nothing
4.
Windows Memory Diagnostic:
mdched.exe
Result: Nothing
5.
Resetting overclocks
Result: Nothing
6.
Cleanmgr
Result: Nothing
7.
hdwwiz.cpl
All programs cheaked for updates.
Result: Nothing.
8.
Controlpanel - System and Security - System- System properties - Performance options - Change - (Uncheak) Atuomatically mange paging file size - Custom.
1,024 X Ram (16Gb) = 16,384 (1)
16384 X 1.5 = 24,576 (2)
Enter: 16384 into = (Inital size MB)
Enter: 24,576 into = (Mazimum size MB)
Set - Ok - Restart.
Result: Nothing
9.
Windows Update - Wrong search/troubleshot.
Result: Nothing
10.
Memtest
Result: Nothing found.
11.
---------------------------------------------------------------------------------------------------------------------------
Potentiall
1.
In resmon maximal frequency (blue) sometimes goes over 100% - 115%
2.
Samsung SSD 960 EVO 250GB
Driver date is: 2006-06-21 (10.0.16299.15)
3.
---------------------------------------------------------------------------------------------------------------------------
Error codes / Crash Dump Analysis
(WhoCrashed - 5,54)
1.
On Thu 2017-12-21 23:52:01 your computer crashed
crash dump file: C:\WINDOWS\Minidump\122117-3093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x50 (0xFFFFF38835348A49, 0x0, 0xFFFFF803EDB4D68C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
2.
On Thu 2017-12-21 23:52:01 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF38835348A49, 0x0, 0xFFFFF803EDB4D68C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
3.
On Fri 2017-12-22 21:49:47 your computer crashed
crash dump file: C:\WINDOWS\Minidump\122217-3453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8005A804F6C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
---------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------Windows 10 home 64 bit (Version 1709)
GTX: 1080 (8GB) Rog Strix
CPU: i7 8700k 3,7 Ghz 6 cores
RAM: G-Skill Trident 2x8GB 3200Mhz
SSD: Samsung 960 EVO 250 GB
MOB: Z370-F
---------------------------------------------------------------------------------------------------------------------------
System Information (local)
Computer name: DESKTOP-3D1I6EF
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., ROG STRIX Z370-F GAMING
CPU: GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 17100603392 bytes total
---------------------------------------------------------------------------------------------------------------------------
PAGE_FAULT_IN_NONPAGED_AREA
IRQL_not_less_or_equal
---------------------------------------------------------------------------------------------------------------------------
Done sofar:
1.
sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth
Result: Nothing
2.
Reinstall windows 10
Result: Nothing
3.
Updating drivers:
GPU: GeForce Game Ready Driver: Version: 388.71 - 12/20/2017.
Result: Nothing
4.
Windows Memory Diagnostic:
mdched.exe
Result: Nothing
5.
Resetting overclocks
Result: Nothing
6.
Cleanmgr
Result: Nothing
7.
hdwwiz.cpl
All programs cheaked for updates.
Result: Nothing.
8.
Controlpanel - System and Security - System- System properties - Performance options - Change - (Uncheak) Atuomatically mange paging file size - Custom.
1,024 X Ram (16Gb) = 16,384 (1)
16384 X 1.5 = 24,576 (2)
Enter: 16384 into = (Inital size MB)
Enter: 24,576 into = (Mazimum size MB)
Set - Ok - Restart.
Result: Nothing
9.
Windows Update - Wrong search/troubleshot.
Result: Nothing
10.
Memtest
Result: Nothing found.
11.
---------------------------------------------------------------------------------------------------------------------------
Potentiall
1.
In resmon maximal frequency (blue) sometimes goes over 100% - 115%
2.
Samsung SSD 960 EVO 250GB
Driver date is: 2006-06-21 (10.0.16299.15)
3.
---------------------------------------------------------------------------------------------------------------------------
Error codes / Crash Dump Analysis
(WhoCrashed - 5,54)
1.
On Thu 2017-12-21 23:52:01 your computer crashed
crash dump file: C:\WINDOWS\Minidump\122117-3093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x50 (0xFFFFF38835348A49, 0x0, 0xFFFFF803EDB4D68C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
2.
On Thu 2017-12-21 23:52:01 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF38835348A49, 0x0, 0xFFFFF803EDB4D68C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
3.
On Fri 2017-12-22 21:49:47 your computer crashed
crash dump file: C:\WINDOWS\Minidump\122217-3453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8005A804F6C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
---------------------------------------------------------------------------------------------------------------------------
Facebook
Twitter
Instagram