Herkese selam dostlar, bugün sizlere yaşadığım bir sıkıntıdan bahsetmek istiyorum. Geçtiğimiz günlerde AMD'nin 2020 Adrenalin güncellemesini yapmadan önce Tom Clancy's Rainbow Six Siege adlı oyununda bir hata görmeden rahatça oyunu 100 üstü FPS değeri ile oynayabiliyordum. Şimdi bu güncelleme geldikten sonra oyunda takılmalar başladı ve oyunun yarısında mavi ekran yemeye başladım, hem de tüm maçlarda. Bu yüzden 1 hafta ban yedim ve sorunun devam etmemesi için sizlerden yardım istiyorum arkadaşlar, elinizden ne geliyorsa. İyi forumlar.
Çözüldü ASUS RX560 Mavi Ekran hatası
- Konuyu başlatan !Han
- Başlangıç Tarihi
- Mesaj 6
- Görüntüleme 632
Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
Çözüm
Tüm hatalar ekran kartı sürücüsüne ait, Windows 10'a geçmeyi düşünmeni isterim.
Bir eski sürüme geri dön, tekrar test et.
Bir eski sürüme geri dön, tekrar test et.
Kod:
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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for atikmdag.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
GetUlongPtrFromAddress: unable to read from fffff800038ef300
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.24540.amd64fre.win7sp1_ldr_escrow.191127-1706
SYSTEM_MANUFACTURER: To be filled by O.E.M.
SYSTEM_PRODUCT_NAME: To be filled by O.E.M.
SYSTEM_SKU: SKU
SYSTEM_VERSION: To be filled by O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 2501
BIOS_DATE: 04/07/2014
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: M5A99FX PRO R2.0
BASEBOARD_VERSION: Rev 1.xx
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CPU_COUNT: 4
CPU_MHZ: e1c
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 1
CPU_STEPPING: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: RainbowSix.exe
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: DESKTOP-18V31A3
ANALYSIS_SESSION_TIME: 12-21-2019 17:45:09.0914
ANALYSIS_VERSION: 10.0.18362.1 x86fre
DPC_STACK_BASE: FFFFF88002F38FB0
EXCEPTION_RECORD: fffff88002f38568 -- (.exr 0xfffff88002f38568)
ExceptionAddress: fffff88004208f7d (dxgmms1!VidSchiProcessDpcVSyncCookie+0x00000000000000e9)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0
TRAP_FRAME: fffff88002f38610 -- (.trap 0xfffff88002f38610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004208f7d rsp=fffff88002f387a0 rbp=fffffa8009f4e940
r8=0000000000000000 r9=0000000000000000 r10=fffffa8009f4d1f0
r11=fffff88002f38858 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
dxgmms1!VidSchiProcessDpcVSyncCookie+0xe9:
fffff880`04208f7d 48f7f1 div rax,rcx
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800036e90ee to fffff800036e5e70
STACK_TEXT:
fffff880`02f37658 fffff800`036e90ee : 00000000`00000000 00001f80`00000800 fffff880`02f37dd0 fffff800`036adde0 : nt!KeBugCheck
fffff880`02f37660 fffff800`036ed1fd : fffff800`038c8388 fffff800`0381b634 fffff800`03652000 fffff880`02f38568 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f37690 fffff800`036ad125 : fffff800`037fb988 fffff880`02f37708 fffff880`02f38568 fffff800`03652000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f376c0 fffff800`037cceee : fffff880`02f38568 fffff880`02f37dd0 fffff880`00000000 fffffa80`00000004 : nt!RtlDispatchException+0x415
fffff880`02f37da0 fffff800`036f43c2 : fffff880`02f38568 fffffa80`09f8d410 fffff880`02f38610 00000000`00000000 : nt!KiDispatchException+0x17e
fffff880`02f38430 fffff800`036ef1e2 : ffffd319`2f2c2732 00000000`00000001 fffffa80`09f4d000 fffff880`0420e769 : nt!KiExceptionDispatch+0xc2
fffff880`02f38610 fffff880`04208f7d : fffffa80`09f8d410 00000000`00000000 fffffa80`09f4d000 fffffa80`0b795af0 : nt!KiDivideErrorFault+0x2e2
fffff880`02f387a0 fffff880`04208d24 : fffff880`00000000 fffffa80`00000017 fffffa80`00000000 00000000`00000000 : dxgmms1!VidSchiProcessDpcVSyncCookie+0xe9
fffff880`02f38860 fffff880`04208c88 : 000000f4`10870000 fffffa80`09f8d410 fffffa80`0ba16b40 fffffa80`0ba16e28 : dxgmms1!VidSchDdiNotifyDpcWorker+0x80
fffff880`02f388b0 fffff880`042d81cf : fffffa80`08742480 00000000`00000000 00000000`00000001 fffffa80`0ba16e28 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`02f38900 fffff880`1112dbd4 : fffffa80`0ba16b40 fffffa80`0ba16b40 000000f4`10870000 fffffa80`0ba16b40 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`02f38930 fffffa80`0ba16b40 : fffffa80`0ba16b40 000000f4`10870000 fffffa80`0ba16b40 00000000`00000000 : atikmdag+0xcabd4
fffff880`02f38938 fffffa80`0ba16b40 : 000000f4`10870000 fffffa80`0ba16b40 00000000`00000000 fffff880`02f38990 : 0xfffffa80`0ba16b40
fffff880`02f38940 000000f4`10870000 : fffffa80`0ba16b40 00000000`00000000 fffff880`02f38990 00000000`00000000 : 0xfffffa80`0ba16b40
fffff880`02f38948 fffffa80`0ba16b40 : 00000000`00000000 fffff880`02f38990 00000000`00000000 00000000`00000000 : 0x000000f4`10870000
fffff880`02f38950 00000000`00000000 : fffff880`02f38990 00000000`00000000 00000000`00000000 00000000`00000001 : 0xfffffa80`0ba16b40
THREAD_SHA1_HASH_MOD_FUNC: 2df6cf70641b455bff5b51f38841351a51a58ca2
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 83d9e26f91db6b761d2324d7f0e37ae930eb7437
THREAD_SHA1_HASH_MOD: 8e360ce24f604d9f5968fee6e125f1d35ee72d1c
FOLLOWUP_IP:
dxgmms1!VidSchiProcessDpcVSyncCookie+e9
fffff880`04208f7d 48f7f1 div rax,rcx
FAULT_INSTR_CODE: 48f1f748
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: dxgmms1!VidSchiProcessDpcVSyncCookie+e9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5d5222c1
IMAGE_VERSION: 6.1.7601.24513
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: X64_0x1E_dxgmms1!VidSchiProcessDpcVSyncCookie+e9
BUCKET_ID: X64_0x1E_dxgmms1!VidSchiProcessDpcVSyncCookie+e9
PRIMARY_PROBLEM_CLASS: X64_0x1E_dxgmms1!VidSchiProcessDpcVSyncCookie+e9
TARGET_TIME: 2019-12-20T18:28:22.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2019-11-28 05:52:33
BUILDDATESTAMP_STR: 191127-1706
BUILDLAB_STR: win7sp1_ldr_escrow
BUILDOSVER_STR: 6.1.7601.24540.amd64fre.win7sp1_ldr_escrow.191127-1706
ANALYSIS_SESSION_ELAPSED_TIME: 1e8d
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x1e_dxgmms1!vidschiprocessdpcvsynccookie+e9
FAILURE_ID_HASH: {563df3f2-b5ac-cd6b-d157-580c3b7f02da}
Followup: MachineOwner
---------
- Katılım
- 9 Ekim 2015
- Mesajlar
- 12.749
- Çözümler
- 610
Daha fazla
- Cinsiyet
- Erkek
Dosyaları gönderin kontrol edelim.
www.technopat.net
Minidump Dosyalarını Paylaşın
23.06.2025 tarihinde yapılan güncel rehbere aşağıdaki linkten erişebilirsiniz: https://www.technopat.net/sosyal/konu/minidump-nedir-nasil-paylasilir.3817531/ Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi...
- Katılım
- 9 Ekim 2015
- Mesajlar
- 12.749
- Çözümler
- 610
Daha fazla
- Cinsiyet
- Erkek
Tüm hatalar ekran kartı sürücüsüne ait, Windows 10'a geçmeyi düşünmeni isterim.
Bir eski sürüme geri dön, tekrar test et.
Bir eski sürüme geri dön, tekrar test et.
Kod:
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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for atikmdag.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
GetUlongPtrFromAddress: unable to read from fffff800038ef300
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.24540.amd64fre.win7sp1_ldr_escrow.191127-1706
SYSTEM_MANUFACTURER: To be filled by O.E.M.
SYSTEM_PRODUCT_NAME: To be filled by O.E.M.
SYSTEM_SKU: SKU
SYSTEM_VERSION: To be filled by O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 2501
BIOS_DATE: 04/07/2014
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: M5A99FX PRO R2.0
BASEBOARD_VERSION: Rev 1.xx
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CPU_COUNT: 4
CPU_MHZ: e1c
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 1
CPU_STEPPING: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: RainbowSix.exe
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: DESKTOP-18V31A3
ANALYSIS_SESSION_TIME: 12-21-2019 17:45:09.0914
ANALYSIS_VERSION: 10.0.18362.1 x86fre
DPC_STACK_BASE: FFFFF88002F38FB0
EXCEPTION_RECORD: fffff88002f38568 -- (.exr 0xfffff88002f38568)
ExceptionAddress: fffff88004208f7d (dxgmms1!VidSchiProcessDpcVSyncCookie+0x00000000000000e9)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0
TRAP_FRAME: fffff88002f38610 -- (.trap 0xfffff88002f38610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004208f7d rsp=fffff88002f387a0 rbp=fffffa8009f4e940
r8=0000000000000000 r9=0000000000000000 r10=fffffa8009f4d1f0
r11=fffff88002f38858 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
dxgmms1!VidSchiProcessDpcVSyncCookie+0xe9:
fffff880`04208f7d 48f7f1 div rax,rcx
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800036e90ee to fffff800036e5e70
STACK_TEXT:
fffff880`02f37658 fffff800`036e90ee : 00000000`00000000 00001f80`00000800 fffff880`02f37dd0 fffff800`036adde0 : nt!KeBugCheck
fffff880`02f37660 fffff800`036ed1fd : fffff800`038c8388 fffff800`0381b634 fffff800`03652000 fffff880`02f38568 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f37690 fffff800`036ad125 : fffff800`037fb988 fffff880`02f37708 fffff880`02f38568 fffff800`03652000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f376c0 fffff800`037cceee : fffff880`02f38568 fffff880`02f37dd0 fffff880`00000000 fffffa80`00000004 : nt!RtlDispatchException+0x415
fffff880`02f37da0 fffff800`036f43c2 : fffff880`02f38568 fffffa80`09f8d410 fffff880`02f38610 00000000`00000000 : nt!KiDispatchException+0x17e
fffff880`02f38430 fffff800`036ef1e2 : ffffd319`2f2c2732 00000000`00000001 fffffa80`09f4d000 fffff880`0420e769 : nt!KiExceptionDispatch+0xc2
fffff880`02f38610 fffff880`04208f7d : fffffa80`09f8d410 00000000`00000000 fffffa80`09f4d000 fffffa80`0b795af0 : nt!KiDivideErrorFault+0x2e2
fffff880`02f387a0 fffff880`04208d24 : fffff880`00000000 fffffa80`00000017 fffffa80`00000000 00000000`00000000 : dxgmms1!VidSchiProcessDpcVSyncCookie+0xe9
fffff880`02f38860 fffff880`04208c88 : 000000f4`10870000 fffffa80`09f8d410 fffffa80`0ba16b40 fffffa80`0ba16e28 : dxgmms1!VidSchDdiNotifyDpcWorker+0x80
fffff880`02f388b0 fffff880`042d81cf : fffffa80`08742480 00000000`00000000 00000000`00000001 fffffa80`0ba16e28 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`02f38900 fffff880`1112dbd4 : fffffa80`0ba16b40 fffffa80`0ba16b40 000000f4`10870000 fffffa80`0ba16b40 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`02f38930 fffffa80`0ba16b40 : fffffa80`0ba16b40 000000f4`10870000 fffffa80`0ba16b40 00000000`00000000 : atikmdag+0xcabd4
fffff880`02f38938 fffffa80`0ba16b40 : 000000f4`10870000 fffffa80`0ba16b40 00000000`00000000 fffff880`02f38990 : 0xfffffa80`0ba16b40
fffff880`02f38940 000000f4`10870000 : fffffa80`0ba16b40 00000000`00000000 fffff880`02f38990 00000000`00000000 : 0xfffffa80`0ba16b40
fffff880`02f38948 fffffa80`0ba16b40 : 00000000`00000000 fffff880`02f38990 00000000`00000000 00000000`00000000 : 0x000000f4`10870000
fffff880`02f38950 00000000`00000000 : fffff880`02f38990 00000000`00000000 00000000`00000000 00000000`00000001 : 0xfffffa80`0ba16b40
THREAD_SHA1_HASH_MOD_FUNC: 2df6cf70641b455bff5b51f38841351a51a58ca2
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 83d9e26f91db6b761d2324d7f0e37ae930eb7437
THREAD_SHA1_HASH_MOD: 8e360ce24f604d9f5968fee6e125f1d35ee72d1c
FOLLOWUP_IP:
dxgmms1!VidSchiProcessDpcVSyncCookie+e9
fffff880`04208f7d 48f7f1 div rax,rcx
FAULT_INSTR_CODE: 48f1f748
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: dxgmms1!VidSchiProcessDpcVSyncCookie+e9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5d5222c1
IMAGE_VERSION: 6.1.7601.24513
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: X64_0x1E_dxgmms1!VidSchiProcessDpcVSyncCookie+e9
BUCKET_ID: X64_0x1E_dxgmms1!VidSchiProcessDpcVSyncCookie+e9
PRIMARY_PROBLEM_CLASS: X64_0x1E_dxgmms1!VidSchiProcessDpcVSyncCookie+e9
TARGET_TIME: 2019-12-20T18:28:22.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2019-11-28 05:52:33
BUILDDATESTAMP_STR: 191127-1706
BUILDLAB_STR: win7sp1_ldr_escrow
BUILDOSVER_STR: 6.1.7601.24540.amd64fre.win7sp1_ldr_escrow.191127-1706
ANALYSIS_SESSION_ELAPSED_TIME: 1e8d
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x1e_dxgmms1!vidschiprocessdpcvsynccookie+e9
FAILURE_ID_HASH: {563df3f2-b5ac-cd6b-d157-580c3b7f02da}
Followup: MachineOwner
---------Windows 10'a geçmeyi düşünmüyorum, çoğu dostum da geçtikten sonra verimsizlik aldığını söyledi Windows 7'ye göre. Ekran kartının ara sürücüsünü tamamen silip sıfırdan yüklesem düzelir mi? Eski sürüme dönmekle ilgili de AMD hataların farkında olduklarını ve ileride çıkacak sürümlerle düzelteceklerini söyledi.
- Katılım
- 9 Ekim 2015
- Mesajlar
- 12.749
- Çözümler
- 610
Daha fazla
- Cinsiyet
- Erkek
Büyük ihtimal düzelecektir, zaten hatanın sürüm yükseltme ile başladığını söylemiştiniz.
- Durum
Benzer konular
- Soru
- Soru
- Soru
- Soru
