Regular BSOD after minutes to hours

Looking at the WER data from msinfo32.nfo, you've had five 154 BSODs and 10 ef BSODs. Only one dump in the zip and it was for a ef BSOD.

Bug Check 0x154: UNEXPECTED_STORE_EXCEPTION
Bug Check 0xEF: CRITICAL_PROCESS_DIED

Several other systems experiencing ef BSODs that I've looked at ended up having defective RAM, so it would be a good idea to take the time to test yours;

===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

   Warning

MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

   Note

MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

Looking at system-events.txt in Event Logs, there are lots of these:

Code:

Event[686]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2019-01-15T21:05:03.229
  Event ID: 17
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Bruces-HP-Spectre
  Description: 
A corrected hardware error has occurred.

Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)

Bus:Device:Function: 0x0:0x1C:0x1
Vendor ID:Device ID: 0x8086:0x9D11
Class Code: 0x30400

The details view of this entry contains further information.

You have a Realtek PCIE Card Reader according to driver-table.txt. It's possible the device is dwefective but it could also be a driver issue. You have version 10.0.10240.21283 installed. The HP website has version 10.0.10125.212 available, which is older.
I suggest first seeing if you can roll back the driver using Device Manager. If not then download the 10.0.10125.212 version from HP and install it, see if that helps.

If you get any more BSODs, run the Beta log collector if you can, otherwise run the DM log collector. Jus make sure we get the dump or dumps.

Latest dump shows two problems:

Code:

ffffe88e`37b89960  fffff803`35fec010*** ERROR: Module load completed but symbols could not be loaded for AgileVpn.sys
 AgileVpn+0x1c010

Driver Description: RAS Agile Vpn Miniport Call Manager
Driver Update Site: Windows Update
This is a Windows file so unlikely to be the source of a problem.

Code:

ffffe88e`37b89550  fffff80b`42a75450Unable to load image \SystemRoot\system32\DRIVERS\bddci.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bddci.sys
*** ERROR: Module load completed but symbols could not be loaded for bddci.sys
 bddci+0x15450

This belongs to BitDefender AV

I suggest uninstalling BitDefeder and running with Windows Defender for awhile and see if that resolves the problem.

Event log has this for the 26th:

Code:

Event[20328]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2019-02-26T15:44:50.003
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Bruces-HP-Spectre
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000154 (0xffffd8090284e000, 0xffffe88e37b89390, 0x0000000000000002, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 4e1fec39-8f82-4343-af9d-6ba58f1d9e7b.

Please zip C:\WINDOWS\MEMORY.DMP and upload to a file sharing site like Onedrive then post a link here so I can download it to look at it. It will be pretty big so will take a while to upload. May not provide any additional info but then again it might.