Windows 10: win10 updated, keep randomly crashing and blue screen. help please!!!!!

Loading Dump File [C:\Users\cf\OneDrive\Documents\MINIDUMP\091119-16062-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff801`6ac00000 PsLoadedModuleList = 0xfffff801`6b047590
Debug session time: Wed Sep 11 15:25:56.191 2019 (UTC - 4:00)
System Uptime: 0 days 0:07:54.044
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`6adc10a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb18d`b72e62b0=000000000000007e



SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801781317f4, The address that the exception occurred at
Arg3: ffffb18db72e72c8, Exception Record Address
Arg4: ffffb18db72e6b10, Context Record Address

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

:)

 

Crash/blue screen

Hi

I assume from the title of your post Crash/Blue Screen that the PC has crashed and produced a *BSOD=[Blue Screen Of Death] =Blue Screen; and that the PC recovered from this; if and when you see the Blue Screen write the Stop Code down; recover the PC or use one that is working to access the net and look up the Stop Code.

nb: You may be able to view this with a [*BlueScreenView] application, google for this.

Edit Link - Blue screen of death (STOP error) information in dump files.

Description
===========

BlueScreenView scans all your minidump files created during 'blue screen
of death' crashes, and displays the information about all crashes in one
table. For each crash, BlueScreenView displays the minidump filename, the
date/time of the crash, the basic crash information displayed in the blue
screen (Bug Check Code and 4 parameters), and the details of the driver
or module that possibly caused the crash (filename, product name, file
description, and file version).
For each crash displayed in the upper pane, you can view the details of
the device drivers loaded during the crash in the lower pane.
BlueScreenView also mark the drivers that their addresses found in the
crash stack, so you can easily locate the suspected drivers that possibly
caused the crash.

atb

Law-II

 

Blue Screen of Death (Crash) When Playing Games


Nothing for step 10.

Step 11 -

 

Blue screen crashes

Hi Howard,

We would like to know if you're still experiencing blue screen errors. If yes, the error WHEA_UNCORRECTABLE_ERROR message you received may possibly occur due to a hardware error.
To efficiently assist you, kindly answer the following questions:

• Have you made any recent changes prior to this issue?
• What troubleshooting steps have you done so far?

Meanwhile, I suggest that you follow the steps in this article on how to troubleshoot WHEA_UNCORRECTABLE_ERROR.

If the issue still persists, I recommend that you follow the steps in this
article on how to troubleshoot blue screen errors. You can choose when did you get the error and perform
the instructions.

Let us know if you need further assistance.