Help! Fall Creators Update Causes BSODs.


  1. Posts : 3
    Win 10
       #1

    Help! Fall Creators Update Causes BSODs.


    The Fall Creators Update has been stuck for me for months. I finally figured out how to get it to install. Before I did that, I updated my video drivers to make sure it wasn't a problem.

    Installation went fine. It rebooted at the end of installation, which also went fine. It finished up the last touches on that final boot and login.

    On my first restart, I got a BSOD (driver irql not less or equal). Now, EVERY time I boot, I get that BSOD.

    Safe Mode with Networking also causes the BSOD, but Safe Mode without networking seems to work. All my system restore points seem to have disappeared.

    Any help would be appreciated!
      My Computer


  2. Posts : 5,299
    Windows 11 Pro 64-bit
       #2

    Check manufacturer of your computer to see if there are new device drivers also upgrade BIOS firmware.
      My Computer


  3. Posts : 3
    Win 10
    Thread Starter
       #3

    I don't know if this is the usual issue, given that this update caused BSOD nightmares for so many people.

    How can I narrow down what the problem is? If I'm getting BSODs in Safe Mode with Networking, it must be a core component.
      My Computer


  4. Posts : 5,299
    Windows 11 Pro 64-bit
       #4

    You can get help from below forum link.

    https://www.tenforums.com/bsod-crashes-debugging/
      My Computer


  5. Posts : 1,572
    win10 home
       #5

    Have a look at Reliability History and see if there is a recurring problem with either your drivers or graphic card or both.
      My Computer


  6. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #6

    Please fill out your System Specs:

    See here: System Specs - Fill in at Ten Forums

    The more information you can provide the better.
      My Computers


  7. Posts : 3
    Win 10
    Thread Starter
       #7

    So the recovery boot mode's option to revert to the prior version of Windows didn't work. However, by booting into Safe Mode without networking, I was able to successfully revert to the prior version (1709). Now, I at least have a working system.

    Before I did that, I was able to recover a crash dump:


    ==================================================================

    Microsoft (R) Windows Debugger Version 10.0.18303.1000 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\MEMORY.DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


    ************* Path validation summary **************
    Response Time (ms) Location
    Deferred srv*
    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 17134 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 17134.1.amd64fre.rs4_release.180410-1804
    Machine Name:
    Kernel base = 0xfffff802`7cca5000 PsLoadedModuleList = 0xfffff802`7d053170
    Debug session time: Sat Jan 19 13:28:38.116 2019 (UTC - 8:00)
    System Uptime: 0 days 0:00:07.114
    Loading Kernel Symbols
    .....................................Page 20102f850 too large to be in the dump file.
    .............Page 201002703 too large to be in the dump file.
    .............
    ................................................................
    ..........................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 000000e0`cfd3a018). Type ".hh dbgerr001" for details
    Loading unloaded module list
    .........
    For analysis of this file, run !analyze -v
    nt!KeBugCheckEx:
    fffff802`7ce4dca0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffe02`0db06150=000000000000000a
    2: 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: 0000000000000003, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff801b57820c5, address which referenced memory

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


    KEY_VALUES_STRING: 1


    PROCESSES_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 401

    BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

    SYSTEM_MANUFACTURER: System manufacturer

    SYSTEM_PRODUCT_NAME: System Product Name

    SYSTEM_SKU: SKU

    SYSTEM_VERSION: System Version

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: 1302

    BIOS_DATE: 03/15/2018

    BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

    BASEBOARD_PRODUCT: PRIME Z270-A

    BASEBOARD_VERSION: Rev 1.xx

    DUMP_TYPE: 1

    BUGCHECK_P1: 3

    BUGCHECK_P2: 2

    BUGCHECK_P3: 0

    BUGCHECK_P4: fffff801b57820c5

    READ_ADDRESS: 0000000000000003

    CURRENT_IRQL: 2

    FAULTING_IP:
    cmdhlp+20c5
    fffff801`b57820c5 0f1002 movups xmm0,xmmword ptr [rdx]

    CPU_COUNT: 8

    CPU_MHZ: 1068

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 9e

    CPU_STEPPING: 9

    CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)

    BLACKBOXBSD: 1 (!blackboxbsd)


    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: AV

    PROCESS_NAME: svchost.exe

    ANALYSIS_SESSION_HOST: MAINPC

    ANALYSIS_SESSION_TIME: 01-19-2019 18:03:01.0042

    ANALYSIS_VERSION: 10.0.18303.1000 amd64fre

    TRAP_FRAME: fffffe020db06290 -- (.trap 0xfffffe020db06290)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000000003ce rbx=0000000000000000 rcx=000000000000dd86
    rdx=0000000000000003 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff801b57820c5 rsp=fffffe020db06420 rbp=0000000000000ab8
    r8=0000000000000000 r9=0000000000000005 r10=0000000000000000
    r11=fffff801b5784493 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na po nc
    cmdhlp+0x20c5:
    fffff801`b57820c5 0f1002 movups xmm0,xmmword ptr [rdx] ds:00000000`00000003=????????????????????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff8027ce5e869 to fffff8027ce4dca0

    STACK_TEXT:
    fffffe02`0db06148 fffff802`7ce5e869 : 00000000`0000000a 00000000`00000003 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffffe02`0db06150 fffff802`7ce5b4e5 : fffffe02`0db06440 fffff802`7cd71f4a fffffe02`0db06401 fffffe02`0db06428 : nt!KiBugCheckDispatch+0x69
    fffffe02`0db06290 fffff801`b57820c5 : ffffe607`f3a1ce03 fffff801`b39969e9 ffffe607`f2d39d02 00000000`00000028 : nt!KiPageFault+0x425
    fffffe02`0db06420 fffff801`b42a64c2 : ffffe607`ee39f280 fffffe02`0db06560 fffffe02`0db06758 fffff801`b3c0f0cd : cmdhlp+0x20c5
    fffffe02`0db06460 fffff801`b42a5087 : 00000000`00000041 fffffe02`0db06c40 fffffe02`0db06d30 00000000`00000000 : NETIO!ProcessCallout+0x862
    fffffe02`0db065f0 fffff801`b42a2d88 : ffffe607`ec810b90 fffffe02`0db06c40 00000000`00000000 fffffe02`0db069b0 : NETIO!ArbitrateAndEnforce+0x4a7
    fffffe02`0db067e0 fffff801`b3ccb71b : ffffe607`f3a132c0 fffffe02`0db06d00 00000000`00000000 00000000`00000000 : NETIO!KfdClassify+0x2f8
    fffffe02`0db06c00 fffff801`b3c56de5 : 00000000`00000040 8a000001`87a7e867 00000000`00000005 ffffe607`f3a132c0 : tcpip!AleNotifyEndpointDeactivate+0x71e97
    fffffe02`0db07170 fffff801`b3c56589 : ffffe607`f2b018c0 ffffe607`ef013950 ffffe607`f3a136d0 ffffe607`f3a135c0 : tcpip!UdpCloseEndpoint+0x851
    fffffe02`0db07480 fffff801`b4e5739c : 00000000`00000000 00000000`00000000 ffffe607`f2fa0fc0 00000000`00000000 : tcpip!UdpTlProviderCloseEndpoint+0x9
    fffffe02`0db074b0 fffff801`b4e363a6 : ffffe607`f3a135c0 ffffe607`f3a136d0 ffffe607`f2b018c0 ffffe607`f3a20c20 : afd!AfdTLCloseEndpoint+0x48
    fffffe02`0db074f0 fffff801`b4e56b76 : ffffe607`f3a135c0 ffffe607`f3a136d0 ffffe607`f3a135c0 fffffe02`0db07608 : afd!AfdCloseTransportEndpoint+0x76
    fffffe02`0db075d0 fffff801`b4e57030 : 00000000`00000001 ffffe607`f3a135c0 ffffe607`f2cd5dc0 00000000`00000000 : afd!AfdCleanupCore+0x376
    fffffe02`0db07720 fffff802`7ccbe199 : 00000000`00000290 fffff802`7ccbe465 ffffe607`f2ff1a20 00000000`001f0001 : afd!AfdDispatch+0x80
    fffffe02`0db07790 fffff802`7d18322e : ffffe607`f2ff1a20 00000000`00000000 00000000`00000000 000000e0`d07fe510 : nt!IofCallDriver+0x59
    fffffe02`0db077d0 fffff802`7d168b02 : ffffe607`f2ff19f0 00000000`00000001 ffffd40c`00000000 00000000`00007fcd : nt!IopCloseFile+0x15e
    fffffe02`0db07860 fffff802`7d17048d : ffffe607`f2fa0a80 00000000`00000000 00000000`08f0d180 ffff58c0`f73596ae : nt!ObCloseHandleTableEntry+0x212
    fffffe02`0db079a0 fffff802`7ce5e343 : ffffe607`f37ed080 00000208`7ac3b8f0 ffffe607`f37ed080 fffffe02`0db07a80 : nt!NtClose+0xcd
    fffffe02`0db07a00 00007ff9`1134a094 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    000000e0`d07ff1f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`1134a094


    THREAD_SHA1_HASH_MOD_FUNC: 1d51f5bb92538e78298732a1c3399f1616cfdc8d

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 196b2954e68c7e37607db66e2e38c87261d104d8

    THREAD_SHA1_HASH_MOD: 9593461777ea2afa5e4824250b019577072174b0

    FOLLOWUP_IP:
    cmdhlp+20c5
    fffff801`b57820c5 0f1002 movups xmm0,xmmword ptr [rdx]

    FAULT_INSTR_CODE: f302100f

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: cmdhlp+20c5

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: cmdhlp

    IMAGE_NAME: cmdhlp.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 5a724285

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 20c5

    FAILURE_BUCKET_ID: AV_cmdhlp!unknown_function

    BUCKET_ID: AV_cmdhlp!unknown_function

    PRIMARY_PROBLEM_CLASS: AV_cmdhlp!unknown_function

    TARGET_TIME: 2019-01-19T21:28:38.000Z

    OSBUILD: 17134

    OSSERVICEPACK: 228

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2018-08-02 20:10:45

    BUILDDATESTAMP_STR: 180410-1804

    BUILDLAB_STR: rs4_release

    BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

    ANALYSIS_SESSION_ELAPSED_TIME: 675

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:av_cmdhlp!unknown_function

    FAILURE_ID_HASH: {d8bdf104-ead9-2192-523c-997aafeec77a}

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

    ==================================================================



    Am I interpreting it correctly that the problem was caused by cmdhlp.sys?
    That file belongs to Comodo Firewall, so it makes sense that that could be the source of the problem.
      My Computer


  8. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #8

    Can you zip the dump and upload it here please?

    and fill out system specs
      My Computers


  9. Posts : 41,420
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    The log collectors can be ran while in safe mode.
    The results can be saved to a flash drive and moved to another computer in case networking is not available.
    Please run both the DM and BETA log collectors and post a zip into the thread:
    BSOD - Posting Instructions - Windows 10 Forums

    The above text report implicated the Comodo firewall driver but there may be another driver that caused the BSOD.
      My Computer


 

  Related Discussions
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 02:14.
Find Us




Windows 10 Forums