1. Are you overclocking in any form? Overclocking if the clock isnt stable can cause system errors so try either using one of the preset XMP profile if you have done an overclock manually or if using XMP already try disabling it with in BIOS.
2. Did you update to newest drivers for GPU (if so Id recommend reverting GPU drivers to october 2024 or older) the newest drivers are horrible in terms of compatibility with cards that aren't the AI GPUs (newest gen GPUs) because the newest drivers are technically vGPU drivers (v=virtual).
3. Another thing is have you updated bios recently (if not try and see if you have a newer BIOS update) if your BIOS is acting up and not updated the power distribution can be extremely inconsistent on some systems and cause crashing.
4. Have you tried reinstalled ur windows to see if that fixed the Blue screening? I was having a similar issue where PC wouldnt Blue Screen but just fully shut down and it was due to power distrabution was being messed with from one of the Windows updates which then corrupted my full windows install after reinstalling the windows OS. I havent had any Issue related to that.
English
-
Hope that helps and apologize if your not super techy and know what any of those things really are. Ill try and answer any questions and help if I see the noti. I wish you the best of luck though and feel ur pain, when these type of things happen it can cause you to have to do alot of trouble shooting to find the actual cause for error.
-
BEDaisy.sys issues causing the issue. Seems to be battle eye... I no longer know how to fix it. I installed battle eye, reinstalled, didn't work. I uninstalled EVERY Game. reinstalled. didn't work I wiped my PC. reinstalled. still crashes. I have no idea how to stop battle eye from killing my PC
-
a) Just did a NIVIDIA rollback to september, immediately BSOD'd my PC. So that did not work. b) I am on intel baseline (safety mode, whatever you wish to call it) because of their instability issues. I have overclocked RAM only, nothing else is OC. Ram I do not believe to be the problem though, but just to prove that it isn't the issue I just put that to auto (far less than the OC) and it BSOD again. XMP is off. c) BIOS is fresh, I keep up with them. no difference that I can tell d) I have used sfc /scannow and some other scanning tool. nothing appears broken in the windows side. I COULD do a windows reset, but I have a lot of my job on here, so it makes it awkward because it takes like 10 hours to set everything back up.
-
Edytowany przez użytkownika TikTok @ ichirp: 4/25/2025 1:19:54 AM1. Check event viewer for the critical error and search the error code it shows. 2. Use XMP profile 1 instead of manually OC and lets the auto tuner set the rest of the OC under option 1 in BIOS. 3. Reinstall windows with the fix option in windows settings. (this wont get rid of all ur apps but fix any corruption) 4. (FOR THIS SECTION YOU ONLY NEED ONE OR THE OTHER. CMD OR POWERSHELL IT DOESNT MATTER WHICH BUT I USE CMD) Set ur power plan to ultimate performance mode. You'll need to open the Command Prompt or PowerShell with administrative privileges. For Command Prompt, hit Start, type "cmd" into the search box, right-click the Command Prompt result, and choose "Run As Administrator." For PowerShell, hit Windows+X and choose the "Windows PowerShell (Admin) option. At the prompt, type (or copy and paste) the following command and then hit Enter: powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61 If you already have the Power Options window open, you might have to close and reopen it before you see the plan appear, but it should be there. Then select the Ultimate power plan and close the Control Panel.
-
Sorry been working a lot. Critical failure, all of them at as follows: Critical, Kernel-Power, Event 41, Category 63. Definition: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Not too useful to me tbh. Idk if you know more about this than I do, but that just reads "it turns off randomly" to me. Nothing too helpful online either that I can see. especially because if you look it up, it basically says "this can be any part in your PC" lol tried the power cmd, did not do anything. Tried XMP 1, did not change anything. I'll do the reinstall windows on Sunday and see how she goes and report back o7
-
any luck with the fresh windows install? Kernel Power event 41 is exactly what I had happening to me and my system. Window reinstall is the only thing that fixed it.
-
[b][u]Solution[/u]************** [/b] So I looked into Kernel-Power (Event Viewer issue causing BSOD) and It basically said that it could be from a faulty PSU, Motherboard, or CPU. But I'm broke lol. So I tried this: Windows Repair: Did not work. <-- Not the Software PSU software checker: No issues detected Windows RAM checker: No issues detected Motherboard: Did a range of BIOS, Did not work. Fresh Windows install: Did not work. Result, must be the CPU. Shocker. I looked into this even further and decided that I should undervolt my CPU, as Intel is famously unstable right now. So I installed Intel XTU (Extreme Tuning Utility), and I went from x55 (because I'm using an i9-13900k) to x53. I also did the Intel baseline from their website, NOT the Intel baseline from my Motherboard, since apparently that's different. Obviously, this will make you lose some performance, but if BattleEye (the reason the crashes happen in the first place) is causing a throttle, which is causing BSOD is so unstable you can't play, then eh. its justified. Also the performance lost is minor. so who cares. Sources: Baseline Values used: https://www.youtube.com/watch?v=iiS04RcswHA The video that gave me the idea to undervolt + reduce my performance cores, since you showed me how to use Event Viewer and I figured what it was: https://www.youtube.com/watch?v=aB81bgzNM1w&t=286s
-
Yup I have the XTU as well haha glad you found a fix and I hope it holds!
-
These are the next trouble shooting steps Id take. Itll get you more information as to what is causing the Error, if it doesnt just solve the issue all together.