Çözüldü DRIVER_CORRUPTED_EXPOOL hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
Çözüm
Merhaba,

DRIVER_CORRUPTED_EXPOOL (c5) ve vgk.sys

Aslında aşağıdaki konuyla neredeyse birebir diyebiliriz.


Yani genelde güncel olmayan Vanguard sürücüsünü kullandığınızdan kaynaklanır.

Bu konudaki çözümü uyguladığınızda bir problem kalmayacaktır yüksek ihtimalle.

Tabii belli başlı dönemlerde Vanguard'da veya başka anti-hilelerde, oyun sürücülerinde bu tarz problemler yaşanıyor ve sadece size özel olmayabiliyor. Güncelleme beklemek gerekebiliyor. Riot güncellemeyi yayınlayınca çözülüyor, bu yeni güncellemelerden birinde olan soruna mı denk geldiniz orasını bilmiyorum. :)


Döküm:
Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: ffffae0eeff8e743, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80119e9a08e, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1328

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3640

    Key  : Analysis.Init.CPU.mSec
    Value: 140

    Key  : Analysis.Init.Elapsed.mSec
    Value: 59811

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xc5

    Key  : Bugcheck.Code.Register
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  092622-7781-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

BUGCHECK_CODE:  c5

BUGCHECK_P1: ffffae0eeff8e743

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80119e9a08e

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  VALORANT-Win64

TRAP_FRAME:  ffffad0bcfb09540 -- (.trap 0xffffad0bcfb09540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffae0ee5e00000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80119e9a08e rsp=ffffad0bcfb096d0 rbp=0000000000000000
 r8=ffffc40144c21cb0  r9=0000000000000001 r10=ffffc4014fc6d668
r11=ffffad0bcfb09758 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!ExFreePoolWithTag+0x7e:
fffff801`19e9a08e f647f308        test    byte ptr [rdi-0Dh],8 ds:ffffffff`fffffff3=??
Resetting default scope

STACK_TEXT:
ffffad0b`cfb093f8 fffff801`19833fa9     : 00000000`0000000a ffffae0e`eff8e743 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffad0b`cfb09400 fffff801`1982fee8     : fffff801`29c00000 ffffc401`44c21cb0 00000000`00040286 00000000`00000076 : nt!KiBugCheckDispatch+0x69
ffffad0b`cfb09540 fffff801`19e9a08e     : 01000000`00100000 00000000`00000004 00000000`00000000 00000000`00040246 : nt!KiPageFault+0x468
ffffad0b`cfb096d0 fffff801`2a40f3ef     : fffff801`00000000 fffff801`29c7ac40 00000000`00000000 00000000`00000000 : nt!ExFreePoolWithTag+0x7e
ffffad0b`cfb09760 fffff801`00000000     : fffff801`29c7ac40 00000000`00000000 00000000`00000000 00000000`00000001 : vgk+0x80f3ef
ffffad0b`cfb09768 fffff801`29c7ac40     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000008 : 0xfffff801`00000000
ffffad0b`cfb09770 00000000`00000000     : 00000000`00000000 00000000`00000001 00000000`00000008 00000000`00000001 : vgk+0x7ac40


SYMBOL_NAME:  vgk+80f3ef

MODULE_NAME: vgk

IMAGE_NAME:  vgk.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  80f3ef

FAILURE_BUCKET_ID:  0xC5_2_vgk!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f440937e-e808-2f2e-10ad-7db228ddf2cc}

Followup:     MachineOwner
---------
Merhaba,

DRIVER_CORRUPTED_EXPOOL (c5) ve vgk.sys

Aslında aşağıdaki konuyla neredeyse birebir diyebiliriz.


Yani genelde güncel olmayan Vanguard sürücüsünü kullandığınızdan kaynaklanır.

Bu konudaki çözümü uyguladığınızda bir problem kalmayacaktır yüksek ihtimalle.

Tabii belli başlı dönemlerde Vanguard'da veya başka anti-hilelerde, oyun sürücülerinde bu tarz problemler yaşanıyor ve sadece size özel olmayabiliyor. Güncelleme beklemek gerekebiliyor. Riot güncellemeyi yayınlayınca çözülüyor, bu yeni güncellemelerden birinde olan soruna mı denk geldiniz orasını bilmiyorum. :)


Döküm:
Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: ffffae0eeff8e743, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80119e9a08e, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1328

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3640

    Key  : Analysis.Init.CPU.mSec
    Value: 140

    Key  : Analysis.Init.Elapsed.mSec
    Value: 59811

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xc5

    Key  : Bugcheck.Code.Register
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  092622-7781-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

BUGCHECK_CODE:  c5

BUGCHECK_P1: ffffae0eeff8e743

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80119e9a08e

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  VALORANT-Win64

TRAP_FRAME:  ffffad0bcfb09540 -- (.trap 0xffffad0bcfb09540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffae0ee5e00000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80119e9a08e rsp=ffffad0bcfb096d0 rbp=0000000000000000
 r8=ffffc40144c21cb0  r9=0000000000000001 r10=ffffc4014fc6d668
r11=ffffad0bcfb09758 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!ExFreePoolWithTag+0x7e:
fffff801`19e9a08e f647f308        test    byte ptr [rdi-0Dh],8 ds:ffffffff`fffffff3=??
Resetting default scope

STACK_TEXT:
ffffad0b`cfb093f8 fffff801`19833fa9     : 00000000`0000000a ffffae0e`eff8e743 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffad0b`cfb09400 fffff801`1982fee8     : fffff801`29c00000 ffffc401`44c21cb0 00000000`00040286 00000000`00000076 : nt!KiBugCheckDispatch+0x69
ffffad0b`cfb09540 fffff801`19e9a08e     : 01000000`00100000 00000000`00000004 00000000`00000000 00000000`00040246 : nt!KiPageFault+0x468
ffffad0b`cfb096d0 fffff801`2a40f3ef     : fffff801`00000000 fffff801`29c7ac40 00000000`00000000 00000000`00000000 : nt!ExFreePoolWithTag+0x7e
ffffad0b`cfb09760 fffff801`00000000     : fffff801`29c7ac40 00000000`00000000 00000000`00000000 00000000`00000001 : vgk+0x80f3ef
ffffad0b`cfb09768 fffff801`29c7ac40     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000008 : 0xfffff801`00000000
ffffad0b`cfb09770 00000000`00000000     : 00000000`00000000 00000000`00000001 00000000`00000008 00000000`00000001 : vgk+0x7ac40


SYMBOL_NAME:  vgk+80f3ef

MODULE_NAME: vgk

IMAGE_NAME:  vgk.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  80f3ef

FAILURE_BUCKET_ID:  0xC5_2_vgk!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f440937e-e808-2f2e-10ad-7db228ddf2cc}

Followup:     MachineOwner
---------
 
Çözüm
Merhaba,

DRIVER_CORRUPTED_EXPOOL (c5) ve vgk.sys

Aslında aşağıdaki konuyla neredeyse birebir diyebiliriz.


Yani genelde güncel olmayan Vanguard sürücüsünü kullandığınızdan kaynaklanır.

Bu konudaki çözümü uyguladığınızda bir problem kalmayacaktır yüksek ihtimalle.

Tabii belli başlı dönemlerde Vanguard'da veya başka anti-hilelerde, oyun sürücülerinde bu tarz problemler yaşanıyor ve sadece size özel olmayabiliyor. Güncelleme beklemek gerekebiliyor. Riot güncellemeyi yayınlayınca çözülüyor, bu yeni güncellemelerden birinde olan soruna mı denk geldiniz orasını bilmiyorum. :)

Döküm:
Kod:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an.
interrupt request level (IRQL) that is too high. This is.
caused by drivers that have corrupted the system pool. Run the driver.
verifier against any new (or suspect) drivers, and if that doesn't turn up.
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: ffffae0eeff8e743, memory referenced.
Arg2: 0000000000000002, IRQL.
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg4: fffff80119e9a08e, address which referenced memory.

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1328.

 Key : Analysis.DebugAnalysisManager
 Value: Create.

 Key : Analysis.Elapsed.mSec
 Value: 3640.

 Key : Analysis.Init.CPU.mSec
 Value: 140.

 Key : Analysis.Init.Elapsed.mSec
 Value: 59811.

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

 Key : Bugcheck.Code.DumpHeader
 Value: 0xc5.

 Key : Bugcheck.Code.Register
 Value: 0xa.

 Key : Dump.Attributes.AsUlong
 Value: 1008.

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

FILE_IN_CAB: 092622-7781-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008.
 Kernel Generated Triage Dump.

BUGCHECK_CODE: c5.

BUGCHECK_P1: ffffae0eeff8e743.

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80119e9a08e.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VALORANT-Win64

TRAP_FRAME: ffffad0bcfb09540 -- (.trap 0xffffad0bcfb09540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffae0ee5e00000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80119e9a08e rsp=ffffad0bcfb096d0 rbp=0000000000000000
 r8=ffffc40144c21cb0 r9=0000000000000001 r10=ffffc4014fc6d668
r11=ffffad0bcfb09758 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc.
nt!ExFreePoolWithTag+0x7e:
fffff801`19e9a08e f647f308 test byte ptr [rdi-0Dh],8 ds:ffffffff`fffffff3=??
Resetting default scope.

STACK_TEXT:
ffffad0b`cfb093f8 fffff801`19833fa9 : 00000000`0000000a ffffae0e`eff8e743 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffad0b`cfb09400 fffff801`1982fee8 : fffff801`29c00000 ffffc401`44c21cb0 00000000`00040286 00000000`00000076 : nt!KiBugCheckDispatch+0x69
ffffad0b`cfb09540 fffff801`19e9a08e : 01000000`00100000 00000000`00000004 00000000`00000000 00000000`00040246 : nt!KiPageFault+0x468
ffffad0b`cfb096d0 fffff801`2a40f3ef : fffff801`00000000 fffff801`29c7ac40 00000000`00000000 00000000`00000000 : nt!ExFreePoolWithTag+0x7e
ffffad0b`cfb09760 fffff801`00000000 : fffff801`29c7ac40 00000000`00000000 00000000`00000000 00000000`00000001 : vgk+0x80f3ef
ffffad0b`cfb09768 fffff801`29c7ac40 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000008 : 0xfffff801`00000000
ffffad0b`cfb09770 00000000`00000000 : 00000000`00000000 00000000`00000001 00000000`00000008 00000000`00000001 : vgk+0x7ac40

SYMBOL_NAME: vgk+80f3ef

MODULE_NAME: vgk.

IMAGE_NAME: vgk.sys

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 80f3ef.

FAILURE_BUCKET_ID: 0xC5_2_vgk!unknown_function

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {f440937e-e808-2f2e-10ad-7db228ddf2cc}

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

Çok teşekkür ederim.
 

Yeni konular

Geri
Yukarı