Looking for any information regarding Blue screen trap
with stop code: 0x00000044 and specifically 0x84391e48.
This is a production server with a Unix database running
via a kornshell. All is patched up to date but occasional
bluescreen/reboot (2-3 times per month). Any ideas or
suggestions are greatly appreciated.

This is a fairly specific bug in a system device driver.

http://msdn.microsoft.com/library/de...codes_93tz.asp

If this is a Windows 2000 or higher machine, turn on the driver verifier
(verifier.exe) for at least the non-Microsoft provided drivers you may have
on your system (virus scanners, quote management, etc.). In particular, you
want to turn on the IO verification options. The next bugcheck may be able
to finger the guilty driver right on the blue screen itself.

http://msdn.microsoft.com/library/de...ls/dv_2mlv.asp

What I would probably do first, though, is figure out which non-Microsoft
drivers you have on your system (the verifier's list will show this) and
make sure you have the latest versions of all of them.

Dan Lovinger
--
This posting is provided "AS IS" with no warranties, and confers no
rights.

----- Original Message -----
From: "Scott_W" <(E-Mail Removed)>
Newsgroups: microsoft.public.win2000.file_system
Date: Tuesday, November 25, 2003 10:56 AM
S&ubject: Blue Screen Trap

> Looking for any information regarding Blue screen trap
> with stop code: 0x00000044 and specifically 0x84391e48.
> This is a production server with a Unix database running
> via a kornshell. All is patched up to date but occasional
> bluescreen/reboot (2-3 times per month). Any ideas or
> suggestions are greatly appreciated.