DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory
Jer-Cedar19.09.2008 01:14 This problem has been ongoing for over 2 months now. Have an open case w/Kaspersky Support, have submitted several crash dumps (both mini and full), but still no answers from KL Support. Anyone else experiencing BSoD's at random? I have over 25% of my nodes with this problem. All are running 6.0.3.837 release. All running XP Pro w/SP-3. All are related to klim5.sys or the LAN NIC drivers. Nothing specific causes the crash dump reboot - in fact some are crashing in the middle of the night when sitting idle waiting for a user logon. Others are crashing during the day with applications open. The problem is very random, but the crash dumps always point toward a Kaspersky issue. Also, none of these systems have Blue Screened when Kaspersky is exited or uninstalled. Kaspersky has been running on the affected systems for 14 months - problem has only appeared in the past 2 months or since the May 28th release of updates.
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: c:\windows\System32; c:\windows\system\System32; http://www.alexander.com/SymServe Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 2600.xpsp.080413-2111 Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0 Debug session time: Thu Sep 18 16:54:17.896 2008 (GMT-5) System Uptime: 1 days 12:53:16.656 Loading Kernel Symbols ................................................................................ ................................................................................. ...... Loading User Symbols Loading unloaded module list ........................................... ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {0, 2, 0, 0}
Unable to load image klim5.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for klim5.sys *** ERROR: Module load completed but symbols could not be loaded for klim5.sys *** WARNING: Unable to verify timestamp for e1e5132.sys *** ERROR: Module load completed but symbols could not be loaded for e1e5132.sys Probably caused by : klim5.sys ( klim5+18ad )
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 00000000, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 00000000, address which referenced memory
