Çözüldü 8600K Z370 Overclock WHEA_UNCORRECTABLE_ERROR mavi ekran hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
Durum
Mesaj gönderimine kapalı.
B

by_cyberia

Hectopat
Katılım
1 Mart 2019
Mesajlar
45
Çözümler
1
Merhaba arkadaşlar, sistemde sorun var çözemedim kitleniyor oyunda crash veriyor genelde. Ya da mavi ekran.

Sistem 8600K- Venom sıvı soğutma - Z370 TUF Plus ASUS - 2x8 3200 Corsair RAM - 750W 80+ Power
İşlemci ve ekran kartı 55 derecelerde çalışıyor oyunda. Kitlenme sorunum oyunda oluyor genelde sadece oyun oynuyorum ( PUBG )

W10 64 Bit kullanıyorum, 3 kez kurdum farklı zamanlarda. Tüm driverler güncel, ekran kartı son driver ve eski driverlarda denedim.

Öncelikle Power değiştirdim sorun düzelmedi.
Ekran kartı değiştirdim sorun düzelmedi. ( Ekran kartım 980 Ti hybrid EVGA, 4790K sistemde aylarca sorunsuz çalışan kart )
Windows açlıştaki RAM testini yaptım sorun yok. İlave olarak 3000HMZlik 2x8 başka kit denedim aynı şekilde kitlenme devam ediyor.
3 Kez Windows kurdum.

Anakartın standar 3 mod OC profilinde de yapıyor, YouTube'dan bulduğum detaylı OC profilindede kitleniyor değişen bir şey olmadı.

Manuel OC'de YouTube'daki videoda CPU voltaj 1, 29 da çalıştırıyor link ( https://www.youtube.com/watch?v=EQ15NW1qaxs&t=1197s )

Ben 1, 33 - 1, 34'lerde anca yakalıyorum ama bir zaman sonra kitleniyor oyunda yine.

Prime95 programında 5GHz'de test ettim 80 derecelere geldi işlemci bayada çalıştırdım kitlenmedi sistem.

Genel olarak
RAM ok
İŞlemci OK
Sıcaklıklar OK

Oyunda kitlenmesi aklıma bu 3 parçaya aynı anda yüklendiğimde işi çeviren anakartta gibime geliyor.

Varmı yardımcı olabilecek konu ile ilgili arkadaşlar? Yanlış yaptığım bir noktamı var anlamadım.

Not olarak OC yapmamdaki amaç işlemci standart 4, 1'de çalışyıor ve şu an yetmiyor oyunda, hafiften kastığını hissediyorsun. 5hgz ya da 4, 5GHz'e de alsam hissediyorum oyundaki akıcılığı. 4, 5GHz'e de ayarlasam yetecek aslında ama aynı şekilde kitleniyor.
 

Dosya Ekleri

  • 1016f39a4feacb12cd5fb8f23471b2a6.jpeg
    1016f39a4feacb12cd5fb8f23471b2a6.jpeg
    272,7 KB · Görüntüleme: 66
Son düzenleyen: Moderatör:
Çözüm
MayCrasH
İşlemci yanıt vermeyi kesiyor, yani kapanıyor, ya GHz düşürün ya da biraz daha voltaj verin.

Neden oradaki adamın aynısını yapamıyorum diye soracak olursan silikon kalitesi diyebilirim.

Ayın 15'inde aldığın mavi ekran hataları da ekran kartı sürücüsü ile alakalı onunda sürücüsünü DDU ile kaldırın tekrar kurun.

Afterburner, SteelSeries yazılımlarını kaldır.

Rehber: DDU ile Sürücü Kaldırma Rehberi

Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
www.technopat.net www.technopat.net
Kod: 
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffdc090afd1028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000030005, Low order 32-bits of the MCi_STATUS value.

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

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffdc090afd1028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 30005

BUGCHECK_STR:  0x124_GenuineIntel

CPU_COUNT: 6

CPU_MHZ: e10

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  f

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-20-2020 00:39:47.0562

ANALYSIS_VERSION: 10.0.18362.1 x86fre

STACK_TEXT:
ffffb080`41799ad8 fffff806`093a4ff8 : 00000000`00000124 00000000`00000000 ffffdc09`0afd1028 00000000`b2000000 : nt!KeBugCheckEx
ffffb080`41799ae0 fffff806`0c981920 : ffffdc09`041f0620 00000000`00000000 ffffdc09`0afd1028 00000000`00000000 : hal!HalBugCheckSystem+0xd8
ffffb080`41799b20 fffff806`09740a52 : ffffdc09`041f0620 ffffb080`41799ba9 00000000`00000000 ffffdc09`0afd1028 : PSHED!PshedBugCheckSystem+0x10
ffffb080`41799b50 fffff806`093a6956 : ffffb080`41799c70 00000000`00000003 ffffdc09`041f0670 ffffdc09`041f0620 : nt!WheaReportHwError+0x382
ffffb080`41799c10 fffff806`093a6dea : 00000000`00000010 ffffdc09`041f0670 ffffb080`41799dc8 ffffb080`4179a010 : hal!HalpMcaReportError+0x72
ffffb080`41799d70 fffff806`093a6cc4 : ffffdc09`03eb5b20 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2
ffffb080`41799dc0 fffff806`093a6f30 : 00000000`00000006 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0
ffffb080`41799e00 fffff806`093a5fd8 : 00000000`00000000 ffffb080`4179a090 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
ffffb080`41799e30 fffff806`093a71b7 : ffffdc09`03eb5b20 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
ffffb080`41799e60 fffff806`096a4b20 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
ffffb080`41799e90 fffff806`095d05ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
ffffb080`41799ec0 fffff806`095d0271 : 00000000`00000000 00000000`00000000 00000227`bade0000 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffb080`4179a000 00007ffc`1759d7c8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x271
000000aa`a59aa080 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`1759d7c8


THREAD_SHA1_HASH_MOD_FUNC:  4de11a045a075685c6206f99f334fdcf81e00201

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  b81e20147bc97b7f4cdb24c82387f6cd05f9a6b5

THREAD_SHA1_HASH_MOD:  e68de900930b6f9798c6a02efd69edc806b33cb0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE_UNKNOWN

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE_UNKNOWN

PRIMARY_PROBLEM_CLASS:  0x124_GenuineIntel_PROCESSOR_MAE_UNKNOWN

TARGET_TIME:  2020-02-19T20:02:24.000Z

OSBUILD:  18362

OSSERVICEPACK:  657

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:  2005-04-23 04:40:32

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME:  1756

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_mae_unknown

FAILURE_ID_HASH:  {d1b54118-491d-1f97-b145-f80457d2955b}

Followup:     MachineOwner
---------
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: fffff8028ebb054e, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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

*** WARNING: Unable to verify timestamp for nvlddmkm.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: ffffffffc0000005

BUGCHECK_P2: fffff8028ebb054e

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: fffff8027f1733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffffffffffffff

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

FAULTING_IP:
nvlddmkm+71054e
fffff802`8ebb054e 488b01 mov rax,qword ptr [rcx]

EXCEPTION_PARAMETER2: ffffffffffffffff

BUGCHECK_STR: 0x1E_c0000005_R

CPU_COUNT: 6

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: TslGame.exe

CURRENT_IRQL: 8

ANALYSIS_SESSION_HOST: DESKTOP-18V31A3

ANALYSIS_SESSION_TIME: 02-20-2020 00:42:13.0028

ANALYSIS_VERSION: 10.0.18362.1 x86fre

DPC_STACK_BASE: FFFFF80282C10FB0

LAST_CONTROL_TRANSFER: from fffff8027eea663e to fffff8027edc1510

STACK_TEXT:
fffff802`82c0d5f8 fffff802`7eea663e : 00000000`0000001e ffffffff`c0000005 fffff802`8ebb054e 00000000`00000000 : nt!KeBugCheckEx
fffff802`82c0d600 fffff802`7edca33f : fffff802`7f111000 fffff802`7ec00000 0005e530`00ab6000 00000000`0010001f : nt!KiFatalExceptionHandler+0x22
fffff802`82c0d640 fffff802`7ecc2f15 : 00000000`00000000 00000000`00000000 fffff802`82c0dbb0 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0xf
fffff802`82c0d670 fffff802`7ecc74ae : fffff802`82c0e5a8 fffff802`82c0e2f0 fffff802`82c0e5a8 00000000`00000000 : nt!RtlDispatchException+0x4a5
fffff802`82c0ddc0 fffff802`7edd351d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16e
fffff802`82c0e470 fffff802`7edcf2a2 : 00000400`00000400 00000000`00000000 00000000`00000020 00000000`00000000 : nt!KiExceptionDispatch+0x11d
fffff802`82c0e650 fffff802`8ebb054e : 00000000`00000001 fffff802`8ebcbcd4 ffff9f08`9bd3a840 ffff9f08`9cf62530 : nt!KiGeneralProtectionFault+0x322
fffff802`82c0e7e0 00000000`00000001 : fffff802`8ebcbcd4 ffff9f08`9bd3a840 ffff9f08`9cf62530 ffff9f08`9bd3a840 : nvlddmkm+0x71054e
fffff802`82c0e7e8 fffff802`8ebcbcd4 : ffff9f08`9bd3a840 ffff9f08`9cf62530 ffff9f08`9bd3a840 ffff9f08`9bd3a840 : 0x1
fffff802`82c0e7f0 ffff9f08`9bd3a840 : ffff9f08`9cf62530 ffff9f08`9bd3a840 ffff9f08`9bd3a840 ffff9f08`9b2a1af0 : nvlddmkm+0x72bcd4
fffff802`82c0e7f8 ffff9f08`9cf62530 : ffff9f08`9bd3a840 ffff9f08`9bd3a840 ffff9f08`9b2a1af0 00000003`00000000 : 0xffff9f08`9bd3a840
fffff802`82c0e800 ffff9f08`9bd3a840 : ffff9f08`9bd3a840 ffff9f08`9b2a1af0 00000003`00000000 00000400`00000400 : 0xffff9f08`9cf62530
fffff802`82c0e808 ffff9f08`9bd3a840 : ffff9f08`9b2a1af0 00000003`00000000 00000400`00000400 00000000`00000000 : 0xffff9f08`9bd3a840
fffff802`82c0e810 ffff9f08`9b2a1af0 : 00000003`00000000 00000400`00000400 00000000`00000000 00000000`00000020 : 0xffff9f08`9bd3a840
fffff802`82c0e818 00000003`00000000 : 00000400`00000400 00000000`00000000 00000000`00000020 00000000`00000000 : 0xffff9f08`9b2a1af0
fffff802`82c0e820 00000400`00000400 : 00000000`00000000 00000000`00000020 00000000`00000000 00000000`00000000 : 0x00000003`00000000
fffff802`82c0e828 00000000`00000000 : 00000000`00000020 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000400`00000400


THREAD_SHA1_HASH_MOD_FUNC: 6c83489e084ddf9828daf61b28b927f419e77bde

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 428521c3fe404f6051a402f018b1fd2f6a2cb525

THREAD_SHA1_HASH_MOD: 38daaeb8e5680cd01659e257c1e40cb07d148039

FOLLOWUP_IP:
nvlddmkm+71054e
fffff802`8ebb054e 488b01 mov rax,qword ptr [rcx]

FAULT_INSTR_CODE: 48018b48

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: nvlddmkm+71054e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5e3218c0

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 71054e

FAILURE_BUCKET_ID: 0x1E_c0000005_R_nvlddmkm!unknown_function

BUCKET_ID: 0x1E_c0000005_R_nvlddmkm!unknown_function

PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_R_nvlddmkm!unknown_function

TARGET_TIME: 2020-02-15T19:40:57.000Z

OSBUILD: 18362

OSSERVICEPACK: 657

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: 2005-04-23 04:40:32

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME: e17c

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_nvlddmkm!unknown_function

FAILURE_ID_HASH: {5d60e010-dfb5-f385-5e0f-7c104332ff0c}

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

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: fffff8062e90c879, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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

*** WARNING: Unable to verify timestamp for nvlddmkm.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: ffffffffc0000005

BUGCHECK_P2: fffff8062e90c879

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: fffff8061a5733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffffffffffffff

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

FAULTING_IP:
nvlddmkm+75c879
fffff806`2e90c879 498bbe682d0000 mov rdi,qword ptr [r14+2D68h]

EXCEPTION_PARAMETER2: ffffffffffffffff

BUGCHECK_STR: 0x1E_c0000005_R

CPU_COUNT: 6

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: Discord.exe

CURRENT_IRQL: b

ANALYSIS_SESSION_HOST: DESKTOP-18V31A3

ANALYSIS_SESSION_TIME: 02-20-2020 00:42:10.0970

ANALYSIS_VERSION: 10.0.18362.1 x86fre

EXCEPTION_RECORD: ffffd682d61dc000 -- (.exr 0xffffd682d61dc000)
ExceptionAddress: 0000000000000000
ExceptionCode: 31616956
ExceptionFlags: 00000005
NumberParameters: -703348736
Parameter[0]: ffffd682d6202050
Parameter[1]: 000000000000e39e
Parameter[2]: 000000000000e3ab
Parameter[3]: 000000000000e39e
Parameter[4]: 000000000000e39e
Parameter[5]: 000000000000e39e
Parameter[6]: 0000000000000000
Parameter[7]: 0000000000000000
Parameter[8]: 000000000000e39d
Parameter[9]: 0000000000000000
Parameter[10]: 0000000000000000
Parameter[11]: 0000000000000000
Parameter[12]: 0000000000000000
Parameter[13]: 0000000000000000
Parameter[14]: 0000000000000000

TRAP_FRAME: ffffd682d61df3b0 -- (.trap 0xffffd682d61df3b0)
Unable to read trap frame at ffffd682`d61df3b0

LAST_CONTROL_TRANSFER: from fffff8061a22fea7 to fffff8061a1c1510

STACK_TEXT:
fffff806`21017148 fffff806`1a22fea7 : 00000000`0000001e ffffffff`c0000005 fffff806`2e90c879 00000000`00000000 : nt!KeBugCheckEx
fffff806`21017150 fffff806`1a1d351d : ffffd682`d61dc000 00000000`00000000 ffffd682`d61df3b0 fffff806`2a45dde4 : nt!KiDispatchException+0x168b67
fffff806`21017800 fffff806`1a1cf2a2 : 00000000`00000000 fffff806`2e440a25 fffff806`21017c20 fffff806`27014aa4 : nt!KiExceptionDispatch+0x11d
fffff806`210179e0 fffff806`2e90c879 : 00000000`00000000 00000000`00000005 00000000`00000000 00000000`0000e39e : nt!KiGeneralProtectionFault+0x322
fffff806`21017b70 00000000`00000000 : 00000000`00000005 00000000`00000000 00000000`0000e39e fffff806`2e90c987 : nvlddmkm+0x75c879


THREAD_SHA1_HASH_MOD_FUNC: 62a6ef306d26a017a735c721928ed962f2eaa457

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 98e2cba193f6c2815b4ba5a89415af9b95c1f265

THREAD_SHA1_HASH_MOD: 4e96c4bcc4ec8f85ee49d7124864474789fdce87

FOLLOWUP_IP:
nvlddmkm+75c879
fffff806`2e90c879 498bbe682d0000 mov rdi,qword ptr [r14+2D68h]

FAULT_INSTR_CODE: 68be8b49

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nvlddmkm+75c879

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5e3218c0

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 75c879

FAILURE_BUCKET_ID: 0x1E_c0000005_R_nvlddmkm!unknown_function

BUCKET_ID: 0x1E_c0000005_R_nvlddmkm!unknown_function

PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_R_nvlddmkm!unknown_function

TARGET_TIME: 2020-02-15T19:56:48.000Z

OSBUILD: 18362

OSSERVICEPACK: 657

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: 2005-04-23 04:40:32

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME: 10e95

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_nvlddmkm!unknown_function

FAILURE_ID_HASH: {5d60e010-dfb5-f385-5e0f-7c104332ff0c}

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


PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffe4001ab80498, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80223c4d664, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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

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

Could not read faulting driver name
*** WARNING: Unable to verify timestamp for win32k.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: ffffe4001ab80498

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80223c4d664

BUGCHECK_P4: 2

READ_ADDRESS: fffff80223b733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffe4001ab80498

FAULTING_IP:
nt!ObGetObjectType+4
fffff802`23c4d664 0fb649e8 movzx ecx,byte ptr [rcx-18h]

MM_INTERNAL_CODE: 2

CPU_COUNT: 6

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-18V31A3

ANALYSIS_SESSION_TIME: 02-20-2020 00:42:17.0603

ANALYSIS_VERSION: 10.0.18362.1 x86fre

TRAP_FRAME: ffffe28a61457660 -- (.trap 0xffffe28a61457660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe4001ab80480 rbx=0000000000000000 rcx=ffffe4001ab804b0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80223c4d664 rsp=ffffe28a614577f8 rbp=ffffd00d4b32ee00
r8=0000000000000000 r9=0000000000000000 r10=fffff80222e024f0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!ObGetObjectType+0x4:
fffff802`23c4d664 0fb649e8 movzx ecx,byte ptr [rcx-18h] ds:ffffe400`1ab80498=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff802237e36d6 to fffff802237c1510

STACK_TEXT:
ffffe28a`614573b8 fffff802`237e36d6 : 00000000`00000050 ffffe400`1ab80498 00000000`00000000 ffffe28a`61457660 : nt!KeBugCheckEx
ffffe28a`614573c0 fffff802`23672eef : ffffe406`1cf80080 00000000`00000000 00000000`00000000 ffffe400`1ab80498 : nt!MiSystemFault+0x1d6966
ffffe28a`614574c0 fffff802`237cf620 : ffffd00d`4b348e00 00000000`000699a6 00000000`00000000 00000000`00091ca2 : nt!MmAccessFault+0x34f
ffffe28a`61457660 fffff802`23c4d664 : fffff802`230abfad 00000000`00040282 00000000`00040282 00000000`00040286 : nt!KiPageFault+0x360
ffffe28a`614577f8 fffff802`230abfad : 00000000`00040282 00000000`00040282 00000000`00040286 ffffe28a`614578f0 : nt!ObGetObjectType+0x4
ffffe28a`61457800 00000000`00040282 : 00000000`00040282 00000000`00040286 ffffe28a`614578f0 ffffd00d`4b32ee00 : BEDaisy+0x2abfad
ffffe28a`61457808 00000000`00040282 : 00000000`00040286 ffffe28a`614578f0 ffffd00d`4b32ee00 fffff802`230ac08f : 0x40282
ffffe28a`61457810 00000000`00040286 : ffffe28a`614578f0 ffffd00d`4b32ee00 fffff802`230ac08f ffffd00d`4bafe440 : 0x40282
ffffe28a`61457818 ffffe28a`614578f0 : ffffd00d`4b32ee00 fffff802`230ac08f ffffd00d`4bafe440 fffff800`e2e00000 : 0x40286
ffffe28a`61457820 ffffd00d`4b32ee00 : fffff802`230ac08f ffffd00d`4bafe440 fffff800`e2e00000 00000000`00004542 : 0xffffe28a`614578f0
ffffe28a`61457828 fffff802`230ac08f : ffffd00d`4bafe440 fffff800`e2e00000 00000000`00004542 00000000`00000000 : 0xffffd00d`4b32ee00
ffffe28a`61457830 ffffd00d`4bafe440 : fffff800`e2e00000 00000000`00004542 00000000`00000000 ffffd00d`4bafe440 : BEDaisy+0x2ac08f
ffffe28a`61457838 fffff800`e2e00000 : 00000000`00004542 00000000`00000000 ffffd00d`4bafe440 fffff802`23cb2793 : 0xffffd00d`4bafe440
ffffe28a`61457840 00000000`00004542 : 00000000`00000000 ffffd00d`4bafe440 fffff802`23cb2793 00000000`00000110 : 0xfffff800`e2e00000
ffffe28a`61457848 00000000`00000000 : ffffd00d`4bafe440 fffff802`23cb2793 00000000`00000110 00000000`00000000 : 0x4542


THREAD_SHA1_HASH_MOD_FUNC: 04b87aef2086de37547f4c00122150c0bbb1ebd5

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6eef85b607676fdfb6706f4dbab6a54318fa457d

THREAD_SHA1_HASH_MOD: 028e1716e906a0700ced313853e11e93281c37d7

FOLLOWUP_IP:
BEDaisy+2abfad
fffff802`230abfad 488b152c78d6ff mov rdx,qword ptr [BEDaisy+0x137e0 (fffff802`22e137e0)]

FAULT_INSTR_CODE: 2c158b48

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: BEDaisy+2abfad

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: BEDaisy

IMAGE_NAME: BEDaisy.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5dce5a59

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 2abfad

FAILURE_BUCKET_ID: AV_R_INVALID_BEDaisy!unknown_function

BUCKET_ID: AV_R_INVALID_BEDaisy!unknown_function

PRIMARY_PROBLEM_CLASS: AV_R_INVALID_BEDaisy!unknown_function

TARGET_TIME: 2020-02-15T18:59:33.000Z

OSBUILD: 18362

OSSERVICEPACK: 657

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: 2005-04-23 04:40:32

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME: 341a

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_r_invalid_bedaisy!unknown_function

FAILURE_ID_HASH: {87fe11a0-6d87-e4e2-4753-299ea15a8beb}

Followup: MachineOwner
---------
[/CODE]
Tarihe göre sırala Puana göre sırala
MayCrasH dedi:
Peki, tekrar hata alırsan dosyası ile birlikte bu mesajın altına paylaş.

*Hata yoksa mesajın altına peki/tamam gibi cümleler yazmasan sevinirim, sonra bana bildirim gelmiyor.*
Genişletmek için tıkla...

Şimdilik sorun yok gibi.
Steelseries yazılımı kaldırmıştım
Msi afteburner tekrar kurdum
4,5 - 4,8 - 5ghz sırayla denedim. Voltaj 1,335 şu anda.
Sıcaklık oyunda 60-65 derecelerde.
 

Dosya Ekleri

  • Ekran Alıntısı.JPG
    Ekran Alıntısı.JPG
    27,2 KB · Görüntüleme: 28
Artı 0 Eksi
Durum
Mesaj gönderimine kapalı.

Benzer konular

defuzts
  • Soru
Z370 AORUS Gaming 3 ve i5-8600K BIOS Güncellemesi sonrası mavi ekran
Mesaj
5
Görüntüleme
518
Murat5038
Murat5038
Recep Baltaş
  • Soru
WHEA_UNCORRECTABLE_ERROR Mavi Ekran Hatası
Mesaj
0
Görüntüleme
1.436
Recep Baltaş
Recep Baltaş
chkjz
  • Soru
i5 8600K Sistemde "Dpc_Watchdog_Violation" Mavi Ekran Hatası
Mesaj
7
Görüntüleme
838
chkjz
chkjz
E
  • Soru
i5 9600K ASUS Z370P overclock sonrası mavi ekran hatası
Mesaj
0
Görüntüleme
584
erdal33
E
Akif9748
  • Çözüldü
Çözüldü  Lenovo Z370 mavi ekran sorunu
Mesaj
3
Görüntüleme
783
283156
2

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı