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

Анонимные
2022-08-26T19:52:16+00:00

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

Windows для дома | Windows 10 | Устройства и драйверы

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

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

Ответы: 53

Сортировать по: Наиболее полезные
  1. Анонимные
    2022-08-29T23:05:20+00:00

    *                                                                             *
    *                        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 Без комментариев
  2. Анонимные
    2022-08-29T23:02:49+00:00

    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the BugCheck
    Arg2: fffff80569ea7358, Address of the instruction which caused the BugCheck
    Arg3: ffff96059ac8a880, Address of the context record for the exception that caused the BugCheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    KEY_VALUES_STRING: 1
    
        Key  : Analysis.CPU.mSec
        Value: 4139
    
        Key  : Analysis.DebugAnalysisManager
        Value: Create
    
        Key  : Analysis.Elapsed.mSec
        Value: 9356
    
        Key  : Analysis.Init.CPU.mSec
        Value: 546
    
        Key  : Analysis.Init.Elapsed.mSec
        Value: 33076
    
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 99
    
        Key  : Bugcheck.Code.DumpHeader
        Value: 0x3b
    
        Key  : Bugcheck.Code.Register
        Value: 0x3b
    
        Key  : Dump.Attributes.AsUlong
        Value: 8
    
        Key  : Dump.Attributes.KernelGeneratedTriageDump
        Value: 1
    
    FILE_IN_CAB:  082822-9437-01.dmp
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    BUGCHECK_CODE:  3b
    
    BUGCHECK_P1: c0000005
    
    BUGCHECK_P2: fffff80569ea7358
    
    BUGCHECK_P3: ffff96059ac8a880
    
    BUGCHECK_P4: 0
    
    CONTEXT:  ffff96059ac8a880 -- (.cxr 0xffff96059ac8a880)
    rax=0000080000000000 rbx=ffff9e83c4800290 rcx=0000080000000000
    rdx=ffff9e83d3bb0c68 rsi=0000000000000037 rdi=ffff9e83d3bb0c60
    rip=fffff80569ea7358 rsp=ffff96059ac8b288 rbp=ffff96059ac8b318
     r8=ffff9e83d3902c68  r9=ffff9e83d3902c68 r10=0000000000000000
    r11=ffff96059ac8b490 r12=0000000000000000 r13=ffff9e83d3bb0000
    r14=0000000000000000 r15=0000000000000038
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
    nt!RtlRbRemoveNode+0x148:
    fffff805`69ea7358 488b01          mov     rax,qword ptr [rcx] ds:002b:00000800`00000000=????????????????
    Resetting default scope
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    BLACKBOXWINLOGON: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  MSI.CentralSer
    
    STACK_TEXT:  
    ffff9605`9ac8b288 fffff805`69ea5b75     : ffff9605`9ac8b318 00000000`00000037 ffff9e83`d3bb0c60 00000000`00000038 : nt!RtlRbRemoveNode+0x148
    ffff9605`9ac8b2a0 fffff805`69ea595a     : 00000002`9ac8b400 ffff9e83`c4800200 fffff805`815fa4c8 00000000`00000000 : nt!RtlpHpVsChunkSplit+0x45
    ffff9605`9ac8b360 fffff805`69ea8ed8     : 00000000`00000000 00000000`00000360 ffff9605`9ac8b4a1 00000000`00000360 : nt!RtlpHpVsContextAllocateInternal+0x1fa
    ffff9605`9ac8b3c0 fffff805`6a5b21c4     : 00000000`00000000 ffff9e83`cb9bd230 00000000`4b677844 fffff805`736faea3 : nt!ExAllocateHeapPool+0x888
    ffff9605`9ac8b500 fffff805`73602d1d     : 00000000`00000000 ffff9605`9ac8bb80 ffffffff`ffffffff 00000000`00000000 : nt!ExAllocatePoolWithTag+0x64
    ffff9605`9ac8b550 fffff805`736f85de     : 00000000`00000000 00000000`00000000 ffffc60f`b7f8f078 ffffffff`ffffffff : dxgkrnl!operator new+0x31
    ffff9605`9ac8b580 fffff805`6a00a2b8     : 00000000`00000000 ffffc60f`baf93080 00007ff9`3b29f290 ffffc60f`00000000 : dxgkrnl!DxgkEscape+0x31e
    ffff9605`9ac8bb00 00007ff9`3b2a3af4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
    00000000`04bde6f8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`3b2a3af4
    
    SYMBOL_NAME:  dxgkrnl!operator new+31
    
    MODULE_NAME: dxgkrnl
    
    IMAGE_NAME:  dxgkrnl.sys
    
    IMAGE_VERSION:  10.0.19041.1865
    
    STACK_COMMAND:  .cxr 0xffff96059ac8a880 ; kb
    
    BUCKET_ID_FUNC_OFFSET:  31
    
    FAILURE_BUCKET_ID:  AV_dxgkrnl!operator_new
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    FAILURE_ID_HASH:  {c60f340f-4f53-1790-5405-773a900f1a75}
    
    Followup:     MachineOwner
    ---------
    

    Этот ответ помог вам?

    Комментариев: 0 Без комментариев
  3. Анонимные
    2022-08-29T23:00:37+00:00

    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000080000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff8042e65e500, address which referenced memory
    
    Debugging Details:
    ------------------
    
    KEY_VALUES_STRING: 1
    
        Key  : Analysis.CPU.mSec
        Value: 3405
    
        Key  : Analysis.DebugAnalysisManager
        Value: Create
    
        Key  : Analysis.Elapsed.mSec
        Value: 14049
    
        Key  : Analysis.Init.CPU.mSec
        Value: 703
    
        Key  : Analysis.Init.Elapsed.mSec
        Value: 37899
    
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 90
    
        Key  : Bugcheck.Code.DumpHeader
        Value: 0xa
    
        Key  : Bugcheck.Code.Register
        Value: 0xa
    
        Key  : Dump.Attributes.AsUlong
        Value: 8
    
        Key  : Dump.Attributes.KernelGeneratedTriageDump
        Value: 1
    
    FILE_IN_CAB:  082722-10687-01.dmp
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    BUGCHECK_CODE:  a
    
    BUGCHECK_P1: 80000000000
    
    BUGCHECK_P2: 2
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: fffff8042e65e500
    
    READ_ADDRESS: fffff8042f0fb390: 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
     0000080000000000 
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    BLACKBOXWINLOGON: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  svchost.exe
    
    TRAP_FRAME:  ffffda003d0b4bb0 -- (.trap 0xffffda003d0b4bb0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff8042f04e440 rbx=0000000000000000 rcx=0000080000000000
    rdx=0000000000000003 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8042e65e500 rsp=ffffda003d0b4d48 rbp=0000000000000000
     r8=ffffda003d0b4e30  r9=0000000000000000 r10=ffffc98a6bb07a70
    r11=ffff79ff9a400000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nt!MiBuildWakeList+0x14:
    fffff804`2e65e500 4c8b01          mov     r8,qword ptr [rcx] ds:00000800`00000000=????????????????
    Resetting default scope
    
    STACK_TEXT:  
    ffffda00`3d0b4a68 fffff804`2e80a869     : 00000000`0000000a 00000800`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffda00`3d0b4a70 fffff804`2e806b69     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    ffffda00`3d0b4bb0 fffff804`2e65e500     : fffff804`2e65d43e ffffc98a`00000000 ffffc98a`6f15da90 ffffc98a`6afafa90 : nt!KiPageFault+0x469
    ffffda00`3d0b4d48 fffff804`2e65d43e     : ffffc98a`00000000 ffffc98a`6f15da90 ffffc98a`6afafa90 00000000`6573504d : nt!MiBuildWakeList+0x14
    ffffda00`3d0b4d50 fffff804`2e65d1ae     : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00040246 : nt!MiCheckControlArea+0x27e
    ffffda00`3d0b4dd0 fffff804`2e74d557     : 00000000`00000000 00000000`00000000 ffffc98a`6ef54cb0 00000000`00000000 : nt!MiDereferenceControlAreaBySection+0x2a
    ffffda00`3d0b4e00 fffff804`31049762     : 00000000`00000100 ffffda00`3d0b4f70 ffffc98a`6ef54cb0 00000000`00000000 : nt!MmGetImageFileSignatureInformation+0x97
    ffffda00`3d0b4e30 fffff804`2eaf562a     : 00000000`00000000 ffffda00`3d0b4f90 ffff9e81`a2cd9db0 fffff804`318caf5c : CI!CiGetFileCache+0x52
    ffffda00`3d0b4ec0 fffff804`318f38c3     : 00000000`00000000 ffff9e81`00000050 ffffda00`3d0b4f90 ffff9e81`a2cd9db0 : nt!SeGetCachedSigningLevel+0x4a
    ffffda00`3d0b4f10 00000000`00000000     : ffff9e81`00000050 ffffda00`3d0b4f90 ffff9e81`a2cd9db0 00000000`00000000 : WdFilter+0x338c3
    
    SYMBOL_NAME:  CI!CiGetFileCache+52
    
    MODULE_NAME: CI
    
    IMAGE_NAME:  CI.dll
    
    IMAGE_VERSION:  10.0.19041.1865
    
    STACK_COMMAND:  .cxr; .ecxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  52
    
    FAILURE_BUCKET_ID:  AV_CI!CiGetFileCache
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    FAILURE_ID_HASH:  {9c87998f-2b3a-bf36-cb58-4513704c514b}
    
    Followup:     MachineOwner
    ---------
    

    Этот ответ помог вам?

    Комментариев: 0 Без комментариев
  4. Анонимные
    2022-08-29T22:57:56+00:00

    *                                                                             *
    *                        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: fffff00658ba7e08, memory referenced.
    Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
    bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the processor decided the fault was due to a corrupted PTE.
    bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
    - ARM64: bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
    Arg3: fffff80658b74213, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000002, (reserved)
    
    Debugging Details:
    ------------------
    
    KEY_VALUES_STRING: 1
    
        Key  : AV.Type
        Value: Read
    
        Key  : Analysis.CPU.mSec
        Value: 4124
    
        Key  : Analysis.DebugAnalysisManager
        Value: Create
    
        Key  : Analysis.Elapsed.mSec
        Value: 11041
    
        Key  : Analysis.Init.CPU.mSec
        Value: 1186
    
        Key  : Analysis.Init.Elapsed.mSec
        Value: 88648
    
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 99
    
        Key  : Bugcheck.Code.DumpHeader
        Value: 0x50
    
        Key  : Bugcheck.Code.Register
        Value: 0x50
    
        Key  : Dump.Attributes.AsUlong
        Value: 8
    
        Key  : Dump.Attributes.KernelGeneratedTriageDump
        Value: 1
    
    FILE_IN_CAB:  082722-10468-01.dmp
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    BUGCHECK_CODE:  50
    
    BUGCHECK_P1: fffff00658ba7e08
    
    BUGCHECK_P2: 0
    
    BUGCHECK_P3: fffff80658b74213
    
    BUGCHECK_P4: 2
    
    READ_ADDRESS: fffff80653efb390: 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
     fffff00658ba7e08 
    
    MM_INTERNAL_CODE:  2
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    BLACKBOXWINLOGON: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  NVIDIA Web Hel
    
    TRAP_FRAME:  ffff840f2ff395e0 -- (.trap 0xffff840f2ff395e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0030003300490024 rbx=0000000000000000 rcx=ffffba8d79644598
    rdx=00003578df563870 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80658b74213 rsp=ffff840f2ff39778 rbp=ffff840f2ff3a4c0
     r8=0000000000000008  r9=0000000000000001 r10=fffff8065352b8a0
    r11=ffff840f2ff395c0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz ac pe nc
    Ntfs!memcmp+0x93:
    fffff806`58b74213 483b0411        cmp     rax,qword ptr [rcx+rdx] ds:fffff006`58ba7e08=????????????????
    Resetting default scope
    
    STACK_TEXT:  
    ffff840f`2ff39338 fffff806`5363af53     : 00000000`00000050 fffff006`58ba7e08 00000000`00000000 ffff840f`2ff395e0 : nt!KeBugCheckEx
    ffff840f`2ff39340 fffff806`5346d0e0     : ffffe207`fd782700 00000000`00000000 ffff840f`2ff39660 00000000`00000000 : nt!MiSystemFault+0x1afe23
    ffff840f`2ff39440 fffff806`53606a5e     : ffff940b`08fe7180 fffff806`58c1d809 00000000`00000000 ffff840f`2ff3a4c0 : nt!MmAccessFault+0x400
    ffff840f`2ff395e0 fffff806`58b74213     : fffff806`58c1d27b 00000000`00000003 00000000`00000000 ffffe207`fd7ea010 : nt!KiPageFault+0x35e
    ffff840f`2ff39778 fffff806`58c1d27b     : 00000000`00000003 00000000`00000000 ffffe207`fd7ea010 00000000`00000000 : Ntfs!memcmp+0x93
    ffff840f`2ff39780 fffff806`58c1cd66     : 00000000`00010000 ffff840f`2ff39a30 ffffe207`f0e77000 80000003`f4435921 : Ntfs!NtfsFindInFileRecord+0x10b
    ffff840f`2ff39810 fffff806`58c1a997     : ffff840f`2ff39a30 ffffe207`fd7ea170 00000000`00000000 ffff840f`2ff39aa0 : Ntfs!NtfsLookupInFileRecord+0x186
    ffff840f`2ff398c0 fffff806`58c24883     : ffff940b`08fe7180 00000000`00000000 ffff940b`08306b00 ffff940b`0fa7e340 : Ntfs!FindFirstIndexEntry+0x57
    ffff840f`2ff39970 fffff806`58c23d17     : ffff940b`1180a010 00000000`00000000 ffffe207`fd7ea1c8 fffff806`5346163e : Ntfs!NtfsUpdateFileNameInIndex+0x273
    ffff840f`2ff39bf0 fffff806`58c2376e     : 00000000`00000000 ffff940b`0ff071b0 00000000`00000000 00000000`00000000 : Ntfs!NtfsUpdateFileNameInParent+0x167
    ffff840f`2ff39de0 fffff806`58c39e5c     : ffff840f`2ff3a4c0 ffff940b`1180a010 ffff840f`2ff3a080 ffff840f`2ff3a038 : Ntfs!NtfsUpdateDuplicateInfo+0x18e
    ffff840f`2ff39f80 fffff806`58c2b9dd     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff840f`2ff3a490 : Ntfs!NtfsCommonCleanup+0x482c
    ffff840f`2ff3a420 fffff806`534abac5     : ffff940b`11b558b0 ffff840f`2ff3a840 ffff940b`1180a010 ffff940b`08fb6440 : Ntfs!NtfsFsdCleanup+0x1bd
    ffff840f`2ff3a770 fffff806`52b370cf     : 00000000`00000005 ffff840f`2ff3a820 ffff940b`11b558b0 ffff940b`1180a010 : nt!IofCallDriver+0x55
    ffff840f`2ff3a7b0 fffff806`52b34a03     : ffff840f`2ff3a840 00000000`00000000 00000000`00000000 ffff940b`11c2e080 : FLTMGR!FltIsCallbackDataDirty+0x42f
    ffff840f`2ff3a820 fffff806`534abac5     : ffff940b`11b39190 fffff806`53462c7d 00000000`00000000 fffff806`534abfb7 : FLTMGR!FltDecodeParameters+0x683
    ffff840f`2ff3a880 fffff806`537f0b3a     : 00000000`00000001 ffff940b`11b39190 00000000`00000000 00000000`000c0042 : nt!IofCallDriver+0x55
    ffff840f`2ff3a8c0 fffff806`5382229f     : ffff940b`11c2e080 00000000`00000001 ffffe207`00000000 ffff940b`11b39160 : nt!IopCloseFile+0x17a
    ffff840f`2ff3a950 fffff806`5382627c     : 00000000`00000320 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObCloseHandleTableEntry+0x51f
    ffff840f`2ff3aa90 fffff806`5360a2b8     : 00000000`00023900 ffff940b`11d130c0 ffff840f`2ff3ab80 00000000`02a3e4b8 : nt!NtClose+0xec
    ffff840f`2ff3ab00 00000000`77b81cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
    00000000`02a3edb8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b81cfc
    
    SYMBOL_NAME:  Ntfs!memcmp+93
    
    MODULE_NAME: Ntfs
    
    IMAGE_NAME:  Ntfs.sys
    
    IMAGE_VERSION:  10.0.19041.1193
    
    STACK_COMMAND:  .cxr; .ecxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  93
    
    FAILURE_BUCKET_ID:  AV_R_(null)_Ntfs!memcmp
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    FAILURE_ID_HASH:  {96a1ec1c-2f61-79f4-750a-a962f4ee7c3e}
    
    Followup:     MachineOwner
    ---------
    

    Этот ответ помог вам?

    Комментариев: 0 Без комментариев
  5. Alexandr S 106.7K Баллы репутации Независимый помощник
    2022-08-29T22:18:02+00:00

    Теперь по шагам:

    1. Запустите программу.
    2. Файл-Open Dump File-Browse. Выберите файл дампа и подтвердите его открытие кнопкой Open
    3. Дождитесь загрузки и окончания первичной обработки (в окне обработки Command будет текст в конце которого строка "For analysis of this file, run !analyze -v", а командная строка ниже примет вид "0: kd>" с мигающим левее текстовым курсором).
    4. Кликните на "!analyze -v" и также дождитесь окончания анализа (командная строка снова примет вид "0: kd>" с курсором.
    5. Пролистайте окно Command назад до "!analyze -v" и выделите мышью текст, начиная от "Bugcheck Analysis" (в красивой рамочке из звездочек) и до конца текста.
    6. После выделения текста нажмите сочетание клавиш Ctrl+C
    7. Здесь (в данной теме) в сообщении либо кликните ПКМ и "Вставить", либо просто кликните на свободном месте ЛКМ и нажмите Clrl+V.

    .........

    P.S. Через несколько минут я добавлю сюда скриншоты.

    После этого закрыть приложение и запустить снова. Повторить те же процедуры со следующим файлом дампа.

    Этот ответ помог вам?

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