Failed to initialise
|
Hello! Everytime I try to launch PoE this error message pops up. Any ideas how to fix it?
Last bumped20 сент. 2016 г., 03:13:25
|
|
" You might want to check out this thread to see if that solutions helps you. Specifically: make sure you're running it as a user with Administrator privs. ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒░░░░░░░░░░░░░ cipher_nemo ░░░░░░░░░░░░░▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Последняя редакция: cipher_nemo#6436. Время: 19 сент. 2016 г., 13:14:23
|
|
" I can´t download Poe Front so it doesn´t help too much. +I already tried to running it as admin. |
|
" 1.) From your Client.txt file (eg: C:\Program Files (x86)\Path of Exile\logs\Client.txt), what's shown before the error? Or is this blank? 2.) Do you get past the launcher to loading the client itself? 3.) Under the properties for your shortcut, what is it pointing to? 4.) What's the rest of the error message? Screen cap or look in your Event Viewer for a record of it. ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒░░░░░░░░░░░░░ cipher_nemo ░░░░░░░░░░░░░▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Последняя редакция: cipher_nemo#6436. Время: 19 сент. 2016 г., 13:28:07
|
|
" 1)
Скрытый текст
2016/09/19 18:06:58 ***** LOG FILE OPENING *****
2016/09/19 18:07:09 186600109 fc [INFO Client 82428] Changing to device "Speakers (Realtek High Definition Audio)" 2016/09/19 18:07:10 186601046 4cd [CRIT Client 82428] Failed to initialise UI::Core with error code 3 2016/09/19 18:08:16 ***** LOG FILE OPENING ***** 2016/09/19 18:08:17 186668218 fc [INFO Client 83216] Changing to device "Speakers (Realtek High Definition Audio)" 2016/09/19 18:08:17 186668343 4cd [CRIT Client 83216] Failed to initialise UI::Core with error code 3 2016/09/19 18:09:06 ***** LOG FILE OPENING ***** 2016/09/19 18:09:07 186718015 fc [INFO Client 83872] Changing to device "Speakers (Realtek High Definition Audio)" 2016/09/19 18:09:07 186718203 52 [WARN Client 83872] FMOD Failed to load bank FMOD/Desktop/temp.bank with error code 18 2016/09/19 18:09:07 186718265 4cd [CRIT Client 83872] Failed to initialise UI::Core with error code 3 2016/09/19 18:18:59 ***** LOG FILE OPENING ***** 2016/09/19 18:19:02 ***** LOG FILE OPENING ***** 2016/09/19 18:19:03 187314062 fc [INFO Client 85256] Changing to device "Speakers (Realtek High Definition Audio)" 2016/09/19 18:19:03 187314187 4cd [CRIT Client 85256] Failed to initialise UI::Core with error code 3 2016/09/19 18:19:09 ***** LOG FILE OPENING ***** 2016/09/19 18:19:11 ***** LOG FILE OPENING ***** 2016/09/19 18:19:12 187323562 fc [INFO Client 85668] Changing to device "Speakers (Realtek High Definition Audio)" 2016/09/19 18:19:13 187323921 4cd [CRIT Client 85668] Failed to initialise UI::Core with error code 3 2016/09/19 18:20:03 ***** LOG FILE OPENING ***** 2016/09/19 18:20:05 ***** LOG FILE OPENING ***** 2016/09/19 18:20:06 187377250 fc [INFO Client 85624] Changing to device "Speakers (Realtek High Definition Audio)" 2016/09/19 18:20:06 187377359 4cd [CRIT Client 85624] Failed to initialise UI::Core with error code 3 2016/09/19 18:20:23 ***** LOG FILE OPENING ***** 2016/09/19 18:20:25 ***** LOG FILE OPENING ***** 2016/09/19 18:20:27 187397781 fc [INFO Client 85684] Changing to device "Speakers (Realtek High Definition Audio)" 2016/09/19 18:20:27 187397906 4cd [CRIT Client 85684] Failed to initialise UI::Core with error code 3 2016/09/19 18:29:47 ***** LOG FILE OPENING ***** 2016/09/19 18:29:48 187959000 fc [INFO Client 85072] Changing to device "Speakers (Realtek High Definition Audio)" 2016/09/19 18:29:48 187959125 4cd [CRIT Client 85072] Failed to initialise UI::Core with error code 3 2016/09/19 19:01:55 ***** LOG FILE OPENING ***** 2016/09/19 19:01:56 189887281 fc [INFO Client 89332] Changing to device "Speakers (Realtek High Definition Audio)" 2016/09/19 19:01:56 189887406 4cd [CRIT Client 89332] Failed to initialise UI::Core with error code 3 2) No , it pops up immediately after I click play. 3)What do you mean? 4)  |
|
" So that's the real error in your log file from #1: "Failed to initialise UI::Core with error code 3" Don't worry about #3. Instead, do you run PoE standalone or from Steam? At any rate, I've searched for this error and found something related to it, though it's quite old. Try the fix recommended in this thread: https://www.pathofexile.com/forum/view-thread/69214/page/3 ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒░░░░░░░░░░░░░ cipher_nemo ░░░░░░░░░░░░░▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ |
|
|
I´m running steam version of the game, and unfortunately nothing here seems to work.
|
|
" I'm almost out of ideas. The last four things I'd do is... 1.) Perform a pack check on your client. Guide: https://www.pathofexile.com/forum/view-thread/18531 2.) If that doesn't help, I'd just wipe the client and try again 3.) A DXDiag report for system info may give us new ideas of things to try. Use a service such as http://pastebin.com to copy and paste your info, then link it here. Guide: http://tinyurl.com/dxdiag-info-guide 4.) Contact GGG support directly to see if they can help you with this error. ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒░░░░░░░░░░░░░ cipher_nemo ░░░░░░░░░░░░░▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Последняя редакция: cipher_nemo#6436. Время: 19 сент. 2016 г., 14:47:58
|
|
" I hope this will help, somehow. + I really appreciate your help cipher :D |
|
" No problem. :-) From your DXDiag it looks like you're running the built-in Intel HD graphics on a system with a Celeron B815 1.6GHz CPU. Your processor barely makes the minimum requirements for PoE, but you have no discrete graphics (ie: AMD or NVIDIA GPU) and hence that does not meet the minimum requirements (NVIDIA GeForce 7800 GT or ATI Radeon X1950 Pro or better). That said, your "failed to initialize" issue may be completely unrelated to those specs. I've noticed that you have many error reports in the DXDiag, specifically... " Specifically, these are Windows Defender, NetSetupEngine.dll, and MpEngine. If there's a problem with the NetSetupEngine, there's a problem with Windows' system files. You can try to rememdy this a few ways... 1.) Within a command prompt with Administrator privs (to open a command prompt with Administrator privileges, follow these instructions: https://technet.microsoft.com/en-us/library/cc947813(v=ws.10).aspx ), do the following command: sfc /scannow 2.) In that same command prompt, try to register the dll by the following command: regsvr32 netsetupengine.dll 3.) Make sure Windows Defender is working correctly: http://www.tenforums.com/tutorials/5918-windows-defender-turn-off-windows-10-a.html ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒░░░░░░░░░░░░░ cipher_nemo ░░░░░░░░░░░░░▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Последняя редакция: cipher_nemo#6436. Время: 19 сент. 2016 г., 15:48:53
|
|
