Windows 10: Windows update failing - version 1709 Update - no real error message. Solved

Page 3 of 3 FirstFirst 123
  1.    23 Jan 2018 #21

    Ok, changes made to CCleaner, Crash Dump test run - results below.


    --------------------------------------------------------------------------------
    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dumps are enabled on your computer.

    Crash dump directories:
    C:\Windows
    C:\Windows\Minidump



    On Tue 23/01/2018 07:23:31 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\012318-3218-01.dmp
    This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
    Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x19B41837, 0x3C2A58ED)
    Error: MANUALLY_INITIATED_CRASH1
    file path: C:\Windows\system32\drivers\rspcrash64.sys
    product: WhoCrashed
    company: Resplendence Software Projects Sp.
    description: Resplendence WhoCrashed Crash Dump Test
    Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.



    On Tue 23/01/2018 07:23:31 your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP
    This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
    Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x19B41837, 0x3C2A58ED)
    Error: MANUALLY_INITIATED_CRASH1
    file path: C:\Windows\system32\drivers\rspcrash64.sys
    product: WhoCrashed
    company: Resplendence Software Projects Sp.
    description: Resplendence WhoCrashed Crash Dump Test
    Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.



    On Mon 22/01/2018 16:48:53 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\012218-12406-01.dmp
    This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
    Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x19B4007E, 0x3C2A58ED)
    Error: MANUALLY_INITIATED_CRASH1
    file path: C:\Windows\system32\drivers\rspcrash64.sys
    product: WhoCrashed
    company: Resplendence Software Projects Sp.
    description: Resplendence WhoCrashed Crash Dump Test
    Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.





    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------

    3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

    Here is the zip from the log collector run after the Crash Test Analyser.
    LASERBEAK (2018-01-23 07 26).zip
      My ComputerSystem Spec


  2. Posts : 20,001
    windows 10 professional version 1607 build 14393.969 64 bit
       23 Jan 2018 #22

    The crashes created dumps and the dump formed mini and memory dumps.
    The mini dump files were able to be debugged.
    So the computer environment is now ready for using windows driver verifier.
    If you run it now you will be on your own. After each BSOD run whocrashed > analyze > uninstall the misbehaving driver.
    Some drivers may not be able to be analyzed by whocrashed. Our tools perform a more thorough debugging. So after the dumps run the log collector and post zips into the thread for debugging.
    At this time I'm heading to bed and will check in with you later in the day.

    Make sure that you have created a brand new restore point.
    Sometimes the computer becomes sluggish when using windows driver verifier.
    Other times it may be unable to boot.
    If there is difficulty booting the number of custom active tests will need to be reduced.
    If there are no problems plan to use the tool for 48 hours.
    After the last BSOD plan to use the tool for an additional 36 hours of typical computer use.
      My ComputerSystem Spec

  3.    23 Jan 2018 #23

    Thanks Zbook, I was lucky, first driver failure seemed to be the culprit. All updated now with build 1709. Really appreciate all the help and guidance :)
      My ComputerSystem Spec


  4. Posts : 20,001
    windows 10 professional version 1607 build 14393.969 64 bit
       23 Jan 2018 #24

    That's great news.
    You are welcome.
    Which driver was it?
    Please post a new zip.
    log collector v2-beta08.zip
      My ComputerSystem Spec

  5.    25 Jan 2018 #25

    zbook said: View Post
    That's great news.
    You are welcome.
    Which driver was it?
    Please post a new zip.
    log collector v2-beta08.zip
    It was a driver for one of my flight controls, as I play flight simulators. Once that was removed all was ok and update went ok. I am off for work at the moment so unable to post another log. I will try to post one over the next few days.
      My ComputerSystem Spec


 
Page 3 of 3 FirstFirst 123

Related Threads
I had similar troubles when upgrading from windows 7 to windows 10 but managed to get through it by removing all usb peripherals except keyboard and mouse. I recently upgraded my motherboard, ram, cpu and graphics card. I was online with...
Solved Feature update windows 10 version 1709 in Windows Updates and Activation
It downloads then tries to install but said I need to fix issue first click on fix issue . When i click fix issue it starts over again and when done says can not update? Have done this numerous times and still wont download or install this update.
Feature update to Windows 10 version 1709 in Installation and Upgrade
I have Windows 10 version 1703 OS Build 15063.726 . The Feature update 1709 says it is downloading on my Laptop, but it hasn't moved from 0% for a full day (10 hours)...any advice would be welcome as I think it should have moved on by now.
so just like the creators update which ive previously not had any success installing. i gave up and went about my daily use of my computer. now the feature update 1703 is being forced upon me and have no way of holding it off.. it to is also...
I have Windows 10 Home 64-bit installed on a PC and have realised that it's been failing to install the anniversary update 1607 for a few months (I'm always seeing the 'Update and Shut Down' option but then getting a notification after start-up...
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 18:05.
Find Us