Windows 10: BSOD for several weeks now on win 10

I am experiencing BSOD for several weeks now on win 10, run windbg on dmp files and received the output below, can anyone help and tell me what needs to be done?



*******************************************************************************
* *
* 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: ffffcc862b2f0e24, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff8050b631819, 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.18362.295 (WinBuild.160101.0800)

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

DUMP_TYPE: 2

BUGCHECK_P1: ffffcc862b2f0e24

BUGCHECK_P2: 2

BUGCHECK_P3: fffff8050b631819

BUGCHECK_P4: 2

READ_ADDRESS: fffff8050bb713b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffcc862b2f0e24

FAULTING_IP:
nt!IofCallDriver+59
fffff805`0b631819 4883c438 add rsp,38h

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: TeamViewer.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: MOSHE-PC-ROG

ANALYSIS_SESSION_TIME: 08-15-2019 23:05:35.0919

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

TRAP_FRAME: ffff9408f1872590 -- (.trap 0xffff9408f1872590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000103 rbx=0000000000000000 rcx=0000000000000004
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8050b631819 rsp=ffff9408f1872720 rbp=0000000000000002
r8=0000000000000001 r9=0000000000000000 r10=ffff83004b479180
r11=ffff9408f1872520 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!IofCallDriver+0x59:
fffff805`0b631819 4883c438 add rsp,38h
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8050b7e1f34 to fffff8050b7bfcc0

STACK_TEXT:
ffff9408`f18722e8 fffff805`0b7e1f34 : 00000000`00000050 ffffcc86`2b2f0e24 00000000`00000002 ffff9408`f1872590 : nt!KeBugCheckEx
ffff9408`f18722f0 fffff805`0b6729df : 00000000`00000000 00000000`00000002 00000000`00000000 ffffcc86`2b2f0e24 : nt!MiSystemFault+0x1d5374
ffff9408`f18723f0 fffff805`0b7cdd20 : 00000000`00000000 ffffffff`ffffd8f0 00000000`00000000 ffffcc86`1c684030 : nt!MmAccessFault+0x34f
ffff9408`f1872590 fffff805`0b631819 : ffffcc86`1b6bd560 00000000`00000000 00000000`00000001 ffffcc86`1b6bd750 : nt!KiPageFault+0x360
ffff9408`f1872720 fffff805`0bbe7215 : ffffcc86`1b6bd560 00000000`00000000 00000000`00000000 ffffcc86`11fbe200 : nt!IofCallDriver+0x59
ffff9408`f1872760 fffff805`0bbe7020 : 00000000`00000000 ffff9408`f1872a80 ffffcc86`1b6bd560 ffff9408`f1872a80 : nt!****00`00000001 00000000`00000000 ffff9408`f1872900 : nt!NtDeviceIoControlFile+0x56
ffff9408`f1872990 00000000`770d1cbc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`0beef088 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770d1cbc


THREAD_SHA1_HASH_MOD_FUNC: e629a206acf5e06da2a77637dd406dea6fb67938

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 0e4d82c2ac431adbdbc7fac000a7d2a68949976d

THREAD_SHA1_HASH_MOD: 9f457f347057f10e1df248e166a3e95e6570ecfe

FOLLOWUP_IP:
nt!IofCallDriver+59
fffff805`0b631819 4883c438 add rsp,38h

FAULT_INSTR_CODE: 38c48348

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!IofCallDriver+59

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 35707659

IMAGE_VERSION: 10.0.18362.295

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 59

FAILURE_BUCKET_ID: AV_INVALID_nt!IofCallDriver

BUCKET_ID: AV_INVALID_nt!IofCallDriver

PRIMARY_PROBLEM_CLASS: AV_INVALID_nt!IofCallDriver

TARGET_TIME: 2019-08-16T05:58:08.000Z

OSBUILD: 18362

OSSERVICEPACK: 295

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: 1998-05-30 14:12:57

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.18362.295

ANALYSIS_SESSION_ELAPSED_TIME: 683

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_invalid_nt!iofcalldriver

FAILURE_ID_HASH: {c9a00350-f20b-c7f5-62da-4ca999adb554}

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

:)

 

Win 10 BSOD while using

Did upgrade to Win 10 over a month ago. This morning my Lenovo T410 laptop had the BSOD with Error=0xc000000f on it (it does backups overnight). I've run diags on the hardware (mem, motherboard bus, PCI bus and HDD) all PASS. Tried using my repair disk
(built in Jan with Win7) and was unable to recover. I checked for bad sectors and found none. From CMD prompt I did DISKPART and LIST VOLUME and all volumes say HEALTHY but I see that my C: drive (primary partition) says it is RAW (instead of NTFS). My backup
media is a network attached (NAS) disk and I used Cobian 11 Backup. Not sure what my next step would be. Looking for suggestions before I have to restore to Win7 and re-upgrade, etc.

 

Win 10 BSOD constantly

Lenovo just replaced mother board and screen, and restored Win 7. I upgraded to Win 10, then did a clean install of Win 10. I've been using it for a week without a problem, but over last 2 days it crashes regularly. Sometimes I see BSOD, other times the
screen flickers and it just turns off. I also spent an hour just getting it to turn on this morning. here is link to files from latest crash https://onedrive.live.com/redir?resid=E9F1B8E0D999A411!157&authkey=!AKVo3tLGICpmbzY&ithint=file,rar

i'm hoping someone can review and let me know of any suggestions to resolve.

Cheers

 

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.