CRITICAL_STRUCTURE_CORRUPTION mavi ekran hatası

Mehmet12

Kilopat
Katılım
11 Ağustos 2014
Mesajlar
30
Daha fazla  
Cinsiyet
Erkek
Merhabalar. Son birkaç gündür mavi ekran veriyor bilgisayarım. Mavi ekran minidump dosyalarını paylaşıyorum. Bilgisi olan arkadaşlar yardımcı olur musunuz? Teşekkürler.

mavi_ekran.rar dosyasını indir - download
  • Ryzen 5 3600
  • Gigabyte B450M anakart
  • ASUS ROG STRIX GTX 1070 ekran kartı
  • Corsair 240GB SSD
  • Corsair 2X 8 GB 2400MHz RAM
  • Corsair VS650 PSU
 
Son düzenleyen: Moderatör:
Virüs taraması yap.
Kod:
Unable to load image \??\C:\Users\LastLuck26\Desktop\ollly\PCHunter64ar.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PCHunter64ar.sys

ASUS araçlarını kaldır.
Kod:
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a00d64652e2665, Reserved
Arg2: b3b719eab7afd50b, Reserved
Arg3: ffffce0bc9acb960, Failure type dependent information
Arg4: 0000000000000008, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    2a  : Type 4 pool corruption
    2b  : Modification of a function or .pdata
    2c  : Image integrity corruption
    2d  : Processor misconfiguration
    2e  : Type 5 process list corruption
    2f  : Process shadow corruption
    30  : Retpoline code page corruption
    101 : General pool corruption
    102 : Modification of win32k.sys

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:  16299.637.amd64fre.rs3_release_svc.180808-1748

DUMP_TYPE:  2

BUGCHECK_P1: a3a00d64652e2665

BUGCHECK_P2: b3b719eab7afd50b

BUGCHECK_P3: ffffce0bc9acb960

BUGCHECK_P4: 8

CPU_COUNT: c

CPU_MHZ: f98

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  BAD_STACK_0x109

BUGCHECK_STR:  0x109

PROCESS_NAME:  Stranded_Deep.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-04-2020 23:55:26.0357

ANALYSIS_VERSION: 10.0.18362.1 x86fre

DPC_STACK_BASE:  FFFFF801D6C46FB0

STACK_TEXT: 
fffff801`d6c45568 00000000`00000000 : 00000000`00000109 a3a00d64`652e2665 b3b719ea`b7afd50b ffffce0b`c9acb960 : nt!KeBugCheckEx


THREAD_SHA1_HASH_MOD_FUNC:  81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD:  76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID:  BAD_STACK_0x109

PRIMARY_PROBLEM_CLASS:  BAD_STACK_0x109

FAILURE_BUCKET_ID:  BAD_STACK_0x109

TARGET_TIME:  2020-02-04T20:15:41.000Z

OSBUILD:  16299

OSSERVICEPACK:  1087

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:  2019-04-02 07:29:15

BUILDDATESTAMP_STR:  180808-1748

BUILDLAB_STR:  rs3_release_svc

BUILDOSVER_STR:  10.0.16299.637.amd64fre.rs3_release_svc.180808-1748

ANALYSIS_SESSION_ELAPSED_TIME:  39e9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:bad_stack_0x109

FAILURE_ID_HASH:  {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}

Followup:     MachineOwner
---------
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a011e043e2da04, Reserved
Arg2: b3b71e669662e21a, Reserved
Arg3: ffffd287a20c2780, Failure type dependent information
Arg4: 0000000000000008, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    2a  : Type 4 pool corruption
    2b  : Modification of a function or .pdata
    2c  : Image integrity corruption
    2d  : Processor misconfiguration
    2e  : Type 5 process list corruption
    2f  : Process shadow corruption
    30  : Retpoline code page corruption
    101 : General pool corruption
    102 : Modification of win32k.sys

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:  16299.637.amd64fre.rs3_release_svc.180808-1748

DUMP_TYPE:  2

BUGCHECK_P1: a3a011e043e2da04

BUGCHECK_P2: b3b71e669662e21a

BUGCHECK_P3: ffffd287a20c2780

BUGCHECK_P4: 8

CPU_COUNT: c

CPU_MHZ: f98

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  BAD_STACK_0x109

BUGCHECK_STR:  0x109

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-04-2020 23:55:20.0134

ANALYSIS_VERSION: 10.0.18362.1 x86fre

STACK_TEXT: 
ffff8486`2cc129f8 00000000`00000000 : 00000000`00000109 a3a011e0`43e2da04 b3b71e66`9662e21a ffffd287`a20c2780 : nt!KeBugCheckEx


THREAD_SHA1_HASH_MOD_FUNC:  81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD:  76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID:  BAD_STACK_0x109

PRIMARY_PROBLEM_CLASS:  BAD_STACK_0x109

FAILURE_BUCKET_ID:  BAD_STACK_0x109

TARGET_TIME:  2020-02-04T16:04:06.000Z

OSBUILD:  16299

OSSERVICEPACK:  1087

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:  2019-04-02 07:29:15

BUILDDATESTAMP_STR:  180808-1748

BUILDLAB_STR:  rs3_release_svc

BUILDOSVER_STR:  10.0.16299.637.amd64fre.rs3_release_svc.180808-1748

ANALYSIS_SESSION_ELAPSED_TIME:  6003

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:bad_stack_0x109

FAILURE_ID_HASH:  {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}

Followup:     MachineOwner
---------
 
Virüs taraması yap.
Kod:
Unable to load image \??\C:\Users\LastLuck26\Desktop\ollly\PCHunter64ar.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PCHunter64ar.sys

ASUS araçlarını kaldır.
Kod:
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a00d64652e2665, Reserved
Arg2: b3b719eab7afd50b, Reserved
Arg3: ffffce0bc9acb960, Failure type dependent information
Arg4: 0000000000000008, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    2a  : Type 4 pool corruption
    2b  : Modification of a function or .pdata
    2c  : Image integrity corruption
    2d  : Processor misconfiguration
    2e  : Type 5 process list corruption
    2f  : Process shadow corruption
    30  : Retpoline code page corruption
    101 : General pool corruption
    102 : Modification of win32k.sys

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:  16299.637.amd64fre.rs3_release_svc.180808-1748

DUMP_TYPE:  2

BUGCHECK_P1: a3a00d64652e2665

BUGCHECK_P2: b3b719eab7afd50b

BUGCHECK_P3: ffffce0bc9acb960

BUGCHECK_P4: 8

CPU_COUNT: c

CPU_MHZ: f98

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  BAD_STACK_0x109

BUGCHECK_STR:  0x109

PROCESS_NAME:  Stranded_Deep.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-04-2020 23:55:26.0357

ANALYSIS_VERSION: 10.0.18362.1 x86fre

DPC_STACK_BASE:  FFFFF801D6C46FB0

STACK_TEXT:
fffff801`d6c45568 00000000`00000000 : 00000000`00000109 a3a00d64`652e2665 b3b719ea`b7afd50b ffffce0b`c9acb960 : nt!KeBugCheckEx


THREAD_SHA1_HASH_MOD_FUNC:  81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD:  76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID:  BAD_STACK_0x109

PRIMARY_PROBLEM_CLASS:  BAD_STACK_0x109

FAILURE_BUCKET_ID:  BAD_STACK_0x109

TARGET_TIME:  2020-02-04T20:15:41.000Z

OSBUILD:  16299

OSSERVICEPACK:  1087

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:  2019-04-02 07:29:15

BUILDDATESTAMP_STR:  180808-1748

BUILDLAB_STR:  rs3_release_svc

BUILDOSVER_STR:  10.0.16299.637.amd64fre.rs3_release_svc.180808-1748

ANALYSIS_SESSION_ELAPSED_TIME:  39e9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:bad_stack_0x109

FAILURE_ID_HASH:  {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}

Followup:     MachineOwner
---------
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a011e043e2da04, Reserved
Arg2: b3b71e669662e21a, Reserved
Arg3: ffffd287a20c2780, Failure type dependent information
Arg4: 0000000000000008, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    2a  : Type 4 pool corruption
    2b  : Modification of a function or .pdata
    2c  : Image integrity corruption
    2d  : Processor misconfiguration
    2e  : Type 5 process list corruption
    2f  : Process shadow corruption
    30  : Retpoline code page corruption
    101 : General pool corruption
    102 : Modification of win32k.sys

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:  16299.637.amd64fre.rs3_release_svc.180808-1748

DUMP_TYPE:  2

BUGCHECK_P1: a3a011e043e2da04

BUGCHECK_P2: b3b71e669662e21a

BUGCHECK_P3: ffffd287a20c2780

BUGCHECK_P4: 8

CPU_COUNT: c

CPU_MHZ: f98

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  BAD_STACK_0x109

BUGCHECK_STR:  0x109

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-04-2020 23:55:20.0134

ANALYSIS_VERSION: 10.0.18362.1 x86fre

STACK_TEXT:
ffff8486`2cc129f8 00000000`00000000 : 00000000`00000109 a3a011e0`43e2da04 b3b71e66`9662e21a ffffd287`a20c2780 : nt!KeBugCheckEx


THREAD_SHA1_HASH_MOD_FUNC:  81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD:  76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID:  BAD_STACK_0x109

PRIMARY_PROBLEM_CLASS:  BAD_STACK_0x109

FAILURE_BUCKET_ID:  BAD_STACK_0x109

TARGET_TIME:  2020-02-04T16:04:06.000Z

OSBUILD:  16299

OSSERVICEPACK:  1087

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:  2019-04-02 07:29:15

BUILDDATESTAMP_STR:  180808-1748

BUILDLAB_STR:  rs3_release_svc

BUILDOSVER_STR:  10.0.16299.637.amd64fre.rs3_release_svc.180808-1748

ANALYSIS_SESSION_ELAPSED_TIME:  6003

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:bad_stack_0x109

FAILURE_ID_HASH:  {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}

Followup:     MachineOwner
---------
Merhaba. Dediğiniz şekilde ASUS araçlarını kaldırdım. Fakat sistem halen mavi ekran verip yeniden başlıyor. Minidump klasörü boş gözüküyor.
 
  • Mavi ekranın fotoğrafını gönder.
  • Memtest86 testi yap.
  • Virüs taramasından ne haber?
Mavi ekranın resmini alamadan yeniden başlamış şekilde buluyorum bilgisayarı. Minidump klasörüde boş. Dediğiniz şekilde Memtest86 ile test edip temiz güncel format atayım. Sıkıntı olursa yazarım. Teşekkür ederim ilginiz için.

Memtest86 ile test ettim. Fakat bu çıkan hata CPU kaynaklı mı? Yoksa RAM hatası mı?
IMG_20200207_221827.jpg
 
Son düzenleyen: Moderatör:
Uyarı! Bu konu 7 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

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

Technopat Haberler

Geri
Yukarı