Sürekli mavi ekran hataları

  • Konuyu başlatan Skyrx
  • Başlangıç Tarihi
  • Mesaj 76
  • Görüntüleme 4.580

Skyrx

Kilopat
Katılım
18 Kasım 2015
Mesajlar
98
Daha fazla  
Cinsiyet
Erkek
Yeni bilgisayarda sürekli mavi ekran hatası yiyorum. Temiz format attım ama genede aynı yardımcı olabilecek var mı?
 
Mallesef duzelmemis
Kardeşim bu işi hızlı bir şekilde çözmek istiyorsan sıkıntı en çok neydeyse ona göre bir bileşen satın al yoksa mavi ekranla başa çıkılmaz. Garantiye gönderirsin 20 iş günü beklersin sorunsuz diye geri yollarlar. Fark ettiğim kadarıyla da zaten bu sorun pek yazılımsal bir soruna benzemiyor.
 
Ve Memtest86 ile bellek testi yapınız tekrar.
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: fffff80019cbfb84, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffffffffffffff

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba

FAULTING_IP:
nt!KiTimerWaitTest+1f4
fffff800`19cbfb84 0fb74602        movzx   eax,word ptr [rsi+2]

EXCEPTION_PARAMETER2:  ffffffffffffffff

BUGCHECK_STR:  0x1E_c0000005_R

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from fffff80019ef455e to fffff80019df4540

STACK_TEXT: 
fffff800`1ddc0158 fffff800`19ef455e : 00000000`0000001e ffffffff`c0000005 fffff800`19cbfb84 00000000`00000000 : nt!KeBugCheckEx
fffff800`1ddc0160 fffff800`19dfd402 : fffff800`19ef453c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff800`1ddc01a0 fffff800`19c52d97 : fffff800`1ddc0710 00000000`00000000 fffff800`1ddabc60 fffff800`19df80ae : nt!RtlpExecuteHandlerForException+0x12
fffff800`1ddc01d0 fffff800`19c519a6 : fffff800`1ddab5f8 fffff800`1ddc0e20 fffff800`1ddab5f8 ffff8205`632136c0 : nt!RtlDispatchException+0x297
fffff800`1ddc08f0 fffff800`19df53d2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff800`1ddc0fb0 fffff800`19df53a0 : fffff800`19e065a5 ffff8205`ffffffff 00000000`00000000 ffff8205`608e2400 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff800`1ddab4b8 fffff800`19e065a5 : ffff8205`ffffffff 00000000`00000000 ffff8205`608e2400 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff800`1ddab4c0 fffff800`19e022e0 : 00000000`00000003 00000000`00250eaa fffff800`15494180 fffff800`19d29cc0 : nt!KiExceptionDispatch+0x125
fffff800`1ddab6a0 fffff800`19cbfb84 : ffff8205`632136c8 00000000`00000000 ffff8205`63213790 e36d0f00`00001022 : nt!KiGeneralProtectionFault+0x320
fffff800`1ddab830 fffff800`19cbf71c : ffff8205`632136c0 00000000`00000000 fffff800`1ddabb18 00000000`00000000 : nt!KiTimerWaitTest+0x1f4
fffff800`1ddab8e0 fffff800`19ce4f09 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00161696 : nt!KiProcessExpiredTimerList+0xdc
fffff800`1ddab9d0 fffff800`19df80ae : 00000000`00000000 fffff800`15494180 fffff800`1a727600 ffff8205`619e4080 : nt!KiRetireDpcList+0x9d9
fffff800`1ddabc60 00000000`00000000 : fffff800`1ddac000 fffff800`1dda6000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80019d966be-fffff80019d966c1  4 bytes - nt!MiFreeUltraMapping+32
    [ a0 7d fb f6:c0 bb 77 ef ]
4 errors : !nt (fffff80019d966be-fffff80019d966c1)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000005bb5a36e8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8056c8decc1, address which referenced memory

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


READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 00000005bb5a36e8

CURRENT_IRQL:  2

FAULTING_IP:
nt!KeWaitForSingleObject+1e1
fffff805`6c8decc1 483901          cmp     qword ptr [rcx],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  AV

PROCESS_NAME:  EpicGamesLaunc

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

TRAP_FRAME:  ffff8c0f8b0687e0 -- (.trap 0xffff8c0f8b0687e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff8f8ebb5a36e8 rbx=0000000000000000 rcx=00000005bb5a36e8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8056c8decc1 rsp=ffff8c0f8b068970 rbp=ffff8c0f8b068a01
 r8=0000000000000000  r9=00000010e4306857 r10=0000000000000002
r11=fffff780000003b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!KeWaitForSingleObject+0x1e1:
fffff805`6c8decc1 483901          cmp     qword ptr [rcx],rax ds:00000005`bb5a36e8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8056ca06469 to fffff8056c9f4540

STACK_TEXT: 
ffff8c0f`8b068698 fffff805`6ca06469 : 00000000`0000000a 00000005`bb5a36e8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff8c0f`8b0686a0 fffff805`6ca02769 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff805`6c8dffad : nt!KiBugCheckDispatch+0x69
ffff8c0f`8b0687e0 fffff805`6c8decc1 : ffff8c0f`0000000b fffff805`6ccef721 ffffb901`d7389101 ffff8f8e`bb62c1c0 : nt!KiPageFault+0x469
ffff8c0f`8b068970 fffff805`6ccf0e41 : ffff8f8e`bb5a36e0 00000000`00000006 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x1e1
ffff8c0f`8b068a60 fffff805`6ccf0eea : ffff8f8e`bb62c080 000000a3`30c5fa18 00000000`00000000 fffff805`6ca05d18 : nt!ObWaitForSingleObject+0x91
ffff8c0f`8b068ac0 fffff805`6ca05eb8 : 0000023d`6849da80 00000000`00000000 ffff8c0f`8b068b18 ffffffff`fffe7960 : nt!NtWaitForSingleObject+0x6a
ffff8c0f`8b068b00 00007ff9`312abe14 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000a3`30c5f9e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`312abe14


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8056c9966be-fffff8056c9966c1  4 bytes - nt!MiFreeUltraMapping+32
    [ a0 7d fb f6:80 2d 5b b6 ]
4 errors : !nt (fffff8056c9966be-fffff8056c9966c1)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

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

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


READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffffffffffffff

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba

FAULTING_IP:
NETIO!RtlCopyMdlToBuffer+ba
fffff801`483495ea c3              ret

EXCEPTION_PARAMETER2:  ffffffffffffffff

BUGCHECK_STR:  0x1E_c0000005_R

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  EpicGamesLaunc

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from fffff80143c30005 to fffff80143bf4540

STACK_TEXT: 
ffffee8d`6091d8c8 fffff801`43c30005 : 00000000`0000001e ffffffff`c0000005 fffff801`483495ea 00000000`00000000 : nt!KeBugCheckEx
ffffee8d`6091d8d0 fffff801`43c065ac : 00000000`00000000 33333333`33333333 00000000`00000000 00000000`0000021c : nt!KiDispatchException+0x1de7e5
ffffee8d`6091df90 fffff801`43c022e0 : 00000000`00000000 00001f80`00000029 00000000`0000004e 000001bf`68851000 : nt!KiExceptionDispatch+0x12c
ffffee8d`6091e170 fffff801`483495ea : 8f0e79fd`fa59487d 00000000`00000000 00000000`00000000 00000000`000005a5 : nt!KiGeneralProtectionFault+0x320
ffffee8d`6091e308 8f0e79fd`fa59487d : 00000000`00000000 00000000`00000000 00000000`000005a5 00000000`00000001 : NETIO!RtlCopyMdlToBuffer+0xba
ffffee8d`6091e310 00000000`00000000 : 00000000`00000000 00000000`000005a5 00000000`00000001 ffffee8d`6091e348 : 0x8f0e79fd`fa59487d


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !FLTMGR
    fffff801420a995c-fffff801420a995d  2 bytes - FLTMGR!FltpDataScanCsqAcquireLock+1c
    [ 48 ff:4c 8b ]
    fffff801420a9963-fffff801420a9967  5 bytes - FLTMGR!FltpDataScanCsqAcquireLock+23 (+0x07)
    [ 0f 1f 44 00 00:e8 58 0f a3 01 ]
    fffff801420a9a2e-fffff801420a9a2f  2 bytes - FLTMGR!FltpDataScanCsqInsertIrp+6e (+0xcb)
    [ 48 ff:4c 8b ]
    fffff801420a9a35-fffff801420a9a39  5 bytes - FLTMGR!FltpDataScanCsqInsertIrp+75 (+0x07)
    [ 0f 1f 44 00 00:e8 f6 bf ac 01 ]
    fffff801420a9a51-fffff801420a9a52  2 bytes - FLTMGR!FltpDataScanCsqInsertIrp+91 (+0x1c)
    [ 48 ff:4c 8b ]
    fffff801420a9a58-fffff801420a9a5c  5 bytes - FLTMGR!FltpDataScanCsqInsertIrp+98 (+0x07)
    [ 0f 1f 44 00 00:e8 b3 57 9e 01 ]
    fffff801420a9aad-fffff801420a9aae  2 bytes - FLTMGR!FltpDataScanCsqReleaseLock+d (+0x55)
    [ 48 ff:4c 8b ]
    fffff801420a9ab4-fffff801420a9ab8  5 bytes - FLTMGR!FltpDataScanCsqReleaseLock+14 (+0x07)
    [ 0f 1f 44 00 00:e8 87 06 97 01 ]
    fffff801420a9bb8-fffff801420a9bb9  2 bytes - FLTMGR!FltpQueueDataScanSynchronization+90 (+0x104)
    [ 48 ff:4c 8b ]
    fffff801420a9bbf-fffff801420a9bc3  5 bytes - FLTMGR!FltpQueueDataScanSynchronization+97 (+0x07)
    [ 0f 1f 44 00 00:e8 2c 25 a1 01 ]
    fffff801420a9bde-fffff801420a9bdf  2 bytes - FLTMGR!FltpQueueDataScanSynchronization+b6 (+0x1f)
    [ 48 ff:4c 8b ]
37 errors : !FLTMGR (fffff801420a995c-fffff801420a9bdf)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 00007ffa9504be14, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffe80f028bcb80, Call type (0 - system call, 1 - worker routine)

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


FAULTING_IP:
+2181d474e59359
00007ffa`9504be14 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x1

PROCESS_NAME:  EpicGamesLaunc

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from fffff8007b606469 to fffff8007b5f4540

STACK_TEXT: 
ffffe80f`028bc9b8 fffff800`7b606469 : 00000000`00000001 00007ffa`9504be14 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffffe80f`028bc9c0 fffff800`7b606333 : 00000000`00000000 00000000`00000000 ffffe80f`028bcb18 ffffffff`fffe7960 : nt!KiBugCheckDispatch+0x69
ffffe80f`028bcb00 00007ffa`9504be14 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
0000006f`4c7efa58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`9504be14


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8007b5966be-fffff8007b5966c1  4 bytes - nt!MiFreeUltraMapping+32
    [ a0 7d fb f6:60 f1 e2 c5 ]
    fffff8007b606391-fffff8007b606394  4 bytes - nt!KiSystemServiceExitPico+25c (+0x6fcd3)
    [ ff d0 0f 1f:e8 4a df 60 ]
    fffff8007b6063ec-fffff8007b6063ef  4 bytes - nt!KiSystemServiceExitPico+2b7 (+0x5b)
    [ ff d0 0f 1f:e8 ef de 60 ]
12 errors : !nt (fffff8007b5966be-fffff8007b6063ef)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffff980db8d0e5e0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffff980db8d0e538, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


TRAP_FRAME:  ffff980db8d0e5e0 -- (.trap 0xffff980db8d0e5e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8027eebb6e8 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe2034a9ca1a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80280a6fbc7 rsp=ffff980db8d0e770 rbp=0000000000002c20
 r8=0000000000000000  r9=0000000000000051 r10=0000000000000000
r11=fffff80280600000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
nt!KiCancelTimer+0x18e587:
fffff802`80a6fbc7 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffff980db8d0e538 -- (.exr 0xffff980db8d0e538)
ExceptionAddress: fffff80280a6fbc7 (nt!KiCancelTimer+0x000000000018e587)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x139

PROCESS_NAME:  UnrealCEFSubPr

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000409 - Sistem, bu uygulamada y

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - Sistem, bu uygulamada y

EXCEPTION_PARAMETER1:  0000000000000003

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

EXCEPTION_STR:  0x0

LAST_CONTROL_TRANSFER:  from fffff80280a06469 to fffff802809f4540

STACK_TEXT: 
ffff980d`b8d0e2b8 fffff802`80a06469 : 00000000`00000139 00000000`00000003 ffff980d`b8d0e5e0 ffff980d`b8d0e538 : nt!KeBugCheckEx
ffff980d`b8d0e2c0 fffff802`80a06890 : 0004db02`0000ffff 00000000`304cf1ff 00000000`ffffffff fffff802`00000000 : nt!KiBugCheckDispatch+0x69
ffff980d`b8d0e400 fffff802`80a04c23 : 00000001`ffffffff fffffff6`00000007 ffff980d`b8d0e7c0 00000000`000000c0 : nt!KiFastFailDispatch+0xd0
ffff980d`b8d0e5e0 fffff802`80a6fbc7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x323
ffff980d`b8d0e770 fffff802`808e010c : ffffcc81`00000000 00000000`00000000 ffff980d`b8d0ea00 00000000`00000000 : nt!KiCancelTimer+0x18e587
ffff980d`b8d0e820 fffff802`808df46f : ffffe203`00000003 00000000`00000001 ffff980d`b8d0e9e0 00000000`00000000 : nt!KiSwapThread+0x6cc
ffff980d`b8d0e8d0 fffff802`808ded13 : ffffe203`00000051 fffff802`00000000 00000000`00040201 ffffe203`4a9ca1c0 : nt!KiCommitThreadWait+0x14f
ffff980d`b8d0e970 fffff802`80cf0e41 : ffffe203`4d4dc960 00000000`00000006 00000000`00000001 ffffe203`4d4dc000 : nt!KeWaitForSingleObject+0x233
ffff980d`b8d0ea60 fffff802`80cf0eea : ffffe203`4a9ca080 00000073`dd8ef5e8 00000000`00000000 00000073`dd8ee9f0 : nt!ObWaitForSingleObject+0x91
ffff980d`b8d0eac0 fffff802`80a05eb8 : ffffe203`4a9ca080 ffffe203`49ca13e0 ffff980d`b8d0eb18 ffffffff`ffe04300 : nt!NtWaitForSingleObject+0x6a
ffff980d`b8d0eb00 00007ffd`4bb4be14 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000073`dd8ef5b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`4bb4be14


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff802809966be-fffff802809966c1  4 bytes - nt!MiFreeUltraMapping+32
    [ a0 7d fb f6:20 7f fe fc ]
4 errors : !nt (fffff802809966be-fffff802809966c1)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------
 
Ağ kartını nasıl kaldırabılırım ve anakartım B450 M GAMING X anakartım var buradakı lan drıverını mı ındırcem sıldıkten sonra.
 
aygıt yoneticinden ağ bağdaştırıcılarından
Realtek Gaming GbE Family Controller
olanı kaldırdım ve sıteden indirdim en güncel olanı
memteset de denıcem
 
Bundan sonra tekrar mavi ekran alırsanız ağ kartının sürücüsünü kaldırın ve yüklemeyin. Memtest sonucunu bekliyorum .
 
Son düzenleme:

Bu konuyu görüntüleyen kullanıcılar

Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…