GTX 1650 Oyun esnasında mavi ekran hatası

shakur558

Decapat
Katılım
20 Aralık 2019
Mesajlar
157
Herkese merhaba. Henüz 1 buçuk aylık olan ASUS TUF Gaming FX505DT-BQ190 Ryzen 5 3550H işlemcili GTX1650 ekran kartlı 8 GB ramli bir laptopum var. Sistem olarak Win 10 1903 lisanslı kurulu.

Geçenlerde gece kapatmadan şu an ismini hatırlamadığım 2 Update yapmıştı bilgisayar kapatırken otomatik yükledi kapandı. Ertesi gün açtım CS GO oyununu oynarken pilde oynuyordum birden ekran dondu ve aynı zamanda kasanın sağ kısmından Power tuşu ve numpad taraflarından yoğun zırıltı sesi geliyordu mavi ekran verdi.

Cihazda ilk mavi ekranda hata kodu THREAD_STUCK_IN_DEVICE_DRIVER olarak göründü. Yeniden başlattım daha sonra tekrar aynı oyunu açtım yine pilde oynarken tekrar aynı donma ve zırıltı sesi oldu ve mavi ekran vererek bu sefer DPC_WATCH_DOG_VIOLATION hata kodu verdi.

Tüm sürücülerim güncel ve Win10'un otomatik Update'lerini geri sildim ve ekran kartı driverını temiz kurulum yaptım. 5 gündür de deniyorum bilgisayar stabil çalışıyor fakat ASUS ile iletişime geçtim servise göndermeniz gerekebilir dediler. Yeni bir bilgisayar olduğu için donanımsal sıkıntı durumu var mı o aklımı karıştırıyor. Minidump dosyasını yüklüyorum. Herhangi bir donanımsal sıkıntı var ise bu şekilde görülebilinir mi bilmiyorum. Yardımcı olursanız sevinirim

Minidump.rar
 
AMD Ryzen Master, Asus özel yazılımları kullanma.

Hatanın nedeni APU ekran sürücüsünün ve Chipset sürüsünün hata vermesi, temiz kurulum ile zaten üst üste kurulan sürücüleri halletmişsin, eğer tekrardan dosya oluşursa gönder.

Kod:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8060df64750, memory referenced
Arg2: 000000000000000f, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff8060df64750, address which referenced memory

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


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:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME:  TUF Gaming FX505DT_FX505DT

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  FX505DT.308

BIOS_DATE:  09/19/2019

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  FX505DT

BASEBOARD_VERSION:  1.0

DUMP_TYPE:  2

BUGCHECK_P1: fffff8060df64750

BUGCHECK_P2: f

BUGCHECK_P3: 8

BUGCHECK_P4: fffff8060df64750

READ_ADDRESS: fffff8060eb733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8060df64750

CURRENT_IRQL:  f

FAULTING_IP:
AMDPcore.sys+4750
fffff806`0df64750 ??              ???

IP_MODULE_UNLOADED:
AMDPcore.sys+4750
fffff806`0df64750 ??              ???

CPU_COUNT: 8

CPU_MHZ: 830

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 18

CPU_STEPPING: 1

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  taskhostw.exe

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  12-22-2019 02:12:07.0452

ANALYSIS_VERSION: 10.0.18362.1 x86fre

TRAP_FRAME:  ffffdf01a63d8d80 -- (.trap 0xffffdf01a63d8d80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8060df64750 rbx=0000000000000000 rcx=ffffc205a2d63f10
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8060df64750 rsp=ffffdf01a63d8f18 rbp=ffffc205a2d63f90
r8=ffff98822f36d8a0  r9=fffff8060f108e20 r10=0000fffff8060df6
r11=ffffcef8eee00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po cy
<Unloaded_AMDPcore.sys>+0x4750:
fffff806`0df64750 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8060e7d32e9 to fffff8060e7c14e0

FAILED_INSTRUCTION_ADDRESS:
AMDPcore.sys+4750
fffff806`0df64750 ??              ???

STACK_TEXT:
ffffdf01`a63d8c38 fffff806`0e7d32e9 : 00000000`0000000a fffff806`0df64750 00000000`0000000f 00000000`00000008 : nt!KeBugCheckEx
ffffdf01`a63d8c40 fffff806`0e7cf62b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000b88 : nt!KiBugCheckDispatch+0x69
ffffdf01`a63d8d80 fffff806`0df64750 : fffff806`0f0e621b ffff99bc`83edb472 fffff806`00000002 00000000`00000f32 : nt!KiPageFault+0x46b
ffffdf01`a63d8f18 fffff806`0f0e621b : ffff99bc`83edb472 fffff806`00000002 00000000`00000f32 fffff806`00400a02 : <Unloaded_AMDPcore.sys>+0x4750
ffffdf01`a63d8f20 fffff806`0e602a25 : ffff9882`20ed8300 00000000`00000010 ffff99bc`83edb522 ffff9882`2f695580 : hal!HalpPerfInterrupt+0x10b
ffffdf01`a63d8f60 fffff806`0e7c2f7a : ffffc205`a2d63f90 ffff9882`20ed8300 00000000`00000038 ffff9882`20ed8300 : nt!KiCallInterruptServiceRoutine+0xa5
ffffdf01`a63d8fb0 fffff806`0e7c34e7 : 00000000`0000000f fffff806`0f0ef1f2 fffff806`0f121de0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffc205`a2d63f10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37


THREAD_SHA1_HASH_MOD_FUNC:  f5a7fbe8ed4b439b043f766c753ec793d12342da

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d369e161b8442eec836455e975c6029090fe9dc2

THREAD_SHA1_HASH_MOD:  6afce71294ca5c79f449671e51438006924fce0b

FOLLOWUP_IP:
AMDPcore.sys+4750
fffff806`0df64750 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  AMDPcore.sys+4750

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AMDPcore

IMAGE_NAME:  AMDPcore.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  4750

FAILURE_BUCKET_ID:  AV_CODE_AV_UNLOADED_IP_AMDPcore.sys!unknown_function

BUCKET_ID:  AV_CODE_AV_UNLOADED_IP_AMDPcore.sys!unknown_function

PRIMARY_PROBLEM_CLASS:  AV_CODE_AV_UNLOADED_IP_AMDPcore.sys!unknown_function

TARGET_TIME:  2019-12-08T00:23:25.000Z

OSBUILD:  18362

OSSERVICEPACK:  476

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  2011-12-30 02:28:41

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  3d4d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_code_av_unloaded_ip_amdpcore.sys!unknown_function

FAILURE_ID_HASH:  {032bd19c-cad5-0e51-79f9-8aa2b0760295}

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

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: ffff8b899db05080, Pointer to a stuck thread object.  Do .thread then kb on it to find
    the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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

*** WARNING: Unable to verify timestamp for atikmdag.sys

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:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: ffff8b899db05080

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  ffff8b899db05080

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CPU_COUNT: 8

CPU_MHZ: 830

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 18

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  MSIAfterburner.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  12-22-2019 02:12:02.0829

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff80227870db5 to fffff8021ddc14e0

STACK_TEXT:
ffff9d84`5bd55ab8 fffff802`27870db5 : 00000000`000000ea ffff8b89`9db05080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff9d84`5bd55ac0 fffff802`27870e8e : ffff9d84`5bd55ba0 fffff802`2784beab ffff9d84`5bd55ba0 fffff802`30983954 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff9d84`5bd55b30 fffff802`308edb00 : 00000001`8ac1554b fffff802`30983954 00000000`00000000 ffff8b89`91443000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff9d84`5bd55b70 00000001`8ac1554b : fffff802`30983954 00000000`00000000 ffff8b89`91443000 00000000`00989680 : atikmdag+0x6db00
ffff9d84`5bd55b78 fffff802`30983954 : 00000000`00000000 ffff8b89`91443000 00000000`00989680 00000000`00000001 : 0x00000001`8ac1554b
ffff9d84`5bd55b80 00000000`00000000 : ffff8b89`91443000 00000000`00989680 00000000`00000001 00000000`00000028 : atikmdag+0x103954


STACK_COMMAND:  .thread 0xffff8b899db05080 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  72fdf9c2701b15ee3875c8d84432bb6f4f878992

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  8733c7833060fb02ce8c6a0258e1674615927de1

THREAD_SHA1_HASH_MOD:  7711aec31f9092c0b1e7c4bf053e92961bf05370

FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
fffff802`27870db5 cc              int     3

FAULT_INSTR_CODE:  cccccccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.449

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

PRIMARY_PROBLEM_CLASS:  0xEA_IMAGE_dxgkrnl.sys

TARGET_TIME:  2019-12-16T10:05:12.000Z

OSBUILD:  18362

OSSERVICEPACK:  535

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1980-01-11 18:53:20

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  11180

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xea_image_dxgkrnl.sys

FAILURE_ID_HASH:  {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}

Followup:     MachineOwner

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80155373358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

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:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80155373358

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CPU_COUNT: 8

CPU_MHZ: 830

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 18

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  12-22-2019 02:11:57.0861

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff80154feeac1 to fffff80154fc14e0

STACK_TEXT:
fffff801`5aa75b08 fffff801`54feeac1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`55373358 : nt!KeBugCheckEx
fffff801`5aa75b10 fffff801`54e1f61c : 0000026a`48045c84 fffff801`52f9a180 00000000`00013a4e 00000000`00013a4e : nt!KeAccumulateTicks+0x1cc061
fffff801`5aa75b70 fffff801`54d5e4b7 : 00000000`00000001 ffffe68a`86221db0 ffffe68a`86221e30 00000000`0000000c : nt!KeClockInterruptNotify+0x98c
fffff801`5aa75f30 fffff801`54e02a25 : 00000002`ed7edcc1 fffff801`54dcc0e0 fffff801`54dcc190 00000000`00000000 : hal!HalpTimerClockInterrupt+0xf7
fffff801`5aa75f60 fffff801`54fc2f7a : ffffe68a`86221e30 fffff801`54dcc0e0 00000000`00000000 fffff801`54dcc0e0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`5aa75fb0 fffff801`54fc34e7 : 00000000`b28e7888 ffffe68a`86221e30 fffff801`54dcc0e0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffe68a`86221db0 fffff801`54eb36de : 00000000`00000000 fffff801`52f9a180 00000000`00000000 fffff07c`00ab2fc8 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffe68a`86221f40 fffff801`54eb16ec : fffff801`55268b00 00000000`00000000 ffffe68a`86222190 00000000`00000000 : nt!MiFlushTbList+0x39e
ffffe68a`86222090 fffff801`54ec2212 : 80000002`223a1963 00000000`00000000 00000000`00000000 fffff07c`00ab2fd0 : nt!MiTerminateWsleCluster+0x38c
ffffe68a`86222230 fffff801`54e57ee0 : ffffaa0d`caf98710 00000000`00000004 00000000`00000000 ffffaa0d`b97dc028 : nt!MiRemoveMappedPtes+0x202
ffffe68a`862222f0 fffff801`553fda53 : fffff801`552668a0 00000000`00004001 00000000`00000001 ffffd401`00000000 : nt!MiRemoveFromSystemSpace+0x328
ffffe68a`86222420 fffff801`553fd995 : ffffd401`d49dab30 ffffe68a`00000000 ffffd401`d49dab30 ffffd401`c7214ba0 : nt!MmUnmapViewInSystemSpace+0x23
ffffe68a`86222450 fffff801`553fd4b4 : ffffaa0d`cbadff90 ffffd401`d5804960 00007ffc`3b5b0000 00000000`00000000 : nt!MiUpdateCfgSystemWideBitmapWorker+0x285
ffffe68a`86222530 fffff801`554211e0 : ffffaa0d`cbadfd50 fffff05f`00cd94f8 00007ffc`3b5b0000 00000000`00000000 : nt!MiUpdateCfgSystemWideBitmap+0x70
ffffe68a`86222570 fffff801`55420d1e : 00007ffc`3b5b0000 ffffe68a`86222840 ffffaa0d`ca2ed080 00000000`00000000 : nt!MiRelocateImageAgain+0x10c
ffffe68a`86222600 fffff801`554207b6 : 00000000`00000002 ffffe68a`00000000 ffffaa0d`c9d54dd0 ffffe68a`86222840 : nt!MiValidateExistingImage+0x66
ffffe68a`862226a0 fffff801`553da683 : ffffaa0d`c9d54dd0 ffffe68a`86222840 ffffaa0d`ca2ed080 ffffaa0d`c9d54dd0 : nt!MiShareExistingControlArea+0xc2
ffffe68a`862226d0 fffff801`553daab4 : ffffaa0d`cbadfd50 00000000`00000000 ffffaa0d`c9d54dd0 00000000`00000000 : nt!MiCreateImageOrDataSection+0x1a3
ffffe68a`862227c0 fffff801`553da10f : 00000000`01000000 ffffe68a`86222b80 00000000`00000001 00000000`00000010 : nt!MiCreateSection+0xf4
ffffe68a`86222940 fffff801`553d9ea0 : 0000008a`de6ff6d8 00000000`0000000d 00000000`00000000 00000000`00000001 : nt!MiCreateSectionCommon+0x1ff
ffffe68a`86222a20 fffff801`54fd2d18 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateSection+0x60
ffffe68a`86222a90 00007ffc`4b3bca04 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000008a`de6ff688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`4b3bca04


THREAD_SHA1_HASH_MOD_FUNC:  fc266d5b7cde156fa3d8cf724f4eb60cf181aa9b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  fcbf038e544da419ca7925d224f02f4fa18d65c7

THREAD_SHA1_HASH_MOD:  c679893896b7ac49f728be5210ad6454910d2317

FOLLOWUP_IP:
nt!KeAccumulateTicks+1cc061
fffff801`54feeac1 cc              int     3

FAULT_INSTR_CODE:  ab3944cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KeAccumulateTicks+1cc061

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  12dcb470

IMAGE_VERSION:  10.0.18362.535

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1cc061

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

PRIMARY_PROBLEM_CLASS:  0x133_ISR_nt!KeAccumulateTicks

TARGET_TIME:  2019-12-16T10:29:33.000Z

OSBUILD:  18362

OSSERVICEPACK:  535

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1980-01-11 18:53:20

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  5b00

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x133_isr_nt!keaccumulateticks

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Followup:     MachineOwner
---------
 
Amd Ryzen Master kullanmıyorum ama ASUS Armory Crate ile My ASUS programları yüklü. Tekrar oluşursa yine dosya gönderirim o halde. Bayadır stabil çalışıyor zaten şarjdayken hiç böyle bir durum olmamıştı pilde oynarken olmuştu sonra pilde de denedim fakat hiçbir sorun yaşamadım.

Donduğu esnada çıkan yoğun zırıltı sesi normal mi o halde aklıma takıldı. Videosu da var ama yükleniyor mu buraya bilmiyorum henüz forumda yeniyim. Bazen de oyunlara ilk girdiğim zaman veya oyun içerisinde hafif bir cızırtı geliyor sağ kısımdan. O kısımda bildiğim kadarı ile ekran kartı, ssd ve fan var ama fan sesi değil, coil whine sesini andırıyor ama çok belli belirsiz onun da videosunu çektim.

Donanımsal bir sorun yoktur değil mi ? Servise göndermeme gerek var mı cihazı ? gereksiz yere verilerim silinsin istemiyorum servise göndererek.
 
Hocam konu dışı ama ben de aynı laptopu düşünüyorum.Sorum şu HOİ4 ve EU4 de denediniz mi oyunu? Ryzen işlemcilerin tek çekirdek performansından dolayı GS oyunlarında düşük FPS verdirdigini okumuştum da
 
@Pwieh Yok hocam oynadığım oyunlar değil malesef. Ama genel oyun performansı olarak çok memnun olduğumu söyleyebilirim.
@MayCrasH Evet haklısınız. Ama donduğu esnada yoğun bir zırıtlı sesi de olduğu için biraz korktum açıkçası. Servise göndermelik bir durum yok o halde.
Biraz konu dışı olacak ama şunu da sorayım. Bazı oyunlarda 90 derecelere çıkıp geri 83-85 dercelere indiği oluyor işlemcinin, ekran kartı maximum 75 derece gördüm bu ısılar normal mi ?
 
Son düzenleme:
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Yeni konular

Geri
Yukarı