The usual KERNELBASE.dll

I think the title speaks for itself.
Went around every post trying to find a fix.
From windows safe boot to memory scan. Updated my bios and even upgraded to windows 11. From launching the game in admin from root to using windows 8 package. Scanned faulty hdd/ssd package, re-installed .NET visual c++ and directX, went back to factory setting motherboard, underclocked my cpu, under volt my cpu (wich is something actualy dangerous to do), updated every single driver...

I think I can say that I've tried everything to fix this issue and start thinking like one the microsoft developper that posted on the support page, the main reason for this to happen is poorly developed software.

At least I can play (sort of) as long as I don't go into any lobby, do any expedition or heist, or get unlucky on map settings. This is defenitaly an issue that come from one of the countless assets in the game.

I don't know if this information can help developpers to fix it but besides random crash (what I would call random is Kernelbase crash when I go into a lobby or some heist or maps), there is one thing where this happen everytime and it's expedition. As soon as the explosion happen, sound start buging and I get 1 or 2 frame with 1 fps before game shutdown. I can see the beginning of the animation (the big wave on the ground). I don't if there's some sort of particules in the game (I call particule the same thing you can do in 3D software) but once I see the first wave something that makes me crash spawns-in.

Since most of the post I'm seeing with this issue (that aren't resolved) are from 3.25, I think it's something that have been added in 3.25.

"

kittyet#5615 wrote:

I think the title speaks for itself.

It really doesn't. The file you've named is a core part of the Windows OS, and - just due to the nature of Windows - a variety of errors which fail to properly ascertain the cause of a problem will erroneously blame KernelBase.dll. This is perhaps most commonly due to drivers behaving badly - as they interact with KernelBase.dll and can, essentially, 'lead it astray'.

Your post can be summed up as "I am getting an error message. I will not elaborate further." - which is, essentially, telling us you have a problem but refusing to be any more specific. We don't even know whether we're dealing with a program crash or a Blue Screen of Death...

Nobody here is in the business of being mind readers. If you're not willing to do something as rudimentary as quoting / posting a screenshot of an error message, you won't get much useful assistance on forums. You are the only source of information we have for your issue.