Solved DRIVER_IRQL_NOT_LESS_OR_EQUAL and KMODE_EXCEPTION_NOT_HANDLED

[ESL]

In the last three days, I have gotten these two BSODs. Logs are attached.

Jim

 

[koolkat77]

Hello.

Please remove Kaspersky Antivirus and use Microsoft Security Essentials for the time being.

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other internet security software. Malwarebytes is a great combo to MSE. They are free and lightweight.

Also uninstall your existing Antivirus software before you install MSE.

http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

 Clean boot

• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

• How to Change, Add, or Remove Startup Programs in Windows 7

Please uninstall Daemon Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7.

 SPTD Removal:

• Uninstall the software using Add/Remove Programs.
• Reboot the system.
• Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.
• DuplexSecure - Downloads

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Run Disk Check on your Hard Drive for file system errors and bad sectors on it.

 Hard Drive Diagnostics

• Double click and open my computer.
• Right click on desired drive and hit properties.
• Click on tools tab and Check now.

Read complete instructions on the tutorial: http://www.sevenforums.com/tutorials/433-disk-check.html

Other Tests:

 

• Upload a screenshot of your hard disk using Crystal Disk Info.
• Make a hard drive test from the hard drive manufacturers website.
• Test your Hard Drive with SeaTools.

 

[ESL]

Kaspersky was indeed the cause of this; they are working on a patch. A Kaspersky driver named KLIM 6 was causing the issue.