lilimali said:
Hi !
After reading this thread, it seems I might finally get rid of the problem that's been bothering me for a while now.
At first I encountered frequent reboots which I thought might come from an overheating problem. It happens generally during hot days and when I let the computer open things seem to improve...
But recently I've been getting a blue screen with the famous "driver_irql_not_less_or_equal" quite frequently.
My log says :
The system event of COM+ has detected a bad return code while its internal processing. HRESULT is C0000005 from line 44 of d:\qxp_slp\com\com1x\src\events\tier1\eventsystemobj.cpp. Contact Microsoft tech support to report the error.
If anyone could help me decrypt my minidumps that would help greatly !! I could at least make some progress in troubleshooting this.
Thanks in advance for your help,
ma
Hi lilimali,
Faulty ram is the culprit and aslo you have to check the CPU to make sure that it is overheat
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: 9dc0287a, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804edb18, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 9dc0287a
CURRENT_IRQL: 2
FAULTING_IP:
nt!ExRemoveHeadNBQueue+63
804edb18 8b5108 mov edx,[ecx+0x8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from 8054a18a to 804edb18
STACK_TEXT:
a21df83c 8054a18a 82b16eb5 a21df854 00000001 nt!ExRemoveHeadNBQueue+0x63
a21df85c 804edc67 00000001 00000000 a21dfa68 nt!MiReserveSystemPtes+0x3a
a21df890 f87e7e1e 823bf8e4 00000000 00000001 nt!MmMapLockedPagesSpecifyCache+0x101
a21df8bc a2eff126 825a7000 00000000 00000050 TDI!TdiCopyBufferToMdl+0x48
a21df8e4 a2effc05 823bf8c8 825a7000 00000050 tcpip!CopyFlatToNdis+0x23
a21dfb40 a2effa15 8293bec0 0093be50 a21dfae4 tcpip!TdiQueryInformationEx+0x116
a21dfbe0 a2eff03c 8293be50 8293bec0 8293bec0 tcpip!TCPQueryInformationEx+0x1bf
a21dfbfc a2efeff4 8293be50 8293bec0 82717758 tcpip!TCPDispatchDeviceControl+0x129
a21dfc34 804e37f7 8279abc0 8293be50 806ee2d0 tcpip!TCPDispatch+0x127
a21dfc44 8056a101 8293bec0 826da450 8293be50 nt!IopfCallDriver+0x31
a21dfc58 80579a8a 8279abc0 8293be50 826da450 nt!IopSynchronousServiceTail+0x60
a21dfd00 8057bfa5 000004b4 00000000 00000000 nt!IopXxxControlFile+0x611
a21dfd34 804de7ec 000004b4 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
a21dfd34 7c91eb94 000004b4 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0173f52c 00000000 00000000 00000000 00000000 0x7c91eb94
FOLLOWUP_IP:
TDI!TdiCopyBufferToMdl+48
f87e7e1e 3bc6 cmp eax,esi
SYMBOL_STACK_INDEX: 3
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: TDI!TdiCopyBufferToMdl+48
MODULE_NAME: TDI
IMAGE_NAME: TDI.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 41107d33
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0xA_TDI!TdiCopyBufferToMdl+48
BUCKET_ID: 0xA_TDI!TdiCopyBufferToMdl+48