Jump to content

FoxMulder

Members
  • Posts

    2
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Oops, I made an error in my post. It should be WerFault.exe.
  2. I own a copy of MBAM for my desktop, and I installed a trial copy on my laptop. I noticed that both devices were reporting a similar error in Windows Error Reporting: The instruction numbers were different, but the referenced memory address was the same. My first concern was that this was some kind of malware infection, so I ran Process Manager and logged the activity of my computer so that I could see what was happening and when. I looked specifically at what was happening when the error was reported, and I found one sequence of events that was only present at the time of the error and present at no other time. mbamservice.exe would query C:\Windows\System32\msi.dll, then C:\Windows\System32\Faultrep.dll, then C:\Windows\System32\WerFault.dll, then C:\Windows\System32\sechost.dll and finally C:\Windows\System32\wer.dll. This error would only show up when that sequence was run, and no other time. I have DEP enabled, if that makes any difference. Is this a well-known issue?
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.