Page 1 of 1

runtime error (at 399:97): could not call proc in ELDEN RING Colosseum v1.08

Posted: 03 Jun 2023, 12:09
by anon209304
hello. i've never had this kind of issue, nor could I find anything about it in google, essentially the installer file for the ELDEN RING Colosseum release throws this error immediately after starting:

Image

I've tried restarting, disabling the antivirus, redownloading, checking system file integrity, but nothing works. my operating system is Microsoft Windows [Version 10.0.19044.2965]. event viewer gives out logs for the crashes similar to this:

Code: Select all

Faulting application name: Install.tmp, version: 51.1052.0.0, time stamp: 0x4d60b06f
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2965, time stamp: 0xf18c1c30
Exception code: 0x0eedfade
Fault offset: 0x0013d6c2
Faulting process id: 0xd50
Faulting application start time: 0x01d9960a17dcd209
Faulting application path: C:\Users\rasel\AppData\Local\Temp\is-0MTQE.tmp\Install.tmp
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 1d71c89f-40c7-4f84-bff5-41941fa5ee91
Faulting package full name: 
Faulting package-relative application ID: 

Re: runtime error (at 399:97): could not call proc in ELDEN RING Colosseum v1.08

Posted: 03 Jun 2023, 15:53
by KiNG
sorry i have no idea, never seen that before. is it just that one installer or do they all do that on your system?

Re: runtime error (at 399:97): could not call proc in ELDEN RING Colosseum v1.08

Posted: 03 Jun 2023, 21:13
by anon209304
KiNG wrote: 03 Jun 2023, 15:53 sorry i have no idea, never seen that before. is it just that one installer or do they all do that on your system?
so I booted up the system in safe mode and it worked, no idea what causes it though, other installers didn't have this issue

Re: runtime error (at 399:97): could not call proc in ELDEN RING Colosseum v1.08

Posted: 03 Jun 2023, 22:03
by KiNG
anon209304 wrote: 03 Jun 2023, 21:13
KiNG wrote: 03 Jun 2023, 15:53 sorry i have no idea, never seen that before. is it just that one installer or do they all do that on your system?
so I booted up the system in safe mode and it worked, no idea what causes it though, other installers didn't have this issue
weird, the installer code constantly gets updated so lets hope the issue was corrected somewere down the line, thanx for letting us know.