DRIVER_IRQL_NOT_LESS_OR_EQUAL mavi ekran

caner ceylan · 2 Mayıs 2020

Arkadaşlar selamlar konu başlıgımda da belirtmiş oldugum gibi mavi ekran sorunu alıyorum. Ve bu sorun genelde oyuna girince oluyor ama normal kullanımda da oluyor. Ben sürücülerden şüpheleniyorum. bana yardımcı olmanız dilegiyle mindump dosyalarımı bırakıyorum. Genelde açılmış konulara baktığımda minidump dosyaları isteniyor.

Yandex

Finds everything

yadi.sk

Sistem özellikleri: Intel Core i5 4210U 1.7 GHz 2.4 GHz Turbo Ekran kartı: Intel HD grapichs harici Ekran kartı: NVIDIA GeForce 840M

İşletim sistemi: Win10 64 Bit

24099 · 2 Mayıs 2020

Ya konuya bakıyorum. Bir tane adam akıllı çözüm yok maalesef.

Mavi ekranlar DMP dosyalarındaki şeylere göre çözülür. Benim şimdilik fırsatım olmadığından inceleyemiyorum.

Aşağıya etiketleyelim.

@MayCrasH @Murat5038 @claus

creative01 · 2 Mayıs 2020

caner ceylan dedi:
Performans kaybı yaşar mıyım oyunlarda?

Hayir yasamazsin hatta artis yasarsin.

Grafik Sürücüsü - GeForce Game Ready Sürücüsü | NVIDIA

fromhell1 · 2 Mayıs 2020

24099 dedi:
Ya konuya bakıyorum. Bir tane adam akıllı çözüm yok maalesef.

Mavi ekranlar DMP dosyalarındaki şeylere göre çözülür. Benim şimdilik fırsatım olmadığından inceleyemiyorum.

Aşağıya etiketleyelim.

@MayCrasH @Murat5038 @claus

Biliyorum fakat minidump okumayı bilmediğim için HDD sonuçları belki gösterir diye düşündüm.

Recep Baltaş · 2 Mayıs 2020

İlk olarak bir bellek testi yapar mısınız?

Memtest86 USB'den Çalışan RAM Test Programı

RAM'lerinizi test etmek için kullanabileceğiniz en kapsamlı yazılım Memtest86'dır. Aracı USB belleğe yazmak için: Bu video rehberde Memtest86 ile belleklerinizi nasıl test edeceğinizi öğrenebilirsiniz: Adım adım: Öncelikle yazılımı buradan indirin. UEFI desteği olmayan eski sistemler...

www.technopat.net

Cihazın BIOS'u güncel değilse güncelelyin.

Kod:

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000048, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8002674758f, address which referenced memory

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 0

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G25IS1E

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 0

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

Key : Analysis.System
Value: CreateObject

Key : WER.CorruptModuleList
Value: 1


ADDITIONAL_XML: 1

BUGCHECK_CODE: d1

BUGCHECK_P1: 48

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8002674758f

READ_ADDRESS: Unable to get size of nt!_MMPTE - probably bad symbols
0000000000000048

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
fffff800`105ee4f8 fffff800`0d1d32e9 : 00000000`0000000a 00000000`00000048 00000000`00000002 00000000`00000000 : 0xfffff800`0d1c14e0
fffff800`105ee500 00000000`0000000a : 00000000`00000048 00000000`00000002 00000000`00000000 fffff800`2674758f : 0xfffff800`0d1d32e9
fffff800`105ee508 00000000`00000048 : 00000000`00000002 00000000`00000000 fffff800`2674758f fffff800`0876d800 : 0xa
fffff800`105ee510 00000000`00000002 : 00000000`00000000 fffff800`2674758f fffff800`0876d800 408f4000`00000000 : 0x48
fffff800`105ee518 00000000`00000000 : fffff800`2674758f fffff800`0876d800 408f4000`00000000 00000000`00000000 : 0x2


SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_AV

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fc259191-ef0c-6215-476f-d32e5dcaf1b7}

Followup: MachineOwner
---------

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: 0000000000000002, Stack cookie instrumentation code detected a stack-based
buffer overrun.
Arg2: fffff805777e6d40, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff805777e6c98, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 0

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G25IS1E

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 0

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

Key : Analysis.System
Value: CreateObject

Key : WER.CorruptModuleList
Value: 1


ADDITIONAL_XML: 1

BUGCHECK_CODE: 139

BUGCHECK_P1: 2

BUGCHECK_P2: fffff805777e6d40

BUGCHECK_P3: fffff805777e6c98

BUGCHECK_P4: 0

TRAP_FRAME:  fffff805777e6d40 -- (.trap 0xfffff805777e6d40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000103 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8058cbb4de5 rsp=fffff805777e6ed8 rbp=ffff9c0a787ceebc
r8=0000000000000001 r9=0000000000000000 r10=fffff805742484f0
r11=0000000000000058 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po nc
fffff805`8cbb4de5 ?? ???
Resetting default scope

EXCEPTION_RECORD:  fffff805777e6c98 -- (.exr 0xfffff805777e6c98)
ExceptionAddress: fffff8058cbb4de5
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000002
Subcode: 0x2 FAST_FAIL_STACK_COOKIE_CHECK_FAILURE

CUSTOMER_CRASH_COUNT: 1

EXCEPTION_STR: 0xc0000409

STACK_TEXT:
fffff805`777e6ed8 fffff805`8cbb1a27 : 00000000`00000000 ffff9c0a`787ceebc 00000000`00000000 fffff805`00000000 : 0xfffff805`8cbb4de5
fffff805`777e6ee0 00000000`00000000 : ffff9c0a`787ceebc 00000000`00000000 fffff805`00000000 ffff9c0a`00000020 : 0xfffff805`8cbb1a27


STACK_COMMAND: .trap 0xfffff805777e6d40 ; kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x139

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {bec1bc00-1c8a-a417-55b2-9f8b67cbb1c5}

Followup: MachineOwner
---------

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

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 0

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-G25IS1E

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 0

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.CorruptModuleList
    Value: 1


ADDITIONAL_XML: 1

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8045e26326b

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: Unable to get size of nt!_MMPTE - probably bad symbols
 ffffffffffffffff

EXCEPTION_PARAMETER2:  ffffffffffffffff

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT: 
fffff189`76028448 fffff804`5e4a653e : 00000000`0000001e ffffffff`c0000005 fffff804`5e26326b 00000000`00000000 : 0xfffff804`5e3c14e0
fffff189`76028450 00000000`0000001e : ffffffff`c0000005 fffff804`5e26326b 00000000`00000000 ffffffff`ffffffff : 0xfffff804`5e4a653e
fffff189`76028458 ffffffff`c0000005 : fffff804`5e26326b 00000000`00000000 ffffffff`ffffffff ffff898e`410b6c70 : 0x1e
fffff189`76028460 fffff804`5e26326b : 00000000`00000000 ffffffff`ffffffff ffff898e`410b6c70 fffff804`5e4a651c : 0xffffffff`c0000005
fffff189`76028468 00000000`00000000 : ffffffff`ffffffff ffff898e`410b6c70 fffff804`5e4a651c fffff804`5e3ca312 : 0xfffff804`5e26326b


SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  CORRUPT_MODULELIST_0x1E_c0000005_R

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9fbb6b05-1d22-18a3-1c13-7401b750327b}

Followup:     MachineOwner


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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff8001ba23185, The address that the exception occurred at
Arg3: fffff8001bf91400, Parameter 0 of the exception
Arg4: fffff8001bafa9b0, Parameter 1 of the exception

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 0

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G25IS1E

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 0

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

Key : Analysis.System
Value: CreateObject

Key : WER.CorruptModuleList
Value: 1


ADDITIONAL_XML: 1

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc000001d

BUGCHECK_P2: fffff8001ba23185

BUGCHECK_P3: fffff8001bf91400

BUGCHECK_P4: fffff8001bafa9b0

EXCEPTION_PARAMETER1: fffff8001bf91400

EXCEPTION_PARAMETER2: fffff8001bafa9b0

CUSTOMER_CRASH_COUNT: 1

FAILED_INSTRUCTION_ADDRESS:
+0
fffff800`1ba23185 ?? ???

STACK_TEXT:
fffff800`203fc138 fffff800`1bca653e : 00000000`0000001e ffffffff`c000001d fffff800`1ba23185 fffff800`1bf91400 : 0xfffff800`1bbc14e0
fffff800`203fc140 00000000`0000001e : ffffffff`c000001d fffff800`1ba23185 fffff800`1bf91400 fffff800`1bafa9b0 : 0xfffff800`1bca653e
fffff800`203fc148 ffffffff`c000001d : fffff800`1ba23185 fffff800`1bf91400 fffff800`1bafa9b0 fffff800`1ba73c63 : 0x1e
fffff800`203fc150 fffff800`1ba23185 : fffff800`1bf91400 fffff800`1bafa9b0 fffff800`1ba73c63 fffff800`1bca651c : 0xffffffff`c000001d
fffff800`203fc158 fffff800`1bf91400 : fffff800`1bafa9b0 fffff800`1ba73c63 fffff800`1bca651c fffff800`1bbca312 : 0xfffff800`1ba23185
fffff800`203fc160 fffff800`1bafa9b0 : fffff800`1ba73c63 fffff800`1bca651c fffff800`1bbca312 fffff800`1bf11000 : 0xfffff800`1bf91400
fffff800`203fc168 fffff800`1ba73c63 : fffff800`1bca651c fffff800`1bbca312 fffff800`1bf11000 fffff800`1ba00000 : 0xfffff800`1bafa9b0
fffff800`203fc170 fffff800`1bca651c : fffff800`1bbca312 fffff800`1bf11000 fffff800`1ba00000 0005e548`00ab6000 : 0xfffff800`1ba73c63
fffff800`203fc178 fffff800`1bbca312 : fffff800`1bf11000 fffff800`1ba00000 0005e548`00ab6000 00000000`0010001f : 0xfffff800`1bca651c
fffff800`203fc180 fffff800`1bf11000 : fffff800`1ba00000 0005e548`00ab6000 00000000`0010001f fffff800`203fc770 : 0xfffff800`1bbca312
fffff800`203fc188 fffff800`1ba00000 : 0005e548`00ab6000 00000000`0010001f fffff800`203fc770 fffff800`1bac2fa5 : 0xfffff800`1bf11000
fffff800`203fc190 0005e548`00ab6000 : 00000000`0010001f fffff800`203fc770 fffff800`1bac2fa5 00000000`00000000 : 0xfffff800`1ba00000
fffff800`203fc198 00000000`0010001f : fffff800`203fc770 fffff800`1bac2fa5 00000000`00000000 00000000`00000000 : 0x0005e548`00ab6000
fffff800`203fc1a0 fffff800`203fc770 : fffff800`1bac2fa5 00000000`00000000 00000000`00000000 fffff800`203fc6f0 : 0x10001f
fffff800`203fc1a8 fffff800`1bac2fa5 : 00000000`00000000 00000000`00000000 fffff800`203fc6f0 00007fff`ffff0000 : 0xfffff800`203fc770
fffff800`203fc1b0 00000000`00000000 : 00000000`00000000 fffff800`203fc6f0 00007fff`ffff0000 00000000`00000000 : 0xfffff800`1bac2fa5


SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x1E_c000001d

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {1317f67f-e01f-874d-b4c9-a3a1ee68b035}

Followup: MachineOwner
---------

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffc008c49fb4b0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8032e8b1c84, address which referenced memory

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 3

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G25IS1E

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 27

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

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE: d1

BUGCHECK_P1: ffffc008c49fb4b0

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8032e8b1c84

READ_ADDRESS: fffff8032d9733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8032d82a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff8032d82a3c8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffc008c49fb4b0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME:  fffff803301e7660 -- (.trap 0xfffff803301e7660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe004624fda20 rbx=0000000000000000 rcx=ffffe004624fda90
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8032e8b1c84 rsp=fffff803301e77f0 rbp=fffff803301e7889
r8=0000000000000010 r9=0000000000000010 r10=fffff8032d427de0
r11=ffffa97b86400000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
ACPI!ACPIInterruptDispatchEventDpc+0xc4:
fffff803`2e8b1c84 8a040a mov al,byte ptr [rdx+rcx] ds:ffffe004`624fda90=00
Resetting default scope

STACK_TEXT:
fffff803`301e7518 fffff803`2d5d32e9 : 00000000`0000000a ffffc008`c49fb4b0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff803`301e7520 fffff803`2d5cf62b : 00000000`0a600a80 fffff803`301e76e0 ffffe004`62c22001 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff803`301e7660 fffff803`2e8b1c84 : fffff803`2841e180 00000000`00000000 00000000`00000010 ffffe004`62306040 : nt!KiPageFault+0x46b
fffff803`301e77f0 fffff803`2d46ae95 : fffff803`28420f80 fffff803`2e911ec0 fffff803`2841e180 00000000`00000002 : ACPI!ACPIInterruptDispatchEventDpc+0xc4
fffff803`301e78f0 fffff803`2d46a4ef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x305
fffff803`301e7a30 fffff803`2d5c5024 : 00000000`00000000 fffff803`2841e180 fffff803`2d991400 ffffe004`7138f080 : nt!KiRetireDpcList+0x1ef
fffff803`301e7c60 00000000`00000000 : fffff803`301e8000 fffff803`301e2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84


SYMBOL_NAME: ACPI!ACPIInterruptDispatchEventDpc+c4

MODULE_NAME: ACPI

IMAGE_NAME:  ACPI.sys

IMAGE_VERSION: 10.0.18362.329

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: c4

FAILURE_BUCKET_ID: AV_ACPI!ACPIInterruptDispatchEventDpc

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {96b254a4-0514-468b-168d-08c425f84f92}

Followup: MachineOwner
---------

Murat5038 · 2 Mayıs 2020

https://ftp.hp.com/pub/softpaq/sp92501-93000/sp92961.exe

BIOS güncel değil güncelleyin.

Ekran kartı, sistem dosyaları, ses sürün sorunlu. Bu yüzden en iyisi 1909 build ile temiz bir kurulum yapıp güncel sürücülerinizi kurun.

caner ceylan · 8 Mayıs 2020

Recep Baltaş dedi:

İlk olarak bir bellek testi yapar mısınız?

Memtest86 USB'den Çalışan RAM Test Programı

RAM'lerinizi test etmek için kullanabileceğiniz en kapsamlı yazılım Memtest86'dır. Aracı USB belleğe yazmak için: Bu video rehberde Memtest86 ile belleklerinizi nasıl test edeceğinizi öğrenebilirsiniz: Adım adım: Öncelikle yazılımı buradan indirin. UEFI desteği olmayan eski sistemler...

www.technopat.net

Cihazın BIOS'u güncel değilse güncelelyin.

Kod:

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000048, memory referenced.
Arg2: 0000000000000002, IRQL.
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg4: fffff8002674758f, address which referenced memory.

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

KEY_VALUES_STRING: 1.

Key : Analysis.CPU.Sec.
Value: 0.

Key : Analysis.DebugAnalysisProvider.CPP.
Value: Create: 8007007e on DESKTOP-G25IS1E.

Key : Analysis.DebugData.
Value: CreateObject.

Key : Analysis.DebugModel.
Value: CreateObject.

Key : Analysis.Elapsed.Sec.
Value: 0.

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

Key : Analysis.System.
Value: CreateObject.

Key : WER.CorruptModuleList.
Value: 1.

ADDITIONAL_XML: 1.

BUGCHECK_CODE: d1.

BUGCHECK_P1: 48.

BUGCHECK_P2: 2.

BUGCHECK_P3: 0.

BUGCHECK_P4: fffff8002674758f.

READ_ADDRESS: Unable to get size of nt!_MMPTE - probably bad symbols.
0000000000000048.

CUSTOMER_CRASH_COUNT: 1.

STACK_TEXT:
fffff800`105ee4f8 fffff800`0d1d32e9 : 00000000`0000000a 00000000`00000048 00000000`00000002 00000000`00000000 : 0xfffff800`0d1c14e0.
fffff800`105ee500 00000000`0000000a : 00000000`00000048 00000000`00000002 00000000`00000000 fffff800`2674758f : 0xfffff800`0d1d32e9.
fffff800`105ee508 00000000`00000048 : 00000000`00000002 00000000`00000000 fffff800`2674758f fffff800`0876d800 : 0xa.
fffff800`105ee510 00000000`00000002 : 00000000`00000000 fffff800`2674758f fffff800`0876d800 408f4000`00000000 : 0x48.
fffff800`105ee518 00000000`00000000 : fffff800`2674758f fffff800`0876d800 408f4000`00000000 00000000`00000000 : 0x2.

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE.

MODULE_NAME: Unknown_Module.

IMAGE_NAME: Unknown_Image.

STACK_COMMAND: .thread ; .cxr ; kb.

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_AV.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {fc259191-ef0c-6215-476f-d32e5dcaf1b7}

Followup: MachineOwner.
---------

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: 0000000000000002, Stack cookie instrumentation code detected a stack-based.
buffer overrun.
Arg2: fffff805777e6d40, Address of the trap frame for the exception that caused the bugcheck.
Arg3: fffff805777e6c98, Address of the exception record for the exception that caused the bugcheck.
Arg4: 0000000000000000, Reserved.

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

KEY_VALUES_STRING: 1.

Key : Analysis.CPU.Sec.
Value: 0.

Key : Analysis.DebugAnalysisProvider.CPP.
Value: Create: 8007007e on DESKTOP-G25IS1E.

Key : Analysis.DebugData.
Value: CreateObject.

Key : Analysis.DebugModel.
Value: CreateObject.

Key : Analysis.Elapsed.Sec.
Value: 0.

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

Key : Analysis.System.
Value: CreateObject.

Key : WER.CorruptModuleList.
Value: 1.

ADDITIONAL_XML: 1.

BUGCHECK_CODE: 139.

BUGCHECK_P1: 2.

BUGCHECK_P2: fffff805777e6d40.

BUGCHECK_P3: fffff805777e6c98.

BUGCHECK_P4: 0.

TRAP_FRAME: fffff805777e6d40 -- (.trap 0xfffff805777e6d40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000103 rbx=0000000000000000 rcx=0000000000000002.
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000.
rip=fffff8058cbb4de5 rsp=fffff805777e6ed8 rbp=ffff9c0a787ceebc.
r8=0000000000000001 r9=0000000000000000 r10=fffff805742484f0.
r11=0000000000000058 r12=0000000000000000 r13=0000000000000000.
r14=0000000000000000 r15=0000000000000000.
iopl=0 nv up ei ng nz ac po nc.
fffff805`8cbb4de5 ?? ???
Resetting default scope.

EXCEPTION_RECORD: fffff805777e6c98 -- (.exr 0xfffff805777e6c98)
ExceptionAddress: fffff8058cbb4de5.
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001.
NumberParameters: 1.
Parameter[0]: 0000000000000002.
Subcode: 0x2 FAST_FAIL_STACK_COOKIE_CHECK_FAILURE.

CUSTOMER_CRASH_COUNT: 1.

EXCEPTION_STR: 0xc0000409.

STACK_TEXT:
fffff805`777e6ed8 fffff805`8cbb1a27 : 00000000`00000000 ffff9c0a`787ceebc 00000000`00000000 fffff805`00000000 : 0xfffff805`8cbb4de5.
fffff805`777e6ee0 00000000`00000000 : ffff9c0a`787ceebc 00000000`00000000 fffff805`00000000 ffff9c0a`00000020 : 0xfffff805`8cbb1a27.

STACK_COMMAND: .trap 0xfffff805777e6d40 ; kb.

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE.

MODULE_NAME: Unknown_Module.

IMAGE_NAME: Unknown_Image.

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x139.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {bec1bc00-1c8a-a417-55b2-9f8b67cbb1c5}

Followup: MachineOwner.
---------

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

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

KEY_VALUES_STRING: 1.

Key : Analysis.CPU.Sec.
Value: 0.

Key : Analysis.DebugAnalysisProvider.CPP.
Value: Create: 8007007e on DESKTOP-G25IS1E.

Key : Analysis.DebugData.
Value: CreateObject.

Key : Analysis.DebugModel.
Value: CreateObject.

Key : Analysis.Elapsed.Sec.
Value: 0.

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

Key : Analysis.System.
Value: CreateObject.

Key : WER.CorruptModuleList.
Value: 1.

ADDITIONAL_XML: 1.

BUGCHECK_CODE: 1e.

BUGCHECK_P1: ffffffffc0000005.

BUGCHECK_P2: fffff8045e26326b.

BUGCHECK_P3: 0.

BUGCHECK_P4: ffffffffffffffff.

READ_ADDRESS: Unable to get size of nt!_MMPTE - probably bad symbols.
ffffffffffffffff.

EXCEPTION_PARAMETER2: ffffffffffffffff.

CUSTOMER_CRASH_COUNT: 1.

STACK_TEXT:
fffff189`76028448 fffff804`5e4a653e : 00000000`0000001e ffffffff`c0000005 fffff804`5e26326b 00000000`00000000 : 0xfffff804`5e3c14e0.
fffff189`76028450 00000000`0000001e : ffffffff`c0000005 fffff804`5e26326b 00000000`00000000 ffffffff`ffffffff : 0xfffff804`5e4a653e.
fffff189`76028458 ffffffff`c0000005 : fffff804`5e26326b 00000000`00000000 ffffffff`ffffffff ffff898e`410b6c70 : 0x1e.
fffff189`76028460 fffff804`5e26326b : 00000000`00000000 ffffffff`ffffffff ffff898e`410b6c70 fffff804`5e4a651c : 0xffffffff`c0000005.
fffff189`76028468 00000000`00000000 : ffffffff`ffffffff ffff898e`410b6c70 fffff804`5e4a651c fffff804`5e3ca312 : 0xfffff804`5e26326b.

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE.

MODULE_NAME: Unknown_Module.

IMAGE_NAME: Unknown_Image.

STACK_COMMAND: .thread ; .cxr ; kb.

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x1E_c0000005_R.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {9fbb6b05-1d22-18a3-1c13-7401b750327b}

Followup: MachineOwner.

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: ffffffffc000001d, The exception code that was not handled.
Arg2: fffff8001ba23185, The address that the exception occurred at.
Arg3: fffff8001bf91400, Parameter 0 of the exception.
Arg4: fffff8001bafa9b0, Parameter 1 of the exception.

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

KEY_VALUES_STRING: 1.

Key : Analysis.CPU.Sec.
Value: 0.

Key : Analysis.DebugAnalysisProvider.CPP.
Value: Create: 8007007e on DESKTOP-G25IS1E.

Key : Analysis.DebugData.
Value: CreateObject.

Key : Analysis.DebugModel.
Value: CreateObject.

Key : Analysis.Elapsed.Sec.
Value: 0.

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

Key : Analysis.System.
Value: CreateObject.

Key : WER.CorruptModuleList.
Value: 1.

ADDITIONAL_XML: 1.

BUGCHECK_CODE: 1e.

BUGCHECK_P1: ffffffffc000001d.

BUGCHECK_P2: fffff8001ba23185.

BUGCHECK_P3: fffff8001bf91400.

BUGCHECK_P4: fffff8001bafa9b0.

EXCEPTION_PARAMETER1: fffff8001bf91400.

EXCEPTION_PARAMETER2: fffff8001bafa9b0.

CUSTOMER_CRASH_COUNT: 1.

FAILED_INSTRUCTION_ADDRESS:
+0.
fffff800`1ba23185 ?? ???

STACK_TEXT:
fffff800`203fc138 fffff800`1bca653e : 00000000`0000001e ffffffff`c000001d fffff800`1ba23185 fffff800`1bf91400 : 0xfffff800`1bbc14e0.
fffff800`203fc140 00000000`0000001e : ffffffff`c000001d fffff800`1ba23185 fffff800`1bf91400 fffff800`1bafa9b0 : 0xfffff800`1bca653e.
fffff800`203fc148 ffffffff`c000001d : fffff800`1ba23185 fffff800`1bf91400 fffff800`1bafa9b0 fffff800`1ba73c63 : 0x1e.
fffff800`203fc150 fffff800`1ba23185 : fffff800`1bf91400 fffff800`1bafa9b0 fffff800`1ba73c63 fffff800`1bca651c : 0xffffffff`c000001d.
fffff800`203fc158 fffff800`1bf91400 : fffff800`1bafa9b0 fffff800`1ba73c63 fffff800`1bca651c fffff800`1bbca312 : 0xfffff800`1ba23185.
fffff800`203fc160 fffff800`1bafa9b0 : fffff800`1ba73c63 fffff800`1bca651c fffff800`1bbca312 fffff800`1bf11000 : 0xfffff800`1bf91400.
fffff800`203fc168 fffff800`1ba73c63 : fffff800`1bca651c fffff800`1bbca312 fffff800`1bf11000 fffff800`1ba00000 : 0xfffff800`1bafa9b0.
fffff800`203fc170 fffff800`1bca651c : fffff800`1bbca312 fffff800`1bf11000 fffff800`1ba00000 0005e548`00ab6000 : 0xfffff800`1ba73c63.
fffff800`203fc178 fffff800`1bbca312 : fffff800`1bf11000 fffff800`1ba00000 0005e548`00ab6000 00000000`0010001f : 0xfffff800`1bca651c.
fffff800`203fc180 fffff800`1bf11000 : fffff800`1ba00000 0005e548`00ab6000 00000000`0010001f fffff800`203fc770 : 0xfffff800`1bbca312.
fffff800`203fc188 fffff800`1ba00000 : 0005e548`00ab6000 00000000`0010001f fffff800`203fc770 fffff800`1bac2fa5 : 0xfffff800`1bf11000.
fffff800`203fc190 0005e548`00ab6000 : 00000000`0010001f fffff800`203fc770 fffff800`1bac2fa5 00000000`00000000 : 0xfffff800`1ba00000.
fffff800`203fc198 00000000`0010001f : fffff800`203fc770 fffff800`1bac2fa5 00000000`00000000 00000000`00000000 : 0x0005e548`00ab6000.
fffff800`203fc1a0 fffff800`203fc770 : fffff800`1bac2fa5 00000000`00000000 00000000`00000000 fffff800`203fc6f0 : 0x10001f.
fffff800`203fc1a8 fffff800`1bac2fa5 : 00000000`00000000 00000000`00000000 fffff800`203fc6f0 00007fff`ffff0000 : 0xfffff800`203fc770.
fffff800`203fc1b0 00000000`00000000 : 00000000`00000000 fffff800`203fc6f0 00007fff`ffff0000 00000000`00000000 : 0xfffff800`1bac2fa5.

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE.

MODULE_NAME: Unknown_Module.

IMAGE_NAME: Unknown_Image.

STACK_COMMAND: .thread ; .cxr ; kb.

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x1E_c000001d.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {1317f67f-e01f-874d-b4c9-a3a1ee68b035}

Followup: MachineOwner.
---------

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffc008c49fb4b0, memory referenced.
Arg2: 0000000000000002, IRQL.
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg4: fffff8032e8b1c84, address which referenced memory.

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

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

KEY_VALUES_STRING: 1.

Key : Analysis.CPU.Sec.
Value: 3.

Key : Analysis.DebugAnalysisProvider.CPP.
Value: Create: 8007007e on DESKTOP-G25IS1E.

Key : Analysis.DebugData.
Value: CreateObject.

Key : Analysis.DebugModel.
Value: CreateObject.

Key : Analysis.Elapsed.Sec.
Value: 27.

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

Key : Analysis.System.
Value: CreateObject.

ADDITIONAL_XML: 1.

BUGCHECK_CODE: d1.

BUGCHECK_P1: ffffc008c49fb4b0.

BUGCHECK_P2: 2.

BUGCHECK_P3: 0.

BUGCHECK_P4: fffff8032e8b1c84.

READ_ADDRESS: fffff8032d9733b8: Unable to get MiVisibleState.
Unable to get NonPagedPoolStart.
Unable to get NonPagedPoolEnd.
Unable to get PagedPoolStart.
Unable to get PagedPoolEnd.
fffff8032d82a3c8: Unable to get Flags value from nt!KdVersionBlock.
fffff8032d82a3c8: Unable to get Flags value from nt!KdVersionBlock.
unable to get nt!MmSpecialPagesInUse.
ffffc008c49fb4b0.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1.

CUSTOMER_CRASH_COUNT: 1.

PROCESS_NAME: System.

TRAP_FRAME: fffff803301e7660 -- (.trap 0xfffff803301e7660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe004624fda20 rbx=0000000000000000 rcx=ffffe004624fda90.
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000.
rip=fffff8032e8b1c84 rsp=fffff803301e77f0 rbp=fffff803301e7889.
r8=0000000000000010 r9=0000000000000010 r10=fffff8032d427de0.
r11=ffffa97b86400000 r12=0000000000000000 r13=0000000000000000.
r14=0000000000000000 r15=0000000000000000.
iopl=0 nv up ei pl nz na pe nc.
ACPI!ACPIInterruptDispatchEventDpc+0xc4:
fffff803`2e8b1c84 8a040a mov al,byte ptr [rdx+rcx] ds:ffffe004`624fda90=00.
Resetting default scope.

STACK_TEXT:
fffff803`301e7518 fffff803`2d5d32e9 : 00000000`0000000a ffffc008`c49fb4b0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx.
fffff803`301e7520 fffff803`2d5cf62b : 00000000`0a600a80 fffff803`301e76e0 ffffe004`62c22001 00000000`00000000 : nt!KiBugCheckDispatch+0x69.
fffff803`301e7660 fffff803`2e8b1c84 : fffff803`2841e180 00000000`00000000 00000000`00000010 ffffe004`62306040 : nt!KiPageFault+0x46b.
fffff803`301e77f0 fffff803`2d46ae95 : fffff803`28420f80 fffff803`2e911ec0 fffff803`2841e180 00000000`00000002 : ACPI!ACPIInterruptDispatchEventDpc+0xc4.
fffff803`301e78f0 fffff803`2d46a4ef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x305.
fffff803`301e7a30 fffff803`2d5c5024 : 00000000`00000000 fffff803`2841e180 fffff803`2d991400 ffffe004`7138f080 : nt!KiRetireDpcList+0x1ef.
fffff803`301e7c60 00000000`00000000 : fffff803`301e8000 fffff803`301e2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84.

SYMBOL_NAME: ACPI!ACPIInterruptDispatchEventDpc+c4.

MODULE_NAME: ACPI.

IMAGE_NAME: ACPI.sys.

IMAGE_VERSION: 10.0.18362.329.

STACK_COMMAND: .thread ; .cxr ; kb.

BUCKET_ID_FUNC_OFFSET: c4.

FAILURE_BUCKET_ID: AV_ACPI!ACPIInterruptDispatchEventDpc.

OS_VERSION: 10.0.18362.1.

BUILDLAB_STR: 19h1_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {96b254a4-0514-468b-168d-08c425f84f92}

Followup: MachineOwner.
---------

Recep abi bellek testim temiz çıktı Memtest'le test yaptım bir sorun yok alttaki arkadaşın vermiş oldugu linkten programı indirdim BIOS güncelledim umarım vermeye devam etmez yardımlarınız için çok sagolun.

Murat5038 · 8 Mayıs 2020

caner ceylan dedi:
BIOS güncelledim umarım vermeye devam etmez.

Sadece BIOS'u yazmadık orada diğerlerini de yap yapmadıysan.

caner ceylan · 8 Mayıs 2020

Murat5038 dedi:
Sadece BIOS'u yazmadık orada diğerlerini de yap yapmadıysan.

Dostum daha once 8.1 kullanıyordum yine aynı hatayı alıyorum güncel Windows'u kursam degişme olacak mı olmayacaksa bence ugrasmama değmez diye dusunuyorum yardımın için teşekkür ediyorum.
@Murat5038 hocam yardim edin lütfen kafayı yemek üzereyim.

DRIVER_IRQL_NOT_LESS_OR_EQUAL mavi ekran

Ayrıntılı düzenleme

caner ceylan

Hectopat

Yandex

24099

Petapat

creative01

Hectopat

fromhell1

Gigapat

Recep Baltaş

Technopat

Memtest86 USB'den Çalışan RAM Test Programı

Murat5038

Yottapat!

caner ceylan

Hectopat

Memtest86 USB'den Çalışan RAM Test Programı

Murat5038

Yottapat!

caner ceylan

Hectopat

Benzer konular