ValveSoftware / Dota2-Gameplay

Public Bug Tracker for Dota2
1.49k stars 85 forks source link

pak01.vpk file is corrupted #15737

Open moiezl opened 9 months ago

moiezl commented 9 months ago

Description

Receive this crash error, apparently has something related to ram. I had to turn off the XMP profile setting to fix this and problem has been around for a couple of months. unable to verify integrity of files and game doesn't even launch after doing so

Example Match ID (and possibly Timestamp)

No response

Screenshots

image

SpiritWinD86 commented 9 months ago

Last year i'm faced the same issue and the only thing that helped me was replacing my ram (2 sticks out of 4 ) and I haven’t had any problems since then. Usually that error is a symptom of faulty ram. If you suspect that the ram is faulty, then check it with tm5 (extreme config) or OCCT memory test, and if there is no errors, then the problem may be the disk where is the game installed (check its "health") and make sure there is free space on the disk.. Also you can try to install game on another drive (and better if it's an SSD rather than HDD) or completely delete game folder and reinstall it. https://github.com/ValveSoftware/Dota2-Gameplay/issues/8584

rownpown commented 6 months ago

having similar issues ran memtest86, memdiagnostic and both came up clean. Crystal mark info on disk and that came up clean too. This issue really only started after the latest patch. Not sure, but maybe dota doesn't play well with XMP?

robert-gogolan commented 3 months ago

Issue happens to me aswell. Symptoms:

Specs:

ThatsDrew commented 1 month ago

I am also having the exact same issue. RAM was already tested. RAM XMP was disabled. CPU overclock was disabled. Game was reinstalled, tried the launch options mentioned by other users (e.g. #8584 ) . Nothing works. None of the other games in my steam library (including other online multiplayer games with anticheat) have any issues running. If anyone could please take a look at the issue that would be great. Please let us know which kind of logs you need or how we can be further of help. This is extremely frustrating :(

see:

8584

22472

20645

20478

19695

16483

might be worth merging these/marking them as duplicate and closing them ;)