Eric Kohl wrote:
I think the bugcheck happens when csrss.exe loads
win32csr.dll and
thus user32.dll and user32 gets initialized.
Did anything change in the initialization within the last month? I
made a full rebuild on March 2nd and it installed perfectly.
No changes in win32csr by me (none I actually committed; only in an
offline local tree). Also plug-in loader is untouched (no docs: looking
into it to understand how it works).
The major changes are:
- sm loads the required subsystems reading the registry
- csrss needs ok from sm to boot (registering)
- winlogon is child of csrss not sm (for future multiuser w32)
To do:
- DEBUG subsystem may be an external native process
- sm dies if any required subsystem dies (actually only win32)
- sm kills any subsystem that doesn't not follow the registration protocol
Maybe a race condition between win32csr.dll and winlogon? When it was
run by sm it was done after csrss had notified sm signalling a named
event to day boot was OK.
Emanuele