Solved Regular BSODs

Since KB5032288 (preview) started to get BSODs...decided to wait for the patch Tuesday release KB5033375 to see if it would fix the issue. Alas it did not, although BSODs have reduced in frequency. This is the link to my data on OneDrive is OneDrive.
Thanks in advance for any help. Not sure what the power supply specs are...the computer is HP about 3 years old.

Please perform the following steps:


1) Run Tuneup plus > post a share link





2) The BIOS Version/Date AMI F.48, 27/07/2022

Upgrade the BIOS: F.48 > F.51



3) Make a new restore point:



4) Read this tutorial on Windows Driver Verifier:



Learn the methods to recover from using the tool by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail


Plan to run the tool for approximately 48 hrs with various customized tests.

Start the tool with these settings:

a) Test all non-Microsoft drivers
b) Test no Microsoft drivers
c) Start with the 3 customized tests in the TF tutorial


If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link into this thread using one drive, drop box, or google drive.

For any new BSOD post a new V2 share link into the newest post.

Upgrade the HP UEFI hardware diagnostics:



Reinstall the Intel GPU drivers with the driver displayed on the HP website.

igfx igfx c:\windows\system32\driverstore\filerepository\iigd_dch.inf_amd64_0f12908b4ff13ff7\igdkmd64.sys

Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\IIGD_DCH.INF_AMD64_0F12908B4FF13FF7\IGDKMD64.SYS (31.0.101.2125, 42.19 MB (44,234,696 bytes), 20/06/2023 12:35 PM)

Hi zbook,
Results for Tuneup and Verifier at this link OneDrive.
Have also upgraded HP UEFI hardware diagnostics.
Had trouble trying to install the HP GPU driver. For my computer, the HP website lists 11 graphics drivers, the first Intel driver is Intel High-Definition (UHD) Graphics Driver (GLK) (Windows 10 v1909) ...downloaded OK but failed to install with an error message "OS not recognised". Same thing happened when I tried the next Intel driver on the list. So, the current driver hasn't changed, that is, (C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\IIGD_DCH.INF_AMD64_0F12908B4FF13FF7\IGDKMD64.SYS (31.0.101.2125, 42.19 MB).

I guess I won't post again unless I get a BSOD or 48 hours have passed.

Thank you, I really appreciate your help.

Well, that didn't take long! Here's the link to the V2 detail OneDrive

If there were no major performance including very slow boot please modify the WDV settings:

[ ] 0x00000001 Special pool.
[ ] 0x00000002 Force IRQL checking.
[ ] 0x00000008 Pool tracking.
[ ] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[ ] 0x00000100 Security checks.
[ ] 0x00000800 Miscellaneous checks.
[ ] 0x00020000 DDI compliance checking.
[ ] 0x00080000 DDI compliance checking (additional).


If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link into this thread using one drive, drop box, or google drive.

For any new BSOD post a new V2 share link into the newest post.

Verifier detail link Verifier2.docx

New V2 link OneDrive

If there were no major performance problems including very slow boot please modify the WDV settings:

[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.
[ ] 0x00000010 I/O verification.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.



If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link into this thread using one drive, drop box, or google drive.

For any new BSOD post a new V2 share link into the newest post.

​

If there is no immediate BSOD when WDV is turned on and there are no major performance problems then run all customized tests except:

[ ] 0x00000004 Randomized low resources simulation.


If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link into this thread using one drive, drop box, or google drive.

For any new BSOD post a new V2 share link into the newest post.

Got immediate BSOD...had to power off, then power on and immediate BSOD. Powered off again, waited for 1 minute and powered on into a HP recovery environment where the only option was to click a restore button, then there was a diagnosis procedure then an attempted repair which eventually worked and opened into the windows recovery options page. here is the latest V2 link OneDrive

My message #11 is in response to your message #9, sent just before your message #10. So, I'll wait for you to confirm the next step.

Which VPN software is in use?

Uninstall or Uninstall and reinstall:

avpndriver avpndriver c:\windows\system32\drivers\avpndriver.sys


Restart WDV using post #10.

(heading to bed, its 425 am)

Most of those Driver Verifier settings are going to lead to false positives and random unrelated crashes, as explained in the DV tutorial which has been specifically written for Windows 11: BSOD - Driver Verifier Instructions [Official]

Please read that tutorial carefully, particularly about how to recover from a situation, whereby the machine may get stuck into a boot loop. I've outlined in detail, why some of those settings should not be used and how they're rather dangerous to recommend unless you're testing for a very specific issue.

Edit: Fixed typo

Been out most of today...just about to start a full backup in case things go pear shaped before I have a crack at post #10. Also, just trying to digest what x BlueRobot has said in post #14.

I use PureVPN. I uninstalled it, rebooted, then reinstalled it. I've also turned off Microsoft's new VPN in Edge under settings>privacy, search and services>security>microsoft edge secure network. Trying to think if there is any connection between the recent updates and the BSODs. Haven't had any problems now for about 15 hours but the computer has been in sleep mode for most of that time.

For WDV please follow the methods in this tutorial:



Post a new V2 share link after another day or two.

I think there is enough justification in this thread: BSOD page_fault_in_nonpaged_area ntoskrnl.exe windows 11

Started WDV as per post #10. On reboot, got instant BSOD. Powered off and booted into RE>command prompt>reset WDV. Reboot to instant BSOD. Reboot to WRE to attempt repair...tried all options but couldn't get into normal windows. Had to resort to using my backup to get up and running again. Now I intend to do a repair install and see if things settle down. If not, I'll be back! Thanks heaps for the help especially when it's so close to Christmas.

Wishing everyone at ElevenForums and their families, peace and happiness over the festive season.

Plodder said:

Started WDV as per post #10. On reboot, got instant BSOD.

Click to expand...

That doesn't surprise me at all, as already mentioned, most of the settings recommended by @zbook should not be used as they can lead to an unbootable machine. In addition to that, settings like "Low Resources Simulation" can generate false positives which just muddles the actual root cause of your crashes.

I'll leave the matter to you, I'm unsubscribing from this thread as it isn't productive with two competing viewpoints, one of which is based on ignorance.

I'm back. After mulling over the decision to do a repair install, I decided instead, to restore from a full computer image I had taken in mid November, before any BSOD events. This took me back to Build 22631.2715. From there, I used Windows update to bring me up to v 2861.
Ran dism, sfc, chkdsk, MS defender offline scan, Malwarebytes threat scan...all good.

I read somewhere that disabling hyperthreading in the BIOS can help...so I did that.

Computer was stable for 5 days when a BSOD occurred. At least this was a normal BSOD event, in that after collecting the info, the computer booted itself back into windows. Ran all the above checks, plus the win memory diagnostic tool...no errors found. Computer has been stable since then.

Here's a link to the V2 log data OneDrive