Credit deduction very fast

Hi team,

I have read and enabled “Web Inspect feature” to exclude all web traffics except the game item related. However, the credit deduction is still very fast.

In my opinion, this issue might be similar with the following topic:

Please check my comment and try to monitor your network traffic.

Hi Weongyo,

I did enable the logging before.
Are you able to see anything unusual from this set of logs?

Thank you for this result. When I reviewed this result, it shows IP addresses like 104.29.141.x. These IPs are belong to CloudFlare (one of CDN company) so it could be CDN and Mudfish issue.

However you said you enabled Web Inspect feature.. So it could be a different issue. For this case, please try to monitor your networkt traffics using a tool like https://www.glasswire.com/

Hi there,
There is another abnormal amount of credits deducted again.
Upon using glasswire, this is the consumption from mudfish core process.


Thank you for showing this screenshot. It helps a lot to understand what’s going on. Here is my understands:

  • 52.229.20.211 is public IP of mudfish node “US West (Washington - Azure)”. This means you were using this node.
  • 104.29.142.51 is from Discord. However this IP is a part of Cloudflare (CDN provider).
  • When I checked overall traffic usage between processes, it looks like Discord is going through Mudfish because 104.29.142.51 is one of parts in Mudfish game item “MapleStory”. :frowning: So it’s CDN and Mudfish issue.
  • If this issue happens even with Web Inspect feature enabled, it means that Discord uses other custom(?) traffics which is not a HTTP-protocol based. So Web Inspect feature doesn’t do anything for Discord traffic…

For this case, two ways to avoid this issue in my opinion might be 1) WFP Item mode.. :frowning: or 2) Create Custom Item

When i try to use item mode, these errors pop up.

However, i have allowed mudfish WPN on the list of approved apps on Windows Defender

Is there anyway to resolve this?

As you can see MUDEC_00514 document, 0x4fb means ERROR_DRIVER_BLOCKED… :frowning: So it looks like something is blocking mudwfp.sys driver.

To identify the specific reason for this block, could you please check the Windows Event Logs?

  • Press Win + R, type eventvwr.msc, and press Enter.
  • Navigate to the following path: Applications and Services Logs > Microsoft > Windows > CodeIntegrity > Operational
  • Look for Event ID 3004 (or any Error level events) that occurred at the time you tried to start the service.
  • Please share the details or a screenshot of the event description.

This information will help us pinpoint exactly why the driver is being blocked.

Hmm, sadly there isn’t any Event ID 3004 or any Error level events when I tried to start the mudfish service.