Meehhhh! ED or AMD is Trolling Me.

It's crashed 5 times when loading the game.

And it's chosen to do this while I have man flu (it's actually quite bad. Lol)

So here I am, trying to roll back my driver's, and now half my desktop is off screen (and bios!)

And of course, restarting my PC takes about 4 weeks. I really need an upgrade. Lol

I just wanna fly my Anaconda home from the Pleiades, and run some missions for Federation rank, to take my mind of this collosal head/neck/back/legs/arm-ache I woke up with.
I already watched all the star trek discovery episodes. :p

I'm sure my PC never used to be this slow....

Edit:
This is the error I keep getting;
"A file has failed to load after multiple attemps as Direct3D cannot lock to buffer"

I've rolled back my AMD driver's from the latest (17.9.3), to 17.7.2. still doing the same thing.
I've also set my graphics to lowest possible.

Nothing seems to work. Currently validating game files, again.

I might just nap instead. Lol

Anyhoo, rant over.

As you were.

CMDR Cosmic Spacehead
 
Last edited:
My ED rarely crashes. Like maybe I've seen the crash report about 3-4 times since September last year.
 
- Turn PC off and unplug power for at least a minute to make sure there's nothing in RAM. Turn back on.

- Upgrade drivers to latest version.

- Open CMD window as administrator and type:

sfc /scannow

- Then run a full malwarebytes scan for anything nefarious. It's free, just don't click on the Premium version as that costs money.

https://www.malwarebytes.com

- Follow this guide from Frontier:

https://support.frontier.co.uk/kb/faq.php?id=79

- If still having stability issues, open a ticket with support and send them your DXDIAG report and log files.
 
That error is caused by something conking out in the video pipeline and ruining timing, so clear out anything that could interfere. Don't run any 3rd party screen/video capture software (the one time I saw that error with my RX480 was due to a bug in XSplit, but I won't put other software like OBS, ReLive, or whatever else there is above it), and try setting your card to max out at stock clock in WattMan.
 
It's crashed 5 times when loading the game. You should have stopped the second time.

And it's chosen to do this while I have man flu (it's actually quite bad. Lol) Hungover?

So here I am, trying to roll back my driver's, and now half my desktop is off screen (and bios!) Don't roll them back, just run the installer for the new driver. It will take care of that.

And of course, restarting my PC takes about 4 weeks. I really need an upgrade. Lol No computer should need 4 weeks to reboot. You gots major things wrong there

I just wanna fly my Anaconda home from the Pleiades, and run some missions for Federation rank, to take my mind of this collosal head/neck/back/legs/arm-ache I woke up with. Get thee to a pharmacist post-haste and get a cold remedy, there is a bad strain going around. Buy no-name, its cheaper
I already watched all the star trek discovery episodes. :p Did you see the tribble in the last one? Watch them again.

I'm sure my PC never used to be this slow.... LIAR, you just said it takes 4 weeks to reboot.

Edit:
This is the error I keep getting;
"A file has failed to load after multiple attemps as Direct3D cannot lock to buffer" You gummed it up with an imperfect rollback.

I've rolled back my AMD driver's from the latest (17.9.3), to 17.7.2. still doing the same thing. STOP DOING THAT!
I've also set my graphics to lowest possible.

Nothing seems to work. Currently validating game files, again. Restore your comp to an earlier time.

I might just nap instead. Lol Ship it to me in Toronto, I'll fix it

Anyhoo, rant over.

As you were.

CMDR Cosmic Spacehead
You're such a nut, but you are our nut!

I have an AMD card, and it was working perfectly fine yesterday night. It may not be a driver issue.

The problem is between the chair and the screen Max.
 
I have an AMD card, and it was working perfectly fine yesterday night. It may not be a driver issue.

I love my new RX550. I am an exclusive ATI user since the beginning.
They run cooler with less overhead crap running in the background.
I prefer stable over state of the art.
The game is twice as fast now for me. That's with a 6yr old build E6500 pentium too.
 
Last edited:
Well, most ignoring all advice given (thanks anyway! Lol), I've managed to run the game perfectly, using just ED64. No crashes what so ever in about an hour of travel and bounty hunting.
I also underclocked my GPU by around 10%, including the power consumption. It made no noticeable difference. (Still 60~fps everywhere).

Then rebooted the game in to ED:H 64, and continued bounty hunting for another hour or so.

No crashes!

I have no idea what sorted it.

Lol

I'm also feeling much better already. Weird not-even-24h bug....!
Which is a shame really, because I have to go to work tomorrow now. Bah!

CMDR Cosmic Spacehead
 
I love my new RX550. I am an exclusive ATI user since the beginning.
They run cooler with less overhead crap running in the background.
I prefer stable over state of the art.
The game is twice as fast now for me. That's with a 6yr old build E6500 pentium too.

That is an old pentium. I have an i5 2500k which I don't wan't to change. I may have to update soon though as my Oculus Rift keeps doing the odd thing. I am prettry sure it is CPU/Motherboard related. My GPU is an AMD Fury, which is superb and should be fine for a while.
 
Meeeehhhh, it's doing it again. Lol

"A file has failed to load after multiple attemps as Direct3D cannot lock to buffer".

I wasn't even near a planet this time. I was in Hyperspace. Lol

So I've re-updated my driver's to the absolute latest (17.10.1).

And I shall try again.... Again.

Grrr.

CMDR Cosmic Spacehead
 
What kind of an overall toaster are we talking about? You don't seem to have mentioned what GPU, CPU and how much RAM you have. Maybe your system is just Too Damn Weak for the game at this point.
 
What kind of an overall toaster are we talking about? You don't seem to have mentioned what GPU, CPU and how much RAM you have. Maybe your system is just Too Damn Weak for the game at this point.

Good point.

My specs are more or less;

  • AMD FX 8320 (turbo off)
  • Gigabyte GA-970-UD3P (I think)
  • 8Gb (2x4Gb) DDR 3 2133mhz (but stuck at 1600mhz, because it refuses to cooperate!)
  • AMD R9 280x 3Gb (latest drivers)
  • WD 1Tb HDD 7200rpm
  • Windows 10 Pro / 64Bit (fully up to date)

The game was completely stable on my old AMD HD 6870 1Gb, from 1.4, to 2.3.
Then I upgraded to the R9 280x, which was also stable during 2.3.
But since 2.4, I keep getting that error.

But that said, I just played for a good hour without getting it once. It's very unpredictable. Lol

CMDR Cosmic Spacehead
 
Yeah, it's caused by something throwing off timing or stalling the graphics pipeline. Your system should be good for the game though.

If you have anything trying to fudge with graphics, like MSI Afterburner/rivatuner or overlays (Steam?), disable that stuff. Close other applications, especially those that could try to play video or render 3D (browsers…). If you're normally playing in open mode, check if things improve if you stay in solo or a private group since having other players around can eat a lot of CPU time.
 
Yeah, it's caused by something throwing off timing or stalling the graphics pipeline. Your system should be good for the game though.

If you have anything trying to fudge with graphics, like MSI Afterburner/rivatuner or overlays (Steam?), disable that stuff. Close other applications, especially those that could try to play video or render 3D (browsers…). If you're normally playing in open mode, check if things improve if you stay in solo or a private group since having other players around can eat a lot of CPU time.

Everything is running stock, with the exception of the CPU turbo being disabled. I turned that off due to heat issues I had with it, then forgot how to re-enable it when I replaced my CPU cooler. Lol

No tuning programs, ReLive or programs running in the background. Not even AV software.
Steam overlay is enabled, but I never use it, and should probably disable it, but it's never interfered before.
First few crashes happened almost immediately after 2.4.01 was released, in Open, while landed on a planet, then I switched to Mobius, and got it again. Then solo, and kept getting it.

I updated my driver's, and validated the game files, and it worked again for a while.
Then 2.4.02 came out, and once again, I was unable to stay in the game long enough to undock from the planet. (Crashed in less than 30 seconds)
Did the same routine again, and it worked.

Then this morning, it did it, but during Hyperspace (in solo). So I updated the drivers to the very latest that only came out the other day.
And now it seems ok. For now. Lol

And now we have 2.4.03 coming. So I'm hoping I don't need to faff with drivers again. Lol

NMS has been working perfectly fine the entire time. No hints of issues with graphics.

CMDR Cosmic Spacehead
 
Back
Top Bottom