Hi there,

We have got a high number of Windows 7 Enterprise 64 bit machines randomly goingot into BSOD at boot up. The message at the Blue Screen is:

 

Stop:c0000142 {DLL INITIALIZATION FAILED}

Initialization of the Dynamic Link Library winsrv.dll failed. The process is terminating abnormally

 

In most cases we can recover the machine by going through Last Known Good Profile. Some machines were not so lucky and a re-image is required.

 

On the machines that I was able to recovered. I looked at the Windows System Log and I could see these errors:

Event ID:10010
DCOM got error "206" attempting to start the service TrustedInstaller with arguments "" in order to run the server:
{752073A1-23F2-4396-85F0-8FDB879ED0ED}


Event ID: 7000
The Windows Modules Installer service failed to start due to the following error:
The filename or extension is too long.

 

Also I can't see anything installed from the system log.

 

Like I said Last Known Good Profile would let me recover the machine but some time after a couple of days the machine will blue screen again and again I had to use Last Known Good Profile.

 

Anyone would have any idea what has caused that please?

 

I had tried the followings with no avail:

 

1. Scandisk did not find anything

2. Windows Startup Repair failed to find any problem

3. Virus scanned with NOD32 and Malwarebyte (with the hard drive out hooked up to other machine) and again nothing was found.

 

Thanks,

Edmond.

 

 

Hello, please use Microsoft Skydrive to upload dump files (%systemroot%\minidumps like c:\windows\minidumps) and post a link here. If you want to read dump files without my help, use Windbg and refer to this Microsoft article: http://support.microsoft.com/kb/315263 You can also contact Microsoft CSS. You can start by running sfc /scannow

Did you ever find a solution to this? We are getting very similar issues.

Hi,

9 of our machines have had this issue. Did any solution come of this. Wre very worried this is getting worse.

KevHal

• Edited by Kevin Halstead Tuesday, October 16, 2012 9:04 AM

FYI, we found this to be due to GP prefrences appending an enviroment variable to the PATH field each time the clients refreshed their policies. Due to machines eventually running over the character limit, it caused the enviroment variables to become unreadable by the system.

A restoration of the enviroment registry keys in the following location and a modification to the offending group policy appears to have resolved the problem.

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

Hope this helps others who may encounter similar issues :)

• Proposed as answer by montelaphone Monday, October 22, 2012 3:22 PM
• Edited by montelaphone Monday, October 22, 2012 3:22 PM

This was the answer for me

Path variable cleared, everything works.

A GP adding in a value was killing our machines

• Edited by MattM310 Tuesday, August 05, 2014 5:55 PM

THANK YOU! 

This helped with a 2008 server I've been troubleshooting for months!

Great find, this was our exact issue. Thank you.