1. Use Driver Verifier to Detect Driver Issues
- Run verifier from Command Prompt (Admin)
- Select “Create standard settings” → Automatically select all drivers
- Reboot and let BSOD trigger if necessary
- Use WinDbg or BlueScreenView to analyse the memory dump
- After debugging, disable Verifier:
verifier /reset
2. Update Kernel-Level Drivers and Software
- Go to Device Manager
- Update drivers for Network Adapters, System Devices, and Security Devices
- Revert recent updates if BSOD began after installation
- Make sure all endpoint protection tools are fully compatible with your Windows version
3. Uninstall Recently Installed Security Tools
- Navigate to Control Panel → Programs → Uninstall a program
- Remove any recently added antivirus or identity monitoring software
- Restart and test system stability
- Use Microsoft’s Windows Security temporarily to isolate the issue
4. Run System File Checker and DISM Repair
- Open Command Prompt as Admin
- Run:
sfc /scannow
- Follow with:
DISM /Online /Cleanup-Image /RestoreHealth
- These tools repair corrupt system files related to user authentication and session handling
5. Perform a Clean Boot to Identify Conflicts
- Type msconfig in Run (Win + R)
- Under Services, check “Hide all Microsoft services” → Click Disable all
- Go to Startup tab, open Task Manager → Disable all items
- Restart the system and check if the BSOD still occurs
6. Restore to a Previous Stable State
- Open Control Panel → Recovery → Open System Restore
- Select a restore point before the appearance of the BSOD
- Let the system roll back to that configuration
- This helps revert faulty registry or session handling changes
7. Verify Domain Session Policies (if domain-connected)
- Ensure domain logon policies, session impersonation scripts, and group policies are up-to-date and not referencing stale tokens
- Check Event Viewer logs under Security for failed session authentication attempts