1. #1
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    16,638
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    BSOD Bugchecks (STOP ERRORS) 0xC0000142 + -1073741502



    "0xC0000142" or "-1073741502" Stop error when many PowerShell scripts call the Console.Write method or when you try to start many console applications on a PowerShell console in Windows 7 or in Windows Server 2008 R2



    Symptoms
    Assume that many Windows PowerShell scripts call the Console.Write method, or you try to start many console applications on a Windows PowerShell console on a computer that is running Windows 7 or Windows Server 2008 R2. In this situation, the script exits or the console applications do not start, and you receive one of the following exit codes:

    0xC0000142
    -1073741502

    Additionally, you cannot start any of the console applications from the PowerShell console.
    Notes
    •The exit code describes a STATUS_DLL_INIT_FAILED issue.
    •This issue is resolved temporarily when you stop the PowerShell script and then restart the PowerShell console.

    Cause
    This issue is caused by an error in the Microsoft.powershell.consolehost.dll file. When a Windows PowerShell script calls the Console.Write method, or when you run an executable file for an application from a Windows PowerShell session, values are written into the PowerShell console. Additionally, a corresponding console handle is created. When many console handles are created, the console handles leak, and the issue that is described in the "Symptoms" section occurs.

    Resolution
    This hotfix is also available at Microsoft Update Catalog.

    Hotfix information
    A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

    If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

    Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
    http://support.microsoft.com/contactus/?ws=support

    Note: The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

    Prerequisites
    To apply this hotfix, you must be running one of the following operating systems:•Windows 7
    •Windows 7 Service Pack 1 (SP1)
    •Windows Server 2008 R2
    •Windows Server 2008 R2 Service Pack 1 (SP1)

    For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

    976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

    Registry information
    To apply this hotfix, you do not have to make any changes to the registry.

    Restart requirement

    You must restart the computer after you apply this hotfix.

    Hotfix replacement information
    This hotfix does not replace a previously released hotfix.


    Please see -
    https://support.microsoft.com/en-us/...l-scripts-call


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2
    Jared's Avatar
    Join Date
    Feb 2014
    Age
    21
    Posts
    1,589
    • specs System Specs
      • Manufacturer:
        Custom
      • Motherboard:
        ASUS Maximus VII Ranger
      • CPU:
        i7 4790K @ 4.4GHz
      • Memory:
        Corsair Vengeance 16GB 1866MHz
      • Graphics:
        MSI Gaming 4G GTX 980
      • Sound Card:
        Creative Soundblaster ZxR
      • Hard Drives:
        Samsung 850 SSD 250GB
      • Disk Drives:
        Western Digital Black Caviar 2TB
      • Power Supply:
        Corsair RM650 Modular 650 Watts
      • Case:
        Fractal Design Define R5 Window
      • Cooling:
        Corsair H100i GTX
      • Display:
        Dell U2515H 25inch 2560x1440 + LG Flatron M2262D 22inch 1920x1080
      • Operating System:
        Windows 10 Professional x64

    Re: BSOD Bugchecks (STOP ERRORS) 0xC0000142 + -1073741502

    Just to clarify, this isn't a stop error - it's just an application crash with STATUS_DLL_INIT_FAILED.

Similar Threads

  1. Bugchecks (STOP ERROR) Codes
    By jcgriff2 in forum BSOD Kernel Dump Analysis Debugging Information
    Replies: 0
    Last Post: 07-17-2015, 10:27 PM
  2. Error (0xc0000142)
    By bubblebooy in forum BSOD, Crashes, Kernel Debugging
    Replies: 7
    Last Post: 11-25-2013, 06:49 PM
  3. Replies: 0
    Last Post: 11-05-2013, 07:44 PM
  4. BsoD STOP: 0x000000124
    By droidek2013 in forum BSOD, Crashes, Kernel Debugging
    Replies: 2
    Last Post: 06-25-2013, 04:50 AM

Log in

Log in