Oyun oynarken alınan mavi ekran ve reset sorunu

Recep Baltaş dedi:

Yo, biz burada her mavi ekran hatası alana format atın demiyoruz. Olaya bilimsel yaklaşıp minidump dosyalarını analiz ediyoruz. Kaldı ki donanımsal hatalar format ile çözülemez.

Sorun ekran kartınız ya da ekran kartı sürücünüzle ilgili. Öncelikle 1903'e geçin, ekran kartı sürücünüzü güncelleyin. Sorun devam ederse kartınızı Furmark ile stres testine sokun.

Kod:Panoya kopyala

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: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 00000000002f794f
Arg3: 00000000002f796e
Arg4: ffff8500f7d8b000
KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 1

Key : Analysis.Elapsed.Sec
Value: 113

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


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1201

BIOS_DATE: 04/25/2019

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: PRIME B450M-K

BASEBOARD_VERSION: Rev X.0x

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

WRONG_SYMBOLS_TIMESTAMP: 5cf9f460

WRONG_SYMBOLS_SIZE: 954000

FAULTING_MODULE: fffff8007729d000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5cf9f460

DUMP_TYPE: 2

BUGCHECK_P1: 1

BUGCHECK_P2: 2f794f

BUGCHECK_P3: 2f796e

BUGCHECK_P4: ffff8500f7d8b000

CPU_COUNT: 4

CPU_MHZ: f35

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 11

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


CUSTOMER_CRASH_COUNT: 1

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-NG9H4F5

ANALYSIS_SESSION_TIME: 06-23-2019 19:59:01.0379

ANALYSIS_VERSION: 10.0.18869.1002 amd64fre

LAST_CONTROL_TRANSFER: from fffff80d0426331e to fffff80077447ab0

STACK_TEXT:
ffff9b84`e65e9288 fffff80d`0426331e : 00000000`00000119 00000000`00000001 00000000`002f794f 00000000`002f796e : nt+0x1aaab0
ffff9b84`e65e9290 fffff80d`0645e08f : 00000000`00000001 00000000`00000000 ffff8500`f7d22000 00000000`00000000 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffff9b84`e65e92d0 fffff80d`0644c739 : 00000000`00000001 00000000`00000001 00000000`00000000 ffff9b84`e65e94e0 : dxgmms2!VidSchiProcessIsrCompletedPacket+0x1179f
ffff9b84`e65e9370 fffff80d`06473c91 : ffff9b84`002f794f 00000000`00000000 ffff9b84`e65e9530 00000000`00000000 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x2a9
ffff9b84`e65e93d0 fffff800`77448bb2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiCallNotifyInterruptAtISR+0x81
ffff9b84`e65e9410 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x1abbb2


THREAD_SHA1_HASH_MOD_FUNC: 2fc471b741380398607fe3b3fb8b209cbbf59b6c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 670a9fd471f4860ee4a0d2e5c31196cb6a3249b1

THREAD_SHA1_HASH_MOD: 8776c7f27178640404a86974a111ebe127cec1d5

FOLLOWUP_IP:
dxgmms2!VidSchiProcessIsrCompletedPacket+1179f
fffff80d`0645e08f cc int 3

FAULT_INSTR_CODE: 48d233cc

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt_wrong_symbols!5CF9F460954000

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 10.0.17134.829

STACK_COMMAND: .thread ; .cxr ; kb

BUGCHECK_STR: 5CF9F460

EXCEPTION_CODE: (NTSTATUS) 0x5cf9f460 - <Unable to get error code text>

EXCEPTION_CODE_STR: 5CF9F460

EXCEPTION_STR: WRONG_SYMBOLS

PROCESS_NAME: ntoskrnl.wrong.symbols.exe

IMAGE_NAME: ntoskrnl.wrong.symbols.exe

MODULE_NAME: nt_wrong_symbols

BUCKET_ID:  WRONG_SYMBOLS_X64_17134.1.amd64fre.rs4_release.180410-1804_TIMESTAMP_190607-052136

DEFAULT_BUCKET_ID: WRONG_SYMBOLS_X64_17134.1.amd64fre.rs4_release.180410-1804_TIMESTAMP_190607-052136

PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_17134.1.amd64fre.rs4_release.180410-1804_TIMESTAMP_190607-052136_5CF9F460_nt_wrong_symbols!5CF9F460954000

TARGET_TIME: 2019-06-22T14:05:33.000Z

OSBUILD: 17134

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2019-06-07 08:21:36

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 1bc7b

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols_x64_17134.1.amd64fre.rs4_release.180410-1804_timestamp_190607-052136_5cf9f460_nt_wrong_symbols!5cf9f460954000

FAILURE_ID_HASH: {6384463c-d53d-58fe-39c1-29ac3a718430}

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

Genişletmek için tıkla...

olyxus dedi:

Evet herşeyim güncel ama ekran kartım 2200g apu 3.9ghz bu bilgiyi vermeyi unutmuşum sistem yeni 4 aylık ve önceden böyle olmuyordu sığutma sistemim 5 ısı borulu dual ram 16gb neden ekran kartı almadın diye sorarsanız fiyatlar çok pahalıydı

Genişletmek için tıkla...