Launcher Crashes On Launch, then Crash Report Client also Crashes!?

Development Programming & Scripting C++
, , , ,
1

I installed UE4 without incident. I then tried to launch it. I can hear my PC’s fan crank up for a second, and then go back down… and nothing happens…

I investigated a bit more by opening the task manager, and I noticed that when I click the start menu shortcut for UE4 is starts a task called the launcher, and then the task immediately closes.

I went to the event viewer, and here are the relevant events related to the crash:

Faulting application name: CrashReportClient.exe, version: 4.5.0.0, time stamp: 0x54468643
Faulting module name: CrashReportClient.exe, version: 4.5.0.0, time stamp: 0x54468643
Exception code: 0xc0000005
Fault offset: 0x00000000003d52f0
Faulting process id: 0x232c
Faulting application start time: 0x01cfef9d8d79121e
Faulting application path: [path redacted]\Epic Games\Launcher\Engine\Binaries\Win64\CrashReportClient.exe
Faulting module path: [path redacted]\Epic Games\Launcher\Engine\Binaries\Win64\CrashReportClient.exe
Report Id: ccf5df93-5b90-11e4-8826-14feb59dc625

Fault bucket 72790754, type 20
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: CrashReportClient.exe
P2: 4.5.0.0
P3: 54468643
P4: CrashReportClient.exe
P5: 4.5.0.0
P6: 54468643
P7: c0000005
P8: 00000000003d52f0
P9:
P10:

Attached files:
[path redacted]AppData\Local\Temp\WER17F2.tmp.WERInternalMetadata.xml

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: UE4-UnrealEngineLauncher
P2: 1.8.2.0
P3: 54468489
P4: UnrealEngineLauncher.exe
P5: 1.8.2.0
P6: 54468489
P7: c0000005
P8: 00000000006B4350
P9: !“[path redacted]\Epic Games\Launcher\Engine\Binaries\Win64\UnrealEngineLauncher.exe” -SaveToUserDir!AssertLog=“”
P10: ++depot+UE4-LauncherLive![path redacted]/Epic Games/Launcher/Engine/Binaries/Win64/!㶀㤈ž琀䠈֍䓈s胃鸸!2335841

Attached files:
[path redacted]/AppData/Local/UnrealEngineLauncher/Saved/Logs/Dump-1344960832.dmp
[path redacted]/AppData/Local/UnrealEngineLauncher/Saved/Logs/UnrealEngineLauncher.log
[path redacted]\AppData\Local\Temp\WERBA3.tmp.WERInternalMetadata.xml

These files may be available here:
[path redacted]\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppCrash_UE4-UnrealEngine_51fd6e5de6ab44594ebad31218bf1286415b_cab_31ee0ba3

Analysis symbol:
Rechecking for solution: 0
Report Id: cb08d56b-5b90-11e4-8826-14feb59dc625
Report Status: 4

Contents of UnrealEngineLauncher.log reveals this entry:

[2014.10.24-15.16.57:946][ 0]LogWindows: === Critical error: ===
Fatal error!

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000000

UnrealEngineLauncher.exe!UnknownFunction (0x000000013f7f4350) + 0 bytes [UnknownFile:0]
UnrealEngineLauncher.exe!UnknownFunction (0x000000013f7edbd7) + 0 bytes [UnknownFile:0]
UnrealEngineLauncher.exe!UnknownFunction (0x000000013f43a838) + 0 bytes [UnknownFile:0]
UnrealEngineLauncher.exe!UnknownFunction (0x000000013f45d3eb) + 0 bytes [UnknownFile:0]
UnrealEngineLauncher.exe!UnknownFunction (0x000000013f6b9f90) + 0 bytes [UnknownFile:0]
UnrealEngineLauncher.exe!UnknownFunction (0x000000013f709a49) + 0 bytes [UnknownFile:0]
UnrealEngineLauncher.exe!UnknownFunction (0x000000013f7106b8) + 0 bytes [UnknownFile:0]
UnrealEngineLauncher.exe!UnknownFunction (0x000000013f6d83b1) + 0 bytes [UnknownFile:0]
UnrealEngineLauncher.exe!UnknownFunction (0x000000013f747516) + 0 bytes [UnknownFile:0]
UnrealEngineLauncher.exe!UnknownFunction (0x000000013f19b6aa) + 0 bytes [UnknownFile:0]
UnrealEngineLauncher.exe!UnknownFunction (0x000000013f19a62c) + 0 bytes [UnknownFile:0]
UnrealEngineLauncher.exe!UnknownFunction (0x000000013f19aa79) + 0 bytes [UnknownFile:0]
UnrealEngineLauncher.exe!UnknownFunction (0x000000013f19bc0c) + 0 bytes [UnknownFile:0]
UnrealEngineLauncher.exe!UnknownFunction (0x000000013f8bdf25) + 0 bytes [UnknownFile:0]
kernel32.dll!UnknownFunction (0x00000000771059ed) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x000000007733c541) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x000000007733c541) + 0 bytes [UnknownFile:0]

My computer specs:
Intel Core i5 CPU M480 @ 2.67Ghz
8GB ram
windows 7 64bit professional.
Nvidia GeForce GT 420M and Intel HD Graphics

Any help would be appreciated.

2

Hi, sorry to see you’re having issues here! Immediate start up crash sounds like a known issue we had with win7 64bit that is usually fixed by SP1. Do you have that installed yet?

If that’s not it then what would help a lot is if you don’t mind zipping up and attaching the dump file from the logs folder. It’s mentioned above, you’ll find it here:

C:/username/AppData/Local/UnrealEngineLauncher/Saved/Logs/Dump-1344960832.dmp

3

Windows 7 Service Pack 1 is already installed. Here is the dump file
link text

4

Thanks! I’ll investigate asap

5

Thank you very much

6

It looks like an issue initializing the d3d renderer. I wonder if perhaps your intel HD gpu does not meet min spec, but the nvidia gpu is not being used by default.

Could you try looking in the nvidia control panel to see if you can force nvidia gpu? Just to see if that is the fix, and if so, i think for now you are able to force it force the launcher specifically. Sorry for being a bit vague but i’m not on a machine with both atm :slight_smile:

If you right-click on you desktop and select NVIDIA Control Panel, then select Manage 3D settings on the left, you should see something under the global settings tab to select preferred gpu? Select the nvidia one and apply, you may need to restart.

Let me know how that goes?

7

The preferred graphics processor is already globally set at the NVIDIA graphics processor.

8

ahh ok, sorry about that. I’ll raise the issue and let you know if we find anything else. As a long shot you could also try opengl by adding the commandline argument -opengl to the end of the Target box on your shortcut’s properties

9

still crashes using opengl

of interest in the problem signature:
Problem signature:
P1: UE4-UnrealEngineLauncher
P2: 1.8.2.0
P3: 54468489
P4: KERNELBASE.dll
P5: 6.1.7601.18409
P6: 5315a05a
P7: 00000001
P8: 000000000000940D
P9: !“[path redacted]\Epic Games\Launcher\Engine\Binaries\Win64\UnrealEngineLauncher.exe” -opengl -SaveToUserDir!AssertLog="Assertion failed: bFileFound [File:D:\BuildFarm\buildmachine_++depot+UE4-LauncherLive\Engine\Source\Developer\StandaloneRenderer\Private
P10: ++depot+UE4-LauncherLive![path redacted]/Epic Games/Launcher/Engine/Binaries/Win64/!㶀㤈ž琀䠈֍䓈s胃鸸!2335841

10

Ok, sorry for the back and forth :). If you could try without the opengl, and just -d3ddebug

This should add direct x debugging to the log files, which we’d need you to zip up and attach, after running a few times. They’re found in the same folder as the dump from above

11

Here you are.

12

forgive me, here too is the log file.

13

That log doesnt look like it was ran with the -d3ddebug command. Is there a newer one maybe? On the 9th line of the log it shows the commandline at the end so you can check there :slight_smile:

14

once again

15

So, anything?

16

I’m afraid not just yet. Adding the -d3ddebug caused the initial device creation to fail, it’s probably because you don’t have the directx debug layer installed or enabled.

If you hit the windows key, and type directx in the search box, do you see the “DirectX Control Panel (64-bit)” result? If so, when you open that you should see the “Direct3d 10.x/11” tab where there will be a “Debug Layer” section. If not you could try installing the directx sdk (June 2010) to see if re-running will then get a better log.

A dxdiag output might be helpful here too.

The only other things I can think to try right now are making sure you have the latest drivers from nvidia installed, and windows updates, and perhaps reinstall the directx runtime which you’ll find in the Launcher install directory DirectXRedist/DXSETUP.exe

17

I jumped through all the hoops, and the log still looks the same. Maybe the problem isn’t DirectX? I mean, it doesn’t even get to anything graphical… the launcher itself crashes on launch, I’m not even able to attempt to launch UE itself.

18

This latest log is still a DirectX failure, but it’s because the -d3ddebug arg is still on your shortcut, that’s clearly not working for you without the directx sdk setup.

Is it still identical if you remove that arg?

Sorry again for your problems here, I understand it’s really frustrating!!

When you say you cannot launch UE itself, do you mean you have a version of UE4 on your machine, but that also isn’t launching when you run UE4Editor.exe?

19

The DirectX SDK is installed.
The error seems to occur before any DirectX calls are made, thus there are no DirectX errors, and no debug output.
I’ll try getting logs launching the launcher sans args, right now I’m away from my pc.
Also when I say I cannot launch UE, I mean that I can’t because the launcher itself, the app that would give me the option to launch UE crashes on launch. I click the short cut, and the only thing that happens is my fan speeds up for a moment, and my mouse does the please wait wheel thing, and then the fan goes down, and the mouse cursor goes back to normal… litterally nothing else happens from a user standpoint. I had to dig through the event viewer to get the info I have shown you.
I mean the info include that both the UElauncher and the CrashReportClient are both crashing every time they are run.

20

I removed the arg, and ran the process as admin just to be sure that the errors had nothing to do with privilege and access. Now there are a plethora of resources that are unfound. I have checked the locations and verified that they are not included in my installation. :confused: