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

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 AMD64Copyright 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 availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 16 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff801`40400000 PsLoadedModuleList = 0xfffff801`408460f0Debug session time: Sat Nov 14 20:39:54.743 2020 UTC - 3:00System Uptime: 36 days 22:10:19.226Loading Kernel Symbols...........................................................................................................................................................................................Loading User SymbolsLoading unloaded module list..................................................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff801`405c2990 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff486`a5bd9f90=000000000000001e15: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KMODE_EXCEPTION_NOT_HANDLED 1eThis is a very common bugcheck. Usually the exception address pinpointsthe driver/function that caused the problem. Always note this addressas well as the link date of the driver/image that contains this address.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: 0000000000000000, The address that the exception occurred atArg3: 0000000000000008, Parameter 0 of the exceptionArg4: 0000000000000000, Parameter 1 of the exceptionDebugging 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.sysKEY_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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 1eBUGCHECK_P1: ffffffffc0000005BUGCHECK_P2: 0BUGCHECK_P3: 8BUGCHECK_P4: 0BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemTRAP_FRAME: ffff800000000000 -- .trap 0xffff800000000000Unable to read trap frame at ffff8000`00000000STACK_TEXT: fffff486`a5bd9f88 fffff801`40619d71 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckExfffff486`a5bd9f90 fffff801`405d495d : ffffd9ec`f67b3000 fffff486`a5bda820 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x18c871fffff486`a5bda640 fffff801`405d0b43 : 00000000`0022b377 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x11dfffff486`a5bda820 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff486`a5bdaa10 : nt!KiPageFault+0x443SYMBOL_NAME: nt!KiDispatchException+18c871MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.18362.1082STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 18c871FAILURE_BUCKET_ID: 0x1E_nt!KiDispatchExceptionOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_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 AMD64Copyright 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 LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 16 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff801`17000000 PsLoadedModuleList = 0xfffff801`174461b0Debug session time: Sun Nov 29 01:11:10.762 2020 UTC - 3:00System Uptime: 0 days 1:07:32.445Loading Kernel Symbols................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list.......For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff801`171c3b20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8405`9c3da730=000000000000000a15: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL d1An attempt was made to access a pageable or completely invalid address at aninterrupt request level IRQL that is too high. This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: 0000000000000002, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000008, value 0 = read operation, 1 = write operationArg4: 0000000000000002, address which referenced memoryDebugging 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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: d1BUGCHECK_P1: 2BUGCHECK_P2: 2BUGCHECK_P3: 8BUGCHECK_P4: 2READ_ADDRESS: 0000000000000002 PROCESS_NAME: SystemBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1TRAP_FRAME: ffff84059c3da870 -- .trap 0xffff84059c3da870NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=fffff801174660f8rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=0000000000000002 rsp=ffff84059c3daa00 rbp=ffffde879d6c8290 r8=0000000000000000 r9=ffffde879d6c8290 r10=0000000000000000r11=fffff801174660f8 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl zr na po nc00000000`00000002 ?? ???Resetting default scopeFAILED_INSTRUCTION_ADDRESS: +000000000`00000002 ?? ???STACK_TEXT: ffff8405`9c3da728 fffff801`171d5929 : 00000000`0000000a 00000000`00000002 00000000`00000002 00000000`00000008 : nt!KeBugCheckExffff8405`9c3da730 fffff801`171d1c69 : ffff8405`9c3daa40 fffff801`1707c9a6 ffffde87`9d77d080 00000000`00000001 : nt!KiBugCheckDispatch+0x69ffff8405`9c3da870 00000000`00000002 : 00000000`00000008 ffffde87`9d6c8290 fffff400`00000000 00000000`00000000 : nt!KiPageFault+0x469ffff8405`9c3daa00 00000000`00000008 : ffffde87`9d6c8290 fffff400`00000000 00000000`00000000 ffffce80`1c0f9180 : 0x2ffff8405`9c3daa08 ffffde87`9d6c8290 : fffff400`00000000 00000000`00000000 ffffce80`1c0f9180 fffff801`1702a151 : 0x8ffff8405`9c3daa10 fffff400`00000000 : 00000000`00000000 ffffce80`1c0f9180 fffff801`1702a151 fffff801`00000010 : 0xffffde87`9d6c8290ffff8405`9c3daa18 00000000`00000000 : ffffce80`1c0f9180 fffff801`1702a151 fffff801`00000010 00000000`00000002 : 0xfffff400`00000000SYMBOL_NAME: nt!KiPageFault+469MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 469FAILURE_BUCKET_ID: AV_CODE_AV_NULL_IP_nt!KiPageFaultOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {4ce35ff9-c5cf-d66d-0323-0f05e33f6692}Followup: MachineOwner---------

:)

 

BSOD When playing games

Hi Jackson,

Thank you for contacting Microsoft Community.

Please share the information requested below:

• Does the BSOD occur while playing a particular game?
• Is the game downloaded from Windows Store?

I suggest you to update the Graphic Card drivers by following the steps provided below and check if it helps.

• Press Windows key + X, select Device Manager.
• Expand Display Adapters.
• Right click on the driver and select Update Driver Software.
• Follow the on-screen prompts to update.

Refer the link below for more information:

http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

Hope this helps. Keep us posted on the status for further assistance.

 

BSOD from Xbox Game Pass PC.

More than half of the games on Xbox Game pass on PC has been causing me to have a BSOD. It never happened until a few months ago. Every Xbox game Pass PC games worked fine for me.

For example, when Bloodstained Ritual of the Night came out on game pass, I would play it perfectly, just fine. But now it causes a BSOD.

My PC can run it, the Microsoft Store says that my PC can run the games. I have updated all my drivers, I've recently changed my ram. I have made sure I have all the latest Windows 10 updates and nothing yet. Basically all game pass games causes a BSOD.
It doesn't do it for any of my games on Steam that run much more heavier games, they all run fine.

But the Xbox game pass games causes a BSOD and it's only been the Xbox Game pass games. I've been waiting months hoping that Microsoft will Issue a patch or it'll fix by itself, but nothing.

I just want to enjoy some games on the Game Pass, but basically all games causes my PC to crash. Only exception being Astroneer and that's it. Every other games just crashes my PC.

And remember, my PC runs every other game on Steam, etc just fine. Its just the Xbox game Pass causing this.

I really need help.

 

BSOD when starting a game

Whenever I try to start a game , a specific game nit all of them , I get the BSOD giving error

Page fault in non paged area

The reason xhunter1.sys

I tried deleting the fike but it kseps coming back

I contacted the game's customer support but apparently this case is unique to them and not a problem from their side.

Dows anyone have any idea what is happening and how to deal with it ?