Requesting advice from computer wizards

Status
Thread Closed: Not open for further replies.

SlickPBW

S
For the past several months, I have been having a frustrating problem that I cannot solve.

Problem: Each time, after initially starting ED, 99% of the time I get a crash. This typically happens within the first 5 minutes of starting the game, whether I just sit there or start playing. The crash begins with a total system lockup, screen goes black, then the computer reboots itself. After starting the game again, the crash almost never happens again, and I can play for hours without further problems. This is so predictable that most of the time, I launch the game, wait 5 minutes or so for the crash and reboot, then relaunch and everything is fine after that.


my rig is old:
Processor Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz 3.41 GHz
Installed RAM 32.0 GB
System type 64-bit operating system, x64-based processor
Windows 10
NVIDIA GeForce GTX 1660

Other info that might be related:
  • frequently before the crash, it seems that not all the sound files initially load (usually no engine or boost sounds; also sometimes no ambient sounds or music). Then, upon engaging the FSD for either supercruise or hyperjump, a short buzz is heard from speakers, after which all sounds are normal. Since there's only a single crash, I don't think it's related to sound but I included this because it seems odd. This lack of sound does not happen after the reboot.
  • I have an old Oculus Rift, which I normally don't use, but the Oculus software loads automatically when I launch ED. I don't remember how/if I set this up, but since I don't normally play in VR, I normally close the Oculus software after it launches. The crash happens whether the Oculus software is running in the background or not.
  • I make sure that I don't have any other unnecessary things running before starting ED.
  • I have tried rebooting before starting ED and this does not seem to help.
  • I have tried logging out and logging back in before starting ED and this does not seem to help. This machine is set up with multiple logins for other family members but others rarely use it.
  • I have tried modifying/restoring numerous computer settings as well as game settings and nothing seems to help.


Does the weird single crash point to anything?
Any advice is appreciate.
 

STRONTIUM DOG

STRONTIUM DOG
add novr to commad line and disable in the in game HMD graphics options interface
1713921468592.png


do what enoch did here (rename bindings) to possibly solve crash issue

Launcher is not launching after update 18.02

Neither Odyssey nor Horizons. I get a black screen for a brief moment then back to desktop Horizons Legacy does launch How can I contact FDEV support? I have not been able to find customer support
forums.frontier.co.uk forums.frontier.co.uk
i assume your gpu drivers are up to date?
not a wizzard i am afraid more of a pettie dabbler;)
for a wizzard morbad's your man when he next appears.................
 
Last edited:

SlickPBW

S
Thanks. I will do that. However, as I mentioned above, subsequent game launches after the crash/reboot don't crash again; and although I didn't explicitly say it, the Oculus software currently launches on every launch (which I will now disable, thanks), but I don't think that's causing the crash.
 

STRONTIUM DOG

STRONTIUM DOG
regarding the sound issue its an old minor bug that older rigs get i get it from time to time btw

gpu driver update regarding crash?
as well as backing up bindings via rename try deleting the gpuworktable.xml in your products folder

does sound continue after black screen and subsquent crash..........?
 
Last edited:

Dragsham

Dragsham
I'd wait about 5 mins or so after p.o.s.t
Let the pc settle. Clear down any stuff on the task bar that's not nessesary.
Clear windows temp folder too.
Run a disk defrag or scandisk even though it ain't nessesary what with modern hard drives. But I'd argue that it won't hurt.
Have a look for a folder with a rake of crash addresses in it. Delete it.
Empty recycle bin.
Just the standard things to declutter the pc seen as its old. Defo not a temperature related issue or drivers seen as it only happens shortly after starting the pc/game.
Hope you get to the bottom of it
 

SlickPBW

S
Than
Dragsham said:
I'd wait about 5 mins or so after p.o.s.t
Let the pc settle. Clear down any stuff on the task bar that's not nessesary.
Clear windows temp folder too.
Run a disk defrag or scandisk even though it ain't nessesary what with modern hard drives. But I'd argue that it won't hurt.
Have a look for a folder with a rake of crash addresses in it. Delete it.
Empty recycle bin.
Just the standard things to declutter the pc seen as its old. Defo not a temperature related issue or drivers seen as it only happens shortly after starting the pc/game.
Hope you get to the bottom of it
Click to expand...
I’m old and don’t recognize p.o.s.t. What’s that?
 

Planewalker

Planewalker
metatheurgist said:
How long has it been since you've cleaned the PC?
Click to expand...
A pc rebooting itself can indeed often be due to heat-related issues.
Another thing i would look at is the PSU and that everything is cleaned & socketed properly.


SlickPBW said:
Than

I’m old and don’t recognize p.o.s.t. What’s that?
Click to expand...
Power On Self Test.



Are you using an XMP-profile or overclocking your RAM?
(elite really dislikes misconfigured hardware)

Also, are you running Live or Legacy, Odyssey or Horiozons?
Depending on the above, your 1660 might be struggling a bit.
(how much VRAM does it have?)

_
 
Last edited:

STRONTIUM DOG

STRONTIUM DOG
power on self test if it beeps once on boot up its the mother board saying i am ok
if it beeps more its saying i am not
type dxdiag in pc windows start and run it in there you will see a host of things driver version vram etc
typically the 1660 has 6gb which is ok really as even as low as a 4gb card can produce fairly good results if mb has good fast ram too especially if not using a hmd or a 8k high res monitor and is set to somthing like a moderate 1920 x 1080 res
 
Last edited:

SlickPBW

S
Results report #1.

- @STRONTIUM DOG you are my hero! I have created another launcher shortcut using the /novr statement and it looks very promising! I have played 3 sessions >1 hour using this shortcut with no crashes! I started each play session with a power up in order to have the same initial conditions. This may be the fix! thank you. In addition to probably fixing my crash problem, I have seen a significant performance improvement with /novr giving me increased FPS.

- @Morbad you are also my hero. I had no idea there was such a thing as the Event Viewer. Unfortunately (fortunately, now that I know?) I have lots of Warnings, Errors, and even 1 Critical entry. However, I have no idea what they mean. Is there some kind of decoder ring that explains the entries and what the recommended corrective action would be?

- @Dragsham Thanks! I still need to do the maintenance such as defrag, etc. that you have mentioned. Yep, it's been too long since my last maintenance cycle. If anything significant comes from these, I will report here. You are in the running for hero status too; I suspect that I will see a performance increase after these.

- @Planewalker please use small words lol! I don't know what an XMP profile is. I do know what overclocking is but I don't think I ever messed with it. How can I check if I had previously increased my overclocking?


Thanks again everyone!
 

STRONTIUM DOG

STRONTIUM DOG
if you have not ever run an overclocking program or entered the pc bios on startup and changed the settings within
then your pc will be at stock value meaning default balanced factory settings xmp profiles are changing ram frequencys within for possibly better performance
glad i did my part happy trails(y)
you can lignor event viewer critical errors even loads of em they are just an indicator to possibly trace a current problem in the memory etc
if your pc don't have a problem you should be fine still show a picture of them to morbad if still concerned he may spot something not quite right but it was probably something to do with with the now disabled hmd imo
 
Last edited:

Morbad

Morbad
SlickPBW said:
I had no idea there was such a thing as the Event Viewer. Unfortunately (fortunately, now that I know?) I have lots of Warnings, Errors, and even 1 Critical entry. However, I have no idea what they mean. Is there some kind of decoder ring that explains the entries and what the recommended corrective action would be?
Click to expand...

Open Event Viewer, go to Custom Views, Administrative Events. Sort by date, scroll to the time of the last crash, and take a screen shot of all the warnings and errors around that time. Often there will be a kernel-power critical error if something is crashing so hard the system reboots itself. Everything prior to and immediately after this event is what we're looking for. Post it here, I'll take a look at it.

You can also look up event IDs, then extrapolating from the source and any other details provided, plus your knowledge of the build and system state, try to infer what may have gone wrong.
 

SlickPBW

S
Results Report #2

- It seems that launching the game without VR has helped but not eliminated my crashes. I am seeing them again but not every time.

- I have defragged my drives.

@Morbad here's my screenshot of event viewer. Below all these errors are warnings with event ID's 200, 201, 202 mostly

Screenshot (1).png
 

STRONTIUM DOG

STRONTIUM DOG
so its still crashing?
hard to pin down looking like a job for https://www.resplendence.com/download/whocrashedSetup.exe or something sim imo?
but i would start with simply setting the graphic settings to all low to see if it still occurs and possibly a lower res too
i ask again are your gpu drivers up to date?
https://www.nvidia.com/en-gb/drivers/details/224165/ on the info given thus far that is the update but more card specific info available when you type dxdiag in pc start and run it
sorry if that seems like a suck eggs question but you have not answered it yet............
 
Last edited:

Morbad

Morbad
SlickPBW said:
View attachment 390992
Click to expand...

Check the other entries for the specific BugCheck ID.

Most 116 BSODs (0x00000116 is what I'm looking at) are ultimately hardware issues. Typically insufficient memory controller or I/O hub voltage, or occasionally an unstable GPU that is corrupting data in the memory addresses assigned to it.

If the other BugChecks are also predominantly 116s (list anything that isn't), we can test your memory and GPU to isolate potential errors.

Any kind of software maintenance/reconfiguration should wait until after this issue is sorted out as pushing data through a clearly flaky system will likely result in corruption sooner or later.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom