После каких-то моих манипуляций ноут раз в сутки начал BSOD'ить.
Включил запись малых дампов памяти, дождался пары бсодов и с помощью MiniDumper, а так же WinDbg, проанализировал дампы и выяснил, что виной обновление драйверов nVidia до версии 511.79 от 14.02.2022. Зашёл в диспетчер устройств, выбрал RTX 3070 и выбрал "Откатить драйвер". Откат произошёл до драйвера версии 30.0.14.7247 от 26.10.2021. В итоге второй день полёт нормальный, ни одного бсода.
Но, нужно заметить, что не смотря на явное указание на драйвер nvlddmkm.sys (драйвер Nvidia) ещё в результатах диагностики фигурирует snapman.sys (Acronis Snapshot API) и iaStorVD.sys (в моем случае это драйвер приложения Intel® Optane™ Memory and Storage Management aka Управление памятью и системой хранения Intel® Optane™).
UPD: Видимо, проблема была всё же в DisplayPort Multi-Stream Transport (MST) - к ноутбуку подключён по DisplayPort монитор № 1, а к монитору № 1 так же по DisplayPort подключён монитор № 2 и, благодаря тому, что оба монитора поддерживают DisplayPort MST, я могу подключить и использовать одновременно к 1 порту ноутбука как будто-бы 2 монитора:
Источник.
Однако, при выходе мониторов из сна после 'x' минут неактивности, ноутбук уходил в BSOD даже после отката драйвера. Пришлось второй монитор отключить от первого и подключить напрямую по HDMI к ноутбуку и проблемы нет уже 4-5 дней.
-----
MiniDumper № 12 | Дамп: 031922-14906-01.dmp (19.03.2022 17:06:42) |
3 | Код: 0x1000007E - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M |
4 | Процесс: System, вероятно вызвано: nvlddmkm.sys |
5 | Сторонние модули в стеке: nvlddmkm.sys, snapman.sys |
6 | Сторонние модули в Raw-стеке: nvlddmkm.sys, iaStorVD.sys, snapman.sys |
7 | FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function |
MiniDumper № 22 | Дамп: 031922-14984-01.dmp (19.03.2022 20:16:30) |
3 | Код: 0x1000007E - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M |
4 | Процесс: System, вероятно вызвано: nvlddmkm.sys |
5 | Сторонние модули в стеке: nvlddmkm.sys |
6 | FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function |
WinDbg Standalone001 | Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64 |
002 | Copyright (c) Microsoft Corporation. All rights reserved. |
005 | Loading Dump File [C:\Users\user\Desktop\031922-14906-01.dmp] |
006 | Mini Kernel Dump File: Only registers and stack trace are available |
009 | ************* Path validation summary ************** |
010 | Response Time (ms) Location |
011 | Deferred SRV*C:\Windows\symbol_cache*http: |
012 | Symbol search path is: SRV*C:\Windows\symbol_cache*http: |
013 | Executable search path is: |
014 | Windows 10 Kernel Version 22000 MP (16 procs) Free x64 |
015 | Product: WinNt, suite: TerminalServer SingleUserTS |
017 | Kernel base = 0xfffff805`78000000 PsLoadedModuleList = 0xfffff805`78c29b90 |
018 | Debug session time: Sat Mar 19 17:06:42.448 2022 (UTC + 3:00) |
019 | System Uptime: 0 days 5:08:05.239 |
020 | Loading Kernel Symbols |
021 | ............................................................... |
022 | ................................................................ |
023 | ................................................................ |
024 | ................................................................ |
027 | Loading unloaded module list |
029 | For analysis of this file, run !analyze -v |
030 | Unable to load image nvlddmkm.sys, Win32 error 0n2 |
031 | *** WARNING: Unable to verify timestamp for nvlddmkm.sys |
033 | ******************************************************************************* |
037 | ******************************************************************************* |
039 | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) |
040 | This is a very common bugcheck. Usually the exception address pinpoints |
041 | the driver/ function that caused the problem. Always note this address |
042 | as well as the link date of the driver/image that contains this address. |
043 | Some common problems are exception code 0x80000003. This means a hard |
044 | coded breakpoint or assertion was hit, but this system was booted |
045 | /NODEBUG. This is not supposed to happen as developers should never have |
046 | hardcoded breakpoints in retail code, but ... |
047 | If this happens, make sure a debugger gets connected, and the |
048 | system is booted /DEBUG. This will let us see why this breakpoint is |
051 | Arg1: ffffffffc0000005, The exception code that was not handled |
052 | Arg2: fffff805999ceafc, The address that the exception occurred at |
053 | Arg3: ffffc0031ce1ce38, Exception Record Address |
054 | Arg4: ffffc0031ce1c650, Context Record Address |
059 | *** WARNING: Unable to verify timestamp for snapman.sys |
066 | Key : Analysis.CPU.mSec |
069 | Key : Analysis.DebugAnalysisManager |
072 | Key : Analysis.Elapsed.mSec |
075 | Key : Analysis.Init.CPU.mSec |
078 | Key : Analysis.Init.Elapsed.mSec |
081 | Key : Analysis.Memory.CommitPeak.Mb |
085 | DUMP_FILE_ATTRIBUTES: 0x8 |
086 | Kernel Generated Triage Dump |
090 | BUGCHECK_P1: ffffffffc0000005 |
092 | BUGCHECK_P2: fffff805999ceafc |
094 | BUGCHECK_P3: ffffc0031ce1ce38 |
096 | BUGCHECK_P4: ffffc0031ce1c650 |
098 | EXCEPTION_RECORD: ffffc0031ce1ce38 -- (.exr 0xffffc0031ce1ce38) |
099 | ExceptionAddress: fffff805999ceafc (nvlddmkm+0x000000000001eafc) |
100 | ExceptionCode: c0000005 (Access violation) |
101 | ExceptionFlags: 00000000 |
103 | Parameter[0]: 0000000000000000 |
104 | Parameter[1]: 0000000000680146 |
105 | Attempt to read from address 0000000000680146 |
107 | CONTEXT: ffffc0031ce1c650 -- (.cxr 0xffffc0031ce1c650) |
108 | rax=0000000000680066 rbx=ffffd48e827a44a0 rcx=ffffd480030bf660 |
109 | rdx=ffffd48e9124a5a0 rsi=ffffd480030bf660 rdi=ffffd480030bf660 |
110 | rip=fffff805999ceafc rsp=ffffc0031ce1d070 rbp=ffffc0031ce1d170 |
111 | r8=0000000001017df8 r9=ffffc0031ce1d0f8 r10=0000000000000001 |
112 | r11=0000000000000018 r12=ffffc0031ce1d488 r13=ffffd48e89f6e6f0 |
113 | r14=ffffc0031ce1d480 r15=0000000000000000 |
114 | iopl=0 nv up ei ng nz na po nc |
115 | cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286 |
117 | fffff805`999ceafc ff90e0000000 call qword ptr [rax+0E0h] ds:002b:00000000`00680146=???????????????? |
118 | Resetting default scope |
120 | CUSTOMER_CRASH_COUNT: 1 |
124 | READ_ADDRESS: fffff80578d05450: Unable to get MiVisibleState |
125 | Unable to get NonPagedPoolStart |
126 | Unable to get NonPagedPoolEnd |
127 | Unable to get PagedPoolStart |
128 | Unable to get PagedPoolEnd |
129 | unable to get nt!MmSpecialPagesInUse |
132 | ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p 0x%p. %s. |
134 | EXCEPTION_CODE_STR: c0000005 |
136 | EXCEPTION_PARAMETER1: 0000000000000000 |
138 | EXCEPTION_PARAMETER2: 0000000000680146 |
140 | EXCEPTION_STR: 0xc0000005 |
143 | ffffc003`1ce1d070 ffffd48e`827a44a0 : ffffd48e`9124a5a0 ffffd48e`827a44a0 fffff805`7d67f2a0 ffffc003`1ce1d0b4 : nvlddmkm+0x1eafc |
144 | ffffc003`1ce1d078 ffffd48e`9124a5a0 : ffffd48e`827a44a0 fffff805`7d67f2a0 ffffc003`1ce1d0b4 00000000`00000000 : 0xffffd48e`827a44a0 |
145 | ffffc003`1ce1d080 ffffd48e`827a44a0 : fffff805`7d67f2a0 ffffc003`1ce1d0b4 00000000`00000000 00000000`00000000 : 0xffffd48e`9124a5a0 |
146 | ffffc003`1ce1d088 fffff805`7d67f2a0 : ffffc003`1ce1d0b4 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffd48e`827a44a0 |
147 | ffffc003`1ce1d090 ffffc003`1ce1d0b4 : 00000000`00000000 00000000`00000000 00000000`00000000 000000f0`00000f01 : snapman+0x2f2a0 |
148 | ffffc003`1ce1d098 00000000`00000000 : 00000000`00000000 00000000`00000000 000000f0`00000f01 ffffc409`000000e9 : 0xffffc003`1ce1d0b4 |
151 | SYMBOL_NAME: nvlddmkm+1eafc |
155 | IMAGE_NAME: nvlddmkm.sys |
157 | STACK_COMMAND: .cxr 0xffffc0031ce1c650 ; kb |
159 | BUCKET_ID_FUNC_OFFSET: 1eafc |
161 | FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function |
167 | FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3} |
169 | Followup: MachineOwner |
173 | Browse full module list |
175 | fffff805`999b0000 fffff805`9c2d6000 nvlddmkm T (no symbols) |
176 | Loaded symbol image file: nvlddmkm.sys |
177 | Image path: nvlddmkm.sys |
178 | Image name: nvlddmkm.sys |
179 | Browse all global symbols functions data |
180 | Timestamp: Thu Feb 10 05:19:23 2022 (6204762B) |
183 | Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 |
184 | Information from resource tables: |
186 | Browse full module list |
188 | fffff805`999b0000 fffff805`9c2d6000 nvlddmkm T (no symbols) |
189 | Loaded symbol image file: nvlddmkm.sys |
190 | Image path: nvlddmkm.sys |
191 | Image name: nvlddmkm.sys |
192 | Browse all global symbols functions data |
193 | Timestamp: Thu Feb 10 05:19:23 2022 (6204762B) |
196 | Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 |
197 | Information from resource tables: |
WinDbg Microsoft Store001 | Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64 |
002 | Copyright (c) Microsoft Corporation. All rights reserved. |
005 | Loading Dump File [C:\Users\user\Desktop\031922-14906-01.dmp] |
006 | Mini Kernel Dump File: Only registers and stack trace are available |
009 | ************* Path validation summary ************** |
010 | Response Time (ms) Location |
012 | Symbol search path is: srv* |
013 | Executable search path is: |
014 | Windows 10 Kernel Version 22000 MP (16 procs) Free x64 |
015 | Product: WinNt, suite: TerminalServer SingleUserTS |
017 | Kernel base = 0xfffff805`78000000 PsLoadedModuleList = 0xfffff805`78c29b90 |
018 | Debug session time: Sat Mar 19 17:06:42.448 2022 (UTC + 3:00) |
019 | System Uptime: 0 days 5:08:05.239 |
020 | Loading Kernel Symbols |
023 | Press ctrl-c (cdb, kd, ntsd) or ctrl- break (windbg) to abort symbol loads that take too long. |
024 | Run !sym noisy before .reload to track down problems loading symbols. |
026 | ............................................................. |
027 | ................................................................ |
028 | ................................................................ |
029 | ................................................................ |
032 | Loading unloaded module list |
034 | For analysis of this file, run !analyze -v |
035 | *** WARNING: Unable to verify timestamp for nvlddmkm.sys |
037 | fffff805`999ceafc ff90e0000000 call qword ptr [rax+0E0h] ds:002b:00000000`00680146=???????????????? |
039 | ******************************************************************************* |
043 | ******************************************************************************* |
045 | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) |
046 | This is a very common BugCheck. Usually the exception address pinpoints |
047 | the driver/ function that caused the problem. Always note this address |
048 | as well as the link date of the driver/image that contains this address. |
049 | Some common problems are exception code 0x80000003. This means a hard |
050 | coded breakpoint or assertion was hit, but this system was booted |
051 | /NODEBUG. This is not supposed to happen as developers should never have |
052 | hardcoded breakpoints in retail code, but ... |
053 | If this happens, make sure a debugger gets connected, and the |
054 | system is booted /DEBUG. This will let us see why this breakpoint is |
057 | Arg1: ffffffffc0000005, The exception code that was not handled |
058 | Arg2: fffff805999ceafc, The address that the exception occurred at |
059 | Arg3: ffffc0031ce1ce38, Exception Record Address |
060 | Arg4: ffffc0031ce1c650, Context Record Address |
071 | Key : Analysis.CPU.mSec |
074 | Key : Analysis.DebugAnalysisManager |
077 | Key : Analysis.Elapsed.mSec |
080 | Key : Analysis.Init.CPU.mSec |
083 | Key : Analysis.Init.Elapsed.mSec |
086 | Key : Analysis.Memory.CommitPeak.Mb |
090 | FILE_IN_CAB: 031922-14906-01.dmp |
092 | DUMP_FILE_ATTRIBUTES: 0x8 |
093 | Kernel Generated Triage Dump |
097 | BUGCHECK_P1: ffffffffc0000005 |
099 | BUGCHECK_P2: fffff805999ceafc |
101 | BUGCHECK_P3: ffffc0031ce1ce38 |
103 | BUGCHECK_P4: ffffc0031ce1c650 |
105 | EXCEPTION_RECORD: ffffc0031ce1ce38 -- (.exr 0xffffc0031ce1ce38) |
106 | ExceptionAddress: fffff805999ceafc (nvlddmkm+0x000000000001eafc) |
107 | ExceptionCode: c0000005 (Access violation) |
108 | ExceptionFlags: 00000000 |
110 | Parameter[0]: 0000000000000000 |
111 | Parameter[1]: 0000000000680146 |
112 | Attempt to read from address 0000000000680146 |
114 | CONTEXT: ffffc0031ce1c650 -- (.cxr 0xffffc0031ce1c650) |
115 | rax=0000000000680066 rbx=ffffd48e827a44a0 rcx=ffffd480030bf660 |
116 | rdx=ffffd48e9124a5a0 rsi=ffffd480030bf660 rdi=ffffd480030bf660 |
117 | rip=fffff805999ceafc rsp=ffffc0031ce1d070 rbp=ffffc0031ce1d170 |
118 | r8=0000000001017df8 r9=ffffc0031ce1d0f8 r10=0000000000000001 |
119 | r11=0000000000000018 r12=ffffc0031ce1d488 r13=ffffd48e89f6e6f0 |
120 | r14=ffffc0031ce1d480 r15=0000000000000000 |
121 | iopl=0 nv up ei ng nz na po nc |
122 | cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286 |
124 | fffff805`999ceafc ff90e0000000 call qword ptr [rax+0E0h] ds:002b:00000000`00680146=???????????????? |
125 | Resetting default scope |
127 | CUSTOMER_CRASH_COUNT: 1 |
131 | READ_ADDRESS: fffff80578d05450: Unable to get MiVisibleState |
132 | Unable to get NonPagedPoolStart |
133 | Unable to get NonPagedPoolEnd |
134 | Unable to get PagedPoolStart |
135 | Unable to get PagedPoolEnd |
136 | unable to get nt!MmSpecialPagesInUse |
139 | ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p 0x%p. %s. |
141 | EXCEPTION_CODE_STR: c0000005 |
143 | EXCEPTION_PARAMETER1: 0000000000000000 |
145 | EXCEPTION_PARAMETER2: 0000000000680146 |
147 | EXCEPTION_STR: 0xc0000005 |
150 | ffffc003`1ce1d070 ffffd48e`827a44a0 : ffffd48e`9124a5a0 ffffd48e`827a44a0 fffff805`7d67f2a0 ffffc003`1ce1d0b4 : nvlddmkm+0x1eafc |
151 | ffffc003`1ce1d078 ffffd48e`9124a5a0 : ffffd48e`827a44a0 fffff805`7d67f2a0 ffffc003`1ce1d0b4 00000000`00000000 : 0xffffd48e`827a44a0 |
152 | ffffc003`1ce1d080 ffffd48e`827a44a0 : fffff805`7d67f2a0 ffffc003`1ce1d0b4 00000000`00000000 00000000`00000000 : 0xffffd48e`9124a5a0 |
153 | ffffc003`1ce1d088 fffff805`7d67f2a0 : ffffc003`1ce1d0b4 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffd48e`827a44a0 |
154 | ffffc003`1ce1d090 ffffc003`1ce1d0b4 : 00000000`00000000 00000000`00000000 00000000`00000000 000000f0`00000f01 : snapman+0x2f2a0 |
155 | ffffc003`1ce1d098 00000000`00000000 : 00000000`00000000 00000000`00000000 000000f0`00000f01 ffffc409`000000e9 : 0xffffc003`1ce1d0b4 |
158 | SYMBOL_NAME: nvlddmkm+1eafc |
162 | IMAGE_NAME: nvlddmkm.sys |
164 | STACK_COMMAND: .cxr 0xffffc0031ce1c650 ; kb |
166 | BUCKET_ID_FUNC_OFFSET: 1eafc |
168 | FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function |
174 | FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3} |
176 | Followup: MachineOwner |
180 | Browse full module list |
182 | fffff805`999b0000 fffff805`9c2d6000 nvlddmkm T (no symbols) |
183 | Loaded symbol image file: nvlddmkm.sys |
184 | Image path: nvlddmkm.sys |
185 | Image name: nvlddmkm.sys |
186 | Browse all global symbols functions data |
187 | Timestamp: Thu Feb 10 05:19:23 2022 (6204762B) |
190 | Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 |
191 | Information from resource tables: |
193 | Browse full module list |
195 | fffff805`999b0000 fffff805`9c2d6000 nvlddmkm T (no symbols) |
196 | Loaded symbol image file: nvlddmkm.sys |
197 | Image path: nvlddmkm.sys |
198 | Image name: nvlddmkm.sys |
199 | Browse all global symbols functions data |
200 | Timestamp: Thu Feb 10 05:19:23 2022 (6204762B) |
203 | Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 |
204 | Information from resource tables: |
Исправлено: JIABP, 24.03.2022 21:33