I'm mearly suggesting that it might not be the anti-virus scanner, if not it would seem the problem has been fixed but just happen less offen more randomly as either it's scanning memory causing the issue or conflicting (disk intensive applications such as antivirus software will trigger it). Disabling this makes it harder to solve as they may be triggered in association with some other event.
I know Kaspersky Internet Security ver 9.0.0.736 is fully compatible with the offical version of Windows 7, as it was designed and released for it. Rather than replacing it completely, I believe using the repair option would be a better option.
Which leads me to believe it's hardware like the memory or motherboard, a conflict or incompatible drivers.
This Stop message is typically caused by incompatible or faulty hardware or software. IRQL stands for Interrupt Request Level. An IRQL "defines the hardware priority at which a processor operates at any given time".
It would be best to first check - a faulty device driver, system service, or firmware? In the worst case, failing or defective hardware. It doesn't have to be the memory, could be the hard drive, dying motherboards, or failing power supplies, etc.
If it started after updates, the problem could be caused by an system service, incompatible driver, virus scanner, or backup. I however don't think it's this at all, because you said you had the same problem with Windows XP?
Quite often, stop errors are associated with dud RAM. That includes main memory, video and CPU cache memory. I suggest you do a full test of all if you haven't already.
Since you have already ruled out the main memory as okay.
The error's parameter (hexadecimal) refers to a specific issue:
• Parameter 1 - An address that was referenced incorrectly.
• Parameter 2 - An IRQL that was required to access the memory.
• Parameter 3 - The type of access, where 0 is a read operation and 1 is a write operation.
• Parameter 4 - The address of the instruction that referenced memory in parameter 1.
0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error.
0x0000000A IRQL_NOT_LESS_OR_EQUAL 0xA
Drivers are using improper memory addresses. Check for buggy device drivers.
If it was me...
Memory would be the first bet, you want to fully rule it out as it causes random problems -
1. Perform overall RAM Error Checking, maybe start with the boot tool:
http://oca.microsoft.com/en/windiag.aspCorrupt disks and viruses can cause all kinds of stop errors -
2. Perform Malware checking. This is more a safety check to do first. It also shows up corrupt or areas which need addressing, such as scanning file blah makes it suddenly crash.
3. Ensure your anti-virus scanner is working correctly, do a repair if needed. Don't remove it.
4. Malware like the Conflictor virus attempt to disable the anti-virus and creates crashes, Kaspersky has self-protection, but Windows Defender, security websites, etc will be blocked. It stays in a breeding till the 1st April, if you started having problems around that time it might be something to be aware of. It won't let you install any protection and will attempt to disable what you have.
5. Perform disk error checking. Your Windows page file might be corrupting.
Hiberation is a issue with everything Microsoft, this happens when you have a smart motherboard BIOS which also has power saving features and they both attempt to hiberate devices together:
6. Disable both power management on Windows and in your BIOS to check.
Conflicts between other devices/services -
7. Does it happen when you plug in a device, Kaspersky will come along and scan, it triggers the USB port.
8. Check for conflicting services, like two scanners running in background at the same time.
Buggy device drivers -
9. Incompatible device drivers need replacing.
10. Ensure drivers and your BIOS are the latest versions. The BIOS is important as it supports later hardware.
Overheating damage
11. If you are over-clocking your motherboard or graphic card, disable it for now.
Graphic cards
12. Try updating or downgrading your graphic card drivers or just using a standard Microsoft VGA driver for testing. You can also get bench/stable testing tools for the graphic card.
Hardware
13. Check Motherboard and hard drives for faults.
