Game freezes when returning after months, rig not changed

Are you letting Windows 10 update hardware drivers (VR, Nvidia GPU, etc.) anytime it wants? If so go into Windows 10 and tell it to not ever update hardware drivers.

If Windows 10 is updating your Nvidia GPU drivers every time Nvidia releases a new driver that could be a major part of your problem.
 
New information - I checked the CPU (Intel i7600 4 core) today when the game froze. The game exe file was using 98% of the CPU resources.... not joking, it was literally using almost all of the CPU processing power!!!! Obviously this why the game stops streaming. I restarted the game from scratch to see what it used when loading - it was around 30% of the CPU processing power (which is where it has remained while I've been writing this post - about last 20 mins) but with no actual gameplay."

Thanks for all the info. I'll update the OP in a minute.. The CPU usage is almost certainly rather a symptom than a cause. When a thread gets stuck in an endless loop (which is one of the typical ways for freezes to happen), it is prone to max out the CPU utilization. CPU utilization of correctly running code is typically lower, as this code asks the system to wait for ressources (like: "wake me up when a network packet arrived", "wake me up when my data was written to hard disk" etc).
 
Are you letting Windows 10 update hardware drivers (VR, Nvidia GPU, etc.) anytime it wants? If so go into Windows 10 and tell it to not ever update hardware drivers.

If Windows 10 is updating your Nvidia GPU drivers every time Nvidia releases a new driver that could be a major part of your problem.

I don't always update the nVidia drivers, but every now and then use Geforce Experience to update it. As I didn't play ED for months, there were updates in between. The other software (mainly Win 10 and Oculus stuff) updates automatically. The interesting thing about this is:

- Not a new bug: some players reported this already years ago. Still there might be a different cause.
- ED seemingly more prone to this bug since 3.2
- did not change my rig except a few software parts
- no special problems with other games (and I did play a lot: X-Plane 11, VTOL-VR, Prey) - all stuff that has heavy system and GPU load

Just an update from my side: I played several hours yesterday without this issue coming up. I hope I can retry wing missions on weekend. I somehow have the feeling this is wing-related (network).
 
OK, may have the answer - corrupted or damaged system files. This can be checked using the Win 10 inbuilt tool which will find any damaged system files and repair them. Here is a link to the instructions:

https://support.microsoft.com/en-gb...er-tool-to-repair-missing-or-corrupted-system

I don't claim the credit for this solution. As mentioned earlier, I had an open ticket with FD and have been working with them for about a week on the problem. Pretty much tried everything mentioned earlier in this thread and more. Support then came up with the system file scan and repair. Did this and problem solved. So my strong recommendation, if you encounter the problem described by Conceit at the beginning of this thread, is try the scan first as you may save a lot of time and angst. : - )
 
Last edited:
OK, may have the answer - corrupted or damaged system files. This can be checked using the Win 10 inbuilt tool which will find any damaged system files and repair them. Here is a link to the instructions:

https://support.microsoft.com/en-gb...er-tool-to-repair-missing-or-corrupted-system [...]

So, I tried here, starting from file system checks on C: and the drive where ED is installed, over to DISM.exe and CSM.exe (as explained in the link). None of the tools found any errors or inconsistencies. So, I guess for me this solution didn't work. Anyhow, if the error is definitely gone for you, it might be helpful to others, so I will update the OP.
 
So, I tried here, starting from file system checks on C: and the drive where ED is installed, over to DISM.exe and CSM.exe (as explained in the link). None of the tools found any errors or inconsistencies. So, I guess for me this solution didn't work. Anyhow, if the error is definitely gone for you, it might be helpful to others, so I will update the OP.

Sorry to hear that, was hoping it was the real McCoy. It definitely helped me - 1 "freeze" in around 5 - 6 hours of play instead of every 20 mins. But something is broken and clearly ED, Nividia and DirectX do not always play together nicely. There's a number of people reporting the "buffer" problem and I've yet to find an explanation for the error, just various suggestions on how to fix it. Its frustrating because until the reason is known its just trial and error with moving targets.
 
I had 2 similar issues in the past, something was locking up and I was able to narrow it down to both MSI Afterburner(which I was using to overclock/monitor my gpu) and Malwarebytes(my AV software). Killed both those programs while running Elite Dangerous and haven't had a problem since.

Malwarebytes took offense to the network traffic back and forth and was locking me out. MSI, I'm assuming it was either the overlay itself or maybe just bad coding interfering with ED.
 
Having the exact same issue here. nVidia 1070 GPU, Oculus VR. Done a clean install of the drivers, same issue. Win 10, game mode and all associated is disabled.

Frustrating to say the least.
 
I had 2 similar issues in the past, something was locking up and I was able to narrow it down to both MSI Afterburner(which I was using to overclock/monitor my gpu) and Malwarebytes(my AV software). Killed both those programs while running Elite Dangerous and haven't had a problem since.

Malwarebytes took offense to the network traffic back and forth and was locking me out. MSI, I'm assuming it was either the overlay itself or maybe just bad coding interfering with ED.

I'm not using any of these, but I more and more get the feeling the problem is more "behavior based" than process based, meaning that background task behaviors like high network traffic or CPU utilization may trigger the issue. Then, potentially many, and also very different software setups are prone to trigger the bug. I'll update the OP with your info of course and think about a better approach of narrowing these kind of things down.
 
Checked your cpu core tempratures?

Yes, I did. And also GPU temperature. Additionally, I have BIOS temperature and fan warnings active, which makes sounds on the internal buzzer if something's going wrong. Anyhow, good suggestion. Thanks. Edit: This signature... :D

Does any of you guys use "Sandboxie"?
 
OK, may have the answer - corrupted or damaged system files. This can be checked using the Win 10 inbuilt tool which will find any damaged system files and repair them. Here is a link to the instructions:

https://support.microsoft.com/en-gb...er-tool-to-repair-missing-or-corrupted-system

I don't claim the credit for this solution. As mentioned earlier, I had an open ticket with FD and have been working with them for about a week on the problem. Pretty much tried everything mentioned earlier in this thread and more. Support then came up with the system file scan and repair. Did this and problem solved. So my strong recommendation, if you encounter the problem described by Conceit at the beginning of this thread, is try the scan first as you may save a lot of time and angst. : - )


My 1st week of ED in VR was amazing then the dreaded poor performance started stutters, judders etc. I have tweaked changed reinstalled almost everything and without any success at all.
I came across this thread and ran the disk checks which did find some corruption which it duly repaired, and hey presto performance is considerably better, 90fps even in stations whereas before it 45 or less.

Many thanks

J
 
I came across this in the DCS (Digital Combat Simulator) forum where some folks are having issues with the game stuttering, much like some of us experience in ED.

DCS forum link https://forums.eagle.ru/showthread.php?t=220117

I downloaded the utility and found that (my system) the GTX 1070 & High Definition Audio Controller were sharing the same IRQ (remember them ?).
Well from the dim and distant past IIRC sharing IRQ's was not a good idea and a real PITA to resolve conflicts. So I changed the Controller to run in MSI mode thus leaving the GPU to it own IRQ (figured that was the least risky), rebooted and everything still working ok, now those devices are not sharing the same IRQ.

Link to a more detailed explanation and the utility download links https://forums.guru3d.com/threads/windows-line-based-vs-message-signaled-based-interrupts.378044/


Disclaimer :)
Please be careful with when making any changes of this nature as it might render your system un-bootable or make things worse.

However it may help YMMV after making many changes to my system from a number of suggestions in this thread and others on this board, I'm sure my system is running better than it was. Thanks to every one for there help, tips & tricks.

J
 
I came across this in the DCS (Digital Combat Simulator) forum where some folks are having issues with the game stuttering, much like some of us experience in ED.

DCS forum link https://forums.eagle.ru/showthread.php?t=220117

I downloaded the utility and found that (my system) the GTX 1070 & High Definition Audio Controller were sharing the same IRQ (remember them ?).
Well from the dim and distant past IIRC sharing IRQ's was not a good idea and a real PITA to resolve conflicts. So I changed the Controller to run in MSI mode thus leaving the GPU to it own IRQ (figured that was the least risky), rebooted and everything still working ok, now those devices are not sharing the same IRQ.

Link to a more detailed explanation and the utility download links https://forums.guru3d.com/threads/windows-line-based-vs-message-signaled-based-interrupts.378044/


Disclaimer :)
Please be careful with when making any changes of this nature as it might render your system un-bootable or make things worse.

However it may help YMMV after making many changes to my system from a number of suggestions in this thread and others on this board, I'm sure my system is running better than it was. Thanks to every one for there help, tips & tricks.

J

Updated the OP. Thanks for this bit.. OMG... IRQ conflicts.. Those were the days.. :D
 
Updated the OP. Thanks for this bit.. OMG... IRQ conflicts.. Those were the days.. :D

Yeah really, I thought they done and dusted but maybe not...

Update I have changed the Video card to MSI mode and everything appears to be working.


z9gV90R.png

J
 
Ran into this issue yesterday. Had just upgraded my R9 390 from 4.9.1 to 4.9.4, updated Afterburner for diagnostics. Went on a road trip with my Dad and, on my way around doing Power Play resupplies, hit this lock problem when trying to fly to the station 2200Ls away from the sun. I first started by making sure the GPU hadn't come loose, then tried a lower power profile (-50%). No change at all. Soon as I Super Cruise, it freezes and the error pops up. Decided to roll bag my drivers to the last version I knew worked. All's golden so far, no more error.

As a programmers note, the buffer lock isnt part of the problem, it's a symptom. The game needs to lock the buffer to draw to it. If this stays locked for too long, it will error out. My case was a bad driver. Bad files, hard to read files, bad networking can all bottleneck the process. The more strain you put on the device, the more likely it is to occur. If this happens in any other 3D program, suspect drivers. If this only happens in Elite, suspect storage. If Elite is installed on an SSD other than the OS and significant software, suspect power. If power changes make no difference, you may be plugged into the wrong GPU, or your GPU is failing you. Look into reapplying thermal paste (cracks won't show heat problems, but may cause performance problems) or try another GPU if you have one lying around. More solutions may exist, but this should help those who run across it in the near future.
 
Back
Top Bottom