I was not notified you had replied again, this forum is a bit strange please use the Comment section on my replies, so I get a notification when you reply.
That minidump file also just indicated generic errors, nothing specific either this time.
Repeated BSOD Errors on Lenovo Legion Pro 7 After Windows Update
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 22%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMR%3C/text%3E%3C/svg%3E)
Mohammed Riad
5
Reputation points
Experiencing a series of unpredictable Blue Screen of Death (BSOD) errors on a Lenovo Legion Pro 7 16IRX8H (Type 82WQ) running Windows 11. The issues started while working in Android Studio for app development and crashed twice with the error:
DRIVER_OVERRUN_STACK_BUFFER
Following an automatic Windows Update, the uninstallation of those updates triggered a massive wave of BSODs with various error codes, including:
-
KERNEL_MODE_HEAP_CORRUPTION -
DRIVER_OVERRUN_STACK_BUFFER -
SYSTEM_SERVICE_EXCEPTION -
HYPERVISOR_ERROR -
IRQL_NOT_LESS_OR_EQUAL
These crashes persist even when attempting to boot into the Windows Recovery/Repair environment, hindering normal troubleshooting.
Steps Taken So Far:
- Uninstalled the latest Windows updates that were installed on the day the BSODs started.
- Rebooted, only to encounter a continuous series of BSODs.
- Tried to reboot to the UEFI diagnostic tab but ended up in Windows Recovery and Automatic Repair, where BSODs still occurred.
- Accessed UEFI diagnostics to perform hardware checks, and all components (CPU, MEMORY, STORAGE, MOTHERBOARD) passed.
- Unplugged the USB connection to the Android device.
- Successfully rebooted without entering the Automatic Repair Tool and without experiencing BSODs.
- Collected crash dump files from
C:\Windows\Minidumpfor analysis:
Windows for home | Windows 11 | Performance and system failures
-
Mohammed Riad 5 Reputation points
2025-09-21T15:47:57.4466667+00:00 I have tried the command
sfc /scannowand this is the CBS.log
Sign in to comment
5 answers
Sort by: Most helpful
-
DaveM121 891.9K Reputation points Independent Advisor2025-09-21T17:43:09.13+00:00 -
Mohammed Riad 5 Reputation points
2025-09-21T17:57:29.9166667+00:00 I don't know, i checked again and yet Verifier is enabled.All these BSODs shares same timing after device boot up within 5~9 minutes without doing anything, it triggers with random error codes and just reboots and the same thing happens again & again.
All of these tests were conducted without having to do anything at all, just leaving windows on home screen.
-
DaveM121 891.9K Reputation points Independent Advisor
2025-09-21T18:00:23.5333333+00:00 Okay, please disable Driver Verifier and do not re-enable it, then wait for your PC to crash normally and please upload any new minidump files you may get for analysis.
-
Mohammed Riad 5 Reputation points
2025-09-21T18:02:22.9966667+00:00 I am unsure to tell exactly, but i think it just started today I'll mention some updates done from Windows Update today, maybe if there's any other issues faced from different users.
Quality Updates:
- KB5064401
- KB5065426
No driver update were performed on today, last one was Lenevo System from 04/09/2025.
Other Minidump generated:
2- DRIVER_OVERRUN_STACK_BUFFER [NO DMP]
3- VIDEO_MEMORY_MANAGEMENT_INTERNAL [NO DMP]
4- VIDEO_MEMORY_MANAGEMENT_INTERNAL: https://drive.google.com/file/d/1yJo7Y1uaEa7j17rbJX4qlOyUiwPmHooT/view?usp=drivesdk
5- ???: https://drive.google.com/file/d/1M20XvMGhzo0_aoFzFIaArSKp-maUD7Wj/view?usp=drivesdk
-
Mohammed Riad 5 Reputation points
2025-09-21T18:04:54.13+00:00 Regarding ones without verifier enabled, they're already given in initial post.
-
DaveM121 891.9K Reputation points Independent Advisor
2025-09-21T18:05:56.5866667+00:00 Those two minidump files indicate the graphics drivers caused your system to crash.
-
Mohammed Riad 5 Reputation points
2025-09-21T18:17:31.91+00:00 But i don't remember to have any graphic update recently or any soon.
GeForce Game Ready Driver 561.09 — Wed Sep 11, 2024
Neither Windows Update has any record about any updates on drivers since 04/09/2025.
-
DaveM121 891.9K Reputation points Independent Advisor
2025-09-21T18:22:51.68+00:00 The 561 versions of the Nvidia drivers are usually very stable, go to the Nvidia website and from there, try installing a couple of versions around version 572 to try to find a version of the drivers that may stabilize your system.
-
Mohammed Riad 5 Reputation points
2025-09-21T18:25:15.5666667+00:00 Also for some reasons i have an "Unknown device" in Device Manager > Other devices.
Details has value "ROOT\SYSTEM\0004"
In events it had "Device configured (null)" on
13/07/2025 (4 times)
14/08/2025 (2 times)
15/08/2025 (1 time)
21/09/2025 (22 time)
-
Mohammed Riad 5 Reputation points
2025-09-21T18:30:10.2433333+00:00 Also the issue seems to be gone when i uninstalled a specific WU.
unfortunately i don't remember which KB i did uninstall, surely it was "Security Update for Microsoft Windows", i may predict KB5063878 or KB5064401
-
Mohammed Riad 5 Reputation points
2025-09-21T18:34:11.62+00:00 Regarding NVIDIA driver, i didn't seem to have any problem with it previously, so I'm quite sure it's not the cause of the issue, ofc as long as the future Windows Update have backwards compatibility to older drivers like the version i had.
-
DaveM121 891.9K Reputation points Independent Advisor
2025-09-22T06:35:39.1566667+00:00 If you are able to uninstall the KB update you believe is causing the BSOD's, then that may be the best option, then pause your updates and wait for the October update
-
Mohammed Riad 5 Reputation points
2025-09-23T14:32:26.43+00:00 For some reason it started doing it again, and i am unable to boot up successfully or at least if successfully, only for few seconds to BSOD.
Same thing either for Automatic Repair Tool, it never succeed to load, only to drop BSOD again with error like "DRIVER_OVERRUN_STACK_BUFFER"
-
Mohammed Riad 5 Reputation points
2025-09-23T15:53:49.1366667+00:00 I tried booting on USB that i set-up with Media Creation Tool, and it lasted few seconds until an error shown up APC_INDEX_MISMATCH.
At this point i have no clue whether this is a hardware failure or something else i don't know yet.
-
Mohammed Riad 5 Reputation points
2025-09-23T20:42:35.07+00:00 I tried a bootable Linux Ubuntu and it seemed to work fine, now i am unsure again if it's a driver fault..
-
DaveM121 891.9K Reputation points Independent Advisor
2025-09-24T06:13:09.1066667+00:00 Sorry, I was offline, in that case, if you are unable to get Windows installed from a USB to result in a stable and responsive system, most likely, there is an underlying hardware issue, it is time to consider taking your system to a PC Shop to have the hardware tested.
Sign in to comment -
-
Mohammed Riad 5 Reputation points
2025-09-21T17:23:36.09+00:00 -
Mohammed Riad 5 Reputation points
2025-09-21T17:16:10.0466667+00:00 Ok it seems that it reproduced itself without any further actions, perhaps Windows Update, managed to grab the driver that the crash happened on "ntoskml.exe" also during the runtime it's always
DRIVER_OVERRUN_STACK_BUFFER.i turned driver verifier in wait for any future issues to happen then I'll provide the dumps.
-
Mohammed Riad 5 Reputation points
2025-09-21T15:51:40.7766667+00:00 I don't think i am able to reproduce this, however judging by CBS.log file i attached in comment of the initial post, says corruption on
bthmodem.sys-
DaveM121 891.9K Reputation points Independent Advisor
2025-09-21T16:42:22.41+00:00 Sorry, I was not notified you had replied, this forum is a bit strange please use the Comment section on my replies, so I get a notification when oyu reply.
That driver you list is a Windows System Bluetooth driver and that was not indicated in the minidump files as the underlying cause of the system crashes.
Sign in to comment -
-
DaveM121 891.9K Reputation points Independent Advisor
2025-09-21T15:47:08.0233333+00:00 Your minidump files just indicate generic errors, nothing specific.
To try to force Windows to show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files
Before you run Driver Verifier, please create a new System Restore Point
.
.
Note, if you have any difficulty getting into Windows with Driver Verifier enabled:
Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down
Do this twice
On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.
Go to Troubleshoot - Advanced Option - Startup Settings and click Restart
Upon restart, press 4 to enter Safe Mode
Open Command Prompt as Administrator and run these two commands, then restart your PC.
verifier /reset
verifier /bootmode resetonbootfail