Re: SP2 Causes Blue Screen Crashes--"BAD_POOL_HEADER"

tatane79@hotmail.com (tatane79) wrote in message news:<aead2ca.0411021358.747fab5@posting.google.com>...
> Steven Litvintchouk <sdlitvin@earthlink.net> wrote in message news:<u9InyB0rEHA.2596@TK2MSFTNGP12.phx.gbl>...
> > Ever since I installed SP2, my system keeps crashing, often several
> > times a day, with a "blue screen" message--something about
> > "BAD_POOL_HEADER."
> >
> > When the system comes back up, I allow info about this crash to be
> > transmitted back to Microsoft. And it opens up IE, to inform me that
> > the crash was due to a bad driver--though it doesn't know which one.
> >
> > I never had this problem before I installed SP2.
> >
> > In disgust, I removed SP2 entirely via System Restore, by rolling back
> > to a checkpoint before I installed SP2. No more "BAD_POOL_HEADER"
> > crashes. But it's too bad I won't be able to install SP2 at all this way.
> >
> > Has Microsoft figured out a fix for this yet?
>
> I have exactly the same problem with a Netgear MA111 WiFi USB adapter
> :
> 1. I disconnect the USB adapter
> 2. I install Win XP SP 2
> 3. restart
> 4. once Windows is run, I plug the USB adapter, and immediatly, I have
> the blue screen "BAD_POOL_HEADER"
> 5. I uninstall SP2, and it works again.
>
> s.o has a solution ?


First of all, the Netgear MA111 v1.1 driver seems not to play nice
with XP SP2, from what I read in discussion groups. I bet that's part
of your problem.

Here's what worked for me. Bottom line, don't use Netgear's drivers at
all. Read on for the full story.

The 'puter (Gateway P4 1.4 ghz desktop) was a fresh install of XP SP1
from the OEM CD, then I ran the SP2 update (appx. 274MB .exe file I
keep on a USB hard drive to copy to all the puters I have to do). The
reason for installing a wireless on this puter was so that I could
allow my laptop (centrino with built-in wireless) to share the
desktop's hardwire internet connection as well as share the printer
and files. Previously I had this working with Win98se and the MA111 on
the desktop.

I downloaded the Netgear MA111 V2.0 driver from the website, paying
careful attention that I got the one for the v1 hardware. There's
apparently a MA111v2 adaptor which I don't have, and the drivers are
not compatible. I extracted the files from the .zip file into a
directory, which created a tree of several subdirectories which were
named after driver versions for XP, 2K, 98 etc. as well as including a
subdir for the configuration utility setup files. I did NOT run any
setup.exe at this point, because I thought XP's Wireless Zero Config
might do the job with less resource overhead, as I've found with other
wireless adaptors (Intel 2200BG for example).

So, first I tried plugging in the MA111 (to the desktop puter) and
when XP came up with the hardware wizard, I pointed it to the XP
subdirectory of the driver directory tree mentioned above. The driver
loaded fine. Next, I brought up the properties screen for the new
wireless connection and created a new ad-hoc "preferred network" under
the wireless networks tab, with a 10-digit hexadecimal WEP key. The
laptop then responded that it found a "network within range" and
allowed me to connect to the MA111 with the WEP key, but things were
stuck at "acquiring network address."

My memory is not clear on what happened right after that, but I think
I ran the network setup wizard on the desktop, which configured the
hardwired ethernet to be the shared internet connection and the MA111
to be the internal LAN, so the MA111 was now looking like a DHCP
server. Then an IP was automatically assigned to the MA111 and the
laptop picked one up, and I could get internet on the laptop. Great!
But I couldn't get the laptop or desktop to "see" each other within
network neighborhood (my network places) so file and printer sharing
were still having problems. I tried the usual crap in the network
connection properties and advanced configuration screens, flipping
network bindings on and off. I messed with XP-SP2's firewall settings,
no dice.

Now the MA111 and the laptalk are not talking to each other at all, so
I'm thinking maybe there's something good in the Netgear utilities
after all. So I do a system restore to the approximate time when the
MA111 was able to connect the first time, then run "setup" on the
Netgear driver utility package like the instructions said to do. I use
Netgear's configuration instead of XP's Wireless Zero. I play with
more properties in the "network connections." No better, in fact it
never connected once.

Now I'm pissed. I've played with so many settings that the hardwire
connection is acting funny too. So I unplug the MA111 and do a system
restore back to a time before I first plugged in the MA111, and I lose
one other application program in the process (no big deal, I can
install that again later). Back to pre-MA111 functional state.

Now I'm feeling a bit adventurous. I plug in the MA111 and when XP
came up with the hardware wizard, I checked "Yes connect to Windows
Update this time only." By golly it finds a driver there, and the
driver says it's from Netgear but it's a February 2004 date which
appears to be NEWER than the one you can get from Netgear's website.

Then, like the first try, I created a new WEP-secured, ad-hoc
"preferred network" in the new wireless connection properties. The
laptop found it and connected. In the "advanced" tab of the desktop's
hardwire ethernet properties, I turned off internet connection sharing
and clicked OK, then opened the property sheet again and turned ICS on
again. Now DHCP assigned IP's on the MA111 and the laptop, and the
laptop was on the web.

Now the laptop and desktop can see each other in network places, but
won't give "authorization" to reveal or access any previously shared
resources. I checked that SP2's firewall was allowing the "exception"
for file and printer sharing, all fine there. I added a new shared
folder to one puter and BINGO the other can see it and everything in
it. So I turned off all shares on both puters and turned them back on,
and suddenly all was working fine.

So, the MA111 works with XP SP2 using Wireless Zero Configuration and
drivers from Windowsupdate, Netgear utility not needed.

Hope this helps.

%mod%