In T77498#950581, @Pascal (pascalg) wrote:

@Robert Guetzkow (rjg) I guess I have to stay at 2.82 then :(

Let me understand:
my NVidia Geforce 310M has 1GB ram (1024MB) and is OpenGL 3.3. Drivers are of 2016, so less than 10yo.
It should match the minimum requirements.

Oh great... thanks Robert.
Well, Blender should notify the user about this, instead of a crash on startup.

I've the same issues and the same log file. Running with NVidia Geforce 310M with latest drivers (342.01).

In T51721#490572, @Ray Molenkamp (LazyDodo) wrote:

The bug that caused opengl to be forced to 4.5 is without a doubt fixed and resolved (Ie i can run 2.8 on windows with mesa that only does ogl 3.3) however there may be other bugs, we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members.

How many people are still stuck with this problem? I also have a Nvidia card that supports OpenGL 3.3 and I can't start Blender 2.80.
I download the nightly builds everyday to try, but it's always crashing after run.
This bug is marked like resolved, but it's not. And 2.80 is going to be a beta release soon!

My computer supports OpenGL 3.3 (Nvidia Geforce 310M) and Blender 2.80 is still not starting. It's not resolved for me. Can you tell me how to do?

Why is this bug "Closed/Resolved" ? The problem is still here. Blender won't start without the --debug-gpu.

Thank you Brecht. The fix allowed me to start blender with the --debug-gpu parameter and play with Eevee.
Without the parameter, Blender won't start with usual: "Error: EXCEPTION_ACCESS_VIOLATION" output.

I got this log, which I didn't have before. Hope it could help:

On my Geforce 310M, Blender 2.78 always worked fine.
If I start 2.80 with command line: blender.exe -d --debug-gpu it works too and I can use Eevee and so on. So the card is ok.
The question is why the --debug-gpu thing make the deal?

I have the same problem. The console log says: