bad_pool_header server 2003 enterprise edition, 2gb ram

[Temmu]

greets!

the subject server is 3 or 4 years old, and isn't under a lot of memory, cpu or hd load.

4 months ago, i added a second 4 port fax card to the subject machine.
it's run fine since.

yesterday, i discovered all the fax processes i monitor, stopped.
when i looked, the machine was hung. i restarted it.

this morning, i discovered the glorious blue screen of death:

bad_pool_header

stop: 0x00000019
(0x00000020, 0xe29fde20, 0xe29fde88, 0x0c0d080d)

a cold reboot lets the machine run for 5 or 10 minutes, then it crashes.
here's another one, just now

bad_pool_header

stop: 0x00000019
(0x00000020, 0xe29c5e48, 0xe29c5eb0, 0x0c0d0213)


any input would be greatly appreciated!

 

[Temmu]

booting into safe mode produces a quick logon and apparently stable environment.

of course, that's no solution... but obviously, some driver's vomiting on itself. but why now?

 

[x BlueRobot]

Please follow - https://www.sysnative.com/forums/bs...structions-windows-8-7-and-windows-vista.html

 

[Temmu]

thanks anyway - realizing that it was driver related, i disabled first one company's drivers, then the other, giving me who was at fault.
sorry to have bothered ya'll.

 

[Patrick]

What was the culprit?

 

[Temmu]

well, the big hint - the hard drive light remained lit for the 5 to 10 minutes it took the server to blue-screen.
having isolated the "bad" driver to the fax vendor's software
and having discovered that there were 2.5 million (!!) files in the log folder
the vendor disabled logging and that was the temporary fix.

will see what they do about it monday.
thanks for asking, patrick.
(ps, would have been improbable to find that diagnosis w/o logging into server & being the software vendor... just guessing.)

 

[x BlueRobot]

Glad you were able to find the culprit driver :smile9:

 

[Temmu]

thx, bluerobot!