kernel-mode memory leak

Hi all

I have a windows XP image that I deploy to similar machines and I'm having a
problem with a particular driver given a particular set of circumstances. I
know the driver that is causing the problem and I'm currently working with
the vendor to correct the issue. I'm looking for a fix to carry me over till
such time as the driver issue is resolved.

I'm using Powerquest to deploy the image and on first boot the OS loads and
everything is fine. I receive a prompt that new hardware has been installed
and I'm prompted to reboot. At this point everything if fine, the problem
driver is loaded and is functioning correctly and there is no leak. As soon
as reboot I have the issue. The driver is now leaking and the open handle
count on the "system" process slowly climbs till around 4 days when the
machine will lock up and become unresponsive.A reboot corrects the problem,
for another 4 days.

If "new hardware" is not detected on the freshly imaged system, I experience
no issues at all. The problem only manifests itself when new hardware is
detected and a reboot is required as a result of this first boot. If no
reboot is required the issue never appears, even after subsequest reboots.

Does anyone have any idea on how I can work-around this issue?

I'd also like to see if the issue will appear on the machine I do not have a
problem on if subsequently new hardware is detected. Is there a way to
trigger the "New hardware has been detected and windows needs to reboot
message"?

TIA
KIWI