I've been running Vista Business on a Lenovo 3000 N100 laptop (2GB ram,
dual-core) for about 6 months without significant problems.

Then, starting yesterday afternoon, I began getting "page fault in non
paged area" blue screens, about 15-60 minutes after a cold boot or
restart. The timing is not very consistent, but it is consistently
happening.

Any clue what could be happening? One thing that may be relevant:

Just before this started, I was using it in a location with about 10
minimal-strength Wifi networks, so told it to disconnect in the "connect
to a network" window. Then when I came home, on resuming from hibernate,
it wouldn't find anything, including my high-strength home wireless
network, so I did a shut down / cold reboot. Then it found my network --
and page fault bluescreened for the first time about 15 minutes later.

Maybe that's relevant, maybe not. The timing makes me think it's
correlated to some scheduled updater task -- seems everything you
install has that these days -- that kicks off and screws up. But I can't
tell what starts just before the bluescreen.

--
Greg

Well, may as well answer this myself, since after doing this a bunch of
times, it seems to have stopped.

The 10 reboot solution.

Greg wrote:
I've been running Vista Business on a Lenovo 3000 N100 laptop (2GB ram,
dual-core) for about 6 months without significant problems.

Then, starting yesterday afternoon, I began getting "page fault in non
paged area" blue screens, about 15-60 minutes after a cold boot or
restart. The timing is not very consistent, but it is consistently
happening.

Any clue what could be happening? One thing that may be relevant:

Just before this started, I was using it in a location with about 10
minimal-strength Wifi networks, so told it to disconnect in the "connect
to a network" window. Then when I came home, on resuming from hibernate,
it wouldn't find anything, including my high-strength home wireless
network, so I did a shut down / cold reboot. Then it found my network --
and page fault bluescreened for the first time about 15 minutes later.

Maybe that's relevant, maybe not. The timing makes me think it's
correlated to some scheduled updater task -- seems everything you
install has that these days -- that kicks off and screws up. But I can't
tell what starts just before the bluescreen.

--
Greg