Windows 10: Machine Constantly Failing

Discus and support Machine Constantly Failing in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello, I have been getting constant BSOD over the last 4 weeks since the update. So much so that I can no longer use my desktop. I've tried a variety... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by SL101000999, Aug 23, 2019.

  1. SL101000999
    SL101000999 Win User

    Machine Constantly Failing


    Hello,


    I have been getting constant BSOD over the last 4 weeks since the update. So much so that I can no longer use my desktop. I've tried a variety of the troubleshooting. Here are 4 different dump files


    Number 1






    Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\Minidump\082219-10437-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 17134 MP (8 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Machine Name:

    Kernel base = 0xfffff803`18019000 PsLoadedModuleList = 0xfffff803`183c60f0

    Debug session time: Thu Aug 22 21:54:53.616 2019 (UTC - 5:00)

    System Uptime: 0 days 0:21:19.299

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ..............................

    Loading User Symbols

    Loading unloaded module list

    ..........

    For analysis of this file, run !analyze -v

    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: fffff8031710bec8, memory referenced

    Arg2: 00000000000000ff, IRQL

    Arg3: 0000000000000096, value 0 = read operation, 1 = write operation

    Arg4: fffff8031710bec8, address which referenced memory



    Debugging Details:

    ------------------





    KEY_VALUES_STRING: 1





    PROCESSES_ANALYSIS: 1



    SERVICE_ANALYSIS: 1



    STACKHASH_ANALYSIS: 1



    TIMELINE_ANALYSIS: 1





    DUMP_CLASS: 1



    DUMP_QUALIFIER: 400



    BUILD_VERSION_STRING: 10.0.17134.950 (WinBuild.160101.0800)



    DUMP_FILE_ATTRIBUTES: 0x8

    Kernel Generated Triage Dump



    DUMP_TYPE: 2



    BUGCHECK_P1: fffff8031710bec8



    BUGCHECK_P2: ff



    BUGCHECK_P3: 96



    BUGCHECK_P4: fffff8031710bec8



    READ_ADDRESS: fffff80318465388: Unable to get MiVisibleState

    Unable to get NonPagedPoolStart

    Unable to get NonPagedPoolEnd

    Unable to get PagedPoolStart

    Unable to get PagedPoolEnd

    fffff8031710bec8



    CURRENT_IRQL: 0



    FAULTING_IP:

    +0

    fffff803`1710bec8 0000 add byte ptr [rax],al



    ADDITIONAL_DEBUG_TEXT: The trap occurred when interrupts are disabled on the target.



    BUGCHECK_STR: DISABLED_INTERRUPT_FAULT



    CPU_COUNT: 8



    CPU_MHZ: e10



    CPU_VENDOR: GenuineIntel



    CPU_FAMILY: 6



    CPU_MODEL: 9e



    CPU_STEPPING: 9



    CUSTOMER_CRASH_COUNT: 1



    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



    PROCESS_NAME: System



    ANALYSIS_SESSION_HOST: DESKTOP-72M9HPN



    ANALYSIS_SESSION_TIME: 08-22-2019 22:16:34.0794



    ANALYSIS_VERSION: 10.0.18362.1 amd64fre



    TRAP_FRAME: fffff8031a4634a0 -- (.trap 0xfffff8031a4634a0)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=00000000ffffffff rbx=0000000000000000 rcx=fffff80317106180

    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff8031710bec8 rsp=fffff8031a463630 rbp=fffff8031710be01

    r8=0000000000000000 r9=0000000000000000 r10=fffff80317106180

    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up di ng nz na po nc

    fffff803`1710bec8 0000 add byte ptr [rax],al ds:00000000`ffffffff=??

    Resetting default scope



    LAST_CONTROL_TRANSFER: from fffff803181d4669 to fffff803181c3ab0



    FAILED_INSTRUCTION_ADDRESS:

    +0

    fffff803`1710bec8 0000 add byte ptr [rax],al



    STACK_TEXT:

    fffff803`1a463358 fffff803`181d4669 : 00000000`0000000a fffff803`1710bec8 00000000`000000ff 00000000`00000096 : nt!KeBugCheckEx

    fffff803`1a463360 fffff803`181d12eb : 00000000`00000000 ffff850e`fd1a45a0 fffff803`1a4636c0 fffff80d`6a937a1d : nt!KiBugCheckDispatch+0x69

    fffff803`1a4634a0 fffff803`1710bec8 : 00000001`0c1afec4 00000001`0c1ae202 00000000`00000002 00000001`00000000 : nt!KiPageFault+0x42b

    fffff803`1a463630 00000001`0c1afec4 : 00000001`0c1ae202 00000000`00000002 00000001`00000000 ffff850e`f70fa320 : 0xfffff803`1710bec8

    fffff803`1a463638 00000001`0c1ae202 : 00000000`00000002 00000001`00000000 ffff850e`f70fa320 fffff80d`67b86d66 : 0x00000001`0c1afec4

    fffff803`1a463640 00000000`00000002 : 00000001`00000000 ffff850e`f70fa320 fffff80d`67b86d66 ffff0001`00010000 : 0x00000001`0c1ae202

    fffff803`1a463648 00000001`00000000 : ffff850e`f70fa320 fffff80d`67b86d66 ffff0001`00010000 00000001`00000000 : 0x2

    fffff803`1a463650 ffff850e`f70fa320 : fffff80d`67b86d66 ffff0001`00010000 00000001`00000000 ffff850e`f70fa000 : 0x00000001`00000000

    fffff803`1a463658 fffff80d`67b86d66 : ffff0001`00010000 00000001`00000000 ffff850e`f70fa000 00000000`da678400 : 0xffff850e`f70fa320

    fffff803`1a463660 ffffffff`da678340 : 00000001`0c1afec4 ffffa701`ffffffff ffff850e`f68c9d00 ffff850e`f7149eb0 : storport!RaidAdapterReleaseInterruptLock+0x4a

    fffff803`1a463690 00000001`0c1afec4 : ffffa701`ffffffff ffff850e`f68c9d00 ffff850e`f7149eb0 ffff850e`f70fa428 : 0xffffffff`da678340

    fffff803`1a463698 ffffa701`ffffffff : ffff850e`f68c9d00 ffff850e`f7149eb0 ffff850e`f70fa428 fffff80d`67b8259a : 0x00000001`0c1afec4

    fffff803`1a4636a0 ffff850e`f68c9d00 : ffff850e`f7149eb0 ffff850e`f70fa428 fffff80d`67b8259a ffff850e`f70fa318 : 0xffffa701`ffffffff

    fffff803`1a4636a8 ffff850e`f7149eb0 : ffff850e`f70fa428 fffff80d`67b8259a ffff850e`f70fa318 00000000`00000002 : 0xffff850e`f68c9d00

    fffff803`1a4636b0 ffff850e`f70fa428 : fffff80d`67b8259a ffff850e`f70fa318 00000000`00000002 fffff803`17106180 : 0xffff850e`f7149eb0

    fffff803`1a4636b8 fffff80d`67b8259a : ffff850e`f70fa318 00000000`00000002 fffff803`17106180 00000000`00000001 : 0xffff850e`f70fa428

    fffff803`1a4636c0 fffff80d`00000020 : 00000002`fa859214 00000000`00000004 ffff850e`f70fa000 00000000`00000008 : storport!StorPortNotification+0x2aa

    fffff803`1a4637a0 00000002`fa859214 : 00000000`00000004 ffff850e`f70fa000 00000000`00000008 00000000`00000000 : 0xfffff80d`00000020

    fffff803`1a4637a8 00000000`00000004 : ffff850e`f70fa000 00000000`00000008 00000000`00000000 fffff803`18114d2d : 0x00000002`fa859214

    fffff803`1a4637b0 ffff850e`f70fa000 : 00000000`00000008 00000000`00000000 fffff803`18114d2d fffff803`17106180 : 0x4

    fffff803`1a4637b8 00000000`00000008 : 00000000`00000000 fffff803`18114d2d fffff803`17106180 00000002`fe840000 : 0xffff850e`f70fa000

    fffff803`1a4637c0 00000000`00000000 : fffff803`18114d2d fffff803`17106180 00000002`fe840000 00000000`00000000 : 0x8





    THREAD_SHA1_HASH_MOD_FUNC: cc32a1648e551ffbfe4904b39f59ea2c7489ba46



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6ae36b11ffbefc66a3f657342b114e573b07412f



    THREAD_SHA1_HASH_MOD: ef3e6dd1f56d20cef2b15527b9d0302555ca7073



    FOLLOWUP_IP:

    storport!RaidAdapterReleaseInterruptLock+4a

    fffff80d`67b86d66 488b5c2430 mov rbx,qword ptr [rsp+30h]



    FAULT_INSTR_CODE: 245c8b48



    SYMBOL_STACK_INDEX: 9



    SYMBOL_NAME: storport!RaidAdapterReleaseInterruptLock+4a



    FOLLOWUP_NAME: MachineOwner



    MODULE_NAME: storport



    IMAGE_NAME: storport.sys



    DEBUG_FLR_IMAGE_TIMESTAMP: 0



    IMAGE_VERSION: 10.0.17134.376



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 4a



    FAILURE_BUCKET_ID: DISABLED_INTERRUPT_FAULT_CODE_AV_BAD_IP_storport!RaidAdapterReleaseInterruptLock



    BUCKET_ID: DISABLED_INTERRUPT_FAULT_CODE_AV_BAD_IP_storport!RaidAdapterReleaseInterruptLock



    PRIMARY_PROBLEM_CLASS: DISABLED_INTERRUPT_FAULT_CODE_AV_BAD_IP_storport!RaidAdapterReleaseInterruptLock



    TARGET_TIME: 2019-08-23T02:54:53.000Z



    OSBUILD: 17134



    OSSERVICEPACK: 950



    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: 2019-08-07 02:34:16



    BUILDDATESTAMP_STR: 160101.0800



    BUILDLAB_STR: WinBuild



    BUILDOSVER_STR: 10.0.17134.950



    ANALYSIS_SESSION_ELAPSED_TIME: 11c3



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:disabled_interrupt_fault_code_av_bad_ip_storport!raidadapterreleaseinterruptlock



    FAILURE_ID_HASH: {8fd8016f-3b4c-44e8-1c81-56630db9b9ad}



    Followup: MachineOwner

    ---------



    Here is number 2

    Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\Minidump\082219-9390-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 17134 MP (8 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 17134.1.amd64fre.rs4_release.180410-1804

    Machine Name:

    Kernel base = 0xfffff803`3b600000 PsLoadedModuleList = 0xfffff803`3b9ad0f0

    Debug session time: Thu Aug 22 19:39:01.271 2019 (UTC - 5:00)

    System Uptime: 0 days 1:49:28.455

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    .............................

    Loading User Symbols

    Loading unloaded module list

    ...............

    For analysis of this file, run !analyze -v

    1: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    SYSTEM_SERVICE_EXCEPTION (3b)

    An exception happened while executing a system service routine.

    Arguments:

    Arg1: 00000000c000001d, Exception code that caused the bugcheck

    Arg2: fffff8033b68e904, Address of the instruction which caused the bugcheck

    Arg3: ffffed80274e6800, Address of the context record for the exception that caused the bugcheck

    Arg4: 0000000000000000, zero.



    Debugging Details:

    ------------------



    *** WARNING: Unable to verify timestamp for win32k.sys



    KEY_VALUES_STRING: 1





    PROCESSES_ANALYSIS: 1



    SERVICE_ANALYSIS: 1



    STACKHASH_ANALYSIS: 1



    TIMELINE_ANALYSIS: 1





    DUMP_CLASS: 1



    DUMP_QUALIFIER: 400



    BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804



    DUMP_TYPE: 2



    BUGCHECK_P1: c000001d



    BUGCHECK_P2: fffff8033b68e904



    BUGCHECK_P3: ffffed80274e6800



    BUGCHECK_P4: 0



    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.



    FAULTING_IP:

    nt!ExReleaseResourceLite+d4

    fffff803`3b68e904 c4 ???



    CONTEXT: ffffed80274e6800 -- (.cxr 0xffffed80274e6800)

    rax=0000000000000000 rbx=ffffc085e4977010 rcx=ffffd400d3020180

    rdx=0000000000000000 rsi=ffffed80274e7440 rdi=0000000000000000

    rip=fffff8033b68e904 rsp=ffffed80274e71f8 rbp=0000000000000000

    r8=ffffed80274e7230 r9=0000000000000030 r10=0000000000000001

    r11=0000000000000100 r12=0000000000000000 r13=ffffc085e4977010

    r14=ffffed80274e7440 r15=ffffab04751f8670

    iopl=0 nv up ei ng nz na pe nc

    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282

    nt!ExReleaseResourceLite+0xd4:

    fffff803`3b68e904 c4 ???

    Resetting default scope



    BUGCHECK_STR: 0x3B_c000001d



    CPU_COUNT: 8



    CPU_MHZ: e10



    CPU_VENDOR: GenuineIntel



    CPU_FAMILY: 6



    CPU_MODEL: 9e



    CPU_STEPPING: 9



    CUSTOMER_CRASH_COUNT: 1



    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



    PROCESS_NAME: Dropbox.exe



    CURRENT_IRQL: 0



    ANALYSIS_SESSION_HOST: DESKTOP-72M9HPN



    ANALYSIS_SESSION_TIME: 08-22-2019 22:19:46.0490



    ANALYSIS_VERSION: 10.0.18362.1 amd64fre



    MISALIGNED_IP:

    nt!ExReleaseResourceLite+d4

    fffff803`3b68e904 c4 ???



    LAST_CONTROL_TRANSFER: from ffffed80274e7440 to fffff8033b68e904



    STACK_TEXT:

    ffffed80`274e71f8 ffffed80`274e7440 : fffff804`fb95c9eb ffffed80`274e7440 00000000`00000002 ffffc085`e4977010 : nt!ExReleaseResourceLite+0xd4

    ffffed80`274e7258 fffff804`fb95c9eb : ffffed80`274e7440 00000000`00000002 ffffc085`e4977010 ffffed80`274e7440 : 0xffffed80`274e7440

    ffffed80`274e7260 fffff804`fba30663 : ffffc085`e4977160 00000000`00000000 ffffab04`63891af0 ffffc085`e4977010 : Ntfs!NtfsReleaseFcbEx+0x97

    ffffed80`274e7290 fffff804`fba2f644 : ffffed80`274e7440 ffffab04`751f8670 00000000`00000000 ffffab04`00000003 : Ntfs!NtfsCommonQueryInformation+0xe53

    ffffed80`274e73a0 fffff804`fba2f550 : ffffed80`274e7440 ffffab04`751f8670 ffffab04`751f8670 ffffab04`751f8670 : Ntfs!NtfsFsdDispatchSwitch+0xd4

    ffffed80`274e7420 fffff803`3b689839 : 00000000`00000005 ffffed80`274e7770 00000000`00060874 fffff804`fa00629c : Ntfs!NtfsFsdDispatchWait+0x40

    ffffed80`274e76a0 fffff804`fa007207 : ffffed80`274e7770 fffff804`fa0053b4 00000000`00000000 00000000`00000005 : nt!IofCallDriver+0x59

    ffffed80`274e76e0 fffff804`fa0051c6 : ffffed80`274e7770 00000000`00000001 00000000`00000000 00000000`00000014 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x157

    ffffed80`274e7750 fffff803`3b689839 : ffffab04`655caef0 00000000`20206f49 00000000`00000000 00000000`00000001 : FLTMGR!FltpDispatch+0xb6

    ffffed80`274e77b0 fffff803`3b67aeb4 : 00000000`20206f49 ffffab04`00000000 ffffab04`64536700 00000000`00000001 : nt!IofCallDriver+0x59

    ffffed80`274e77f0 fffff803`3bb047d3 : 00000000`00000004 ffffed80`274e7a80 00000000`00000001 00000000`00000000 : nt!IopCallDriverReference+0xf4

    ffffed80`274e7860 fffff803`3b7bb143 : ffffab04`64536700 00000000`1e52e868 00000000`1e52f120 00000000`00000028 : nt!NtQueryInformationFile+0x473

    ffffed80`274e7990 00007ff8`38feabc4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

    00000000`1e52e818 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`38feabc4





    THREAD_SHA1_HASH_MOD_FUNC: 003705c762640edb3ba461027e60e777b9107996



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 54f3238c41228163f406f2b0892667119bb59f06



    THREAD_SHA1_HASH_MOD: b91bc680876e53a0d8cb0c101e0668b8fad0c7b8



    FOLLOWUP_IP:

    nt!ExReleaseResourceLite+d4

    fffff803`3b68e904 c4 ???



    FAULT_INSTR_CODE: c35f50c4



    SYMBOL_STACK_INDEX: 0



    SYMBOL_NAME: nt!ExReleaseResourceLite+d4



    FOLLOWUP_NAME: MachineOwner



    IMAGE_NAME: hardware



    DEBUG_FLR_IMAGE_TIMESTAMP: 0



    IMAGE_VERSION: 10.0.17134.950



    STACK_COMMAND: .cxr 0xffffed80274e6800 ; kb



    MODULE_NAME: hardware



    FAILURE_BUCKET_ID: IP_MISALIGNED



    BUCKET_ID: IP_MISALIGNED



    PRIMARY_PROBLEM_CLASS: IP_MISALIGNED



    TARGET_TIME: 2019-08-23T00:39:01.000Z



    OSBUILD: 17134



    OSSERVICEPACK: 950



    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: 2019-08-07 02:34:16



    BUILDDATESTAMP_STR: 180410-1804



    BUILDLAB_STR: rs4_release



    BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804



    ANALYSIS_SESSION_ELAPSED_TIME: 4819



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:ip_misaligned



    FAILURE_ID_HASH: {201b0e5d-db2a-63d2-77be-8ce8ff234750}



    Followup: MachineOwner

    ---------



    Here is Number 3




    Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\Minidump\082219-9750-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 17134 MP (8 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Machine Name:

    Kernel base = 0xfffff802`8e80f000 PsLoadedModuleList = 0xfffff802`8ebbc0f0

    Debug session time: Thu Aug 22 21:32:59.244 2019 (UTC - 5:00)

    System Uptime: 0 days 0:18:23.927

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ..............................

    Loading User Symbols

    Loading unloaded module list

    .............

    For analysis of this file, run !analyze -v

    0: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    DRIVER_PORTION_MUST_BE_NONPAGED (d3)

    When possible, the guilty driver's name (Unicode string) is printed on

    the bugcheck screen and saved in KiBugCheckDriver.

    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 marking code or data as pageable when it should be

    marked nonpaged.

    If kernel debugger is available get stack backtrace.

    Arguments:

    Arg1: fffff80e89ba1010, memory referenced

    Arg2: 00000000000000ff, IRQL

    Arg3: 0000000000000016, value 0 = read operation, 1 = write operation

    Arg4: fffff8028ea44140, address which referenced memory



    Debugging Details:

    ------------------





    KEY_VALUES_STRING: 1





    PROCESSES_ANALYSIS: 1



    SERVICE_ANALYSIS: 1



    STACKHASH_ANALYSIS: 1



    TIMELINE_ANALYSIS: 1





    DUMP_CLASS: 1



    DUMP_QUALIFIER: 400



    BUILD_VERSION_STRING: 10.0.17134.950 (WinBuild.160101.0800)



    DUMP_FILE_ATTRIBUTES: 0x8

    Kernel Generated Triage Dump



    DUMP_TYPE: 2



    BUGCHECK_P1: fffff80e89ba1010



    BUGCHECK_P2: ff



    BUGCHECK_P3: 16



    BUGCHECK_P4: fffff8028ea44140



    WRITE_ADDRESS: fffff8028ec5b388: Unable to get MiVisibleState

    Unable to get NonPagedPoolStart

    Unable to get NonPagedPoolEnd

    Unable to get PagedPoolStart

    Unable to get PagedPoolEnd

    fffff80e89ba1010



    CURRENT_IRQL: 0



    FAULTING_IP:

    nt!IopUpdateMinidumpContext+160

    fffff802`8ea44140 0000 add byte ptr [rax],al



    CPU_COUNT: 8



    CPU_MHZ: e10



    CPU_VENDOR: GenuineIntel



    CPU_FAMILY: 6



    CPU_MODEL: 9e



    CPU_STEPPING: 9



    CUSTOMER_CRASH_COUNT: 1



    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



    BUGCHECK_STR: 0xD3



    PROCESS_NAME: System



    ANALYSIS_SESSION_HOST: DESKTOP-72M9HPN



    ANALYSIS_SESSION_TIME: 08-22-2019 22:22:22.0533



    ANALYSIS_VERSION: 10.0.18362.1 amd64fre



    TRAP_FRAME: fffff80290c633d0 -- (.trap 0xfffff80290c633d0)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=fffff80e89ba1010 rbx=0000000000000000 rcx=ffffe408ddf100b0

    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff8028ea44140 rsp=fffff80290c63568 rbp=0000000000000000

    r8=fffff80290c635a0 r9=fffff80290c635a8 r10=fffff8028d976180

    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up di pl nz na pe nc

    nt!IopUpdateMinidumpContext+0x160:

    fffff802`8ea44140 0000 add byte ptr [rax],al ds:fffff80e`89ba1010=48

    Resetting default scope



    MISALIGNED_IP:

    nt!IopUpdateMinidumpContext+160

    fffff802`8ea44140 0000 add byte ptr [rax],al



    LAST_CONTROL_TRANSFER: from fffff8028e9ca669 to fffff8028e9b9ab0



    STACK_TEXT:

    fffff802`90c63288 fffff802`8e9ca669 : 00000000`0000000a fffff80e`89ba1010 00000000`000000ff 00000000`00000016 : nt!KeBugCheckEx

    fffff802`90c63290 fffff802`8e9c72eb : ffffe408`dda2b000 fffff80e`8ae937ba 00000000`00000001 ffffe408`ddf39710 : nt!KiBugCheckDispatch+0x69

    fffff802`90c633d0 fffff802`8ea44140 : fffff802`8e8a81c5 000001c0`70bd89f9 fffff802`8e8a8bb2 00000196`3978c811 : nt!KiPageFault+0x42b

    fffff802`90c63568 00000000`00000000 : 00000000`00000000 ffffe408`dd72a820 fffff802`8ea81da3 ffffe408`ddbe20f0 : nt!IopUpdateMinidumpContext+0x160





    THREAD_SHA1_HASH_MOD_FUNC: fa8460cec85d1add60bd85c10a486b56f0ba1b3f



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d93c63fc0f46ffb00b5d220bbf6e52a8fbd26d9c



    THREAD_SHA1_HASH_MOD: d084f7dfa548ce4e51810e4fd5914176ebc66791



    FOLLOWUP_IP:

    nt!IopUpdateMinidumpContext+160

    fffff802`8ea44140 0000 add byte ptr [rax],al



    FAULT_INSTR_CODE: 8b480000



    SYMBOL_STACK_INDEX: 3



    SYMBOL_NAME: nt!IopUpdateMinidumpContext+160



    FOLLOWUP_NAME: MachineOwner



    IMAGE_NAME: hardware



    DEBUG_FLR_IMAGE_TIMESTAMP: 0



    IMAGE_VERSION: 10.0.17134.950



    STACK_COMMAND: .thread ; .cxr ; kb



    MODULE_NAME: hardware



    FAILURE_BUCKET_ID: IP_MISALIGNED



    BUCKET_ID: IP_MISALIGNED



    PRIMARY_PROBLEM_CLASS: IP_MISALIGNED



    TARGET_TIME: 2019-08-23T02:32:59.000Z



    OSBUILD: 17134



    OSSERVICEPACK: 950



    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: 2019-08-07 02:34:16



    BUILDDATESTAMP_STR: 160101.0800



    BUILDLAB_STR: WinBuild



    BUILDOSVER_STR: 10.0.17134.950



    ANALYSIS_SESSION_ELAPSED_TIME: ac5



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:ip_misaligned



    FAILURE_ID_HASH: {201b0e5d-db2a-63d2-77be-8ce8ff234750}



    Followup: MachineOwner

    ---------



    All drivers are updated. I've reset windows and received a BSOD moments after.

    :)
     
    SL101000999, Aug 23, 2019
    #1
  2. SLARTYBART
    Slartybart Win User

    Windows 10 fails to update


    When you finish testing the Avast suggestion, make sure that you restart your machine.

    Then if the issue persists, please return to the trouble shooting list in post# 89

    I think there are three steps that remain; the WU troubleshooter, reset WU components, and manual WU reset.
     
    Slartybart, Aug 23, 2019
    #2
  3. NEWTEKIE1
    newtekie1 Win User
    Is this a symptom of a failing PSU?

    If the machine is failing to POST then it isn't related to anything with the trojan/worm.

    It can be a failing battery, try what imperialreign suggests to test.
     
    newtekie1, Aug 23, 2019
    #3
  4. CHIDEOCK
    chideock Win User

    Machine Constantly Failing

    KB4025339 Fails Install 0x80070564


    Thanks
    I am trying Eagle 51's suggestions now. Windows Update troubleshooter found a bunch of errors and fixed all but one.The update is trying to download KB4025339 again. I'll see what happens. At step one troubleshooter finishes with one error unresolved "Potential Windows Update Database Error Detected-Not Fixed". Windows update stalled at 0%.

    At step 2 same troubleshooter error. The KB finished a new download failed to install.
    Did step 3 KB has downloaded but fails to install.

    If Eagle's suggestion doesn't work I'll try EdTittel's suggestion

    Tried bothe Eagle & Ed 's suggestions - do not work. Anyone else?

    I have noticed that the latest update for my nvidia drivers has failed to update. Wondering about that!
     
    chideock, Aug 23, 2019
    #4
Thema:

Machine Constantly Failing

Loading...

  1. Machine Constantly Failing - Similar Threads - Machine Constantly Failing

  2. Camera constantly fails

    in Windows 10 Gaming
    Camera constantly fails: I have a Surface Pro 8 and it constantly tells me there is no camera installed. I use the troubleshooter and get it working but this is not a useful fix as it happens constantly. Most days I have to log on using my PIN as the camera for Windows Hello does not work. Then I log...

  3. Camera constantly fails

    in Windows 10 Software and Apps
    Camera constantly fails: I have a Surface Pro 8 and it constantly tells me there is no camera installed. I use the troubleshooter and get it working but this is not a useful fix as it happens constantly. Most days I have to log on using my PIN as the camera for Windows Hello does not work. Then I log...

  4. Windows update constantly failing

    in Windows 10 Software and Apps
    Windows update constantly failing: Please help with Windows update constantly failing,1/ System is Windows 10 Home, Version 22H2, OS build 19045.35162/ The test from Windows Update window I have retried multiple times , getting the same:"There were some problems installing updates, but we'll try again later....

  5. Installation failed in Windows Machine

    in Windows 10 Installation and Upgrade
    Installation failed in Windows Machine: While Installing Third-party Application using MSI Installer some application failed with Error " The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance."...

  6. New Machine Constantly Having BSOD

    in Windows 10 Drivers and Hardware
    New Machine Constantly Having BSOD: Hello! I have a new pre-built machine that has the following hardware: AMD Ryzen 5 3600 6-core Processor @ 3593 MHz 16 GB of Thermaltake ram RGB Gigabyte GeForce RTX 3060 Ti OC 8GB B450 AORUS PRO WIFI rev. 1.x motherboard Thermaltake Water 3.0 360 ARGB cooler Long...

  7. Update constantly failing

    in Windows 10 Installation and Upgrade
    Update constantly failing: Windows 10 trying every day or so to update but each time fails. No error code but message "Windows could not configure one or more system components. To install window, re-start . . . . ." I'm on a 64-bit OS with 22.3Gb free on drive C, plus much more free on D, F, and K K...

  8. Machines Fail to Start and Initialize

    in Windows 10 Virtualization
    Machines Fail to Start and Initialize: My Windows 8.1 virtual machines worked fine. I just upgraded to Windows 10 and when I attempt to start the machines I get the error '(machine name)' failed to start. and '(machine name)' could not initialize. The same thing happens when I attempt to create a new virtual...

  9. Sluggish Machine, constant thrashing

    in Windows 10 Performance & Maintenance
    Sluggish Machine, constant thrashing: Hi, I have a desktop Windows 10 x64 machine that's been working fine for months/years. It was automatically updated from Win7 last year. Ever since the upgrade it is relatively slow. Last week I installed some more memory for a total of 16GB, in the hope that it would...

  10. Anniversary fails on older machine

    in Windows 10 Installation and Upgrade
    Anniversary fails on older machine: Twice I have been notified of awaiting update and to restart. The update is the Anniversary version. After over an hour of time, the computer will fail to boot and after fiddling you are notified you must restart to return to the previous version. That restart took me over an...