Please help. Logos 5 won't start anymore
I had some issues when upgrading my AMD graphic driver and had to delete the old Catalyst software to get it to work properly and after that Logos5B2 refuse to start. The Splash screen is visible for 5 secs and then disapear. The harddisk is working for a while but nothing more is happen.
I think maybe uninstalling AMD software deleted some necessary files and tried to start Proclaim but it refuse to start as well.
When new versions was published I try to install them today after some days abroad, but it still not works.
I'm running Win 8 Pro on an Samsung NP7 (i7-2675QM, 2.20 GHz)
My graphic card is AMD Radeon HD 6750M.
Before I updated my graphic drive everything works fine. Today everything works fine except for Logos 5 (and Proclaim).
Here is my most recent logs from Beta 3 install and try to start L5:
And here is logs from a week ago when I tried to start L5 B2 after the graphic driver update:
Any ideas someone?
Comments
-
If you are running Logos in Compatibility Mode then untick everything in the tab and try again.
Dave
===Windows 11 & Android 13
0 -
I can't tell for sure from the logs, but the problem is probably with the .NET Framework. Are there any errors logged in the Windows Event Viewer?
0 -
Thanks for replying!
I can't tell for sure from the logs, but the problem is probably with the .NET Framework.
I tried yesterday to reinstall .NET but Windows says it's OK.
Are there any errors logged in the Windows Event Viewer?
I have an error logged in Windows Event Viewer:
Screen dumps looks bad in this edit window so I paste the text from the Event Viewer below:
#1:
Felet uppstod i programmet med namn: Logos.exe, version 5.1.1.586, tidsstämpel 0x520bf6fe
, felet uppstod i modulen med namn: ntdll.dll, version 6.2.9200.16578, tidsstämpel 0x515fac6e
Undantagskod: 0xc0000374
Felförskjutning: 0x000daa3c
Process-ID: 0x13f0
Programmets starttid: 0x01ce9b697c8bf466
Sökväg till program: C:\Users\Ebbe\AppData\Local\Logos4\System\Logos.exe
Sökväg till modul: C:\WINDOWS\SYSTEM32\ntdll.dll
Rapport-ID: bcc36ae7-075c-11e3-beb3-90a4de9eaa68
Fullständigt namn på felaktigt paket:
Program-ID relativt till felaktigt paket:#2:
EventData Logos.exe 5.1.1.586 520bf6fe ntdll.dll 6.2.9200.16578 515fac6e c0000374 000daa3c 13f0 01ce9b697c8bf466 C:\Users\Ebbe\AppData\Local\Logos4\System\Logos.exe C:\WINDOWS\SYSTEM32\ntdll.dll bcc36ae7-075c-11e3-beb3-90a4de9eaa68 0 -
Here is my screen dumps as jpgs:
0 -
Maybe something is wrong in .NET?
.NET is not listed among uninstallable softwares in Windows:
Microsoft Visual C++ 2012 Redistributable (x64) and (x86) was installed during graphic driver update and since then Logos has refused to start.
0 -
I think the ntdll.dll is the problem. Probably it is corrupt in some way. I've tried to re-register it (using RegSvr32) but I get an error message something like:
Module c:\...\ntdll.dll was read but start adress to DllRegisterServer was not found. Check if c:\...\ntdll.dll is a valid DLL- or OCX-file and try again."
As I understand it the NET framework is a built in part of Win 8. What do you think?
0 -
If you are running Logos in Compatibility Mode then untick everything in the tab and try again.
Thanks Dave!
I have checked this but everything is unticked.
0 -
I've tried to re-register it (using RegSvr32) but I get an error message
RegSvr32 only works with certain types of DLLs (COM components); it doesn't work with many normal Windows DLLs (such as ntdll.dll). This error message is "normal".
As I understand it the NET framework is a built in part of Win 8. What do you think?
It is; I'm not sure if there's any way to repair it (other than repairing the whole OS).
Try opening an Administrator Command Prompt and run: sfc /scannow
0 -
It is; I'm not sure if there's any way to repair it (other than repairing the whole OS).
It is; I'm not sure if there's any way to repair it (other than repairing the whole OS).
In the end I had to repair the whole OS. Now Logos is reinstalled (still indexing) and everything feels much better. It would be great if there was a "compile all your PBBs" option.
Thank you for your efforts to help me.
0 -
Hey Everyone,
I apologize for the difficulty. We've seen a few of these come through the support line and they threw us for a bit of a loop, but it appears AMD is aware of the problem. They seem to own this (display related) DLL, and their support crew should be able to get it sorted out for you by somehow uninstalling and re-installing certain drivers. Their contact info is available here.
0
