Windows 10: BSOD while gaming in Windows 10 1903

Been having major BSOD issues playing games after updating to Windows 10 1903, Sniper Elite 4 and BioShock causing the most occurrences.


PC Specs:


i7-8700K

32GB DDR4 2666MHz

ASUS Z370-A II PRIME

ASUS RTX 2080 Strix


Crash dump as follows,





Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\minidump\060719-10718-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available





************* Path validation summary **************

Response Time (ms) Location

Deferred SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 10 Kernel Version 18362 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 18362.1.amd64fre.19h1_release.190318-1202

Machine Name:

Kernel base = 0xfffff806`4b000000 PsLoadedModuleList = 0xfffff806`4b4432b0

Debug session time: Fri Jun 7 03:23:19.589 2019 (UTC + 12:00)

System Uptime: 0 days 0:00:38.308

Loading Kernel Symbols

...............................................................

................................................................

................................................................

............................

Loading User Symbols

Loading unloaded module list

........

For analysis of this file, run !analyze -v

3: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



IRQL_NOT_LESS_OR_EQUAL (a)

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 a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 0000000006e851d7, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, bitfield :

bit 0 : value 0 = read operation, 1 = write operation

bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

Arg4: fffff8064b1d79dd, address which referenced memory



Debugging Details:

------------------





KEY_VALUES_STRING: 1





PROCESSES_ANALYSIS: 1



SERVICE_ANALYSIS: 1



STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 400



BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202



SYSTEM_MANUFACTURER: System manufacturer



SYSTEM_PRODUCT_NAME: System Product Name



SYSTEM_SKU: SKU



SYSTEM_VERSION: System Version



BIOS_VENDOR: American Megatrends Inc.



BIOS_VERSION: 0801



BIOS_DATE: 04/24/2019



BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.



BASEBOARD_PRODUCT: PRIME Z370-A II



BASEBOARD_VERSION: Rev X.0x



DUMP_TYPE: 2



BUGCHECK_P1: 6e851d7



BUGCHECK_P2: 2



BUGCHECK_P3: 1



BUGCHECK_P4: fffff8064b1d79dd



WRITE_ADDRESS: fffff8064b56e3b0: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

0000000006e851d7



CURRENT_IRQL: 2



FAULTING_IP:

nt!KiAttachProcess+1a2fad

fffff806`4b1d79dd 8760d1 xchg esp,dword ptr [rax-2Fh]



CPU_COUNT: c



CPU_MHZ: e70



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 9e



CPU_STEPPING: a



CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: 96'00000000 (cache) 96'00000000 (init)



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXNTFS: 1 (!blackboxntfs)





BLACKBOXPNP: 1 (!blackboxpnp)





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



BUGCHECK_STR: AV



PROCESS_NAME: gldriverquery.exe



ANALYSIS_SESSION_HOST: MICHAEL



ANALYSIS_SESSION_TIME: 06-08-2019 02:10:08.0360



ANALYSIS_VERSION: 10.0.18362.1 amd64fre



TRAP_FRAME: ffff93845f4169a0 -- (.trap 0xffff93845f4169a0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000006e85206 rbx=0000000000000000 rcx=ffff9909e2d96920

rdx=fffffa7a7c680240 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8064b1d79dd rsp=ffff93845f416b38 rbp=ffff9909effe4500

r8=0000000000000004 r9=0000000000000008 r10=0000000000000001

r11=ffff9909e2d96920 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe nc

nt!KiAttachProcess+0x1a2fad:

fffff806`4b1d79dd 8760d1 xchg esp,dword ptr [rax-2Fh] ds:00000000`06e851d7=????????

Resetting default scope



MISALIGNED_IP:

nt!KiAttachProcess+1a2fad

fffff806`4b1d79dd 8760d1 xchg esp,dword ptr [rax-2Fh]



LAST_CONTROL_TRANSFER: from fffff8064b1ce569 to fffff8064b1bc8a0



STACK_TEXT:

ffff9384`5f416858 fffff806`4b1ce569 : 00000000`0000000a 00000000`06e851d7 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx

ffff9384`5f416860 fffff806`4b1ca8a5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`000000b0 : nt!KiBugCheckDispatch+0x69

ffff9384`5f4169a0 fffff806`4b1d79dd : fffff806`4b142969 00000000`00098968 fffff806`4bab3848 fffff780`00000320 : nt!KiPageFault+0x465

ffff9384`5f416b38 00000000`00000000 : ffff9909`effe4500 00000000`00000524 ffff9909`e2da19c0 00000000`00000002 : nt!KiAttachProcess+0x1a2fad





THREAD_SHA1_HASH_MOD_FUNC: d4778c19a18e5b5eb991462cfc99f4600c507afd



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: b3c4afc984bd46995192f5241c3206ecf7be49ee



THREAD_SHA1_HASH_MOD: d084f7dfa548ce4e51810e4fd5914176ebc66791



FOLLOWUP_IP:

nt!KiAttachProcess+1a2fad

fffff806`4b1d79dd 8760d1 xchg esp,dword ptr [rax-2Fh]



FAULT_INSTR_CODE: e5d16087



SYMBOL_STACK_INDEX: 3



SYMBOL_NAME: nt!KiAttachProcess+1a2fad



FOLLOWUP_NAME: MachineOwner



IMAGE_NAME: hardware



DEBUG_FLR_IMAGE_TIMESTAMP: 0



IMAGE_VERSION: 10.0.18362.145



STACK_COMMAND: .thread ; .cxr ; kb



MODULE_NAME: hardware



FAILURE_BUCKET_ID: IP_MISALIGNED



BUCKET_ID: IP_MISALIGNED



PRIMARY_PROBLEM_CLASS: IP_MISALIGNED



TARGET_TIME: 2019-06-06T15:23:19.000Z



OSBUILD: 18362



OSSERVICEPACK: 145



SERVICEPACK_NUMBER: 0



OS_REVISION: 0



SUITE_MASK: 272



PRODUCT_TYPE: 1



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS



OS_LOCALE:



USER_LCID: 0



OSBUILD_TIMESTAMP: unknown_date



BUILDDATESTAMP_STR: 190318-1202



BUILDLAB_STR: 19h1_release



BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202



ANALYSIS_SESSION_ELAPSED_TIME: 388e



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:ip_misaligned



FAILURE_ID_HASH: {201b0e5d-db2a-63d2-77be-8ce8ff234750}



Followup: MachineOwner

---------


So far I have done chkdsk, sfc scans, memtests, all proving inconclusive.


Any help appreciated.



Thanks,


Michael

:)

 

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.

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

Local profile issue after upgrading to 1903


Hi roblinb

Not listed in the Known.

Known issues for Windows 10 May 2019 Update version 1903


As far as Wifi any chance it is Qualcom inside USB adapter, if Qualcom then yes known issue.


I might create another user (Local) and when if try again see if this issue occurs on both users.

Would also suggest you run the first 5 steps in this tutorial to see if you have any corruption with current build.

Use DISM to Repair Windows 10 Image


Ken