BAD POOL HEADER ERROR AFTER FRESH XP 2 INSTALL? DELL X300

[wildman]

I just installed XP 2 Pro on a Dell Latitude x300. It was previously
running windows 2003 server.

Install appeared to go well and complete, but now when I boot I get
the blue screen with error:

BAD POOL HEADER and then it takes me to a menu where I can go into
Safe mode.

BTW, how do freeze that screen so i can read it all.. its only up
about 2 seconds.

I was able to go into safe mode and look at the event viewer and don't
see any errors except errors about select services not being able to
start in safe mode.

I open device manager and see the audio controller, network control
and pci modem are not configured, but this is normal on fresh
installs.

What could this be?

Thanks for any help or information.

 

[Gerry]

Please post copies of the Stop Error Reports.

Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly. Right click on
the My Computer icon on the Desktop and select Properties, Advanced,
Start-Up and Recovery, System Failure and uncheck box before
Automatically Restart.

Do not re-enable automatic restart on system failure until you have
resolved the problem. Check for variants of the Stop Error message.

An alternative is to keep pressing the F8 key during Start-Up and select
option - Disable automatic restart on system failure.

If you are using a wireless keyboard and the F8 key does not work
substitute a wired keyboard and mouse for this exercise only.

Background information on Stop Error message 0x19
http://msdn2.microsoft.com/en-us/library/ms793223.aspx

0x00000019: BAD_POOL_HEADER
A pool header issue is a problem with Windows memory allocation. Device
driver issues are probably the mstt common, but this can have diverse
causes including bad sectors or other disk write issues, and problems
with some routers. (By theory, RAM problems would be suspect for memory
pool issues, but I haven't been able to confirm this as a cause.)
Source: http://aumha.org/a/stop.htm


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[wildman]

thanks.

BAD_POOL_HEADER

STOP: 0x00000019 (0x00000020,0x8251E4E8,0x8251E618,0x0A260065)

presuming this is the stop error report, if not where do I get that?

 

[Bob I]

Pick 19 in the left column at the link below
http://aumha.org/a/stop.htm

 

[jc]

0x00000019: BAD_POOL_HEADER
(Click to consult the online MSDN article.)
A pool header issue is a problem with Windows memory allocation.
Device driver issues are probably the msot common, but this can have
diverse causes including bad sectors or other disk write issues, and
problems with some routers. (By theory, RAM problems would be suspect
for memory pool issues, but I haven't been able to confirm this as a
cause.)


Cause
The pool is already corrupted at the time of the current request.

This may or may not be due to the caller.

Resolving the Problem
The internal pool links must be walked to figure out a possible cause
of the problem.

Then you can use special pool for the suspect pool tags, or use Driver
Verifier on the suspect driver. The !analyze debugger extension may be
of help in pinpointing the suspect driver, but this is frequently not
the case with pool corrupters.


I doubt memory happen to go bad right now as I attempt to install XP
sp2.

Any idea how I can find the suspect driver?

Worth trying to reinstall Windows XP sp2?

It was running win 2003 for months prior to that with no problem?

 

[Bob I]

You could try Disc Diagnostic from the Harddrive vendor, and there is
Memtest86 you can test memory with

http://www.memtest86.com/

 

[Gerry]

That is the Stop Error Report. Sometimes there can be further
information on the lines below identifying the driver causing the
problem. You may get additional information from the corresponding
report in Event Viewer.

http://www.microsoft.com/whdc/DevTools/tools/DrvVerifier.mspx
Using Driver Verifier is not an easy route to take.

Earlier you said "I open device manager and see the audio controller,
network control and pci modem are not configured, but this is normal on
fresh
installs." I am not sure you can ignore what I think you are saying!

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

Try Start, Run, type "sigverif.exe" without quotes and hit OK. What
drivers are listed as unsigned? Disregard those which are not checked.

If the BSOD does not occur when accessing in safe mode that means it is
caused by a driver which only loads in normal mode. The Event Viewer
Reports about drivers not loading may offer a pointer?

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~