Question Motherboard issue?

[itnorm]

Laptop is an HP 17-ce100. Keeps BSODing with Windows. Sometimes crashing Windows and sometimes restarting the laptop.
Fresh installs of Windows 10-22H2 and Win11 23H2 still BSODs. It does the BSODs in normal mode and in safe mode. No overclocking ever. Bios updated to the latest. With a Ubuntu 22.04 Normal installation (no 3rd-party sw) with a complete delete of the Nvme storage and it does NOT crash or restart the laptop (ran overnight w/o an issue). Ran PcCheck 8.08 UEFI (for some reason the laptop will not run CSM-type flash drive sw, nor will it recognize that there is a flash drive installed, prob. normal behavior) with the comprehensive script and all tests pass. Ran MemTest86+ for 5 complete loops and no failure. Also, tried putting in new Nvme storage and the laptop still BSODs. I have the laptop set to not restart on BSOD and there are two error types shown, WHEA_Uncorrectable_error and Critical service failed. No dump file is ever created (Event viewer just says that dump file creation can't occur, or something to that effect) . The crashing or restarting occurs within 10 minutes (sometimes less, sometimes more time) of Windows loading. The BSOD still occurs even if I disable the graphics driver and the Microsoft basic driver is installed. HP-installed offline diags passes all tests. The CMOS battery has been disconnected sufficiently long enough to reset the BIOS.

Is there any software which can do a more thorough test of the hardware? Or even target a hw subsystem which may be at fault here?
Is it Windows having a temporary (soon-to-be fixed issue most likely, hopefully) compatibility problem?
Did I miss anything?

(Hopefully this post is in the correct sub-forum and hopefully it will get sufficient visibility, please advise otherwise)

 

[Fix_that_Glitch]

Laptop is an HP 17-ce100. Keeps BSODing with Windows. Sometimes crashing Windows and sometimes restarting the laptop.
Fresh installs of Windows 10-22H2 and Win11 23H2 still BSODs. It does the BSODs in normal mode and in safe mode. No overclocking ever. Bios updated to the latest. With a Ubuntu 22.04 Normal installation (no 3rd-party sw) with a complete delete of the Nvme storage and it does NOT crash or restart the laptop (ran overnight w/o an issue). Ran PcCheck 8.08 UEFI (for some reason the laptop will not run CSM-type flash drive sw, nor will it recognize that there is a flash drive installed, prob. normal behavior) with the comprehensive script and all tests pass. Ran MemTest86+ for 5 complete loops and no failure. Also, tried putting in new Nvme storage and the laptop still BSODs. I have the laptop set to not restart on BSOD and there are two error types shown, WHEA_Uncorrectable_error and Critical service failed. No dump file is ever created (Event viewer just says that dump file creation can't occur, or something to that effect) . The crashing or restarting occurs within 10 minutes (sometimes less, sometimes more time) of Windows loading. The BSOD still occurs even if I disable the graphics driver and the Microsoft basic driver is installed. HP-installed offline diags passes all tests. The CMOS battery has been disconnected sufficiently long enough to reset the BIOS.

Is there any software which can do a more thorough test of the hardware? Or even target a hw subsystem which may be at fault here?
Is it Windows having a temporary (soon-to-be fixed issue most likely, hopefully) compatibility problem?
Did I miss anything?

(Hopefully this post is in the correct sub-forum and hopefully it will get sufficient visibility, please advise otherwise)

If it is crashing in safe mode I would say it is a hardware issue somewhere. Do you have anything plugged into the laptop?

 

[itnorm]

Nothing is plugged into the laptop.

So, there is no more thorough diag sw that is available that you know of? (Searching Google proved fruitless for mobo diag sw)

And Ubuntu runs just fine.

 

[punkncat]

When searching for information about HP models you often need the 'service code' to see specifics, but this is the i7 model of the laptop?

Are you monitoring temps in both OS?

When you have been inside the machine did you verify the cooler is working properly?

 

[itnorm]

The model is HP ENVY - 17t-ce100 CTO. It is the i7 model. The laptop is running less than 10 minutes before it BSODs. Windows Safe mode will most likely not be raising the temp to any level of concern. I will test both OSes for temp. And verify the cooler is working properly.

 

[itnorm]

EDIT 2:
BSODing more often now even with a vanilla Win10 install. About every 5 or 6 hours. Ran Pc-Check Windows and all tests ran fine.

EDIT:
I transferred alot of data yesterday into that laptop and in order to do it fast I connected the ethernet cable to it (was using wifi previously). Those are the only two changes I made yesterday to that laptop. So, after 2 days, the BSOD occurred. Oddly, it has happened at about the same time of day, 5:02am on Nov. 27 and 5:09am on Nov. 29. Need ideas as to why this would trigger a BSOD for this laptop. ESD, power possible? No issues with other computers at this time.

BSOD may be related to an obscure Windows 10 driver related to the CPU (on this laptop it is an i7 -10th gen):
(listed under System devices)
Intel XEON E3 - 1200/1500 v5/6th gen Intel Core Gaussian Mixture Model 1911 (this driver was suggested in an HP forum by an HP representative.)
when the drive is not installed, it is:
Other devices: Base System device
This driver is not installed with a default Win10 install. And it is not listed on HP's support site.
Without this driver, the computer does not BSOD or restart. (It all sounds improbable I know)

I had made an image of the machine from its original condition, which was Win11. It does not have this driver. The upgrade to Win11 happened several months ago. So it had that amount of time where it ran fine.

The laptop originally came with Win10 and HP's support drivers do not have Win11 versions.

Did not get the temps for WIn11. The Win10 temps were within normal range. The cooler is running fine.

So, in the end it could be hw or it could be a driver. (I'd like to go further, but the laptop owner wants their pc back)

Would like anyone to comment on all this to get more clarity.

 

[itnorm]

EDIT 3:
Created a custom script with Pc-Check Windows of all the CPU tests and all the Mobo tests. It BSOD'ed each time I ran the script (but then I restored the original image made from the machine when I first started working on it and ran the test and it did not BSOD, so who knows). The verbose logs show a possible CPU issue with changing from 1 core to the next in the Multi Core test according to the Eurosoft engineer (they put out Pc-Check Windows). This is as close as I can get to the source of the problem and the BSOD'ing.