BSOD on a custom gaming pc - bsod when starting or finising a game.

T

ThueLund Mølgaard

I have been slowly replacing/switching parts for my pc, still I havent figured out why my PC does the BSOD.


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


Loading Dump File [C:\Users\*\Desktop\112920-8734-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff801`40400000 PsLoadedModuleList = 0xfffff801`408460f0
Debug session time: Sat Nov 14 20:39:54.743 2020 (UTC - 3:00)
System Uptime: 36 days 22:10:19.226
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run
!analyze -v
nt!KeBugCheckEx:
fffff801`405c2990 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff486`a5bd9f90=000000000000001e
15: 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: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4655

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 38328

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: 0

BUGCHECK_P3: 8

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (
!blackboxbsd)


BLACKBOXNTFS: 1 (
!blackboxntfs)


BLACKBOXPNP: 1 (
!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffff800000000000 --
(.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
fffff486`a5bd9f88 fffff801`40619d71 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
fffff486`a5bd9f90 fffff801`405d495d : ffffd9ec`f67b3000 fffff486`a5bda820 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x18c871
fffff486`a5bda640 fffff801`405d0b43 : 00000000`0022b377 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x11d
fffff486`a5bda820 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff486`a5bdaa10 : nt!KiPageFault+0x443


SYMBOL_NAME: nt!KiDispatchException+18c871

MODULE_NAME:
nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.18362.1082

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 18c871

FAILURE_BUCKET_ID: 0x1E_nt!KiDispatchException

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {4c003660-11e1-3fb7-2474-3522eb7ee67b}

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

NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2007.6001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2007.6001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2007.6001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2007.6001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2007.6001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2007.6001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2007.6001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2007.6001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2007.6001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2007.6001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2007.6001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis'

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


Loading Dump File [C:\Users\Paranoid\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be 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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff801`17000000 PsLoadedModuleList = 0xfffff801`174461b0
Debug session time: Sun Nov 29 01:11:10.762 2020 (UTC - 3:00)
System Uptime: 0 days 1:07:32.445
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols

Loading unloaded module list
.......
For analysis of this file, run
!analyze -v
nt!KeBugCheckEx:
fffff801`171c3b20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8405`9c3da730=000000000000000a
15: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000002, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000002, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1593

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 1587

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: d1

BUGCHECK_P1: 2

BUGCHECK_P2: 2

BUGCHECK_P3: 8

BUGCHECK_P4: 2

READ_ADDRESS: 0000000000000002

PROCESS_NAME: System

BLACKBOXBSD: 1 (
!blackboxbsd)


BLACKBOXNTFS: 1 (
!blackboxntfs)


BLACKBOXPNP: 1 (
!blackboxpnp)


BLACKBOXWINLOGON: 1

TRAP_FRAME: ffff84059c3da870 --
(.trap 0xffff84059c3da870)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff801174660f8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000002 rsp=ffff84059c3daa00 rbp=ffffde879d6c8290
r8=0000000000000000 r9=ffffde879d6c8290 r10=0000000000000000
r11=fffff801174660f8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
00000000`00000002 ?? ???
Resetting default scope

FAILED_INSTRUCTION_ADDRESS:
+0
00000000`00000002 ?? ???

STACK_TEXT:
ffff8405`9c3da728 fffff801`171d5929 : 00000000`0000000a 00000000`00000002 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffff8405`9c3da730 fffff801`171d1c69 : ffff8405`9c3daa40 fffff801`1707c9a6 ffffde87`9d77d080 00000000`00000001 : nt!KiBugCheckDispatch+0x69
ffff8405`9c3da870 00000000`00000002 : 00000000`00000008 ffffde87`9d6c8290 fffff400`00000000 00000000`00000000 : nt!KiPageFault+0x469
ffff8405`9c3daa00 00000000`00000008 : ffffde87`9d6c8290 fffff400`00000000 00000000`00000000 ffffce80`1c0f9180 : 0x2
ffff8405`9c3daa08 ffffde87`9d6c8290 : fffff400`00000000 00000000`00000000 ffffce80`1c0f9180 fffff801`1702a151 : 0x8
ffff8405`9c3daa10 fffff400`00000000 : 00000000`00000000 ffffce80`1c0f9180 fffff801`1702a151 fffff801`00000010 : 0xffffde87`9d6c8290
ffff8405`9c3daa18 00000000`00000000 : ffffce80`1c0f9180 fffff801`1702a151 fffff801`00000010 00000000`00000002 : 0xfffff400`00000000


SYMBOL_NAME: nt!KiPageFault+469

MODULE_NAME:
nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 469

FAILURE_BUCKET_ID: AV_CODE_AV_NULL_IP_nt!KiPageFault

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {4ce35ff9-c5cf-d66d-0323-0f05e33f6692}

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



Continue reading...
 
Back
Top Bottom