BSOD's on start up and reliability history showing hardware failure

Page 2 of 2 FirstFirst 12

  1. Posts : 73
    Windows 8.1 Enterprise x64
       #11

    Code:
    Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\michal01\Downloads\041119-9203-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\SymCache*https://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\SymCache*https://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 10 Kernel Version 17763 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0xfffff804`7a299000 PsLoadedModuleList = 0xfffff804`7a6b49f0
    Debug session time: Thu Apr 11 15:51:06.526 2019 (UTC + 2:00)
    System Uptime: 0 days 2:47:02.528
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    .............................
    Loading User Symbols
    Loading unloaded module list
    .....................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff81e7a91b9f0, 10, fffff81e7a91b9f0, 2}
    
    *** WARNING: Unable to verify timestamp for mbae64.sys
    *** ERROR: Module load completed but symbols could not be loaded for mbae64.sys
    
    Could not read faulting driver name
    Probably caused by : mbae64.sys ( mbae64+848e )
    
    Followup:     MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: fffff81e7a91b9f0, memory referenced.
    Arg2: 0000000000000010, value 0 = read operation, 1 = write operation.
    Arg3: fffff81e7a91b9f0, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000002, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    KEY_VALUES_STRING: 1
    
        Key  : Dump.Attributes.InsufficientDumpfileSize
        Value: 1
    
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  10.0.17763.379 (WinBuild.160101.0800)
    
    SYSTEM_MANUFACTURER:  HP
    
    SYSTEM_PRODUCT_NAME:  HP Pavilion x360 Convertible
    
    SYSTEM_SKU:  4AS57EA#ABU
    
    SYSTEM_VERSION:  Type1ProductConfigId
    
    BIOS_VENDOR:  Insyde
    
    BIOS_VERSION:  F.32
    
    BIOS_DATE:  11/08/2018
    
    BASEBOARD_MANUFACTURER:  HP
    
    BASEBOARD_PRODUCT:  8486
    
    BASEBOARD_VERSION:  72.23
    
    DUMP_FILE_ATTRIBUTES: 0xc
      Insufficient Dumpfile Size
      Kernel Generated Triage Dump
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: fffff81e7a91b9f0
    
    BUGCHECK_P2: 10
    
    BUGCHECK_P3: fffff81e7a91b9f0
    
    BUGCHECK_P4: 2
    
    READ_ADDRESS: fffff8047a7db390: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
     fffff81e7a91b9f0 
    
    FAULTING_IP: 
    +0
    fffff81e`7a91b9f0 ??              ???
    
    MM_INTERNAL_CODE:  2
    
    CPU_COUNT: 8
    
    CPU_MHZ: 708
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 8e
    
    CPU_STEPPING: a
    
    CPU_MICROCODE: 6,8e,a,0 (F,M,S,R)  SIG: 96'00000000 (cache) 96'00000000 (init)
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  AV
    
    PROCESS_NAME:  services.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_SESSION_HOST:  MICHAL
    
    ANALYSIS_SESSION_TIME:  04-11-2019 17:30:42.0616
    
    ANALYSIS_VERSION: 10.0.17763.132 amd64fre
    
    TRAP_FRAME:  ffffb0807823e910 -- (.trap 0xffffb0807823e910)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffb0807823eb08 rbx=0000000000000000 rcx=ffffc486fbb7c080
    rdx=0000000000000200 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff81e7a91b9f0 rsp=ffffb0807823eaa8 rbp=ffffb0807823ebc9
     r8=0000000000000000  r9=00000000001fffff r10=fffff804797a4914
    r11=ffffb0807823eaf8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    fffff81e`7a91b9f0 ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8047a47c00f to fffff8047a44c5e0
    
    FAILED_INSTRUCTION_ADDRESS: 
    +0
    fffff81e`7a91b9f0 ??              ???
    
    STACK_TEXT:  
    ffffb080`7823e628 fffff804`7a47c00f : 00000000`00000050 fffff81e`7a91b9f0 00000000`00000010 ffffb080`7823e910 : nt!KeBugCheckEx
    ffffb080`7823e630 fffff804`7a3a0ab7 : ffffc486`fd1a5480 00000000`00000010 00000000`00000000 fffff81e`7a91b9f0 : nt!MiSystemFault+0x1ac34f
    ffffb080`7823e770 fffff804`7a45a083 : ffffb080`7823e910 ffffb080`00000000 00000000`00000001 00000000`00000010 : nt!MmAccessFault+0x327
    ffffb080`7823e910 fffff81e`7a91b9f0 : fffff804`797a848e ffffffff`ffffffff 00000000`00000101 ffffc486`fbae64b0 : nt!KiPageFault+0x343
    ffffb080`7823eaa8 fffff804`797a848e : ffffffff`ffffffff 00000000`00000101 ffffc486`fbae64b0 fffff804`7a93d6b5 : 0xfffff81e`7a91b9f0
    ffffb080`7823eab0 ffffffff`ffffffff : 00000000`00000101 ffffc486`fbae64b0 fffff804`7a93d6b5 00000000`00000000 : mbae64+0x848e
    ffffb080`7823eab8 00000000`00000101 : ffffc486`fbae64b0 fffff804`7a93d6b5 00000000`00000000 ffffb080`7823eb00 : 0xffffffff`ffffffff
    ffffb080`7823eac0 ffffc486`fbae64b0 : fffff804`7a93d6b5 00000000`00000000 ffffb080`7823eb00 ffffb080`7823eb08 : 0x101
    ffffb080`7823eac8 fffff804`7a93d6b5 : 00000000`00000000 ffffb080`7823eb00 ffffb080`7823eb08 ffffc486`fbbb4040 : 0xffffc486`fbae64b0
    ffffb080`7823ead0 fffff804`797a84c1 : ffffb080`7823ebc9 00000000`00000000 00000000`00000000 00000000`000007b8 : nt!PsLookupProcessByProcessId+0x55
    ffffb080`7823eb00 ffffb080`7823ebc9 : 00000000`00000000 00000000`00000000 00000000`000007b8 ffffb080`7823eba0 : mbae64+0x84c1
    ffffb080`7823eb08 00000000`00000000 : 00000000`00000000 00000000`000007b8 ffffb080`7823eba0 fffff804`797a2b7d : 0xffffb080`7823ebc9
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  374e2765d2f0405ed508508cdc7f8bfe1ca922e7
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  74cb620ed3c6e81cdf8fd836cf2f1535e7b6a0e8
    
    THREAD_SHA1_HASH_MOD:  549b3b1153fe0b6f830ab4a20328a35e206916ed
    
    FOLLOWUP_IP: 
    mbae64+848e
    fffff804`797a848e ??              ???
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  mbae64+848e
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: mbae64
    
    IMAGE_NAME:  mbae64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5bf3fece
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  848e
    
    FAILURE_BUCKET_ID:  AV_INVALID_BAD_IP_mbae64!unknown_function
    
    BUCKET_ID:  AV_INVALID_BAD_IP_mbae64!unknown_function
    
    PRIMARY_PROBLEM_CLASS:  AV_INVALID_BAD_IP_mbae64!unknown_function
    
    TARGET_TIME:  2019-04-11T13:51:06.000Z
    
    OSBUILD:  17763
    
    OSSERVICEPACK:  379
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  784
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  unknown_date
    
    BUILDDATESTAMP_STR:  160101.0800
    
    BUILDLAB_STR:  WinBuild
    
    BUILDOSVER_STR:  10.0.17763.379
    
    ANALYSIS_SESSION_ELAPSED_TIME:  983
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:av_invalid_bad_ip_mbae64!unknown_function
    
    FAILURE_ID_HASH:  {19728808-2a26-2169-b474-80b7eb525481}
    
    Followup:     MachineOwner
    ---------
    
    3: kd> .load pde
    =========================================================================================
     PDE v11.3 - Copyright 2017 Andrew Richards
    =========================================================================================
    3: kd> !dpx
    Start memory scan  : 0xffffb0807823e628 ($csp)
    End memory scan    : 0xffffb08078240000 (Kernel Stack Base)
    
    0xffffb0807823e698 : 0xfffff8047a35c417 : nt!KiExitDispatcher+0x187
    0xffffb0807823e738 : 0xfffff8047a2da067 : nt!KiStackAttachProcess+0x247
    0xffffb0807823e768 : 0xfffff8047a3a0ab7 : nt!MmAccessFault+0x327
    0xffffb0807823e7a0 : 0xffffb0807823e8d0 : 0xfffff8047a773c58 : nt!PspCreateProcessNotifyRoutine+0x68
    0xffffb0807823e7b8 : 0xfffff8047a3ba288 : nt!KeQueryCurrentStackInformation+0x68
    0xffffb0807823e7d8 : 0xfffff8047a8fc5c1 : nt!FsRtlCancellableWaitForMultipleObjects+0x91
    0xffffb0807823e7e8 : 0xfffff8047a3ba204 : nt!RtlpGetStackLimits+0x14
    0xffffb0807823e818 : 0xfffff8047a2027a9 : hal!KeQueryPerformanceCounter+0x1d9
    0xffffb0807823e828 : 0xfffff809e3f19060 : FLTMGR!WPP_GLOBAL_Control
    0xffffb0807823e8d0 : 0xfffff8047a773c58 : nt!PspCreateProcessNotifyRoutine+0x68
    0xffffb0807823e908 : 0xfffff8047a45a083 : nt!KiPageFault+0x343
    0xffffb0807823e910 : 0xffffb0807823e910 :  Trap @ ffffb0807823e910
    *** WARNING: Unable to verify timestamp for mbae64.sys
    *** ERROR: Module load completed but symbols could not be loaded for mbae64.sys
    0xffffb0807823e9e8 : 0xffffb0807823ea00 : 0xfffff8047a773c50 : nt!PspCreateProcessNotifyRoutine+0x60
    0xffffb0807823ea00 : 0xfffff8047a773c50 : nt!PspCreateProcessNotifyRoutine+0x60
    Unable to load image farflt.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for farflt.sys
    *** ERROR: Module load completed but symbols could not be loaded for farflt.sys
    0xffffb0807823eac8 : 0xfffff8047a93d6b5 : nt!PsLookupProcessByProcessId+0x55
    0xffffb0807823eb58 : 0xfffff8047a91a72d : nt!PspCallProcessNotifyRoutines+0x249
    0xffffb0807823eb90 : 0xfffff80490075520 : bam!BampKernelCalloutTable
    0xffffb0807823ec28 : 0xfffff8047a851de7 : nt!PspInsertThread+0x5d7
    0xffffb0807823ece8 : 0xfffff8047a886cfe : nt!NtCreateUserProcess+0x88e
    0xffffb0807823eda8 : 0x0053002b002b0033 :  !du "3++S++"
    0xffffb0807823f980 : 0xffffb0807823fa80 :  !du "SERSPROF"
    0xffffb0807823f988 : 0xfffff8047a45d785 : nt!KiSystemServiceCopyEnd+0x25
    0xffffb0807823f9f8 : 0xfffff8047a45d785 : nt!KiSystemServiceCopyEnd+0x25
    0xffffb0807823fa00 : 0xffffc486fbbb4040 :  Trap @ ffffb0807823fa00
    0xffffb0807823fa10 : 0xffffb0807823fa80 :  !du "SERSPROF"
    0xffffb0807823fa80 : 0x0053005200450053 :  !du "SERSPROF"
    
    3: kd> !pte fffff81e7a91b9f0
                                               VA fffff81e7a91b9f0
    PXE at FFFFD8EC763B1F80    PPE at FFFFD8EC763F03C8    PDE at FFFFD8EC7E079EA0    PTE at FFFFD8FC0F3D48D8
    contains 0000000004A08063  contains 0000000000000000
    pfn 4a08      ---DA--KWEV  not valid
    
    3: kd> lmvm mbae64
    Browse full module list
    start             end                 module name
    fffff804`797a0000 fffff804`797c6000   mbae64   T (no symbols)           
        Loaded symbol image file: mbae64.sys
        Image path: mbae64.sys
        Image name: mbae64.sys
        Browse all global symbols  functions  data
        Timestamp:        Tue Nov 20 13:32:14 2018 (5BF3FECE)
        CheckSum:         000282F6
        ImageSize:        00026000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
        Information from resource tables:
    3: kd> lmvm farflt
    Browse full module list
    start             end                 module name
    fffff804`79770000 fffff804`79791000   farflt   T (no symbols)           
        Loaded symbol image file: farflt.sys
        Image path: farflt.sys
        Image name: farflt.sys
        Browse all global symbols  functions  data
        Timestamp:        Wed Jan  9 17:44:11 2019 (5C3624DB)
        CheckSum:         00022FDD
        ImageSize:        00021000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
        Information from resource tables:
    Uninstall Malwarebytes Anti-Exploit
    Code:
    Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\michal01\Downloads\041119-9234-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\SymCache*https://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\SymCache*https://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 10 Kernel Version 17763 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0xfffff801`1fea7000 PsLoadedModuleList = 0xfffff801`202c29f0
    Debug session time: Thu Apr 11 16:08:18.336 2019 (UTC + 2:00)
    System Uptime: 0 days 0:00:49.338
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ...........................
    Loading User Symbols
    Loading unloaded module list
    ...................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffff800202ac8a8, a, 0, fffff80b0eae40e7}
    
    Probably caused by : Wdf01000.sys ( Wdf01000!FxInterrupt::_InterruptThunk+47 )
    
    Followup:     MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: fffff800202ac8a8, memory referenced
    Arg2: 000000000000000a, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff80b0eae40e7, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
        Key  : Dump.Attributes.InsufficientDumpfileSize
        Value: 1
    
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  10.0.17763.379 (WinBuild.160101.0800)
    
    SYSTEM_MANUFACTURER:  HP
    
    SYSTEM_PRODUCT_NAME:  HP Pavilion x360 Convertible
    
    SYSTEM_SKU:  4AS57EA#ABU
    
    SYSTEM_VERSION:  Type1ProductConfigId
    
    BIOS_VENDOR:  Insyde
    
    BIOS_VERSION:  F.32
    
    BIOS_DATE:  11/08/2018
    
    BASEBOARD_MANUFACTURER:  HP
    
    BASEBOARD_PRODUCT:  8486
    
    BASEBOARD_VERSION:  72.23
    
    DUMP_FILE_ATTRIBUTES: 0xc
      Insufficient Dumpfile Size
      Kernel Generated Triage Dump
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: fffff800202ac8a8
    
    BUGCHECK_P2: a
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: fffff80b0eae40e7
    
    READ_ADDRESS: fffff801203e9390: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
     fffff800202ac8a8 
    
    CURRENT_IRQL:  a
    
    FAULTING_IP: 
    Wdf01000!FxInterrupt::_InterruptThunk+47 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 367]
    fffff80b`0eae40e7 488b4010        mov     rax,qword ptr [rax+10h]
    
    CPU_COUNT: 8
    
    CPU_MHZ: 708
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 8e
    
    CPU_STEPPING: a
    
    CPU_MICROCODE: 6,8e,a,0 (F,M,S,R)  SIG: 96'00000000 (cache) 96'00000000 (init)
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  AV
    
    PROCESS_NAME:  System
    
    ANALYSIS_SESSION_HOST:  MICHAL
    
    ANALYSIS_SESSION_TIME:  04-11-2019 17:33:06.0992
    
    ANALYSIS_VERSION: 10.0.17763.132 amd64fre
    
    TRAP_FRAME:  fffff80122df5d70 -- (.trap 0xfffff80122df5d70)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff800202ac898 rbx=0000000000000000 rcx=ffffb080bdb71280
    rdx=ffffda09a2c02cc0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80b0eae40e7 rsp=fffff80122df5f00 rbp=ffffda09a2c02d60
     r8=0000000000000000  r9=ffffda09a2ff7f60 r10=fffff80b0eae40a0
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    Wdf01000!FxPerfTraceInterrupt+0x7 [inlined in Wdf01000!FxInterrupt::_InterruptThunk+0x47]:
    fffff80b`0eae40e7 488b4010        mov     rax,qword ptr [rax+10h] ds:fffff800`202ac8a8=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8012006bd69 to fffff8012005a5e0
    
    STACK_TEXT:  
    fffff801`22df5c28 fffff801`2006bd69 : 00000000`0000000a fffff800`202ac8a8 00000000`0000000a 00000000`00000000 : nt!KeBugCheckEx
    fffff801`22df5c30 fffff801`2006818e : ffffda09`ad571000 00000000`00000000 ffffda09`a2bb7000 00000000`c0000001 : nt!KiBugCheckDispatch+0x69
    fffff801`22df5d70 fffff80b`0eae40e7 : fffff801`1db4a180 fffff801`1ff18b41 ffffb080`be38d500 ffffda09`a23c0f10 : nt!KiPageFault+0x44e
    fffff801`22df5f00 fffff801`1fee98b5 : fffff801`1db4a180 fffff801`1fe77790 fffff801`1db4a180 fffff801`1fee98b5 : Wdf01000!FxInterrupt::_InterruptThunk+0x47 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 367] 
    fffff801`22df5f40 fffff801`2005bd5f : fffff801`22de6a50 ffffb080`bdb71280 00000000`000005d4 ffffb080`bdb71280 : nt!KiCallInterruptServiceRoutine+0xa5
    fffff801`22df5f90 fffff801`2005c027 : 00000000`00000002 00000000`00000000 fffff801`22de6b00 00000000`00000000 : nt!KiInterruptSubDispatch+0x11f
    fffff801`22de69d0 fffff801`2005dfd2 : 00000000`00000000 fffff801`1db4a180 fffff801`20406400 ffffda09`af11d080 : nt!KiInterruptDispatch+0x37
    fffff801`22de6b60 00000000`00000000 : fffff801`22de7000 fffff801`22de0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x32
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  445e18ec6bb6bd020c537501f5a114eff9ac32eb
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  fcf6959fd233fb21b6bf65d12f36bc05ac03618b
    
    THREAD_SHA1_HASH_MOD:  34bc9a96e19b7c332383ecb54a5e9fca5b03dd73
    
    FOLLOWUP_IP: 
    Wdf01000!FxInterrupt::_InterruptThunk+47 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 367]
    fffff80b`0eae40e7 488b4010        mov     rax,qword ptr [rax+10h]
    
    FAULT_INSTR_CODE:  10408b48
    
    FAULTING_SOURCE_LINE:  minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp
    
    FAULTING_SOURCE_FILE:  minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp
    
    FAULTING_SOURCE_LINE_NUMBER:  367
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  Wdf01000!FxInterrupt::_InterruptThunk+47
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Wdf01000
    
    IMAGE_NAME:  Wdf01000.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  1.27.17763.132
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  47
    
    FAILURE_BUCKET_ID:  AV_Wdf01000!FxInterrupt::_InterruptThunk
    
    BUCKET_ID:  AV_Wdf01000!FxInterrupt::_InterruptThunk
    
    PRIMARY_PROBLEM_CLASS:  AV_Wdf01000!FxInterrupt::_InterruptThunk
    
    TARGET_TIME:  2019-04-11T14:08:18.000Z
    
    OSBUILD:  17763
    
    OSSERVICEPACK:  379
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  784
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  unknown_date
    
    BUILDDATESTAMP_STR:  160101.0800
    
    BUILDLAB_STR:  WinBuild
    
    BUILDOSVER_STR:  10.0.17763.379
    
    ANALYSIS_SESSION_ELAPSED_TIME:  931
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:av_wdf01000!fxinterrupt::_interruptthunk
    
    FAILURE_ID_HASH:  {25e6ef61-b8e1-b60c-e8b6-e4f1fe0c8a1f}
    
    Followup:     MachineOwner
    ---------
    
    0: kd> .load pde
    =========================================================================================
     PDE v11.3 - Copyright 2017 Andrew Richards
    =========================================================================================
    0: kd> !dpx
    Start memory scan  : 0xfffff80122df5c28 ($csp)
    End memory scan    : 0xfffff80122df6000 (ISR Stack Base)
    
                   rax : 0xfffff80122df5d30 : 0xffffda09a2c02cc0 :  dt Wdf01000!FxInterrupt
                   rbx : 0xffffda09a2c02cc0 :  dt Wdf01000!FxInterrupt
                   rsp : 0xfffff80122df5c28 : 0xfffff8012006bd69 : nt!KiBugCheckDispatch+0x69
    0xfffff80122df5c28 : 0xfffff8012006bd69 : nt!KiBugCheckDispatch+0x69
    0xfffff80122df5c50 : 0xfffff80b0eae40e7 : Wdf01000!FxInterrupt::_InterruptThunk+0x47
    Unable to load image igdkmd64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for igdkmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
    0xfffff80122df5d30 : 0xffffda09a2c02cc0 :  dt Wdf01000!FxInterrupt
    0xfffff80122df5d68 : 0xfffff8012006818e : nt!KiPageFault+0x44e
    0xfffff80122df5d70 : 0xffffda09ad571000 :  Trap @ fffff80122df5d70
    0xfffff80122df5db0 : 0xffffda09a2c02cc0 :  dt Wdf01000!FxInterrupt
    0xfffff80122df5dc8 : 0xfffff80b0eae40a0 : Wdf01000!FxInterrupt::_InterruptThunk
    0xfffff80122df5ed8 : 0xfffff80b0eae40e7 : Wdf01000!FxInterrupt::_InterruptThunk+0x47
    0xfffff80122df5f08 : 0xfffff8011ff18b41 : nt!KiInterruptMessageDispatch+0x11
    0xfffff80122df5f38 : 0xfffff8011fee98b5 : nt!KiCallInterruptServiceRoutine+0xa5
    0xfffff80122df5f48 : 0xfffff8011fe77790 : hal!HalpKInterruptHeap+0x7b0
    0xfffff80122df5f58 : 0xfffff8011fee98b5 : nt!KiCallInterruptServiceRoutine+0xa5
    0xfffff80122df5f88 : 0xfffff8012005bd5f : nt!KiInterruptSubDispatch+0x11f
    0xfffff80122df5fd8 : 0xfffff8012005c027 : nt!KiInterruptDispatch+0x37
    
    0: kd> lmvm igdkmd64
    Browse full module list
    start             end                 module name
    fffff801`38df0000 fffff801`39bc2000   igdkmd64 T (no symbols)           
        Loaded symbol image file: igdkmd64.sys
        Image path: igdkmd64.sys
        Image name: igdkmd64.sys
        Browse all global symbols  functions  data
        Timestamp:        Fri Sep 14 10:03:00 2018 (5B9B6B34)
        CheckSum:         00DC5474
        ImageSize:        00DD2000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
        Information from resource tables:
    Update Intel graphics card driver
    Code:
    Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\michal01\Downloads\041119-9437-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\SymCache*https://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\SymCache*https://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 10 Kernel Version 17763 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0xfffff803`12c10000 PsLoadedModuleList = 0xfffff803`1302b9f0
    Debug session time: Thu Apr 11 16:11:07.852 2019 (UTC + 2:00)
    System Uptime: 0 days 0:00:22.854
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ..........................
    Loading User Symbols
    Loading unloaded module list
    ..................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {ffffc5cfed8f4d40, 2, 1, fffff8000e3537d2}
    
    Probably caused by : Wdf01000.sys ( Wdf01000!FxInterrupt::_InterruptDpcThunk+52 )
    
    Followup:     MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: ffffc5cfed8f4d40, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff8000e3537d2, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
        Key  : Dump.Attributes.InsufficientDumpfileSize
        Value: 1
    
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  10.0.17763.379 (WinBuild.160101.0800)
    
    SYSTEM_MANUFACTURER:  HP
    
    SYSTEM_PRODUCT_NAME:  HP Pavilion x360 Convertible
    
    SYSTEM_SKU:  4AS57EA#ABU
    
    SYSTEM_VERSION:  Type1ProductConfigId
    
    BIOS_VENDOR:  Insyde
    
    BIOS_VERSION:  F.32
    
    BIOS_DATE:  11/08/2018
    
    BASEBOARD_MANUFACTURER:  HP
    
    BASEBOARD_PRODUCT:  8486
    
    BASEBOARD_VERSION:  72.23
    
    DUMP_FILE_ATTRIBUTES: 0xc
      Insufficient Dumpfile Size
      Kernel Generated Triage Dump
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: ffffc5cfed8f4d40
    
    BUGCHECK_P2: 2
    
    BUGCHECK_P3: 1
    
    BUGCHECK_P4: fffff8000e3537d2
    
    WRITE_ADDRESS: fffff80313152390: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
     ffffc5cfed8f4d40 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    Wdf01000!FxInterrupt::_InterruptDpcThunk+52 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 404]
    fffff800`0e3537d2 48891401        mov     qword ptr [rcx+rax],rdx
    
    CPU_COUNT: 8
    
    CPU_MHZ: 708
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 8e
    
    CPU_STEPPING: a
    
    CPU_MICROCODE: 6,8e,a,0 (F,M,S,R)  SIG: 96'00000000 (cache) 96'00000000 (init)
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  AV
    
    PROCESS_NAME:  System
    
    ANALYSIS_SESSION_HOST:  MICHAL
    
    ANALYSIS_SESSION_TIME:  04-11-2019 17:34:39.0733
    
    ANALYSIS_VERSION: 10.0.17763.132 amd64fre
    
    TRAP_FRAME:  fffff80315be6640 -- (.trap 0xfffff80315be6640)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffc5cfed8f4d40 rbx=0000000000000000 rcx=0000000000000000
    rdx=ffffc50bf0e192f0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000e3537d2 rsp=fffff80315be67d0 rbp=fffff80315be6910
     r8=ffffc50bf0920cf0  r9=0000000000000000 r10=fffff8000e353780
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    Wdf01000!_FX_DRIVER_TRACKER_CACHE_AWARE::TrackDriver+0x18 [inlined in Wdf01000!FxInterrupt::_InterruptDpcThunk+0x52]:
    fffff800`0e3537d2 48891401        mov     qword ptr [rcx+rax],rdx ds:ffffc5cf`ed8f4d40=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80312dd4d69 to fffff80312dc35e0
    
    STACK_TEXT:  
    fffff803`15be64f8 fffff803`12dd4d69 : 00000000`0000000a ffffc5cf`ed8f4d40 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff803`15be6500 fffff803`12dd118e : 00000006`d31fef1a fffff800`103444be ffff4117`b63b8743 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff803`15be6640 fffff800`0e3537d2 : fffff803`10ad9180 fffff803`136817a9 00000000`00000000 00000000`00000004 : nt!KiPageFault+0x44e
    fffff803`15be67d0 fffff803`12cc8c67 : fffff803`15be6900 00000000`00000000 00000000`00020001 00000000`00000000 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x52 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 404] 
    fffff803`15be6810 fffff803`12cc82ae : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x2e7
    fffff803`15be6950 fffff803`12dc6ffa : 00000000`00000000 fffff803`10ad9180 00000000`001a6550 fffff803`1316f400 : nt!KiRetireDpcList+0x1ae
    fffff803`15be6b60 00000000`00000000 : fffff803`15be7000 fffff803`15be0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  974a67edff106974ffa233cb8b73f76811f2ae15
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  0847a0c8b3cedfef0b0dbf6a82888066f52916a8
    
    THREAD_SHA1_HASH_MOD:  2d66b1b229917fd259a42a29d505f7192c3ba378
    
    FOLLOWUP_IP: 
    Wdf01000!FxInterrupt::_InterruptDpcThunk+52 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 404]
    fffff800`0e3537d2 48891401        mov     qword ptr [rcx+rax],rdx
    
    FAULT_INSTR_CODE:  1148948
    
    FAULTING_SOURCE_LINE:  minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp
    
    FAULTING_SOURCE_FILE:  minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp
    
    FAULTING_SOURCE_LINE_NUMBER:  404
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  Wdf01000!FxInterrupt::_InterruptDpcThunk+52
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Wdf01000
    
    IMAGE_NAME:  Wdf01000.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  1.27.17763.132
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  52
    
    FAILURE_BUCKET_ID:  AV_Wdf01000!FxInterrupt::_InterruptDpcThunk
    
    BUCKET_ID:  AV_Wdf01000!FxInterrupt::_InterruptDpcThunk
    
    PRIMARY_PROBLEM_CLASS:  AV_Wdf01000!FxInterrupt::_InterruptDpcThunk
    
    TARGET_TIME:  2019-04-11T14:11:07.000Z
    
    OSBUILD:  17763
    
    OSSERVICEPACK:  379
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  784
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  unknown_date
    
    BUILDDATESTAMP_STR:  160101.0800
    
    BUILDLAB_STR:  WinBuild
    
    BUILDOSVER_STR:  10.0.17763.379
    
    ANALYSIS_SESSION_ELAPSED_TIME:  8ba
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:av_wdf01000!fxinterrupt::_interruptdpcthunk
    
    FAILURE_ID_HASH:  {777a6888-f8ab-7103-ee5a-3801317a01ff}
    
    Followup:     MachineOwner
    ---------
    
    0: kd> .load pde
    =========================================================================================
     PDE v11.3 - Copyright 2017 Andrew Richards
    =========================================================================================
    0: kd> !dpx
    Start memory scan  : 0xfffff80315be64f8 ($csp)
    End memory scan    : 0xfffff80315be7000 (Kernel Stack Base)
    
                   rax : 0xfffff80315be6600 : 0xffffc50bf0920cf0 :  dt Wdf01000!FxInterrupt
                   rbx : 0xffffc50bf0920cf0 :  dt Wdf01000!FxInterrupt
                   rsp : 0xfffff80315be64f8 : 0xfffff80312dd4d69 : nt!KiBugCheckDispatch+0x69
                   r14 : 0xfffff80315be6a20 : 0xfffff8000e353780 : Wdf01000!FxInterrupt::_InterruptDpcThunk
    0xfffff80315be64f8 : 0xfffff80312dd4d69 : nt!KiBugCheckDispatch+0x69
    0xfffff80315be6520 : 0xfffff8000e3537d2 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x52
    0xfffff80315be65f8 : 0xfffff80312d37acf : nt!KiCheckForTimerExpiration+0x10f
    0xfffff80315be6600 : 0xffffc50bf0920cf0 :  dt Wdf01000!FxInterrupt
    0xfffff80315be6628 : 0xfffff80315be6a20 : 0xfffff8000e353780 : Wdf01000!FxInterrupt::_InterruptDpcThunk
    0xfffff80315be6638 : 0xfffff80312dd118e : nt!KiPageFault+0x44e
    0xfffff80315be6640 : 0x00000006d31fef1a :  Trap @ fffff80315be6640
    0xfffff80315be6648 : 0xfffff800103444be : dxgkrnl!DxgNotifyDpcCB+0xfe
    0xfffff80315be6688 : 0xffffc50bf0920cf0 :  dt Wdf01000!FxInterrupt
    0xfffff80315be6698 : 0xfffff8000e353780 : Wdf01000!FxInterrupt::_InterruptDpcThunk
    0xfffff80315be66a8 : 0xfffff803136817a9 : hal!KeQueryPerformanceCounter+0x1d9
    0xfffff80315be6718 : 0xfffff803136819f5 : hal!HalpApicRequestInterrupt+0x95
    0xfffff80315be67a8 : 0xfffff8000e3537d2 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x52
    0xfffff80315be67d8 : 0xfffff803136817a9 : hal!KeQueryPerformanceCounter+0x1d9
    0xfffff80315be6808 : 0xfffff80312cc8c67 : nt!KiExecuteAllDpcs+0x2e7
    0xfffff80315be6848 : 0xffffc50bf0920cf0 :  dt Wdf01000!FxInterrupt
    0xfffff80315be6858 : 0xffffc50bf0920cf0 :  dt Wdf01000!FxInterrupt
    0xfffff80315be6860 : 0xfffff8000e353780 : Wdf01000!FxInterrupt::_InterruptDpcThunk
    0xfffff80315be6880 : 0xfffff8031316f400 : nt!KiInitialThread
    0xfffff80315be6920 : 0xfffff8031316f400 : nt!KiInitialThread
    0xfffff80315be6940 : 0xfffff8031316f400 : nt!KiInitialThread
    0xfffff80315be6948 : 0xfffff80312cc82ae : nt!KiRetireDpcList+0x1ae
    0xfffff80315be6998 : 0xfffff80313682ae6 : hal!HalPerformEndOfInterrupt+0x16
    0xfffff80315be69c0 : 0xfffff8031316f400 : nt!KiInitialThread
    0xfffff80315be69c8 : 0xfffff80312dc5075 : nt!KiInterruptDispatch+0x85
    0xfffff80315be6a20 : 0xfffff8000e353780 : Wdf01000!FxInterrupt::_InterruptDpcThunk
    0xfffff80315be6b18 : 0xfffff80312dca930 : nt!SwapContext+0x4d0
    0xfffff80315be6b58 : 0xfffff80312dc6ffa : nt!KiIdleLoop+0x5a
    0xfffff80315be6b78 : 0xfffff8031316f400 : nt!KiInitialThread
    
    0: kd> !verifier
    fffff8031302ba00: Unable to get verifier list.
      My ComputerSystem Spec

  2. Ztruker's Avatar
    Posts : 7,701
    Windows 10 Pro X64 1809 17763.437
       #12

    Please don't use Dropbox or another file sharing site.

    Read the instructions here: Blue Screen of Death (BSOD) Posting Instructions . Use the Beta log collector.

    Upload the zip file created by the beta log collector here to this site. Makes it a lot easier for us to get them. There are additional files we need to see.
      My ComputersSystem Spec


  3. Posts : 8
    Windows 10 home 64 bit
    Thread Starter
       #13

    Hi Ztruker and MrPepka
    It happened again, nothing much left to uninstall now.

    I also did what you said Ztruker, i downloaded the tool and the file is attached to this message.
    could you please take a look again, see if its possible to get to the bottom of this

    Thanks
    Robert
    BSOD's on start up and reliability history showing hardware failure Attached Files
      My ComputerSystem Spec

  4. philc43's Avatar
    Posts : 4,033
    64bit Win 10 Pro ver 1809 Build 17763.437 and W10 Insider Build 18362 and 18865
       #14

    Looking at your event logs shows a number of issues:

    Corrected hardware events:

    Click image for larger version. 

Name:	2019-04-12.png 
Views:	11 
Size:	15.6 KB 
ID:	230441

    Controller errors on Harddisk 3 ( I think this is one of your external drives?)
    Click image for larger version. 

Name:	2019-04-12 (1).png 
Views:	11 
Size:	9.4 KB 
ID:	230442

    On the 9th April you were repeatedly getting these errors:
    Code:
    2019-04-09T20:12:25.376  An error was detected on device \Device\Harddisk2\DR3 during a paging operation.
    2019-04-09T20:12:25.381  The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume8.
    (A device which does not exist was specified.)

    I would focus on your hard drives and remove external storage drives while troubleshooting. Do you have a backup system running all the time? The recent crash seems to be associated with storage processes and page faults.






      My ComputersSystem Spec


  5. Posts : 8
    Windows 10 home 64 bit
    Thread Starter
       #15

    philc43 said: View Post
    Looking at your event logs shows a number of issues:

    Corrected hardware events:

    Click image for larger version. 

Name:	2019-04-12.png 
Views:	11 
Size:	15.6 KB 
ID:	230441

    Controller errors on Harddisk 3 ( I think this is one of your external drives?)
    Click image for larger version. 

Name:	2019-04-12 (1).png 
Views:	11 
Size:	9.4 KB 
ID:	230442

    On the 9th April you were repeatedly getting these errors:
    Code:
    2019-04-09T20:12:25.376  An error was detected on device \Device\Harddisk2\DR3 during a paging operation.
    2019-04-09T20:12:25.381  The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume8.
    (A device which does not exist was specified.)

    I would focus on your hard drives and remove external storage drives while troubleshooting. Do you have a backup system running all the time? The recent crash seems to be associated with storage processes and page faults.






    I have an external hard drive connected yes and a memory stick, i will remove them and see if that is the problem. what is that mention of a PCI express port, is that just something plugged in by USB?

    - - - Updated - - -

    philc43 said: View Post
    Looking at your event logs shows a number of issues:

    Corrected hardware events:

    Click image for larger version. 

Name:	2019-04-12.png 
Views:	11 
Size:	15.6 KB 
ID:	230441

    Controller errors on Harddisk 3 ( I think this is one of your external drives?)
    Click image for larger version. 

Name:	2019-04-12 (1).png 
Views:	11 
Size:	9.4 KB 
ID:	230442

    On the 9th April you were repeatedly getting these errors:
    Code:
    2019-04-09T20:12:25.376  An error was detected on device \Device\Harddisk2\DR3 during a paging operation.
    2019-04-09T20:12:25.381  The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume8.
    (A device which does not exist was specified.)

    I would focus on your hard drives and remove external storage drives while troubleshooting. Do you have a backup system running all the time? The recent crash seems to be associated with storage processes and page faults.






    I have an external hard drive connected yes and a memory stick, i will remove them and see if that is the problem. what is that mention of a PCI express port, is that just something plugged in by USB?

    Looking at the partition list the hard disk 3 i think is the C: drive, maybe im looking at the wrong thing though which is fairly possible. :) see below excerpt from the partitions.txt file.
    C: 221.34 156.9 \Device\HarddiskVolume3
    D: 15.9 2.27 \Device\HarddiskVolume5
    E: 0.01 0 \Device\CdRom0
    F: 465.73 190.2 \Device\HarddiskVolume10
    G: 57.28 15.74 \Device\HarddiskVolume9
    I: 58.22 51.5 \Device\HarddiskVolume11
      My ComputerSystem Spec

  6. philc43's Avatar
    Posts : 4,033
    64bit Win 10 Pro ver 1809 Build 17763.437 and W10 Insider Build 18362 and 18865
       #16

    The partitions.txt file can change with each reboot depending on how the external drives are detected so it can be quite difficult to relate eventlog entries in the past with the latest state. You can also look up in the MSInfo file under storage. I think disk 3 was external.

    The PCI express port can be found in device manager. You can also check which devices are using it by looking through the devices and in the details tab of Properties you can check the parent. They could be network devices and/or USB devices. Look for a matching vendor and device ID. See below for an example (not same IDs as yours):

    Click image for larger version. 

Name:	2019-04-11.png 
Views:	9 
Size:	11.6 KB 
ID:	230448
      My ComputersSystem Spec


  7. Posts : 8
    Windows 10 home 64 bit
    Thread Starter
       #17

    OK, will check all of that, what about the crashes which happened today. are they related to the same thing? the ones you have referenced seem to be yesterday and before going by the dates.
      My ComputerSystem Spec

  8. philc43's Avatar
    Posts : 4,033
    64bit Win 10 Pro ver 1809 Build 17763.437 and W10 Insider Build 18362 and 18865
       #18

    These were all the system errors and driver related logs I extracted from the 12th April:

    Code:
    2019-04-12T05:19:58.982  Volume C: (\Device\HarddiskVolume3) is healthy.  No action is needed.
    2019-04-12T05:19:59.201  Volume D: (\Device\HarddiskVolume5) is healthy.  No action is needed.
    2019-04-12T05:19:59.698  Volume \\?\Volume{04ab85b1-8518-4547-8f66-78a7afac3c5c} (\Device\HarddiskVolume4) is healthy.  No action is needed.
    2019-04-12T05:19:59.706  The driver \Driver\WUDFRd failed to load for the device PCI\VEN_8086&DEV_1903&SUBSYS_8486103C&REV_08\3&11583659&2&20.
    2019-04-12T05:20:01.295  The driver \Driver\WUDFRd failed to load for the device SWD\DRIVERENUM\WirelessButtonDriver_usersvc&3&9489f59&0.
    2019-04-12T05:20:02.996  The driver \Driver\WudfRd failed to load for the device HID\Vid_8087&Pid_0AC2\6&141b2170&0&0000.
    2019-04-12T05:20:02.999  The driver \Driver\WudfRd failed to load for the device HID\Vid_8087&Pid_0AC2\6&26d4d215&0&0000.
    2019-04-12T05:20:03.027  Intel(R) Trusted Execution Engine Interface driver has started successfully.
    2019-04-12T05:20:03.039  The driver \Driver\WUDFRd failed to load for the device ACPI\SYNA8007\1.
    2019-04-12T05:20:04.890  Volume F: (\Device\HarddiskVolume7) is healthy.  No action is needed.
    2019-04-12T05:20:06.145  The igfxCUIService2.0.0.0 service failed to start due to the following error: 
    The system cannot find the file specified.
    2019-04-12T05:20:07.321  The following boot-start or system-start driver(s) did not load: 
    dam
    hpdskflt
    2019-04-12T11:58:09.653  The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xfffff86f057545d0, 0x0000000000000010, 0xfffff86f057545d0, 0x0000000000000002). A dump was saved in: C:\WINDOWS\Minidump\041219-9078-01.dmp. Report Id: afe841f7-f6ae-4d5c-a71b-f6f687b1e069.
    2019-04-12T11:58:02.042  Volume C: (\Device\HarddiskVolume3) is healthy.  No action is needed.
    2019-04-12T11:58:02.278  Volume D: (\Device\HarddiskVolume5) is healthy.  No action is needed.
    2019-04-12T11:58:02.483  The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    2019-04-12T11:58:02.777  The driver \Driver\WUDFRd failed to load for the device PCI\VEN_8086&DEV_1903&SUBSYS_8486103C&REV_08\3&11583659&2&20.
    2019-04-12T11:58:02.779  Volume \\?\Volume{04ab85b1-8518-4547-8f66-78a7afac3c5c} (\Device\HarddiskVolume4) is healthy.  No action is needed.
    2019-04-12T11:58:04.483  The driver \Driver\WUDFRd failed to load for the device SWD\DRIVERENUM\WirelessButtonDriver_usersvc&3&9489f59&0.
    2019-04-12T11:58:06.207  The driver \Driver\WudfRd failed to load for the device HID\Vid_8087&Pid_0AC2\6&141b2170&0&0000.
    2019-04-12T11:58:06.209  The driver \Driver\WudfRd failed to load for the device HID\Vid_8087&Pid_0AC2\6&26d4d215&0&0000.
    2019-04-12T11:58:06.243  Intel(R) Trusted Execution Engine Interface driver has started successfully.
    2019-04-12T11:58:06.248  The driver \Driver\WUDFRd failed to load for the device ACPI\SYNA8007\1.
    2019-04-12T11:58:07.965  Volume F: (\Device\HarddiskVolume6) is healthy.  No action is needed.
    2019-04-12T11:58:09.589  The igfxCUIService2.0.0.0 service failed to start due to the following error: 
    The system cannot find the file specified.
    2019-04-12T11:58:11.051  The following boot-start or system-start driver(s) did not load: 
    dam
    hpdskflt
    2019-04-12T12:00:03.703  Volume F: (\Device\HarddiskVolume10) is healthy.  No action is needed.
    The actual BSOD was storage related as I said in my earlier post:

    Here is the call stack at the time of the crash - note the calls are nearly all drive related.

    Code:
    7: kd> knL
     # Child-SP          RetAddr           Call Site
    00 ffffad0f`b7f46fd8 fffff805`5a87d00f nt!KeBugCheckEx
    01 ffffad0f`b7f46fe0 fffff805`5a7a1ab7 nt!MiSystemFault+0x1ac34f
    02 ffffad0f`b7f47120 fffff805`5a85b083 nt!MmAccessFault+0x327
    03 ffffad0f`b7f472c0 fffff86f`057545d0 nt!KiPageFault+0x343
    04 ffffad0f`b7f47458 fffff809`066059a4 0xfffff86f`057545d0
    05 ffffad0f`b7f47460 fffff809`05751c4e EhStorClass!FilterDeviceEvtWdmIoctlIrpPreprocess+0x214
    06 (Inline Function) --------`-------- Wdf01000!PreprocessIrp+0x2e
    07 (Inline Function) --------`-------- Wdf01000!DispatchWorker+0x179
    08 (Inline Function) --------`-------- Wdf01000!FxDevice::Dispatch+0x197
    09 ffffad0f`b7f47490 fffff805`5a7520d9 Wdf01000!FxDevice::DispatchWithLock+0x1ee
    0a ffffad0f`b7f474f0 fffff805`70637623 nt!IofCallDriver+0x59
    0b ffffad0f`b7f47530 fffff805`706369b9 CLASSPNP!SubmitTransferPacket+0x2c3
    0c ffffad0f`b7f47570 fffff805`706379ef CLASSPNP!ServiceTransferRequest+0x209
    0d ffffad0f`b7f47600 fffff805`706367a0 CLASSPNP!ClasspEnqueueIdleRequest+0x30f
    0e ffffad0f`b7f476c0 fffff805`70631404 CLASSPNP!ClassReadWrite+0x1a0
    0f ffffad0f`b7f47710 fffff805`5a7520d9 CLASSPNP!ClassGlobalDispatch+0x24
    10 ffffad0f`b7f47740 fffff809`05ba1c8f nt!IofCallDriver+0x59
    11 ffffad0f`b7f47780 fffff809`05ba1f21 partmgr!PmWrite+0x16f
    12 ffffad0f`b7f47800 fffff805`5a7520d9 partmgr!PmGlobalDispatch+0x21
    13 ffffad0f`b7f47830 fffff809`05ba1a88 nt!IofCallDriver+0x59
    14 ffffad0f`b7f47870 fffff809`05ba189e partmgr!PartitionIo+0x1d8
    15 ffffad0f`b7f47920 fffff809`05ba1f21 partmgr!PartitionWrite+0x1e
    16 ffffad0f`b7f47950 fffff805`5a7520d9 partmgr!PmGlobalDispatch+0x21
    17 ffffad0f`b7f47980 fffff809`05c81af4 nt!IofCallDriver+0x59
    18 ffffad0f`b7f479c0 fffff805`5a7520d9 volmgr!VmReadWrite+0xf4
    19 ffffad0f`b7f47a00 fffff805`704143a3 nt!IofCallDriver+0x59
    1a ffffad0f`b7f47a40 fffff805`7041403c fvevol!FveFilterRundownReadWrite+0x2f3
    1b ffffad0f`b7f47b40 fffff805`5a7520d9 fvevol!FveFilterRundownWrite+0x4c
    1c ffffad0f`b7f47be0 fffff805`705e3c3e nt!IofCallDriver+0x59
    1d ffffad0f`b7f47c20 fffff805`705e4de8 iorate!IoRateIssueAndRecordIo+0x7a
    1e ffffad0f`b7f47c60 fffff805`705e4fc0 iorate!IoRateProcessIrpWrapper+0x180
    1f ffffad0f`b7f47d70 fffff805`5a7520d9 iorate!IoRateDispatchReadWrite+0x80
    20 ffffad0f`b7f47db0 fffff805`704e102e nt!IofCallDriver+0x59
    21 ffffad0f`b7f47df0 fffff805`5a7520d9 volume!VolumePassThrough+0x1e
    22 ffffad0f`b7f47e20 fffff805`704f14e4 nt!IofCallDriver+0x59
    23 ffffad0f`b7f47e60 fffff805`704f13b3 volsnap!VolsnapWriteFilter+0x114
    24 ffffad0f`b7f47ee0 fffff805`5a7520d9 volsnap!VolSnapWrite+0x13
    25 ffffad0f`b7f47f10 fffff809`05ec0ec7 nt!IofCallDriver+0x59
    26 ffffad0f`b7f47f50 fffff805`5a850dae Ntfs!NtfsStorageDriverCallout+0x17
    27 ffffad0f`b7f47f80 fffff805`5a850d6c nt!KxSwitchKernelStackCallout+0x2e
    28 ffffad0f`b97b6af0 00000000`00000000 nt!KiSwitchKernelStackContinue
    7: kd> .time
    Debug session time: Fri Apr 12 11:57:32.736 2019 (UTC + 1:00)
    System Uptime: 0 days 6:37:36.738

    It looks like the system was running for 6h 37min before it crashed and in that time there were no errors logged after the initial boot up.
      My ComputersSystem Spec


 
Page 2 of 2 FirstFirst 12

Related Threads
BSOD NMI hardware failure in BSOD Crashes and Debugging
Hello all, I am a newbie and have been struggling with this BSOD NMI Hardware Failure problem for a few months. I run a HP Workstation on Windows 10 Pro for a couple of years with no problems. Have not added new software or hardware (that I can...
Hi Keep getting BSOD with same cause intermittently. Bluescreenview says its caused by hal.dll+3957e. Attached are minidump and diag files. Thx Tom
Hi. Just wondering if anyone can let me know what this error message indicates on Reliability History. It occurred as soon as I started my PC (didn't get any error message or BSOD on start up). I only noticed it in Reliability History. The error is:...
I've used gpedit to allow manual control of updates and manually download and install updates when available, and I set "Notifiy to download" option. That gave me control similar to what I had with Win7. Or so I thought. But the Reliability...
Hey there, Ive been having blue screens for quite a while now and been trying to fix them myself but Ive decided it might be easier with some assistance. Ive ran memtest86+ for a whole day and found no errors. I ran prime95 and furmark for a...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:21.
Find Us