Windows 10: BSOD WHEN GAMING

Dear，anyone can help me find the problem, i always get the BSOD when i play the andrpid emulator

WIN10

new laptop bought from last year. I update the driver already, BSOD Code is different every times.


the new one is "

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




************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff802`5e610000 PsLoadedModuleList = 0xfffff802`5ea2b790
Debug session time: Fri Apr 5 08:31:56.321 2019 (UTC - 4:00)
System Uptime: 0 days 21:39:38.061
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`5e7c36a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9a02`f907f270=0000000000000050
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff802de6f6f83, memory referenced.
Arg2: 0000000000000010, value 0 = read operation, 1 = write operation.
Arg3: fffff802de6f6f83, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

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: 10.0.17763.404 (WinBuild.160101.0800)

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

DUMP_TYPE: 2

BUGCHECK_P1: fffff802de6f6f83

BUGCHECK_P2: 10

BUGCHECK_P3: fffff802de6f6f83

BUGCHECK_P4: 2

READ_ADDRESS: GetUlongFromAddress: unable to read from fffff8025ead7540
fffff8025eb52390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff802de6f6f83

FAULTING_IP:
+0
fffff802`de6f6f83 ?? ???

MM_INTERNAL_CODE: 2

CPU_COUNT: c

CPU_MHZ: e70

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-RICKY¡®

ANALYSIS_SESSION_TIME: 04-08-2019 01:24:29.0606

ANALYSIS_VERSION: 10.0.18317.1001 amd64fre

TRAP_FRAME: ffff9a02f907f550 -- (.trap 0xffff9a02f907f550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffb28f5ad99ea0
rdx=ffffda801efd3180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802de6f6f83 rsp=ffff9a02f907f6e0 rbp=0000000000000000
r8=0000000000000000 r9=ffffb28f5ad99e40 r10=fffff802693c13e0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
fffff802`de6f6f83 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8025e86779b to fffff8025e7c36a0

FAILED_INSTRUCTION_ADDRESS:
+0
fffff802`de6f6f83 ?? ???

STACK_TEXT:
ffff9a02`f907f268 fffff802`5e86779b : 00000000`00000050 fffff802`de6f6f83 00000000`00000010 ffff9a02`f907f550 : nt!KeBugCheckEx
ffff9a02`f907f270 fffff802`5e6d83d7 : ffff9a02`f907f400 00000000`00000010 00000000`00000000 fffff802`de6f6f83 : nt!MiSystemFault+0x13016b
ffff9a02`f907f3b0 fffff802`5e7d1183 : 00000000`00000000 00000000`00000000 ffffb28f`5aeeb100 00000000`00000000 : nt!MmAccessFault+0x327
ffff9a02`f907f550 fffff802`de6f6f83 : 00000000`00000000 00000000`00000081 00000000`00000000 00000000`0000024b : nt!KiPageFault+0x343
ffff9a02`f907f6e0 00000000`00000000 : 00000000`00000081 00000000`00000000 00000000`0000024b 00000000`00000000 : 0xfffff802`de6f6f83


THREAD_SHA1_HASH_MOD_FUNC: 35852f70c1fb96d682b5bd0e931cc10c7b9fe1fe

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: c499a214b93072531447d3584bfc416abdb8bf51

THREAD_SHA1_HASH_MOD: d084f7dfa548ce4e51810e4fd5914176ebc66791

FOLLOWUP_IP:
nt!MiSystemFault+13016b
fffff802`5e86779b cc int 3

FAULT_INSTR_CODE: 1a05f7cc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiSystemFault+13016b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 627e2507

IMAGE_VERSION: 10.0.17763.404

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 13016b

FAILURE_BUCKET_ID: AV_INVALID_BAD_IP_nt!MiSystemFault

BUCKET_ID: AV_INVALID_BAD_IP_nt!MiSystemFault

PRIMARY_PROBLEM_CLASS: AV_INVALID_BAD_IP_nt!MiSystemFault

TARGET_TIME: 2019-04-05T12:31:56.000Z

OSBUILD: 17763

OSSERVICEPACK: 404

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2022-05-13 05:29:43

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.17763.404

ANALYSIS_SESSION_ELAPSED_TIME: 5bc

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_invalid_bad_ip_nt!misystemfault

FAILURE_ID_HASH: {48ad9531-e3f8-1044-fc5f-d917677674c7}

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.

 

7 different BSoD

Hey guys,

I have a serious problem. I make it as short as possible:

• system runs 100 % fine with the 10.12
• updatet to Catalyst 11.1 -> BSoD
• updatet to 11.1 Hotfix -> BSoD
• rollback to 10.12 -> BSoD
• removed ALL AMD files manually, installed 10.12 -> BSoD

• Temps are fine
• no sfc /scannow errors
• no chkdsk errors
• Prime, Furmark all fine
• regardless what driver I install -> BSoD
• I did no hw changes, no OC

Here are my BSoDs I receive:

• 0x0000010e
• 0x1000007e
• 0x0000007e
• 0x0000004e
• 0x0000003b
• dxgmms1.sys
• PFN_LIST_CORRUPT

They all refer to the GPU of course ...

From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
Apparently the 11.1 damaged my system irreparable.

Any advice or info would be very much appreciated *Smile

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.