HP EliteBook 840 users are reporting a surge of Blue Screen of Death (BSOD) crashes following recent Windows updates, with stop codes like CRITICAL_PROCESS_DIED, SYSTEM_SERVICE_EXCEPTION, and IRQL_NOT_LESS_OR_EQUAL appearing on screens. The crashes typically occur during boot or shortly after login, rendering business laptops temporarily unusable and disrupting workflows.

These BSOD incidents follow Windows Update cycles, particularly after cumulative updates or driver patches. Users describe the EliteBook 840 freezing, displaying the blue error screen, then automatically restarting—sometimes entering a reboot loop that prevents normal system access. The timing strongly suggests update-related conflicts rather than widespread hardware failure.

Understanding the Stop Codes

Different stop codes point to different underlying issues. CRITICAL_PROCESS_DIED indicates Windows core processes are failing, often due to corrupted system files or incompatible drivers. SYSTEM_SERVICE_EXCEPTION suggests problems with system services or their dependencies. IRQL_NOT_LESS_OR_EQUAL typically points to driver conflicts, especially with storage, network, or security drivers.

HP EliteBook 840 models affected span multiple generations, from G5 to current G10 models, though G7 and G8 units appear most frequently in reports. Both Windows 10 and Windows 11 installations are experiencing these crashes, with no clear pattern based on operating system version alone.

Immediate Access: Safe Mode and Recovery Options

When facing a boot-looping BSOD, accessing Safe Mode is the critical first step. For EliteBook 840s, interrupt the automatic restart by holding the power button during boot. After three failed boot attempts, Windows should automatically launch the Automatic Repair environment.

From there, select Troubleshoot > Advanced Options > Startup Settings > Restart. After the restart, press 4 or F4 for Safe Mode, or 5 or F5 for Safe Mode with Networking. Safe Mode loads only essential drivers and services, often bypassing the problematic component causing the BSOD.

If Automatic Repair doesn't trigger, use installation media. Boot from a Windows USB drive, select your language, then click "Repair your computer" instead of "Install now." This provides access to the same recovery tools.

Driver Conflicts: The Primary Culprit

Driver incompatibility emerges as the most common cause. Windows Update sometimes installs generic or newer drivers that conflict with HP's customized hardware implementation. The EliteBook 840's management engine, Thunderbolt controllers, and security features seem particularly vulnerable.

In Safe Mode, open Device Manager and check for warning icons. Pay special attention to display adapters, network controllers, storage controllers, and any HP-specific devices. Right-click problematic devices and select "Properties" to view driver details.

Roll back drivers through Device Manager by selecting the driver tab and clicking "Roll Back Driver" if available. If not, manually download the previous driver version from HP's support site. Use your EliteBook's exact model number (found on the bottom label) to ensure compatibility.

For critical systems like storage controllers, avoid using Windows Update for driver installation. Instead, download drivers directly from HP and install them manually. Disable automatic driver updates temporarily by going to System Properties > Hardware > Device Installation Settings and selecting "No."

System File Repair: SFC and DISM Commands

Corrupted system files frequently cause BSODs after updates. Windows includes built-in tools to repair these files without reinstalling the entire operating system.

Run System File Checker (SFC) first. In Safe Mode with Command Prompt (or PowerShell as Administrator), type sfc /scannow and press Enter. This scans all protected system files and replaces corrupted versions with cached copies. The process typically takes 10-15 minutes on an EliteBook 840.

If SFC reports it cannot repair some files, use Deployment Image Servicing and Management (DISM). Run DISM /Online /Cleanup-Image /RestoreHealth to repair the Windows image that SFC uses as a source. This command requires an internet connection in Safe Mode with Networking.

After DISM completes, run SFC again. Many users report this two-step process resolves BSODs caused by update corruption. Document any specific files SFC reports repairing—this can help identify patterns across affected systems.

Update Management and Prevention

Preventing future BSOD incidents requires strategic update management. Delay major Windows updates by 7-10 days to allow early adopters to identify issues. Use Group Policy or registry edits to configure update deferral periods.

Create system restore points before installing any updates. While Windows creates automatic restore points, manual ones provide additional insurance. In System Properties > System Protection, select your C: drive and click "Create." Name it with the update KB number for easy identification.

Consider using Windows Update pause features. Windows 10 and 11 allow pausing updates for up to 35 days, providing a buffer while HP and Microsoft address compatibility issues. For enterprise deployments, use Windows Update for Business or WSUS to control update rollout.

Monitor HP's support announcements. The company typically releases driver updates and BIOS revisions addressing compatibility issues within weeks of major Windows updates. Subscribe to update notifications for your specific EliteBook 840 model.

When Hardware Might Actually Be the Problem

While most post-update BSODs stem from software conflicts, some might reveal underlying hardware issues. Memory problems often surface as BSODs during system stress like updates. Run Windows Memory Diagnostic from the recovery environment or use third-party tools like MemTest86.

Storage drive failures can also cause similar symptoms. Check drive health using HP's built-in diagnostics (press F2 during boot) or tools like CrystalDiskInfo. EliteBook 840s with NVMe drives should particularly monitor drive temperature and health statistics.

If BSODs persist after all software troubleshooting, consider hardware diagnostics. HP's built-in UEFI diagnostics test memory, storage, and other components. For out-of-warranty units, professional diagnosis might be necessary to rule out motherboard or component failure.

Enterprise Considerations for IT Departments

For organizations deploying EliteBook 840s, these BSOD incidents highlight update management challenges. Implement phased update rollouts, testing on pilot groups before company-wide deployment. Maintain a library of known-good driver versions for quick rollback when issues arise.

Configure BitLocker recovery key access before troubleshooting. Some BSOD fixes require booting from external media, which can trigger BitLocker recovery on encrypted EliteBooks. Ensure recovery keys are accessible through Azure AD, Microsoft accounts, or printed documentation.

Document successful resolution procedures. When you find a working fix for your specific EliteBook 840 configuration, document the exact steps, driver versions, and update KB numbers. This creates institutional knowledge that speeds future troubleshooting.

Consider driver management solutions. Tools like HP Image Assistant or enterprise management systems can standardize driver versions across fleets, reducing compatibility issues from Windows Update's variable driver selection.

The Bigger Picture: Windows Update Quality Control

These EliteBook 840 BSOD incidents reflect broader Windows Update quality challenges. Microsoft's accelerated update cadence sometimes outpaces hardware manufacturer testing cycles. HP typically certifies drivers and BIOS updates for specific Windows builds, but Windows Update may deliver newer, uncertified versions.

The situation highlights the tension between security and stability. Critical security updates must deploy quickly, but compatibility testing takes time. For business devices like the EliteBook 840, where reliability is paramount, this creates difficult trade-offs.

Users should report BSODs through Windows Feedback Hub, including stop codes and update versions. These reports help Microsoft identify patterns and work with partners like HP on fixes. The more detailed the report, the faster compatibility updates can be developed.

Looking forward, both Microsoft and HP need to improve their coordination around update testing. Hardware manufacturers should have earlier access to upcoming Windows changes, while Microsoft needs better mechanisms to prevent incompatible drivers from deploying through Windows Update. Until then, EliteBook 840 users must remain vigilant with update management and maintain robust recovery options.