Crash Error with "Geocomply player location services"

[Hoflax24]

I've been trying to fix easy anti cheat crashes for a while, and upon looking at the event viewer, it gives me errors with "player location check" and "geocomply".

As far as I've sen from this forum, no one has posted about it, but does anyone have any thoughts? I know there's the steam_appid fix but I'm trying everything I can to see why easy anti cheat is crashing my pc. It has shown "player location check" and "geocomply" as the cause of the last two crashes I've tested in the last 15 minutes.

[Hoflax24]

Originally posted by csand:

Geocomply seems to be some other software ofteb included in gambling apps or sports streaming, and so w other stuff like that. Maybe it is causing issues, see if you can uninstall it or disable it

Wow. So I have a fanduel account, and using the browser site requires you to have a locatoin service enabeled, and I guess it messes with EAC. I never thought about that, but it seems like that was the issue

[dark-breed]

Good job csand.

@hoflax24 the service that caused the problem seams to have not secure access to some things at your System and it is with 100% chance not Microsoft certified.

It is questionable when a service has such a impact to a anticheat Software.

[Hoflax24]

Originally posted by dark-breed:

Good job csand.

@hoflax24 the service that caused the problem seams to have not secure access to some things at your System and it is with 100% chance not Microsoft certified.

It is questionable when a service has such a impact to a anticheat Software.

Thanks for the reply! Turns out that still wasn't the tissue, something with the Kernel 28 error is doing it now. I read up and it seems I need to update my bios which seems like a hassle, but I'm not sure of any other fixes

[dark-breed]

Originally posted by Hoflax24:

Originally posted by dark-breed:

Good job csand.

@hoflax24 the service that caused the problem seams to have not secure access to some things at your System and it is with 100% chance not Microsoft certified.

It is questionable when a service has such a impact to a anticheat Software.

Thanks for the reply! Turns out that still wasn't the tissue, something with the Kernel 28 error is doing it now. I read up and it seems I need to update my bios which seems like a hassle, but I'm not sure of any other fixes

Where appears this error ? Do you mean a eventid 28 Kernel trace error in event viewer ?

A kernel trace error can be the bios but also specific Firmware Updates at the related device.
Post a Screenshot of the error.

[Hoflax24]

Originally posted by dark-breed:

Originally posted by Hoflax24:

Thanks for the reply! Turns out that still wasn't the tissue, something with the Kernel 28 error is doing it now. I read up and it seems I need to update my bios which seems like a hassle, but I'm not sure of any other fixes

Where appears this error ? Do you mean a eventid 28 Kernel trace error in event viewer ?

A kernel trace error can be the bios but also specific Firmware Updates at the related device.
Post a Screenshot of the error.

I'm not quite sure how to post a screenshot, but these are the consistent error messages I get each time:

Microsoft-Windows-Kernel-EventTracing/Admin
Source: Kernel-EventTracing
Event ID: 28
Task Category: Provider
Error setting traits on Provider {8444a4fb-d8d3-4f38-84f8-89960a1ef12f}. Error: 0xC0000001

Kernel-PnP
Event ID: 219
The driver \Driver\WudfRd failed to load for the device HID\VID_03F0&PID_0D8B&MI_03&Col02\9&bd3a57&0&0001.

WHEA-Logger
Event ID: 18
A fatal hardware error has occurred.
Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 0
EventData

ErrorSource 3
ApicId 0
MCABank 22
MciStat 0xbaa000000002010b
MciAddr 0x0
MciMisc 0xd01a0ffe00000000
ErrorType 9
TransactionType 2
Participation 256
RequestType 0
MemorIO 256
MemHierarchyLvl 3
Timeout 256
OperationType 256
Channel 256
Length 936

Then there's a very long "Raw data" string that's mostly 0s

[Hoflax24]

There's also Critcal Error Kernel Power Event 41, another identical Kernel 28 message, and a second WHEA 18 error message, but the error type is different, "Bus/Interconnect Error"