Loaded SP1 for Server 2003, now BSOD
Ok, for some backgound, this has happened before.
https://www.experts-exchange.com/questions/21593848/URGENT-Bad-Pool-Header-stop-error-BSOD.html
Yes, like an idiot, I loaded service pack 1 again. But I have it narrowed down to NIC. This system has 3 nic cards installed. I have them all 3 disabled. If they are disabled, the server will boot. As soon as I go into the device manager and enable one of the nics, it bluescreens with BAD_POOL_HEADER and stop error 0x00000019, same as before.
Any insight as to why? I've loaded newer drivers, older drivers, nothing! There are 2 different brands of nics in here. One is an Intel Pro 1000 MT, and the other 2 are 3COM. I'm trying a different nic right now, a Netgear FA311.
Help?
https://www.experts-exchange.com/questions/21593848/URGENT-Bad-Pool-Header-stop-error-BSOD.html
Yes, like an idiot, I loaded service pack 1 again. But I have it narrowed down to NIC. This system has 3 nic cards installed. I have them all 3 disabled. If they are disabled, the server will boot. As soon as I go into the device manager and enable one of the nics, it bluescreens with BAD_POOL_HEADER and stop error 0x00000019, same as before.
Any insight as to why? I've loaded newer drivers, older drivers, nothing! There are 2 different brands of nics in here. One is an Intel Pro 1000 MT, and the other 2 are 3COM. I'm trying a different nic right now, a Netgear FA311.
Help?
ASKER
I don't think that fix is for me, as my prob has to do more with the NIC cards being enabled or disabled. I'll see if I can find the hotfix that is listed in that kb article you linked, without contacting microsoft to get it, otherwise I'm not going to mess with it.
ASKER
Yes, this does not apply here, as it states on that Kb article: "This problem was corrected in Windows Server 2003 Service Pack 1."
I just loaded SP1.
I just loaded SP1.
ASKER
Ok, just got done removing all nics and installing the Netgear FA311. Same thing, once the drivers finished loading, Bluescreen, BAD_POOL_HEADER 0x00000019 (0x00000020, somthin, somethin, somethin).
WTF?
WTF?
I would still contact Microsoft for the hotfix even though they state that the first fix option is sp1. I have seen before where this did not resolve but the hotfix did.
Just for thought. :)
Just for thought. :)
ASKER
Well, after comparing my ntfs.sys file with the ntfs.sys file from the hotfix, I'm sure they're the same file.
I'll see if I can get ahold of it without microsoft charging me... that's what pisses me off the most. Their software doesn't work right, and they're gonna charge me to talk to them about how to fix it. Idiots.
I'll see if I can get ahold of it without microsoft charging me... that's what pisses me off the most. Their software doesn't work right, and they're gonna charge me to talk to them about how to fix it. Idiots.
Not if it is a hotfix. There is no charge. Just specify the KB article and you will not be asked for money.
ASKER
Whohoo!
Did it work?
ASKER
Nope, did get the hotfix for free though. But still same prob.
ASKER
Well, I'm now going to run a repair off my Server 2003 (no SP) disc, and go from there.
Got a recent backup?
ASKER
Haha, nope, that's another problem, Yosemite's Tapeware has started to cause an error on startup. Bad things in general have been happening with this stupid server. Ran a repair, everything seems ok again for the time being, disabled automatic updates and made myself a note about SP1 so I don't do that again.
So SP1 is killing just that server eh? I have loaded it on 6 of my servers and have not seen any issues. All of the servers are HP/Compaq G3 and G4 servers.
What brand server hardware are you running?
What brand server hardware are you running?
ASKER
Running a Dell PowerEdge 1600.
OK. Thanks
Doesnt dell have any support pages with regards to the poweredge 1600 ? What about diagnosis software that dell supply ?
Aside from that and as a very very last resort if you cant find out or dig anything else up , possibly a bios update ?
I would be interested to see what happens with regards to using the different NIC though.
Aside from that and as a very very last resort if you cant find out or dig anything else up , possibly a bios update ?
I would be interested to see what happens with regards to using the different NIC though.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Microsoft has a hotfix that specifically addresses this issue. Hotfixes are supplied free of charge.
See kb article: http://support.microsoft.com/kb/892260/en-us
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Mike