Windows 10: Keep getting BSOD since last Win10 feature update

Discus and support Keep getting BSOD since last Win10 feature update in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi there, Since installing the last Win10 feature update on 29/10, I keep getting a BSOD almost on a daily basis. In Event Viewer, I can see that... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Erik Sundermann, Nov 19, 2019.

  1. ERIK SUNDERMANN
    Erik Sundermann Win User

    Keep getting BSOD since last Win10 feature update


    Hi there,


    Since installing the last Win10 feature update on 29/10, I keep getting a BSOD almost on a daily basis.

    In Event Viewer, I can see that the same error is reported after rebooting from BSOD:

    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff800572dca64, 0xffff810bbf0cf288, 0xffff810bbf0cead0). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: edfaabae-31d0-4ee2-a3b8-d4c4d81de3ba.

    I have installed WinDbg to have a look at the dump file.

    Below is the output from !analyze -v

    Can anyone help me make sense of what is causing the problem?


    Thx,


    Erik


    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8056c8dca64, The address that the exception occurred at
    Arg3: ffffc88c6dbbf288, Exception Record Address
    Arg4: ffffc88c6dbbead0, Context Record Address

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

    KEY_VALUES_STRING: 1


    Key : AV.Dereference

    Value: NullClassPtr


    Key : AV.Fault

    Value: Read


    PROCESSES_ANALYSIS: 1

    SERVICE_ANALYSIS: 1


    STACKHASH_ANALYSIS: 1


    TIMELINE_ANALYSIS: 1

    DUMP_CLASS: 1


    DUMP_QUALIFIER: 401


    BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202


    SYSTEM_MANUFACTURER: Microsoft Corporation


    SYSTEM_PRODUCT_NAME: Surface Book 2


    SYSTEM_SKU: Surface_Book_1793


    SYSTEM_VERSION: D:0B:08K:1F:5C:10P:38


    BIOS_VENDOR: Microsoft Corporation


    BIOS_VERSION: 389.2837.768


    BIOS_DATE: 08/21/2019


    BASEBOARD_MANUFACTURER: Microsoft Corporation


    BASEBOARD_PRODUCT: Surface Book 2


    DUMP_TYPE: 1


    BUGCHECK_P1: ffffffffc0000005


    BUGCHECK_P2: fffff8056c8dca64


    BUGCHECK_P3: ffffc88c6dbbf288


    BUGCHECK_P4: ffffc88c6dbbead0


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.


    FAULTING_IP:

    ndis!NdisGetDeviceReservedExtension+4

    fffff805`6c8dca64 488b4028 mov rax,qword ptr [rax+28h]


    EXCEPTION_RECORD: ffffc88c6dbbf288 -- (.exr 0xffffc88c6dbbf288)
    ExceptionAddress: fffff8056c8dca64 (ndis!NdisGetDeviceReservedExtension+0x0000000000000004)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000000000000028
    Attempt to read from address 0000000000000028

    CONTEXT: ffffc88c6dbbead0 -- (.cxr 0xffffc88c6dbbead0)

    rax=0000000000000000 rbx=ffff95087add6000 rcx=ffff95087106e060

    rdx=00003383ff1bfb10 rsi=0000000000000003 rdi=0000000000000000

    rip=fffff8056c8dca64 rsp=ffffc88c6dbbf4c8 rbp=0000000000000000

    r8=0000000000000000 r9=0000000000000000 r10=ffff95086e9ff000

    r11=ffff95086e9ff9a8 r12=0000000000000001 r13=0000000000000002

    r14=fffff8058274b7d0 r15=0000000000000003

    iopl=0 nv up ei ng nz na po nc

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

    ndis!NdisGetDeviceReservedExtension+0x4:

    fffff805`6c8dca64 488b4028 mov rax,qword ptr [rax+28h] ds:002b:00000000`00000028=????????????????

    Resetting default scope


    CPU_COUNT: 8


    CPU_MHZ: 840


    CPU_VENDOR: GenuineIntel


    CPU_FAMILY: 6


    CPU_MODEL: 8e


    CPU_STEPPING: a


    CPU_MICROCODE: 6,8e,a,0 (F,M,S,R) SIG: B4'00000000 (cache) B4'00000000 (init)


    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXNTFS: 1 (!blackboxntfs)


    BLACKBOXPNP: 1 (!blackboxpnp)


    BLACKBOXWINLOGON: 1


    PROCESS_NAME: System


    CURRENT_IRQL: 0


    FOLLOWUP_IP:

    msux64w10+4132

    fffff805`826c4132 48832000 and qword ptr [rax],0


    BUGCHECK_STR: AV


    READ_ADDRESS: 0000000000000028


    DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.


    EXCEPTION_CODE_STR: c0000005

    EXCEPTION_PARAMETER1: 0000000000000000


    EXCEPTION_PARAMETER2: 0000000000000028

    ANALYSIS_SESSION_HOST: ELMO


    ANALYSIS_SESSION_TIME: 11-20-2019 16:43:51.0357


    ANALYSIS_VERSION: 10.0.18362.1 amd64fre


    LAST_CONTROL_TRANSFER: from fffff805826c4132 to fffff8056c8dca64


    STACK_TEXT:

    ffffc88c`6dbbf4c8 fffff805`826c4132 : ffff9508`7add6000 00000000`00000003 00000000`00000000 ffffccfb`f24f386f : ndis!NdisGetDeviceReservedExtension+0x4

    ffffc88c`6dbbf4d0 fffff805`827487a2 : 00000000`00000000 ffff9508`7add6000 00000000`00000003 ffffc88c`6dbbf680 : msux64w10+0x4132

    ffffc88c`6dbbf510 fffff805`6c9b7e80 : ffff9508`7b6ee1a0 ffffc88c`6dbbf628 00000000`00000003 ffff9508`86bccab0 : msux64w10+0x887a2

    ffffc88c`6dbbf570 fffff805`6c9d8064 : 00000000`00000006 00000000`00000000 ffff9508`7b6ee1a0 00000000`00000003 : ndis!ndisMInvokeHalt+0xbc

    ffffc88c`6dbbf5c0 fffff805`6c921db2 : ffff9508`7b6ee1a0 fffff805`0000017e ffff9508`71f6c8c0 fffff805`6c985050 : ndis!ndisMCommonHaltMiniport+0x53c

    ffffc88c`6dbbf670 fffff805`6c9dbb53 : ffff9508`7b6ee1a0 ffffc88c`6dbbf7b0 ffff9508`7b6ef590 ffff9508`86bccab0 : ndis!ndisMHaltMiniport+0x9a

    ffffc88c`6dbbf6b0 fffff805`6c945114 : ffff9508`7b6ee1a0 ffff9508`7b6ee1a0 fffff805`6c985050 fffff805`6c985050 : ndis!ndisPnPRemoveDevice+0x34f

    ffffc88c`6dbbf8f0 fffff805`6c9b919f : ffff9508`7b6ee1a0 fffff805`6c9b9210 ffff9508`7b6ee1a0 ffff9508`7b6ef500 : ndis!ndisPnPRemoveDeviceEx+0x148

    ffffc88c`6dbbf940 fffff805`6c9b9219 : 00000000`00000300 ffff9508`759d7040 ffff9508`6beab9d0 fffff805`6c9aaa30 : ndis!ndisPnPIrpSurpriseRemovalInner+0x13f

    ffffc88c`6dbbfa40 fffff805`66abd465 : ffff9508`6beab9d0 fffff805`6c8b6900 ffff9508`6beab900 ffff9508`6beab9d0 : ndis!ndisQueuedPnPIrpSurpriseRemoval+0x9

    ffffc88c`6dbbfa70 fffff805`66b2a725 : ffff9508`759d7040 00000000`00000080 ffff9508`6bea1380 00000000`00000000 : nt!ExpWorkerThread+0x105

    ffffc88c`6dbbfb10 fffff805`66bc886a : ffffa780`54763180 ffff9508`759d7040 fffff805`66b2a6d0 00000000`00000246 : nt!PspSystemThreadStartup+0x55

    ffffc88c`6dbbfb60 00000000`00000000 : ffffc88c`6dbc0000 ffffc88c`6dbb9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


    THREAD_SHA1_HASH_MOD_FUNC: 5df9ce30f2ae7d678df8d96258f3aa67b8b480e1


    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d6f2faf48327797d02a43583d325dd9c56105f88


    THREAD_SHA1_HASH_MOD: 17f3e392585ab6c18721fdbdf3f550388d23c5d2


    FAULT_INSTR_CODE: 208348


    SYMBOL_STACK_INDEX: 1


    SYMBOL_NAME: msux64w10+4132


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: msux64w10


    IMAGE_NAME: msux64w10.sys


    DEBUG_FLR_IMAGE_TIMESTAMP: 5cff1c5c


    STACK_COMMAND: .cxr 0xffffc88c6dbbead0 ; kb


    BUCKET_ID_FUNC_OFFSET: 4132


    FAILURE_BUCKET_ID: AV_msux64w10!unknown_function


    BUCKET_ID: AV_msux64w10!unknown_function


    PRIMARY_PROBLEM_CLASS: AV_msux64w10!unknown_function


    TARGET_TIME: 2019-11-20T03:20:21.000Z


    OSBUILD: 18362


    OSSERVICEPACK: 0


    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: unknown_date


    BUILDDATESTAMP_STR: 190318-1202


    BUILDLAB_STR: 19h1_release


    BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202


    ANALYSIS_SESSION_ELAPSED_TIME: a1a7


    ANALYSIS_SOURCE: KM


    FAILURE_ID_HASH_STRING: km:av_msux64w10!unknown_function


    FAILURE_ID_HASH: {a399b448-f36e-8b3e-3c58-f726a7cd4e58}


    Followup: MachineOwner

    ---------

    :)
     
    Erik Sundermann, Nov 19, 2019
    #1
  2. USER33331
    user33331 Win User

    Win10: windows update stuck at never ending loop ?

    When in win10:
    • Update&security -> Windows update -> Finding update... .... .... ....
    Planning to download the latest Win10.ISO (vers.1803) and manually update:
    - Then wait that my ordered new SSD arrives and clone the old HDD to it.
     
    user33331, Nov 19, 2019
    #2
  3. BTARUNR
    btarunr Win User
    Intel E5200 Gets Updated, R0 Stepping Coming Up

    Intel's Pentium Dual-Core E5200 processor is getting on course for a specifications update. The chip will feature in a new, improved Wolfdale-2M core, spec'd out as the R0 stepping, from its current M0 stepping. The new stepping is intended to add new instructions, power-management features, and bring about changes in the chip-package. A short list of known changes is as follows:
    • CPUID changed from 10677 to 1067A
    • Power State Indicator (PSI) support with Intel 4 series chipsets
    • New instructions - XSAVE and XRSTOR
    • New S-spec and MM numbers
    • New halide-free chip package
    Due to the changed CPUID, users may require BIOS updates to detect the CPU. According to the company, E5200 R0 should be out by April 13.

    Source: TechConnect Magazine
     
    btarunr, Nov 19, 2019
    #3
  4. DARKSABER
    Darksaber Win User

    Keep getting BSOD since last Win10 feature update

    XBox 360 dashboard gets 125 new features

    The next Xbox 360 update is coming along nicely. The download should take less than a minute and will be available to all Xbox 360 Live users. The feature list is quite long, so I suggest you click on the following link for the entire list:Xbox update.

    Source: DailyTech
     
    Darksaber, Nov 19, 2019
    #4
Thema:

Keep getting BSOD since last Win10 feature update

Loading...

  1. Keep getting BSOD since last Win10 feature update - Similar Threads - Keep getting BSOD

  2. Windows crashes BSOD since last Update

    in Windows 10 BSOD Crashes and Debugging
    Windows crashes BSOD since last Update: Hello,since the latest update, I can't boot my Surface Laptop Pro 2 to Windows anymore. During the boot process, I get a blue screen with the error code CRITICAL_PROCESS_DIED. The recovery tool can't help me either, because it can't find an account with administration...

  3. Office Features Not Working Since Last Window Update

    in Windows 10 BSOD Crashes and Debugging
    Office Features Not Working Since Last Window Update: I have Windows 10 running on a Dell Laptop. Windows Update KB5003537 automatically downloaded on 6/25. Since that time, I have not been able to open Word, Excel or Outlook. Running Office Home 2016.Have tried both shutting down and restart several times and that hasn't...

  4. PC not sleeping since last update, also getting the odd BSOD

    in Windows 10 Ask Insider
    PC not sleeping since last update, also getting the odd BSOD: Ever since updating, my pc refuses to sleep when left idle. Supposedly it may be an issue with a windows update process, but I've not been able to verify. I have also encountered 2 random blue screens. It's a very new build, but was running flawlessly, without either issue....

  5. BSODs since last update

    in Windows 10 BSOD Crashes and Debugging
    BSODs since last update: Split from this thread. Hi Windows 10 Support, I'm having very unstable machine since last update gone in 20H2, see below for more details: Hi Everyone, Would you please be able to assist, i'm having unpredictable BSOD errors in Windows 10 latest update 20H2, going...

  6. Random BSODs since update last week

    in Windows 10 BSOD Crashes and Debugging
    Random BSODs since update last week: Windows version 1903. Ever since a middle of the night update last week (10/5) the system has random bsods. Also cannot access the system information app, "windows management files may be moved or missing." although running sfc /scannow reports everything is fine. The...

  7. Latency problems since last couple Win10 updates

    in Windows 10 BSOD Crashes and Debugging
    Latency problems since last couple Win10 updates: In the last week it seems several updates have been pushed to my Win10 laptop and now I have significant latency issues affecting overall sluggishness and streaming audio (not locally stored media). The latency monitor identifies ndis.sys as the latency hog. dxgkrnl.sys seems...

  8. Bootcamp WiFi Intermittent since last update to Win10

    in Windows 10 Network and Sharing
    Bootcamp WiFi Intermittent since last update to Win10: Hello. I am not sure why the WiFi is now intermittent after the last Windows 10 update. I have reverted the driver for it, reinstalled it, turned off power management on it and it is still not working. Thanks for any ideas. Farzad [ATTACH] [ATTACH]...

  9. Autostart Features Ignored since last Features Update (1709)

    in Windows 10 Support
    Autostart Features Ignored since last Features Update (1709): Since I upgraded to Version 1709, I can disable Autostart Features via Task Manager but they are Ignored and the Program is started even though it is disabled. In Version 1703 I did not have that Bug. Program in Question: Send To OneNote Tool (OneNote 2013 installed) In...

  10. Since last update

    in Windows 10 Support
    Since last update: Since this little update on 2nd Dec Bing now has sound on home page and headline photo appear across the bottom. When you click on the photo it takes you to the subject to read. So well done Microsoft. Has anyone else found or seen it 32538