BSOD When NOT Gaming

I have a medium-end gaming laptop (OMEN 15 2020) but ever since I bought it, it often BSOD when specifically not gaming. For example, it would sometimes BSOD when browsing, using excel, or just staying on the desktop. I've asked HP for repair numerous times when it was still on warranty. Alas, nothing is solved.

It has NEVER BSOD when gaming, however resource intensive it is.

The BSOD would happen at least once a day. At the usage range of 8-10 hours.

I don't know why I can't take a screenshot when in Event Viewer. But the latest error that ends in BSOD is error ID 162 (volmgr).

Please help, this problem has been bugging me for more than 2 years.

Here's the link of V2 log:

1) Please run: Tuneup plus




2) Run using administrative command prompt (ACP):

PowerShell $D=(New-Object -ComObject Wscript.Shell).SpecialFolders(4);Compress-Archive "%WinDir%\MEMORY.DMP" "$D\Memory_dmp"

Post separate share links into this thread using one drive, drop box or google drive.


3) After posting the above share links increase the free space on C: so that there is > 30 GB free space

Thank you for your response, I've done all the stuff you asked me to. In fact, as I typed this, my laptop froze. No BSOD pop up, just froze and require hard restart.

TuneUp Log: Tuneup.log
Memory Dump: Memory_dmp.zip

1) Reconnect the E: drive


2) Run HD Tune (free or trial version) (test all drives):
Post images or share links for results on these tabs:
a) Health
b) Benchmark
c) Full error scan


3) Open ACP and copy and paste: chkdsk /b /v E:


C:\WINDOWS\system32>chkdsk /b /v E:
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y

Reboot as needed



4) Uninstall the AMD GPU drivers using DDU

Reinstall using the HP website





5) For any new BSOD post a new V2 share link



------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 19.1 GB
Total Space: 487.4 GB
File System: NTFS
Model: WDC PC SN730 SDBPNTY-512G-1006

Drive: D:
Free Space: 813.4 GB
Total Space: 976.7 GB
File System: NTFS
Model: TEAM TM8FPD001T



Event[15384]
Log Name: System
Source: Ntfs
Date: 2023-09-20T13:52:42.0290000Z
Event ID: 55
Task: N/A
Level: Error
Opcode: Info

Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: LAPTOP-I85OKVST
Description:
A corruption was discovered in the file system structure on volume E:.

The exact nature of the corruption is unknown. The file system structures need to be scanned online.



Name AMD Radeon(TM) Graphics
PNP Device ID PCI\VEN_1002&DEV_1636&SUBSYS_8787103C&REV_C6\4&2FEAE042&0&0041
Adapter Type AMD Radeon Graphics Processor (0x1636), Advanced Micro Devices, Inc. compatible
Adapter Description AMD Radeon(TM) Graphics
Adapter RAM 512,00 MB (536.870.912 bytes)
Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\u0394441.inf_amd64_57e767cb37419fb0\B394106\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0394441.inf_amd64_57e767cb37419fb0\B394106\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0394441.inf_amd64_57e767cb37419fb0\B394106\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0394441.inf_amd64_57e767cb37419fb0\B394106\amdxc64.dll
Driver Version 31.0.21023.2010
INF File oem110.inf (ati2mtag_Renoir section)
Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\U0394441.INF_AMD64_57E767CB37419FB0\B394106\AMDKMDAG.SYS (31.0.21023.2010, 95,12 MB (99.737.448 bytes), 21/08/2023 8:14)

I beg your pardon, how do I reconnect the E: drive?

My laptop has 2 SSDs, one is drive C, the other one drive D. There is no drive E.

Unless, is it possible that it can meant as any flashdisk/external HDD ever connected to this laptop hence identified as drive E?

1) The prior post was edited.



2) The event viewer reported problems on E: multiple times during the prior 30 days.
(They were all on the same date: 09/20)



3) Please run chkdsk /b /v on all drives using the syntax:

chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v E: etc.

Make sure that the Windows drive runs overnight while sleeping.



4) After completing all chkdsk runs run:





5) Download and install:

View / Change / Remove drive letters assignment in your system > post images or share links

Do I need to do chkdsk on drive E? It is a removable drive I think.

It is not required but it is in your best interest to reduce or fix potentially significant problems.

The non-windows drives can run in the background.

The Windows drive can run overnight while sleeping.

Alright on it I'll notify you

Ok.
Run HD Tune before chkdsk.

I suspect the E: dive was a flash drive you plugged in, it's quite common to see errors on those. I certainly agree that the free space on your C: drive is too small for comfort, but more worrying is that your System log includes a few of these errors...
Your paging file is on your C: drive, so it's worth downloading the WD Dashboard and run drive diagnostics on there. However, I suspect RAM might be a more likely suspect because in one of the dumps you uploaded (and the corresponding kernel dump you just uploaded) there is an indication of a potential RAM issue. The dump is a common 0xA IRQL_NOT_LESS_OR_EQUAL bugcheck, which means that a driver accessed invalid memory (ie. took a page fault) whilst running at an elevated IRQL (when page faults are not allowed). This is commonly a third-party driver screw-up, but in this case there are no third-party drivers involved, that's often a good indication of a hardware problem.

The bugcheck happens because of an invalid opcode fault (nt!KiInvalidOpcodeFault) which means that the instruction pointed to by the instruction pointer was invalid in some way. Looking at the full call stack we see something interesting...
You read these stacks from the bottom up (they are push-down stacks). You can see a 'read file' operation followed immediately by the nt!KiInvalidOpcodeFault function call. That tends to suggest a RAM issue, since no third-party drivers were involved..

You have two sticks of 8GB RAM, so the easiest and most reliable way to check your RAM is to remove one stick and just run on the other stick for a while (or until it BSODs), then swap sticks and run on just the other stick for a while (or until it BSODs). If it BSODs on both sticks on their own then it's probably not RAM, but if it BSODs on one and not the other then you have your culprit.

BTW. The other (earlier) dump is a 0x133 bugcheck with an argument 1 value of 0x1, these can only be analysed with a kernel dump. Unfortunately there is only ever one kernel dump stored and the dump for this 0x133 was overwritten when the more recent 0xA BSOD occurred.

zbook said:

Ok.
Run HD Tune before chkdsk.

Click to expand...

Done. Attached are the results.

In the meantime, I have done chkdsk on drive E: (which doesn't exist so it rejected the command) and done chkdsk on drive D: and it says
Windows has scanned the file system and found no problems. No further action is required.

I'll do the chkdsk on drive C: later overnight like you suggested.

@ubuysa thank you for your response, but I'm afraid I'm not a tech savvy like you so you lost me a few sentence ago. However, I *did* have my suspicion regarding my hardware specifically the RAM. However, I've put this laptop on repair on its warranty life for like 5-7 times in the course of 2 years. They did changed the motherboard but not RAM. I think that's why I stop suspecting my RAM malfunctioning (as the official repair allegedly found no problem on it).

However, to make things simpler, would it be wiser to just...exchange both RAM for a new ones? Sure it would cost me money, but what can I do if it is the culprit?

The RAM will be troubleshooted if there are recurrent BSOD after modifying the driver.

The multiple types of bugchecks can happen with both.


Please run HD Sentinel (trial version) after completing all chkdsk runs.

Post images or share links for results on these tabs:
a) Overview
b) Temperature
c) SMART


Download and install: HP PC Hardware Diagnostics UEFI – v10.1.0.0


Instructions will be posted later in this thread.

Just pop one RAM card out for a day or two. Then remove the other card and reinsert the first one fir a day or two.

Does it BSOD on one card but not the other?

Attached some updates on this matter. In the meantime, I will reinstall AMD GPU driver.

Chkdsk C:



When available post Nirsoft images or share links.
(post #6, step #5)

Update the progress with:
a) post #2, step #3
b) post #13, download and install HP UEFI hardware diagnostics

Attached are the files you asked for.

Please test E: using HD Sentinel (results are instantaneous) > post images or share links

Plan chkdsk /b /v E:







C: free space report

Attached are the files you asked for.

For any new BSOD post a new V2 share link


Plan to run the HP UEFI hardware diagnostics overnight while sleeping:

Power on the computer > repetitively click F2 or F10 > UEFI Hardware diagnostics > system > extensive > loop until error > the next day if it has made two or more loops > click esc > take pictures > post images or share links