Blue screeny w XP SP3 - ciąg dalszy...

Witam.

Poprzedni temat umarł, minęło kilka dni, zaczynało mi się nawet
wydawać, że przepinanie kabelków pomogło i komputer zaczął działać
poprawnie, przeżył nawet około 6 dni bez BSOD-a...

...ale nic bardziej mylnego. Dziś był kolejny blue screen,
kompletnie nie mam już pomysłów co zrobić, cholera totalna
mnie bierze.

POMOCY... :/

I jeszcze wklejam to, co wypluł debugger:

***************************************************************
* *
* Bugcheck Analysis *
* *
***************************************************************

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: 7fffffff, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 7fffffff, address which referenced memory

Debugging Details:
------------------
READ_ADDRESS: 7fffffff

CURRENT_IRQL: 2

FAULTING_IP:
+fc
7fffffff ?? ???

PROCESS_NAME: uTorrent.exe

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from b4e3b7d4 to 7fffffff

FAILED_INSTRUCTION_ADDRESS:
+fc
7fffffff ?? ???

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b47f582c b4e3b7d4 89cfb6c4 0300000a b4e5bb06 0x7fffffff
b47f5874 b4e40e97 89cfb6a8 89591008 00000000
ipnat!NatMappingAttachEditor+0x74
b47f5898 b4e4f4a6 00004006 0600bb06 b47f58e8 ipnat!NatCreateMapping+0x3ad
b47f591c b4e4fe4c 00000000 00000000 00005a76 ipnat!NatpSendPacket+0x532
b47f5990 b4e8b2b9 b47f5a44 00000000 b47f59d4 ipnat!NatTranslatePacket+0x770
b47f5ad0 b4e94934 b4ec9b98 00000000 897a3020 tcpip!IPTransmit+0x16f2
b47f5b24 b4e94500 898a05b4 00000000 89b8c0b8 tcpip!SendSYN+0x28d
b47f5b68 b4e946ce 187f5b8c 00000001 00000000 tcpip!TdiConnect+0x3ab
b47f5ba4 b4e8e7a0 8a7fba38 8a7fbaf0 8a7fba38 tcpip!TCPConnect+0xa8
b47f5bc0 804ef19f 89d86900 8a7fba38 897482ec
tcpip!TCPDispatchInternalDeviceControl+0x13f
b47f5bd0 b4e1bec4 00012007 b4e1bc55 8a7fba38 nt!IopfCallDriver+0x31
b47f5c30 b4e232d7 895770f8 89d39a90 b47f5c64 afd!AfdConnect+0x3a8
b47f5c40 804ef19f 89d03030 8a7fba38 806e6410
afd!AfdDispatchDeviceControl+0x53
b47f5c50 8057f982 8a7fbb14 895770f8 8a7fba38 nt!IopfCallDriver+0x31
b47f5c64 805807f7 89d03030 8a7fba38 895770f8
nt!IopSynchronousServiceTail+0x70
b47f5d00 80579274 00000464 00000000 00000000 nt!IopXxxControlFile+0x5c5
b47f5d34 8054162c 00000464 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
b47f5d34 7c90e514 00000464 00000000 00000000 nt!KiFastCallEntry+0xfc
0182fc54 00000000 00000000 00000000 00000000 0x7c90e514

STACK_COMMAND: kb

FOLLOWUP_IP:
ipnat!NatMappingAttachEditor+74
b4e3b7d4 897770 mov dword ptr [edi+70h],esi

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: ipnat!NatMappingAttachEditor+74

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ipnat

IMAGE_NAME: ipnat.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48025786

FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_ipnat!NatMappingAttachEditor+74

BUCKET_ID: 0xD1_CODE_AV_BAD_IP_ipnat!NatMappingAttachEditor+74

Followup: MachineOwner
==========================================================
Received on Wed Jul 8 19:35:04 2009