https://www.memorystock.com/memory/LenovoIdeaPadL34015IWL.html?srsltid=AfmBOopFgV_GH7d1O6J8JpDTCCIXUKV5bvLhI2HwI7xMG5FR8tFC0KP2
This PC has 4 GB soldered on motherboard and 1 slot for additional memory (currently 4GB)
The given sire has 8BG and 16GB for that 1 slot. So, total memory can be up to 20GB.
Open Display Settings (RC the Destop)
Set to Extended Displays to see both Display 1 and Display 2 (Was Duplicate)
Select BLUE Display 2 and uncheck Main Display if checked
Select BLUE Display 1 and check Main Display
Set Duplicate Displays as before
This started back in April/May timeframe. But I wanted to capture enough to accurately describe. Note until 5/2527 when my entire system was trashed (no longer boot- thanks MSFT Restore) I was on Windows 23H2. After that I was on 24H2 after a Clean Windows Install. I lost all Event View logs at that time, so am working only with the late May BSOD documentation on 24H2 now (5/30/25 events)
---------------------------------------------------------------------------------
Temporary Workaround :
First, a temporary workaround was to Uninstall the updates put out every 2nd Tuesday of the month and PAUSE windows Updates for 4 weeks until the next cumulative quality/security update hit. BSODs occurred after each 2nd Tuesday install since April (now June). On 5/30/25 KB5058411 was uninstalled. However, on 6/5/25 I reinstalled after finding a new driver for my AMD Radon Vega Graphics Adapter which I installed after laborious efforts to find it. So, you could say another new test mode.
-----------------------------------------------------------------------------------
Problem Description:
My Lenovo Model 81NC000aus is now about 6 years old. Certainly not too old to retire. Yet, this BSOD was quite frequently nailing me. The Event View showed it (See Event Viewer below). However, each time the Minidump failed to initialize (also included in Event Viewer documentation below). I missed information on the actual screen when BSOD happened. It's small and the extreme bottom. Thus, I ran after the Event's BUGCHECK CODE 209 with parameters 0,2,0,0xfffff8047ac3c9b3. The 2nd parameter indicates time of IQRL r4, while 4th parameter indicates "Connected standby in progress false, Bugcheck info from EFI false, etc. The Event 41 Task 63 also came with Keywords 703687441 77664(2). Another of my notes was Driver_IRQL_NOT_LESS_OR_EQUAL and DBGCMD in address. I forgot the details of these, but suffice to say it relates to Crash Dump which failed!
---------------------------------------
RESOLVED!
It took a while without the proper dumps and technical details, but here is a summary and then the resolution:
1. BSOD was exier1enced prior to 5/25/2025, but I focused on the 5/25/2025 one at 7:11 PM
2. Had to hold power to get rebooted
3. Event Viewer when back up showed little; The Event 46 Task 63 that “something happened” and system was powered down abnormally.
4. An event re Minidumps failed to initialize immediately followed.
5. And that was it as far as documentation on the failures.
6. Research led to checking all drivers and getting new ones if necessary.
7. Device Manager reported that all drivers were current.
8. However, later found, was that at least 2 different drivers were noted for the Graphics adapter (AMD Radeon Vega 8) when BSOD were happening about 1-2 times every 2 days.. The first was unknown, but was a W10 driver – unknown because Windows replaced it and not done via Device Manager. Thus, nothing was listed for Rollback when the following driver appeared: Windows Update updated that driver on 5/25/2025 to 26.20.14048.2 W10 Graphics Driver. An important message here is NEVER let Windows Update other software like drivers! This version happened to be another W10 driver.
9. Knowing that a Windows 10 driver was working against W11 23H2 updates led me to look for a new driver. But I thought I’d try a Restore to get me back to a stable Winds level. That was catastrophic! My Boot records at a minimum got wiped out and I had to finally resort to a Clean Install of Windows.
10. A Clean boot installed now 24H2 and I had to reinstall all applications and settings.
11. BSOD were prevalent on 24H2 and 23H2 (different KB-updates always installed 2nd Tuesday of the month and the Cumulative Update). All Event Viewer data was lost!
12. I didn’t have to wait long, uninstalled the cumulative at that time, and received the temporary workaround running system.
Now, in early June I went to the AMD support site and found a W11 Graphic Driver for the AMD Radeon Vega 8 ( 31.0.2193.1000 (denoted on AMD as 25.5.1 Adrenalin Driver) I removed the old driver with AMD Utility tool to ensure it was cleanly off, then installed this one. It is a W11 Graphics Driver for my Radeon Vega8. I also reinstalled the Cujulative update I uninstalled that was conflicting with the Graphic Diver.
13. I went further and looked up the 26.20.14048.2 driver that Windows put on and found this from Google AI:A Blue Screen of Death (BSOD) occurring in conjunction with the AMD Display driver "26.20.14048.2" is a known issue, often pointing to a problem with the graphics card driver. This was the icing on the cake!
14. RESOLUTION: Install the latest driver from the AMD website: After removing the old driver, download and install the latest compatible driver from the official AMD website. [31.0.2193.1000 (25.5.1 Adrenalin Driver on AMD site). After I installed this and restored Cumulative update for May, no BSODs for last 4 days. Fingers crossed]. Heed: DON’T LET WINDOWS UPDATES INSTALL DRIVERS!
------------------
Actions and other information:
1. Update all drivers. Unfortunately, Lenovo site does NOT list any updates by my processor model. I found an AMD Graphics driver (Adrenalin 25.5.1) aka 31.0.21024.2004 8/23/2025), downloaded it and installed it on 6/5/25). Unfortunately, I didn't write down the previous driver. Also, Windows Updates claims to have installed Advanced Micro Devices, Inc. - Display - 26.20.14048.2 on 5/25/25. Can't find verification. My Device Manager for Monitors says 10.0.26100.3624. This is designated a Windows 10 update! Was this the Graphic Adapter driver previous to my install? If so, BSOD almost explained - incompatibility between W10 driver and current 24H2 Updates. Is BSOD fixed? Testing began 6/5/25. Following from Google AI search:
A Blue Screen of Death (BSOD) occurring in conjunction with the AMD Display driver "26.20.14048.2" is a known issue, often pointing to a problem with the graphics card driver.
Potential Causes:
Corrupted graphics driver: The graphics driver itself may be corrupted or damaged, leading to instability.
Outdated or incompatible drivers: Outdated or incompatible drivers can lead to conflicts and crashes.
Windows update conflicts: In some cases, Windows updates may introduce bugs that interfere with the AMD driver.
Other software or hardware conflicts: Conflicts with other software, particularly Discord, or hardware issues can also contribute to the problem.
Troubleshooting Steps:
Clean Reinstall of the AMD Graphics Driver: This is a widely recommended solution.
Use Display Driver Uninstaller (DDU): DDU is a free utility that helps completely remove the existing graphics driver in Safe Mode.
Install the latest driver from the AMD website: After removing the old driver, download and install the latest compatible driver from the official AMD website. [31..0.2193.1000 (25.5.1 Adrenalin Driver on AMD site). After I installed this and restored Cumulative update for May, no BSODs sin last 3 days. Fingers crossed]
Alternatively, try a slightly older version: Sometimes, the latest driver may not be as stable, and an older version might resolve the issue.
Use AMD Cleanup Utility: If you're having trouble removing the older driver, the AMD Clean Uninstall Utility can help ensure no residual files remain.
Check for Windows Updates: Ensure your Windows operating system is fully up to date, as updates can sometimes include driver fixes.
Check Reliability Monitor and Event Viewer: These tools can provide more specific details about the error that caused the BSOD.
Disable Hardware Acceleration in Discord (if applicable): If you're experiencing issues while using Discord, try disabling hardware acceleration within the application.
Consider a Clean Windows Reinstall: If other solutions fail, a clean reinstall of Windows can help rule out software conflicts or corruption issues.
**If the issue persists, consider: **
System Scan: Run a full system scan with your antivirus software to rule out malware infections.
Repair .NET Framework: The .NET Framework Repair Tool can help address issues with the framework, which might be related to the problem.
2. Disable memory caching in BIOS (Yes, it is current) - Pending above test (#10
3. Issue stated was Kernel attempted to access page memory while process IRQL was too high. Attempt is pageable (or completely invalid) while executing at/above Dispatch_Level. Need Dump to check KiBugcheck Driver pinicode_string. and debugger cmd. - Pending above test (#1)
Event Viewer:
This is the BSOD - The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331c3b3a-2005-44c2-ac5e-77220c37d6b4}
EventID 41
Version 10
Level 1
Task 63
Opcode 0
Keywords 0x8000400000000002
- TimeCreated
[ SystemTime] 2025-05-31T00:11:12.6390119Z [ 5/30/25 7:11:12 PM]
Eve
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer L2019
- Security
[ UserID] S-1-5-18
- EventData
BugcheckCode 209
BugcheckParameter1 0x10
BugcheckParameter2 0x2
BugcheckParameter3 0x0
BugcheckParameter4 0xfffff8047ac3c9b3
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 0
CsEntryScenarioInstanceId 0
BugcheckInfoFromEFI false
CheckpointStatus 0
CsEntryScenarioInstanceIdV2 0
LongPowerButtonPressDetected false
LidReliability false
InputSuppressionState 0
PowerButtonSuppressionState 0
LidState 1
WHEABootErrorCount 0
Just prior to BSOD: Crash dump initialization failed!
System
- Provider
[ Name] volmgr [ 5/30/25 10:11:45 [Crashed dump initialization failed]
- EventID 46
[ Qualifiers] 49156
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2025-05-31T00:11:12.1815582Z [5/30/25 7:11:12 P.M.]
EventRecordID 3955
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 300
Channel System
Computer L2019
Security
- EventData
\Device\HarddiskVolume3
0000000001000000000000002E0004C0091000000F0000C000000000000000000000000000000000
--------------------------------------------------------------------------------
Binary data:
In Words
0000: 00000000 00000001 00000000 C004002E
0010: 00001009 C000000F 00000000 00000000
0020: 00000000 00000000
In Bytes
0000: 00 00 00 00 01 00 00 00 ........
0008: 00 00 00 00 2E 00 04 C0 .......À
0010: 09 10 00 00 0F 00 00 C0 .......À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 .....…
Just after to BSOD: The previous system shutdown at 2:38:31 PM on 5/30/2025 was unexpected.
System
- Provider
[ Name] EventLog
- EventID 6008
[ Qualifiers] 32768
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2025-05-31T00:11:22.4124167Z [5/30/2025 7:11:22 PM]
EventRecordID 3935
Correlation
- Execution
[ ProcessID] 2916
[ ThreadID] 3036
Channel System
Computer L2019
Security
- EventData
2:38:31 PM
5/30/2025
10
E907050005001E000E0026001F00C201E907050005001E00130026001F00C2013C0000003C000000000000000000000000000000000000000100000000000000
--------------------------------------------------------------------------------
Binary data:
In Words
0000: 000507E9 001E0005 0026000E 01C2001F
0010: 000507E9 001E0005 00260013 01C2001F
0020: 0000003C 0000003C 00000000 00000000
0030: 00000000 00000000 00000001 00000000
In Bytes
0000: E9 07 05 00 05 00 1E 00 é.......
0008: 0E 00 26 00 1F 00 C2 01 ..&...Â.
0010: E9 07 05 00 05 00 1E 00 é.......
0018: 13 00 26 00 1F 00 C2 01 ..&...Â.
0020: 3C 00 00 00 3C 00 00 00 <...<...
0028: 00 00 00 00 00 00 00 00 ........
0030: 00 00 00 00 00 00 00 00 ........
0038: 01 00 00 00 00 00 00 00 ........
SOLUTION:
My new Sandisk 3.0 64GB Flash Drive attached to a 3.0 USB next to the mouse is known and documented to produce noise that interferes with a wireless mouse attached to a USB. Solution is to separate the mouse receiver from the Sandisk. Attaching the Sandisk to the other side of my computer into a USB-C port (dongle required) resolves the problem. A details is that it interferes with the RF Frequency of the mouse receiver (2.4 GHz). Neither the Sandisk nor the mouse receiver's frequencies can be changed, nor the USB ports. Get to live with it.
