Bluescreen und Gamecrash - fehlerhaften Anwendung: nvcontainer.exe, fehlerhafte Module: ntdll.dll

FabianG01 · 22.10.2022, 14:54

Hallo liebes Forum,

leider habe ich seit längerer Zeit Bluescreens und einer meiner lieblingsspiele crasht immer.
Ich habe schon im Event Viewer nachgeschaut und hier sind folgende logs:

Application Error

Code:

ATTFilter

Name der fehlerhaften Anwendung: Gunfire Reborn.exe, Version: 2018.4.20.34440, Zeitstempel: 0x5e72fef7
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.19041.2130, Zeitstempel: 0xb5ced1c6
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000512a5
ID des fehlerhaften Prozesses: 0x2cb4
Startzeit der fehlerhaften Anwendung: 0x01d8e60f63271fbf
Pfad der fehlerhaften Anwendung: D:\SteamLibrary\steamapps\common\Gunfire Reborn\Gunfire Reborn.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: 014791ab-1b78-4706-9547-7ba74ae3cb1c
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Application Error

Code:

ATTFilter

Name der fehlerhaften Anwendung: nvcontainer.exe, Version: 1.37.3103.4323, Zeitstempel: 0x621dbda6
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.19041.2130, Zeitstempel: 0xb5ced1c6
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000a70e6
ID des fehlerhaften Prozesses: 0x1a6c
Startzeit der fehlerhaften Anwendung: 0x01d8e6027a938dae
Pfad der fehlerhaften Anwendung: C:\Program Files\NVIDIA Corporation\NvContainer\nvcontainer.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: cf046ac4-df54-4ff3-a320-6c14f7b1aff0
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Ich bekomme auch Systemfehler wie z.B.:

Code:

ATTFilter

Der Dienst "MEmuSVC" wurde aufgrund folgenden Fehlers nicht gestartet: 
Das System kann die angegebene Datei nicht finden.

Noch ein Log vom 19.10.2022 von WINDBG Preview

Code:

ATTFilter

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


Loading Dump File [C:\Windows\Minidump\101922-9531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`06600000 PsLoadedModuleList = 0xfffff802`0722a270
Debug session time: Wed Oct 19 19:42:01.594 2022 (UTC + 2:00)
System Uptime: 0 days 0:09:16.257
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`069f90f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffffb86`2c630740=0000000000000119
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 000000000000a000, The subtype of the BugCheck:
Arg2: ffffcf03dbc435d0
Arg3: 0000000000000000
Arg4: 0000000000000001

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6983

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 39498

    Key  : Analysis.IO.Other.Mb
    Value: 7

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 25

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x119

    Key  : Bugcheck.Code.Register
    Value: 0x119

    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


FILE_IN_CAB:  101922-9531-01.dmp

BUGCHECK_CODE:  119

BUGCHECK_P1: a000

BUGCHECK_P2: ffffcf03dbc435d0

BUGCHECK_P3: 0

BUGCHECK_P4: 1

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffffb86`2c630738 fffff802`0b003ad0     : 00000000`00000119 00000000`0000a000 ffffcf03`dbc435d0 00000000`00000000 : nt!KeBugCheckEx
fffffb86`2c630740 fffff802`0cadbf8b     : ffffcf03`dacc8460 ffffcf03`d124a000 ffffcf03`d124a000 ffffcf03`d119f000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffb86`2c630780 fffff802`0cb712ce     : ffffcf03`d124a001 00000000`00000000 ffffcf03`d124a000 fffffb86`2c630a08 : dxgmms2!VidSchiResetHwEngine+0x6ab
fffffb86`2c630930 fffff802`0cb460e3     : ffffcf03`d119f000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xaa
fffffb86`2c630980 fffff802`0cb21252     : fffffb86`2c630a01 00000000`00008a85 00000000`00da7a64 00000000`00000020 : dxgmms2!VidSchiCheckHwProgress+0x24e63
fffffb86`2c6309f0 fffff802`0caaba3a     : 00000000`00000000 ffffcf03`d119f000 fffffb86`2c630b19 00000000`00000001 : dxgmms2!VidSchiWaitForSchedulerEvents+0x372
fffffb86`2c630ac0 fffff802`0cb2d065     : ffffcf03`d7ce1000 ffffcf03`d119f000 ffffcf03`d7ce1010 ffffcf03`d1264620 : dxgmms2!VidSchiScheduleCommandToRun+0x2ca
fffffb86`2c630b80 fffff802`0cb2d01a     : ffffcf03`d119f400 fffff802`0cb2cf50 ffffcf03`d119f000 ffff8680`c09cb100 : dxgmms2!VidSchiRun_PriorityTable+0x35
fffffb86`2c630bd0 fffff802`06871d25     : ffffcf03`d11a2280 fffff802`00000001 ffffcf03`d119f000 00078224`bcbbbdfe : dxgmms2!VidSchiWorkerThread+0xca
fffffb86`2c630c10 fffff802`06a00778     : ffff8680`c09cb180 ffffcf03`d11a2280 fffff802`06871cd0 00350036`0034002d : nt!PspSystemThreadStartup+0x55
fffffb86`2c630c60 00000000`00000000     : fffffb86`2c631000 fffffb86`2c62b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VidSchiResetHwEngine+6ab

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.1940

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  6ab

FAILURE_BUCKET_ID:  0x119_a000_VIDSCH_RESET_HW_ENGINE_SUSPEND_dxgmms2!VidSchiResetHwEngine

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {95884248-9389-91d4-05c4-d0b1411f9702}

Followup:     MachineOwner
---------

3: kd> !blackboxbsd
Version: 0xb0
Product type: 1

Auto advanced boot: FALSE
Advanced boot menu timeout: 30
Last boot succeeded: TRUE
Last boot shutdown: FALSE
Sleep in progress: FALSE

Power button timestamp: 0x0
System running: TRUE
Connected standby in progress: FALSE
User shutdown in progress: FALSE
System shutdown in progress: FALSE
Sleep in progress: 0
Connected standby scenario instance id: 0
Connected standby entry reason: 0
Connected standby exit reason: 0
System sleep transitions to on: 0
Last reference time: 0x1d8e3e0d0ed53cd
	2022-10-19T17:32:52.482Z
Last reference time checksum: 0xf6ae59e0
Last update boot id: 110

Boot attempt count: 1
Last boot checkpoint: TRUE
Checksum: 0x64
Last boot id: 110
Last successful shutdown boot id: 102
Last reported abnormal shutdown boot id: 109

Error info boot id: 0
Error info repeat count: 0
Error info other error count: 0
Error info code: 0
Error info status: 0x0

Power button last press time: 0x0
Power button cumulative press count: 0
Power button last press boot id: 0
Power button last power watchdog stage: 0
Power button watchdog armed: FALSE
Power button shutdown in progress: FALSE
Power button last release time: 0x0
Power button cumulative release count: 0
Power button last release boot id: 0
Power button error count: 0
Power button current connected standby phase: 0
Power button transition latest checkpoint id: 0
Power button transition latest checkpoint type: 0
Power button transition latest checkpoint sequence number: 0

Power transition Shutdown Device Type: 0
Power transition Setup In Progress: FALSE
Power transition OOBE In Progress: FALSE
Power transition Sleep Checkpoint Source: 0
Power transition Sleep Checkpoint: 0
Power transition Connected Standby Entry Reason Category: 0
Power transition Connected Standby Exit Reason Category: 0
Power transition Connected Standby Entry Scenario Instance Id: 0x0

Feature Configuration State : Uninitialized

3: kd> !blackboxntfs

NTFS Blackbox Data

0 Slow I/O Timeout Records Found
0 Oplock Break Timeout Records Found
3: kd> !blackboxbsd
Version: 0xb0
Product type: 1

Auto advanced boot: FALSE
Advanced boot menu timeout: 30
Last boot succeeded: TRUE
Last boot shutdown: FALSE
Sleep in progress: FALSE

Power button timestamp: 0x0
System running: TRUE
Connected standby in progress: FALSE
User shutdown in progress: FALSE
System shutdown in progress: FALSE
Sleep in progress: 0
Connected standby scenario instance id: 0
Connected standby entry reason: 0
Connected standby exit reason: 0
System sleep transitions to on: 0
Last reference time: 0x1d8e3e0d0ed53cd
	2022-10-19T17:32:52.482Z
Last reference time checksum: 0xf6ae59e0
Last update boot id: 110

Boot attempt count: 1
Last boot checkpoint: TRUE
Checksum: 0x64
Last boot id: 110
Last successful shutdown boot id: 102
Last reported abnormal shutdown boot id: 109

Error info boot id: 0
Error info repeat count: 0
Error info other error count: 0
Error info code: 0
Error info status: 0x0

Power button last press time: 0x0
Power button cumulative press count: 0
Power button last press boot id: 0
Power button last power watchdog stage: 0
Power button watchdog armed: FALSE
Power button shutdown in progress: FALSE
Power button last release time: 0x0
Power button cumulative release count: 0
Power button last release boot id: 0
Power button error count: 0
Power button current connected standby phase: 0
Power button transition latest checkpoint id: 0
Power button transition latest checkpoint type: 0
Power button transition latest checkpoint sequence number: 0

Power transition Shutdown Device Type: 0
Power transition Setup In Progress: FALSE
Power transition OOBE In Progress: FALSE
Power transition Sleep Checkpoint Source: 0
Power transition Sleep Checkpoint: 0
Power transition Connected Standby Entry Reason Category: 0
Power transition Connected Standby Exit Reason Category: 0
Power transition Connected Standby Entry Scenario Instance Id: 0x0

Feature Configuration State : Uninitialized

Folgendes habe ich schon ausprobiert:

sfc /Scannow
DISM repair tool von windows
CHECKDSK
Rams auch gecheckt

Leider hat das nicht geholfen.

Ich benutze nicht so gerne Tools aber jede mögliche Hilfe oder Debugging Tipps nehme ich gerne an.

Freundliche Grüße

Fabian

Bluescreen und Gamecrash - fehlerhaften Anwendung: nvcontainer.exe, fehlerhafte Module: ntdll.dll

Alles rund um Windows: Bluescreen und Gamecrash - fehlerhaften Anwendung: nvcontainer.exe, fehlerhafte Module: ntdll.dll

Problem: Bluescreen und Gamecrash - fehlerhaften Anwendung: nvcontainer.exe, fehlerhafte Module: ntdll.dll

Ähnliche Themen: Bluescreen und Gamecrash - fehlerhaften Anwendung: nvcontainer.exe, fehlerhafte Module: ntdll.dll