Newcomer / Intro Guaranteed BSOD while fuel scooping?

I tried looking around for information on this, but there doesn't seem to be any technical support for the game.

Has anyone run into this? a guaranteed unrecoverable Blue Screen of Death during Fuel Scooping (and only when fuel scooping)
 
I tried looking around for information on this, but there doesn't seem to be any technical support for the game.

Has anyone run into this? a guaranteed unrecoverable Blue Screen of Death during Fuel Scooping (and only when fuel scooping)

Nope. Never had that (or any BSOD). Points to a computer issue more than a game one. Has it always been like this or did it change on a recent release (say the move to v1.5). Suggest you raise a support ticket with FD.
 
Nope. Never had that (or any BSOD). Points to a computer issue more than a game one. Has it always been like this or did it change on a recent release (say the move to v1.5). Suggest you raise a support ticket with FD.

It didn't happen in Gamma, but it has since release. I tend to discount a computer problem because it runs many other games flawlessly with no issues. I've looked for the data dump, but apparently the crash is so abrupt that all I get is "unable to create data dump" when I look through the logs.
 
What's your graphics card?

There's no "so abrupt" in Windows. If you're not able to create the crash dump that's usually another issue entirely. Have you turned off your swap file on all your hard drives?
 
It didn't happen in Gamma, but it has since release. I tend to discount a computer problem because it runs many other games flawlessly with no issues. I've looked for the data dump, but apparently the crash is so abrupt that all I get is "unable to create data dump" when I look through the logs.

Well seeing as everyone else has no problems I'm afraid it is pointing to a computer problem at your end.
 
What's your graphics card?

There's no "so abrupt" in Windows. If you're not able to create the crash dump that's usually another issue entirely. Have you turned off your swap file on all your hard drives?

Nvidia Geforce 660 Ti

I have a SSD so the page file is on a secondary drive which has no issues. My theory is that drive is in power save mode while playing Elite Dangerous (as it's not on that drive) and the system bottoms out before the drive spins up.

I'm 90% certain that whenever I figure out how to restore that log, it will give me some video card stop code. I suspect there's some graphical element about stars or refuelling that the video driver doesn't like, or at least doesn't like with the combination of graphics settings I'm using.
 
Found it. For any future googlers:

It crashes under the following conditions:
Fullscreen: Borderless
Anti-Aliasing: SMAA

They apparently don't want to work together.
 
Great that you figured that out. Whenever I get a BSOD I have a mini heart-attack, luckily I've had none since I switched to a laptop a decent while back.

Let's add some possible search words to this topic, so people with the same problem can find this thread on google a bit more easy. I know how frustrating it is to have a major game-breaking issue that nobody else seems to be familiar with.





elite dangerous ED fuel scoop blue screen of death BSOD crash E:D scoping sun star solution fix
 
Go to advanced system settings and turn off "automatically restart" on system failure; it will hang at the blue screen until you turn the power off, which gives you time to write down the stop code.
 
Found it. For any future googlers:

It crashes under the following conditions:
Fullscreen: Borderless
Anti-Aliasing: SMAA

They apparently don't want to work together.

Still a computer/config issue, I have that exact same configuration with a GTX 660 and the game works flawlessly for me. And I scoop at every jump.
 
For all you insecure guys who were being cool by telling me it's my computer: Congratulations, Sherlock, you're a genius!

The thing is, that there are so many PC configurations out there that there's no telling what single option is causing the problem. This machine has dozens of parts, I'm not going to start taking apart hardware because one game of the hundreds I own doesn't work right. On the software side there are literally hundreds of thousands of options and settings that could be the problem.. it's a big haystack.

That's why I came here. Maybe there's someone out there like me who had already searched this haystack and found the needle. I got lucky and found the workaround pretty early.
 
Welcome CMDR!

These are the three things I would check, do them in order and don't take your compy apart yet.

Nine times out of ten it's a software issue. Make sure you have all the windows updates and up to date drivers for your video card.

If that doesn't help, make sure your power supply is adequate for your computer. Today's video cards use alot of wattage.
You can look up online what your CPU, and video card use in terms of wattage.

Lastly, overheating can cause problems as well. CPU and Video card temps can easily peak out when running a resource intensive game like our beloved E: D
There's usually options to turn on High Performance for the fans in the BIOS power section, check it out. If that's not enough, add a fan or two.

Hope that helps. Any questions feel free to ask away.

I've been a builder and done support for family and friends for 25 years :)
 
Last edited:
Found it. For any future googlers:

It crashes under the following conditions:
Fullscreen: Borderless
Anti-Aliasing: SMAA

They apparently don't want to work together.

My system just recently started doing the same thing! Everything is fine unless I jump to a new system and start fuel scooping. Then crash! Video blacks out, then sound and the rest of the system locks hard. Upon reboot Win7 reports the system BSOD'd (keep forgetting to grab screenshot and/or error code).

Klaitu -- Yer not crazy and these other players that are less than helpful should be ignored.


I didn't play for a couple weeks, then played during imperial slave event with no problems jumping back and forth between HR 1064 and Cemiess (got within top 15% contribs... yay me).

The best guess I have to when this started --- after Nvidia Experience decided I wasn't running optimal settings, I chose to let it set things for me (except I forced Borderless @ 1920x1080 instead of full screen ultra high res). So I'm trying default High setting to see if this continues (will update in a day or two when time allows).

The facts: I was running fine for a couple months then started having the trouble and my hardware tests fine (see below). This points to an update of some sort causing a software conflict triggered when fuel scooping ... very strange toggle. Why only when Fuel Scooping!?! But I cannot get my system to crash any other way.


Other notes for those trolls that wanna act like they know everything and trash talk anyone with a problem:

  • i5-2500k (not OC) on Asus Z68 .. not overheating via HWMonitor nor any problems reported after 6 hr Prime95 stress (blend or small)
  • 16 GB RAM ... no errors when ran 24+ hr MEM check
  • EVGA GTX 670 4GB ... No issues on any stress/benchmark. Not overheating. Updated Nvidia driver to 347.88 and still occurs -- not driver specific (even uninstalled and reverted to older driver as double check).
  • etc etc etc ... I 've been building and testing PCs for 20+ yrs; I know what I'm doing. It's not a hardware problem.


I want to keep testing but don't like my RAID going through verification for a couple hours after each crash! :( I'd like to remove my ED config and start from scratch. Go through a bit more testing to confirm SMAA on/off toggles the problem. ... etc...

I'll post again if I find anyt'ing new.

- - - Updated - - -

WOW! ... so moving to the HIGH graphics settings: Jump to new system, start fuel scooping and video goes black. This time no full lock up! The video driver crashed (digging in to Windows logs to see what I can learn). Game dumps to desktop but the sound for the game is still working: I can hear, "fuel scooping complete".

Maybe I can continue testing without risking my RAID.



Two Event 13s in Windows System events:
The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.


If the event originated on another computer, the display information had to be saved with the event.


The following information was included with the event:


\Device\Video7
Graphics Exception: Shader Program Header 9 Error

The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.


If the event originated on another computer, the display information had to be saved with the event.


The following information was included with the event:


\Device\Video7
Graphics Exception: ESR 0x405840=0x82000200

Followed up by "Display driver nvlddmkm stopped responding and has successfully recovered."



Last update:
Seems to be fixed. I re-installed latest Nvidia Experience and told it to Optimize ED. It went ultra, DSR, Fullscreen. No problem. Went to Borderless ... no problem. Tried a few jumps with fuel scoop, no problems.
 
Last edited:
Back
Top Bottom