W
WeinerTiberiu
Hello. The problem started when i've updated to windows 1903 and all hell broke loose. I started gaining crashes when playing media on any browser, especially chrome. Usually the bug check string is system_thread_exception_not_handled and address in stack is bridge.sys and ndis.sys. All drivers are up to date, less so the bios of the motherboard, newer bios/s are causing much frequently bsods. Thank you !
Microsoft (R) Windows Debugger Version 10.0.18362.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\hypnos\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`4f000000 PsLoadedModuleList = 0xfffff802`4f4480b0
Debug session time: Thu Dec 19 00:01:50.344 2019 (UTC + 2:00)
System Uptime: 0 days 3:21:57.030
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
14: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff8024a1c807e, The address that the exception occurred at
Arg3: ffffa287bb7d69b8, Exception Record Address
Arg4: ffffb78072af7930, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
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: Gigabyte Technology Co., Ltd.
SYSTEM_PRODUCT_NAME: Z390 AORUS MASTER
SYSTEM_SKU: Default string
SYSTEM_VERSION: Default string
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: F8
BIOS_DATE: 03/14/2019
BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
BASEBOARD_PRODUCT: Z390 AORUS MASTER-CF
BASEBOARD_VERSION: x.x
DUMP_TYPE: 1
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8024a1c807e
BUGCHECK_P3: ffffa287bb7d69b8
BUGCHECK_P4: ffffb78072af7930
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
FAULTING_IP:
bridge+807e
fffff802`4a1c807e 488b4918 mov rcx,qword ptr [rcx+18h]
EXCEPTION_RECORD: ffffa287bb7d69b8 -- (.exr 0xffffa287bb7d69b8)
ExceptionAddress: fffff8024a1c807e (bridge+0x000000000000807e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffffb78072af7930 -- (.cxr 0xffffb78072af7930)
rax=0000000000000000 rbx=0000000000000000 rcx=cd50d33a76e0de18
rdx=0000000000000000 rsi=ffffa50c6bd497a0 rdi=ffffa50c60e2f930
rip=fffff8024a1c807e rsp=ffffa287bb7d6bf0 rbp=ffffa287bb7d6d00
r8=ffffa50c6589d970 r9=fffffffffffffffe r10=fffff8024f0620f0
r11=ffffa287bb7d6a80 r12=0000000000000000 r13=00000000fffeff00
r14=ffffa50c6bd499d0 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00050286
bridge+0x807e:
fffff802`4a1c807e 488b4918 mov rcx,qword ptr [rcx+18h] ds:002b:cd50d33a`76e0de30=????????????????
Resetting default scope
CPU_COUNT: 10
CPU_MHZ: e10
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: c
CPU_MICROCODE: 6,9e,c,0 (F,M,S,R) SIG: A2'00000000 (cache) A2'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
FOLLOWUP_IP:
bridge+807e
fffff802`4a1c807e 488b4918 mov rcx,qword ptr [rcx+18h]
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-4OVJIEG
ANALYSIS_SESSION_TIME: 12-19-2019 00:20:59.0633
ANALYSIS_VERSION: 10.0.18362.1 x86fre
BAD_STACK_POINTER: ffffb78072af70c8
LAST_CONTROL_TRANSFER: from fffff8024a1c872f to fffff8024a1c807e
STACK_TEXT:
ffffa287`bb7d6bf0 fffff802`4a1c872f : 00000000`00000002 00000000`00000004 ffffa287`bb7d6d80 00000000`0000000e : bridge+0x807e
ffffa287`bb7d6c80 fffff802`4f12a7a5 : ffffa50c`439a5040 ffffa50c`439a5040 fffff802`4a1c8500 00000000`0000000e : bridge+0x872f
ffffa287`bb7d7b10 fffff802`4f1c8a5a : ffffb780`72ad1180 ffffa50c`439a5040 fffff802`4f12a750 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffa287`bb7d7b60 00000000`00000000 : ffffa287`bb7d8000 ffffa287`bb7d1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a
THREAD_SHA1_HASH_MOD_FUNC: 4b27b247caadaebb83569df9b772254ec51933b1
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 12a2bfa35ea975e90ee55b0f6d08aa7975c1cb5d
THREAD_SHA1_HASH_MOD: af97ffc91037bc680eaf7bc6cdd00050b9235ff8
FAULT_INSTR_CODE: 18498b48
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: bridge+807e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: bridge
IMAGE_NAME: bridge.sys
DEBUG_FLR_IMAGE_TIMESTAMP: f1470b4
STACK_COMMAND: .cxr 0xffffb78072af7930 ; kb
BUCKET_ID_FUNC_OFFSET: 807e
FAILURE_BUCKET_ID: AV_STACKPTR_ERROR_bridge!unknown_function
BUCKET_ID: AV_STACKPTR_ERROR_bridge!unknown_function
PRIMARY_PROBLEM_CLASS: AV_STACKPTR_ERROR_bridge!unknown_function
TARGET_TIME: 2019-12-18T22:01:50.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: 2011-01-12 15:55:39
BUILDDATESTAMP_STR: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: 4a7f
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_stackptr_error_bridge!unknown_function
FAILURE_ID_HASH: {7c978e5a-5f78-1ec3-8e3c-e245486b5eda}
Followup: MachineOwner
---------
14: kd> g
^ No runnable debuggees error in 'g'
Continue reading...
Microsoft (R) Windows Debugger Version 10.0.18362.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\hypnos\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`4f000000 PsLoadedModuleList = 0xfffff802`4f4480b0
Debug session time: Thu Dec 19 00:01:50.344 2019 (UTC + 2:00)
System Uptime: 0 days 3:21:57.030
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
14: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff8024a1c807e, The address that the exception occurred at
Arg3: ffffa287bb7d69b8, Exception Record Address
Arg4: ffffb78072af7930, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
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: Gigabyte Technology Co., Ltd.
SYSTEM_PRODUCT_NAME: Z390 AORUS MASTER
SYSTEM_SKU: Default string
SYSTEM_VERSION: Default string
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: F8
BIOS_DATE: 03/14/2019
BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
BASEBOARD_PRODUCT: Z390 AORUS MASTER-CF
BASEBOARD_VERSION: x.x
DUMP_TYPE: 1
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8024a1c807e
BUGCHECK_P3: ffffa287bb7d69b8
BUGCHECK_P4: ffffb78072af7930
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
FAULTING_IP:
bridge+807e
fffff802`4a1c807e 488b4918 mov rcx,qword ptr [rcx+18h]
EXCEPTION_RECORD: ffffa287bb7d69b8 -- (.exr 0xffffa287bb7d69b8)
ExceptionAddress: fffff8024a1c807e (bridge+0x000000000000807e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffffb78072af7930 -- (.cxr 0xffffb78072af7930)
rax=0000000000000000 rbx=0000000000000000 rcx=cd50d33a76e0de18
rdx=0000000000000000 rsi=ffffa50c6bd497a0 rdi=ffffa50c60e2f930
rip=fffff8024a1c807e rsp=ffffa287bb7d6bf0 rbp=ffffa287bb7d6d00
r8=ffffa50c6589d970 r9=fffffffffffffffe r10=fffff8024f0620f0
r11=ffffa287bb7d6a80 r12=0000000000000000 r13=00000000fffeff00
r14=ffffa50c6bd499d0 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00050286
bridge+0x807e:
fffff802`4a1c807e 488b4918 mov rcx,qword ptr [rcx+18h] ds:002b:cd50d33a`76e0de30=????????????????
Resetting default scope
CPU_COUNT: 10
CPU_MHZ: e10
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: c
CPU_MICROCODE: 6,9e,c,0 (F,M,S,R) SIG: A2'00000000 (cache) A2'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
FOLLOWUP_IP:
bridge+807e
fffff802`4a1c807e 488b4918 mov rcx,qword ptr [rcx+18h]
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-4OVJIEG
ANALYSIS_SESSION_TIME: 12-19-2019 00:20:59.0633
ANALYSIS_VERSION: 10.0.18362.1 x86fre
BAD_STACK_POINTER: ffffb78072af70c8
LAST_CONTROL_TRANSFER: from fffff8024a1c872f to fffff8024a1c807e
STACK_TEXT:
ffffa287`bb7d6bf0 fffff802`4a1c872f : 00000000`00000002 00000000`00000004 ffffa287`bb7d6d80 00000000`0000000e : bridge+0x807e
ffffa287`bb7d6c80 fffff802`4f12a7a5 : ffffa50c`439a5040 ffffa50c`439a5040 fffff802`4a1c8500 00000000`0000000e : bridge+0x872f
ffffa287`bb7d7b10 fffff802`4f1c8a5a : ffffb780`72ad1180 ffffa50c`439a5040 fffff802`4f12a750 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffa287`bb7d7b60 00000000`00000000 : ffffa287`bb7d8000 ffffa287`bb7d1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a
THREAD_SHA1_HASH_MOD_FUNC: 4b27b247caadaebb83569df9b772254ec51933b1
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 12a2bfa35ea975e90ee55b0f6d08aa7975c1cb5d
THREAD_SHA1_HASH_MOD: af97ffc91037bc680eaf7bc6cdd00050b9235ff8
FAULT_INSTR_CODE: 18498b48
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: bridge+807e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: bridge
IMAGE_NAME: bridge.sys
DEBUG_FLR_IMAGE_TIMESTAMP: f1470b4
STACK_COMMAND: .cxr 0xffffb78072af7930 ; kb
BUCKET_ID_FUNC_OFFSET: 807e
FAILURE_BUCKET_ID: AV_STACKPTR_ERROR_bridge!unknown_function
BUCKET_ID: AV_STACKPTR_ERROR_bridge!unknown_function
PRIMARY_PROBLEM_CLASS: AV_STACKPTR_ERROR_bridge!unknown_function
TARGET_TIME: 2019-12-18T22:01:50.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: 2011-01-12 15:55:39
BUILDDATESTAMP_STR: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: 4a7f
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_stackptr_error_bridge!unknown_function
FAILURE_ID_HASH: {7c978e5a-5f78-1ec3-8e3c-e245486b5eda}
Followup: MachineOwner
---------
14: kd> g
^ No runnable debuggees error in 'g'
Continue reading...