[SOLVED] Blue screen ntoskrnl.exe

[PINK SKYLINE]

Getting BSOD since today when starting the game. Dumps say it's related to EAC, which I tried repairing, with no success. Anyone else getting BSOD?

Verified files
Reinstalled
Ran as admin
Tried reinstalling EAC
Reinstalled gfx driver
Defaulted BIOS
Tried changing windows settings for kernel protection
Run the “winsat formal”

[Likon]

look into the troubleshoting guide

[PINK SKYLINE]

Originally posted by Likon:

look into the troubleshoting guide

i did, it didn't solve bsods

[Lim1tBreak]

Have you tried reinstalling Windows? It may sound extreme but it sounds like you have tried a lot and ntoskrnl.exe is the kernel of Windows. issues with the kernel can cause kernel "panics" or what is known in the Window's world as a BSOD. The game could be causing it, but since its not happening to everyone this may just be an oddity with your system's particular configuration at this time.

A fresh install of Windows should reset everything back to a fresh slate. I have to do it myself from time to time.

[PINK SKYLINE]

Originally posted by Lim1tBreak:

Have you tried reinstalling Windows? It may sound extreme but it sounds like you have tried a lot and ntoskrnl.exe is the kernel of Windows. issues with the kernel can cause kernel "panics" or what is known in the Window's world as a BSOD. The game could be causing it, but since its not happening to everyone this may just be an oddity with your system's particular configuration at this time.

A fresh install of Windows should reset everything back to a fresh slate. I have to do it myself from time to time.

I have not and will not reinstall Windows for EAC. I've had lots of issues with EAC on many different systems and heard as much from friends. It's malware essentially, that causes problems for anyone. So no, I will rather uninstall Pavlov, as ♥♥♥♥♥♥ as it got after the update. Reinstalling Windows will with 90% probability not fix this, as this is not issue with Windows per se.

ntoskrnl is what runs EAC, so that's why it says "ntoskrnl". It also mentiones the EAC.exe as well, so it's really not a Windows issue but the EAC causing the BSOD. I run 13900k so if anytning, it is realated to EAC updates not being tested properly for new hardware.

ps i'm a tech guru on my free time, so no real need to explain what bsod it, but thank you

[Gnarly Gnorc]

I love Pavlov but these fixes are getting out of hand.

The proper way to fix Pavlov is to install Linux on your toenail and reinstall oculus software on your vas deferens and see if openXVrRuneskape is running on omnipower + if that doesn't work reinstall Earth.exe and see if that does anything.

[PINK SKYLINE]

Originally posted by Gnarly Gnorc:

I love Pavlov but these fixes are getting out of hand.

The proper way to fix Pavlov is to install Linux on your toenail and reinstall oculus software on your vas deferens and see if openXVrRuneskape is running on omnipower + if that doesn't work reinstall Earth.exe and see if that does anything.

I don't do oculus, my Pimax is Windows only AFAIK. Linux is not there yet for gaming, unfortunately. Would switch in a heartbeat.

What Earth.exe and toenail are you talking about? Feels like a complicated set of steps not applicable to my problem or config. I just want to play Pavlov, not reinstall my OS. It worked fine yesterday before EAC update.

[Lim1tBreak]

Originally posted by PINK SKYLINE:

Originally posted by Lim1tBreak:

Have you tried reinstalling Windows? It may sound extreme but it sounds like you have tried a lot and ntoskrnl.exe is the kernel of Windows. issues with the kernel can cause kernel "panics" or what is known in the Window's world as a BSOD. The game could be causing it, but since its not happening to everyone this may just be an oddity with your system's particular configuration at this time.

A fresh install of Windows should reset everything back to a fresh slate. I have to do it myself from time to time.

I have not and will not reinstall Windows for EAC. I've had lots of issues with EAC on many different systems and heard as much from friends. It's malware essentially, that causes problems for anyone. So no, I will rather uninstall Pavlov, as ♥♥♥♥♥♥ as it got after the update. Reinstalling Windows will with 90% probability not fix this, as this is not issue with Windows per se.

ntoskrnl is what runs EAC, so that's why it says "ntoskrnl". It also mentiones the EAC.exe as well, so it's really not a Windows issue but the EAC causing the BSOD. I run 13900k so if anytning, it is realated to EAC updates not being tested properly for new hardware.

ps i'm a tech guru on my free time, so no real need to explain what bsod it, but thank you

EAC is a factor, but the fact that other systems are running without the BSOD alludes to an issue somewhere else (maybe caused by EAC, maybe caused by another change). If EAC was the culprit, my machine would also BSOD (I am running Windows and EAC with Pavlov and it works fine). a reinstall just wipes the slate clean, its not a root cause fix but it provides a blank slate to troubleshoot from.

ntoskrnl runs EAC because its the windows kernel, it has to run everything by design. something is messing up in the kernel itself when EAC is doing something. So yes it is something EAC is doing, but on a fresh system this blue screen doesnt happen, which points to something else. Is another program patching kernel calls in a way ntoskrnl doesnt expect like a driver? Were certain permissions messed up with critical files or the registry? I dont know how EAC works, but these would be questions I would ask while troubleshooting.

You don't have to believe me though, and it sounds like you might not, but hopefully the message above explains things in a bit more detail.

[PINK SKYLINE]

Originally posted by Lim1tBreak:

If EAC was the culprit, my machine would also BSOD (I am running Windows and EAC with Pavlov and it works fine)

Our setup is not identical, and therefore you can not assume that the issue is within my machine. This is a combination of EAC and config/hw. If everything works butter smooth, yet EAC casuses identical BSOD each and every time, it's clearly an issue with EAC.

Originally posted by Lim1tBreak:

a reinstall just wipes the slate clean, its not a root cause fix but it provides a blank slate to troubleshoot from.

Yes, but do I want to reinstall a relatively fresh, well-functioning and otherwise super stable OS for a game that has peaked and is on it's way to the bottom? I do not want to spend whole day restoring my dev. env. for a buggy game that breaks with each update (see all threads after update).

Originally posted by Lim1tBreak:

I dont know how EAC works

Nobody does, that's the only reason it's used by devs. Rootkit by design, super intrusive and buggy. Malware in my book, since it's causing malicious activity.

Originally posted by Lim1tBreak:

ntoskrnl runs EAC because its the windows kernel, it has to run everything by design. something is messing up in the kernel itself when EAC is doing something. So yes it is something EAC is doing, but on a fresh system this blue screen doesnt happen, which points to something else. Is another program patching kernel calls in a way ntoskrnl doesnt expect like a driver? Were certain permissions messed up with critical files or the registry?

Dumps state following

 *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80232c85705, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 15

    Key  : Analysis.Elapsed.mSec
    Value: 1186

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_EasyAntiCheat_EOS!unknown_function

    Key  : Failure.Hash
    Value: {220d5b3d-33fc-4c8e-6484-ebd7c9e905b8}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  a

BUGCHECK_P1: 8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80232c85705

FILE_IN_CAB:  072123-10000-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

READ_ADDRESS: fffff8023371c468: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 0000000000000008 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Pavlov.exe

IRP_ADDRESS: ffffa78bc110e010

DEVICE_OBJECT: ffffa78baafb08f0

TRAP_FRAME:  ffffbe896871c430 -- (.trap 0xffffbe896871c430)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80232c85705 rsp=ffffbe896871c5c0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000001 r10=ffffa78bc9b0a320
r11=ffffa78bc3afaae0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!KeSetEvent+0xa5:
fffff802`32c85705 4c395108        cmp     qword ptr [rcx+8],r10 ds:00000000`00000008=????????????????
Resetting default scope

STACK_TEXT:  
ffffbe89`6871c2e8 fffff802`32e442a9     : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffbe89`6871c2f0 fffff802`32e3f934     : ffffa78b`00000000 ffffbe89`6871c780 00000000`00000001 fffff802`32e443fc : nt!KiBugCheckDispatch+0x69
ffffbe89`6871c430 fffff802`32c85705     : 00000000`00000000 ffffbe89`6871bd38 ffffbe89`6871da20 ffffa78b`c110e020 : nt!KiPageFault+0x474
ffffbe89`6871c5c0 fffff802`32d37e37     : ffffa78b`00000000 ffffbe89`6871c779 ffffa78b`c110e010 ffffa78b`c9b0a320 : nt!KeSetEvent+0xa5
ffffbe89`6871c650 fffff802`32d56c26     : ffffa78b`c110e088 00000000`00001000 ffffa78b`c110e010 f0bca87f`fd16c500 : nt!IopCompleteRequest+0x887
ffffbe89`6871c720 fffff802`32e34a6c     : f357e66f`f8b3a300 00000000`00000000 00000000`00000004 fd4d6f56`00000000 : nt!KiDeliverApc+0x186
ffffbe89`6871c7e0 fffff802`32cd4f28     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiApcInterrupt+0x35c
ffffbe89`6871c970 fffff802`a6e7bc7b     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExReleaseFastMutex+0x38
ffffbe89`6871c9a0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff802`32cd4ef0 : EasyAntiCheat_EOS+0xbc7b


SYMBOL_NAME:  EasyAntiCheat_EOS+bc7b

MODULE_NAME: EasyAntiCheat_EOS

IMAGE_NAME:  EasyAntiCheat_EOS.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  bc7b

FAILURE_BUCKET_ID:  AV_EasyAntiCheat_EOS!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {220d5b3d-33fc-4c8e-6484-ebd7c9e905b8}

Followup:     MachineOwner 

Originally posted by Lim1tBreak:

You don't have to believe me though, and it sounds like you might not, but hopefully the message above explains things in a bit more detail.

This is not about believing, I don't have to believe when I can look at the symptoms, dumps, timeline of events and put two and two together. If you say things that make sence, I know you're correct. If you say things that don't or that I don't understand I will ask questions to understand what you mean.

[Lim1tBreak]

Originally posted by PINK SKYLINE:

Originally posted by Lim1tBreak:

If EAC was the culprit, my machine would also BSOD (I am running Windows and EAC with Pavlov and it works fine)

Our setup is not identical, and therefore you can not assume that the issue is within my machine. This is a combination of EAC and config/hw. If everything works butter smooth, yet EAC casuses identical BSOD each and every time, it's clearly an issue with EAC.

Originally posted by Lim1tBreak:

a reinstall just wipes the slate clean, its not a root cause fix but it provides a blank slate to troubleshoot from.

Yes, but do I want to reinstall a relatively fresh, well-functioning and otherwise super stable OS for a game that has peaked and is on it's way to the bottom? I do not want to spend whole day restoring my dev. env. for a buggy game that breaks with each update (see all threads after update).

Originally posted by Lim1tBreak:

I dont know how EAC works

Nobody does, that's the only reason it's used by devs. Rootkit by design, super intrusive and buggy. Malware in my book, since it's causing malicious activity.

Originally posted by Lim1tBreak:

ntoskrnl runs EAC because its the windows kernel, it has to run everything by design. something is messing up in the kernel itself when EAC is doing something. So yes it is something EAC is doing, but on a fresh system this blue screen doesnt happen, which points to something else. Is another program patching kernel calls in a way ntoskrnl doesnt expect like a driver? Were certain permissions messed up with critical files or the registry?

Dumps state following

 *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80232c85705, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 15

    Key  : Analysis.Elapsed.mSec
    Value: 1186

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_EasyAntiCheat_EOS!unknown_function

    Key  : Failure.Hash
    Value: {220d5b3d-33fc-4c8e-6484-ebd7c9e905b8}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  a

BUGCHECK_P1: 8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80232c85705

FILE_IN_CAB:  072123-10000-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

READ_ADDRESS: fffff8023371c468: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 0000000000000008 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Pavlov.exe

IRP_ADDRESS: ffffa78bc110e010

DEVICE_OBJECT: ffffa78baafb08f0

TRAP_FRAME:  ffffbe896871c430 -- (.trap 0xffffbe896871c430)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80232c85705 rsp=ffffbe896871c5c0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000001 r10=ffffa78bc9b0a320
r11=ffffa78bc3afaae0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!KeSetEvent+0xa5:
fffff802`32c85705 4c395108        cmp     qword ptr [rcx+8],r10 ds:00000000`00000008=????????????????
Resetting default scope

STACK_TEXT:  
ffffbe89`6871c2e8 fffff802`32e442a9     : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffbe89`6871c2f0 fffff802`32e3f934     : ffffa78b`00000000 ffffbe89`6871c780 00000000`00000001 fffff802`32e443fc : nt!KiBugCheckDispatch+0x69
ffffbe89`6871c430 fffff802`32c85705     : 00000000`00000000 ffffbe89`6871bd38 ffffbe89`6871da20 ffffa78b`c110e020 : nt!KiPageFault+0x474
ffffbe89`6871c5c0 fffff802`32d37e37     : ffffa78b`00000000 ffffbe89`6871c779 ffffa78b`c110e010 ffffa78b`c9b0a320 : nt!KeSetEvent+0xa5
ffffbe89`6871c650 fffff802`32d56c26     : ffffa78b`c110e088 00000000`00001000 ffffa78b`c110e010 f0bca87f`fd16c500 : nt!IopCompleteRequest+0x887
ffffbe89`6871c720 fffff802`32e34a6c     : f357e66f`f8b3a300 00000000`00000000 00000000`00000004 fd4d6f56`00000000 : nt!KiDeliverApc+0x186
ffffbe89`6871c7e0 fffff802`32cd4f28     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiApcInterrupt+0x35c
ffffbe89`6871c970 fffff802`a6e7bc7b     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExReleaseFastMutex+0x38
ffffbe89`6871c9a0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff802`32cd4ef0 : EasyAntiCheat_EOS+0xbc7b


SYMBOL_NAME:  EasyAntiCheat_EOS+bc7b

MODULE_NAME: EasyAntiCheat_EOS

IMAGE_NAME:  EasyAntiCheat_EOS.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  bc7b

FAILURE_BUCKET_ID:  AV_EasyAntiCheat_EOS!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {220d5b3d-33fc-4c8e-6484-ebd7c9e905b8}

Followup:     MachineOwner 

Originally posted by Lim1tBreak:

You don't have to believe me though, and it sounds like you might not, but hopefully the message above explains things in a bit more detail.

This is not about believing, I don't have to believe when I can look at the symptoms, dumps, timeline of events and put two and two together. If you say things that make sence, I know you're correct. If you say things that don't or that I don't understand I will ask questions to understand what you mean.

Read the dump, here is the issue:

FAILURE_BUCKET_ID: AV_EasyAntiCheat_EOS!unknown_function

EasyAntiCheat is calling an unknown function. This is further confirmed by what is stated here:

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.

Its probably trying to access a function that doesn't exist in kernel space on your system. Why is it missing? I don't know, you are right, our systems are different and not comparable. However, if you reinstalled windows they would be comparable (clean slate).

I'll go back to enjoying Pavlov now, seems to work on my system.
Enjoy troubleshooting.

[PINK SKYLINE]

Originally posted by Lim1tBreak:

Read the dump, here is the issue:

FAILURE_BUCKET_ID: AV_EasyAntiCheat_EOS!unknown_function

EasyAntiCheat is calling an unknown function. This is further confirmed by what is stated here:

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.

Its probably trying to access a function that doesn't exist in kernel space on your system. Why is it missing? I don't know, you are right, our systems are different and not comparable. However, if you reinstalled windows they would be comparable (clean slate).

I'll go back to enjoying Pavlov now, seems to work on my system.
Enjoy troubleshooting.

Why do you have rub it in?
ReAd ThE dUmP hErE iS ThE iSsuE

Yeah no ♥♥♥♥ sherlock, I have read the dump and I can see that it's calling outside of it's memory address. Why? Nobody knows, thus it's useless information. You can not fix it, so there is nothing to be read.

I have not updated my drivers overnight, and neither did i have any windows updates installed (yes I checked the perfmon /rel)

Why is it trying to access a function it did not access yesterday? And why does my DISM+sfc scannow come out clean? Maybe because it's not the windows that's corrupt?

I'm not here asking you to tell me to nuke my system, I can do that without writing out these long posts. I just don't want to, not for a game that is just gonna be abandonware next monday looking at the reviews charts.

"Seems to work on my system" haha
Well, then mount your system on the rack, bozo

[PINK SKYLINE]

Issue solved. Malwarebytes Beta causes this.
Fix: Reinstall a non-beta Malwarebytes.
Confirmed broken: 4.5.34.275
Confirmed working: 4.5.33.272