Share via

Issues with HP ProBook 6475b

Anonymous
2018-09-10T17:04:38+00:00

Before going into any specifics on the situation, here are the laptop's specifications:

  • Model :: HP ProBook 6475b
  • CPU :: AMD A10-5750M
  • GPU :: AMD Radeon HD 8650G
  • RAM :: 8GB (2x4GB) PC3-12800 DDR3-1600MHz SODIMM
  • HDD :: 2TB, 5400RPM, SATA III (ST2000LM007-1R8174)
  • OS :: Windows 10 Pro v.1803 build 17134.254

The laptop was working relatively well after the Windows 10 1709 Update, but then began to experience issues, because it had been accidentally registered with the Insiders Program - signified by the GSOD's I used to get at the time. So, I had Windows 10 reset itself - wipe everything but the OS (but not before backing up my app installers and data first). After that, I slowly moved all of my applications back onto the laptop. From my entire time using this laptop (up until the latest OS and driver upadtes), I haven't experienced like this until now. I've been getting frequent BSOD's, with most of them occurring while I'm away from the machine. It's gotten bad enough where I went on and changed settings so I could get full memory dumps from the laptop (along with minidumps). I can upload the smaller ones, but the larger ones are going to have to wait. If anyone can help, it would be greatly appreciated, since I have yet to be able to successfully read the dumps myself without resorting to this:

Due to the possibility of this being caused by drivers, I may try out this suggestion whenever I get the time:

I am a college student, so I might not always have free time for troubleshooting. This computer is my main laptop, which is why I am so concerned. It worked perfectly fine until after the OS/driver updates that followed the Windows reset (180X and later). I don't want to point my finger at a specific cause yet, because I am unsure of what may be causing it. I did install two new Windows Store apps recently, but I doubt that they are that dangerous (Ditto, QuickLook). Besides that, I haven't installed any new applications on this machine - for months. 

If anyone wants to help, please do - but there a few things that I am not willing to try at this point in time:

  • full or partial Windows Reset (since I just did that only a short while ago, and this still happened)
  • buying a new laptop (cash is tight right now, and I've already quit my summer job)
  • CPU downgrade (has been in use for over half a year now - issues are way too recent to have been caused by it)

Anything else is fair game. And, before anyone makes this mistake again, yes, this laptop has a proper CPU socket. It can be swapped for another CPU. I've already had one person make the assumption that such is not the case, and it's annoying. Furthermore, this model is compatible with Windows 10 - there are updated drivers and support pages for it here. Please do research before just saying something. I need assistance - not to be bludgeoned by misinformed statements and repeated suggestions. Please look at the comments above you before replying, to make sure you aren't unknowingly repeating someone else. With that said, any assistance will be greatly appreciated.

Here are links to the mini-dumps I mentioned before:

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-09-10T17:20:51+00:00

    Hi, TopHatProductions115

    Check these links, I hope it helps.

    https://answers.microsoft.com/en-us/windows/for...

    https://www.windowscentral.com/how-troubleshoot...

    https://www.thewindowsclub.com/blue-screen-deat...

    I would recommend you to check your SSD or Hard Disk HDD with chkdsk.

    https://www.tekrevue.com/tip/fix-hard-drives-ch...

    And check your Ram Memory with MemTest86.

    https://www.windowscentral.com/how-check-your-p...

    https://www.memtest86.com/

    Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-09-13T01:00:21+00:00

    When I went to run sfc /scannow, CMD stated "There Is System Repair Pending Which Requires Reboot To Complete". I went on and looked into it a bit:

    is the file that holds data pertaining to pending repairs, so I checked it for myself - it looked like a long list. So, I decided to see if Windows would do the auto-repairs (as stated) - I rebooted. But, Windows Updates were pending as well. 

    So I'm hoping that Windows was smart enough to run the repairs before the update. I will run sfc /scannow again, to check and see if the repair (queue/xml record) was either simply emptied or actually acted on.

    EDIT :: The command finished, with the following result:

    "Windows Resource Protection found corrupt files but was unable to fix some of them."

    If I get the time, I will try booting into Safe Mode and running the command(s) again. I haven't had a BSOD occur so far since running these commands, so hopefully, they helped in some capacity (unless placebo effect - in which case, BSOD chain combo in bound). I will be back...

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-09-12T23:58:50+00:00

    I apologise for the delay. College made it difficult to respond in a timely manner. Here is my current progress:

    • I did the MemTest procedure.
    • I just finished doing the chkdsk procedure (right before a major update - lol).
    • I am running sfc /scannow and DISM commands now

    Both MemTest and CHKDSK found no errors/no issues. The first link had sfc /scannow/DISM, so I'll go for it - nothing to lose there.

    The second link spent a lot of time focusing on BSOD's that may occur in situations that mostly did not apply to what I'm experiencing:

    • during Windows Update/Upgrade
    • during initial boot (with Desktop access)
    • during initial boot (with no Desktop access)
    • due to out-of-date drivers (already checked for drivers on manufacturer's website)
    • due to peripherals (the BSOD's occur without any devices connected as well)

    The only parts that may have applied were pertaining to BSOD's that are:

    • due to a recent driver installation
    • due to a recent application install
    • due to a recent Windows 10 Update

    But, in all three of these cases, I will have to spend time checking to see which background applications (since the BSOD has occured with nothing in foreground - minutes after login) and/or device drivers may be the culprit(s).

    The third link was a repeat of information covered in the second link, and was more limited in scope. Nonetheless, I will keep this info in mind for if the situation worsens.

    In addition to this, sfc /scannow should remove the possibility of system files being corrupted if it either comes back clean or fixes any files that require attention (upon reboot).

    I will return with more results.

    On a side note, did you see my error dumps?

    Was this answer helpful?

    0 comments