Windows 10 mavi ekran hatası

Yardım edermisiniz

işlemcim r5 3500X


minidump dosyaları linkte
*******************************************************************************
* *
* 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: 00007ff99368be44, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff68158310b80, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3281

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on KAYSERI

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 14430

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

Key : Analysis.System
Value: CreateObject

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 1

BUGCHECK_P1: 7ff99368be44

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: fffff68158310b80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Doping Hafýza.exe

STACK_TEXT:
fffff681`583109b8 fffff806`39005e69 : 00000000`00000001 00007ff9`9368be44 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff681`583109c0 fffff806`39005d33 : ffffb006`bdfd8080 ffffb006`c1937080 fffff681`58310b18 ffffffff`fe1dd280 : nt!KiBugCheckDispatch+0x69
fffff681`58310b00 00007ff9`9368be44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000075`880ff568 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`9368be44


SYMBOL_NAME: nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.508

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1fe

FAILURE_BUCKET_ID: 0x1_SysCallNum_4_nt!KiSystemServiceExitPico

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {52cd694c-15ec-48c3-924a-3539560711db}

Followup: MachineOwner
---------
hocam driverlerinizi güncelleyin ve memtest64 testi yapın zamanınız oluncada memtest86 ile test yapın
 
*******************************************************************************
* *
* 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: 00007ff99368be44, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff68158310b80, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3281

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on KAYSERI

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 14430

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

Key : Analysis.System
Value: CreateObject

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 1

BUGCHECK_P1: 7ff99368be44

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: fffff68158310b80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Doping Hafýza.exe

STACK_TEXT:
fffff681`583109b8 fffff806`39005e69 : 00000000`00000001 00007ff9`9368be44 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff681`583109c0 fffff806`39005d33 : ffffb006`bdfd8080 ffffb006`c1937080 fffff681`58310b18 ffffffff`fe1dd280 : nt!KiBugCheckDispatch+0x69
fffff681`58310b00 00007ff9`9368be44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000075`880ff568 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`9368be44


SYMBOL_NAME: nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.508

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1fe

FAILURE_BUCKET_ID: 0x1_SysCallNum_4_nt!KiSystemServiceExitPico

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {52cd694c-15ec-48c3-924a-3539560711db}

Followup: MachineOwner
---------
hocam driverlerinizi güncelleyin ve memtest64 testi yapın zamanınız oluncada memtest86 ile test yapın
*******************************************************************************
* *
* 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: 00007ff99368be44, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff68158310b80, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3281

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on KAYSERI

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 14430

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

Key : Analysis.System
Value: CreateObject

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 1

BUGCHECK_P1: 7ff99368be44

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: fffff68158310b80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Doping Hafýza.exe

STACK_TEXT:
fffff681`583109b8 fffff806`39005e69 : 00000000`00000001 00007ff9`9368be44 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff681`583109c0 fffff806`39005d33 : ffffb006`bdfd8080 ffffb006`c1937080 fffff681`58310b18 ffffffff`fe1dd280 : nt!KiBugCheckDispatch+0x69
fffff681`58310b00 00007ff9`9368be44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000075`880ff568 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`9368be44


SYMBOL_NAME: nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.508

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1fe

FAILURE_BUCKET_ID: 0x1_SysCallNum_4_nt!KiSystemServiceExitPico

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {52cd694c-15ec-48c3-924a-3539560711db}

Followup: MachineOwner
---------
hocam driverlerinizi güncelleyin ve memtest64 testi yapın zamanınız oluncada memtest86 ile test yapın
memtest ne testi oluyor
 
*******************************************************************************
* *
* 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: 00007ff99368be44, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff68158310b80, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3281

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on KAYSERI

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 14430

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

Key : Analysis.System
Value: CreateObject

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 1

BUGCHECK_P1: 7ff99368be44

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: fffff68158310b80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Doping Hafýza.exe

STACK_TEXT:
fffff681`583109b8 fffff806`39005e69 : 00000000`00000001 00007ff9`9368be44 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff681`583109c0 fffff806`39005d33 : ffffb006`bdfd8080 ffffb006`c1937080 fffff681`58310b18 ffffffff`fe1dd280 : nt!KiBugCheckDispatch+0x69
fffff681`58310b00 00007ff9`9368be44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000075`880ff568 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`9368be44


SYMBOL_NAME: nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.508

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1fe

FAILURE_BUCKET_ID: 0x1_SysCallNum_4_nt!KiSystemServiceExitPico

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {52cd694c-15ec-48c3-924a-3539560711db}

Followup: MachineOwner
---------
hocam driverlerinizi güncelleyin ve memtest64 testi yapın zamanınız oluncada memtest86 ile test yapın
ramler sıkıntılıysa ne yapmam gerekiyor itopyadan aldımda
 
bugün nedense acayip şekilde çok mavi ekran yiyen oldu
 
*******************************************************************************
* *
* 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: 00007ff99368be44, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff68158310b80, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3281

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on KAYSERI

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 14430

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

Key : Analysis.System
Value: CreateObject

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 1

BUGCHECK_P1: 7ff99368be44

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: fffff68158310b80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Doping Hafýza.exe

STACK_TEXT:
fffff681`583109b8 fffff806`39005e69 : 00000000`00000001 00007ff9`9368be44 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff681`583109c0 fffff806`39005d33 : ffffb006`bdfd8080 ffffb006`c1937080 fffff681`58310b18 ffffffff`fe1dd280 : nt!KiBugCheckDispatch+0x69
fffff681`58310b00 00007ff9`9368be44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000075`880ff568 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`9368be44


SYMBOL_NAME: nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.508

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1fe

FAILURE_BUCKET_ID: 0x1_SysCallNum_4_nt!KiSystemServiceExitPico

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {52cd694c-15ec-48c3-924a-3539560711db}

Followup: MachineOwner
---------
hocam driverlerinizi güncelleyin ve memtest64 testi yapın zamanınız oluncada memtest86 ile test yapın
Kaç saat sürüyor testler
 
bugün nedense acayip şekilde çok mavi ekran yiyen oldu
1600773947846.png

begin testemi basacağım
 
benim dersim başlayacak 1 saate yapmayım şimdi sonra yaparım
hayır bu kısa sürüyor memtest 86 uzun sürüyor
Mesajlar otomatik olarak birleştirildi:

bu test memtest64 testi
 
Yeni mesajlar Yeni Konu Aç  

   

SON KONULAR

Forum istatistikleri

Konular
1,193,993
Mesajlar
10,768,428
Üyeler
189,530
Son üye
HayranBaba1
Geri
Top