This started happening only a couple months back, but every time my blade 14 starts, Synapse crashes (and keyboard backlighting shuts off, etc.) until I forcibly exit and restart the application. Then everything works fine until the next boot. I’ve tried reinstall synapse and reinstalling the VS C++ redistributables. No change. Seems to me like an issue within the Synapse software.
Same issue here!
Glad to hear it's not just me. I did a lot of diag on this and realized that part of the universal c runtime dll on win 11 is always the system version, not from a redistributable - so tracked back to when that dll was last modified and tried reverting the windows updates that affected that dll. This did not fix the issue which makes sense because I believe the onset coincided with a synapse update. I'm 99% sure it's a bug in the synapse software. If razer gave me the sources to run locally I'd debug and fix it.
Seems there are many others with issue since months ago but no official solution so far🙄.
Contact with Razer support, run DISM and SFC seems solved the issue.
Contact with Razer support, run DISM and SFC seems solved the issue.
Glad you got it fixed - the same does not work to resolve the issue for me.
After a long back and forth with Razer support I kind of just got a “we’re not sure try reinstalling windows again” response. I went back to the drawing board on diagnosing the problem and thought more about the fact that this issue doesn’t happen on restart, only on a cold boot. That’s what lead me to the solution - disabling fast startup.
whether or not you have this issue probably depends on a few things, but I am on the very latest updates for win 11, on the latest 2023 blade 14 firmware/bios, and have 64gb RAM. Something about this combination is causing an issue when using “fast startup”, as disabling it fixes the problem entirely. Also with my SK Hynix P41 NVME drive there is no difference in boot time with this disabled. Unfortunately wasted a lot of time trying to fix what wasn’t broken with this (clean reinstalling everything multiple times, digging through logs, memory dumps, etc.) This was the simple solution. Hopefully it helps others facing this issue who don’t have any windows corruption or issues with other applications.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
