Blender 64bit triggers error on launch with a fresh Windows 8.1 install. #40642

New Issue

Klaim - A. Joel Lamotte · 2014-06-15T17:51:20+02:00

2014-06-15 17:51:20 +02:00

System Information
Fresh Windows 8.1 64bit install, up to date.
Graphic card: ATI Mobility Radeon HD 4670 (Microsoft Corporation - WDDM v1.1)
I have Python 3.4.1 installed (no other python version but I suspect that might not have an impact).
I also have Visual Studio 2013 Update 2 installed.

Blender Version
Broken: 2.70a 64bit, 2.71-RC1 64bit
Worked: 2.70a 32bit, 2.71-RC1 32bit

Short description of error

On launch, either by double clicking the install icon or by command line "blender" from the installation directory (or the unarchived output for the RC) I get a console window open with nothing displayed, and an error prompt stating:

LoadLibrary failed with error 87: The parameter is incorrect.

In command line, I tried "blender -d" to get more details, with 2.71-RC1 64Bit I get the following output before triggering the same error prompt:


D:\Downloads\web\blender-2.71-RC1-win64\blender-2.71-RC1-win64>blender -d
Switching to fully guarded memory allocator.
Blender 2.71 (sub 0)
Build: 2014-06-12 22:53:31 Windows:32bit Release
argv[0] = blender
argv[1] = -d
read file
  Version 267 sub 1 date 1970-01-01 00:00 hash

ordered
 OBCube
 OBLamp
 OBCamera

Note that the "Windows:32bit Release" part is incorrect, this is the 64bit package from the website and it is indeed a 64bit binary (I checked using "dumpbin /headers") so I suspect there is a minor issue in the RC which is not reporting the right thing.

With 2.70a 64bit installed using the installer I get apparently the same problem:


C:\Program Files\Blender Foundation\Blender>blender -d
Switching to fully guarded memory allocator.
Blender 2.70 (sub 0)
Build: 2014-04-11 06:43:29 Windows:64bit Release
argv[0] = blender
argv[1] = -d
read file
  Version 267 sub 1 date 1970-01-01 00:00 hash

ordered
 OBCube
 OBLamp
 OBCamera

Both 32 bit variants of these blender versions does launch with no error.

Exact steps for others to reproduce the error
Just launch Blender.
Since I installed Windows 8.1 (new hard drive, so totally) I didn't found any way to launch Blender in 64bit yet.

**System Information** Fresh Windows 8.1 64bit install, up to date. Graphic card: ATI Mobility Radeon HD 4670 (Microsoft Corporation - WDDM v1.1) I have Python 3.4.1 installed (no other python version but I suspect that might not have an impact). I also have Visual Studio 2013 Update 2 installed. **Blender Version** Broken: 2.70a 64bit, 2.71-RC1 64bit Worked: 2.70a 32bit, 2.71-RC1 32bit **Short description of error** On launch, either by double clicking the install icon or by command line "blender" from the installation directory (or the unarchived output for the RC) I get a console window open with nothing displayed, and an error prompt stating: ``` LoadLibrary failed with error 87: The parameter is incorrect. ``` In command line, I tried "blender -d" to get more details, with 2.71-RC1 64Bit I get the following output before triggering the same error prompt: ``` D:\Downloads\web\blender-2.71-RC1-win64\blender-2.71-RC1-win64>blender -d Switching to fully guarded memory allocator. Blender 2.71 (sub 0) Build: 2014-06-12 22:53:31 Windows:32bit Release argv[0] = blender argv[1] = -d read file Version 267 sub 1 date 1970-01-01 00:00 hash ordered OBCube OBLamp OBCamera ``` Note that the "Windows:32bit Release" part is incorrect, this is the 64bit package from the website and it is indeed a 64bit binary (I checked using "dumpbin /headers") so I suspect there is a minor issue in the RC which is not reporting the right thing. With 2.70a 64bit installed using the installer I get apparently the same problem: ``` C:\Program Files\Blender Foundation\Blender>blender -d Switching to fully guarded memory allocator. Blender 2.70 (sub 0) Build: 2014-04-11 06:43:29 Windows:64bit Release argv[0] = blender argv[1] = -d read file Version 267 sub 1 date 1970-01-01 00:00 hash ordered OBCube OBLamp OBCamera ``` Both 32 bit variants of these blender versions does launch with no error. **Exact steps for others to reproduce the error** Just launch Blender. Since I installed Windows 8.1 (new hard drive, so totally) I didn't found any way to launch Blender in 64bit yet.

Klaim - A. Joel Lamotte commented

2014-06-15 17:51:21 +02:00

Changed status to: 'Open'

Klaim - A. Joel Lamotte commented

2014-06-15 17:51:21 +02:00

Added subscriber: @klaim

Klaim - A. Joel Lamotte commented

2014-06-15 17:57:54 +02:00

"either by double clicking the install icon"

I meant "either by double clicking on the application icon after installation".

"either by double clicking the install icon" I meant "either by double clicking on the application icon after installation".

Bastien Montagne commented

2014-06-15 18:04:41 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2014-06-15 18:04:41 +02:00

That sounds like a GPU/driver issue to me? Could you try to start Blender with factory settings (--factory-startup option in commandline)?

That sounds like a GPU/driver issue to me? Could you try to start Blender with factory settings (`--factory-startup` option in commandline)?

Klaim - A. Joel Lamotte commented

2014-06-15 18:43:43 +02:00

I tried the --factory-startup option but it behave exactly as just calling blender at least for both 64bit versions.
Actually, just to check, I tried random arguments too (like afddfgsedgf) but they are not even read I think because it always trigger the same error.

I don't think it's a GPU/driver issue because it seems that blender don't even reach a point of basic initialization (I don't know the blender code but as a dev it feels like it).

Also I realized that there should be an error log somewhere in appdata but I can't find it, there is none, so it the problem seems to be too early in the launch to be logged.

My current suspicion is that the 64bit versions are dependent on something that I don't have, as the error is triggered by wrong arguments using LoadLibrary, which basically is related to dll modules loaded at runtime.

I tried the `--factory-startup` option but it behave exactly as just calling `blender` at least for both 64bit versions. Actually, just to check, I tried random arguments too (like afddfgsedgf) but they are not even read I think because it always trigger the same error. I don't think it's a GPU/driver issue because it seems that blender don't even reach a point of basic initialization (I don't know the blender code but as a dev it feels like it). Also I realized that there should be an error log somewhere in appdata but I can't find it, there is none, so it the problem seems to be too early in the launch to be logged. My current suspicion is that the 64bit versions are dependent on something that I don't have, as the error is triggered by wrong arguments using LoadLibrary, which basically is related to dll modules loaded at runtime.

Klaim - A. Joel Lamotte commented

2014-06-15 18:45:05 +02:00

Actually, the --help does work so I guess the error is after parsing arguments.

Actually, the `--help` does work so I guess the error is after parsing arguments.

Bastien Montagne commented

2014-06-15 20:05:15 +02:00

Can you please try to put ftp://ftp.blender.org/sergey/softwaregl/win64/opengl32.dll in your Blender install dir (next to the exe itself)? It’s a software implementation of OGL, if it works then the issue is your dirver somehow, else OGL (gpu) can be removed from potential causes…

Klaim - A. Joel Lamotte commented

2014-06-15 20:09:45 +02:00

So I tried this dll in the directory of both 64bit versions and it does work.
However I have trouble understanding why my driver would omit this or why blender wouldn't have access to it while I have no problem with all other opengl applications (like my own, I'm working on a game, it's using OGL).
Are you sure that blender looks in the right directories for Windows 8?

So I tried this dll in the directory of both 64bit versions and it does work. However I have trouble understanding why my driver would omit this or why blender wouldn't have access to it while I have no problem with all other opengl applications (like my own, I'm working on a game, it's using OGL). Are you sure that blender looks in the right directories for Windows 8?

Klaim - A. Joel Lamotte commented

2014-06-15 20:16:26 +02:00

Ok I don't have it on the whole computer so you are certainly right. I am trying to upgrade my driver but apparently for Mobility Radeon there is a lot of trouble. I'll report here if I manage to make it work after changing the drivers.

Bastien Montagne commented

2014-06-15 20:22:10 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2014-06-15 20:22:10 +02:00

Bastien Montagne self-assigned this 2014-06-15 20:22:10 +02:00

Bastien Montagne commented

2014-06-15 20:22:10 +02:00

Yeah, we have all kind of issues reported with win 8.1 and drivers since a few months… :/

Anyway, will close it for now, unfortunately we can’t do anything about that kind of issues (and we can always reopen if needs arise). Thanks for the report!

Yeah, we have all kind of issues reported with win 8.1 and drivers since a few months… :/ Anyway, will close it for now, unfortunately we can’t do anything about that kind of issues (and we can always reopen if needs arise). Thanks for the report!

Klaim - A. Joel Lamotte commented

2014-06-15 20:54:32 +02:00

Ok I found the issue with my driver ( explained there: http://steamcommunity.com/app/231160/discussions/0/792924952616339808/ to be short I have to force generic microsoft driver for the AMD installer to work.... and I have to remember that when I install a new window...).

Now that I fixed my driver, I can launch the 64bit versions without errors.

I would suggest to add some specific checks determining if this opengl file is actually available and then display an error that is clear on what is missing and that there is a problem with drivers. I think it would help a lot users to get directly to the source of the issue (fixing drivers issues) instead of reporting obscure errors here.

Anyway, thank you very much for the help.

Ok I found the issue with my driver ( explained there: http://steamcommunity.com/app/231160/discussions/0/792924952616339808/ to be short I have to force generic microsoft driver for the AMD installer to work.... and I have to remember that when I install a new window...). Now that I fixed my driver, I can launch the 64bit versions without errors. I would suggest to add some specific checks determining if this opengl file is actually available and then display an error that is clear on what is missing and that there is a problem with drivers. I think it would help a lot users to get directly to the source of the issue (fixing drivers issues) instead of reporting obscure errors here. Anyway, thank you very much for the help.

Michael Adelodun commented

2015-02-27 19:40:33 +01:00

Added subscriber: @Adelodun1

Michael Adelodun commented

2015-02-27 19:40:33 +01:00

just installed blender on my win8.1 on dell inspiron15 intel and its not to be loading please can anybody help

Bastien Montagne commented

2015-02-27 19:41:46 +01:00

Please do not resurrect closed issue - create new ones.

Please **do not** resurrect closed issue - create new ones.

Michael Adelodun commented

2015-02-27 20:16:35 +01:00

downloaded python still same problems

Michael Adelodun commented

2015-02-27 20:21:02 +01:00

In #40642#292110, @mont29 wrote:
Please do not resurrect closed issue - create new ones.

please what was the conclusion on the issue and what and what solutions were provided will be glad if you can send all to me on adelodun2@gmail.com

> In #40642#292110, @mont29 wrote: > Please **do not** resurrect closed issue - create new ones. please what was the conclusion on the issue and what and what solutions were provided will be glad if you can send all to me on adelodun2@gmail.com

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

Blender 64bit triggers error on launch with a fresh Windows 8.1 install. #40642