How to remove dxcompiler.dll
dxcompiler.dll
The module dxcompiler.dll has been detected as Trojan.Patched
dxcompiler.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft(r) DirectX for Windows(r) - Google Dawn Custom Build. The reported company name is Microsoft(r) Corporation. The current detection status is Trojan.Patched, based on the latest analysis from 2024-09-27 23:02:46 (2 years ago).
If dxcompiler.dll appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Trojan.Patched.
File Details
| Product Name: | Microsoft(r) DirectX for Windows(r) - Google Dawn Custom Build |
| Company Name: | Microsoft(r) Corporation |
| MD5: | d93db29ba0bc6d0e28767b94b369d10c |
| Size: | 24 MB |
| First Published: | 2024-09-27 23:02:46 (2 years ago) |
| Latest Published: | 2024-09-27 23:02:46 (2 years ago) |
| Status: | Trojan.Patched (on last analysis) | |
| Analysis Date: | 2024-09-27 23:02:46 (2 years ago) |
Common Places:
| %programfiles%\google\chrome\application |
ThreatInfo has observed dxcompiler.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.
Geography:
| 100.0% |
The strongest geographic signal for this file is Portugal with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
| Windows 10 | 100.0% |
The most common operating system signal for dxcompiler.dll 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.
Analysis
dxcompiler.dll is identified as pe for 64 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.
| Subsystem: | Windows CUI |
| PE Type: | pe |
| OS Bitness: | 64 |
| Image Base: | 0x0000000180000000 |
| Entry Address: | 0x013bae00 |
PE Sections:
| Name | Size of data | MD5 |
| .text | 21054464 | 0425f915c878eb2ec86a31139809093f |
| .rdata | 3952640 | 56e53f1ae9850ce21c2475ccc0e1316b |
| .data | 29696 | 001ebfa58d25cf0dfdd48152f3f3bbf5 |
| .pdata | 623616 | 176b9327ad6d63014c131f66c55952a6 |
| .gxfg | 12800 | 1aad452cd92dc28824cb377d9a7d510a |
| .retplne | 512 | 8c950f651287cbc1296bcb4e8cd7e990 |
| .tls | 512 | 1f354d76203061bfdd5a53dae48d5435 |
| _RDATA | 512 | c0f6abbe036316acb9ab4c7cf8c50131 |
| .rsrc | 1024 | 5a25c48f722488ee225a117a75155f3f |
| .reloc | 71168 | f45a2bc501ca522bb3909d88a011d7bd |
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.
More information: