BSOD When NOT Gaming

zbook · Oct 28, 2023

Please post a new V2 share link.

gmahadhika · Oct 30, 2023

Here's the link: LAPTOP-I85OKVST-(2023-10-30_11-57-34).zip

zbook · Oct 30, 2023

The last BSOD was on 10/24/2023.

That's five days of computer stability.

gmahadhika · Oct 31, 2023

Well yeah, but I'll keep watch. Is there any other RAM test I should do other than memtest?

ubuysa · Oct 31, 2023

The gold test for RAM is to remove one stick and run on just one for a day or two, or until you get a BSOD. Then swap sticks and run on just the other one for a day or two, or until you get a BSOD. That will definitely reveal whether one stick is flaky.

zbook · Oct 31, 2023

Memtest86+: Both RAM modules tested for 11 passes > no errors = test PASS

5 days of computer monitoring with both RAM modules: no BSOD or unexpected shutdowns and restarts reported or seen in collected V2 log files

The above in most cases is sufficient software testing and computer monitoring to rule out malfunctioning RAM.

Code:

Location     : Bottom - Slot 1 (left)
BankLabel    : P0 CHANNEL A
Manufacturer : Micron Technology
MemoryType   : DDR4
FormFactor   : SODIMM
Capacity     : 8GB
Speed        : 3200
Serial       : 2B74CC43
PartNumber   : 4ATF1G64HZ-3G2E2  
ECC          : False
TypeDetail   : {Synchronous, Unbuffered (Unregistered)}

Location     : Bottom - Slot 2 (right)
BankLabel    : P0 CHANNEL B
Manufacturer : Micron Technology
MemoryType   : DDR4
FormFactor   : SODIMM
Capacity     : 8GB
Speed        : 3200
Serial       : 2B74CBA1
PartNumber   : 4ATF1G64HZ-3G2E2  
ECC          : False
TypeDetail   : {Synchronous, Unbuffered (Unregistered)}

gmahadhika · Oct 31, 2023

It happened again just now. Here's the new V2 link: LAPTOP-I85OKVST-(2023-11-01_09-43-20).zip

zbook · Nov 1, 2023

Please run:

https://www.tenforums.com/attachments/bsod-crashes-debugging/317051d1612150787-batch-files-use-bsod-debugging-getmemoryconfiguration.bat

Post images or share links into the newest post.

It may take one week or more between BSOD.
This makes testing longer / harder.

For how long did HP test the laptop?
What tests were performed?

If a Windows 10 clean install is performed can you be without computer files for one week?

Consider making free or pay backup images.

Then clean install Windows 10 without drivers or applications.

Monitor using Reliability Monitor:

View Reliability History in Windows 11 Tutorial

This tutorial will show you how to view reliability history for your Windows 11 device. The Reliability Monitor provides a system stability overview and details about events that impact reliability. It calculates the Stability Index shown in the System Stability Chart. Reliability Monitor...

www.elevenforum.com

Using one RAM module at a time in the same DIMM was already mentioned and can be performed simultaneously.

ubuysa · Nov 1, 2023

The latest dump (1st Nov) also points very strongly at a RAM problem. The bugcheck code is 0xA, IRQL_NOT_LESS_OR_EQUAL, and that simply means that a page fault occurred whilst running at an elevated IRQL (when page faults are not allowed). The reason for the page fault is because the referenced memory page was not allocated, was paged out, or the RAM was bad. Commonly this BSOD is caused by a third-party driver fouling up a memory pointer and trying to read memory that it hasn't allocated or doesn't own. In this case however, there are no third-party drivers on the call stack leading to the bugcheck. In addition, the bugcheck occurred during idle processing.

Here's the call stack (you read it from the bottom up)...

Code:

1: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffff9400`f023e8e8 fffff807`5ec2bfa9     nt!KeBugCheckEx
01 ffff9400`f023e8f0 fffff807`5ec27634     nt!KiBugCheckDispatch+0x69
02 ffff9400`f023ea30 fffff807`5ea3d0bc     nt!KiPageFault+0x474
03 ffff9400`f023ebc0 fffff807`5ec20509     nt!KiBeginThreadAccountingPeriod+0x16c
04 ffff9400`f023ec00 fffff807`5ec1b846     nt!SwapContext+0x629
05 ffff9400`f023ec40 00000000`00000000     nt!KiIdleLoop+0x176

You can see that the page fault occurred in a Windows function - nt!KiBeginThreadAccountingPeriod - and Windows code is error free, so this is not a bug in Windows. If we look at the details of that frame...

Code:

1: kd> .frame /r 3
03 ffff9400`f023ebc0 fffff807`5ec20509     nt!KiBeginThreadAccountingPeriod+0x16c
rax=0000000001000001 rbx=ffff800e11a9a080 rcx=0000000003001052
rdx=ffffa88113e62410 rsi=ffffa880fbe5a180 rdi=00000000000000a0
rip=fffff8075ea3d0bc rsp=ffff9400f023ebc0 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=ffff800e041ae6c4
r11=ffff9400f023eb68 r12=0000000001000000 r13=ffff800e12e55080
r14=00000000000000ae r15=ffffa880fbe69000
iopl=0         nv up di ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00040086
nt!KiBeginThreadAccountingPeriod+0x16c:
fffff807`5ea3d0bc 488b0cce        mov     rcx,qword ptr [rsi+rcx*8] ds:002b:ffffa881`13e62410=????????????????

BAD_STACK_POINTER:  ffff9400f023e8e8

Here you can see that the failing instruction was a MOV instruction using the RSI and RCX registers are pointers. Those two registers seem to have values stored in them (ie. they're not zeroed and thus possibly flaky) and yet the resulting memory location, which seems to be a reasonable address (it's in the kernel space), is invalid - note the ???????????????? - and that's what caused the page fault.

In addition, at the bottom there we have a flag for a bad stack pointer, this indicates that there has been a foul-up in incrementing (or decrementing) a stack pointer and that's not the fault of the Windows function of course. Thus we have a Windows function executing what looks likes a good instruction and yet the target memory location is invalid. In addition the stack pointer (which likely depends on the result of this instruction) is invalid. It's hard to imagine any other cause for this other than the RAM at that target memory location is bad.

My advice would be to remove one RAM stick and run on just one for a few days, or until you get a BSOD. Then swap sticks and run on just the other for a few days, or until you get a BSOD. That's the very best RAM test you can do.

zbook · Nov 1, 2023

How often is hyper-v /virtual machine in use?

Upgrade the BIOS:

Driver - OMEN Laptop - 15-en0013ax | HP® Customer Support

support.hp.com

Code:

Event[396]
  Log Name: System
  Source: Service Control Manager
  Date: 2023-10-02T23:40:40.5870000Z
  Event ID: 7023
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: LAPTOP-I85OKVST
  Description:
The vmms service terminated with the following error:
Ran out of memory

gmahadhika · Nov 1, 2023

@zbook

I've attached the screenshot of memory configuration. Unfortunately, I didn't know exactly what HP did to my laptop. At one time, they just said that they've replaced the motherboard. It did seem to lessen the BSOD somewhat, but not entirely. Sadly, I wouldn't be able to backup my files and reinstall Windows 10 as it require a lot of efforts and time and I just can't do it/risk it right now.

Hyper-v/virtual machine is practically never used. I did use it to run bluestacks a few years ago, but not anymore.

I'll be sure to update my BIOS from your link.

@ubuysa

Same reason as above, I just can't find the time nor afford the risk of doing that test. If from this discussion it is deemed to be critical neccesities, I would reconsider. But for now, I try to keep testing/fixing as simplest as possible. I apologize if I seem to be not commited, but I really have other priorities right now.

zbook · Nov 1, 2023

Are you comfortable or uncomfortable removing or inserting RAM modules?

This link is how to make and restore images instead of manually backing up files:

Backup and Restore with Macrium Reflect

How to Create and Restore a System Image Backup with Macrium Reflect

www.tenforums.com

gmahadhika · Nov 2, 2023

No, I am not comfortable with removing or inserting RAM modules as I have never done it. I'm sure I'm able to do that though once I learn how to.

I have updated the BIOS with the link you provided me.

However, BSOD happened again just now. It's Hyper-V error again. Here's the link to the new V2.

LAPTOP-I85OKVST-(2023-11-02_14-11-27).zip

drive.google.com

zbook · Nov 2, 2023

Run ACP:

fltmc filters
Dism /online /get-drivers /format:table > "%userprofile%\desktop\drivers.txt"

Post results for fltmc.

Post a share link for the text report.

Indicate if you can / cannot make backup images and run windows 10.
Then when troubleshooting Windows 10 has completed restore a Windows 11 image.

gmahadhika · Nov 2, 2023

I've attached both files below.

zbook · Nov 2, 2023

Make a new restore point.

Run ACP:

pnputil /delete-driver oem17.inf /uninstall /force

Post results.

Reboot.

ubuysa · Nov 2, 2023

The latest dump (the 0x20001) has all the hallmarks of a hardware failure, and RAM is always at the top of that list. In the call stack we can see a series of NMI (non-maskable interrupt) calls, these generally happen because of an unknown hardware issue that can't be corrected...

Code:

13: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffff8000`0f05eca8 fffff801`63d44cb1     nt!KeBugCheckEx
01 ffff8000`0f05ecb0 fffff801`63c690c4     nt!HvlSkCrashdumpCallbackRoutine+0x81
02 ffff8000`0f05ecf0 fffff801`63c24542     nt!KiProcessNMI+0x264834
03 ffff8000`0f05ed30 fffff801`63c242ae     nt!KxNmiInterrupt+0x82
04 ffff8000`0f05ee70 fffff801`60000003     nt!KiNmiInterrupt+0x26e
05 fffffc8a`6a33a4b8 00000000`00000000     0xfffff801`60000003

This is a long thread and this may have been asked already, but are you overclocking the CPU or RAM (or GPU)? If so (even just XMP on the RAM) please remove all overclocks (and any undervolts on the CPU) and run at stock voltages and frequencies to see whether these BSODs continue.

Have you checked the temperatures at all? HWMonitor (free) will display all temps, so please let us know what the maximum CPU/GPU temps are, both at idle and under maximum load.

If you're not comfortable removing the RAM then don't try.

gmahadhika · Nov 2, 2023

@zbook

I'll do that ASAP

@ubuysa

I've never OC'd anything in my life on any device. I seem to remember I've provided the temperatures earlier in this thread? Unless it's not there.

ubuysa · Nov 2, 2023

OK, but this feels like a hardware problem to me. I don't know whether you've tried starting Windows in Safe Mode? I don't have time to re-read the entire thread to see whether you've done this.

gmahadhika · Nov 2, 2023

Fair, it might be a hardware problem. Funny thing is, BSOD literally never happened when I'm running a heavy game program. Not once, in its 2,5 years life time. It is why I haven't bought a new laptop, because it performed well for the reason I bought it in the first place (gaming). It always happened when the laptop is idling/opening youtube on chrome/opening MS excel.

Do you mean I should at least try to run Windows in safe mode for like 8 hours or something?