Multiple similar BSODs every day at random intervals.

You have tried nearly everything, sometimes those values for TdrDelay and TdrDiDelay could help. It gives your GPU some more time to swallow all the data....instead of the default two seconds given by Windows.


_____________________________________________________

"Used Windows 10 Home 64 USB media to repair Windows 10 installation"

I think you also should try to do a repair-upgrade with an ISO, and then use an ISO-version that is higher, or newer, than your existing version.
It will take about an hour.....instead of struggling days or weeks with some endless search.

NTN said:

You have tried nearly everything, sometimes those values for TdrDelay and TdrDiDelay could help. It gives your GPU some more time to swallow all the data....instead of the default two seconds given by Windows.

I have gone to the registry address shown in your image and TdrDelay, TdrDiDelay, and UnsupportedMonitorModesAllowed are not there, only the first five entries of that list are present. Would I need to add the Tdr entries manually?

Would I need to add the Tdr entries manually?[/QUOTE]

Yes.


UnsupportedMonitorModesAllowed you don't need, if you are sure your monitors are supported.

NTN said:

"Used Windows 10 Home 64 USB media to repair Windows 10 installation"

I think you also should try to do a repair-upgrade with an ISO, and then use an ISO-version that is higher, or newer, than your existing version.
It will take about an hour.....instead of struggling days or weeks with some endless search.

I believe that is what I did, unless you're referring to something else entirely. I downloaded an ISO of my present version of Windows directly from Microsoft that is used for repairing, upgrading, or reformatting Windows 10. The only thing I did differently was place it into a bootable USB drive rather than a Disc as I have no optical drive.

"my present version..."

Newer version if you could get one.....what version do you have now?


Here is the absolutely last version of Windows 10, 19045.2670 in your language en-US.
HiDrive


Put it in a folder on the desktop, WindowsISO you could call it...or whatever.
Extract it to the same folder. (When you are finished it is easier to clean up....)
Open setup.exe as adm., and then it will nearly suit it self, you just click yes a couple of times......and no when it ask if you also want to update the drivers or something.
Will take about half an hour, dependent how powerful your PC is.
And of course you take a back-up first of your system, you always do.

NTN said:

"my present version..."

Newer version if you could get one.....what version do you have now?


Here is the absolutely last version of Windows 10, 19045.2670 in your language en-US.
HiDrive


Put it in a folder on the desktop, WindowsISO you could call it...or whatever.
Extract it to the same folder. (When you are finished it is easier to clean up....)
Open setup.exe as adm., and then it will nearly suit it self, you just click yes a couple of times......and no when it ask if you also want to update the drivers or something.
Will take about half an hour, dependent how powerful your PC is.
And of course you take a back-up first of your system, you always do.

I am unable to edit my initial post to correct the version number, but after updates I am now on build 19045.2604. The KB5022906 update to bring me to build 19045.2670 has not yet appeared in Windows Update when I check for updates.

"The KB5022906 update to bring me to build 19045.2670 has not yet appeared in Windows Update when I check for updates."

But that is good!

Than you will use the ISO I gave you to upgrade.




By the way.....your Nvidia GTX 1660ti (Mobile) 6GB, do you have the last driver for this?
GeForce Game Ready Driver | 528.49 | Windows 10 64-bit, Windows 11 | NVIDIA
528.49 you should have.

With a new version, 19045.2670, you probably must put in the Tdr-values one more time there.

Jagick said:

I will break this post up into sections for easy digestion. The "culprits" of the crashes, the errors they cause, the steps I've taken to try to figure it out or fix it, and my system specs. Any information or help that can be provided will be greatly appreciated!

Multiple times a day, every day the following two items cause my Laptop to either simply crash and restart with no error screen or message given, or I do get the dreaded blue screen before it restarts. There is no discernible reason for the crashes. They will happen when the system is idle on the desktop with nothing else really running, when it is under heavy load, or even just when browsing the web. When I get the crashes in which no actually BSOD appears (yet a minidump is still created,) typically my screen either freezes or turns black and the sound through my headset just becomes a loud buzzing noise until the system restarts. Sometimes, the screen will turn black except for numerous red, green, and white pixels in various patterns at different locations on the screen. When it comes to the Minidumps though, Whocrashed said the "culprits" are as follows but with no specific information about why:

1. ntkrnlmp.exe
2. ntoskrnl.exe
3. hardware.sys

When I do get an actual BSOD with an error code, I've received all of the following as a result, the actual error varies but it seems to be getting worse. This is the order in which they have ever appeared:

1. IRQL_NOT_LESS_OR_EQUAL
2. KMODE_EXCEPTION_NOT_HANDLED
3. ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (Received only on one occasion)
4. SYSTEM_SERVICE_EXCEPTION
5. KERNEL_SECURITY_CHECK_FAILURE

I am at wits end attempting to figure out what specifically is causing this. Here are the steps I have taken thus far to try to discern the cause and remedy the crashes:

1. Ran Chkdsk /f /r -- No issues found at all.
2. Ran DISM.exe /Online /Cleanup-Image /Restorehealth -- Preemptive step to SFC
3. Ran SFC /Scannow -- No issues found at all.
4. Ran Memtest 86 through all possible tests with four passes each. -- No Errors found at all.
5. Ran Lenovo Diagnostics Full Test for two hours -- No issues found, everything passed.
6. Cleaned out fans and internals. -- Temperatures are average and stable.
7. Updated and reinstalled as many drivers as I could for things such as chipset, GPU, etc.
8. Updated BIOS.
9. Used Windows 10 Home 64 USB media to repair Windows 10 installation

The laptop I am using is a Lenovo Legion 5 15ARH05H and my system specifications are as follows:

1. Operating System: Windows 10 Home 64-bit (Version 22H2, OS Build 19045.2546)
2. CPU: AMD Ryzen 7 4800H
3. RAM: DDR4 16GB (2x8GB) Dual-Channel Kingston @ 3200MHz (22-22-22-52)
4. Motherboard: LENOVO LNVNB161216 (FP6)
5. GPU: 6GB NVIDIA GeForce GTX 1660 Ti (Lenovo)
6. Storage: 1TB Samsung SSD 980 NVMe
7. Audio: Sound Blaster Play! 3 USB sound card

I was considering running driver verifier next but have heard it can brick your PC on rare occasions, so have refrained from doing that thus far. I have also considered reformatting but would like to use that only as a last ditch effort.

I have linked v2 logs from two different sets of crash dumps (some older crashes from earlier this week I had saved and the most recent ones) for your convenience. Unfortunately the zip was a bit too large to use the attachment method on the forum. Thank you for any help any of you can provide!

VALARIUS-M-(2023-02-17_20-34-44)

Something is going on with one of the gpu's. i dont know if you realize it, but you have 2.

1: NVIDIA GeForce GTX 1660 Ti
2: AMD Ryzen 7 4800H with Radeon Graphics

im not sure why lenovo would use a cpu with onboard graphics (amd based graphics) and an nvidia card.

the dmp's are all over the place, but the common item in most is calling out a power/idle state issue with the video subsystem. maybe lenovo is using the cpu's gpu for 2d and the nvidia for 3d, but would make more sense to use an amd card over the nvidia for driver compatibility.

its late and i drove my taxi 14 hours today, but look in the tutorial index for how to DDU. Remove all drivers. Reboot. Install amd drivers. reboot. install nvidia drivers. reboot. test.

im gonna sleep and check tomorrow if it helped

tomdsr said:

Something is going on with one of the gpu's. i dont know if you realize it, but you have 2.

1: NVIDIA GeForce GTX 1660 Ti
2: AMD Ryzen 7 4800H with Radeon Graphics

im not sure why lenovo would use a cpu with onboard graphics (amd based graphics) and an nvidia card.

the dmp's are all over the place, but the common item in most is calling out a power/idle state issue with the video subsystem. maybe lenovo is using the cpu's gpu for 2d and the nvidia for 3d, but would make more sense to use an amd card over the nvidia for driver compatibility.

its late and i drove my taxi 14 hours today, but look in the tutorial index for how to DDU. Remove all drivers. Reboot. Install amd drivers. reboot. install nvidia drivers. reboot. test.

im gonna sleep and check tomorrow if it helped

You're not off the mark at all. Lenovo laptops use a feature called "Hybrid Mode" through the Lenovo Vantage software. This defers to the CPU based graphics for non intensive tasks and the Nvidia GPU would be activated for gaming and 3D tasks. I have kept this feature disabled since I got the laptop back in August of 2021 so that only the Nvidia GPU is utilized at all times. It is known to cause shoddy performance and other issues so I have always kept it off.

I should have clarified in my initial post concerning my updating and re-installation of drivers, but I did use DDU to remove both AMD and Nvidia display drivers. I opted not to reinstall the AMD drivers at all just in case they were coming into conflict. Since doing this. I have only experienced one BSOD which occurred while in the process of reinstalling the Nvidia display driver. I unfortunately cannot recall if I have crashed again since then. I'll give DDU another go just for good measure.

- - - Updated - - -

I would edit my posts if it would let me, so sorry if this constitutes a rule breaking bump.

Unfortunately I crashed three times within an hour this afternoon, though none of those generated a dump file. Nothing above has worked thus far. Could this potentially be a hardware issue with the GPU?