Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

T3.medium Instance Freezing – (Stockholm )

0

Hi everyone, I'm experiencing an issue with my T3.medium EC2 instance (Windows Server) located in Stockholm, used primarily for MetaTrader.

For the past 2 days, the instance becomes unresponsive — either I can't connect via Remote Desktop, or if I'm already connected, the screen freezes completely and I can't do anything. After a reboot, it works normally for a while, but then the same issue happens again.

Additional info:

This issue only started recently — for about 10 days prior, everything was working fine.

No new software or configuration changes have been made. CPU credit option is set to “unlimited”, so it shouldn't be a credit-related throttle. Doesn't appear to be a port or firewall issue, since RDP works fine after reboot. It seems like the instance is crashing or freezing, rather than just dropping RDP.

Any suggestions or ideas would be greatly appreciated. Thanks!

Topics
Compute
Tags
Amazon EC2WindowsAmazon EC2 Spot Instances
Language
English

asked a year ago188 views

2 Answers
6

Would suggest to take a look at the following area:

  1. Memory Pressure or Resource Exhaustion o T3.medium has 4 GB RAM. If MetaTrader or other background services spike memory usage, the OS may become unresponsive. o Windows Server can be particularly sensitive to memory starvation, especially with GUI-based apps.
  2. Disk I/O Bottlenecks o If your instance is using standard EBS volumes (gp2 or gp3), high IOPS demand (e.g., from logging or trading activity) might cause freezing.
  3. Windows Services or Scheduled Tasks o Check for scheduled tasks (like Windows Updates or Defender scans) that might be kicking in and consuming resources.
  4. RDP Session Hangs vs. Full OS Freeze o If only RDP is freezing but the instance is still running (e.g., you can ping it or access via EC2 Serial Console), it may be a session issue rather than a full crash.
EXPERT

answered a year ago

  • LEO
    a year ago

    The root cause seems to be item number 4 mentioned above.

    I’ve realized that the issue occurs when the resolution is set to Full HD. When I lower the resolution, the problem goes away.

    Is there any way to fix this issue, or do I just have to keep using lower resolutions?

0

Hey,

Hope you're keeping well.

Since the issue started suddenly, I’d start by checking CloudWatch metrics for CPU, memory (via the CloudWatch agent), and EBS volume I/O during the freeze periods to see if there’s a resource spike. On Windows, open EC2 Serial Console or enable EC2 Rescue to troubleshoot if the OS is hanging. If you see memory pressure or high disk latency, consider moving to a larger instance type (e.g., T3.large) or using gp3 volumes with higher IOPS. Also review Windows Event Viewer for any critical system or application errors around the time of the freeze. This will help pinpoint whether it’s an OS-level issue or an EC2 resource bottleneck.

Thanks and regards,
Taz

answered 9 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content