После смены озу начали вылетать синие экраны смерти с разными ошибками

Анонимные

Стояло две планки по 4гб озу, решил поставить другие две планки по 8гб, после чего спустя какое-то время начали вылетать синие экраны смерти с разными ошибками но гугля их одной из причин была именно озу.
Озу которую поставил: Corsair Vengeance LPX Black DDR4 16GB (2x8GB) 2666MHz CL16 1.20V
Материнская плата: Asus PRIME B450M-K
Процессор: Ryzen 3 2200G
Вроде бы смотрел и эта озу поддерживается и процессором и мат платой, залезал в биос и выставлена частота 2666MHz
Подскажите в чем проблема и можно ли ее решить как-то без замены озу, или поможет только замена? Старые плашки по ошибке поторопился и выкинул.

Заблокированный вопрос. Этот вопрос был перенесен из сообщества службы поддержки Майкрософт. Вы можете проголосовать о его полезности, но не можете добавлять комментарии или ответы, а также подписаться на этот вопрос.

Комментариев: 0

Ответы: 53

Alexandr S 106.7K Баллы репутации Независимый помощник

2022-08-30T00:20:59+00:00

Нажмите сочетание клавиш Win+Q и в строке поиска введите команду slmgr.vbs /dlv (лучше не вручную, а скопировать/вставить). И в результатах поиска кликните на "slmgr.vbs /dlv Выполнить команду".

По поводу установленных программ - уточните, где и как Вы получили лицензию на Офис 2010?
Этот ответ помог вам?

Комментариев: 0 Без комментариев
Анонимные

2022-08-29T23:43:11+00:00

а что такое окна команды?
Этот ответ помог вам?

Комментариев: 0 Без комментариев
Alexandr S 106.7K Баллы репутации Независимый помощник

2022-08-29T23:34:26+00:00
Кратко (чтоб не расписывать на несколько страниц...):

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

Проблема указывает на неполадки чтения и записи данных на диск. Источником проблемы может быть неполадки с памятью (FAILURE_BUCKET_ID: AV_R_(null)_Ntfs!memcmp)

IMAGE_NAME: CI.dll

Проблема библиотеки проверки целостности драйверов и компонентов из за ошибок кэша (FAILURE_BUCKET_ID: AV_CI!CiGetFileCache)

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

Критическая ошибка при выполнении подпрограммы системной службы, связанной с DirectX (FAILURE_BUCKET_ID: AV_dxgkrnl!operator_new)

PROCESS_NAME: System

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

А вот это очень специфичный "маркер". Выложите здесь скриншоты:
1. Окна Панель управления-Программы и компоненты со списком всех установленных программ.
2. Окна команды slmgr.vbs /dlv
MODULE_NAME: hardware

IMAGE_NAME: hardware_ram

Вот это плохо:(

Аппаратная проблема с памятью.
Этот ответ помог вам?

Комментариев: 0 Без комментариев

Анонимные

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the BugCheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffa618037d31d8, Virtual address for the attempted write.
Arg2: 8a00000000200121, PTE contents.
Arg3: fffffc034e696d80, (reserved)
Arg4: 000000000000000a, (reserved)

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2749

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2829

    Key  : Analysis.Init.CPU.mSec
    Value: 593

    Key  : Analysis.Init.Elapsed.mSec
    Value: 6695

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xbe

    Key  : Bugcheck.Code.Register
    Value: 0xbe

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Memory.System.Errors.BadPageCount
    Value: 158

    Key  : Memory.System.Errors.ScrubErrors
    Value: 158

FILE_IN_CAB:  082822-10406-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  be

BUGCHECK_P1: ffffa618037d31d8

BUGCHECK_P2: 8a00000000200121

BUGCHECK_P3: fffffc034e696d80

BUGCHECK_P4: a

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  NVIDIA Share.e

BAD_PAGES_DETECTED: 9e

TRAP_FRAME:  fffffc034e696d80 -- (.trap 0xfffffc034e696d80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffa618037d31c0
rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8060351eafd rsp=fffffc034e696f10 rbp=ffffa618037d31c0
 r8=0000000000000003  r9=ffffc43ffeb76d98 r10=fffffc034e696ed8
r11=ffffc46231188000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiLockSetPfnPriority+0x11:
fffff806`0351eafd f0480fba69183f  lock bts qword ptr [rcx+18h],3Fh ds:ffffa618`037d31d8=0000000000000000
Resetting default scope

STACK_TEXT:  
fffffc03`4e696b88 fffff806`03679782     : 00000000`000000be ffffa618`037d31d8 8a000000`00200121 fffffc03`4e696d80 : nt!KeBugCheckEx
fffffc03`4e696b90 fffff806`0346d1cf     : 8a000000`00200121 00000000`00000003 fffffc03`4e696e00 00000000`00000000 : nt!MiRaisedIrqlFault+0x1413a6
fffffc03`4e696be0 fffff806`03606a5e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x4ef
fffffc03`4e696d80 fffff806`0351eafd     : ffffb382`95d27700 00000000`00000001 ffffc43f`feb76470 ffffc43f`feb76470 : nt!KiPageFault+0x35e
fffffc03`4e696f10 fffff806`0343f6a1     : ffffa600`00000000 00000000`00000000 ffffa600`00000000 fffff806`034351e0 : nt!MiLockSetPfnPriority+0x11
fffffc03`4e696f40 fffff806`0343f4cf     : fffffc03`4e697560 ffffc43f`feb76470 ffffa618`037d31c0 00000000`00000000 : nt!MiAgePteWorker+0x1a1
fffffc03`4e696fa0 fffff806`0346c166     : fffffc03`4e697560 ffffc43f`feb76470 00000000`00000000 06000801`29bb4025 : nt!MiAgePte+0x51f
fffffc03`4e697040 fffff806`0346c27b     : ffffc462`00000000 ffffb382`95d27700 00000000`00000000 fffffc03`4e6975b0 : nt!MiWalkPageTablesRecursively+0x776
fffffc03`4e6970e0 fffff806`0346c27b     : ffffc462`310fffa8 ffffb382`95d27700 00000000`00000001 fffffc03`4e6975c0 : nt!MiWalkPageTablesRecursively+0x88b
fffffc03`4e697180 fffff806`0346c27b     : ffffc462`310ff000 ffffb382`95d27700 00000000`00000002 fffffc03`4e6975d0 : nt!MiWalkPageTablesRecursively+0x88b
fffffc03`4e697220 fffff806`0349ca6b     : 00000000`00000000 ffffb382`95d27700 00000000`00000003 fffffc03`4e6975e0 : nt!MiWalkPageTablesRecursively+0x88b
fffffc03`4e6972c0 fffff806`0349c501     : fffffc03`4e697560 fffff806`00000000 00000000`00000002 00000000`00000000 : nt!MiWalkPageTables+0x36b
fffffc03`4e6973c0 fffff806`0349bc09     : 00000000`00000000 00000000`00000000 ffffc581`d60c51c0 00000000`00000000 : nt!MiAgeWorkingSet+0x3d1
fffffc03`4e6978d0 fffff806`0349b417     : 00000000`00000000 fffffc03`4e697a80 fffffc03`4e697a40 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0x3c9
fffffc03`4e6979c0 fffff806`034d2120     : fffff806`03e50b80 fffffc03`4e697a80 00000000`00001a58 fffff806`00000200 : nt!MiProcessWorkingSets+0x227
fffffc03`4e697a60 fffff806`035b69f7     : 00000000`00000002 00000000`00000002 00000000`ffffffff ffffc581`d2f36180 : nt!MiWorkingSetManager+0x110
fffffc03`4e697b20 fffff806`03558235     : ffffb382`8c30f040 00000000`00000080 fffff806`035b68a0 00000000`00000000 : nt!KeBalanceSetManager+0x157
fffffc03`4e697c10 fffff806`035fff48     : ffffc581`d2e80180 ffffb382`8c30f040 fffff806`035581e0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffc03`4e697c60 00000000`00000000     : fffffc03`4e698000 fffffc03`4e692000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME:  PAGE_NOT_ZERO

MODULE_NAME: hardware

IMAGE_NAME:  hardware_ram

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  PAGE_NOT_ZERO_AV

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {91fefd05-7a2b-5d37-e27f-7af624353ffc}

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

 *** Memory manager detected 158 instance(s) of page corruption, target is likely to have memory corruption.

Комментариев: 0

Анонимные

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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: fffff804674fbe9d, The address that the exception occurred at
Arg3: ffffd1078ad24a08, Parameter 0 of the exception
Arg4: ffffd1078ad24240, Parameter 1 of the exception

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7374

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 8497

    Key  : Analysis.Init.CPU.mSec
    Value: 639

    Key  : Analysis.Init.Elapsed.mSec
    Value: 18622

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x1e

    Key  : Bugcheck.Code.Register
    Value: 0x1e

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

FILE_IN_CAB:  082822-9640-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff804674fbe9d

BUGCHECK_P3: ffffd1078ad24a08

BUGCHECK_P4: ffffd1078ad24240

EXCEPTION_PARAMETER1:  ffffd1078ad24a08

EXCEPTION_PARAMETER2:  ffffd1078ad24240

WRITE_ADDRESS: fffff80467efb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffffd1078ad24240 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:  
ffffd107`8ad239c8 fffff804`6770f93f     : 00000000`0000001e ffffffff`c0000005 fffff804`674fbe9d ffffd107`8ad24a08 : nt!KeBugCheckEx
ffffd107`8ad239d0 fffff804`67611f26     : ffffd107`8ad24240 fffff804`67542a45 ffffd107`8ad24c40 fffff804`674fbe9d : nt!KiFatalFilter+0x1f
ffffd107`8ad23a10 fffff804`675cde62     : fffff804`00000002 fffff804`672d2360 ffffd107`8ad20000 ffffd107`8ad26000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
ffffd107`8ad23a50 fffff804`676017b2     : fffff804`672d2360 ffffd107`8ad24030 fffff804`675cddc0 00000000`00000000 : nt!_C_specific_handler+0xa2
ffffd107`8ad23ac0 fffff804`674e2467     : ffffd107`8ad24030 00000000`00000000 ffffd107`8ad25340 fffff804`674dae28 : nt!RtlpExecuteHandlerForException+0x12
ffffd107`8ad23af0 fffff804`674e1066     : ffffd107`8ad24a08 ffffd107`8ad24740 ffffd107`8ad24a08 00000000`00000000 : nt!RtlDispatchException+0x297
ffffd107`8ad24210 fffff804`6760a9ac     : 00000000`00001000 ffffd107`8ad24ab0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
ffffd107`8ad248d0 fffff804`67606b43     : ffffe48f`21010340 ffffe48f`237e18ff 00000000`00000706 01800040`00000000 : nt!KiExceptionDispatch+0x12c
ffffd107`8ad24ab0 fffff804`674fbe9d     : 00000000`00000000 ffffe48f`2846b1b0 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x443
ffffd107`8ad24c40 fffff804`69072da8     : 00000000`00000000 ffffe48f`2c607370 00000000`00000000 ffffe48f`237e2410 : nt!ExReinitializeResourceLite+0xfd
ffffd107`8ad24ca0 fffff804`68f59412     : ffffe48f`2b732328 ffffd30b`d9d4f800 ffffd30b`d9d4f7c0 ffffd107`00008000 : Ntfs!NtfsDeleteFcb+0x1f8
ffffd107`8ad24d20 fffff804`690733fa     : ffffe48f`2b732328 ffffe48f`237e2180 ffffd30b`d9d305a0 ffffd30b`d9d30a00 : Ntfs!NtfsTeardownFromLcb+0x272
ffffd107`8ad24dc0 fffff804`68f58f56     : ffffe48f`2b732328 ffffd30b`d9d30700 ffffd30b`d9d30a00 ffffd30b`d9d305a0 : Ntfs!NtfsTeardownStructures+0xea
ffffd107`8ad24e40 fffff804`6903530f     : ffffe48f`2b732328 00000000`00000000 00000000`00000000 ffffd30b`d9d30500 : Ntfs!NtfsDecrementCloseCounts+0xf6
ffffd107`8ad24ea0 fffff804`6904b1c4     : ffffe48f`2b732328 ffffd30b`d9d30700 ffffd30b`d9d305a0 ffffe48f`237e2180 : Ntfs!NtfsCommonClose+0xadf
ffffd107`8ad24f70 fffff804`690a1f16     : ffffe48f`237b7000 00000000`00000000 ffffd107`8ad253f0 fffff804`674abac5 : Ntfs!NtfsFspCloseInternal+0x244
ffffd107`8ad250d0 fffff804`690526d0     : 00000000`00000000 00000000`00000000 ffffe48f`237e2180 00000000`00000001 : Ntfs!NtfsFlushVolume+0x15e
ffffd107`8ad251f0 fffff804`69052b19     : ffffe48f`2b832d98 ffffe48f`2b1448b0 ffffe48f`2b832d01 ffffd107`8ad25420 : Ntfs!NtfsCommonFlushBuffers+0x8cc
ffffd107`8ad25310 fffff804`674dae28     : ffffd107`8ad25420 ffffe48f`2b832d98 00100003`00000000 ffffe48f`2b1448b0 : Ntfs!NtfsCommonFlushBuffersCallout+0x19
ffffd107`8ad25340 fffff804`674dad9d     : fffff804`69052b00 ffffd107`8ad25420 00000000`00000000 ffffe48f`237e1280 : nt!KeExpandKernelStackAndCalloutInternal+0x78
ffffd107`8ad253b0 fffff804`6909454b     : 00000000`00000000 ffffe48f`2f4069b0 ffffd107`8ad26000 00000000`00000310 : nt!KeExpandKernelStackAndCalloutEx+0x1d
ffffd107`8ad253f0 fffff804`69094475     : 00000000`00000000 ffffe48f`236253c0 ffffd107`8ad25488 00000000`00000000 : Ntfs!NtfsCommonFlushBuffersOnNewStack+0x67
ffffd107`8ad25460 fffff804`674abac5     : ffffe48f`23a20830 ffffe48f`2b1448b0 ffffe48f`2b832d98 ffffd107`8ad25488 : Ntfs!NtfsFsdFlushBuffers+0xe5
ffffd107`8ad254d0 fffff804`62ea70cf     : ffffd107`8ad20005 00000000`00000000 ffffd107`8ad25530 00000000`00000000 : nt!IofCallDriver+0x55
ffffd107`8ad25510 fffff804`62ea4a03     : ffffd107`8ad255a0 00000000`00000000 00000000`00000000 ffffe48f`2356fd00 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f
ffffd107`8ad25580 fffff804`674abac5     : ffffe48f`2b1448b0 ffffe48f`20aaa200 ffffd107`8ad25810 ffffb080`c140e000 : FLTMGR!FltpDispatch+0xa3
ffffd107`8ad255e0 fffff804`6781b538     : ffffd107`8ad25810 ffffe48f`2b1448b0 00000000`00000001 00000000`00000000 : nt!IofCallDriver+0x55
ffffd107`8ad25620 fffff804`678efe19     : ffffe48f`00000000 ffffd107`8ad25810 00000000`00000000 ffffd107`8ad25810 : nt!IopSynchronousServiceTail+0x1a8
ffffd107`8ad256c0 fffff804`678efc06     : ffffe48f`2920f080 00000000`00000000 ffffe48f`237e1040 00000000`00000000 : nt!NtFlushBuffersFileEx+0x1f9
ffffd107`8ad25750 fffff804`6760a2b8     : fffff804`67200000 fffff804`674ae0ce ffffd107`8ad259e0 00000000`00000000 : nt!NtFlushBuffersFile+0x16
ffffd107`8ad25790 fffff804`675fc750     : fffff804`67b95f9a ffffd107`8871e380 ffffe48f`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
ffffd107`8ad25928 fffff804`67b95f9a     : ffffd107`8871e380 ffffe48f`00000000 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
ffffd107`8ad25930 fffff804`67558235     : ffffe48f`2920f080 ffffe48f`2920f080 fffff804`67b95e10 00000000`00000000 : nt!PopFlushVolumeWorker+0x18a
ffffd107`8ad25c10 fffff804`675fff48     : ffffb080`c1400180 ffffe48f`2920f080 fffff804`675581e0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffd107`8ad25c60 00000000`00000000     : ffffd107`8ad26000 ffffd107`8ad20000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME:  nt!ExReinitializeResourceLite+fd

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.1889

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  fd

FAILURE_BUCKET_ID:  AV_nt!ExReinitializeResourceLite

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d46532d4-a1d4-e059-087f-428af1b2ce29}

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

Комментариев: 0