BSOD on third boot

[abc]

Hello out there. I've run into a strange problem with an XPE load that I am
working on and I'm hoping that someone out that has a suggestion to help me
fix the problem.

Here is the sequence of events:
1. Create SLX (dependency check finds no errors)
2. Build image from SLX (no errors reported)
3. System boots up for the first time (FBA runs and does it job; I don't see
any errors here)
4. System boots up for the second time into Windows XPE; I logon, check some
things out, and then restart the system
5. System boots up for the third time and gets a BSOD after the Windows XPE
logo

The BSOD is:

STOP: c000021a {Fatal System Error}
The Session Manager Initialization system process terminated unexpectedly
with a status of 0xc000003a (0x00000000 0x00000000).
The system has been shut down.

I looked for this error at Microsoft's web site and found an article stating
to fix it try these two things:
1.. Identify missing dependencies. For information, see Checking
Dependencies.
2.. If you determine that a dependency is not missing, then the error
probably occurred because a file that the driver depends on is missing. Use
the Microsoft® Visual Studio® Depends utility, which runs using the
Depends.exe file, to view the statically loaded libraries located in the
import section of the binary file. Search for required files that are
missing from your run-time image.
I've re-run the dependency checker in Target Designer and it did list any
errors.

I've also attempted to run the DEPENDS.EXE but I'm not too sure how to use
it for my problem.

Any thoughts/suggestions/other would be greatly appreciated.

Thank you

 

[Gordon Smith \(eMVP\)]

Have you tried adding Dr Watson to your build and checking it's log?

--Gordon Smith (eMVP)

 

[abc]

The Dr. Watson component was already in the build. I could not find a log
file for Dr. Watson on the system.

 

[Gordon Smith \(eMVP\)]

Are you doing funny this with your partitions? That error can come up if
the partition becomes corrupt, your system forgets the drive letter
assignment for the boot device, etc.

--Gordon Smith (eMVP)

 

[Gordon Smith \(eMVP\)]

Pardon the typo. "this" = "things"

Are you doing funny this with your partitions? That error can come
up if the partition becomes corrupt, your system forgets the drive
letter assignment for the boot device, etc.

--Gordon Smith (eMVP)

 

[abc]

I have two drives in my system:

Drive 0 - Windows 2000 Professional SP4 (Drive C)
Drive 1 - Windows XPE SP1 (Drive E)

After the STOP error I will boot into Win2k and get the message "The file
system structure on the disk is corrupt and unusable. Please run the chkdsk
utility on th evolume E". Chkdsk will then run automatically and corretc
whatever problem it found. After I've logged in (Win2k) I checked the E
drive and could still see files/directories there.

 

[Gordon Smith \(eMVP\)]

Did you copy XP's NTLDR to your win2k partition? They're backward
compatible.

 

[abc]

Yes, I copied XP's NTLDR and NTDETECT.COM.

Did you copy XP's NTLDR to your win2k partition? They're backward
compatible.

 

[Gordon Smith \(eMVP\)]

Well, it seems as though we know why the error happens (corrupt partition).
Now you have to figure out what's causing the corruption. Good luck.

 

[KM]

abc,

Not sure about your TD partition settings. But your apps (drivers) may use a hardcoded (or mistyped) C:\ path.
Try using Slobodan's approach (http://msdn.microsoft.com/embedded/community/tips/xp/rtpartin/default.aspx) to make your runtime
think it is running from C:\. See if you still see the error. If not - that was the problem. If you still see the error, the problem
may not be in corrupt partition. Then you may try removing drive 0 when you run FBA on runtime.

 

[abc]

Well, I've figured out what the problem was and how to correct it.

The disk that I was building my image to was once used in a different
Windows 2000 Pro system prior to me "acquiring it" for my testing. When it
was in that system it was converted from a basic disk to a dynamic disk.

My XPE build didn't like this for some reason even though I had the both the
Basic and Dynamic Disk Management components in the build.

I then found an article that described how to convert the disk back to basic
from dynamic without any data loss
(http://faq.arstechnica.com/link.php?i=1806) and it worked.

Go figure.....