Game frozen and them crashed to windows

The event log errors are file access failures, which could be anti-virus, or something wrong with the drive.

Or a network failure. Is the computer part of a domain?

I'd do more disk testing on your c:/ drive. A full chkdsk /r that will check for bad sectors. (takes a long time)

 
Last edited by a moderator:
Jugginator said:
Try running these two in the console (first uninstalls second reinstalls)

regsvr32.exe /u ntdll.dll

regsvr32.exe ntdll.dll

I'm really confident this is an OS issue.
Click to expand...
I already tried that, I follow also all the instructions of this page https://softwaretested.com/windows/how-to-fix-ntdll-dll-crash-error-on-windows-10/, but of the many crashes of the game I think only two times in the logs appeared ntdll.dll, usually the error is this: "UnityPlayer.dll caused an Illegal Instruction (0xc000001d)
  in module UnityPlayer.dll at 0033:6be85cc7" At this time I think my only solution is to reinstall windows,  I am installing right now the alpha 18.4 and I´ll try again, if this fail also it´s clear that I have a problem with the OS.

Beelzybub said:
The event log errors are file access failures, which could be anti-virus, or something wrong with the drive.

Or a network failure. Is the computer part of a domain?

I'd do more disk testing on your c:/ drive. A full chkdsk /r that will check for bad sectors. (takes a long time)
Click to expand...
I already did this and the game still crashes. The computer is not part of a domain.

 
Last edited by a moderator:
Kunish said:
I already tried that, I follow also all the instructions of this page https://softwaretested.com/windows/how-to-fix-ntdll-dll-crash-error-on-windows-10/, but of the many crashes of the game I think only two times in the logs appeared ntdll.dll, usually the error is this: "UnityPlayer.dll caused an Illegal Instruction (0xc000001d)
  in module UnityPlayer.dll at 0033:6be85cc7" At this time I think my only solution is to reinstall windows,  I am installing right now the alpha 18.4 and I´ll try again, if this fail also it´s clear that I have a problem with the OS.

I already did this and the game still crashes. The computer is not part of a domain.
Click to expand...
Yeah regardless if it's just A19 or not, this issue is 100% localized with these particular vectors of crashing, and these are Windows dlls that are failing. I recommend you not only reinstall Windows but do a hard-format on the installation drive before installing Windows again (the formatter for the Windows installer is quick, sometimes misses some things). 

Kunish said:
Ok, the game also crashes in A18.4, I attach the output log and the event log, the error was again with the UnityPlayer.dll, in the past two weeks  I've been playing also several hours at Subnautica, an Unity game, and no problems at all, maybe this week-end I´ll reinstall windows, I´ll post the results here, thanks again.

View attachment 14703 View attachment 14704
Click to expand...
Thanks for the extra observation and testing. Yeah this game really stresses everything computational alot more than other games. Games such as Subnautica are mostly GPU-stressing, 7 Days stresses your CPU, storage drive and sometimes under high settings your GPU as well. Heh this is one of the few games where upgrading from an HDD to an SSD or M.2 will improve your performance outside of load times.

Actually one more quick idea before hard formatting and reinstalling, @Kunish, you can always try "refreshing" your install. That's much quicker and you can see if that helps (and leaves your files/games alone). If that doesn't work, well it's a gamble that took like 15 - 20 mins lol

 
Last edited by a moderator:
Last edited by a moderator:
Beelzybub said:
I think that's a known bug but tfp may need more info on it. If you have a log from that session

that you made the video, it may be helpful.
Click to expand...
This happens to me too but only in my base.   Never happens outside my base.  My guess it has to do with my solar banks powering everything because before i installed them it never happened.

EDIT:  I believe it has something to do with the Text storage chests.  Started a new game and it didnt start crashing until I built a bunch of Text storage chests. @Jugginator

 
Last edited by a moderator:
Jugginator said:
Well hmm. I don't remember, did we stress test your storage device?

https://docs.microsoft.com/en-us/windows-hardware/test/hlk/testref/738735f7-245a-4b39-9d81-20339ce31fd4

You may want to try that out and then hard format that drive and reinstall Windows. 

I mean unless there's a driver(s) causing the issue... try disabling non-vital devices. Such as these two: View attachment 14728

I dont use the 3.5mm connections I use the USB headset. Shooting in the dark, here, lol.
Click to expand...
I download the windows harware lab kit, but I have no idea how to run this test, but It´s a good idea because a run a stress that put my processor and graphic card at 100% for an hour and no problems at all, At least there isn´t bad sectors.

dd.jpg

 
Last edited by a moderator:
@Kunish

You seem to have gone through all the software related possibilities, and I'm convinced at this point that you

have a hardware/driver problem. I would root through the Windows Event logs to see if there is a new clue there.

Maybe the Windows 10 Reliability Monitor will have a clue in it.

Some of your errors suggest a disk problem. I know it passed the tests though so it's hard to say what's up.

It seems to be the only clue we have to go on at this point.

Maybe have a look at the bios and see if there are any options for the nvme drive.

Is it running in pcie v4 mode? Can you switch it to pcie v3 mode? I dunno really. Are there any network drives, or

iSCSI drives?

Sometimes a system builder will accidentally leave the plastic on the thermal pad of the nvme heat sink, which

could cause errors.

An extreme test would be cloning the nvme to another drive, (an ssd) and removing it.

 
Beelzybub said:
@Kunish

You seem to have gone through all the software related possibilities, and I'm convinced at this point that you

have a hardware/driver problem. I would root through the Windows Event logs to see if there is a new clue there.

Maybe the Windows 10 Reliability Monitor will have a clue in it.

Some of your errors suggest a disk problem. I know it passed the tests though so it's hard to say what's up.

It seems to be the only clue we have to go on at this point.

Maybe have a look at the bios and see if there are any options for the nvme drive.

Is it running in pcie v4 mode? Can you switch it to pcie v3 mode? I dunno really. Are there any network drives, or

iSCSI drives?

Sometimes a system builder will accidentally leave the plastic on the thermal pad of the nvme heat sink, which

could cause errors.

An extreme test would be cloning the nvme to another drive, (an ssd) and removing it.
Click to expand...
I installed the nvme, no plastic , but I was thinking in installing windows in the other ssd and try again, the new components of my computer are motherboard, processor, memories and the nvme, I hope is not a hardware problem, but I think it have to be a windows problem or maybe some incompatibilty between the nvme, windows and the game. This week-end I´ll format the nvme and do a new install of windows, if that not work I´ll remove the nvme and install windows in the ssd, wish me luck.

 
Diskspd.exe -b8K -d60 -h -L -o2 -t4 -r -w30 -c50M c:\io.dat

You can try that out, replace c:\ with the drive letter of yours.

There is an open-source disk stress-tester called crystaldisk, it's based off of Diskspd (that's a built-in Windows function).

But... yeah I mean, I really second Beelzy in this may be a drive failure somewhere, or something of that nature. Conjecture, but SSD's aren't as long-lasting as HDDS either (if you have an HDD that has great mechanical parts, that is).

 
Kunish said:
the new components of my computer are motherboard, processor, memories and the nvme
Click to expand...
When you installed these new parts, did you keep the existing Win10 install, or start fresh?

Jugginator said:
(if you have an HDD that has great mechanical parts
Click to expand...
Off topic but, one of my crap test machines has an 80 Gb HDD from... 2002? I think?. Runs fine, reports no smart errors or block errors. One of my bug reports acually was recorded on that drive. It won't die, and as long as it's working, I can't bring myself to throw it out.

 
Beelzybub said:
When you installed these new parts, did you keep the existing Win10 install, or start fresh?

Off topic but, one of my crap test machines has an 80 Gb HDD from... 2002? I think?. Runs fine, reports no smart errors or block errors. One of my bug reports acually was recorded on that drive. It won't die, and as long as it's working, I can't bring myself to throw it out.
Click to expand...
Yeah right, if you get a good HDD it will last you forever if you don't treat it rough.

 
Jugginator said:
Diskspd.exe -b8K -d60 -h -L -o2 -t4 -r -w30 -c50M c:\io.dat

You can try that out, replace c:\ with the drive letter of yours.

There is an open-source disk stress-tester called crystaldisk, it's based off of Diskspd (that's a built-in Windows function).

But... yeah I mean, I really second Beelzy in this may be a drive failure somewhere, or something of that nature. Conjecture, but SSD's aren't as long-lasting as HDDS either (if you have an HDD that has great mechanical parts, that is).
Click to expand...
These are the results.

View attachment Diskspd.txt

Beelzybub said:
When you installed these new parts, did you keep the existing Win10 install, or start fresh?

Off topic but, one of my crap test machines has an 80 Gb HDD from... 2002? I think?. Runs fine, reports no smart errors or block errors. One of my bug reports acually was recorded on that drive. It won't die, and as long as it's working, I can't bring myself to throw it out.
Click to expand...
A fresh start in the nvme.

 
Your nvme is fast.

Really the only two concerning things are your cpu and kernal worked rather hard for the test and:

5-nines |     11.950 |      1.232 |      7.559
6-nines |    464.266 |      4.358 |    461.062

That's a huge jump in time. Normally it's a little more progressive. If a clean install doesn't work... I am kinda sorta leaning to it (drive issue) but not too sure yet.

 
Ok, I did a clean install and the game crashed again, I played for about 40 minutes in navezgane, this time I thinked that the problem was resolved, no configuration changes in the game, I only install the amd driver, steam and 7 days to die, the crash to windows desktop was faster than ever, even in the outlog the crash is not registered, I attach the output log and the event log. My only solution now is install another clean installation of windows in another disk and if this fail I´m out of options.

View attachment output_log__2020-09-17__22-24-06.txt
View attachment event log.txt

 
You must log in or register to reply here.
Back
Top