Several BSOD occurrences - - IRQL, KMODE and related issues?
Several BSOD occurrences - - IRQL, KMODE and related issues?
Hello everyone,
I've encountered various BSODs recently and need assistance in understanding the issue. My system was self-built in April 2023 and has been operating smoothly until recently. No hardware changes have been made. Windows updates and NVIDIA drivers are consistently current.
BSODs I've experienced:
IRQL_NOT_LESS_OR_EQUAL
KMODE_EXCEPTION_NOT_HANDLED
SYSTEM_SERVICE_EXCEPTION
related to WATCHDOG
"Boot failure detected" when waking from sleep mode. This occurred only once. After searching, I selected "Load optimized defaults and boot," which resolved the problem.
I now experience one of the first three BSODs randomly, every few hours. In BlueScreenView, all entries show ntoskrnl.exe with an unusual code at the top, but no other errors. The WATCHDOG error appeared twice during the initial Windows installation from a USB drive, which is why I haven’t reinstalled Windows yet. I’m hesitant to try again, so I’m attempting a fix without a full reinstall. Previously, when BSODs appeared, simply reinstalling Windows was my usual solution, as it consistently resolved the issues. I keep my PC lightweight, storing important data in the cloud and using few apps.
So far, I’ve:
- Reinstalled Windows via USB, encountering WATCHDOG errors before the installation began
- Run MemTest86 – No Errors
- Windows System File Checker – No Errors / Corrupted Files
- Windows Memory Diagnostic – No Errors
- Used Gigabyte Control Center to update all motherboard drivers and BIOS
After each step, I waited to see if the BSOD would return, but it always did.
Additional details:
CPU: Intel Core i7 13700
CPU cooler: ENDORFY Fortis 5 Dual Fan
Motherboard: Gigabyte Z790 GAMING X
RAM: Slots 2+4 – G.Skill Ripjaws S5 DDR5-6000 (32GB, CL32, Dual Channel, 2 units) – Intel XMP
Storage: 2TB Kingston KC3000 NVME M.2 SSD
GPU: 24GB Palit GeForce RTX 4090 GameRock
Power supply: be quiet! Pure Power 12 M 850W – 80 PLUS Gold
Chassis: be quiet! Pure Base 500DX Midi Tower
OS: Windows 11 Home 24H2
Monitor: Displayport – LG 43UD79-B, 107.98 cm (42.51 inches), UHD 4K IPS
HDMI: BenQ XL2411Z (24-inch)
All components were purchased new in late April 2023 and assembled by me.
I’ve uploaded a zip from the Synapsis File Collection App containing the last 10 minidumps. Two occurred during the post creation, but others were lost because Windows only saved five at a time, and by then several had vanished. The WATCHDOG errors didn’t generate any files. If you have anything else that could help, please let me know.
Thank you for your support.
Update your post with complete hardware details and operating system information.
Power supply: make, model, wattage, age, condition (original, new, used, refurbished)?
Disk drive(s): make, model, capacity, current usage?
All connected peripherals?
Review Reliability History/Monitor or Event Viewer for any error codes, warnings, or alerts.
Ensure all critical data is securely backed up in at least two separate locations away from the system.
Confirm backups are both recoverable and readable.
Proceed by powering down, unplugging, and opening the case.
Remove dust and debris, then inspect every connection, card, RAM, jumpers, and case firmly.
Utilize a bright flashlight to detect any signs of damage.
I would visit Gigabyte and search for the GIGABYTE IT5701/5702 RGB lighting controller firmware upgrade package. It seems to clash with the Cosair software.
https://www.gigabyte.com/Motherboard/Z79...dl-utility
Machine details:
BIOS Version: F12
BIOS Starting Address Segment: f000
BIOS Release Date: 01/07/2025
Manufacturer: Gigabyte Technology Co., Ltd.
Product: Z790 GAMING X
Processor: Intel® Corporation, ID 71060b00fffbebbf
Version: 13th Gen Intel® Core™ i7-13700
Voltage: 88h - 0.8V
External Clock: 100MHz
Max Speed: 5200MHz
Current Speed: 2079MHz
There was a bug check for kernel stack corruption, and the system is running Corsair Service.
=== Bug check due to stack corruption in kernel ===
Bug check triggered by stack corruption in kernel
=== Bug check due to stack corruption ===
Running iCUE.exe
I have entered my system specifications in the initial post.
Reliability History / Event Viewer displays BSOD events but I can't extract any useful information from them.
All crucial data is backed up. If something fails, I'm prepared for a clean Windows reinstall. I purchased a new USB stick and created a bootable media that also works.
I opened the case and cleaned it with compressed air. I inspected all connections but found no signs of physical issues.
There are many concerning reports about people attempting to install the RGB lighting firmware update. I don't mind RGB in my case (the case window is next to the wall, the RGB versions were just cheaper when I bought the parts), but I'm concerned about installing it. It seems to be installed via Flash.bat?
I performed a clean uninstall of the NVIDIA driver using the DDU tool in safe mode, and there was a guide on that page somewhere. Then I reinstalled the latest driver.
How do I remove gdrv3.sys?
I've experienced two more IRQL_NOT_LESS_OR_EQUAL errors a few days ago, which were added to the upload folder.
I would simply download microsoft autoruns64.exe, run it with admin privileges, locate the gdrv3.sys driver and remove its entry or deselect the driver name so it won’t load (it’s easy to re-add if needed).
Alternatively, I’d update the firmware and disable the driver. You don’t want the firmware reacting to events specific to your Corsair device, as this could lead to stack overflows and memory corruption.
The firmware update appears to be functioning properly with no problems detected. I'll wait a few days and then check again, reporting any further issues.
Is there another BSOD with IRQL_NOT_LESS_OR_EQUAL occurring recently, and have you uploaded the latest minidump to that folder? The PC was just idling while I wasn’t around. Would a clean Windows install be more effective than investigating the cause of this issue?
last bugcheck showed chrome running and instructing the file system to write a file. the file system attempted but encountered a bugcheck. usually, issues should be found in the data path. try disabling any chrome extensions, updating network and filter drivers (such as malware scanners), and checking drive firmware. i’ll review it quickly, but proper debugging might require a kernel dump for this issue.