epmvolfl.sys is part of Windows (R) Codename Longhorn DDK driver and developed by Windows (R) Codename Longhorn DDK provider according to the epmvolfl.sys version information.
epmvolfl.sys's description is "Disk Performance Driver"
epmvolfl.sys is digitally signed by CHENGDU YIWO Tech Development Co., Ltd..
epmvolfl.sys is usually located in the 'C:\Windows\system32\drivers\' folder.
None of the anti-virus scanners at VirusTotal reports anything malicious about epmvolfl.sys.
If you have additional information about the file, please share it with the FreeFixer users by posting a comment at the bottom of this page.
The following is the available information on epmvolfl.sys:
Property | Value |
---|---|
Product name | Windows (R) Codename Longhorn DDK driver |
Company name | Windows (R) Codename Longhorn DDK provider |
File description | Disk Performance Driver |
Internal name | EPMVolFlt.sys |
Original filename | EPMVolFlt.sys |
Legal copyright | © Microsoft Corporation. All rights reserved. |
Product version | 6.0.6001.18000 |
File version | 6.0.6001.18000 built by: WinDDK |
Here's a screenshot of the file properties when displayed by Windows Explorer:
Product name | Windows (R) Codename Longhorn DDK dr.. |
Company name | Windows (R) Codename Longhorn DDK pr.. |
File description | Disk Performance Driver |
Internal name | EPMVolFlt.sys |
Original filename | EPMVolFlt.sys |
Legal copyright | © Microsoft Corporation. All rights.. |
Product version | 6.0.6001.18000 |
File version | 6.0.6001.18000 built by: WinDDK |
epmvolfl.sys has a valid digital signature.
Property | Value |
---|---|
Signer name | CHENGDU YIWO Tech Development Co., Ltd. |
Certificate issuer name | VeriSign Class 3 Code Signing 2010 CA |
Certificate serial number | 73ccb86b36f6c0236fea22d15300ad19 |
None of the 72 anti-virus programs at VirusTotal detected the epmvolfl.sys file.
The following information was gathered by executing the file inside Cuckoo Sandbox.
ERROR: Failed to execute process.
[ { "process_path": "C:\\Windows\\System32\\lsass.exe", "process_name": "lsass.exe", "pid": 476, "summary": {}, "first_seen": 1564192385.3281, "ppid": 376 } ]
[ { "markcount": 1, "families": [], "description": "This executable has a PDB path", "severity": 1, "marks": [ { "category": "pdb_path", "ioc": "d:\\epm\\epm12.10_release\\drivers\\epmvolflt\\objfre_wlh_amd64\\amd64\\EPMVolFlt.pdb", "type": "ioc", "description": null } ], "references": [], "name": "has_pdb" }, { "markcount": 2, "families": [], "description": "The executable contains unknown PE section names indicative of a packer (could be a false positive)", "severity": 1, "marks": [ { "category": "section", "ioc": "PAGE", "type": "ioc", "description": null }, { "category": "section", "ioc": "INIT", "type": "ioc", "description": null } ], "references": [], "name": "pe_features" } ]
The Yara rules did not detect anything in the file.
{ "tls": [], "udp": [ { "src": "192.168.56.101", "dst": "224.0.0.252", "offset": 710, "time": 1.0196869373322, "dport": 5355, "sport": 53595 }, { "src": "192.168.56.101", "dst": "224.0.0.252", "offset": 1038, "time": -0.089644193649292, "dport": 5355, "sport": 55314 }, { "src": "192.168.56.101", "dst": "239.255.255.250", "offset": 1366, "time": 1.040198802948, "dport": 3702, "sport": 49152 } ], "dns_servers": [], "http": [], "icmp": [], "smtp": [], "tcp": [], "smtp_ex": [], "mitm": [], "hosts": [], "pcap_sha256": "3f8f86cf1c48b98af8787731ccf89408b6d64a27c5de66b4eae56ea4d9a4de77", "dns": [], "http_ex": [], "domains": [], "dead_hosts": [], "sorted_pcap_sha256": "3c837f002f5c700560297ee9bc66c1caae727c35867ae96ffc61500980547ab3", "irc": [], "https_ex": [] }
Property | Value |
---|---|
MD5 | 8bf2d66be1934d63fff8d2f6883ee1b8 |
SHA256 | c1bc8fb172d07d30269f555e9e7d3b5bfcdd99f30715eededbc19ecce0df8edf |
To help other users, please let us know what you will do with epmvolfl.sys:
The poll result listed below shows what users chose to do with epmvolfl.sys. 70% have voted for removal. Based on votes from 20 users.
NOTE: Please do not use this poll as the only source of input to determine what you will do with epmvolfl.sys.
If you feel that you need more information to determine if your should keep this file or remove it, please read this guide.
Hi, my name is Roger Karlsson. I've been running this website since 2006. I want to let you know about the FreeFixer program. FreeFixer is a freeware tool that analyzes your system and let you manually identify unwanted programs. Once you've identified some malware files, FreeFixer is pretty good at removing them. You can download FreeFixer here. It runs on Windows 2000/XP/2003/2008/2016/2019/Vista/7/8/8.1/10. Supports both 32- and 64-bit Windows.
If you have questions, feedback on FreeFixer or the freefixer.com website, need help analyzing FreeFixer's scan result or just want to say hello, please contact me. You can find my email address at the contact page.
Please share with the other users what you think about this file. What does this file do? Is it legitimate or something that your computer is better without? Do you know how it was installed on your system? Did you install it yourself or did it come bundled with some other software? Is it running smoothly or do you get some error message? Any information that will help to document this file is welcome. Thank you for your contributions.
I'm reading all new comments so don't hesitate to post a question about the file. If I don't have the answer perhaps another user can help you.
Still not sure what to do with it, or why. I just got a message to reboot to check hard drive. The check completed 100%, but Win 10 Pro hung on start. Rebooted ok Ran "Whocrashed" and got the following:
------------------------
On Tue 09/02/2021 9:56:01 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: epmvolfl.sys (EPMVolFl+0x142B)
Bugcheck code: 0x7F (0x8, 0xFFFFE38022D29F50, 0xFFFFE38027203FA0, 0xFFFFF803EDEEC3E9)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\drivers\epmvolfl.sys
product: Windows (R) Codename Longhorn DDK driver
company: Windows (R) Codename Longhorn DDK provider
description: Disk Performance Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: epmvolfl.sys (Disk Performance Driver, Windows (R) Codename Longhorn DDK provider).
Google query: epmvolfl.sys Windows (R) Codename Longhorn DDK provider UNEXPECTED_KERNEL_MODE_TRAP
Conclusion
--------------------------------------------------------------------------------
One crash dump has been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
epmvolfl.sys (Disk Performance Driver, Windows (R) Codename Longhorn DDK provider)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
-----------------------------
The system is a complete reinstall after Acronis backup put a recovery boot sector on the backup drive, and then Windows 10 decided to boot from it instead of my drive C. Drive C was no longer recognised by my Bios, until I shut down, disconnected all my other drives and rebooted. The final reboot was ok and all my data is there.
# 12 Feb 2021, 5:20
CCHRISTOF writes