Question Pc crashes randomly. Please help.

Apr 3, 2020
3
0
10
Here is whats happening to my pc. BSoD, lockup/freezing then monitor turns off but pc fans and lights are still on.
I first encountered it when i just tried to stream while playing. It didn't bother me. I just thought it might be my slight overclocked wasnt stable so i just revert my bios settings to default.
But after that my pc still keeps crashing at random moments.
This are the moments when my pc crash.
  • while playing games. (this happened in league of legends, call of duty warzone, world war z, lurk in the dark: prologue (this was the game i was streaming when it first crashed) and bayoneta these are the games that i am currently playing )
  • when a game is done and i return to lobby/client (this happened in league of legends and world war z)
  • while playing a video in youtube, and sometimes just clicking play or resuming a video.
  • sometimes it crashes when i just click on something
These are the thing i tried so far.
  • reseating everything on the mobo except for my cpu
  • using ddu and installing previous drivers
  • reinstalling windows without wiping my D: drive (only wiped my C: drive)
  • reinstalling an older version of window with the iso file i used last year because i only encountered this after updating to 1909
  • moving ram stick to other slots
  • moving hdd sata cable to other slots
  • memtest 86 finished it without errors
  • running furmark for 15mins ( i know its a short time but i saw someone said if it can run furmark after 10mins its fine)
  • tried updating mobo bios and reverting to a previous version
PC SPECS: if it helps
Mobo: Asrock AB350m PRO 4 currently on bios version 5.80 (tried bios versions 5.90 and 6.00)
CPU: Ryzen 5 2600
GPU: Gigabyte gtx 1070 8gb
RAM: 8gbx1 Hyper x 2400mhz
HDD: 1TB Seagate Barracuda

will link dump files after i upload

edit: while i'm still uploading dump file
1.
Problem signature
Problem Event Name: BlueScreen
Code: 1e
Parameter 1: ffffffffc0000005
Parameter 2: fffff8025de9412c
Parameter 3: 0
Parameter 4: ffffffffffffffff
OS version: 10_0_18362
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.18362.2.0.0.256.48
Locale ID: 13321

2.
- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff8025de9412c, 0x0000000000000000, 0xffffffffffffffff). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 0ef8cd1f-5cb1-448d-a0f2-91cf687ce35a.

3.
Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Fri 03/04/2020 4:23:07 am your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\040320-18140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC810)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80332A9412C, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 03/04/2020 3:47:02 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!KeRegisterNmiCallback+0x1EE)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8025DE9412C, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\Minidump\040320-18906-01.dmp


Here are the dump files.
https://drive.google.com/open?id=1CX8dR1aB5PYMc38dhooT8yWP8vcH0-hq
 
Last edited: