📎 AI Summary:
The thread discusses a Windows 8 crash caused by the DRIVER_IRQL_NOT_LESS_OR_EQUAL error, with the bugcheck analysis pointing to the network driver e22w8x64.sys as the likely culprit. The responder explains that this error usually involves drivers using improper addresses and suggests reinstalling the network driver, possibly with security features disabled, and recommends removing third-party antivirus software to resolve ongoing BSODs. Overall, the advice aims to troubleshoot and address driver conflicts to fix the crash.
The thread discusses a Windows 8 crash caused by the DRIVER_IRQL_NOT_LESS_OR_EQUAL error, with the bugcheck analysis pointing to the network driver e22w8x64.sys as the likely culprit. The responder explains that this error usually involves drivers using improper addresses and suggests reinstalling the network driver, possibly with security features disabled, and recommends removing third-party antivirus software to resolve ongoing BSODs. Overall, the advice aims to troubleshoot and address driver conflicts to fix the crash.
Solution
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {28, 2, 0, fffff88001aaef6f}
*** WARNING: Unable to verify timestamp for e22w8x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e22w8x64.sys
Probably caused by : e22w8x64.sys ( e22w8x64+7046 )
Followup: MachineOwner
the bugcheck D1...
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,163
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {28, 2, 0, fffff88001aaef6f}
*** WARNING: Unable to verify timestamp for e22w8x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e22w8x64.sys
Probably caused by : e22w8x64.sys ( e22w8x64+7046 )
Followup: MachineOwner
the bugcheck D1 means a driver or drivers is using an improper addresses.
The probable cause 'e22w8x64.sys' relates to your network driver. As your probably aware laptops must use the drivers supplied by the manufacturer with the only exception being the graphic driver.
Your systems driver page is here:
Link Removed
I know from personal experience (I have the same network chip) that this driver works better (uninstalling and installing) with the security disabled.
I did spot a possible conflict:
avipbb.sys Mon Oct 17 10:01:27 2016: Alvira AV suite
BAPIDRV64.sys Sat Oct 22 04:12:02 2016: Part of 360 Anti Virus
If the bsod continues then remove the AV suites and just run on Defender.