Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
If you're running Windows 10 then check to see if it's the latest version. Update if needed and also update your graphics card drivers. Cldflt.sys is a cloud files mini driver. It might be an auto save bug since I experienced a few crashes during auto saves and beginning / ending of cinematics. Still made it through but it's got its share of bugs.
Quick and manual saves would have been nice.
The first couple of times I didn't realize that UPlay cloud sync was "on" (using that term loosely), which I ended up disabling as well, because the game wasn't saving locally, and whatever it tried to upload to the UPlay cloud seemed to be empty files. Once I disabled that, the game now saves OK locally, but like I said, the savegame file gets coruppted during the BSOD. After a couple of more run-throughs, I ended up exiting the game right after the last checkpoint immediately before the problem cut scene, and had that savegame file manually backed up in Windows Explorer. Now after it BSODs again, at least I can recover to that point and try different fixes without having to replay almost an hour worth of mostly intro cinematics (I feel like I could rehearse all the dialogues by heart at this point...)
Out of curiosity, when you had your crashes, was it usually just the game that would crash back to OS, or were you getting BSODs as well?
Thanks for your interest and reply in any case.
I like your avatar, BTW. Is that System Shock? I may be showing my age here...
Glad to see you got your issue sorted.
OneDrive is just Microsoft's cloud service (works pretty much exactly like Dropbox), it lets you synchronize your personal files between all the computers you own/have login access to...
I VERY HIGHLY RECOMMEND THAT YOU GET IN THE HABIT OF MANUALLY SAVING A COPY OF 2.save FILE TO A DIFFERENT LOCATION (say, Desktop) EVERY TIME YOU'RE DONE PLAYING FOR THE DAY, AND IMMEDIATELY AFTER YOU EXIT THE GAME.
Sorry for shouting, but I really cannot stress this enough. These BSODs will corrupt your save game files, sometimes both current and old, and if you don't have a manual backup, you will have no other option but to start from the very beginning again. 2.save seems to be the only file that matters. Make yourself a shortcut to the ...\40 folder on your Desktop, that way you can be there with a quick double-click every time you need to make a copy, or to copy your backed up version back there after a BSOD.
Now, back to the Animus Island BSOD. It seems to be fine as long as you don't try to go back there from the menu (after completing the fitfth memory, that is) but at one point, the game will automatically take you to the Island as part of the story, and if you haven't resolved the issue it'll kick you out with a BSOD at that spot (corrupting your save game files in the process, so yeah, have that backup). For me it happened after the fire battle in the port, right after you blow up the big chain. I got around it by actually disabling the cldflt.sys file temporarily, but this is a tricky thing to do, as it is a system file and requires you to have administrator privileges, as well as knowledge of how permissions work, to be able to modify the file. If you know how to do this, you can rename the file to cldflt.sy_, reboot the computer, and play through the problem area. After that you should be able to rename the file back to cldflt.sys, and all should go back to normal functionality. Knowing what I know now, however, it might just be more sensible to not complete the fifth memory of Desmond's Journey on the Island until you're pretty much done with the rest of the game.
OMFG! You're my god and savior my dude! I had this issues for a while now, both desmond memory and the lost chapters ♥♥♥♥♥♥ me over and gave me BSOD and like you said the cldflt.sys is the cause of this madness, I discarded that at first, thought "maybe its cause of the weird way they load you in and out of the areas (it wasnt like that on xbox when i played, the transition was smooth)", no joke, I have atm 7 hours of "play time" for ACR and just now completed sequence 1!! (granted like 1 maybe 2 hours was the dlc and desmonds memory, I decided to do them first but yeah)
I even wrote to ubisoft support but they are slow af! wrote them 3rd of January and got a reply 7th where they only asked for dxdiag and msinfo32 and still no reply... so i decided to check the internet about stuff, but nothing worked!
I've played ACR on xbox 360 back when it was released basically, and wanted to relive the nostalgia (as well as the entire ac series from scratch) but this glitch almost made me give up.. I'm still gonna wait for the reply from ubisoft and see what they will say about this and if they will fix it? I know the game is old but just a few days ago they updated black flag I think? and that's a pretty old one too.
Anyway, thanks for the advice about keeping a manual save, cause I doubt it's the last I've seen of the BSOD but really really hope I'll be able to get through the game.