BSOD Address caused by address : ntoskrnl.exe+3f7dd0

Thanks for the reply.

Except for MemTest 86, I have completed the above steps. I will run the Memest86 Test during the night.

The CBS Log Details along with the Screenshots and V2 Logs are attached on the link : V2 Logs 14072022

I contacted HP Support, and they are saying that they wish to perform a complete System Reset. And as a result, I want your advice for the same. They are saying that they will approve RMA (Return Merchandise Authorization) only after they have tried every other alternative.

Please guide me whether to approve the complete System Reset or not. Will perform MemTest86 during the night.

NOTE : MiniDump files are being deleted even after freeing up the required space. See to it as well.

Regards,

Rakesh Kumar

Open administrative command prompt and copy and paste:

sfc /scannow

dism /online /cleanup-image /restorehealth

chkdsk /scan

wmic recoveros set autoreboot = false

wmic recoveros set debuginfotype = 7

wmic recoveros get autoreboot

wmic recoveros get debuginfotype

wmic computersystem where name="%computername%" set automaticmanagedpagefile=true

wmic computersystem where name="%computername%" get automaticmanagedpagefile

bcdedit /enum {badmemory}

Post images or share links displaying the commands with results.

Once there is sufficient drive free space Windows may create and maintain memory dump files.

Once the V2 log collector log files indicates memory dump files I'll post information on how to collect and compress them for debugging.

For Memtest86 please run two tests of four passes each.

Post images and if available include text reports with the images into this thread.

More information is needed to evaluate drivers and hardware.

Thanks for the reply @questions_.

This link : https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup\_plus\_log.bat

which you shared is saying "You are not logged in or you do not have permission to access this page."
Please see to it.

Also, I will use memtest86 in the night.

As far as I can understand, there dosn't seem to be any hardware problem. So, if I update my Windows to Windows 11, will these BSOD's stop troubling me?

Eagerly waiting for your reply.

a) There were three new BSOD dated today July 13, 2022 with bughchecks 139 and A.

All bugchecks displayed the continued use of WDV.

The V2 log collector displayed that WDV is now off.

Please maintain it in the off position as there were no misbehaving drivers.

b) For share links please use non-rar links

c) Run: https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup_plus_log.bat

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

d) In order to create and maintain memory dump files please free up 30 GB

The memory dump file was created but Windows automatically deleted it today, July 13, 2022, due to deficient drive free space.

Please make sure that there is always 30 GB free during the troubleshooting so that memory dumps will be available for debugging.

https://www.tenforums.com/tutorials/83441-free-up-drive-space-windows-10-a.html

https://support.microsoft.com/en-us/windows/free-up-drive-space-in-windows-a18fae02-a0fa-8df9-9838-8970f9939de4

e) Run Memtest86 (free version) for two tests of four passes each (total eight passes)

https://www.memtest86.com/

Take pictures and post images or share links into this thread.

Just one error is a test fail and you can abort testing.

Testing can run overnight.

Memtest86 has a feature to create text reports.

If possible please include the text reports with the images in the share links.

f) For any BSOD run the V2 log collector and post a share link into the newest post

Okay, the following things have been completed.

1. Turned off Windows Driver Verifier.
2. Made Space in C Drive to 28 GB, but after 3 hours, it again went back to 20 GB.
3. Ran Prime95 blended test for 2.25 hours, but no error was reported as such.
4. Ran HP UEFI Diagnostic tool for 7 hours, 2 loops but no error was found.

Only 1 BSOD happened after that : IRQL Not Less or Equal

V2Logs : V2 Logs 13072022

Your reply will be appreciated,

Regards,

Rakesh0710