安裝 Steam
登入
|
語言
簡體中文
日本語（日文）
한국어（韓文）
ไทย（泰文）
Български（保加利亞文）
Čeština（捷克文）
Dansk（丹麥文）
Deutsch（德文）
English（英文）
Español - España（西班牙文 - 西班牙）
Español - Latinoamérica（西班牙文 - 拉丁美洲）
Ελληνικά（希臘文）
Français（法文）
Italiano（義大利文）
Bahasa Indonesia（印尼語）
Magyar（匈牙利文）
Nederlands（荷蘭文）
Norsk（挪威文）
Polski（波蘭文）
Português（葡萄牙文 - 葡萄牙）
Português - Brasil（葡萄牙文 - 巴西）
Română（羅馬尼亞文）
Русский（俄文）
Suomi（芬蘭文）
Svenska（瑞典文）
Türkçe（土耳其文）
tiếng Việt（越南文）
Українська（烏克蘭文）
回報翻譯問題
討論區規矩與守則
檢舉此篇文章
I have windows 7 ultimate - as u see i have nearly 1k playtime, i dont know how to fixx it now?!?!??!?
the game verify via steam is ok - maybe deinstall the game and re-install?
Try reinstalling your drivers?
no, dota and gta stil working fine for me
hmm, you could try _renaming_ your Fallout4 folder in Documents\My Games to see if that causes the issue (maybe one of the .ini files became corrupted).
Mind, I said renaming, since that folder also has your saved games.
For me that folder is: C:\Users\<user>\Documents\My Games\Fallout4
Yeah, I saw your post and those errors when running those commands do not seem right. At least, I recommend OP to start backing up some saved games/important files (if they aren't yet).
both commands found errors, but "fixed" in my case is nothing... it still crashes :( how this can happen? why it want load a system32 dll???? Is there no chance to fix this without a re-install of the OS?
Have you updated your video drivers recently?
Use any other memory-heavy 64 bit software, does it behave?
Anything else use DX10 or the same version of VC++ (in game folder under 'redistributable', can try installing those from that location as well)
Asides from that, you might try two things here;
1 - give FO4 an exception in whatever antivirus you're using; if it's getting tagged, the kernel may simply not be handling that action very well
2 - shut the system down, let it cool a bit, then remove your RAM. Then, put it right back in.
If the DIMMs are the same, swap them and see if anything changes up. If they aren't, make sure they go back where they came from originally. What you're doing is wiping the connection between the sockets and DIMM contacts, some of them can oxidize and if they do then odd issues can start popping up. A different problem occurring after switching DIMMS would indicate one of them has gone bad.
Run checkdisk on your system drive as well, under drive>properties>tools. Listen for any strange clicks or pops while it runs.
There is nothing here that indicates either way.
That's normal, there's supposed to be 2 diferent versions of this file to supprot both 64-bit and 32-bit applications.
Chances are your problem is a kernel mode driver issue, not a probem with the Nt kernel library file itself.
When did the problem begin? did you make any changes? If so, revert them.
Make sure the latest drivers (for everythig, not just the GPU) are installed and/or reinstall them.
Make sure your OS and system firmware is fully upd to date.
If you are using a laptop make sure that it's set to use the dedicated GPUI. The auto-detection often doesn't work right.
do a game cache integrity check
try deleting the user .ini files to reset the game to defaults.
I prefer Win10 myself, but there's nothign wrong with Win7
This doesn't necessarily mean anything. Occasional OS file errors of various types can exist and not really cause any issues.
They didn't, but the versions are more alike than unalike. it doesn't surprise me that the application would run.
Eh. Again, it depends on exactly what the "corruption" is. I've had first run fresh installations come up with "corrupted" files, yet the OS worked perfectly fine.
Then whatever it "fixed" had nothing to do with why FO4 isn't able to run.
Just because you don't understand it doesn't mean it can't happen.
Don't even worry about that. FO4 is a 64-bit application, it does not require or use ANY 32-bit dll's/system files.
There's no guarantee that will be a solution either. Unfortunately, we don't really know exactly what the issue is, but again it's MOST likely a kernel mode driver issue. so try what I suggested.
I suppose an HDD failure is possible, but there is absolutely nothing here to indicate that is the cause. Don't tell people to waste money based on nothing more than a guess.
That said, if OP really wants to check the disk for errors, he can go and get the diagnostics utilities from the manufacturer to run testing and find out.
^Not exactly right, but the line of reasoning is very sound. Most specifically the NTdll.dll file is the NT OS's kernel functions library file. literally anything in Ring0 (protected kernel mode memory space where the OS kernel and kernel mode drivers live) can and will access the kernel libraries.
Fallout 4 itself CANNOT ever (and I mean EVER) access ANYTHING in kernel mode, or directly access hardware, ever. Because if the protected nature of Ring0, Only privileged drivers (such as the the GPU's kernel mode driver like nvlddmkm.sys) can do that. In other words, Fallout has to ask the user mode driver to ask the kernel mode driver to do something. At that point, because ring 0 is a monolithic memory block, unless the application has debugging features it'so often IMPOSSIBLE to know exactly what in kernel memory space is causing the issue. We can only infer that it's a driver, VERY commonly the GPU drivers because games are so dependant on them, but sound device drivers ro any others can do it.
So again this goes back to the general advice of just "upgrade/reinstall" everything.