BSOD on Boot - IRQL_not_less_or_equal

Thanks for clarifying, you'll just need to leave it running until it either crashes again, or for 24-48 hours, whichever happens to occur first. In either case, you'll then need to disable Driver Verifier from an elevated command prompt using:


And then reboot the computer for the changes to take effect. That command will then delete two values from the registry which were set by Driver Verifier, which effectively then disables it.

Alright, thank you. It did crash I think twice when I restarted the laptop after first enabling Verifier, but then it booted normally so I will leave it running for now.

Okay thanks, please upload the dump files as you have previously if it crashes again.

How come you did not follow the tutorial in post #6?

BlueRobot it crashed with error code PFN_list_corrupt. The laptop had been running fine (albeit laggy) under normal load, including watching videos and gaming, but started to act up when I needed to disconnect it from the charger to move it and it crashed shortly afterwards with the charger reconnected. My Chrome tab also crashed right before that with error code stack_buffer_overrun.
Logs here: OneDrive

zbook your instructions said to run it in Safe Mode, but that's basically too unstable for me to get anywhere - it crashes probably about 10 times before it can boot into Safe Mode and then only lasts for probably 5 seconds before freezing or crashing.

fzy1999 said:

zbook your instructions said to run it in Safe Mode, but that's basically too unstable for me to get anywhere - it crashes probably about 10 times before it can boot into Safe Mode and then only lasts for probably 5 seconds before freezing or crashing.

Click to expand...

In post #6 step #1 was safe mode testing.

In post #6 step #3 was WDV testing.


How come you did not follow the WDV tutorial in post #6?



Please restart WDV with the 3 customized tests in the Ten Forums tutorial.


The goal is to find misbehaving drivers or rule in malfunctioning hardware.


So far the findings support malfunctioning hardware.




After WDV testing > run Lenovo UEFI hardware diagnostics and custom diagnostics > post images or share links displaying the tests performed with results








There is limited hardware swap testing for this laptop.



Consider servicing at a local repair store or at Lenovo.

zbook said:

After WDV testing > run Lenovo UEFI hardware diagnostics and custom diagnostics > post images or share links displaying the tests performed with results

Click to expand...

They've already ran Lenovo Diagnostics and all the tests passed.

zbook said:

Please restart WDV with the 3 customized tests in the Ten Forums tutorial.


The goal is to find misbehaving drivers or rule in malfunctioning hardware.

Click to expand...

Those Driver Verifier settings aren't going to verify the point you're trying to make, they have no relevance to the crashes at hand here, those settings are intended for testing for proper IRP handling. Although, I am in agreement with you regarding there most likely being a hardware issue.

@fzy1999

I would disable Driver Verifier now using the following command:


Then reboot the computer for the changes to take effect. Afterwards, I would do a clean boot using the following instructions, if it crashes while in that state, then we can be most certain that a hardware issue is at fault here. You'll effectively be booting like you were in safe mode.

Please make sure that post #6 images / share links are posted into this thread:

What a bizarre issue - I restarted it 10 times in clean mode, and it crashed exactly 5 out of 10 times, the pattern being: crash - fine - crash - fine - crash…

I assume that there’s a high chance of a hardware fault then. Is there any way to narrow it down? My first thought is the RAM but that has passed every test used on it. Maybe the boot drive?

The images attached show Lenovo Diagnostics test I ran: Run All -> Full (Unattended) -> Display, CPU, Memory, Motherboard, PCIE, and Storage. I let it run overnight and it showed 100% or pass next to all of them. I can run it again to see if anything changes.

V2 logs and Lenovo Diagnostics images attached: OneDrive

I would suggest running each of the Prime95 stress tests for maybe 20-30 minutes each, however, my main concern is going to be keeping the CPU temperature down so I would recommend keeping the laptop close by while you run each of the tests. You can use something like CoreTemp to watch the CPU temperature; make sure you abort the test if the temperature gets too close to your TJMax.

Prime95: GIMPS - Free Prime95 software downloads - PrimeNet

If the system crashes while running the test then it is a good indicator that the CPU is faulty.

I have been having this exact problem (which has been getting worse). Each reboot was a gamble - but once the machine booted it would be fine for many days.

Lenovo legion 5 pro 16” 6800h and 3070.

Ran diag tools and no issues reported.
Reinstalled os and problems became worse (unable to install win10, win11 or Linux without crash)
Purchased December 2021 with additional 2yr warranty.

Sent back to Lenovo last week and after a couple of email exchanges they replaced motherboard.

Should arrive back here coming Wednesday (bank holidays and Easter going to delay return).

If you are still in warranty - I strongly suggest you backup data you value and send to Lenovo for fix.