Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • Bluescreens reported on HP machines with the latest Win10 1803 and 1809 cumulative updates

    Posted on October 11th, 2018 at 10:08 woody Comment on the AskWoody Lounge

    But it isn’t at all clear if the bluescreen is due to the cumulative update, the freshly pushed HP keyboard driver, or something else.

    My guess is that there’s a conflict between the “HP Development Company, L.P. – Keyboard -7/11/2018 12:00:00 AM – 11.0.3.1” driver, recently pushed by Windows, and with the Win10 1803 and 1809 cumulative updates. But it’s only a guess.

    Computerworld Poirot on Windows.

    If that helped, take a second to support AskWoody on Patreon

    Home Forums Bluescreens reported on HP machines with the latest Win10 1803 and 1809 cumulative updates

    This topic contains 17 replies, has 11 voices, and was last updated by  anonymous 6 days, 17 hours ago.

    • Author
      Posts
    • #223816 Reply

      woody
      Da Boss

      But it isn’t at all clear if the bluescreen is due to the cumulative update, the freshly pushed HP keyboard driver, or something else. My guess is tha
      [See the full post at: Bluescreens reported on HP machines with the latest Win10 1803 and 1809 cumulative updates]

      4 users thanked author for this post.
    • #223853 Reply

      East
      AskWoody Lounger

      Someone posted (in another forum) that 1809 starts with an odd microcode update that starts when you boot up.  they seem to confirm the original microcode of the cpu in bios but when in win10 1809 it changes to something else.

      It’s suggested that it’s baked into 1809 this time instead of it being an update to 1809.  Can anyone confirm this?  Because there has been conflicting info about 1809 use of microcoded updates for the cpu. Which might play a role in this BSOD.

       

       

      • #223871 Reply

        woody
        Da Boss

        If true, that would be quite bizarre…

    • #223857 Reply

      fred
      AskWoody Lounger

      But it isn’t at all clear if the bluescreen is due to the cumulative update, the freshly pushed HP keyboard driver, or something else. My guess is tha[See the full post at: Bluescreens reported on HP machines with the latest Win10 1803 and 1809 cumulative updates]

      All HP updates manualy applied, aswell the latest windows updates for W10home 1803 build.17134.345 ; holding of the 1809 , I hope
      so far so good(?)
      regards Fred

      1 user thanked author for this post.
    • #223881 Reply

      East
      AskWoody Lounger

      If true, that would be quite bizarre…

      There are also reports that an app called wintimertester.exe reports a different Hz valuefor 1809 from previous win10 updates.  It’s now reads 10Hz were as before it was 3.xxxxx Hz.

       

      • This reply was modified 1 week ago by  East.
    • #223906 Reply

      EP
      AskWoody Lounger

      this article from ZDNet came out yesterday:

      https://www.zdnet.com/article/microsoft-needs-to-refocus-on-windows-10-fundamentals-not-just-new-features/

      perhaps woody & Susan (Patch Lady) may want to check it out and see what they think

      1 user thanked author for this post.
      • #223910 Reply

        BobbyB
        AskWoody Lounger

        @ep yeah I caught that yesterday, good article. I would love them to make it so, but unfortunately we aren’t that lucky M$ seems in the throes of Marketing hype and features for fun mode. “The Spring Stability upgrade” doesent seem to have the same “Jingoistic” ring to it alas. So it seems we will be stuck with the same old half baked features coming our way in the interim alas.
        On a positive note the “Black look” and Timeline have proved to be interesting aesthetic additions, but long overdue tweaks IMHO, but the stability issues continue to be a problem as is the never ending stream of questionable updates. Ah well we live in hope I guess.

      • #223940 Reply

        woody
        Da Boss

        Ed, Mary Jo and Paul have all weighed in — all rightly so, IMHO.

        See Susan’s post from last night:

        Today two more tech journalists have joined myself, Woody and others in tilting at the windmill, better known as Microsoft.

        Susan and I have been fighting this fight for years. Susan’s open letter is legendary.

        1 user thanked author for this post.
        • #223991 Reply

          lurks about
          AskWoody Lounger

          Woody, I see many who cover MS for a living on various tech sites are saying openly the same thing: “MS fix your OS and make sure the patches work and stop the featuritis”. Also, “slow down the release cadence, hire a proper QA team as what is currently done is not working”. While I have not seen these posts crossover to the general media there is a general awareness in tech circles there is something seriously wrong with Windows. Sadly MS seems to be ignoring all the advice.  When you, Susan, Ed Bott, Paul Thurrott, and many others are essentially saying the same thing MS should listen.

          The constant drum beat of serious problems especially with W10 has to hurt user confidence. The quickest way to go out of business is to give customers a good reason to look elsewhere. And shattering user confidence will give users a good reason to look elsewhere.

          • #224169 Reply

            anonymous

            But also be aware of another openly discussed observation. This may in fact be the designed from the beginning goal of this entire drawn out exercise. Kill the OS and make it look like an accident. Reap the rewards along the way, because there is no insurance policy to collect.

    • #223916 Reply

      WildBill
      AskWoody Lounger

      C’est magnifique, Monsieur Hercule Magnificent, Woody! However, this is one mystery I’m not diving into. I’ll stay with my boring, well-read Windows 8.1… & I suspect Windows 7 fans will too, as long as they can.

      Windows 8.1, 64-bit, Group A... switching to Group B in November!
      Wild Bill Rides Again...

      1 user thanked author for this post.
    • #223942 Reply

      BobbyB
      AskWoody Lounger

      The Register has its usual acerbic take on the matter, with a “Fix” suggestion, although apparently its not always successful. https://www.theregister.co.uk/2018/10/11/microsoft_windows_10_october_update_fix_still_stumbling/

      • #223964 Reply

        woody
        Da Boss

        Yeah, they don’t really know either.

        I wonder if MS will ever explain it, or if we’ll just get a silent fix somehow.

    • #223947 Reply

      anonymous

      This is (another!) proof that MS’ update quality is below zero.

      I understand when you have a so vast hardware ecosystem that makes it hard to test everything they support (yet Debian does this correctly for quite some good time now).

      But when you forcibly push new drivers for specific hardware, just test them, at least if the system is able to just boot after install!

      Oh the sheer incompetence… My brain is spitting all the swearing I cannot write here.

    • #224039 Reply

      EP
      AskWoody Lounger

      and here are more recent articles from ZDNet:

      this one from Ed Bott:
      https://www.zdnet.com/article/opinion-two-windows-10-feature-updates-a-year-is-too-many/

      and from Larry Dignan:
      https://www.zdnet.com/article/heres-how-microsoft-can-fix-its-windows-10-update-issues/

      • This reply was modified 1 week ago by  EP.
    • #224050 Reply

      jescott418
      AskWoody Lounger

      Microcode happen early on and probably won’t give BSOD randomly as HP PC users are seeing. Probably a HP driver or value added HP software product that all of a sudden doesn’t work right. I tend to remove these PC maker value added software before they can cause more problems. Like always, sometimes the fixes just create more problems.

    • #224069 Reply

      JB
      AskWoody Lounger

      Have HP 630 Lap Top  which went into extreme slow mode. Removed 1803 Cumulative update KB4462919 And now OK.

       

    • #224128 Reply

      Microfix
      AskWoody MVP

      According to Wiki-WDF I assume that there would have been a new version of KMDF/ UMDF for 1809. All sorts of complaints on reddit with ugly time consuming consequences. It also seems to affect v1803 reading through the reddit link (huddle71)..make of it what you will.

      Woody has started a blog here: https://www.askwoody.com/2018/microsoft-confirms-bug-triggering-bluescreens-in-win10-hp-computers/

      | W8.1 Pro x64 | Linux x64 Hybrids | W7 Pro x64 O/L | XP Pro O/L
        No problem can be solved from the same level of consciousness that created IT - AE

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: Bluescreens reported on HP machines with the latest Win10 1803 and 1809 cumulative updates

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.

    Your information: