搜索结果: *

  1. In Progress Siege still crashing after hotfix 1.05 , 1.06 and 1.07

    Fixed by the beta 1.1.0 patch on my end !

    All hail Talesworld !
  2. Resolved Crash when entering siege

    I had become a vassal of the Khuzait and was besieging the city of Zeonica (of the Western Empire, I believe).
    Of note, I had been a part of many sieges before this one without any issues, but this was the first siege for which I had created and was leading the "army." No problems building siege engines and conducting the siege itself, it just invariably froze/crashed once I clicked to either "lead" or "send troops" for the final battle/assault on the city.

    I am a Khuzait too and have this crash. Don't know if others are also Khuzaits and what that could mean.

    Save: https://we.tl/t-pjsaFckZDm
  3. In Progress Siege still crashing after hotfix 1.05 , 1.06 and 1.07

    Same for me, I can still auto resolve though. Seems to have something to do with a Game.dll read error (I launched as administator, did the scannow, etc).


    Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\ProgramData\Mount and Blade II Bannerlord\crashes\2020-04-05_16.00.48\dump.dmp]
    Could not open dump file [C:\ProgramData\Mount and Blade II Bannerlord\crashes\2020-04-05_16.00.48\dump.dmp], Win32 error 0n3
    "Le chemin d’accès spécifié est introuvable."

    Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\ProgramData\Mount and Blade II Bannerlord\crashes\2020-04-09_19.15.38\dump.dmp]
    User Mini Dump File: Only registers, stack and portions of memory are available


    ************* Path validation summary **************
    Response Time (ms) Location
    Deferred srv*
    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Version 18362 MP (6 procs) Free x64
    Product: WinNt, suite: SingleUserTS
    18362.1.amd64fre.19h1_release.190318-1202
    Machine Name:
    Debug session time: Thu Apr 9 19:15:42.000 2020 (UTC + 2:00)
    System Uptime: not available
    Process Uptime: 0 days 0:03:30.000
    ................................................................
    ................................................................
    ..............................................
    Loading unloaded module list
    ....
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (2510.330c): Access violation - code c0000005 (first/second chance not available)
    For analysis of this file, run !analyze -v
    ntdll!NtGetContextThread+0x14:
    00007ffd`1d4fde54 c3 ret
    0:018> !analyze -v
    *******************************************************************************
    * *
    * Exception Analysis *
    * *
    *******************************************************************************

    Failed to request MethodData, not in JIT code range
    0 is not IP

    KEY_VALUES_STRING: 1

    Key : AV.Dereference
    Value: NullClassPtr

    Key : AV.Fault
    Value: Read

    Key : Analysis.CPU.Sec
    Value: 58

    Key : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-HI5F76J

    Key : Analysis.DebugData
    Value: CreateObject

    Key : Analysis.DebugModel
    Value: CreateObject

    Key : Analysis.Elapsed.Sec
    Value: 68

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 259

    Key : Analysis.System
    Value: CreateObject

    Key : CLR.Engine
    Value: CLR

    Key : CLR.Version
    Value: 4.0.30319.0

    Key : Timeline.Process.Start.DeltaSec
    Value: 210


    ADDITIONAL_XML: 1

    NTGLOBALFLAG: 0

    PROCESS_BAM_CURRENT_THROTTLED: 0

    PROCESS_BAM_PREVIOUS_THROTTLED: 0

    APPLICATION_VERIFIER_FLAGS: 0

    CONTEXT: (.ecxr)
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=0000000000000000 rsp=0000009640e7ffd0 rbp=0000000000000000
    r8=ffffffffffffffff r9=00000250ce0016d0 r10=000002504d612068
    r11=00000000ffffff00 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na po nc
    cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
    00000000`00000000 ?? ???
    Resetting default scope

    EXCEPTION_RECORD: (.exr -1)
    ExceptionAddress: 00007ffcb6704492 (Game+0x0000000000024492)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000000000000048
    Attempt to read from address 0000000000000048

    PROCESS_NAME: TaleWorlds.MountAndBlade.Launcher.exe

    READ_ADDRESS: 0000000000000048

    ERROR_CODE: (NTSTATUS) 0xc0000005 - L'instruction 0x%p emploie l'adresse m moire 0x%p. L' tat de la m moire ne peut pas tre %s.

    EXCEPTION_CODE_STR: c0000005

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: 0000000000000048

    MISSING_CLR_SYMBOL: 0

    FAULTING_THREAD: ffffffff

    STACK_TEXT:
    00007ffc`b6704492 00007ffc`b6704492 Game+0x24492


    STACK_COMMAND: .ecxr ; kb ; ** Pseudo Context ** Pseudo ** Value: 1c2683fc040 ** ; kb

    SYMBOL_NAME: Game+24492

    MODULE_NAME: Game

    IMAGE_NAME: Game.dll

    FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_Game.dll!Unknown

    OS_VERSION: 10.0.18362.1

    BUILDLAB_STR: 19h1_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {25c4022a-7ee1-2f94-0e8e-5264fcbd2504}

    Followup: MachineOwner
    ---------
  4. In Progress e1.0.1 - Game crashes after commencing siege

    Still crashing for me as well, although I can send troops. I just auto resolve sieges now, which is a bit disappointing.
  5. Need More Info Crash during siege

    Issue still present in 1.0.6
  6. Need More Info Crash during siege

    Edited my previous post (mistake)


    Let's hope this gets fixed (today's hotfix did not), I am just playig normally and autoresolving every siege situation.
  7. Need More Info Crash during siege

    What you are describing is happening to me exactly.. siege is going along fine and then it crashes when I get near the walls ... Ryzen 5 cpu, 16gb, gtx 1060 6gb ... I hadn't tried it prior to 1.0.5 so I can't say whether or not it was working before ... I am going to try without building any siege machines and see if that changes anything...


    Let's hope this gets fixed (today's hotfix did not), I am just playig normally and autoresolving every siege situation.
  8. Need More Info Crash during siege

    Every time I get into a siege battle (attacker, in any castle), the game crashes as soon as I get close to the walls. It did not do this before, the game was running very smoothly (Ryzen 5 3500x, 16 gb ddr4, rx 590) So far I tried reinstalling, using minimal graphics, rolling back to previous...
后退
顶部 底部