Çözüldü PFN_REFERENCE_COUNT mavi ekran hatası

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

ozgrdmr

Decapat
Katılım
9 Ekim 2018
Mesajlar
22
Windows 10 Pro kullanmaktayım, yaklaşık 2 aydır farklı farklı mavi ekran hataları alıyorum. Temiz kurulum yapmama rağmen hala da bu problem devam etmekte, sorun neyden kaynaklıdır? Yardımcı olabilir misiniz? Minidump dosyaları ektedir:

Sistem:
  • 2700X
  • MSI X470 GAMING M7 AC
  • GTX 1080 Ti
  • Samsung 970 Evo M.2 SSD
 
Son düzenleyen: Moderatör:
Çözüm
Memtest86 testi yapar mısın?
Kod:
KERNEL_APC_PENDING_DURING_EXIT (20)
The key data item is the thread's APC disable count.
If this is non-zero, then this is the source of the problem.
The APC disable count is decremented each time a driver calls
KeEnterCriticalRegion, FsRtlEnterFileSystem, or acquires a mutex.  The APC
disable count is incremented each time a driver calls KeLeaveCriticalRegion,
FsRtlExitFileSystem, or KeReleaseMutex.  Since these calls should always be in
pairs, this value should be zero when a thread exits.  A negative value
indicates that a driver has disabled APC calls without re-enabling them.  A
positive value indicates that the reverse is true.
If you ever see this error, be very suspicious of all drivers installed on the
machine -- especially unusual or non-standard drivers.  Third party file
system redirectors are especially suspicious since they do not generally
receive the heavy duty testing that NTFS, FAT, RDR, etc receive.
This current IRQL should also be 0.  If it is not, that a driver's
cancelation routine can cause this bugcheck by returning at an elevated
IRQL.  Always attempt to note what you were doing/closing at the
time of the crash, and note all of the installed drivers at the time of
the crash.  This symptom is usually a severe bug in a third party
driver.
Arguments:
Arg1: 0000000000000000, The address of the APC found pending during exit.
Arg2: 00000000ffff0000, The thread's APC disable count
Arg3: 0000000000000002, The current IRQL
Arg4: 0000000000000000

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:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME:  MS-7B77

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1.D0

BIOS_DATE:  11/08/2019

BASEBOARD_MANUFACTURER:  Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT:  X470 GAMING M7 AC (MS-7B77)

BASEBOARD_VERSION:  1.0

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: ffff0000

BUGCHECK_P3: 2

BUGCHECK_P4: 0

BUGCHECK_STR:  0x20_NULLAPC_SAPC_NEGATIVE

CPU_COUNT: 10

CPU_MHZ: e74

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  node.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-15-2020 21:56:08.0701

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff805823cafd4 to fffff80581dc14e0

STACK_TEXT: 
ffffc10a`16aed918 fffff805`823cafd4 : 00000000`00000020 00000000`00000000 00000000`ffff0000 00000000`00000002 : nt!KeBugCheckEx
ffffc10a`16aed920 fffff805`8225e54f : ffffd707`23cb5688 00000000`00000000 00000000`01bef000 00000000`00000000 : nt!KeRundownApcQueues+0x16c778
ffffc10a`16aed960 fffff805`82252113 : 00000000`00000000 00000000`00000000 00000000`01bef000 ffffd707`259a7e60 : nt!PspExitThread+0x487
ffffc10a`16aeda70 fffff805`8225209a : 00000000`00000000 00000000`00000000 ffffd707`23cb5080 00000000`01bef000 : nt!PspTerminateThreadByPointer+0x53
ffffc10a`16aedab0 fffff805`81dd2d18 : 00000000`00000000 ffffd707`23cb5080 ffffc10a`16aedb80 ffffd707`259a7e60 : nt!NtTerminateThread+0x4a
ffffc10a`16aedb00 00000000`77001cbc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`01c3f298 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77001cbc


THREAD_SHA1_HASH_MOD_FUNC:  ba582d62364b9bb7c2b0d39f42c792f3318d1a2e

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5f374101819caef6b1171d8dee89bc0f406bd11b

THREAD_SHA1_HASH_MOD:  ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_IP:
nt!KeRundownApcQueues+16c778
fffff805`823cafd4 cc              int     3

FAULT_INSTR_CODE:  8b48cccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KeRundownApcQueues+16c778

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f6eba0

IMAGE_VERSION:  10.0.18362.592

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  16c778

FAILURE_BUCKET_ID:  0x20_NULLAPC_SAPC_NEGATIVE_nt!KeRundownApcQueues

BUCKET_ID:  0x20_NULLAPC_SAPC_NEGATIVE_nt!KeRundownApcQueues

PRIMARY_PROBLEM_CLASS:  0x20_NULLAPC_SAPC_NEGATIVE_nt!KeRundownApcQueues

TARGET_TIME:  2020-01-15T18:02:48.000Z

OSBUILD:  18362

OSSERVICEPACK:  592

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:  1972-08-22 03:24:00

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  406f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x20_nullapc_sapc_negative_nt!kerundownapcqueues

FAILURE_ID_HASH:  {c81e91b7-515b-84c3-729e-05a7dac4c9a0}

Followup:     MachineOwner
---------
Tüm MSI yazılımları(Afterburner dahil), SteelSeries yazılımlarını kaldır.

Komut satırını(CMD) yönetici olarak başlatın "sfc /scannow" yazın işlemi başlatın, işlem bitince bilgisayarı yeniden başlatın.

Ekran kartı sürücüsünü DDU ile bir kaç sürüm geriye çek.

Killer Network sürücüsünü güvenli mod'da kaldır ve bunu yükle.

Kod:
PFN_REFERENCE_COUNT (1c)
Arguments:
Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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

*** WARNING: Unable to verify timestamp for win32k.sys

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:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CPU_COUNT: 10

CPU_MHZ: e74

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x1C

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-12-2020 23:25:10.0966

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff8055c75f206 to fffff80559fc14c0

STACK_TEXT:
fffffb03`46099588 fffff805`5c75f206 : ffffd781`ca7ddd00 fffff780`00000008 225a303d`52f67401 496bc42c`cbd30035 : nt!KeBugCheck
fffffb03`46099590 fffff805`5c6a65b0 : 0000002d`65592a3c 00000000`00989680 00000000`00000240 ffffd781`ca936e58 : tcpip!TcpProcessExpiredTcbTimers+0xb7456
fffffb03`460996b0 fffff805`59e6ae95 : ffffc480`d7d42f80 ffffd781`c2ad2000 ffffd781`ca936f10 ffffc480`d7d40180 : tcpip!TcpPeriodicTimeoutHandler+0x3f0
fffffb03`460998f0 fffff805`59e6a4ef : 00000000`00000000 00000000`00000001 ffffc480`d7d51440 00001f80`00130200 : nt!KiExecuteAllDpcs+0x305
fffffb03`46099a30 fffff805`59fc5024 : ffffffff`00000000 ffffc480`d7d40180 ffffc480`d7d51440 ffffd781`cfe0d080 : nt!KiRetireDpcList+0x1ef
fffffb03`46099c60 00000000`00000000 : fffffb03`4609a000 fffffb03`46094000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84


THREAD_SHA1_HASH_MOD_FUNC:  c1bae798238224e5b7b9749345ae2eae22acd054

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  2f8f0b5005e5278e9b9c23be0a8fa00a51182e05

THREAD_SHA1_HASH_MOD:  557e04ce91fa5d0b4248b1ed8602597cab24b984

FOLLOWUP_IP:
tcpip!TcpProcessExpiredTcbTimers+b7456
fffff805`5c75f206 cc              int     3

FAULT_INSTR_CODE:  8b41cccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  tcpip!TcpProcessExpiredTcbTimers+b7456

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  56fa3e2f

IMAGE_VERSION:  10.0.18362.476

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  b7456

FAILURE_BUCKET_ID:  0x1C_tcpip!TcpProcessExpiredTcbTimers

BUCKET_ID:  0x1C_tcpip!TcpProcessExpiredTcbTimers

PRIMARY_PROBLEM_CLASS:  0x1C_tcpip!TcpProcessExpiredTcbTimers

TARGET_TIME:  2020-01-12T19:07:11.000Z

OSBUILD:  18362

OSSERVICEPACK:  535

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:  1980-01-11 18:53:20

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  65cf

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1c_tcpip!tcpprocessexpiredtcbtimers

FAILURE_ID_HASH:  {af93484a-3bed-e650-4960-666c8cb460bd}

Followup:     MachineOwner
---------
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8065683351e, Address of the instruction which caused the bugcheck
Arg3: ffffbc872379b250, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8065683351e

BUGCHECK_P3: ffffbc872379b250

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP:
nt!ExAllocateHeapPool+e1e
fffff806`5683351e 0b00            or      eax,dword ptr [rax]

CONTEXT:  ffffbc872379b250 -- (.cxr 0xffffbc872379b250)
rax=0000000000000000 rbx=00000000000011d0 rcx=ffffd50805a54000
rdx=0000000000000000 rsi=0000000000000000 rdi=ffffd507f3010000
rip=fffff8065683351e rsp=ffffbc872379bc40 rbp=ffffbc872379bd40
r8=ffffd507f3010280  r9=0000000000000000 r10=00000000ffffffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=00000000000011d0 r15=000000004b677844
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!ExAllocateHeapPool+0xe1e:
fffff806`5683351e 0b00            or      eax,dword ptr [rax] ds:002b:00000000`00000000=????????
Resetting default scope

BUGCHECK_STR:  0x3B_c0000005

CPU_COUNT: 10

CPU_MHZ: e74

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-12-2020 23:25:07.0138

ANALYSIS_VERSION: 10.0.18362.1 x86fre

MISALIGNED_IP:
nt!ExAllocateHeapPool+e1e
fffff806`5683351e 0b00            or      eax,dword ptr [rax]

LAST_CONTROL_TRANSFER:  from fffff80656b6f06d to fffff8065683351e

STACK_TEXT:
ffffbc87`2379bc40 fffff806`56b6f06d : ffffd508`00000200 00000000`00000000 00000000`00000000 00000000`000011d0 : nt!ExAllocateHeapPool+0xe1e
ffffbc87`2379bd80 fffff806`61c0c915 : ffffd507`fe81a520 ffffbc87`2379cb80 ffffbc87`2379c900 ffffa480`00000000 : nt!ExAllocatePoolWithTag+0x5d
ffffbc87`2379bdd0 fffff806`61d0b177 : 00000000`4b677844 fffff806`56b6f06d 00000000`00000002 00000000`00000000 : dxgkrnl!operator new+0x31
ffffbc87`2379be00 fffff806`61d0ad77 : ffffa480`1b4e7b30 ffffbc87`2379c900 ffffbc87`2379c900 ffffa480`1b4e7b30 : dxgkrnl!DXGCONTEXT::SubmitCommand+0x247
ffffbc87`2379c5d0 fffff806`61d0b54a : ffffbc87`00000000 ffffd507`ff4478e0 ffffa480`1cbf1ab0 00000041`91f7ed10 : dxgkrnl!DxgkSubmitCommandInternal+0x557
ffffbc87`2379cac0 fffff806`569d2d18 : ffffd507`fe954080 00000000`14a40000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgkSubmitCommand+0x5a
ffffbc87`2379cb00 00007ff9`206c5a44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000041`91f7ec48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`206c5a44


THREAD_SHA1_HASH_MOD_FUNC:  5f0a53e1f7607b117945f35e67c3ab589cfa254c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  ea99dda1cb372327fb23a88680db246ee7dd2357

THREAD_SHA1_HASH_MOD:  d2496a4d735498beebaffc618e88b4ad5ec02e8c

FOLLOWUP_IP:
dxgkrnl!operator new+31
fffff806`61c0c915 4883c428        add     rsp,28h

FAULT_INSTR_CODE:  28c48348

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgkrnl!operator new+31

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.449

STACK_COMMAND:  .cxr 0xffffbc872379b250 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

PRIMARY_PROBLEM_CLASS:  IP_MISALIGNED

TARGET_TIME:  2020-01-12T08:37:52.000Z

OSBUILD:  18362

OSSERVICEPACK:  535

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:  1980-01-11 18:53:20

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  6222

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:ip_misaligned

FAILURE_ID_HASH:  {201b0e5d-db2a-63d2-77be-8ce8ff234750}

Followup:     MachineOwner
---------
 
Son düzenleme:
SYSTEM_SERVICE_EXCEPTION: system_service_exception mavi ekran sıkıntısı

Diğer dump dosyası ise genelde (tcpip, Vpn, İnternet bağlantıları ve köprüleme ile alakalı) bunuda ethernet kartınızın driverlerini kaldırıp yeniden kurun. Varsa VPN profilleri veya programları vs silin. Farklı VPN programları ile deneyin. Büyük ihtimal sorununuz çözülücektir.
 
Çok teşekkür ederim ilgi ve alakanızdan dolayı dediklerinizi yaptım. Umarım herhangi bir problem olmaz artık ummadık yerde mavi ekrana düşüp beni kanser ediyordu :)
Teşekkür ederim


Merhaba,
Gene mavi ekran hatası aldım.
Minidump dosyasını ekledim yardımcı olabilir misiniz?
 
Son düzenleyen: Moderatör:
Memtest86 testi yapar mısın?
Kod:
KERNEL_APC_PENDING_DURING_EXIT (20)
The key data item is the thread's APC disable count.
If this is non-zero, then this is the source of the problem.
The APC disable count is decremented each time a driver calls
KeEnterCriticalRegion, FsRtlEnterFileSystem, or acquires a mutex.  The APC
disable count is incremented each time a driver calls KeLeaveCriticalRegion,
FsRtlExitFileSystem, or KeReleaseMutex.  Since these calls should always be in
pairs, this value should be zero when a thread exits.  A negative value
indicates that a driver has disabled APC calls without re-enabling them.  A
positive value indicates that the reverse is true.
If you ever see this error, be very suspicious of all drivers installed on the
machine -- especially unusual or non-standard drivers.  Third party file
system redirectors are especially suspicious since they do not generally
receive the heavy duty testing that NTFS, FAT, RDR, etc receive.
This current IRQL should also be 0.  If it is not, that a driver's
cancelation routine can cause this bugcheck by returning at an elevated
IRQL.  Always attempt to note what you were doing/closing at the
time of the crash, and note all of the installed drivers at the time of
the crash.  This symptom is usually a severe bug in a third party
driver.
Arguments:
Arg1: 0000000000000000, The address of the APC found pending during exit.
Arg2: 00000000ffff0000, The thread's APC disable count
Arg3: 0000000000000002, The current IRQL
Arg4: 0000000000000000

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:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME:  MS-7B77

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1.D0

BIOS_DATE:  11/08/2019

BASEBOARD_MANUFACTURER:  Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT:  X470 GAMING M7 AC (MS-7B77)

BASEBOARD_VERSION:  1.0

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: ffff0000

BUGCHECK_P3: 2

BUGCHECK_P4: 0

BUGCHECK_STR:  0x20_NULLAPC_SAPC_NEGATIVE

CPU_COUNT: 10

CPU_MHZ: e74

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  node.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-15-2020 21:56:08.0701

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff805823cafd4 to fffff80581dc14e0

STACK_TEXT: 
ffffc10a`16aed918 fffff805`823cafd4 : 00000000`00000020 00000000`00000000 00000000`ffff0000 00000000`00000002 : nt!KeBugCheckEx
ffffc10a`16aed920 fffff805`8225e54f : ffffd707`23cb5688 00000000`00000000 00000000`01bef000 00000000`00000000 : nt!KeRundownApcQueues+0x16c778
ffffc10a`16aed960 fffff805`82252113 : 00000000`00000000 00000000`00000000 00000000`01bef000 ffffd707`259a7e60 : nt!PspExitThread+0x487
ffffc10a`16aeda70 fffff805`8225209a : 00000000`00000000 00000000`00000000 ffffd707`23cb5080 00000000`01bef000 : nt!PspTerminateThreadByPointer+0x53
ffffc10a`16aedab0 fffff805`81dd2d18 : 00000000`00000000 ffffd707`23cb5080 ffffc10a`16aedb80 ffffd707`259a7e60 : nt!NtTerminateThread+0x4a
ffffc10a`16aedb00 00000000`77001cbc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`01c3f298 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77001cbc


THREAD_SHA1_HASH_MOD_FUNC:  ba582d62364b9bb7c2b0d39f42c792f3318d1a2e

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5f374101819caef6b1171d8dee89bc0f406bd11b

THREAD_SHA1_HASH_MOD:  ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_IP:
nt!KeRundownApcQueues+16c778
fffff805`823cafd4 cc              int     3

FAULT_INSTR_CODE:  8b48cccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KeRundownApcQueues+16c778

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f6eba0

IMAGE_VERSION:  10.0.18362.592

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  16c778

FAILURE_BUCKET_ID:  0x20_NULLAPC_SAPC_NEGATIVE_nt!KeRundownApcQueues

BUCKET_ID:  0x20_NULLAPC_SAPC_NEGATIVE_nt!KeRundownApcQueues

PRIMARY_PROBLEM_CLASS:  0x20_NULLAPC_SAPC_NEGATIVE_nt!KeRundownApcQueues

TARGET_TIME:  2020-01-15T18:02:48.000Z

OSBUILD:  18362

OSSERVICEPACK:  592

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:  1972-08-22 03:24:00

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  406f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x20_nullapc_sapc_negative_nt!kerundownapcqueues

FAILURE_ID_HASH:  {c81e91b7-515b-84c3-729e-05a7dac4c9a0}

Followup:     MachineOwner
---------
 
Çözüm
Pass 1 de 2 hata.
Pass 2 de 16 hata buldu.
Daha da devam ediyor test.
Ben bu sistemi kuralı 1 sene oldu 16 GB RAM vardı bu zamana kadar bir kere bile hata almadım ama aynı marka model RAM aldım taktım ve yaklaşık 1 ay sonra mavi ekran hataları başladı muhtemelen RAM'de problem var.
 

Dosya Ekleri

  • 15793770435912514597911434776518.jpg
    15793770435912514597911434776518.jpg
    1,7 MB · Görüntüleme: 52
Hemen test'e başlıyorum tek tek teşekkür ederim.
Tekrardan merhaba RAM'ler tek tek test edildi hiçbirinde hata çıkmadı.
 
Son düzenleyen: Moderatör:
Durum
Mesaj gönderimine kapalı.

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

Technopat Haberler

Geri
Yukarı