BSOD happening shortly after Start-up.

Page 1 of 2 12 LastLast

  1. Posts : 12
    Win10 Pro x64 Version 1909
       #1

    BSOD happening shortly after Start-up.


    I've been getting a BSOD occasionally. It appears to have something to do with "Microsoft-Windows-DistributedCOM", but I'm not sure.

    Can you please help?

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

    The zip file I uploaded is empty. I'll run Log Downloader again.
      My Computer


  2. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #2

    Hello

    Unfortunately the zip file is empty. Please try and run the beta log collector instead which is provided at the end of the BSOD Posting instructions.
      My Computers


  3. Posts : 12
    Win10 Pro x64 Version 1909
    Thread Starter
       #3

    I think I got log file right this time.
      My Computer


  4. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #4

    MuggleBornNY said:
    I think I got log file right this time.
    Yes you did, but we get more information from the beta version as I said in my earlier post. Please post this one up as well.
      My Computers


  5. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #5

    In the meantime I have had a look at the crash dump file and the analysis suggests that you may have a problem due to the Intel Wifi Driver and Realtek Network driver.

    Code:
    BugCheck C2, {4, ffffc286, 13e7eb40, ffffc285fd554bf8}
    
    *** WARNING: Unable to verify timestamp for rt640x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
    
    0: kd> .load pde;!dpx
    =========================================================================================
     PDE v11.3 - Copyright 2017 Andrew Richards
    =========================================================================================
    Start memory scan  : 0xfffff803fdb4f208 ($csp)
    End memory scan    : 0xfffff803fdb50000 (Kernel Stack Base)
    
    Unable to load image Netwtw04.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Netwtw04.sys
    *** ERROR: Module load completed but symbols could not be loaded for Netwtw04.sys
    0xfffff803fdb4f298 : 0xfffff80e3802cc0a : NETIO!MdpFree+0x6a
    0xfffff803fdb4f2a0 : 0x44415f594c504552 :  !da "REPLY_ADD_STA"
    0xfffff803fdb4f318 : 0xfffff80e396e62bb : fwpkclnt!FwppInjectComplete+0x5b
    0xfffff803fdb4f358 : 0xfffff80e3802c86e : NETIO!NetioDereferenceNetBufferListChain+0x28e
    0xfffff803fdb4f3d8 : 0xfffff80e39487428 : tcpip!FlSendNetBufferListChainComplete+0x58
    0xfffff803fdb4f408 : 0xfffff80e37ed1da0 : ndis!ndisMSendCompleteNetBufferListsInternal+0x120
    0xfffff803fdb4f438 : 0xfffff80e39ef10a8 : pacer!PcFilterSendNetBufferListsComplete+0x28
    0xfffff803fdb4f4b0 : 0xfffff80e37ed1c80 : ndis!ndisMSendCompleteNetBufferListsInternal
    0xfffff803fdb4f4d8 : 0xfffff80e37ed1b8e : ndis!NdisMSendNetBufferListsComplete+0x20e
    *** WARNING: Unable to verify timestamp for rt640x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
    0xfffff803fdb4f6a8 : 0xfffff80e37ed3f05 : ndis!ndisInterruptDpc+0x185
    0xfffff803fdb4f768 : 0xfffff803faee67c8 : nt!KiDeferredReadyThread+0x398
    0xfffff803fdb4f7c8 : 0xfffff803fafc4fdd : nt!KiGetNextTimerExpirationDueTime+0xfd
    0xfffff803fdb4f7d8 : 0xfffff803fdb4fa20 : 0xfffff80e37ed3d80 : ndis!ndisInterruptDpc
    0xfffff803fdb4f808 : 0xfffff803faf85327 : nt!KiExecuteAllDpcs+0x2e7
    0xfffff803fdb4f860 : 0xfffff80e37ed3d80 : ndis!ndisInterruptDpc
    0xfffff803fdb4f880 : 0xfffff803fb312400 : nt!KiInitialThread
    0xfffff803fdb4f920 : 0xfffff803fb312400 : nt!KiInitialThread
    0xfffff803fdb4f930 : 0xfffff803fb312400 : nt!KiInitialThread
    0xfffff803fdb4f948 : 0xfffff803faf8497b : nt!KiRetireDpcList+0x1db
    0xfffff803fdb4f998 : 0xfffff803fae1f4e6 : hal!HalPerformEndOfInterrupt+0x16
    0xfffff803fdb4f9a8 : 0xfffff803fb312400 : nt!KiInitialThread
    0xfffff803fdb4f9c8 : 0xfffff803fb052de5 : nt!KiInterruptDispatch+0x85
    0xfffff803fdb4fa20 : 0xfffff80e37ed3d80 : ndis!ndisInterruptDpc
    0xfffff803fdb4fb18 : 0xfffff803fb058565 : nt!SwapContext+0x165
    0xfffff803fdb4fb58 : 0xfffff803fb054bca : nt!KiIdleLoop+0x5a
    0xfffff803fdb4fb78 : 0xfffff803fb312400 : nt!KiInitialThread
    

    Of the two drivers the Realtek one is the oldest so this is the one I would update first and test to see if it makes a difference.
    rt640x64.sys Thu Jul 14 02:04:28 2016
    Netwtw04.sys Wed May 30 01:25:56 2018

    You can find the Realtek Ethernet driver here:

    https://support.hp.com/us-en/drivers...model/11715765


    You should also note that there have been several BIOS updates provided for your system that I would also recommend updating in due course.
      My Computers


  6. Posts : 12
    Win10 Pro x64 Version 1909
    Thread Starter
       #6

    Thank you. I 'll check to see if there are any updates.

    I did try to run the log collector, but Bitdefender says a bunch of the files are infected. This is the latest one.
      My Computer


  7. Posts : 659
    10 preview 64bit
       #7

    Hi

    as its quarantined the dump log, that would suggest an infected driver.
    Do you use any 3rd party driver updaters???

    Roy
      My Computer


  8. Posts : 14,903
    Windows 10 Pro
       #8

    hawkman said:
    Hi

    as its quarantined the dump log, that would suggest an infected driver.
    Do you use any 3rd party driver updaters???

    Roy
    More likely because the tool is not signed or something like that, I use Bitdefender as well, have no virus or update software and also have issues running the tool.
      My Computers


  9. Posts : 12
    Win10 Pro x64 Version 1909
    Thread Starter
       #9

    I don't use 3rd-party software for driver updates. I get updates directly from HP or Intel.

    I updated the Realtek driver.

    Still looking into "Netwtw04.sys". I ran Intel's Driver & Support Assistant and it says that file is up-to-date. I'll look into it further over the weekend.

    I'm hoping the old Realtek driver caused the problem. I'll see how things go over the next few days.

    Thank you so much for your help. I'll get back to you on Monday.
      My Computer


  10. Posts : 12
    Win10 Pro x64 Version 1909
    Thread Starter
       #10

    BSOD problem may be solved


    Over the weekend, I found that CrashPlan may have caused many of the Microsoft-Windows-DistributedCOM errors on the Event Log. I checked with their support group. They suggested a solution that involved editing the registry. I'm not comfortable with doing that, so I uninstalled CrashPlan and replaced it with Backblaze on Saturday.
    Since then, I've had no BSODs. It's too soon for me to say the problem is solved, but if I get through the week without crashing, I'll mark this thread as solved.
      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 14:52.
Find Us




Windows 10 Forums