Just a quick warning. My W2K SP4 server, running IIS (with .Net framework)
and MSSQL 2000 has been sitting fat, dumb and happy for months. Immediately
after I installed KB832483, it crashed hard, with:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e
(0xc0000005, 0x8046b689, 0x00000000, 0x00000004). Microsoft Windows 2000
[v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini011804-05.dmp.
It was showing the problem was with ntoskrnl.exe. It would bluescreen
consistently within 15 seconds of bootup. Safe mode would boot and run OK.
Last known good configuration did not work, recovery using ERD caused the
server to boot into a non-responsive blue screen. In-place update from the
W2K server CD bluescreened consistently with 0x000000c2 0x00000099
BAD_POOL_CALLER after which point nothing would boot, it would continually
try to restart the install routine.
I ended up having to reformat and reinstall. Thank god for mirrored drives
and backups. On a CLEAN W2K Server install, I installed SP4. The machine ran
fine. I then installed 832483. Right away, my server started locking up
again. This is on an Asus P4S-533 board, 512 megs of DDR-333 RAM, and an
NVidia video card, nothing else strange in the box. I tried swapping the
RAM, power supply and video card, with no result. I rebuilt the server for
the THIRD time, this time purposefully not installing 832483. The server has
been running perfectly ever since. I will NOT be installing 832843 on any
other of my machines, ever.