RPCRT4.dll crash

The last couple of days I have been getting random crashes in RPCRT4.dll.

The only thing i can think of that I have changed recently is disabling a few Adobe startup services.

I have attached recent logs. Any help would be appreciated

I can't see any .dmp files there....
is there any BSOD?

No BSOD just an appcrash, then Explorer seems to be really flaky after it. Should I post in another forum topic?

RPCRT4.dll is the Remote Procedure Call (RPC) API, used by Windows applications for network and Internet communication.
source

many of the errors from your log are also associated with dllhost.exe

Code:

Event[2870]:
  Log Name: Application
  Source: Application Error
  Date: 2013-05-08T10:49:54.000
  Event ID: 1000
  Task: Application Crashing Events
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Beast
  Description: 
Faulting application name: DllHost.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc6b7
Faulting module name: RPCRT4.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59
Exception code: 0xc0020043
Fault offset: 0x0005cd99
Faulting process id: 0xfc8
Faulting application start time: 0x01ce4b85ed204825
Faulting application path: C:\Windows\SysWOW64\DllHost.exe
Faulting module path: C:\Windows\syswow64\RPCRT4.dll
Report Id: 31f962c2-b779-11e2-ae91-002522f8e029

Dllhost.exe is used for hosting dlls, in this case rpcrt4.dll
chances are this dll is the problem

open command prompt, Start > Run or press Windows Key + R on Keyboard > type "cmd" w/o quotes > enter/ok
type SFC /scannow
let's see the results from there

This PC only has windows defender on it. It is mainly a dev machine and is rarely networked. I did run a scan with house call after I started getting the error though and everything came up clean

sorry, I edited my post above

you can try Microsoft Security Essentials.
There's no harm in being careful, isn't it

Hello,
To all with the rpcrt4.dll error.
My experience is that it originates in dotnet 4.0.
I uninstalled it and installed it again and the problem was fixed.
That's all!