Originally Posted by
MrChris-
This error can be caused by a driver. Driver, as a broad term, can definitely include both Microsoft Antispyware's low level hooks, and an antivirus.
I think I'd try the broad areas that KB article suggests--update drivers for hardware--maybe roll them back for any newly installed hardware, or remove the hardware temporarily.
Simplify the software involved--maybe remove both antivirus and Microsoft Antispyware for testing. See if you can get to a point where the system is stable and doesn't crash.
The memory addresses in the crash message don't tell me anything, although occasionally there will be a KB article searchable using more than just the first one--you might try searching on 0x0000000A and checking all the relevant articles to see if the more precise particulars match your message any better.
A memory dump, and analysis of that using debugging tools, is really the way to get at this. I've done this once or twice myself, but its an art.
Bookmarks