Tech Community Live: Windows edition
Jun 05 2024, 07:30 AM - 11:30 AM (PDT)
Microsoft Tech Community

Problem with critical process died/Critical Error: Kernel-Power.

Copper Contributor

When I turn on something more demanding on the computer, such as a game, I honestly admit that I am unable to locate the source of the error myself, I made typical solutions to these errors according to the guides from the Internet https://www.partitionwizard.com/partitionmagic/critical-process-died.html
unfortunately it didn't help. Below I attach the kernel dump file, because I am not able to read it myself, I hope someone will help me identify the error.

 

Loading Dump File [C:\Windows\Minidump\072223-20093-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff804`13000000 PsLoadedModuleList = 0xfffff804`13c2a2d0
Debug session time: Sat Jul 22 20:16:20.197 2023 (UTC + 2:00)
System Uptime: 0 days 0:05:12.900
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols

Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`133fc0c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffab0f`01145f50=000000000000007a
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: ffffbee041a834b8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000010, error status (normally i/o status code)
Arg3: 0000200206277880, current process (virtual address for lock type 3, or PTE)
Arg4: ffffc08350697010, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3092

    Key  : Analysis.Elapsed.mSec
    Value: 7934

    Key  : Analysis.IO.Other.Mb
    Value: 20

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 34

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x7a

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0x7a_c0000010_UsbHub3!HUBMISC_GetDeviceInterfacePath

    Key  : Failure.Hash
    Value: {fe18c344-78e5-83e7-1211-87dca2f2f7ef}


BUGCHECK_CODE:  7a

BUGCHECK_P1: ffffbee041a834b8

BUGCHECK_P2: ffffffffc0000010

BUGCHECK_P3: 200206277880

BUGCHECK_P4: ffffc08350697010

FILE_IN_CAB:  072223-20093-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

ERROR_CODE: (NTSTATUS) 0xc0000010 - Okre lone   danie nie jest prawid ow  operacj  na urz dzeniu docelowym.

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffffab0f011462f0 -- (.trap 0xffffab0f011462f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc08359fec5f0 rbx=0000000000000000 rcx=ffffc08359fec5f0
rdx=fffffffff66aaa20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff804157bd6d2 rsp=ffffab0f01146488 rbp=000000000000009e
 r8=000000000000009e  r9=0000000000000436 r10=0000000077334855
r11=ffffc083506970ae r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
Wdf01000!memcpy+0x92:
fffff804`157bd6d2 0f100411        movups  xmm0,xmmword ptr [rcx+rdx] ds:ffffc083`50697010=????????????????????????????????
Resetting default scope

STACK_TEXT:  
ffffab0f`01145f48 fffff804`132d0ef9     : 00000000`0000007a ffffbee0`41a834b8 ffffffff`c0000010 00002002`06277880 : nt!KeBugCheckEx
ffffab0f`01145f50 fffff804`132d0375     : ffffab0f`00001000 ffffab0f`01146000 ffffab0f`011460e0 fffff804`00000000 : nt!MiWaitForInPageComplete+0x7d9
ffffab0f`01146040 fffff804`1326e818     : 00000000`c0033333 00000000`00000000 ffffc083`50697010 00000000`00000000 : nt!MiIssueHardFault+0x3c5
ffffab0f`01146150 fffff804`1340bbd8     : 00000000`00000436 fffff804`00000000 00000000`00001001 00000000`00000fff : nt!MmAccessFault+0x468
ffffab0f`011462f0 fffff804`157bd6d2     : fffff804`15801d04 00000000`000000a0 00000000`0000009e ffffac02`16b3aad0 : nt!KiPageFault+0x358
ffffab0f`01146488 fffff804`15801d04     : 00000000`000000a0 00000000`0000009e ffffac02`16b3aad0 ffffac02`27f5c588 : Wdf01000!memcpy+0x92 [minkernel\crts\crtw32\string\amd64\memcpy.asm @ 225] 
ffffab0f`01146490 fffff804`157fd546     : ffffac02`16c957b0 00000000`000000a0 00000000`c0000034 ffffc083`506dddd0 : Wdf01000!FxDuplicateUnicodeString+0xe8 [minkernel\wdf\framework\shared\support\stringutil.cpp @ 280] 
ffffab0f`011464e0 fffff804`0ef503ee     : ffffac02`12cd1a40 00000000`00000000 ffffac02`27f5c520 00000000`00000000 : Wdf01000!imp_WdfDeviceRetrieveDeviceInterfaceString+0x186 [minkernel\wdf\framework\shared\support\fxdeviceinterfaceapi.cpp @ 501] 
ffffab0f`01146550 fffff804`0ef92aca     : 000053fd`ed32e5b8 ffffab0f`01146770 00000000`00000002 00000000`00000000 : UsbHub3!HUBMISC_GetDeviceInterfacePath+0xea
ffffab0f`011465d0 fffff804`0ef930b1     : ffffac02`16b291f0 ffffac02`16b294e0 ffffac02`16b294e0 000053fd`ea0f5fd8 : UsbHub3!HUBDRIVER_EtwRundownUsbDevice+0x15a
ffffab0f`01146820 fffff804`0ef2123d     : 00000000`00000001 ffffac02`15966b10 00000000`00000000 00000000`44777445 : UsbHub3!HUBDRIVER_EtwEnableCallback+0x109
ffffab0f`01146890 fffff804`1371a808     : 00000000`00000000 00000000`00000000 ffffc083`4be00340 00000000`000007ff : UsbHub3!McGenControlCallbackV2+0x10d
ffffab0f`011468e0 fffff804`137180a0     : 00000000`00000000 ffffab0f`01146a99 ffffc083`77c08a10 ffffac02`160a46e0 : nt!EtwpSendDataBlock+0x13c
ffffab0f`01146a30 fffff804`13717c62     : fffff780`00000380 fffff780`00000380 ffffac02`160a46e0 ffffac02`12df2000 : nt!EtwpClearSessionAndUnreferenceEntry+0x26c
ffffab0f`01146b00 fffff804`13712f9e     : ffffab0f`01146bc0 ffffac02`12d3d600 00000000`00000000 00000000`00000004 : nt!EtwpDisableTraceProviders+0x4a
ffffab0f`01146b50 fffff804`13715866     : ffffac02`12d3d600 00000000`00000000 ffffffff`fffffffd ffffffff`fffffffd : nt!EtwpStopLoggerInstance+0x4e
ffffab0f`01146b90 fffff804`13326915     : ffffffff`fffffffd ffffac02`12d41080 00000000`00000080 fffff804`137154e0 : nt!EtwpLogger+0x386
ffffab0f`01146c10 fffff804`13404cf8     : ffffe780`1d880180 ffffac02`12d41080 fffff804`133268c0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffab0f`01146c60 00000000`00000000     : ffffab0f`01147000 ffffab0f`01141000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  UsbHub3!HUBMISC_GetDeviceInterfacePath+ea

MODULE_NAME: UsbHub3

IMAGE_NAME:  UsbHub3.sys

IMAGE_VERSION:  10.0.19041.3205

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  ea

FAILURE_BUCKET_ID:  0x7a_c0000010_UsbHub3!HUBMISC_GetDeviceInterfacePath

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {fe18c344-78e5-83e7-1211-87dca2f2f7ef}

Followup:     MachineOwner

 

0 Replies