Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frequent Crashes with High-End Hardware Configuration #19149

Open
liqianljp opened this issue Jun 6, 2024 · 0 comments
Open

Frequent Crashes with High-End Hardware Configuration #19149

liqianljp opened this issue Jun 6, 2024 · 0 comments

Comments

@liqianljp
Copy link

Description

Here my system specifications
Processor: Intel i9-14900kf (5.6-6.0GMHz)
Graphics Card: NVIDIA RTX 4090
Memory: 32GB RAM DDR5
Storage: NVMe SSD
Operating System: Windows 10 (up to date)
During my gameplay sessions, DOTA2 has crashed multiple times without any apparent reason. This issue persists despite taking several troubleshooting steps, including:
Verifying Game Files: Ensured all game files are intact via the Steam client.
Updating Drivers: Confirmed that all graphics and system drivers are up to date.
Monitoring System Health: Checked hardware temperatures and system resource usage, all within normal parameters.
System Clean Boot: Ensured no conflicting software is running in the background.
Community Feedback: Noticed that many players with similar high-end configurations are facing the same issue. The community has suggested solutions like disabling CPU hyper-threading or reducing CPU frequency, which is not an ideal long-term solution.

The frequent crashes not only disrupt the gaming experience but also lead to potential penalties in ranked matches, affecting the overall enjoyment and competitiveness of the game. As someone who enjoys DOTA2 and has invested in high-performance hardware to experience it at its best, this issue is particularly frustrating.

Through community feedback, I have found temporary solutions such as disabling CPU hyper-threading or reducing CPU frequency, which suggests that the issue might be related to how DOTA2 handles these high-performance features. However, these are not ideal long-term solutions.

Example Match ID (and possibly Timestamp)

No response

Screenshots

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant