Çözüldü R5 3500X sistemde mavi ekran hatası

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

Cihan genç

Hectopat
Katılım
3 Ocak 2021
Mesajlar
25
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
MSI B450 Tomahawk Max.

Ryzen 5 3500X.

Kingston HyperX Fury 8 GB 3200MHz DDR4 RAM hx432c16fb3/8. X 2.

Kingston A2000 SA2000M8/500G M.2 PCI-Express 3.0 SSD.

Palit GTX 1650 Super gp OC.

Thermaltake TR2 s 650W.

Sistem topladım sürekli fakli farkli mavi ekran hatası aliyorum sebebi ne olabilir?
 
Son düzenleyen: Moderatör:
 
Windows 10 20H2 sürümüne geçin.

Aşağıdaki rehberi uygulayın.

[CODE title="Kod"]
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\maksu\Downloads\010521-6750-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 18362 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff804`78200000 PsLoadedModuleList = 0xfffff804`786461b0
Debug session time: Tue Jan 5 08:52:54.375 2021 (UTC + 3:00)
System Uptime: 0 days 0:03:07.056
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`783c3b20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe309`dc963de0=000000000000001e
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4202

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G2EFLS9

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 14586

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: 0

BUGCHECK_P3: 8

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: GoogleUpdate.exe

TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
ffffe309`dc963dd8 fffff804`783e91a9 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
ffffe309`dc963de0 fffff804`783d5a5d : ffff91c8`e4723000 ffffe309`dc964670 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x1d33f9
ffffe309`dc964490 fffff804`783d1c43 : ffffe309`dc964b00 00000004`0772d820 ffffe309`dc9648a4 00000000`00000000 : nt!KiExceptionDispatch+0x11d
ffffe309`dc964670 00000000`00000000 : 00000000`00000000 fffff804`00000000 ffffe309`00000000 00007ffc`4a448000 : nt!KiPageFault+0x443


SYMBOL_NAME: nt!KiDispatchException+1d33f9

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.18362.1256

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1d33f9

FAILURE_BUCKET_ID: 0x1E_nt!KiDispatchException

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {4c003660-11e1-3fb7-2474-3522eb7ee67b}

Followup: MachineOwner
---------[/CODE]
 
Ya şu an Windows10 sürümün eski. Windows 10 Update varsa yap. Yoksa yeni bir Windows 10 sürümüne geç.

Ekran kartı değiştirildi ne? Ben sana sürücünü güncelle diyorum.
 

Yeni konular

Geri
Yukarı