So... as the title says. This has been happening to me since the first time I visited Kumos, but I never really used it so far and thus I just ignored it. However, with the Mysterious Melody update which I love, I went to the site and tried to participate. Every page loads perfectly fine, and then after seconds, it goes white and displays the error message STATUS_ACCESS_VIOLATION in Chrome, rendering the site unusable for me. I've tried doing some research online, seeing some people conclude it's a hardware issue. However, kumos.subeta.net is the only site that does this for me, this hasn't happened to me on any other sites I've ever visited, so I have my doubts. It does work on my partner's PC, though.

I tried doing everything Chrome recommends to fix the problem: updated the browser, cleared the cache, restarted my PC, etc. No dice, sadly.

It happens within like 5-30 seconds after loading a page. Hovering over the navigation bar, specifically the commerce tab, and hovering over the drop down menu crashes me immediately.

I shortly tested using the site in Edge and it seems to work, but I'm not really willing to use a separate browser for the Kumos site. It feels a little iffy being forced to use the new site to access this feature when it doesn't work. I do wanna thank you for the hard work on the new site though! Just wish I could access it, haha. Anyone else experiencing this? Are there any known fixes?

A STATUS_ACCESS_VIOLATION error happens when a piece of software tries to use memory which is not assigned to it. This isn't a problem on Subeta's end, because a webserver has zero influence on which memory your browser tries to access. If a remote server would be able to decide which memory to access, then hackers would have a much, much easier time stealing your bank account.

So this is a problem between Chrome, the operating system, drivers and hardware of your device. Unfortunately, it doesn't seem to be an easy problem to solve, since there can be many factors involved. For some people, reinstalling direct x helped, but other people reinstalled windows (and I assume direct x with it) and that didn't help them at all. Disabling browser extensions could help. Some people reported that disabling hardware acceleration for the browser helped. Others report they had to change settings in the BIOS (disabling Game Boost) and others report it might be an issue with a certain line of CPUs.