Permabanned
- Joined
- 15 Sep 2010
- Posts
- 260
Lately i've been having some blue screens on my PC / Vista 64, i had one about a month ago but have had 3 this week, all with the same error codes. I've done a bit of googling but cant seem to find out what the problem is so i'm hoping some of you might be able to help.
It happens when i'm watching movies/tv etc through VLC media player and downloading at the same time with Downloadthemall firefox addon and it never seems to happen when playing games, video encoding etc.
Here's the BC codes :
BCCode: 44
BCP1: FFFFFA80058ADBD0
BCP2: 0000000000000E7A
BCP3: 0000000000000000
BCP4: 0000000000000000
I can't seem to open the .dmp file though
Edit - Ok with some faffing around i figured out i had to download the SDK and finally got it to generate info, here's some of it.
It looks like it's my network card driver? I've just tried uninstalling it and installing the latest version and i guess i'll need to wait and see if it happens again. Not sure if there's anything else i should have done to make sure the 2 problem ones were completely cleaned out other than run ccleaner between uninstall and install as ccleaner didn't find anything to do with them anyway.
It happens when i'm watching movies/tv etc through VLC media player and downloading at the same time with Downloadthemall firefox addon and it never seems to happen when playing games, video encoding etc.
Here's the BC codes :
BCCode: 44
BCP1: FFFFFA80058ADBD0
BCP2: 0000000000000E7A
BCP3: 0000000000000000
BCP4: 0000000000000000
I can't seem to open the .dmp file though
Edit - Ok with some faffing around i figured out i had to download the SDK and finally got it to generate info, here's some of it.
Code:
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
IRP_ADDRESS: fffffa80058adbd0
FOLLOWUP_IP:
tcpip!TcpSatisfyReceiveRequests+461
fffffa60`0103e2d1 4c8b15f8921100 mov r10,qword ptr [tcpip!TcpInetTransport+0x310 (fffffa60`011575d0)]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x44
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff8000206ce7f to fffff800020bc4d0
STACK_TEXT:
fffff800`03823708 fffff800`0206ce7f : 00000000`00000044 fffffa80`058adbd0 00000000`00000e7a 00000000`00000000 : nt!KeBugCheckEx
fffff800`03823710 fffffa60`0103e2d1 : fffffa80`06989110 fffff800`03823802 fffff800`03823880 fffff800`038238a8 : nt! ?? ::FNODOBFM::`string'+0x2832c
fffff800`038237c0 fffffa60`01057d66 : fffffa80`06989110 fffffa80`07662600 fffffa80`067d29d8 fffff800`03823ba0 : tcpip!TcpSatisfyReceiveRequests+0x461
fffff800`03823a20 fffffa60`010562ce : fffffa80`00000001 fffffa80`06989110 00000000`00000002 fffff800`03823ba8 : tcpip!TcpDeliverDataToClient+0xd6
fffff800`03823b10 fffffa60`0105ca05 : fffffa80`04b68030 fffff800`020b4d56 fffffa80`04b68030 fffffa80`04b68030 : tcpip!TcpDeliverReceive+0x6e
fffff800`03823b90 fffffa60`0105c3ae : 00000000`00000000 fffffa80`067d2890 fffffa80`067d2890 fffffa80`056b1130 : tcpip!TcpTcbFastDatagram+0x1c5
fffff800`03823c60 fffffa60`010567d9 : fffffa80`047bf4c0 fffffa80`04bca900 fffffa80`047b2138 fffffa80`047b23a8 : tcpip!TcpTcbReceive+0x36e
fffff800`03823e10 fffffa60`010561fd : fffffa80`04f55022 fffffa80`047b2138 00000000`00000004 fffffa80`0473b460 : tcpip!TcpMatchReceive+0x1b9
fffff800`03823f10 fffffa60`01046e7d : fffffa80`047c5ff4 fffffa60`00000000 fffff800`03825000 fffffa80`047b2000 : tcpip!TcpPreValidatedReceive+0x2ad
fffff800`03823fb0 fffffa60`01046f29 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IppDeliverListToProtocol+0x4d
fffff800`03824070 fffffa60`01046533 : fffffa60`01140050 fffffa80`056b1130 00000000`00000000 fffff800`03824130 : tcpip!IppProcessDeliverList+0x59
fffff800`038240e0 fffffa60`0104588c : 00000000`00000000 00000000`00000020 fffffa80`056b1130 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x223
fffff800`038241c0 fffffa60`01044e74 : fffffa80`04feb6c0 00000000`00000000 fffffa80`04c1f801 fffffa60`00000004 : tcpip!IpFlcReceivePackets+0x8dc
fffff800`038243c0 fffffa60`010551d3 : fffffa80`04c1f860 fffff800`038244f8 fffffa80`04c1f860 fffffa60`00f70000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x264
fffff800`038244a0 fffffa60`00fad0bc : fffffa80`05127340 fffffa80`04c617a0 fffff800`03824600 fffffa80`04dc91a0 : tcpip!FlReceiveNetBufferListChain+0xd3
fffff800`038244f0 fffffa60`00f758c9 : fffff800`03824650 00000000`00000000 fffffa80`04c4d010 00000000`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0xac
fffff800`03824540 fffffa60`00e54a83 : fffffa80`04dc91a0 00000000`00000002 fffffa80`04c617a0 fffff800`020c25e5 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d9
fffff800`038249c0 fffffa60`00e54bca : fffff800`03824a00 00000000`00000000 fffff800`03824a00 fffffa80`046d6f01 : ndis!ndisDoPeriodicReceivesIndication+0x1d3
fffff800`03824a30 fffff800`020c03fd : fffff800`03824ad8 00000000`00000001 fffff800`021d5cf0 00000000`00000001 : ndis!ndisPeriodicReceivesTimer+0x4a
fffff800`03824a70 fffff800`020bf8d5 : fffff800`03824cd0 fffffa60`00d84702 fffff800`03824cc8 00000000`00000010 : nt!KiTimerListExpire+0x30d
fffff800`03824ca0 fffff800`020bffaf : 00043dba`8a3a7e7d 00000000`00000000 fffff800`00000010 fffff800`021d8a80 : nt!KiTimerExpiration+0x295
fffff800`03824d10 fffff800`020c08d2 : fffff800`021d5680 fffff800`021d5680 00000000`00000000 fffff800`021dab80 : nt!KiRetireDpcList+0x1df
fffff800`03824d80 fffff800`0228d860 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
fffff800`03824db0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4
STACK_COMMAND: kb
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: tcpip!TcpSatisfyReceiveRequests+461
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tcpip
IMAGE_NAME: tcpip.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c18e50c
FAILURE_BUCKET_ID: X64_0x44_tcpip!TcpSatisfyReceiveRequests+461
BUCKET_ID: X64_0x44_tcpip!TcpSatisfyReceiveRequests+461
Followup: MachineOwnerIt looks like it's my network card driver? I've just tried uninstalling it and installing the latest version and i guess i'll need to wait and see if it happens again. Not sure if there's anything else i should have done to make sure the 2 problem ones were completely cleaned out other than run ccleaner between uninstall and install as ccleaner didn't find anything to do with them anyway.
Last edited:
