HP Laptop having random BSOD's

Hi all,

So I have this HP Elitebook 1040 G3 laptop that I got to take home from work, and it's been acting strange. Sometimes it can work fine for days, but then it can throw random memory related errors in Chrome like STATUS_ACCESS_VIOLATION or STATUS_STACK_BUFFER_OVERRUN and also give me BSOD's, also memory related like MEMORY_MANAGEMENT. Ive added the V2 Log collector files to this post. I also ran BlueScreenView which tells me that the cause is ntoskrnl.exe+428f20. Also tried checking the memory with Memtest86 and let it ran for a while, but it didn't return any errors. Tried reinstalling the OS (even tried Windows 11), updated drivers from both HP or latest ones from hardware manufacturers, nothing seems to make a difference. Does anyone have an idea as to what's wrong with this machine? Many thanks.

May these suggestions could help.
How to Fix "Aw, Snap! STATUS_ACCESS_VIOLATION" Error on Chrome & Edge

NTN said:

May these suggestions could help.
How to Fix "Aw, Snap! STATUS_ACCESS_VIOLATION" Error on Chrome & Edge

Thanks for the reply. But yeah the suggestions there aren't really usefull, and I think there's an underlying problem that causes this. The random errors in Chrome I can live with, but the bluescreens not so much....

MrBarma said:

Hi all,

So I have this HP Elitebook 1040 G3 laptop that I got to take home from work, and it's been acting strange. Sometimes it can work fine for days, but then it can throw random memory related errors in Chrome like STATUS_ACCESS_VIOLATION or STATUS_STACK_BUFFER_OVERRUN and also give me BSOD's, also memory related like MEMORY_MANAGEMENT. Ive added the V2 Log collector files to this post. I also ran BlueScreenView which tells me that the cause is ntoskrnl.exe+428f20. Also tried checking the memory with Memtest86 and let it ran for a while, but it didn't return any errors. Tried reinstalling the OS (even tried Windows 11), updated drivers from both HP or latest ones from hardware manufacturers, nothing seems to make a difference. Does anyone have an idea as to what's wrong with this machine? Many thanks.

There is only one dump file to analyze:

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffffcebffcbf3130
Arg3: 0000000000080000
Arg4: 0000000000000000

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2234

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 5068

Key : Analysis.Init.CPU.mSec
Value: 202

Key : Analysis.Init.Elapsed.mSec
Value: 3726

Key : Analysis.Memory.CommitPeak.Mb
Value: 79

Key : MemoryManagement.PFN
Value: 80


DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BUGCHECK_CODE: 1a

BUGCHECK_P1: 41792

BUGCHECK_P2: ffffcebffcbf3130

BUGCHECK_P3: 80000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: msedgewebview2

STACK_TEXT:
ffffd20a`a812ec38 fffff802`5ac6c287 : 00000000`0000001a 00000000`00041792 ffffcebf`fcbf3130 00000000`00080000 : nt!KeBugCheckEx
ffffd20a`a812ec40 fffff802`5ac5bc2d : 00000000`00000000 ffffd20a`a812f140 00000000`00000000 00000000`00000000 : nt!MiDeleteVa+0x1597
ffffd20a`a812ed40 fffff802`5ac5ba2d : ffffcebf`00000000 00000000`00000000 00000000`00000000 ffffbd88`f9c13740 : nt!MiWalkPageTablesRecursively+0xb2d
ffffd20a`a812edd0 fffff802`5ac5ba2d : ffffcee7`00000000 00000000`00000000 00000000`00000001 ffffbd88`f9c13740 : nt!MiWalkPageTablesRecursively+0x92d
ffffd20a`a812ee60 fffff802`5ac5ba2d : ffffcee7`00000000 00000000`00000000 00000000`00000002 ffffbd88`f9c13740 : nt!MiWalkPageTablesRecursively+0x92d
ffffd20a`a812eef0 fffff802`5ac7eaf1 : 00000000`00000000 00000000`00000000 ffffd20a`00000003 ffffbd88`f9c13740 : nt!MiWalkPageTablesRecursively+0x92d
ffffd20a`a812ef80 fffff802`5ac6aad7 : ffffd20a`a812f140 ffff9a80`00000001 ffff9a80`00000002 fffff802`00000000 : nt!MiWalkPageTables+0x371
ffffd20a`a812f080 fffff802`5aca5e62 : 00000000`00000000 fffff802`5aca602d ffffd20a`a812f448 ffffbd88`fa585040 : nt!MiDeletePagablePteRange+0x747
ffffd20a`a812f3b0 fffff802`5b0cc6c8 : 00000000`00000000 ffffd20a`00000001 ffffbd88`f9c130c0 ffffd20a`a812f480 : nt!MiDeleteVirtualAddresses+0x52
ffffd20a`a812f400 fffff802`5b0fd451 : ffffbd88`f9c130c0 ffffbd88`f96c82e0 00000000`00000000 00000000`00000000 : nt!MiDeleteVad+0x1a8
ffffd20a`a812f4c0 fffff802`5b0fcdeb : ffffbd88`f96c82e0 00000000`00000000 ffffbd88`fa585040 00000000`00000000 : nt!MiUnmapVad+0x49
ffffd20a`a812f4f0 fffff802`5b0fc965 : ffffbd88`f96d0080 ffffbd88`f96d0080 ffffbd88`f96d0080 ffffbd88`f9c130c0 : nt!MiCleanVad+0x2f
ffffd20a`a812f520 fffff802`5b146711 : ffffffff`00000000 ffffffff`ffffffff 00000000`00000001 ffffbd88`f9c130c0 : nt!MmCleanProcessAddressSpace+0x10d
ffffd20a`a812f5a0 fffff802`5b0a96e4 : ffffbd88`f9c130c0 ffffa883`8a04f630 ffffd20a`a812f7c9 00000000`00000000 : nt!PspRundownSingleProcess+0xc1
ffffd20a`a812f630 fffff802`5b1e7428 : 00000000`00000000 ffff3f4c`59bfdd01 ffffbd88`fa5850b4 00000002`87af2000 : nt!PspExitThread+0x63c
ffffd20a`a812f730 fffff802`5ac1b477 : ffffbd88`f81c01f8 fffff802`5aca07ea ffffbd88`00000000 00000000`000000c0 : nt!KiSchedulerApcTerminate+0x38
ffffd20a`a812f770 fffff802`5ae2f0c0 : 00000000`00000001 ffffd20a`a812f830 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x4a7
ffffd20a`a812f830 fffff802`5ae3dd8f : 00000000`00000000 00000000`00000054 ffffbd88`fa585040 00000002`8b3ff3f8 : nt!KiInitiateUserApc+0x70
ffffd20a`a812f970 00007ff9`d6d72a54 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
00000002`8b3ff498 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`d6d72a54


MODULE_NAME: hardware

IMAGE_NAME: memory_corruption

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: MachineOwner
---------

tomdsr said:

There is only one dump file to analyze:

This is the first BSOD after a fresh install of Windows. I've had another one since, is it usefull to upload a new log export?

- - - Updated - - -

NTN said:

STATUS_STACK_BUFFER_OVERRUN is one of the exit codes used for the feature. The fact your program aborted with this means your program's memory is somehow corrupted. It is a bug of either your program, a bug of a library used by your program, or a bug of tool (such as compiler or linker) used to build your program.

Windows Memory Diagnostic tool
Press Windows Key+R, type “mdsched.exe” into the Run dialog that appears, and press Enter.
How to Test Your Computer’s RAM for Problems

And for Memtest86+
MemTest86+ - Test RAM


You could also try to boot the PC after the tests to identify any faulty RAMstick by booting with only one RAMstick present in the slots.


ntoskrnl.exe is usually driver related......
But I guess you already have checked your drivers in Dev.Manager.


Let HP check your drivers.
https://support.hp.com/us-en/drivers

sfc /scannow in CMD(adm)

Let HP check your drivers.HP Elitebook 1040 G3
https://support.hp.com/us-en/drivers...ook-pc/8654820

You should check your BIOS if that is the latest one.
Latest BIOS
TITLE: HP Notebook System BIOS Update
VERSION: 01.33 REV: A PASS: 1
EFFECTIVE DATE: August 17, 2018
DESCRIPTION:

https://ftp.hp.com/pub/softpaq/sp900...0/sp90110.html

SOFTPAQ FILE NAME: SP90110.exe
https://ftp.hp.com/pub/softpaq/sp900...00/sp90110.exe

Yeah tested the ram with mdsched.exe and Memtest86, no obvious errors there. Drivers I updated through HP and there are no faults in the devicemanager. It also has the latest BIOS.

It could be helpful if you update your specs....at least with what version of Windows you got.
Search: Winver

NTN said:

It could be helpful if you update your specs....at least with what version of Windows you got.
Search: Winver

The laptop currently has Windows 11 (22H2), but it also happened with Windows 10. I know that Windows 11 is different forum, but I was planning on using Windows 10 on it. I can downgrade to 10 if that's necessary, but the BSOD's happened on every Windows version I tried, including version bumps/service packs....

Then: What OS build of Windows 11?

Search: winver

No answer..
Are you not able to use winver?

NTN said:

Then: What OS build of Windows 11?

Search: winver

No answer..
Are you not able to use winver?

22h2 (22621.1105)