ntdll.dll > STOP: C0000221 unknown hard error

  • Thread starter Thread starter BattleAngel444
  • Start date Start date
B

BattleAngel444

Hi All

Here's my story in a nut shell. I finally finished my XPe image, fully
loaded with all the little custom components. Then my company desides
to switch hardware on my :gulp: Luckly the board has the same chip set
and power supply, so I figured no sweat it should at least boot no
prob, and all I would need is a couple system level components like vid
cards and such.

BUT when I booted up, I got the infamous BSOD (blue screen of death)
which said "Stop: C0000221 unknown Hard Error
\SystemRoot\System32\ntdll.dll" I've seen the HAL.dll BSOD befor but
not this one.

At first, I installed XP pro on the new hardware and it worked fine.
So I dug around the internet and found that in some cases XP pro users
got arround this error by coping an existing ntdll.dll file on the the
local one. So I loaded up my dual boot system with XP pro and XPe.
and I copied over the ntdll.dll file over and i stilll get the same
error.

I suspect it maybe some else that calls/looks for ntdll.dll that is
causing the trouble.

Hardware info:
My board I am working on is a iEi NOVA-8890 with Socket 478 Pentium 4
with dual ethernet LAN / 1394A / SATA AGP4X VGA Embedded

I hope some one can help me
Thanks for your time
-BA4^3
 
BattleAngel444 said:
Hi All

Here's my story in a nut shell. I finally finished my XPe image,
fully loaded with all the little custom components. Then my company
desides to switch hardware on my :gulp: Luckly the board has the
same chip set and power supply, so I figured no sweat it should at
least boot no prob, and all I would need is a couple system level
components like vid cards and such.

BUT when I booted up, I got the infamous BSOD (blue screen of death)
which said "Stop: C0000221 unknown Hard Error
\SystemRoot\System32\ntdll.dll" I've seen the HAL.dll BSOD befor but
not this one.

At first, I installed XP pro on the new hardware and it worked fine.
So I dug around the internet and found that in some cases XP pro users
got arround this error by coping an existing ntdll.dll file on the the
local one. So I loaded up my dual boot system with XP pro and XPe.
and I copied over the ntdll.dll file over and i stilll get the same
error.

I suspect it maybe some else that calls/looks for ntdll.dll that is
causing the trouble.

Hardware info:
My board I am working on is a iEi NOVA-8890 with Socket 478 Pentium 4
with dual ethernet LAN / 1394A / SATA AGP4X VGA Embedded

I hope some one can help me
Thanks for your time
-BA4^3
Click to expand...


There are 7 different HAL components in the XPE component database (or a
different number if I'm on crack and my memory is out of whack).

What I usually do when creating a build is to have a component to represent
their hardware (mirrors the PMQ from TAP). You can then build a component
to house everything else (just the ones you explictly add - not the 100s of
components dragged in when resolving dependances).

To start on a new hardware platform, you'd rerun TAP on the new platform and
make a new hardware component. Start a new build. Add the new hardware
component (from the PMQ) and your "everything else" component. Resolve
dependancies, change the various settings as appropriate for your build,
etc. build and deploy.

I wouldn't go around hand copying ntdll.dll files, etc. It may work, but
you may get bitten down the road as well.
 
Hi Gordan

Thanks for the quick response... too bad i won't be able to try this
out tomorrow morning.

So let me get this straight... you think my ntdll.dll error is caused
by a hal.dll error?

I have run TAP on the target machine and it seemed like all the devices
were the same, but I'll try it again.

Thanks again
 
Back
Top