BLUE SCREEN while attempting HIBERNATION

[Guest]

If I try to bring my pc into hibernation I get a blue screen with a
DRIVER_IRLQ_NOT_LESS_OR_EQUAL error and a STOP: 0x000000D1.
It’s an old 3 GHZ P4, with 1 GB RAM, running XP SP2, kept up to date.
I searched thoroughly the KB and tried various things of what is suggested,
but with no result.
1) As most problems with hibernation/standby should be caused by hw
incompatibilities, I first suspected of my modem, which was the oldest
component, taken from an older pc. But today I tried with a more recent
device and the problem has not changed.
2) In the KB is referred of a similar problem caused by Logitech mouse, I
thus tried to uninstall and reinstall the related sw.
3) I tried the patch KB916595, which promises to solve many STOP: 0x0D1
problems.
4) I listed all unsigned drivers, found a SoftFax driver, which perhaps is a
residual of the older modem (may be not), tried to disable it.

All these trials had no effect, now I don’t know what else I could try.
Is anybody out there who can help, or that has experienced the same problem?
Thanks.

 

[Plato]

If I try to bring my pc into hibernation I get a blue screen with a
DRIVER_IRLQ_NOT_LESS_OR_EQUAL error and a STOP: 0x000000D1.

Stop errors:

http://www.updatexp.com/stop-messages.html
http://aumha.org/win5/kbestop.htm
http://www.theeldergeek.com/stop_error_messages.htm

 

[Guest]

Stop errors:

http://www.updatexp.com/stop-messages.html
http://aumha.org/win5/kbestop.htm
http://www.theeldergeek.com/stop_error_messages.htm

Thanks Plato for your references.
They don't report of this error while attempting suspension however,
although something similar is reported at shut down.
In any case some driver should cause this fault, but... how can I identify
this sticky driver?
As I said I update my system regularly, and I also searched for the
availability of newer versions of specific drivers, but I always find to have
the latest version.
However the list of drivers is very long, also if I restrict it to unsigned
ones, which are the most suspected. Should I try to disable them one by one?
Is there any chance of damaging the system or of making irreversible changes
in doing this?