GridinSoft Threat Intelligence

PCPElam64.sys file report

Clean record File reputation report
MD5 0554719c4df9a5c2e3f2a4a814fd5395
Latest seen 2025-05-27 23:00:46 (a year ago)
First seen 2025-05-27 23:00:46 (a year ago)
Size 20 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2025-05-27 23:00:46 (a year ago); latest analysis 2025-05-27 23:00:46 (a year ago).

Digital signature

Signed by Microsoft Windows Early Launch Anti-malware Publisher. 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.

PCPElam64.sys is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2025-05-27 23:00:46 (a year 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.

MD5: 0554719c4df9a5c2e3f2a4a814fd5395
Size: 20 KB
First Published: 2025-05-27 23:00:46 (a year ago)
Latest Published: 2025-05-27 23:00:46 (a year ago)
Status: Clean (on last analysis)
Analysis Date: 2025-05-27 23:00:46 (a year ago)
Signed By: Microsoft Windows Early Launch Anti-malware Publisher
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%\pcpitstop

ThreatInfo has observed PCPElam64.sys 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 100.0%

The most common operating system signal for PCPElam64.sys is Windows 10 with 100.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.

PCPElam64.sys is identified as pe for 64-bit systems. The subsystem is Native. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 64-bit
Subsystem Native
Entry point 0x00001330
Image base 0x0000000140000000

PE Sections:

Sections 7
Raw data 10240

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

.text 4096 bytes · 40.0% of section data
MD5 773dacb1c9073080a9f414b3e56c7197
.rdata 2560 bytes · 25.0% of section data
MD5 503be134e22ebbd1a3b712e869a96050
.data 512 bytes · 5.0% of section data
MD5 633ca13212c9b92fa1eecd26f3318f44
.pdata 512 bytes · 5.0% of section data
MD5 2b907d61ee0c4a58597c22e1a68c4ea1
INIT 1024 bytes · 10.0% of section data
Uncommon name
MD5 cf74148b32016bcddd3c59b01fa7f73d
.rsrc 1024 bytes · 10.0% of section data
MD5 a46a12abb05f7213c9b08a84e07f26b7
.reloc 512 bytes · 5.0% of section data
MD5 ace7953eb053c50eb464e94909bd39a2

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 0554719c4df9a5c2e3f2a4a814fd5395.
  • 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.