GridinSoft Threat Intelligence

detrca.dll file report

Clean record File reputation report
MD5 7af37e180f0645901266ea41bfbab491
Latest seen 2022-09-30 23:20:54 (3 years ago)
First seen 2022-08-28 23:43:33 (3 years ago)
Size 1 MB
Publisher AMD, Inc.
Product RAIDXpert2

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2022-08-28 23:43:33 (3 years ago); latest analysis 2022-09-30 23:20:54 (3 years ago).

Publisher context

Company metadata: AMD, Inc.. Product metadata: RAIDXpert2.

Digital signature

Signed by Advanced Micro Devices, Inc.. ThreatInfo marks this publisher as trusted for this record.

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

detrca.dll is a Windows file recorded in the ThreatInfo database. It is associated with RAIDXpert2. The reported company name is AMD, Inc.. The current detection status is Clean, based on the latest analysis from 2022-09-30 23:20:54 (3 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: RAIDXpert2
Company Name: AMD, Inc.
MD5: 7af37e180f0645901266ea41bfbab491
Size: 1 MB
First Published: 2022-08-28 23:43:33 (3 years ago)
Latest Published: 2022-09-30 23:20:54 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-09-30 23:20:54 (3 years ago)
Signed By: Advanced Micro Devices, Inc.
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%programfiles%

ThreatInfo has observed detrca.dll in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.

Windows 10 80.0%
Windows 7 20.0%

The most common operating system signal for detrca.dll is Windows 10 with 80.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.

detrca.dll is identified as pe for 32-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 32-bit
Subsystem Windows CUI
Entry point 0x00030923
Image base 0x00400000

PE Sections:

Sections 5
Raw data 1052160

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 380928 bytes · 36.2% of section data
MD5 decd3b1c7dcc94209061be631a5b4725
.rdata 582144 bytes · 55.3% of section data
MD5 a38f41a66c773bf9f0afaf8ecac9405d
.data 58880 bytes · 5.6% of section data
MD5 fbc6619c6190454924430921f833538a
.rsrc 1024 bytes · 0.1% of section data
MD5 acf13a6327140f980d97415b93f6c010
.reloc 29184 bytes · 2.8% of section data
MD5 98e40624b393ffc448738106cefaf9cc

PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.

Report conclusion

This hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 7af37e180f0645901266ea41bfbab491.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.