Windows 10: Need help understanding ho wot fix bluescreens im getting

I've been having this issue for a few weeks now, the blue screen cause is system thread exception not handled. I have tried to use winddbg to look at my memory dump to find the issue and this is what i got




*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8020f031cbc, The address that the exception occurred at
Arg3: ffff870df1abc648, Exception Record Address
Arg4: ffff870df1abbe90, Context Record Address

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


KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.Elapsed.Sec
Value: 38

Key : Analysis.Memory.CommitPeak.Mb
Value: 62


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

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

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME: MS-7B84

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 2.00

BIOS_DATE: 06/04/2018

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT: B450M PRO-M2 (MS-7B84)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 1

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8020f031cbc

BUGCHECK_P3: ffff870df1abc648

BUGCHECK_P4: ffff870df1abbe90

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP:
nt!IofCallDriver+4c
fffff802`0f031cbc 488b44c170 mov rax,qword ptr [rcx+rax*8+70h]

EXCEPTION_RECORD: ffff870df1abc648 -- (.exr 0xffff870df1abc648)
ExceptionAddress: fffff8020f031cbc (nt!IofCallDriver+0x000000000000004c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: ffff870df1abbe90 -- (.cxr 0xffff870df1abbe90)
rax=000000000000000f rbx=ffffa804a108a020 rcx=a3f4d3238d5b2f7f
rdx=ffffa8049bfe9050 rsi=0000000000001000 rdi=ffffa8049bfe9050
rip=fffff8020f031cbc rsp=ffff870df1abc880 rbp=ffffa804a944fdc0
r8=000000000000000f r9=ffffa8049bf9b050 r10=0000000000000001
r11=fffff780000003b0 r12=ffffa804a108a068 r13=0000000000000000
r14=ffffa8049bf9b050 r15=ffffa804a944fdd2
iopl=0 nv up ei ng nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050287
nt!IofCallDriver+0x4c:
fffff802`0f031cbc 488b44c170 mov rax,qword ptr [rcx+rax*8+70h] ds:002b:a3f4d323`8d5b3067=????????????????
Resetting default scope

CPU_COUNT: c

CPU_MHZ: e10

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

FOLLOWUP_IP:
envirtahci+16d1c
fffff802`11826d1c 8bf0 mov esi,eax

BUGCHECK_STR: AV

READ_ADDRESS: ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

ANALYSIS_SESSION_HOST: DESKTOP-48A3G9E

ANALYSIS_SESSION_TIME: 07-10-2019 10:48:31.0851

ANALYSIS_VERSION: 10.0.18914.1001 amd64fre

LAST_CONTROL_TRANSFER: from fffff80211826d1c to fffff8020f031cbc

STACK_TEXT:
ffff870d`f1abc880 fffff802`11826d1c : fffff802`118cac10 00000000`00000000 ffff86d4`024c3200 ffffa804`a108a000 : nt!IofCallDriver+0x4c
ffff870d`f1abc8c0 fffff802`11826f1b : 00000000`00000000 00000000`00000000 ffffa804`986376c0 ffffa804`999901d4 : envirtahci+0x16d1c
ffff870d`f1abc940 fffff802`1182308f : ffffa804`986370d0 ffff870d`f1abc9f8 ffff870d`f1abca10 00000000`00001000 : envirtahci+0x16f1b
ffff870d`f1abc9b0 fffff802`118254e5 : 00000000`00000000 00000000`00000003 00000000`0000007d ffffa804`986340a8 : envirtahci+0x1308f
ffff870d`f1abca40 fffff802`118219eb : ffffa804`a1089a70 ffffa804`999901d4 ffffa804`a0d83080 ffffa804`98645190 : envirtahci+0x154e5
ffff870d`f1abca70 fffff802`1182399b : ffffa804`98645190 ffffa804`a0d83080 ffff02cf`273a8900 ffffa804`9618a900 : envirtahci+0x119eb
ffff870d`f****`00000000 : nt!IopProcessWorkItem+0xff
ffff870d`f1abcb70 fffff802`0f12f725 : ffffa804`9b7e5040 00000000`00000080 ffffa804`96073040 ffff870d`00000001 : nt!ExpWorkerThread+0x105
ffff870d`f1abcc10 fffff802`0f1c3dfa : fffff802`0aedb180 ffffa804`9b7e5040 fffff802`0f12f6d0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff870d`f1abcc60 00000000`00000000 : ffff870d`f1abd000 ffff870d`f1ab7000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC: 2b3cb21ef5e59a13a4862a9c8b0d7271e7d54bc9

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 414a158844c5cb13f802fa719a4fb615373cfb3a

THREAD_SHA1_HASH_MOD: 6540f671dd668ea9796f4d346b73e8a9ae6a8305

FAULT_INSTR_CODE: 33df08b

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: envirtahci+16d1c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: envirtahci

IMAGE_NAME: envirtahci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5c155080

STACK_COMMAND: .cxr 0xffff870df1abbe90 ; kb

BUCKET_ID_FUNC_OFFSET: 16d1c

FAILURE_BUCKET_ID: AV_envirtahci!unknown_function

BUCKET_ID: AV_envirtahci!unknown_function

PRIMARY_PROBLEM_CLASS: AV_envirtahci!unknown_function

TARGET_TIME: 2019-07-10T09:19:04.000Z

OSBUILD: 18362

OSSERVICEPACK: 0

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: 94f5

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_envirtahci!unknown_function

FAILURE_ID_HASH: {d3183d6b-1db0-cb3d-1096-dc95872ddd66}

Followup: MachineOwner


After running a memtest i get these results

https://drive.google.com/open?id=191oA9qIm0RGvhhIFmVr7AGze0YRNkOxM

https://drive.google.com/open?id=1-06bc4Z_rDu5xRlgNTZjUMBnILcH-qP4

also the dump file

https://drive.google.com/drive/folders/1bN7p6tZIxWgdLIkBcwuGr-bTFzMyiwJD?usp=sharing

:)

 

Constant bluescreens - still not fixed

I don't think you understood my issue - my bluescreens are random, so I can't do a clean boot and provoke a bluescreen. I am not sure what the steps you suggested have anything to do with my problem and it is not clear how it will help. The PC does boot
up normally, it just crashes randomly during the day.

I am pretty sure the issue is related to a driver that could be incompatible with Win 10. Please check the older threads to further understand the issue.

Thank you.

 

WOT (Web Of Trust) replacement

Good news. Bad news.

• Good news: WOT may not be going out of business. Or, at least, for the reasons you think.
• Bad news: Firefox and Chrome removed the extension form their store after a German newspaper reported that WOT was selling the browsing history of its users without even bothering to anonymize the data!

Yikes!!
- Web of Trust (WOT) Add-on taken down by Chrome & Firefox
- Mozilla and Google remove WOT extension from Store

 

wot?

Hi hwdkhd,

you can try to reset suggestions by going to:

settings > keyboard > [advanced] > [reset suggestions]

If somehow you added the word wot by mistake this will remove it from the dictionary (along with any other words you've added)

Hope this helps,