• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

STOP 44 Multiple_IRP_Requests

K

Kurl75

Gawd
Joined
Dec 29, 2001
Messages
554
Im getting this message on a Dell Inspiron 8200 Laptop. Microsoft error database is saying this should only happen when the computer is shutrting down or going in standby mode.

The standby has been disabled and the person is using the computer at the time that this is occuring randomly, usually when using hte internet. Anyone have any ideas why the OS is wanting to shutdown?

Win2000 SP3
Novell Client 4.9a SP2
IE 6

Its driving me crazy. I updated the Novell client hoping htat this had something to do with it. The latest patch from Novell said that it addressed some shutdown issues with Win2K but this still seems to be occuring.
 
Bug Check 0x44: MULTIPLE_IRP_COMPLETE_REQUESTS

The MULTIPLE_IRP_COMPLETE_REQUESTS bug check has a value of 0x00000044. This indicates that a driver has tried to requested an IRP be completed that is already complete.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 The address of the IRP

Cause
A driver has called IoCompleteRequest to ask that an IRP be completed, but the packet has already been completed.

Resolving the Problem
This is a tough bug to find because the simplest case — a driver that attempted to complete its own packet twice — is usually not the source of the problem. More likely, two separate drivers each believe that they own the packet, and each has attempted to complete it. The first request succeeds, and the second fails, resulting in this bug check.

Tracking down which drivers in the system caused the error is difficult, because the trail of the first driver has been covered by the second. However, the driver stack for the current request can be found by examining the device object fields in each of the stack locations.

This is what the sdk says about this bug, unfortunatly it will be very hard to track down.
 
You must log in or register to reply here.
Back
Top