Should I block it?

No, this file is 100% safe to run.

VersionsAdditional versions

12e64 85.71%
80dad 14.29%
(Note, the developer publishes each variation of this file with the same version, but the hashes are unique.)

PE structurePE file structure

Show functions
Import table
advapi32.dll
GetUserNameW
kernel32.dll
UnhandledExceptionFilter, DisableThreadLibraryCalls, WideCharToMultiByte, WriteFile, GetCurrentProcess, GetCurrentProcessId, GetProcAddress, LoadLibraryW, GetCurrentThreadId, RaiseException, OutputDebugStringW, FileTimeToDosDateTime, FileTimeToLocalFileTime, CloseHandle, GetFileTime, GetFileSize, CreateFileW, GetModuleFileNameW, GetSystemInfo, GlobalMemoryStatus, lstrcpyW, GetSystemTimeAsFileTime, GetTempPathW, SetFilePointer, GetVersionExW, FreeLibrary, lstrcpynW, SetLastError, VirtualProtect, FlushInstructionCache, LoadLibraryA, GetModuleHandleA, FlushFileBuffers, VirtualQuery, HeapAlloc, SetStdHandle, LCMapStringW, LCMapStringA, GetStringTypeW, ExitProcess, RtlUnwind, GetCommandLineA, GetVersionExA, QueryPerformanceCounter, GetTickCount, GetModuleFileNameA, InterlockedExchange, HeapFree, TlsAlloc, GetLastError, TlsFree, TlsSetValue, TlsGetValue, SetUnhandledExceptionFilter, HeapReAlloc, TerminateProcess, HeapSize, SetHandleCount, GetStdHandle, GetFileType, GetStartupInfoA, DeleteCriticalSection, FreeEnvironmentStringsA, GetEnvironmentStrings, FreeEnvironmentStringsW, GetEnvironmentStringsW, HeapDestroy, HeapCreate, VirtualFree, DebugBreak, LeaveCriticalSection, EnterCriticalSection, VirtualAlloc, IsBadWritePtr, IsBadReadPtr, IsBadCodePtr, GetACP, GetOEMCP, GetCPInfo, MultiByteToWideChar, InitializeCriticalSection, GetProcessHeap, GetLocaleInfoA, GetStringTypeA
shell32.dll
ShellExecuteW
shlwapi.dll
PathFindFileNameW
user32.dll
wsprintfW, wvsprintfW
version.dll
GetFileVersionInfoW, GetFileVersionInfoSizeW, VerQueryValueW
Export table
_MyUnhandledExceptionFilter@4
InstallCrashReport
PushDebugInfo
SetClientVersion
SetCurRcAccount
SetReportUrl

crashreport.dll

Remove crashreport.dll
MD5:   12e64e45f1338759dd9265b2f7fd6d7a
SHA1:   dad1b3498c3fcfc1697c55899cc41dd13b6b6388
SHA256:   9b4fbf6ff3d041b649d44bfdb35a9d89110c9ad402b7201be158941926a64d32

Overview

crashreport.dll is loaded as dynamic link library that runs in the context of a process. It is installed with a couple of know programs including RaidCall published by raidcall.com, RaidCall from raidcall.com and RaidCall by raidcall.com.

DetailsDetails

File name:crashreport.dll
Typical file path:C:\Program Files\raidcall\crashreport.dll
Size:88 KB (90,112 bytes)
Digital DNA
File packed:No
.NET CLR:No
More details

ResourcesPrograms

The following programs will install this file
raidcall.com
26% remove
Some version may be bundled with the OpenCandy distribution and monetization platform.

Windows OS versionsDistribution by Windows OS

OS versiondistribution
Windows 7 Ultimate 42.86%
Microsoft Windows XP 42.86%
Windows 7 Professional 14.29%

Distribution by countryDistribution by country

Brazil installs about 28.57% of crashreport.dll.

OEM distributionDistribution by PC manufacturer

PC Manufacturerdistribution
Dell 44.44%
ASUS 22.22%
American Megatrends 22.22%
Acer 11.11%
Should I remove It? Clean your PC of unwanted adware, toolbars and bloatware.

Download it for FREE