Question Computer crashes sporadically, either full lockup or BSOD with system service exception error

May 29, 2020
7
0
10
0
I have been battling this issue for a while now and can usually replicate the freeze if I launch hearthstone and play for roughly 5mins. Other programs are hit and miss for causing the freeze and i've been able to run memtests, 3dmark and other diagnostics with no issues. Ive fully replaced my PSU, ram, and tried new hard drives. I have also updated my drivers and reloaded windows several times.

Speccy:
Operating System
Windows 10 Home 64-bit
CPU
Intel Core i5 @ 3.70GHz 35 °C
Kaby Lake 14nm Technology
RAM
32.0GB Dual-Channel Unknown @ 1504MHz (17-18-18-36)
Motherboard
ASUSTeK COMPUTER INC. PRIME Z390-P (LGA1151) 31 °C
Graphics
Acer XB240H Aä:7(ré (1920x1080@144Hz)
ASUS VS247 (1920x1080@60Hz)
4095MB NVIDIA GeForce GTX 1070 (Gigabyte) 47 °C
Storage
931GB TOSHIBA DT01ACA100 (SATA ) 31 °C
238GB ADATA SP900 (SATA (SSD)) 39 °C
223GB Kingston SHPM2280P2H/240G (SATA (SSD)) 34 °C
465GB Western Digital WDS500G3XHC-00SJG0 (Unknown (SSD))
Optical Drives
No optical disk drives detected
Audio
NVIDIA Virtual Audio Device (Wave Extensible) (WDM)
Operating System
Windows 10 Home 64-bit
Computer type: Desktop
Installation Date: 5/28/2020 3:20:14 PM
Windows Security Center
User Account Control (UAC) Enabled
Notify level 2 - Default
Firewall Enabled
Windows Update
AutoUpdate Not configured
Windows Defender
Windows Defender Disabled
Antivirus
Windows Defender
Antivirus Disabled
Virus Signature Database Up to date
Malwarebytes
Antivirus Enabled
Virus Signature Database Up to date
.NET Frameworks installed
v4.8 Full
v4.8 Client
Internet Explorer
Version 11.264.19041.0
PowerShell
Version 5.1.19041.1
Environment Variables
USERPROFILE C:\Users\chase
SystemRoot C:\Windows
User Variables
OneDrive C:\Users\chase\OneDrive
Path C:\Users\chase\AppData\Local\Microsoft\WindowsApps
TEMP C:\Users\chase\AppData\Local\Temp
TMP C:\Users\chase\AppData\Local\Temp
Machine Variables
ComSpec C:\Windows\system32\cmd.exe
DriverData C:\Windows\System32\Drivers\DriverData
NUMBER_OF_PROCESSORS 6
OS Windows_NT
Path C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0\
C:\Windows\System32\OpenSSH\
C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common
PATHEXT .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PROCESSOR_ARCHITECTURE AMD64
PROCESSOR_IDENTIFIER Intel64 Family 6 Model 158 Stepping 12, GenuineIntel
PROCESSOR_LEVEL 6
PROCESSOR_REVISION 9e0c
PSModulePath %ProgramFiles%\WindowsPowerShell\Modules
C:\Windows\system32\WindowsPowerShell\v1.0\Modules
TEMP C:\Windows\TEMP
TMP C:\Windows\TEMP
USERNAME SYSTEM
windir C:\Windows
 
May 29, 2020
7
0
10
0
motherboard bios on latest release / PSU ???
Bios has been updated and I had a 650W corsair PSU in there and replaced it with a 550w spare to test. Issue still remains. I don think Id be over the power threshold, but correct me if im wrong. I have not added anything to my computer to increase the draw before this started happening.
 
May 29, 2020
7
0
10
0
could try https://www.resplendence.com/whocrashed might give us a clue as to what is causing it.
I tried running it after a crash and got this;

On Sun 5/31/2020 10:16:25 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x450DD)
Bugcheck code: 0x50 (0xFFFFF80069000000, 0x11, 0xFFFFF80069000000, 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.



On Sun 5/31/2020 10:16:25 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\053120-207687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x50 (0xFFFFF80069000000, 0x11, 0xFFFFF80069000000, 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.

any thoughts on why this would occur? I am not really smart on these things. From what I am reading it could be the cause of bad memory but I've replaced the memory with fresh sticks / isolated it. I dont think it would be the RAM?
 

Sohom

Reputable
Mar 6, 2017
1,194
56
5,740
188
I am not really smart on these things. From what I am reading it could be the cause of bad memory but I've replaced the memory with fresh sticks / isolated it. I dont think it would be the RAM?
Did u check the ram slots on ur motherboard...??? Bad ram slots also can cause such issues... i have seen this happen with a corrupted motherboard after random voltage fluctuations occurring in one's neighbouthood...
 
May 29, 2020
7
0
10
0
Did u check the ram slots on ur motherboard...??? Bad ram slots also can cause such issues... i have seen this happen with a corrupted motherboard after random voltage fluctuations occurring in one's neighbouthood...
How would i verify the integrity of the slots themselves? I moved my RAM to the different slots and tested. Are you saying visually check them? I just ran one more memory diagnostic and it returned with no errors.
 

Sohom

Reputable
Mar 6, 2017
1,194
56
5,740
188
How would i verify the integrity of the slots themselves? I moved my RAM to the different slots and tested. Are you saying visually check them? I just ran one more memory diagnostic and it returned with no errors.
Try with a single stick of ram on each slots and check , check every stick and slots one by one...
 

ASK THE COMMUNITY

TRENDING THREADS