Windows 7 BSOD

[jambo4life1874]

Wonder if anybody can help me, I seem to be getting the Multiple IRP Complete Requests BSOD when booting up. It's Windows 7 32 bit system. It has happened on several occasions next time I have started up after installing a programme or updates. It has happened with different things so not sure what exactly is causing this.

Copy of the dump file attached.

 

[yowanvista]

Boot in safemode with networking
Download Malwarebytes
Install and update it
Run a full scan and remove any infections

An obsolete software from Radialpoint Inc may have caused the crash, this software may be used by a device attached to your computer. Please update that software. Remove that device/software if no new driver updates are found
Home - Radialpoint

Remove any AVG software and use MSE

AVGIDSDriver.sys        0x98d1e000    0x98d46000    0x00028000    0x4acfa5d0    10/10/2009 01:06:24                
AVGIDSEH.sys        0x8b200000    0x8b209000    0x00009000    0x4acfa5e8    10/10/2009 01:06:48                
AVGIDSFilter.sys        0x98d14000    0x98d1e000    0x0000a000    0x4acfa5a5    10/10/2009 01:05:41                
AVGIDSShim.sys        0x98c8b000    0x98c8e580    0x00003580    0x4acfa607    10/10/2009 01:07:19

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

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.
Arguments:
Arg1: 88abdb40, Address of the IRP
Arg2: 00000eae
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


IRP_ADDRESS:  88abdb40

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x44

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8abec2a2 to 82c8fcbd

STACK_TEXT:  
8cf839c8 8abec2a2 88ab14c8 889b9870 88ab14c8 nt!IopfCompleteRequest+0x4b0
8cf839e4 8abf33f3 005367f0 88ab14c8 88ab155c tdx!TdxDisassociateConnection+0x11e
8cf83a00 82c4e593 889b9870 88ab14c8 88ab155c tdx!TdxTdiDispatchInternalDeviceControl+0x135
8cf83a18 90a1b7a1 1c5a2631 8899c818 88ab14c8 nt!IofCallDriver+0x63
WARNING: Stack unwind information not available. Following frames may be wrong.
8cf83c08 90a1f663 8899c818 8899c8d0 88ab14c8 rp_skt32+0x47a1
8cf83c38 82c4e593 8899c802 88ab140f 88ab14c8 rp_skt32+0x8663
8cf83c50 9003a513 8a536a48 00020000 900398cf nt!IofCallDriver+0x63
8cf83c80 90044dfe 8a5369c0 00000000 00000000 afd!AfdIssueDeviceControl+0xcf
8cf83cac 90023b37 8a536a48 8a536ac0 90031ea8 afd!AfdFreeConnectionResources+0x2a
8cf83cc4 90038c42 8a536a48 8cf83cec 9002307e afd!AfdFreeConnectionEx+0xd6
8cf83cd0 9002307e 8a536ac0 88a1e6e8 88950578 afd!AfdFreeConnection+0x1d
8cf83cec 82e2b466 88950578 00000000 8548ed48 afd!AfdDoWork+0x51
8cf83d00 82c94aab 88a1e6e8 00000000 8548ed48 nt!IopProcessWorkItem+0x23
8cf83d50 82e1ff64 00000001 a1501910 00000000 nt!ExpWorkerThread+0x10d
8cf83d90 82cc8219 82c9499e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tdx!TdxDisassociateConnection+11e
8abec2a2 8b4df8          mov     ecx,dword ptr [ebp-8]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  tdx!TdxDisassociateConnection+11e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tdx

IMAGE_NAME:  tdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce78935

FAILURE_BUCKET_ID:  0x44_tdx!TdxDisassociateConnection+11e

BUCKET_ID:  0x44_tdx!TdxDisassociateConnection+11e

Followup: MachineOwner
---------