Crash windows lors des exports Afterfx

Fermé
Facteur_Rhesus - 18 oct. 2021 à 15:28
Bonjour à tous,

Je viens à vous un peu dans l'urgence, le pc de montage que j'utilise à mon bureau à tendance a me faire un bel écran bleu lorsque je veux exporter mes composition Afterfx un peu lourde. J'ai testé plusieurs solution dont le classique changement de logique de rendu sans succès. La seul solution trouvé pour le moment est d'exporter mes compos par tranche de 5 secondes pour les réassembler après ce qui est extrêmement laborieux (impossible de lancé un export pendant la nuit car il arrive qu'un des export face un crash -.-). J'ai pus récupérer les donnée du Memory.DMP mais je n'ai pas vraiment les connaissance pour réussir à comprendre d'où vient le problème (et les recherches internet des id d'erreur cible des résultats anglophone ce qui n'aide pas ^^) . J'espère poster ce message dans la bonne catégorie. Quel information puis-je communiquer afin d'aider à cibler le problème ? Voici le contenus du .DMP :
  • *
  • Bugcheck Analysis *
  • *


KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------
      • ***
      • ***
      • Either you specified an unqualified symbol, or your debugger ***
      • doesn't have full symbol information. Unqualified symbol ***
      • resolution is turned off by default. Please either specify a ***
      • fully qualified symbol module!symbolname, or enable resolution ***
      • of unqualified symbols by typing ".symopt- 100". Note that ***
      • enabling unqualified symbol resolution with network symbol ***
      • server shares in the symbol path may cause the debugger to ***
      • appear to hang for long periods of time when an incorrect ***
      • symbol name is typed or the network symbol server is down. ***
      • ***
      • For some commands to work properly, your symbol path ***
      • must point to .pdb files that have full type information. ***
      • ***
      • Certain .pdb files (such as the public OS symbols) do not ***
      • contain the required information. Contact the group that ***
      • provided you with these symbols if you need this command to ***
      • work. ***
      • ***
      • Type referenced: ExceptionRecord ***
      • ***
      • ***
      • ***
      • Either you specified an unqualified symbol, or your debugger ***
      • doesn't have full symbol information. Unqualified symbol ***
      • resolution is turned off by default. Please either specify a ***
      • fully qualified symbol module!symbolname, or enable resolution ***
      • of unqualified symbols by typing ".symopt- 100". Note that ***
      • enabling unqualified symbol resolution with network symbol ***
      • server shares in the symbol path may cause the debugger to ***
      • appear to hang for long periods of time when an incorrect ***
      • symbol name is typed or the network symbol server is down. ***
      • ***
      • For some commands to work properly, your symbol path ***
      • must point to .pdb files that have full type information. ***
      • ***
      • Certain .pdb files (such as the public OS symbols) do not ***
      • contain the required information. Contact the group that ***
      • provided you with these symbols if you need this command to ***
      • work. ***
      • ***
      • Type referenced: ContextRecord ***
      • ***


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2593

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2590

Key : Analysis.Init.CPU.mSec
Value: 389

Key : Analysis.Init.Elapsed.mSec
Value: 36533

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: 0

BUGCHECK_P3: 8

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: AfterFX.exe

TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
ffff928d`875a1af8 fffff800`42659ecb : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
ffff928d`875a1b00 fffff800`426092ac : 00000000`00001000 ffff928d`875a23a0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x17467b
ffff928d`875a21c0 fffff800`42605443 : 00000000`00000000 fffff800`44fd96e7 ffffa983`26dba050 00000000`00000000 : nt!KiExceptionDispatch+0x12c
ffff928d`875a23a0 00000000`00000000 : ffff928d`875a2500 ffff928d`875a2599 ffffffff`00100080 ffffa983`00000000 : nt!KiPageFault+0x443


SYMBOL_NAME: nt!KiDispatchException+17467b

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 17467b

FAILURE_BUCKET_ID: 0x1E_nt!KiDispatchException

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {4c003660-11e1-3fb7-2474-3522eb7ee67b}

Followup: MachineOwner
---------
A voir également: