BSOD When NOT Gaming

zbook said:

Why not follow the steps in post #26 a) or b) ?

Click to expand...

Sorry I missed that. I'll redo the driver reinstallation.

zbook said:

How come the HP software was not installed?

Click to expand...

The HP PC Hardware Diagnostics Windows v2.3.2.0 is already installed.

Once the new driver is installed run the HP Windows hardware diagnostics component tests > take pictures > post images or share links into this thread

I tried both options a and b. Neither works. Option a fails to initialize a scan even though I've already installed the required framework. Option b scans my device successfully but shown "you are up to date" even though I've already uninstalled (and haven't reinstalled) the AMD graphic driver.

Reinstalling the driver from the executable right now. Will post HP Windows hardware diagnostics component tests when I am able to.

zbook said:

Once the new driver is installed run the HP Windows hardware diagnostics component tests > take pictures > post images or share links into this thread

Click to expand...

Do I need to run the full diagnostics UEFI? Or just the computer test (fast system test)?

EDIT: Fast test returned passed result for everything.

Does the HP Windows hardware diagnostics display these menu options:
system tests
component tests



Select one of the following tests to check the associated sub-system.
Click the Run button to start testing.
Some tests may not be available in HP PC Hardware Diagnostics Windows.
Additional tests including memory test are available in HP PC Hardware Diagnostics UEFI.


Audio
Multimedia
Storage
Audio Playback Test

Video
Power
Input Devices
Wired Networking
Webcam Test (1)
HP HD Webcam
Wireless Networking
Processor Short Drive Self-Test (1)
Storage 1: SanDisk SD6PP4M-256G-1006
Long Drive Self-Test (1) Disk Read Verify (1)

I've tested most of what you asked but admittedly not everything but most of them seems to be fine. It hasn't BSOD for like almost 2 weeks and it BSOD'd again just now.

The BSOD screen show up as Hypervisor Error. Unfortunately I forgot to take a picture of it.

EDIT: I've checked the Hypervisor from Turning Windows Feature On or Off, but the Hypervisor can't be enabled. When I enabled it and then closing the window, it will only get disabled again the next time I open said window.

Please post a new V2 share link into the newest post.

Also attach any new test results.

I've attached the files you asked.

What I'm seeing in that latest V2 log upload is a RAM issue. The 0x20001 dump failed due to a stack pointer error, that can be caused by bad drivers, but there are no third-party drivers on the call stack, in addition, it fails whilst running the idle loop. The 0xD1 dump contains an invalid call reference on the stack...
That 0x244 address is clearly garbage, the earlier addresses without symbols are garbage addresses too.

Both these dumps then are strongly indicative of a RAM problem. In addition, in your System log we see these error messages...
That could indicate a problem with the paging file drive or, more likely in this case, a problem with RAM.

The most reliable way to test your RAM is to remove one RAM stick and run on just the other for a day or two, or until you get a BSOD. Then swap RAM sticks and run on just the other. You'll soon see whether it BSODs on one and not the other. This is a much more reliable (although longer) test than running Memtest86.

Both RAM modules can be removed and one can be reseated for testing.

Then the second RAM module can be tested in the same DIMM.

In order to confirm malfunctioning RAM the computer should have BSOD with only one of the two modules.



Alternatively you can perform RAM testing using Memtest86+ for 8 or more passes.


It sometimes takes passes into the 20s to find malfunctioning RAM.

A substantial portion of the testing can be performed overnight while sleeping.

Just 1 error is a test fail and testing can be aborted.

So, a couple of questions before I test them:
1. Based on both of your findings, is it still needed for me to check all that or let's just conclude that it's definitely a faulty RAM problem? Which means, the only way to fix this is to replace the RAMs.
2. Is there any explanation on why those BSODs (allegedly from faulty RAMs) happens when specifically not running any game program? It mostly happens when using Chrome or using MS excels.

I can't confirm that it's RAM, dump analysis isn't often clear-cut. All I can tell you is that my experience strongly suggests that it's RAM. I wouldn't go out and buy RAM without testing the RAM you have.

Flaky RAM is often unpredictable, it's often not possible to fully explain why a RAM issue causes the effects it does.

The only truth is what you find when you test the RAM.

For RAM, it's commonly 0x50 bugcheck. Same with "BAD_POOL_HEADER".

Also, "MEMORY_MANAGEMENT" is highly suspected of being RAM as well, had this happen out-of-the-blue with G.Skill TridentZ Neo.

Overclocking CPU core(s) too much causes 0xA (IRQL_NOT_LESS_OR_EQUAL) or a WHEA error. Also 0XA with not enough Vcore, especially. Should happen in Linpack very fast, if CPU is returning wrong arithmetic. Same with access violations when browsing=Usually your CPU core OC is too high. (Or defective CPU)

For CPU core testing, Linpack with default values. In your case, it wouldn't be overclocking, of course, it would be to check for CPU defects or bad power delivery at high CPU loads.

gmahadhika said:

So, a couple of questions before I test them:
1. Based on both of your findings, is it still needed for me to check all that or let's just conclude that it's definitely a faulty RAM problem? Which means, the only way to fix this is to replace the RAMs.
2. Is there any explanation on why those BSODs (allegedly from faulty RAMs) happens when specifically not running any game program? It mostly happens when using Chrome or using MS excels.

Click to expand...

Most tests have false negatives and / or false positives.

The HP UEFI hardware diagnostics displayed pass.

Memtest86+ may display pass for 4, 6, or 8 passes and find errors after 20 passes.

There also could be undetected drive or drive connection, DIMM, or motherboard problems.

If new or tested hardware (RAM) were available then swap testing is often the best testing method.

Alright I'll run the tests later tonight.

Hello I apologize I haven't been able to test my system again. Today I encountered 2 BSOD. I didn't get the error the first time, but the second time it shows as IRQL_NOT_LESS_OR_EQUAL. In the what failed line it says ntoskrnl.exe. I read around and yes, one of the reason might be because of faulty RAM.

Please post a new V2 share link.

If you're unable to have downtime then consider the use of only one RAM module at a time until you've got time to run Memtest86+.

BSOD just happened again, this time it showed as page fault in nonpaged area. I've attached both V2 and the newest BSOD screenshot.

V2: LAPTOP-I85OKVST-(2023-10-24_14-20-51).zip

I really don't see why I should be expected to give up my own time to read a new dump from you when you're not prepared to give up your own time to test your RAM properly.

Attached is the memtest result. It successfully completed 11 passes without any errors.