Wednesday, February 27, 2013 2:36 PM
One of my servers has been crashing, the following is the bugcheck analysis. I have searched for this particular error but haven't found anything of use.
Any help would be appreciated.
IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: 000000e0, memory referenced Arg2: d000001b, IRQL Arg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 8083d698, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: 000000e0 CURRENT_IRQL: 1b FAULTING_IP: nt!MmCleanProcessAddressSpace+610 8083d698 890a mov dword ptr [edx],ecx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: Idle LAST_CONTROL_TRANSFER: from 8085bf24 to 8083d698 STACK_TEXT: 808a34f0 8085bf24 00000000 ffdffa40 ffdff120 nt!MmCleanProcessAddressSpace+0x610 808a35a8 8083d4bc 00000000 00000000 02b63c9d nt!MiModifiedPageWriterWorker+0x115 808a3600 80839b9f 00000000 0000000e 00000000 nt!KiSignalTimer+0x1b 808a6b40 00000000 808a6b48 808a6b48 808a6b50 nt!CcSetActiveVacb+0x44 STACK_COMMAND: kb FOLLOWUP_IP: nt!MmCleanProcessAddressSpace+610 8083d698 890a mov dword ptr [edx],ecx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MmCleanProcessAddressSpace+610 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 50339f35 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: 0xA_nt!MmCleanProcessAddressSpace+610 BUCKET_ID: 0xA_nt!MmCleanProcessAddressSpace+610 Followup: MachineOwner ---------
Thursday, February 28, 2013 7:50 AMModerator
This usually happens after installing an inappropriate driver. Please check this KB:
- Marked As Answer by Cheers ZHANGMicrosoft Contingent Staff, Moderator Monday, March 04, 2013 5:54 AM
Monday, March 04, 2013 3:17 PMUpdated drivers and I'm waiting too see if it happens again as this does not happen very frequently.