Store Page
Mount & Blade: Warband
All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Mount & Blade: Warband

Store Page
Mount & Blade: Warband >  Workshop > Faycal#6941's Workshop > Floris_Evolved > Discussions
Floris_Evolved
Description Discussions87 Comments1339 Change Notes
Slyve 13 Apr, 2016 @ 10:56am
Warband only detects 1GB of Ram, won't run without Compatibility mode.
So, now that the game is finally running at all, even though i still can't use the WSELauncher, it keeps crashing after a couple of minutes.

Turns out that the Compatibility Mode für the MB exe prevents it from detecting all my RAM. The rgl_log says i have 1024MB of RAM.

Without Compatibility Mode, the game won't run at all. Steam itself is not using the compatiblity mode.

I have no idea what to do about this. How can i get MB to detect all RAM with comp mode or, alternatively, how can i get it to run without the comp mode in win10?
< >
Showing 1-5 of 5 comments
Slyve 15 Apr, 2016 @ 1:12am 
Here is a post in the TaleWorld forums where i posted the rlg-log file. I don't wanna post it here, since it's long and would spam the post.

https://forums.taleworlds.com/index.php/topic,349420.msg8372261.html#msg8372261
#1
Slyve 15 Apr, 2016 @ 1:52am 
If i try to launch via the WSELauncher, which has never worked for me, it generates the following message in the crash log of WSE:

> Info
Time: 15/04/2016 10:49:25
Type: EXCEPTION_ACCESS_VIOLATION (0xC0000005, 0x00000000, 0x00000000)
> Stack trace
0x00000000 ??+0x0 (??+0x0)
0x5C20E8F3 nvwgf2um.dll+0x7E8F3 (OpenAdapter12+0x74313)
0x5C2E352E nvwgf2um.dll+0x15352E (OpenAdapter12+0x148F4E)
0x5B3A69C5 d3d12.dll+0x269C5 (??+0x0)
0x5B3A4350 d3d12.dll+0x24350 (??+0x0)
0x5B3AA010 d3d12.dll+0x2A010 (D3D12CoreGetLayeredDeviceSize+0x18D0)
0x5B3A7530 d3d12.dll+0x27530 (??+0x0)
0x5B3A8210 d3d12.dll+0x28210 (??+0x0)
0x5B39F87F d3d12.dll+0x1F87F (??+0x0)
0x5B39F818 d3d12.dll+0x1F818 (??+0x0)
0x5B39F66E d3d12.dll+0x1F66E (??+0x0)
0x66C26BD0 dxdiagn.dll+0x16BD0 (??+0x0)
0x66C270D3 dxdiagn.dll+0x170D3 (??+0x0)
0x66C30BA0 dxdiagn.dll+0x20BA0 (DllUnregisterServer+0x4320)
0x66C2F2FF dxdiagn.dll+0x1F2FF (DllUnregisterServer+0x2A7F)
0x66C2F100 dxdiagn.dll+0x1F100 (DllUnregisterServer+0x2880)
0x66C2CDCA dxdiagn.dll+0x1CDCA (DllUnregisterServer+0x54A)
0x005A5D04 mb_warband_old.exe+0x1A5D04 (??+0x0)
0x77814C4A ntdll.dll+0x44C4A (RtlFindActivationContextSectionString+0x1BA)
0x77814775 ntdll.dll+0x44775 (RtlDosApplyFileIsolationRedirection_Ustr+0x6E5)
0x7781CD2D ntdll.dll+0x4CD2D (LdrpResGetResourceDirectory+0xDED)
0x6603622A d3d9.dll+0x7622A (Direct3DCreate9Ex+0x2E62A)
0x6603622A d3d9.dll+0x7622A (Direct3DCreate9Ex+0x2E62A)
>

It's is the exact same message for every crash.

Never really looked at it, since it never worked from the beginning. Maybe this can help someone understand the problem. I don't really understand what i am looking at here.
#2
Faycal#6941  [developer] 15 Apr, 2016 @ 7:32pm 
Uncheck read-only property from your rgl_config.
#3
Slyve 16 Apr, 2016 @ 4:04am 
It turns out, the problems stop if i disable my second monitor. I have no idea how all of these things relate to each other and how comp mode fixed it temporarily but then screwed up ram detection.

If i disable the 2nd monitor, the game runs without comp mode and detects 4gb of ram. Which is still wrong, but at least the game runs fine. Played for about 30 minutes yesterday. No Problems.

THIS[s20.postimg.org] is my current monitor setup. Maybe the weird overall resolution had somethign to do with it. No idea.

All i know is the problems stop once the 2nd monitor is disabled.
#4
Slyve 16 Apr, 2016 @ 12:06pm 
If i start the game once with the 2nd Monitor off, it will run perfectly with both Monitors on, until it crashes again. Then it won't start up again, until i turn the second monitor off and run it once. After that, everything fine again. Something really weird is going on.

Error is even reproduceable. If i force quit the game via task manager while it's loading, it does the same thing.

And even though it runs normally now, i still cannot get it to run via the WSE Launcher. I'm missing certain features (the overhauled prisoner system, for example.) and I'm assuming it's because i don't launch via the WSELauncher.

I get a different Crash message now. It seems to have something to do with DirectX, but i wouldn't know for certain. Could be a coincidence that all the filenames appear to relate to dx.

It's the same as before. The Launcher shows up, and once i click on the play button, the launcher disappears. 2 or 3 seconds later the game exe stops running without an error message or anything.

Monitor counts are not to blame this time. I checked ;)

Here is the Message:

> Info
Time: 16/04/2016 20:53:18
Type: EXCEPTION_ACCESS_VIOLATION (0xC0000005, 0x00000000, 0x00000000)
> Stack trace
0x006E0069 mb_warband_old.exe+0x2E0069 (??+0x0)
0x6D91352E nvwgf2um.dll+0x15352E (OpenAdapter12+0x148F4E)
0x6D7269C5 d3d12.dll+0x269C5 (??+0x0)
0x6D724350 d3d12.dll+0x24350 (??+0x0)
0x6D72A010 d3d12.dll+0x2A010 (D3D12CoreGetLayeredDeviceSize+0x18D0)
0x6D727530 d3d12.dll+0x27530 (??+0x0)
0x6D728210 d3d12.dll+0x28210 (??+0x0)
0x6D71F87F d3d12.dll+0x1F87F (??+0x0)
0x6D71F818 d3d12.dll+0x1F818 (??+0x0)
0x6D71F66E d3d12.dll+0x1F66E (??+0x0)
0x6EEA6BD0 dxdiagn.dll+0x16BD0 (??+0x0)
0x6EEA70D3 dxdiagn.dll+0x170D3 (??+0x0)
0x6EEB0BA0 dxdiagn.dll+0x20BA0 (DllUnregisterServer+0x4320)
0x6EEAF2FF dxdiagn.dll+0x1F2FF (DllUnregisterServer+0x2A7F)
0x6EEAF100 dxdiagn.dll+0x1F100 (DllUnregisterServer+0x2880)
0x6EEACDCA dxdiagn.dll+0x1CDCA (DllUnregisterServer+0x54A)
0x005A6F25 mb_warband_old.exe+0x1A6F25 (??+0x0)
0x005A6F25 mb_warband_old.exe+0x1A6F25 (??+0x0)
>
Last edited by Slyve; 16 Apr, 2016 @ 12:06pm
#5
< >
Showing 1-5 of 5 comments
Per page: 1530 50