Back to All Scenarios
PASSEDserver / windows_bsod_irql
Blue Screen IRQL_NOT_LESS_OR_EQUAL
A production Windows Server experiences repeated Blue Screen of Death (BSOD) with IRQL_NOT_LESS_OR_EQUAL stop code, generating core dumps. The server crashes every 10-15 minutes after boot, caused by a faulty network driver update.
Pattern
PROCESS_CRASH_LOOP
Severity
CRITICAL
Confidence
92%
Remediation
Remote Hands
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | PROCESS_CRASH_LOOP | PROCESS_CRASH_LOOP | |
| Severity Assessment | CRITICAL | CRITICAL | |
| Incident Correlation | Yes | 21 linked | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Remote Hands — Corax contacts on-site support via call, email, or API |
Scenario Conditions
Windows Server 2019 application server. Intel I350 NIC driver updated to version 26.8. Driver accesses paged memory at elevated IRQL. Core dump generated on each crash. 4 critical services hosted on this server.
Injected Error Messages (2)
Windows Server app02 BSOD IRQL_NOT_LESS_OR_EQUAL — core dump generated at C:\Windows\MEMORY.DMP, stop code 0x0000000A, faulting module: e1i65x64.sys (Intel NIC driver), server crashes every 10-15 minutes after reboot, core dump analysis shows driver accessing paged memory at dispatch level
Application health check failing — server app02 producing repeated core dump files, BSOD crash every 10 minutes, all hosted services unavailable during crash recovery cycles
Neural Engine Root Cause Analysis
The Windows server app02.corp.local is experiencing recurring Blue Screen of Death (BSOD) crashes caused by a faulty Intel network interface card driver (e1i65x64.sys). The driver is improperly accessing paged memory at dispatch level (IRQL), which is a critical kernel-level violation causing stop code 0x0000000A. The crash-reboot cycle every 10-15 minutes indicates a consistent driver initialization or operation failure that triggers the same memory access violation repeatedly.
Remediation Plan
1. Immediately disable the faulty Intel NIC driver to prevent continuous crashes 2. Download and install the latest Intel network driver from Intel's support site or Windows Update 3. If driver update fails, rollback to a previous known-good driver version 4. Test network connectivity after driver replacement 5. Monitor system stability for 30+ minutes to ensure crash loop is resolved 6. Consider hardware replacement if driver issues persist
Tested: 2026-03-30Monitors: 2 | Incidents: 2Test ID: cmncjxkno05mvobqeyoumdkp1