Windows 10: Computer BSOD

I've been having system restarts and BSODs for the past 2.5 weeks! somebody please help me decode this mini dump file. I've tried re-installing drivers/ 2 factory resets/ and many other suggestions.






Loading Dump File [C:\Windows\Minidump\091819-7812-01.dmp]

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

Mini Kernel Dump does not have process information
Symbol search path is: srv*
Executable search path is:
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff801`13a00000 PsLoadedModuleList = 0xfffff801`13e475b0
Debug session time: Wed Sep 18 16:27:35.310 2019 (UTC - 7:00)
System Uptime: 0 days 0:53:41.026
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
.Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000

Loading User Symbols
For analysis of this file, run !analyze -v
1: 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: ffff88551a477a00, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff80131ad2793, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

DUMP_TYPE: 2

BUGCHECK_P1: ffff88551a477a00

BUGCHECK_P2: 2

BUGCHECK_P3: fffff80131ad2793

BUGCHECK_P4: 2

READ_ADDRESS: Unable to get size of nt!_MMPTE - probably bad symbols
ffff88551a477a00

FAULTING_IP:
+0
fffff801`31ad2793 ?? ???

MM_INTERNAL_CODE: 2

CPU_COUNT: c

CPU_MHZ: 8a0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CORRUPT_MODULELIST_AV

BUGCHECK_STR: AV

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: LAPTOP-2TS61QKB

ANALYSIS_SESSION_TIME: 09-18-2019 16:53:59.0632

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80113bc10a0

STACK_TEXT:
fffffe08`b17aa3b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff801`13bc10a0


SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID: CORRUPT_MODULELIST_AV

PRIMARY_PROBLEM_CLASS: CORRUPT_MODULELIST_AV

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_AV

TARGET_TIME: 2019-09-18T23:27:35.000Z

OSBUILD: 18362

OSSERVICEPACK: 0

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: unknown_date

ANALYSIS_SESSION_ELAPSED_TIME: 21

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:corrupt_modulelist_av

FAILURE_ID_HASH: {fc259191-ef0c-6215-476f-d32e5dcaf1b7}

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

:)

 

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.

 

BSOD issue after fixing another BSOD error

Hi Williams,

There are several reasons why BSOD occur, which has different resolution. To check for any corruption or the integrity of your computer's Windows, we suggest that you perform a
Check Disk by following these steps:

• Type cmd in the search bar.
• Right-click on the Command Prompt, then Run as administrator.
  
• Type chkdsk x: /r, the /r command will fix errors found on the disk.

Let us know if you need 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