Deadcells killing pc?

Hello Tristan, this is Manuela. I'm an Independent Advisor and community user like you, ready to assist with this.
Not a Microsoft employee.

I’m sorry to hear you’re having some performance issues on your PC.
I can suggest you some possible solutions before considering a factory reset:

1. Open the task manager and go to the startup tab, once there, click "disable" on each app listed there.
After that, restart the PC and see if the problem is solved.

2. Do a clean boot in your Windows PC. For that, please follow this article:
https://support.microsoft.com/topic/how-to-perf...

3. Create a new user on your PC:
https://support.microsoft.com/windows/create-a-...

4. Run the SFC tool, this can help you find and repair possible system corruptions.

https://answers.microsoft.com/en-us/windows/for...

5. Perform an in-place upgrade on your PC:
https://answers.microsoft.com/en-us/windows/for...

If you’re using Windows 10 steps are the same, just download the Windows 10 ISO.

My pc is unable to run long enough to even bring up a menu at this point and all I have attempted to do was the steps you listed. After launching deadcells my PC has degraded to a point of being unable to even repair it. I am beyond words at this point. I am using windows 11 and this pc is decently up to date hardware wise. I'm having to reply on my phone. How is Xbox gamepass allowing this to continue on their gamepass when this seems to be a known issue from my digging. It killed my computer just by launching it. I am furious, and unable to do anything because it crashes roughly 5 minutes after launch.

Hi

So I have Dead Cells installed on the XBox launcher and if I whether I launch the game from there or from the Desktop, I allways get this "Null access" error, when I try to start my first save slot. When I start my second save slot it works for some reason, but then I would loose my progress.

This is the Error (for some reason it is impossible to insert an image)

Null access

Called from tool.SpeedrunData.saveBestRunTime (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\src/tool/SpeedrunData.hx line 44)

Called from tool.SpeedrunData.newGame (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\src/tool/SpeedrunData.hx line 22)

Called from User.endMainGame (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\src/User.hx line 569)

Called from tool.$Save.tryLoad (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\src/tool/Save.hx line 185)

Called from pr.TitleScreen.playMenu (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\src/pr/TitleScreen.hx line 422)

Called from pr.TitleScreen.~mainMenu.0 (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\src/pr/TitleScreen.hx line 345)

Called from pr.TitleScreen.~addMenu.0 (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\src/pr/TitleScreen.hx line 687)

Called from h2d.Interactive.handleEvent (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\.haxelib\heaps/git-haxe4,0,2/h2d/Interactive.hx line 163)

Called from h2d.Scene.handleEvent (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\.haxelib\heaps/git-haxe4,0,2/h2d/Scene.hx line 312)

Called from hxd.SceneEvents.emitEvent (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\.haxelib\heaps/git-haxe4,0,2/hxd/SceneEvents.hx line 128)

Called from hxd.SceneEvents.checkEvents (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\.haxelib\heaps/git-haxe4,0,2/hxd/SceneEvents.hx line 279)

Called from hxd.App.mainLoop (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\.haxelib\heaps/git-haxe4,0,2/hxd/App.hx line 159)

Called from Boot.mainLoop (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\src/Boot.hx line 735)

Called from hxd.$System.mainLoop (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\.haxelib\heaps/git-haxe4,0,2/hxd/System.hl.hx line 70)

Called from hxd.$System.runMainLoop (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\.haxelib\heaps/git-haxe4,0,2/hxd/System.hl.hx line 127)

Called from module @0x37FFC00

Called from haxe.$Timer.~delay.0 (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\.tools\haxe\std/haxe/Timer.hx line 143)

Called from haxe.$Timer.~__constructor__.0 (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\.tools\haxe\std/haxe/Timer.hx line 76)

Called from haxe.$MainLoop.tick (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\.tools\haxe\std/haxe/MainLoop.hx line 174)

Called from haxe.$EntryPoint.processEvents (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\.tools\haxe\std/haxe/EntryPoint.hx line 99)

Called from haxe.$EntryPoint.run (D:\Gitlab-Runner\builds\HQ33PpjF\0\motion-twin\deadcells\client\.tools\haxe\std/haxe/EntryPoint.hx line 125)

I have not played Dead Cells so I may not really help with a proper solution. Instead you can check known issues here to see if there is anything that can help you: https://www.reddit.com/r/deadcells/comments/a9kcr4/11_update_known_issues_look_here_before_posting/

Hello Nicholas_kingK how are you?
My name is Ezequiel. I'm an Independent Consultant. I suggest you delete the game and download it again.