2.80 refuses to complete startup to reach splash screen - always hangs grey with AMD graphics driver crash notice #58629

New Issue

Curtis Walker · 2018-12-03T17:54:47+01:00

Curtis Walker commented

2018-12-03 17:54:47 +01:00

System Information
Operating system:
System:
Manufacture: ASUSTek COMPUTER INC
Model: ASUS Desktop PC CM1855 Series
Processor: AMD FX(tm)-8120 Eight-Core Processor
Installed Memory: 10.0 GB
System Type: 64-bit Operating System, x64-based processor

Graphics card:
Display adapter: AMD Radeon HD 7600 Series
Driver Provider: Advanced Micro Devices, Inc.
Driver Date: 2014-07-04
Driver Version: 13.251.9001.1001
Digital Signer: Microsoft Windows Hardware Compatability Publisher
Device status: "This device is working properly" (as of 2018-12-03)

Virtual Memory: Total paging file size for all drivers: 4000 MB (=admin setting; changeable)

Blender Version
2.80 Beta Windows 64 bit
Blender-2.80-a205493426b-win64.zip
Downloaded 2018-12-02 about midnight

Broken: Unknown

I have tried on four different occasions recently to download and install an experimental build for Blender 2.80, and it has not worked yet. I get the same instant notice shown as soon as I launch the program: "AMD graphics driver has stopped working; driver has successfully recovered". But Blender does not get to open the splash screen: it stays all greyed out and hangs indefinitely until I must close it down using Task Manager override to exit the program.

Worked: 2.80 = Negative ; My Blender 2.79b is working just fine!

**System Information** Operating system: System: Manufacture: ASUSTek COMPUTER INC Model: ASUS Desktop PC CM1855 Series Processor: AMD FX(tm)-8120 Eight-Core Processor Installed Memory: 10.0 GB System Type: 64-bit Operating System, x64-based processor Graphics card: Display adapter: AMD Radeon HD 7600 Series Driver Provider: Advanced Micro Devices, Inc. Driver Date: 2014-07-04 Driver Version: 13.251.9001.1001 Digital Signer: Microsoft Windows Hardware Compatability Publisher Device status: "This device is working properly" (as of 2018-12-03) Virtual Memory: Total paging file size for all drivers: 4000 MB (=admin setting; changeable) **Blender Version** 2.80 Beta Windows 64 bit Blender-2.80-a205493426b-win64.zip Downloaded 2018-12-02 about midnight Broken: Unknown I have tried on four different occasions recently to download and install an experimental build for Blender 2.80, and it has not worked yet. I get the same instant notice shown as soon as I launch the program: "AMD graphics driver has stopped working; driver has successfully recovered". But Blender does not get to open the splash screen: it stays all greyed out and hangs indefinitely until I must close it down using Task Manager override to exit the program. Worked: 2.80 = Negative ; My Blender 2.79b is working just fine!

Curtis Walker commented

2018-12-03 17:54:47 +01:00

Added subscriber: @Avatar108

Sebastian Parborg commented

2018-12-05 19:44:37 +01:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2018-12-05 19:44:37 +01:00

I can't say I'm certain, but I had problems like this on Linux with my AMD 290x sometime during summer this year. However after some new GPU driver updates this was resolved. I'm guessing that this is a driver problem.

If you can not find any newer drivers than the one you have from 2014, then if this is a bug with the drivers, there not much to do.

If you can't find any newer drivers (or if the problem still persists with newer) then you could try if it works when you run linux instead (as the open source drivers are still maintained for older GPUs)

I can't say I'm certain, but I had problems like this on Linux with my AMD 290x sometime during summer this year. However after some new GPU driver updates this was resolved. I'm guessing that this is a driver problem. If you can not find any newer drivers than the one you have from 2014, then if this is a bug with the drivers, there not much to do. If you can't find any newer drivers (or if the problem still persists with newer) then you could try if it works when you run linux instead (as the open source drivers are still maintained for older GPUs)

Clément Foucault was assigned by Sebastian Parborg

2018-12-07 15:25:20 +01:00

Sebastian Parborg commented

2018-12-07 15:25:20 +01:00

If updating drivers or moving to a newer blender beta does not work, try starting blender with --debug-gpu or --debug-gpu-force-workarounds and report your results here.

Curtis Walker commented

2018-12-09 05:09:13 +01:00

Hi Sebastian:
I have downloaded todays' version of Blender 2.80 and run the two debug commands from the Command Prompt window: both times did not work for me. Here is the text readout after doing both times:

C:\Users\Curtis>cd /dC:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-wi
ndows64

C:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-windows64>blender.exe -
d --debug-gpu
Switching to fully guarded memory allocator.
Blender 2.80 (sub 35)
Build: 07/12/2018 17:54 Windows Release
argv- [x] = blender.exe
argv- [x] = -d
argv- [x] = --debug-gpu
read file

Version 280 sub 24 date unknown hash unknown

Using OpenGL 4.3 debug facilities
GL application marker: Successfully hooked OpenGL debug callback.
found bundled python: C:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-w
indows64\2.80\python
GL API deprecated behavior: glLineWidth uses wide lines (parameter with
value '0x0') which are deprecated and do not work outside of the compatibility context

{End of report. Blender main screen opens but remains all greyed and just hangs "not responding" Closed by quitting Command Prompt window}

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Curtis>cd/dC:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-win
dows64

C:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-windows64>blender.exe -
- debug-gpu-force-
found bundled python: C:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-w
indows64\2.80\python
unknown argument, loading as file: --debug-gpu-force-
Error: Cannot read file 'C:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a78983
7-windows64\--debug-gpu-force-': No such file or directory
Error: argument has no '.blend' file extension, not using as new file, exiting!
C:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-windows64\--debug-gpu-force-
Saved session recovery to 'C:\Users\Curtis\AppData\Local\Temp\quit.blend'

Blender quit

C:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-windows64>

{Blender main screen flashed on and then instantly closed, after I hit Enter on the command prompt.}

My System:
Running Windows 8.1 (copyright 2013 Microsoft)
ASUS Desktop PC CM1855 Series
AMD FX9tm)-8120 Eight-Core Processor
AMD Radeon HD 7600 Series Display adapter {I ran the update for this driver yesterday at the AMD website and it returned message that the driver as installed is current and up to date; no newer drivers available}
10.0GB installed memory
64-bit Operating System, x64-based processor
No Pen or Touch Input is available for this display

I hope above reports can help your developer team discover why Blender2.80 won't run. (I just tried my Blender 3.79b, which opens and runs just fine!?)

With my regards,
Curtis Walker

Hi Sebastian: I have downloaded todays' version of Blender 2.80 and run the two debug commands from the Command Prompt window: both times did not work for me. Here is the text readout after doing both times: Microsoft Windows [Version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\Users\Curtis>cd /dC:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-wi ndows64 C:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-windows64>blender.exe - d --debug-gpu Switching to fully guarded memory allocator. Blender 2.80 (sub 35) Build: 07/12/2018 17:54 Windows Release argv- [x] = blender.exe argv- [x] = -d argv- [x] = --debug-gpu read file ``` Version 280 sub 24 date unknown hash unknown ``` Using OpenGL 4.3 debug facilities GL application marker: Successfully hooked OpenGL debug callback. found bundled python: C:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-w indows64\2.80\python GL API deprecated behavior: glLineWidth uses wide lines (parameter <width> with value '0x0') which are deprecated and do not work outside of the compatibility context {End of report. Blender main screen opens but remains all greyed and just hangs "not responding" Closed by quitting Command Prompt window} ``````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````` Microsoft Windows [Version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\Users\Curtis>cd/dC:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-win dows64 C:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-windows64>blender.exe - - debug-gpu-force- found bundled python: C:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-w indows64\2.80\python unknown argument, loading as file: --debug-gpu-force- Error: Cannot read file 'C:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a78983 7-windows64\--debug-gpu-force-': No such file or directory Error: argument has no '.blend' file extension, not using as new file, exiting! C:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-windows64\--debug-gpu-force- Saved session recovery to 'C:\Users\Curtis\AppData\Local\Temp\quit.blend' Blender quit C:\Users\Curtis\Downloads\blender-2.80.0-git.0fe5a789837-windows64> {Blender main screen flashed on and then instantly closed, after I hit Enter on the command prompt.} `````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````` My System: Running Windows 8.1 (copyright 2013 Microsoft) ASUS Desktop PC CM1855 Series AMD FX9tm)-8120 Eight-Core Processor AMD Radeon HD 7600 Series Display adapter {I ran the update for this driver yesterday at the AMD website and it returned message that the driver as installed is current and up to date; no newer drivers available} 10.0GB installed memory 64-bit Operating System, x64-based processor No Pen or Touch Input is available for this display I hope above reports can help your developer team discover why Blender2.80 won't run. (I just tried my Blender 3.79b, which opens and runs just fine!?) With my regards, Curtis Walker

Clément Foucault commented

2018-12-09 08:36:16 +01:00

You missed the full debug argument. it's --debug-gpu-force-workarounds.

It seems that both windows 8.1 and windows 10 have more recent driver version. Maybe consider updating your Operating System.

You missed the full debug argument. it's ` --debug-gpu-force-workarounds`. It seems that both windows 8.1 and windows 10 have more recent driver version. Maybe consider updating your Operating System.

Curtis Walker commented

2018-12-10 09:53:10 +01:00

Bon soir Clement:
I gathered all the Windows updates (as for as I know) for my computer tonight, installed them and restarted it; downloaded today's build blender-2.80.0-git.168a6a4bfc1-windows64, and tried again to open Blender 2.80: still hangs grey with blender.exe and AMD display driver has "stopped working; recovered successfully" and had to use Task Manager to End it again. I then ran the full Argument as stated: here is the Command Prompt report (i.e. Blender still would not load to splash screen, stays greyed out):

C:\Users\Curtis>cd d/C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-wi
ndows64
The filename, directory name, or volume label syntax is incorrect.

C:\Users\Curtis>cd /dC:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-wi
ndows64

C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-windows64>blender.exe -

debug-gpu -force-workarounds
Using OpenGL 4.3 debug facilities
GL application marker: Successfully hooked OpenGL debug callback.
found bundled python: C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-w
indows64\2.80\python
unknown argument, loading as file: -force-workarounds
Error: Cannot read file 'C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc
1-windows64-force-workarounds': No such file or directory
Error: argument has no '.blend' file extension, not using as new file, exiting!
C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-windows64-force-workar
ounds
Saved session recovery to 'C:\Users\Curtis\AppData\Local\Temp\quit.blend'

Blender quit

C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-windows64>

Perhaps I am still missing some important Windows updates, or else this AMD Display Driver I have installed on my computer will never be able to run Blender 2.8? Oh well, at least my Blender 2.79b runs fine!

C'est la Vie. Dans tous les cas, Merci Beaucoup pour tout votre très bon travail = Blender est Le Meilleur!!

Bon soir Clement: I gathered all the Windows updates (as for as I know) for my computer tonight, installed them and restarted it; downloaded today's build blender-2.80.0-git.168a6a4bfc1-windows64, and tried again to open Blender 2.80: still hangs grey with blender.exe and AMD display driver has "stopped working; recovered successfully" and had to use Task Manager to End it again. I then ran the full Argument as stated: here is the Command Prompt report (i.e. Blender still would not load to splash screen, stays greyed out): Microsoft Windows [Version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\Users\Curtis>cd d/C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-wi ndows64 The filename, directory name, or volume label syntax is incorrect. C:\Users\Curtis>cd /dC:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-wi ndows64 C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-windows64>blender.exe - - debug-gpu -force-workarounds Using OpenGL 4.3 debug facilities GL application marker: Successfully hooked OpenGL debug callback. found bundled python: C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-w indows64\2.80\python unknown argument, loading as file: -force-workarounds Error: Cannot read file 'C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc 1-windows64\-force-workarounds': No such file or directory Error: argument has no '.blend' file extension, not using as new file, exiting! C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-windows64\-force-workar ounds Saved session recovery to 'C:\Users\Curtis\AppData\Local\Temp\quit.blend' Blender quit C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-windows64> Perhaps I am still missing some important Windows updates, or else this AMD Display Driver I have installed on my computer will never be able to run Blender 2.8? Oh well, at least my Blender 2.79b runs fine! C'est la Vie. Dans tous les cas, Merci Beaucoup pour tout votre très bon travail = Blender est Le Meilleur!!

Curtis Walker commented

2018-12-10 10:01:37 +01:00

I tried the Argument again, but without the space (oops); here's the report:

C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-windows64>blender.exe -

debug-gpu-force-workarounds

GPU: Bypassing workaround detection.
GPU: OpenGL indentification strings
GPU: vendor: ATI Technologies Inc.
GPU: renderer: AMD Radeon HD 7600 Series
GPU: version: 4.3.12618 Core Profile Context 13.251.9001.1001

found bundled python: C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-w
indows64\2.80\python
GPUTexture: texture alloc failed. Not enough Video Memory.Error : EXCEPTION_AC
CESS_VIOLATION
Address : 0x00007FF6C8FDEE53
Module : C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-windows64\ble
nder.exe

C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-windows64>

I tried the Argument again, but without the space (oops); here's the report: C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-windows64>blender.exe - - debug-gpu-force-workarounds GPU: Bypassing workaround detection. GPU: OpenGL indentification strings GPU: vendor: ATI Technologies Inc. GPU: renderer: AMD Radeon HD 7600 Series GPU: version: 4.3.12618 Core Profile Context 13.251.9001.1001 found bundled python: C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-w indows64\2.80\python GPUTexture: texture alloc failed. Not enough Video Memory.Error : EXCEPTION_AC CESS_VIOLATION Address : 0x00007FF6C8FDEE53 Module : C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-windows64\ble nder.exe C:\Users\Curtis\Downloads\blender-2.80.0-git.168a6a4bfc1-windows64>

Daniele Valesani commented

2018-12-15 09:36:24 +01:00

Added subscriber: @dvalesani

Daniele Valesani commented

2018-12-15 09:36:24 +01:00

Hi Clement

My version of blender 2.80 downloaded a couple of weeks ago always worked fine. Since the beginning of this week, downloading and installing the latest version, I always get "Display driver AMD driver stopped responding and has successfully recovered." on my notebook, OS Windows 7.
The display drivers are up to date.

regards

Daniele Valesani

Hi Clement My version of blender 2.80 downloaded a couple of weeks ago always worked fine. Since the beginning of this week, downloading and installing the latest version, I always get "Display driver AMD driver stopped responding and has successfully recovered." on my notebook, OS Windows 7. The display drivers are up to date. regards Daniele Valesani

noki paike commented

2019-01-01 03:12:29 +01:00

Added subscriber: @nokipaike

noki paike commented

2019-01-01 03:12:29 +01:00

vista or windows 7 .. sux... with these video cards or drivers ..
anyway now the problem has been dammed on windows 10
the performance is at least three times higher than linux ..

on linux ..I would hope they can achieve similar results ..
this situation had been improved about a month ago .. with the last mesa - devel ..
but now changes have been made and shadow ESM and VSM and Lights no longer work ...
follow this bug report .. for detailed information ..
let's see if we solve this problem's
https://developer.blender.org/T60001

vista or windows 7 .. sux... with these video cards or drivers .. anyway now the problem has been dammed on windows 10 the performance is at least three times higher than linux .. on linux ..I would hope they can achieve similar results .. this situation had been improved about a month ago .. with the last mesa - devel .. but now changes have been made and shadow ESM and VSM and Lights no longer work ... follow this bug report .. for detailed information .. let's see if we solve this problem's https://developer.blender.org/T60001

Brecht Van Lommel commented

2019-05-23 03:32:39 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-05-23 03:32:39 +02:00

Changed status from 'Open' to: 'Archived'

Brecht Van Lommel closed this issue

2019-05-23 03:32:39 +02:00

Brecht Van Lommel commented

2019-05-23 03:32:39 +02:00

We no longer officially support this graphics card.
https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/

However it's likely this problem has been solved in the meantime, since there's been many fixes since this report.

We no longer officially support this graphics card. https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/ However it's likely this problem has been solved in the meantime, since there's been many fixes since this report.

Robert Rose commented

2020-03-17 04:41:08 +01:00

Added subscriber: @rtrose87

Robert Rose commented

2020-03-17 04:41:08 +01:00

I've been looking to solve this problem for over a week.

In #58629#685861, @brecht wrote:
We no longer officially support this graphics card.
https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/

However it's likely this problem has been solved in the meantime, since there's been many fixes since this report.

Then I found this, low and behold my gpu is on the amd list.

I've been looking to solve this problem for over a week. > In #58629#685861, @brecht wrote: > We no longer officially support this graphics card. > https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/ > > However it's likely this problem has been solved in the meantime, since there's been many fixes since this report. Then I found this, low and behold my gpu is on the amd list.

Brecht Van Lommel commented

2020-03-17 08:44:31 +01:00

@rtrose87, that page links to a list of all AMD GPUs. If it's supported or not depends on the architecture (Terascale no, GCN yes).

In general the main thing to do is install the latest graphics drivers.
https://docs.blender.org/manual/en/latest/troubleshooting/gpu/windows/amd.html

@rtrose87, that page links to a list of all AMD GPUs. If it's supported or not depends on the architecture (Terascale no, GCN yes). In general the main thing to do is install the latest graphics drivers. https://docs.blender.org/manual/en/latest/troubleshooting/gpu/windows/amd.html

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

2.80 refuses to complete startup to reach splash screen - always hangs grey with AMD graphics driver crash notice #58629