Link to home
Create AccountLog in
Avatar of Agent912

asked on

BSOD when backing up XP machine using Windows Home Server

Configuration is as follows. 2 Laptops one running vista one running XP conected to a router gateway. Also connected to the gateway is a HP mediasmart server running Windows Home Server and a printer. All are currently working without any other issues.

Both laptops have WHS console installed on them in order to be able to communicate and run simple admin on the mediasmart server (which is actually more of a glorified Storage device than a server)
We use the mediasmart server as a fileshare and backup utility. Using the WHS console we are able to back up the connected laptops which communicate with it through the router.  The vista laptop has no errors when backing up to the server however when we try to backup from the xp machine, as the backup process begins the laptop BSOD with error BAD_POOL_HEADER
with the following event viewer log details -
Event ID: 1003
Error code 00000019, parameter1 00000020, parameter2 e3dcbd00, parameter3 e3dcbd20, parameter4 0c040201.
I'm guessing this is an error on the XP machine which is initiated by running the backup process using WHS console so not a direct issue with the mediasmart server.
I feel that my only option would be to do a software rebuild on the xp laptop but would obviously like to avoid this if posible.
Avatar of johnb6767
Flag of United States of America image

Can you upload the .dmp files from c:\windows\minidump to We might be able to isolate the faulting module....

It is not a hidden folder.....

Might need to verify if it is even set to minidump. Paging file needs to be on the C: drive as well, for a dump to occur...

Contro Panel>System>Advanced>Startup and Recovery, and make sure it is checked to do a small minidump, and note the directory...

If you cant boot it, then you can always use a BartPE CD to boot to an alternate OS, and retrieve the files.....

Bart's Preinstalled Environment (BartPE) bootable live windows CD/DVD

or, if you would like to learn it on your own......

The Offline Crash Diagnostic tool for Windows XP is available

BSOD Hell & How to Fix it

If you get Dumps, then the Windows Debugger is usually adequate to read the crash dumps...Takes a little practice though....


Use the Microsoft Symbol Server to obtain debug symbol files
(so you dont need the full symbol packages for each OS, and SP....)

Some of the most basic commands....

!analyze -v

Should be enough to get you started....Use the built in help feature of WinDbg, its a great resource...
Or simply change them to a .txt file, and upload the file here....
Avatar of Agent912


John i have uploaded the .txt dump file to the link you suggested having looked at it, it makes no sense to me at all.

I have also uploaded it here so maybe you could have a look?

How to Use Driver Verifier to Troubleshoot Windows Drivers

I was hoping the dump would be more obvious.... But it is not... Definately driver fault though....

Use the verifier utility to see if you can find any unsigned drivers.... And start with those....
See my previous post for the solution. It's the same problem.

Post #5:

BugCheck 19, {20, e3dcbd00, e3dcbd20, c040201}
Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+2a3 )

f7aab928 8054a583 00000019 00000020 e3dcbd00 nt!KeBugCheckEx+0x1b
f7aab978 8058e9e9 e3dcbd08 00000000 00000000 nt!ExFreePoolWithTag+0x2a3
f7aab9d8 80590401 855ed5a0 e318e6f0 f7aaba44 nt!PipMakeGloballyUniqueId+0x3a9
f7aabacc 8059100f 85c39008 85606a78 86f45008 nt!PipProcessNewDeviceNode+0x185
f7aabd20 805914fe 86f45008 00000001 00000000 nt!PipProcessDevNodeTree+0x16b
f7aabd54 804f6953 00000003 8055a5c0 805637bc nt!PiProcessReenumeration+0x60
f7aabd7c 80537aff 00000000 00000000 86fc23c8 nt!PipDeviceActionWorker+0x14b
f7aabdac 805cea08 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f7aabddc 8054546e 80537a10 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

Tried running the verifier but i have to be honest, i am well out of my depth so i think the best option which is a total cop out is to wipe XPand do a software rebuild of the culprit laptop. Thanks for your help John.

Acronis was the culprit, i found out that it had been installed on the machine a couple of months previously as a trial. After taking the steps below, which i found at the above link the problem seemed to be resolved.

1. Go to windows Device Manager
2. Click "view" and select "show hidden devices"
3. Scroll down to "storage volumes"
4. Click on the plus to expand.
5. Click on each one listed and right click and uninstall. (you will get a message on some saying to reboot before it takes effect. Select no until you do them all.)
6. Reboot.
7. Wait till windows automatically reinstalls devices. Will prompt to reboot again.
8 Reboot.
Now it should work.
Glad you found it. Thanks for updating us....
Avatar of Computer101
Flag of United States of America image

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account