RTX 3080 sistemde mavi ekran hatası

İşletim sistemi
Windows 10

ydagli42

Kilopat
Katılım
25 Ocak 2015
Mesajlar
1.614
Makaleler
1
RAM
g skill gb 3200mhz
SSD veya HDD modeli
crucial p5 plus m2 gen4
Ekran kartı
RTX 3080
Anakart
Z690
İşlemci
i5 12600K
3 hafta önce aldığım yeni bilgisayarımda kişisel bilgisayarınız bir sorunla karşılaştı hatası almaya başladım. 10 dakikada bir bilgisayarı yeniden başlatıyor mavi ekran alt kısımdaki stop code her zaman farklı bir kod çıkıyor. Araştırıp birkaç çözüm denedim olmadı en son format attım yine olmadı. Minidump dosyasını paylaştım yardımcı olursanız sevinirim.

Memtest86 sonuç resimdeki gibidir. Test yaparken XMP kapalıydı mavi ekran alma sebebim RAM'den kaynaklı mı? Yardımcı olursanız sevinirim.

RAM tam model: G.Skill Ripjaws V siyah 16 GB(2x8GB) 3200MHz DDR4 RAM (F4-3200C16D-16gvkb)

IMG_20220813_193302.jpg

IMG_20220813_193328.jpg

IMG_20220813_193411.jpg
 
Son düzenleyen: Moderatör:

Enes3078

Petapat
Süper Moderatör
Sosyal Tayfı
Katılım
28 Nisan 2020
Mesajlar
15.310
Makaleler
14
Çözümler
628
Yer
Malatya
Evet RAM'de bir sorun var. RAM'lerden biri ya da ikisi arızalı. Tek tek deneyip arızalı olanı tespit edip onu varsa garantiye verin. Yoksa da yenisini almanız gerekecek. Arızalı olanı çıkarınca son sonucu belirtirseniz sevinirim.

Kod:
*******************************************************************************
*                                                                             *
*                        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: fffff80722049e8c, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: ffffcb881a42a2d9, 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                                 ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3015

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 12135

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x1e

    Key  : Bugcheck.Code.Register
    Value: 0x1e

    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


FILE_IN_CAB:  081322-2453-01.dmp

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80722049e8c

BUGCHECK_P3: 1

BUGCHECK_P4: ffffcb881a42a2d9

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  ffffcb881a42a2d9

WRITE_ADDRESS: fffff8072236e3b0: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffffcb881a42a2d9

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
fffff90e`c590e4e8 fffff807`220a37fe     : 00000000`0000001e ffffffff`c0000005 fffff807`22049e8c 00000000`00000001 : nt!KeBugCheckEx
fffff90e`c590e4f0 fffff807`21fc550f     : fffff807`2230c000 fffff807`21e00000 0005e5cc`00ab2000 00000000`0010001f : nt!KiFatalExceptionHandler+0x22
fffff90e`c590e530 fffff807`21eb4745     : 00000000`00000000 00000000`00000000 fffff90e`c590eaa0 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0xf
fffff90e`c590e560 fffff807`21eb865e     : fffff90e`c590f498 fffff90e`c590f1e0 fffff90e`c590f498 00000000`00002134 : nt!RtlDispatchException+0x4a5
fffff90e`c590ecb0 fffff807`21fce59d     : 00000000`00000003 00000000`00000001 00000000`00000000 fffff90e`c590f460 : nt!KiDispatchException+0x16e
fffff90e`c590f360 fffff807`21fca77f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x11d
fffff90e`c590f540 fffff807`22049e8c     : ffffcb88`3142b5a0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x43f
fffff90e`c590f6d0 fffff807`21f0beb0     : ffffcb88`00000000 fffff807`0000000c ffff8001`00000002 00000068`00000001 : nt!PpmParkCalculateCoreParkingMask+0x12c69c
fffff90e`c590f7e0 fffff807`21ec1185     : ffff8001`a2d42f80 ffffcb88`2d8fb000 ffff8001`a2d45f90 ffff8001`00000002 : nt!PpmCheckRun+0x40
fffff90e`c590f870 fffff807`21ec07df     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x305
fffff90e`c590f9b0 fffff807`21fc02c4     : ffffffff`00000000 ffff8001`a2d40180 ffff8001`a2d51440 ffffcb88`3581f0c0 : nt!KiRetireDpcList+0x1ef
fffff90e`c590fbe0 00000000`00000000     : fffff90e`c5910000 fffff90e`c5909000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80722049e8c - nt!PpmParkCalculateCoreParkingMask+12c69c
    [ 0f:8f ]
1 error : !nt (fffff80722049e8c)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup:     memory_corruption
---------
 
KS
KS
ydagli42

ydagli42

Kilopat
Katılım
25 Ocak 2015
Mesajlar
1.614
Makaleler
1
Evet RAM'de bir sorun var. RAM'lerden biri ya da ikisi arızalı. Tek tek deneyip arızalı olanı tespit edip onu varsa garantiye verin. Yoksa da yenisini almanız gerekecek. Arızalı olanı çıkarınca son sonucu belirtirseniz sevinirim.

Kod:
*******************************************************************************
* *
* 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: fffff80722049e8c, The address that the exception occurred at.
Arg3: 0000000000000001, Parameter 0 of the exception.
Arg4: ffffcb881a42a2d9, 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 3015.

 Key : Analysis.DebugAnalysisManager
 Value: Create.

 Key : Analysis.Elapsed.mSec
 Value: 12135.

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

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

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

 Key : Bugcheck.Code.DumpHeader
 Value: 0x1e.

 Key : Bugcheck.Code.Register
 Value: 0x1e.

 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

FILE_IN_CAB: 081322-2453-01.dmp

BUGCHECK_CODE: 1e.

BUGCHECK_P1: ffffffffc0000005.

BUGCHECK_P2: fffff80722049e8c.

BUGCHECK_P3: 1

BUGCHECK_P4: ffffcb881a42a2d9.

EXCEPTION_PARAMETER1: 0000000000000001.

EXCEPTION_PARAMETER2: ffffcb881a42a2d9.

WRITE_ADDRESS: fffff8072236e3b0: Unable to get MiVisibleState.
Unable to get NonPagedPoolStart.
Unable to get NonPagedPoolEnd.
Unable to get PagedPoolStart.
Unable to get PagedPoolEnd.
unable to get nt!MmSpecialPagesInUse
 ffffcb881a42a2d9.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

STACK_TEXT:
fffff90e`c590e4e8 fffff807`220a37fe : 00000000`0000001e ffffffff`c0000005 fffff807`22049e8c 00000000`00000001 : nt!KeBugCheckEx
fffff90e`c590e4f0 fffff807`21fc550f : fffff807`2230c000 fffff807`21e00000 0005e5cc`00ab2000 00000000`0010001f : nt!KiFatalExceptionHandler+0x22
fffff90e`c590e530 fffff807`21eb4745 : 00000000`00000000 00000000`00000000 fffff90e`c590eaa0 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0xf
fffff90e`c590e560 fffff807`21eb865e : fffff90e`c590f498 fffff90e`c590f1e0 fffff90e`c590f498 00000000`00002134 : nt!RtlDispatchException+0x4a5
fffff90e`c590ecb0 fffff807`21fce59d : 00000000`00000003 00000000`00000001 00000000`00000000 fffff90e`c590f460 : nt!KiDispatchException+0x16e
fffff90e`c590f360 fffff807`21fca77f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x11d
fffff90e`c590f540 fffff807`22049e8c : ffffcb88`3142b5a0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x43f
fffff90e`c590f6d0 fffff807`21f0beb0 : ffffcb88`00000000 fffff807`0000000c ffff8001`00000002 00000068`00000001 : nt!PpmParkCalculateCoreParkingMask+0x12c69c
fffff90e`c590f7e0 fffff807`21ec1185 : ffff8001`a2d42f80 ffffcb88`2d8fb000 ffff8001`a2d45f90 ffff8001`00000002 : nt!PpmCheckRun+0x40
fffff90e`c590f870 fffff807`21ec07df : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x305
fffff90e`c590f9b0 fffff807`21fc02c4 : ffffffff`00000000 ffff8001`a2d40180 ffff8001`a2d51440 ffffcb88`3581f0c0 : nt!KiRetireDpcList+0x1ef
fffff90e`c590fbe0 00000000`00000000 : fffff90e`c5910000 fffff90e`c5909000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
 fffff80722049e8c - nt!PpmParkCalculateCoreParkingMask+12c69c
 [ 0f:8f ]
1 error : !nt (fffff80722049e8c)

MODULE_NAME: memory_corruption.

IMAGE_NAME: memory_corruption.

MEMORY_CORRUPTOR: ONE_BIT.

STACK_COMMAND: .cxr; .ecxr ; kb.

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: memory_corruption.
---------

Söylediğiniz gibi tek tek denedim ve sonuç resimlerdeki gibi.
IMG_20220815_172657.jpg IMG_20220815_172712.jpg IMG_20220815_194735.jpg IMG_20220815_194746.jpg IMG_20220815_172755.jpg IMG_20220815_194803.jpg
 

Enes3078

Petapat
Süper Moderatör
Sosyal Tayfı
Katılım
28 Nisan 2020
Mesajlar
15.310
Makaleler
14
Çözümler
628
Yer
Malatya
KS
KS
ydagli42

ydagli42

Kilopat
Katılım
25 Ocak 2015
Mesajlar
1.614
Makaleler
1
Her ikisinde de mi hata çıktı? O zaman ikisini de değişmelisiniz. Derseniz farklı bir anakartta da deneyebilirsiniz. Bunun için bir bilgisayarcı yoluna başvurabilirsiniz ayrıca.

Evet her ikisinde de hata çıktı 3 hafta önce almıştım RAM'leri zaten iade etmeye karar verdim. Umarım yeni RAM'ler gelince aynı hatayı almam yardımınız için teşekkür ederim.
 
Yukarı