Unexpected Kernel Mode Trap

Two or more runs of the HP UEFI hardware diagnostics may report all passes.

It has good accuracy except RAM and perhaps the motherboard.

For more thorough RAM testing run Memtest86+ as needed.

"'Memtest86+ is a stand-alone memory tester for x86 and x86-64 architecture computers.
It provides a more thorough memory check than that provided by BIOS memory tests."'

Memtest86+ | The Open-Source Memory Testing Tool


Once you've established that there is no RAM problem the HP Windows hardware diagnostics can be used.

https://ftp.hp.com/pub/softpaq/sp149...0/sp149728.exe

HP PC Hardware Diagnostics Windows v2.4.0.0

Thanks. Replaced the memory chip for a different one so will just assume the old one was faulty. And it has a different/good ssd in it now. Will keep running hardware diagnostics though and try it out to see if all stays stable now.

Hopefully it will then I’ll mark as resolved. Thank you for your excellent help.

- - - Updated - - -

Nope. It started crashing and blue screening again with broken up blue screen and black screen when trying to start up. So think it's the motherboard then.

- - - Updated - - -

I’m marking this as resolved now thank you and resigned to the laptop being on the parts pile. Thank you for the help.

If possible post a new V2 share link.

I'll try!

- - - Updated - - -

Nope. It still just has a black screen at switch on. I tried hard resetting it a couple of times. Last time, after a hard reset and waiting 20 minutes, it did come on, but then crashed and blue screened again - the blue screen wasn’t even that legible - all broken up.

I’ll try a few times and see if it comes on again but at the moment - switch on - black screen. Even booting a Linux stick doesn’t help because the screen is black.

Hence I thought it might be motherboard failing (the ssd and ram have already been replaced with known good ones).

- - - Updated - - -

Ok. After hard resetting a few times and waiting 20 mins or so it booted up. Copied the V2 file across quickly from a usb stick and started to run it. But the screen froze (as before), Nothing would unfreeze it. Windows key didn’t do anything either. Waited quite a long time then turned it off by pressing the on off button. Turned it on again - it started up a bit but blue screened almost straight away. This has been the pattern.

I’m not sure it will stay on long enough to run the v2. Back to not starting and black screen again now.

I’ll see if I can get it going again and boot into safe mode if possible.

- - - Updated - - -

Ok after an hour I managed to get it to start up again and boot into safe mode and run the V2. The first time I ran it, it seemed very short (first link). So I ran it again. Also quite short and had a big "Warning" part way through.

After being in safe mode it restarted to the desktop - so I did sfc/scannow and it was clear - didn't report any issues. I did "reset this PC". It completed that and was back on desktop but froze again shortly after.

It was a clean install of Windows 11 on a formatted M2 ssd. Before reset this PC.

HP14-1-(2024-01-28_17-50-23).zip - Google Drive

https://drive.google.com/file/d/15L0...ew?usp=sharing

Pleas run Tuneup plus > post a share link

https://www.tenforums.com/attachment...p_plus_log.bat

Batch files for use in BSOD debugging

Batch files for use in BSOD debugging


The BSOD bugcheck with it's parameters often requires WDV.

It does not appear that the computer will tolerate the recurrent reboots?

Enable and Disable Driver Verifier in Windows 10

What is WDV?

It does not appear that the computer will tolerate the recurrent reboots?

Maybe? It's more that everything freezes not long after being on the desktop. Meaning can't shut down properly so have to manually shut down. On restarting it (sometimes) then blue screens. Then won't start again for a long time with a black screen.

While I managed to get onto the desktop last time, I downloaded the latest bios and installed those - which was a bit risky in case it froze again part way through, but it completed ok and the bios are now .21

c Microsoft Windows 11 Home Version 23H2 (OS Build 22631.3007)

==================================================================

Started on 28/01/2024 at 19:09:12.68

[SFC /ScanNow]

Beginning system scan. This process will take some time.

Results:

Windows Resource Protection did not find any integrity violations.

==================================================================

Started on 28/01/2024 at 19:10:38.48

[DISM /online /cleanup-image /ScanHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.3007

No component store corruption detected.

The operation completed successfully.

==================================================================

Started on 28/01/2024 at 19:11:52.31

[DISM /online /cleanup-image /RestoreHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.3007

The restore operation completed successfully.

The operation completed successfully.

==================================================================

The second "SFC /ScanNow" was skipped, as the first output the following:

Windows Resource Protection did not find any integrity violations.

==================================================================

Started on 28/01/2024 at 19:13:02.18

[ChkDsk /Scan]

The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
325120 file records processed.
File verification completed.
Phase duration (File record verification): 2.58 seconds.
22430 large file records processed.
Phase duration (Orphan file record recovery): 9.75 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.05 milliseconds.

Stage 2: Examining file name linkage ...
107 reparse records processed.
399316 index entries processed.
Index verification completed.
Phase duration (Index verification): 2.67 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 132.49 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.51 milliseconds.
107 reparse records processed.
Phase duration (Reparse point and Object ID verification): 1.36 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 94.28 milliseconds.
37099 data files processed.
Phase duration (Data attribute verification): 0.05 milliseconds.
CHKDSK is verifying Usn Journal...
38758952 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 99.85 milliseconds.

Windows has scanned the file system and found no problems.

No further action is required.

499192831 KB total disk space.
24912936 KB in 102560 files.
75812 KB in 37100 indexes.
0 KB in bad sectors.
457263 KB in use by the system.
65536 KB occupied by the log file.
473746820 KB available on disk.

4096 bytes in each allocation unit.
124798207 total allocation units on disk.
118436705 allocation units available on disk.
Total duration: 5.59 seconds (5595 ms).

==================================================================

Started on 28/01/2024 at 19:13:18.54

AutoReboot

TRUE

==================================================================

[Set AutoReboot = False]

Updating property(s) of '\\ELAINEHP14\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
==================================================================

AutoReboot

FALSE

==================================================================

DebugInfoType

7

==================================================================

[Set DebugInfoType = 7]

Updating property(s) of '\\ELAINEHP14\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
==================================================================

DebugInfoType

7

==================================================================

[WMIC PageFile list]

AllocatedBaseSize=1920
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20240126024526.614065+000
Name=C:\pagefile.sys
PeakUsage=0
Status=
TempPageFile=FALSE

==================================================================

AutomaticManagedPagefile

TRUE

==================================================================

[Set AutomaticManagedPagefile = True]

Updating property(s) of '\\ELAINEHP14\ROOT\CIMV2:Win32_ComputerSystem.Name="ELAINEHP14"'
Property(s) update successful.
==================================================================

AutomaticManagedPagefile

TRUE

==================================================================

[BcdEdit /enum {badmemory}]

RAM Defects
-----------
identifier {badmemory}

==================================================================

Finished on 28/01/2024 at 19:13:21.04
It took 4 minutes and 8 seconds to complete the operations.

- - - Updated - - -

Does that say bad memory at the end? So I have two sticks of bad ram? Screen hasn't frozen for a while ..........Five minutes later it crashed and black screen.

Tuneup plus results were good.

Windows Driver Verifier (WDV) may be useful in testing all non-Microsoft drivers.
The tool will cause recurrent BSOD until it is turned off.

To turn off the tool > boot into safe mode > op administrative command prompt > type or copy and paste one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail

As there is just Windows 11 and nothing else on, and all the drivers (but one) came with Windows - would it really be a driver? The one I installed was the intel graphics driver - it was worse without it! The identical laptop has all the same drivers as well. I'm kind of thinking I maybe do have two bad ram chips. The one I put in this machine was the one I took out of the other machine. They are both the same age. If that's the case it was rubbish ram if they both failed after 3.5 years. I could try putting the new 16gb ram I got for the other machine into this one. Unless it could get damaged somehow?

Somehow there were some non-Microsoft drivers installed.

chipset
network
GPU
keyboard
etc.

If drivers do not misbehave during the stress testing then it will support a hardware problem.

Ok. Thanks. That makes sense.

- - - Updated - - -

I think Windows does install some Intel and Realtek drivers .