How to Fix Shaderapidx9.dll Faulting Module Error

Shaderapidx9.dll is the faulting module that has left many gamers angry and frustrated. This module has stumped many gamers as they are unable to play their games. The games that seem to be the hardest hit by the shadereapidx9.dll faulting module is Half Life 2 and all Orange Box games.

When Half Life 2 is launched and loads, the game immediately crashes because of a fatal error.

Error Message:

The error message that you will see looks like the one below.

Problem Event Name: APPCRASH
Application Name: hl2.exe
Application Version:
Application Timestamp: 4445c334
Fault Module Name: shaderapidx9.dll
Fault Module Version:
Fault Module Timestamp: 46427727
Exception Code: c0000005
Exception Offset: 0002e59a
OS Version: 6.0.6000.
Locale ID: 1033
Additional Information 1: f708
Additional Information 2: 2d645f9807c58f9e6bcea951e3ac2c9c
Additional Information 3: 17f5
Additional Information 4: 20b2f30032978b4dfa858317ad3ba934

This error does not seem to be limited to Windows Vista as many Windows XP users have been experiencing the crash.


Gamers have been complaining about the delayed response from the manufacturer, Steam, regarding their shaderapidx9.dll trouble tickets. Steam?s long turnaround time has left many gamers trying to find a fix on their own. Steam has responded though and has suggested a possible workaround to the problem.

Other gamers have also come up with solutions to the shaderapidx9.dll issue on their own accord.

How to Fix Shaderapidx9.dll Faulting Module Error

Method 1 ? Steam Fix

  1. Copy wmiprvse.exe from C:\WINDOWS\ServicePackFiles\i386.
  2. Paste the wmiprvse.exe file to C:\WINDOWS\system32\wbem.
  3. Restart Steam.

If the above method does not work for you, proceed to the other suggested methods.

Method 2

  1. Copy the text below into MS Notepad.echo offnet stop winmgmt



    cd c:\windows\system32\wbem

    rd /S /Q repository

    regsvr32 /s %systemroot%\system32\scecli.dll

    regsvr32 /s %systemroot%\system32\userenv.dll

    mofcomp cimwin32.mof

    mofcomp cimwin32.mfl

    mofcomp rsop.mof

    mofcomp rsop.mfl

    for /f %%s in (‘dir /b /s *.dll’) do regsvr32 /s %%s

    for /f %%s in (‘dir /b *.mof’) do mofcomp %%s

    for /f %%s in (‘dir /b *.mfl’) do mofcomp %%s

    mofcomp exwmi.mof

    mofcomp -n:root\cimv2\applications\exchange wbemcons.mof

    mofcomp -n:root\cimv2\applications\exchange smtpcons.mof

    mofcomp exmgmt.mof

  2. Save this as a batch file named shaderapidx9_fix.bat.
  3. Open a DOS window.
  4. Type in the file name at the prompt.
  5. Press Enter.
  6. Answer Y when prompted.
  7. Press Enter.

Method 3

Run the following commands.

net stop winmgmt
winmgmt /resetrepository C:\Windows\System32\wbem\repository
net start winmgmt

This method and the succeeding methods are geared for users who have a WMI problem. The WMI issue seems to stem from the installation of AOL Instant Messenger and other Instant Messaging programs.

These methods will work only if you are experiencing the WMI problem.

To find out if your issue stems from WMI, follow the steps below.

  1. Open Control Panel.
  2. Go to Administrative Tools.
  3. Go to Computer Management next.
  4. Open up Services and Applications.
  5. Go to WMI Control and select More Actions.
  6. Go to Properties.

If there is a WMI issue, you will get an error saying access is denied.
Another way to tell is to look at the network icon on your taskbar. If the network icon has a cross mark but you are connected, then your issue is WMI connected. The same is true if you cannot access the Network and Sharing Center.

Method 4 – Windows Vista Ultimate or Business Users:

  1. Right click on Computer.
  2. Click Manage.
  3. Double click on Users and Groups.
  4. Click Groups.
  5. Right click Administrators.
  6. Click on Add to group.
  7. Click on Add.
  8. Now click Advanced.
  9. Click Find Now.
  10. Double click on Local Service.
  11. Click OK
  12. You should now be able to see NT Authority\Local Service.
  13. Click OK.
  14. Close Computer Management.
  15. Reboot your PC.

Method 5 ? Vista Home Edition

  1. Go to the command prompt.
  2. Type in net localgroup Administrators /add Local Service.
  3. Then type in net localgroup Administrators.
  4. Check if LOCAL NT AUTHORITY/SERVICE is listed. If you see LOCAL NT AUTHORITY/SERVICE, this means that the fix worked.
  5. Reboot your PC.

Method 6

  1. Uninstall all your drivers.
  2. Download the latest drivers from official sites.
  3. Reinstall all updated drivers.

Method 7

If all suggested fixes do not work for you, a fresh reinstall of Windows may be the only solution.