It's time for Exitcode 222-231, 1028 (Access to physical device lost) - Seems fixed with Nvidia 462.07 driver hotfix.
Moderator: Moderators for English X Forum
-
- EGOSOFT
- Posts: 508
- Joined: Fri, 14. Dec 12, 11:02
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
Just to clarify so there's no confusion, regarding perf I didn't do anything for the recent beta (iirc), so thank the rest of the team for that;p
Regarding the lost-device there is one "generic" fix in that beta.
It was very hard to reproduce even with an extra sleep(10ms) call to increase the probability of it happening.
So that probably was responsible for some of the rare lost-device crashes we were getting, and is most likely completely unrelated to the 30xx crashes.
But of course nothing can be ruled out, hence why I asked you to test it.
Given the feedback so far I'd actually expect some people to still have lost-device crashes, but we'll see.
Regarding the lost-device there is one "generic" fix in that beta.
It was very hard to reproduce even with an extra sleep(10ms) call to increase the probability of it happening.
So that probably was responsible for some of the rare lost-device crashes we were getting, and is most likely completely unrelated to the 30xx crashes.
But of course nothing can be ruled out, hence why I asked you to test it.
Given the feedback so far I'd actually expect some people to still have lost-device crashes, but we'll see.
-
- Posts: 51
- Joined: Sat, 13. Aug 16, 00:43
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
@Alan Phipps, thanks for the info, I will post a bug there.
-
- Posts: 51
- Joined: Sat, 13. Aug 16, 00:43
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
Trip report:
with 4.0 beta 5 installed (after I removed a mod that was causing a rightclick problem) I am having NO crashes
I went ahead and overclocked my 3080, and I'm going on 4+ hours (edit: roughly all weekend I had 1 crash when trying out the newer nvidia bugfix, back on 461.09 now) now with no crashes.
The game is a steady 120fps (previous build maxed at 45 fps even on my newly installed 3080) The main build would not break 60fps under ANY conditions. Driver is original 461.09 (where the crashes started)
4.0 beta 5 also increased docked frames/sec by at least 4x. It really is a major difference. (edit: this reduced a bit after I started enabling all the settings to high, but it's still at least 2x faster than the v3.1 game)
NOTE TO ALL: MY Nvidia driver is the original 461.09, I have not updated it with the recommended .33 bugfix!
For the purposes of the thread topic I consider beta 4 to be a solution to the crash problem. Thank you egosoft for being so proactive, I will tell my friends.
If anyone needs specific info about my rig just PM me and I will try to help, or see my dxdiag :https://zerobin.net/?8b7b9e3ea6f4c69a#L ... /6FpV2Ja8=
Pertinent info:
Screen size is 5120x1440@240hz with the Gsync enabled (X4 game gfx settings are maxed)
Video hardware is MSI 3080RTX Gamingtrio connected with 2x into 3 separate 8(split)pin to Corsair AX1200i PSU (so, 2 cables from PSU, 1 cable is split among the first 2 8-pin ports and the 3rd port gets its own cable.
note: for troubleshooting I did try 3 separate cables and it had no effect on the frequency of crashes, but I couldn't close my tower side plate due to the bulk so I returned to my original cabling config)
Processor i7-6950X no overclock
System drive is Samsung 970 EVO nvme 2TB
System Memory is 64GB Corsair
with 4.0 beta 5 installed (after I removed a mod that was causing a rightclick problem) I am having NO crashes
I went ahead and overclocked my 3080, and I'm going on 4+ hours (edit: roughly all weekend I had 1 crash when trying out the newer nvidia bugfix, back on 461.09 now) now with no crashes.
The game is a steady 120fps (previous build maxed at 45 fps even on my newly installed 3080) The main build would not break 60fps under ANY conditions. Driver is original 461.09 (where the crashes started)
4.0 beta 5 also increased docked frames/sec by at least 4x. It really is a major difference. (edit: this reduced a bit after I started enabling all the settings to high, but it's still at least 2x faster than the v3.1 game)
NOTE TO ALL: MY Nvidia driver is the original 461.09, I have not updated it with the recommended .33 bugfix!
For the purposes of the thread topic I consider beta 4 to be a solution to the crash problem. Thank you egosoft for being so proactive, I will tell my friends.
If anyone needs specific info about my rig just PM me and I will try to help, or see my dxdiag :https://zerobin.net/?8b7b9e3ea6f4c69a#L ... /6FpV2Ja8=
Pertinent info:
Screen size is 5120x1440@240hz with the Gsync enabled (X4 game gfx settings are maxed)
Video hardware is MSI 3080RTX Gamingtrio connected with 2x into 3 separate 8(split)pin to Corsair AX1200i PSU (so, 2 cables from PSU, 1 cable is split among the first 2 8-pin ports and the 3rd port gets its own cable.
note: for troubleshooting I did try 3 separate cables and it had no effect on the frequency of crashes, but I couldn't close my tower side plate due to the bulk so I returned to my original cabling config)
Processor i7-6950X no overclock
System drive is Samsung 970 EVO nvme 2TB
System Memory is 64GB Corsair
Last edited by Poopzone on Mon, 1. Feb 21, 07:02, edited 7 times in total.
-
- Posts: 51
- Joined: Sat, 13. Aug 16, 00:43
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
For the purposes of testing the nvidia bugfix driver to try to help those with the same problems I had, I did not see any difference in performance or crashing (update: 1 crash on the newest bugfix so I just reinstalled the original 460.09). At this point I'm not sure how much effect the bugfixes are having on 4.0 beta 5 except that newer ones do crash while .09 does not.
In any case, for my rig, Egosoft's 4.0 beta 5 didn't just fix crashes, it also improved the game performance in incredible ways I did not expect.
In any case, for my rig, Egosoft's 4.0 beta 5 didn't just fix crashes, it also improved the game performance in incredible ways I did not expect.
Last edited by Poopzone on Mon, 1. Feb 21, 06:57, edited 1 time in total.
-
- Posts: 403
- Joined: Tue, 17. Feb 04, 23:34
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
Which RTX3080 do you have?Poopzone wrote: ↑Sat, 30. Jan 21, 10:55 Trip report:
with beta 4.0 installed (after I removed a mod that was causing a rightclick problem) I am having NO crashes
I went ahead and overclocked my 3080, and I'm going on 4+ (edit 8+)hours now with no crashes.
The game is a steady 120fps (previous build maxed at 45 fps even on my newly installed 3080) The main build would not break 60fps under ANY conditions.
beta 4 also increased docked frames/sec by at least 4x. It really is a major difference.
NOTE TO ALL: MY Nvidia driver is the original 461.09, I have not updated it with the recommended .33 bugfix!
For the purposes of the thread topic I consider beta 4 to be a solution to the crash problem. Thank you egosoft for being so proactive, I will tell my friends.
If anyone needs specific info about my rig just PM me and I will try to help, or see my dxdiag :https://zerobin.net/?8b7b9e3ea6f4c69a#L ... /6FpV2Ja8=
Pertinent info:
Screen size is 5120x1440@240hz with the Gsync enabled (X4 game gfx settings are maxed)
Video hardware is 3080RTX
Processor i7-6950X no overclock
System drive is Samsung 970 EVO nvme 2TB
System Memory is 64GB Corsair
And how did you connect the power-cables? (daisy, seperate, 2 or 3 8-pin,...)
-
- Moderator (English)
- Posts: 31742
- Joined: Fri, 16. Apr 04, 19:21
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
To at least get the nomenclature correct, when Poopzone says beta 4.0 above they are actually referring to 4.00 beta 5. Also note that Poopzone is running a modded game, in case that is significant.
@ Poopzone: You can edit your posts here, especially when yours is still the last post in the thread. It would perhaps save you posting the same thing over and over again.
@ Poopzone: You can edit your posts here, especially when yours is still the last post in the thread. It would perhaps save you posting the same thing over and over again.

A dog has a master; a cat has domestic staff.
-
- Posts: 198
- Joined: Fri, 20. Feb 04, 22:20
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
I just sat down to play X4 for an extended time after updating to the Beta 5 patch and the Nvidia 461.40 drivers. I didn't even get a chance to load a game before I got the access to physical device lost crash. I am running an RTX 3080. I can post the dump file of that would be useful.
-
- Posts: 8218
- Joined: Fri, 26. Mar 04, 19:28
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
It can take a couple of reboots and the driver 'learning' the safe limits of your card before it runs stably. I had the same thing on the hotfix driver, but haven't crashed since, no matter how high I crank up the settings.Shepp wrote: ↑Sat, 30. Jan 21, 16:10 I just sat down to play X4 for an extended time after updating to the Beta 5 patch and the Nvidia 461.40 drivers. I didn't even get a chance to load a game before I got the access to physical device lost crash. I am running an RTX 3080. I can post the dump file of that would be useful.
-
- Posts: 51
- Joined: Sat, 13. Aug 16, 00:43
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
Roeleveld wrote: ↑Sat, 30. Jan 21, 12:30Which RTX3080 do you have?Poopzone wrote: ↑Sat, 30. Jan 21, 10:55 Trip report:
with 4.0 beta5 installed (after I removed a mod that was causing a rightclick problem) I am having NO crashes, and Nvidia driver 461.09 (original driver I started having 3080 crashes with)
I went ahead and overclocked my MSI Gamingtrio 3080 (powerlimit 102%), and I'm going on 4+ (edit 8+)hours now with no crashes. (powered by 2x 8 split-pin cables from a Corsair AX1200i)
The game is a steady 120fps (previous build maxed at 45 fps even on my newly installed 3080) The main build would not break 60fps under ANY conditions.
beta 4 also increased docked frames/sec by at least 4x. It really is a major difference.
NOTE TO ALL: MY Nvidia driver is the original 461.09, I have not updated it with the recommended .33 bugfix!
For the purposes of the thread topic I consider beta 4 to be a solution to the crash problem. Thank you egosoft for being so proactive, I will tell my friends.
If anyone needs specific info about my rig just PM me and I will try to help, or see my dxdiag :https://zerobin.net/?8b7b9e3ea6f4c69a#L ... /6FpV2Ja8=
Pertinent info:
Screen size is 5120x1440@240hz with the Gsync enabled (X4 game gfx settings are maxed)
Video hardware is 3080RTX
Processor i7-6950X no overclock
System drive is Samsung 970 EVO nvme 2TB
System Memory is 64GB Corsair
And how did you connect the power-cables? (daisy, seperate, 2 or 3 8-pin,...)
-
- Posts: 51
- Joined: Sat, 13. Aug 16, 00:43
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
Updated my previous post with the requested info and correct beta ID.
-
- Posts: 51
- Joined: Sat, 13. Aug 16, 00:43
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
MSI 3080RTX Gamingtrio connected with 2x cables into 3 separate 8(split)pin ports to Corsair AX1200i PSU (so, 2 cables from PSU, 1 cable is split among the first 2 8-pin ports and the 3rd port gets its own cable.Shepp wrote: ↑Sat, 30. Jan 21, 16:10 I just sat down to play X4 for an extended time after updating to the Beta 5 patch and the Nvidia 461.40 drivers. I didn't even get a chance to load a game before I got the access to physical device lost crash. I am running an RTX 3080. I can post the dump file of that would be useful.
note: for troubleshooting I did try 3 separate cables and it had no effect on the frequency of crashes, but I couldn't close my tower side plate due to the bulk so I returned to my original cabling config)
-
- Posts: 8218
- Joined: Fri, 26. Mar 04, 19:28
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
Sorry, missed this post.Poopzone wrote: ↑Fri, 29. Jan 21, 10:25 @Gavrushka are you seeing the same mega performance increase on beta 5? Prior to this I had assumed egosofts engine was just not capable of 90+fps and I was suddenly on a build where I had to set my 240hz monitor to 120hz to handle x4 framerates that were just not happening AT ALL before that build. edit . yeah a can see an mouse input problem is probably something easy to handle but whatever beta 5 did was INCREDIBLE framerate wise. It went from 25fps to 115fps average on my 3080. I booted up my laptop with a 1070 and tried the same build, same deal. it was 19fps in a space dock with the npc models, and then approached 60fps on beta 5. What the hell happened? This cannot be a "driver problem"
I'm vsync limited during gameplay, but I do not see any drop offs in framerate at any time in any situation. - One thing I've noticed (under beta 5) is that the maximum power draw is down a ridiculous amount. - From just under 105%, I never pull more then 70% now. All the CPU cores (10700K, no overclock, but 240mm water cooled) stay under 50 Celsius! - I don't crash at all now, don't stutter or get micropauses and I would say that the combination of the new beta and (for me) the new driver has left me a happy chappy...
...and a very unhappy chappy too; if I'd known Egosoft were gonna pull this performance rabbit out of the hat, I'd not have spent GBP 2200+ on a new PC.

-
- Posts: 51
- Joined: Sat, 13. Aug 16, 00:43
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
Well, to counter that it's entriely possible that the v4 performance increases are mainly to access the capabilities of modern video hardware. It would be pretty silly if modern games are getting 200+fps and X4 was stuck with a 4-5 year old 60fps cap. So I doubt your new build went for nothing. But are you still getting the crashes on 4.0 beta 5? I am not seeing too many replies here from others so IDK if the beta is resolving the crashing like it did for me, or if my build has something odd about it. edit: and I'm sure the devs would like to knowGavrushka wrote: ↑Mon, 1. Feb 21, 07:04Poopzone wrote: ↑Fri, 29. Jan 21, 10:25 @Gavrushka are you seeing the same mega performance increase on beta 5? Prior to this I had assumed egosofts engine was just not capable of 90+fps and I was suddenly on a build where I had to set my 240hz monitor to
...and a very unhappy chappy too; if I'd known Egosoft were gonna pull this performance rabbit out of the hat, I'd not have spent GBP 2200+ on a new PC.![]()
-
- Posts: 8218
- Joined: Fri, 26. Mar 04, 19:28
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
Ah, I'd needed a new PC as my 2 year old one (I7 8700) had a mechanical drive, and it was a bottleneck in almost everything, including boot time! Comment about being unhappy was very, very tongue in cheek. I only maintain one PC for work and play, so the investment was worthwhile.
There are no crashes at all for me under beta 5. None! And, as I said prior, the power draw is so far down, I'm saving a fortune on electricity bills! - I think the absence of new reports underlines how this problem has either been seriously curtailed or even eliminated. It's human nature to report problems vociferously, but then channel Silent Bob when everything is working fine.
(And sorry for going off topic, @Alan!
)
There are no crashes at all for me under beta 5. None! And, as I said prior, the power draw is so far down, I'm saving a fortune on electricity bills! - I think the absence of new reports underlines how this problem has either been seriously curtailed or even eliminated. It's human nature to report problems vociferously, but then channel Silent Bob when everything is working fine.
(And sorry for going off topic, @Alan!

-
- Posts: 403
- Joined: Tue, 17. Feb 04, 23:34
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
I saw.
I got (since last weekend) a "MSI Suprim X RTX3080" and played for several hours yesterday.
Only rebooted once to adjust the BIOS fancurves to keep the temperatures down.
I also enabled VSync in the game-settings. (100Hz screen being fed 140+ FPS is a waste)
I have 3 seperate cables (fits and I specifically wanted this, leading to the additional wait)
Result:
No crashes
Further info:
Gentoo Linux (fully up-to-date, with a 5.10.10 kernel)
Nvidia driver 460.27.04
X4 3.30 (fully up-to-date as per 2021-01-31, NON-beta)
-
- Posts: 51
- Joined: Sat, 13. Aug 16, 00:43
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
edit: realized this joke could be taken totally the wrong way. Didn't mean to bother anyone 

Last edited by Poopzone on Wed, 3. Feb 21, 03:25, edited 1 time in total.
-
- Posts: 403
- Joined: Tue, 17. Feb 04, 23:34
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
There is no need to respond like this.
I've worked in development in the past and, in my opinion, more info is always better.
Especially in situation where issues don't consistently occur, seeing both reports where issues do and don't happen can help in isolating possible locations in the code.
-
- Posts: 51
- Joined: Sat, 13. Aug 16, 00:43
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
Roeleveld I did not mean to harm you personally, I manages to ubuntu run with game save just to save if it would hurt. I ended up with no crash and just going back to windows 10 gaming. I wish I should just use the linux Logitect drivers. I really think egosoft wants to support linux in the long term... Experimentally I have been able to run the game with Debian distro. But I cannot make this useful to those just running normal DirectxAPI.
I hope in the future we can have open access to the api for open source use, timon says below VVV this is not up to egosoft! The api needs to be properly licensed...
I hope in the future we can have open access to the api for open source use, timon says below VVV this is not up to egosoft! The api needs to be properly licensed...
Last edited by Poopzone on Mon, 1. Feb 21, 13:12, edited 2 times in total.
-
- EGOSOFT
- Posts: 508
- Joined: Fri, 14. Dec 12, 11:02
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
@Roeleveld: it is useful info, thanks
#OT: a fully free-software/hardware ecosystem is the only path out-of-the-hell;) Unfortunately that's very long-term a.k.a. it takes time and effort (from all ends);p
#OT: a fully free-software/hardware ecosystem is the only path out-of-the-hell;) Unfortunately that's very long-term a.k.a. it takes time and effort (from all ends);p
-
- Posts: 403
- Joined: Tue, 17. Feb 04, 23:34
Re: It's time for Exitcode 222-231, 1028 (Access to physical device lost)
X4 (and other games) should simply work, regardless of which OS the player prefers. Unfortunately, that is difficult to achieve, even when using a "cross-platform" method like Java. (Egosoft, please do NOT even consider this as an option!Poopzone wrote: ↑Mon, 1. Feb 21, 12:50 Roeleveld I did not mean to harm you personally, I manages to ubuntu run with game save just to save if it would hurt. I ended up with no crash and just going back to windows 10 gaming. I wish I should just use the linux Logitect drivers. I really think egosoft wants to support linux in the long term... Experimentally I have been able to run the game with Debian distro. But I cannot make this useful to those just running normal DirectxAPI.

Personally, I don't care too much about drivers being open or closed. Same goes for the libraries implementing the APIs, but the API should be the same across different platforms.
I hope in the future we can have open access to the api for open source use, timon says below VVV this is not up to egosoft! The api needs to be properly licensed...