Who would have possibly thought that an invalid memory access is not simply solved by reinstalling… /s,j Oh wait me. /srs I’m totally not experienced in how computers work, totally don’t know how to write code that compiles to machine code and think that computers are just magic stones. /s,j

Then you probably know how to generate a Dxdiag report and upload it on a site and link it here for users of this forum to check it out.

[url]https://c0d3m4513r.com/files/6a5d92c4-4b31-40b8-a729-5a0ee40c0ee8/DxDiag.txt[/url]

No Windows Error reported?

Log Name: Application Source: Application Error Date: 25.10.2023 22:28:49 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: WIN-PQAH7QIAGM6 Description: Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00007ff66432359c Faulting process id: 0x674c Faulting application start time: 0x01da0781ac6a8e58 Faulting application path: bad_module_info Faulting module path: unknown Report Id: 6dec9a9d-bb5c-47ac-a42c-312ab09a92a2 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2023-10-25T20:28:49.1476457Z" /> <EventRecordID>227459</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>WIN-PQAH7QIAGM6</Computer> <Security /> </System> <EventData> <Data>bad_module_info</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>00007ff66432359c</Data> <Data>674c</Data> <Data>01da0781ac6a8e58</Data> <Data>bad_module_info</Data> <Data>unknown</Data> <Data>6dec9a9d-bb5c-47ac-a42c-312ab09a92a2</Data> <Data> </Data> <Data> </Data> </EventData> </Event>

Where 0xc0000005 is: "The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s." (from) [url]https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/596a1078-e883-4972-9bbc-49e60bebca55[/url]

Also under System there are three more related events: at: 25.10.2023 22:28:57 File System Filter 'BEDaisy' (Version 10.0, ‎2022‎-‎04‎-‎19T19:09:51.000000000Z) unloaded successfully. at 25.10.2023 22:27:23: File System Filter 'BEDaisy' (10.0, ‎2022‎-‎04‎-‎19T19:09:51.000000000Z) has successfully loaded and registered with Filter Manager. at: 25.10.2023 22:27:23 A service was installed in the system. Service Name: BEDaisy Service File Name: C:\Program Files (x86)\Common Files\BattlEye\BEDaisy.sys Service Type: kernel mode driver Service Start Type: demand start Service Account:

Given this information I think the Anticheat is just shitting itself rn.

Very possible, but if it does, it's because something else (program, antivirus, firewall) is impeding it.

I don't have any antivirus or firewall (except the default windows stuff) and my software setup has not substancially changed since I switched from NVIDIA to AMD.

It could also be an unexpected interaction with the video drivers.

But if it was AMD GPU drivers in general more people would be having the issue, and it would be known, right?

In fact I don't see a problem with my AMD drivers (well, if you were using 23.10.1 with a RX 7x00 card and Anti-Lag+ activated while playing a game like CS2 you could have got banned though, but that's a peculiar case), but with your installation, possibly something tied to the video card (and respective drivers) change .

I DDU'd my drivers properly though. There should be nothing left of the old drivers. One peculiar thing that AMD has got going is that SystemInformer reads two GPU's (one of which has 0 information)

I don't think that's a good sign.