İşlemci değişimi sonrası rastgele aralıklar ile mavi ekran hatası

mustafa_ugur_cyln dedi:

İşlemci değişimi sonrası bu hatayı almaya başladım. Sıklıkları değişiyor. Şu an Memtest86 ile RAM'leri tarıyorum ama sıkıntı gözükmüyor. RAM'lerde hata yok.
Güncelleme: İşlemciyi ikinci el almıştım tam incelemedim şimdi arkasına baktım 2 tane direnç gibi bir SMD eksik sanırım bu yüzden alıyorum hataları. İşlemcimim arkası aşağıdaki gibi. Ben buraya 2 tane direnç lehimlettirsem bilgisayarcıda olur mu acaba?

Eki Görüntüle 1465077

Orjinal i5 2300
Eki Görüntüle 1465078

Kod:Panoya kopyala

Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Pc\Desktop\072722-8234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`20a00000 PsLoadedModuleList = 0xfffff803`2162a270
Debug session time: Wed Jul 27 00:30:34.438 2022 (UTC + 3:00)
System Uptime: 0 days 0:09:18.163
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`20df71b0 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffc581`cf7af160=000000000000001e
3: 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: ffffffffc0000094, The exception code that was not handled
Arg2: fffff80320d231b6, The address that the exception occurred at
Arg3: ffff8787b62f5a60, Parameter 0 of the exception
Arg4: 000000000000005a, 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                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: 6842

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 41225

    Key  : Analysis.Init.CPU.mSec
    Value: 1452

    Key  : Analysis.Init.Elapsed.mSec
    Value: 51116

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x1e

    Key  : Bugcheck.Code.Register
    Value: 0x1e

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  072722-8234-01.dmp

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000094

BUGCHECK_P2: fffff80320d231b6

BUGCHECK_P3: ffff8787b62f5a60

BUGCHECK_P4: 5a

EXCEPTION_PARAMETER1:  ffff8787b62f5a60

EXCEPTION_PARAMETER2:  000000000000005a

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MsMpEng.exe

STACK_TEXT:
ffffc581`cf7af158 fffff803`20ef5a6e     : 00000000`0000001e ffffffff`c0000094 fffff803`20d231b6 ffff8787`b62f5a60 : nt!KeBugCheckEx
ffffc581`cf7af160 fffff803`20e00072     : fffff803`20ef5a4c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
ffffc581`cf7af1a0 fffff803`20ce6dd7     : ffffc581`cf7af710 00000000`00000000 ffffb108`ad04cfb0 fffff803`20dfe1f5 : nt!RtlpExecuteHandlerForException+0x12
ffffc581`cf7af1d0 fffff803`20ce59d6     : ffffb108`ad04c7b8 ffffc581`cf7afe20 ffffb108`ad04c7b8 00000000`00000064 : nt!RtlDispatchException+0x297
ffffc581`cf7af8f0 fffff803`20df8042     : 00030003`00030003 00030003`00030003 00030003`00030003 00030003`00030003 : nt!KiDispatchException+0x186
ffffc581`cf7affb0 fffff803`20df8010     : fffff803`20e092a5 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffb108`ad04c678 fffff803`20e092a5     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffb108`ad04c680 fffff803`20e01f0a     : 00000000`00000000 ffff8787`b928b0c0 00000000`00000008 00000000`00000000 : nt!KiExceptionDispatch+0x125
ffffb108`ad04c860 fffff803`20d231b6     : ffffc581`cf6282e8 ffffb108`ad04caa9 fffff803`2161ec48 00000000`00000000 : nt!KiDivideErrorFault+0x30a
ffffb108`ad04c9f0 fffff803`20d22fde     : 00000172`3d174600 00000000`00000002 fffff803`216fc4e0 ffff8787`b6598010 : nt!PpmPerfSelectProcessorState+0x1a6
ffffb108`ad04cb10 fffff803`20c1f5c0     : ffffc581`cf792240 ffffb108`ad04ce80 ffffb108`ad04ccb0 ffffb108`ad04ce80 : nt!PpmPerfSelectProcessorStates+0x5e
ffffb108`ad04cb40 fffff803`20c9a24e     : ffffc581`cf792240 ffff8787`b390b000 00000000`00000000 ffffb108`00000002 : nt!PpmCheckRun+0x40
ffffb108`ad04cbb0 fffff803`20c99534     : ffffc581`cf78f180 2a5232cf`00000000 00000000`00000002 00000000`00000004 : nt!KiExecuteAllDpcs+0x30e
ffffb108`ad04cd20 fffff803`20dfe1f5     : 779fe3b2`a6509fad ffffc581`cf78f180 00000000`00000000 000001dd`e6b326c3 : nt!KiRetireDpcList+0x1f4
ffffb108`ad04cfb0 fffff803`20dfdfe0     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
ffffb108`aefaaad0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


SYMBOL_NAME:  nt!PpmPerfSelectProcessorState+1a6

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.1288

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1a6

FAILURE_BUCKET_ID:  0x1E_C0000094_nt!PpmPerfSelectProcessorState

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {bde8e2c9-df0d-be8a-6751-181f4d2268d0}

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

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

Enes3078 dedi:

Bahsettiğiniz gibi eksik varsa sorun olabilir, ayrıca o düzeyde bir işi başarıyla yapabilecek kişi sayısı çok değil, iade imkanınız varsa iade etmenizi öneririm.

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