Another BSOD...

Hello all. My PC had quite a few BSODs recently and I don't have any idea what could have caused that (IRQL_NOT_LESS_OR_EQUAL error, no additional understandable information in screen). Here are some of WinDbg reports (useless data removed), maybe somebody will have any ideas ...

Report 1:

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: 0000001c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8053f6a9, address which referenced memory

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
unable to get nt!MiSessionPoolStart
unable to get nt!MiSessionPoolEnd
0000001c

CURRENT_IRQL: 2

FAULTING_IP:
nt!MmTrimAllSystemPagableMemory+298a
8053f6a9 ff4b1c dec dword ptr [ebx+0x1c]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 8053f6a9 to 804e0aac

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b8c70a0c 8053f6a9 badb0d00 81ccaec4 00000300 nt!Kei386EoiHelper+0x2883
b8c70a88 80529e45 00000000 e1000000 81ccada0 nt!MmTrimAllSystemPagableMemory+0x298a
b8c70ac0 804eede3 c00006c4 001b1000 00000000 nt!IoSetFileOrigin+0xd713
b8c70b84 804f4beb e1839664 001dcfff 00000000 nt!PsGetThreadTeb+0x2c3
b8c70c30 80503d97 81ccada0 81bf1d00 81ccaed8 nt!PsReturnProcessPagedPoolQuota+0x240
b8c70c68 8058c292 01ccada0 81c39538 00000001 nt!RtlInitializeGenericTableAvl+0xf3a
b8c70cf0 8058c9f2 00000001 b8c70d4c 804e75c2 nt!ExRundownCompleted+0xc
b8c70cfc 804e75c2 81c39538 b8c70d48 b8c70d3c nt!ExRundownCompleted+0x76c
b8c70d4c 804dda0a 00000001 00000000 b8c70d64 nt!KeReadStateTimer+0x9c9
b8c70d64 7c90eb94 badb0d00 0012e7d8 ffffffff nt!KiDeliverApc+0xc09
0012e7f8 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: WRONG_SYMBOLS

Report 2:

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: 0000001c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8053f6a9, address which referenced memory

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
unable to get nt!MiSessionPoolStart
unable to get nt!MiSessionPoolEnd
0000001c

CURRENT_IRQL: 2

FAULTING_IP:
nt!MmTrimAllSystemPagableMemory+298a
8053f6a9 ff4b1c dec dword ptr [ebx+0x1c]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 8053f6a9 to 804e0aac

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b8965a24 8053f6a9 badb0d00 81c9bc04 00000070 nt!Kei386EoiHelper+0x2883
b8965aa0 80529e45 00000000 e1000000 81c9bae0 nt!MmTrimAllSystemPagableMemory+0x298a
b8965ad8 804eede3 c01de6c4 779b1000 00000000 nt!IoSetFileOrigin+0xd713
b8965b9c 804f4beb e172f944 77a12fff 00000000 nt!PsGetThreadTeb+0x2c3
b8965c48 80503d97 81c9bae0 81ce6ba0 81c9bc18 nt!PsReturnProcessPagedPoolQuota+0x240
b8965c80 8058c292 01c9bae0 81d23020 81d23268 nt!RtlInitializeGenericTableAvl+0xf3a
b8965d08 805739b4 00000001 81d23020 00000000 nt!ExRundownCompleted+0xc
b8965d28 8058c631 81d23020 00000001 b8965d64 nt!ObLogSecurityDescriptor+0x53c
b8965d54 804dd99f 00000000 00000001 0012fe48 nt!ExRundownCompleted+0x3ab
b8965d64 7c90eb94 badb0d00 0012fd54 baea154a nt!KiDeliverApc+0xb9e
0012fe48 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: WRONG_SYMBOLS

Report 3:

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: 0000001c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8053f6a9, address which referenced memory

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
unable to get nt!MiSessionPoolStart
unable to get nt!MiSessionPoolEnd
0000001c

CURRENT_IRQL: 2

FAULTING_IP:
nt!MmTrimAllSystemPagableMemory+298a
8053f6a9 ff4b1c dec dword ptr [ebx+0x1c]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 8053f6a9 to 804e0aac

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b8965a24 8053f6a9 badb0d00 81c9bc04 00000070 nt!Kei386EoiHelper+0x2883
b8965aa0 80529e45 00000000 e1000000 81c9bae0 nt!MmTrimAllSystemPagableMemory+0x298a
b8965ad8 804eede3 c01de6c4 779b1000 00000000 nt!IoSetFileOrigin+0xd713
b8965b9c 804f4beb e172f944 77a12fff 00000000 nt!PsGetThreadTeb+0x2c3
b8965c48 80503d97 81c9bae0 81ce6ba0 81c9bc18 nt!PsReturnProcessPagedPoolQuota+0x240
b8965c80 8058c292 01c9bae0 81d23020 81d23268 nt!RtlInitializeGenericTableAvl+0xf3a
b8965d08 805739b4 00000001 81d23020 00000000 nt!ExRundownCompleted+0xc
b8965d28 8058c631 81d23020 00000001 b8965d64 nt!ObLogSecurityDescriptor+0x53c
b8965d54 804dd99f 00000000 00000001 0012fe48 nt!ExRundownCompleted+0x3ab
b8965d64 7c90eb94 badb0d00 0012fd54 baea154a nt!KiDeliverApc+0xb9e
0012fe48 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: WRONG_SYMBOLS

-------------------------------------------------

Any ideas where to look for the problem? I have tested RAM with memtest and MS tool, no problems there... I guess it's one of the drivers, but I never get its name mentioned in BSOD.

 

Have you changed/added ANY hardware/accessories recently? Are you using Automatic updates?

 

Recently - no. Actually, I have been getting BSODs since I installed WinXP (been using Linux before that, no problems). Same happens with Win2k and Win2k3, but no problems in Safe Mode or in Linux, so I guess it's a driver or software I'm using (no antivirus, no firewall, sometimes mIRC, VypressChat and Firefox/Opera) what is causing this. The last BSOD occured when I was exiting VypressChat (it's using UDP protocol to send/receive messages) and BSOD mentioned tcpip.sys --> maybe network driver (a lot of UDP traffic goes in and out, maybe that was too much for the driver...) or bug in VC... Will stop using VypressChat for now to check this.

RAM should be OK, as mentioned above, I have tested it; timings appear to be in order too.

What about Automatic Updates - all updates are installed, including SP2.