On 2019-2-12 2:42, Paul wrote:
http://aumha.org/a/stop.htm
Â*Â* "0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Â*Â*Â* A system thread generated an exception which the error handler
Â*Â*Â* did not catch. There are numerous individual causes for this
Â*Â*Â* problem, including hardware incompatibility, a faulty device
Â*Â*Â* driver or system service, or some software issues. Check
Â*Â*Â* Event Viewer (EventVwr.msc) for additional information.
Â*Â* "
The suggestion to check Event Viewer, applies to cases where
this happens after the system is running for some time, and then
the error shows up.
The 0xC0000005 is an "Access Violation".
As you rightly assume, it's the "thing *after* mup.sys" causing
a problem. Boot logging is a useless feature. Boot logging shows
what successfully loaded, when the user has no clue as to what
comes next in the failure case.
About all I can suggest, is checking Event Viewer for unrelated
error events, to see if there is a "theme", some sickness in
the system that might be contributing to the problem. As I don't
know of a way to attack the problem head-on.
Event view has only one warning of ID 1524 from userenv when I log off, no information during start.
There is more info about that event in C:\windows\debug\usermode\userenv.log:
----------------------------------------------------------------------------------------------
USERENV(2d4.2d8) 09:10:56:765 MyRegUnLoadKey: Failed to unmount hive 00000005
USERENV(2d4.2d8) 09:10:56:765 UnLoadClassHive: failed to unload classes key with 5
USERENV(2d4.2d8) 09:10:56:765 DumpOpenRegistryHandle: 1 user registry Handles leaked from \Registry\User\S-1-5-21-2000478354-1078081533-1801674531-1003_Classes
USERENV(2d4.2d8) 09:10:56:765 ReportError: Impersonating user.
USERENV(2d4.2d8) 09:12:09:640 CUserProfile::CleanupUserProfile: Ref Count is not 0
USERENV(2d4.2d8) 09:12:09:640 CUserProfile::CleanupUserProfile: Ref Count is not 0
USERENV(2d4.2d8) 09:12:09:640 CUserProfile::CleanupUserProfile: Ref Count is not 0
----------------------------------------------------------------------------------------------
I have troubleshooted this too, and tried UPHclean, but not work. It seems a trivial warning, I think I could let it be. But BSOD in safe mode makes me nervous.
--
Regards,
Lu Wei
IM:
PGP: 0xA12FEF7592CCE1EA