Bought new computer last year, constant BSOD issues even after sending laptop back to HP for service

[fimum1]

As title says I have been having constant BSOD issues. Plenty of error codes: 

• Kmode exception not handled
  • with sub code intelppm.sys
• Lots of system service exceptions
  • fltmgr.sys, win32kbase.sys
• System Thread Exception
• Kernel Security Check Failure
• Driver Overran Stack Buffer
• Exception on Invalid Stack
• WHEA incorrectable error
• Hypervisor error

I have gone through the loop with HP customer support. They have had me re-install windows, they had me buy a flash drive to re-install windows, and most recently had me send my laptop in to be repaired. When I got my laptop back from the repair they told me the only things done were a re-install of windows and "extensive testing". Within minutes of my laptop being turned back on the issues started once again and havent stopped since. Certain things seem to make the error codes happen more often but it still happens at random from my point of view as someone who doesn't know much about what causes the errors. Every time I turn the computer on I make sure that all updates are installed, even the optional ones. 

Losing patience with the whole process and don't necessarily want to go through all the loops again just for them to tell me the same stuff. Plus my warranty is over. If anyone has any input or ideas on what might be able to help fix these problems it would be much appreciated. 

Another note, when HP sent me back the case with my laptop they did not include my flash drive that I spent $40 dollars on earlier in the process. Just annoying. The HP customer support personnel have told me that it is in fact not a hardware issue that I am dealing with and that it is just a problem with Windows. After having been through all this and re-installed windows multiple times with no changes I find it hard to believe that the only issue is Windows and not something else.

Once again, thank you for any insight

[NonSequitur777]

@fimum1,

Welcome to our HP User Forum!

Your issue(s) can be due to outdated or incompatible system drivers, bad disk sectors, corrupted image files, even a bad processor, primary boot drive or RAM.

So, let's start by trying the following troubleshooting steps first:

Type in file and left-click on the File Explorer App. Then locate your primary boot drive -most likely your C: drive, then right-click on your drive and select: Properties, then: Tools, then click on the Error checking Check button, and click on: Repair drive. You may see the message: "Windows can't repair the drive while it's in use". I would select the "Restart and repair now" option. Once completed, return here, and let me know what feedback, if anything, your PC shares with you.

Next step:

Type: cmd in your Windows search bar, then right-click on the Command Prompt App, then left-click on: Run as administrator, and then Yes.

type in or copy/paste: sfc /scannow and enter. This will take some time.

If all went well, you can anticipate this message: "Windows Resource Protection did not find any integrity violations." But it may not. If it shows any other message, please let me know.

Regardless, the next step:

Copy/paste and enter this command:

DISM.exe /Online /Cleanup-Image /Restorehealth

This will also take some time to complete.

If all went well, you can anticipate this message: "The restore operation completed successfully. The operation completed successfully." Then again, it may not. If it shows any other message(s), please let me know.

Regardless, next step:

Type or copy/paste and enter: chkdsk /f /r /x

It will ask: "Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)". You enter: n and then you want to restart your PC to allow this command to run. Do not touch your mouse or type on your keyboard, as your PC will do a countdown prior to executing the chkdsk command. Do not interrupt chkdsk and wait patiently for the process to end.

What chkdsk /f /r /x does is to scan the integrity of your file system and file system metadata and will automatically try to fix any logical file system errors that it finds. Please let me know what your PC says once it completed this step.

Next step:

Type in: windows memory diagnostic and right-click on the Windows Memory Diagnostic App, then: "Run as administrator", and click on the: "Restart now and check for problems".

Your PC will restart. Then the WMDT will run ("Windows is checking for memory problems").  This will -you guessed it, a (great) while to complete. Please wait until testing is complete. So, take a break, and check in half an hour, even though your PC will say, quote: "This might take several minutes." Trust me, it will take a lot more than several minutes.

Repeat this step:

Type: cmd in your Windows search bar, then right-click on the Command Prompt App, then left-click on: Run as administrator, and then Yes.

type in or copy/paste: sfc /scannow and enter. This will take some time.

If all went well, you should see this message: "Windows Resource Protection did not find any integrity violations." But it may not. If it shows any other message, please let me know.

Let me know if your BSOD issue is resolved or not.

Kind Regards,

NonSequitur777

[fimum1]

@NonSequitur777

Thank you for the reply and the helpful instructions. Went through and performed all of these checks and everything came back normal. All the messages you expected would come back, came back. Unfortunately, I am still seeing BSOD errors coming back from time to time with normal usage of the device. Still happens at random intervals and the message that shows up with the blue screen is different most of the times. Haven't seen anything outside of the normal messages that have been coming back since I got the laptop out of the box a year ago.

I appreciate your help, if you have any other suggestions for what I might look to do please let me know!

[NonSequitur777]

@fimum1,

Yea, the challenge for me -and all Forum members alike I imagine, is that the dreaded BSOD can be caused by any or combination of faulty memory (RAM), hard disk drive (HDD/SSD), motherboard, processor, or -mostly for desktops, your power supply unit (PSU).

At this point in time, in order to properly DIY troubleshoot your issue, you need certain resources/spare parts you may not have.

What I mean is this: I would start by swapping the processor with a different one (I happen to have a large collection of all manner of CPUs since I am a 'dedicated' PC hoarder/hobbyist, and I purchase one or two sporadically if it is offered for a steal), to see if this will improve the situation.  If not, I would keep the replacement CPU in place, and try each RAM stick one by one to see if perchance one of the RAM sticks -or RAM slots, is causing the issue.

If that doesn't work, I would clone my primary (boot) drive to a different drive and see if this fixes the issue.

However, if all of the above doesn't work -and mind you, this is based on my personal, anecdotal experiences with laptops, I would wonder/suspect if my motherboard is causing these issues.  Depending on if I can purchase an affordable motherboard via eBay, I may decide to try that out.  -I would purchase a motherboard from a Seller who will allow returns, in case the BSOD issue persist, I could return it to get my money back -though since we swapped just about anything that would logically cause BSODs, it would be surprising if BSODs would still occur after a mobo swap.

My recommendation: if you know someone who has computer experience (perhaps the business you work for has a computer guru employed) and is willing to take a look at your laptop, try that.  What I do know is that many people at this point don't want to bother about the extra hassle and/or expense and look for a replacement PC.

Kind Regards,

NonSequitur777