A problem with blue screen of death.

[Red Rider 88888]

So I am on my mothers computer and account here. She isn't too computer savy but this is beyond me. Can anyone help me with the troubleshooting steps that I need to take? I grabbed as much info I could from the dump and debugger but a lot of it is Greek to me. I have updated every driver I can get my hands on but it still persists.



Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Steam\steamapps\common\ARK\ShooterGame\Saved\Logs\Dump1481833664.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 18362 MP (16 procs) Free x64
Product: WinNt, suite: SingleUserTS
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Debug session time: Fri Nov 15 15:42:35.000 2019 (UTC - 5:00)
System Uptime: not available
Process Uptime: 0 days 0:01:45.000
................................................................
................................................................
.................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(2bd0.338): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtGetContextThread+0x14:
00007ffd`8569de54 c3 ret

Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Can't set dump file contexts
MachineInfo::SetContext failed - Thread: 0000027D5D9CA480 Handle: 1 Id: 338 - Error == 0x8000FFFF

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff805`42600000 PsLoadedModuleList = 0xfffff805`42a48190
Debug session time: Sat Feb 15 12:03:53.240 2020 (UTC - 5:00)
System Uptime: 0 days 1:58:56.937
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000050`3621e018). Type ".hh dbgerr001" for details
Loading unloaded module list
.............
nt!KeBugCheckEx:
fffff805`427c1510 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe005`b8bef5e0=000000000000001e
||1:14: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80542eb3225, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-L0RPKRC

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 5

Key : Analysis.Memory.CommitPeak.Mb
Value: 72

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80542eb3225

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff

EXCEPTION_PARAMETER2: ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

PROCESS_NAME: conhost.exe

STACK_TEXT:
ffffe005`b8bef5d8 fffff805`4282fea7 : 00000000`0000001e ffffffff`c0000005 fffff805`42eb3225 00000000`00000000 : nt!KeBugCheckEx
ffffe005`b8bef5e0 fffff805`427d351d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x168b67
ffffe005`b8befc90 fffff805`427cf2a2 : 00000000`00000000 ffffffff`ffffffff ffffe005`00000001 00000000`000007ec : nt!KiExceptionDispatch+0x11d
ffffe005`b8befe70 fffff805`42eb3225 : 00000000`000000e0 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KiGeneralProtectionFault+0x322
ffffe005`b8bf0008 fffff805`42ea8205 : 00000000`45ff7800 ffffcc0f`756cf080 ffffcc0f`ca7f97d0 00000000`00000000 : nt!PopFxTracePerfRegistration+0x4d
ffffe005`b8bf0098 fffff19b`45ff7e30 : fffff805`427d2e18 ffffcc0f`756cf080 fffff19b`45ff78a0 00000000`00000000 : nt!PopFxRegisterComponentPerfStates+0x3c1
ffffe005`b8bf0158 fffff805`427d2e18 : ffffcc0f`756cf080 fffff19b`45ff78a0 00000000`00000000 00000000`00000000 : 0xfffff19b`45ff7e30
ffffe005`b8bf0160 ffffcc0f`77990a10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffcc0f`77990a10


SYMBOL_NAME: nt!PopFxTracePerfRegistration+4d

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 4d

FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!PopFxTracePerfRegistration

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d1f84ab0-38c4-44f3-de2e-4b3a8f1442d2}

Followup: MachineOwner
---------



Continue reading...