F5F Stay Refreshed Hardware Desktop Desktop crash occurred yesterday due to BSOD.

Desktop crash occurred yesterday due to BSOD.

Desktop crash occurred yesterday due to BSOD.

Pages (2): Previous 1 2
P
PatrickJosh
Member
109
03-11-2016, 05:36 AM
#11
From what I understand, this hasn't occurred before again? It might have taken Windows some time to resolve itself, which is still unusual, but if it doesn't happen again, it's likely not an issue. I'd recommend backing up crucial files just in case and clearing the CMOS by removing the battery, as I mentioned earlier. You could also attempt a stress test on the machine to check for hardware problems.
P
PatrickJosh
03-11-2016, 05:36 AM #11

From what I understand, this hasn't occurred before again? It might have taken Windows some time to resolve itself, which is still unusual, but if it doesn't happen again, it's likely not an issue. I'd recommend backing up crucial files just in case and clearing the CMOS by removing the battery, as I mentioned earlier. You could also attempt a stress test on the machine to check for hardware problems.

D
dpbigbear10
Member
162
03-11-2016, 01:46 PM
#12
Your setup has been enhanced by XMP settings for RAM and an Intel Turbo Boost adjustment from 4.0 GHz to 4.2 GHz.
D
dpbigbear10
03-11-2016, 01:46 PM #12

Your setup has been enhanced by XMP settings for RAM and an Intel Turbo Boost adjustment from 4.0 GHz to 4.2 GHz.

B
blueunicorn05
Junior Member
30
03-11-2016, 04:21 PM
#13
Consider disabling the Intel Turbo Boost, reset the CMOS, and perform a stress test on the system. If issues arise, revert to the original settings and check if XMP settings can be disabled as well.
B
blueunicorn05
03-11-2016, 04:21 PM #13

Consider disabling the Intel Turbo Boost, reset the CMOS, and perform a stress test on the system. If issues arise, revert to the original settings and check if XMP settings can be disabled as well.

X
Xindis_
Member
249
03-16-2016, 09:21 AM
#14
Visit C:\Windows\Minidump to see if any minidump files exist. If present, return to the Windows directory and move the Minidump folder to the Downloads folder (use your desktop if needed). Compress the moved folder and include it in a post. Please adhere strictly to instructions since Windows doesn't allow file changes there. Tell me which error messages you're encountering if you don't have any files.
X
Xindis_
03-16-2016, 09:21 AM #14

Visit C:\Windows\Minidump to see if any minidump files exist. If present, return to the Windows directory and move the Minidump folder to the Downloads folder (use your desktop if needed). Compress the moved folder and include it in a post. Please adhere strictly to instructions since Windows doesn't allow file changes there. Tell me which error messages you're encountering if you don't have any files.

S
Sahvoz
Member
63
03-16-2016, 09:33 AM
#15
Removed CMOS and turned off XMP settings. Windows 10 was reinstalled to the incorrect drive, but kernel power events keep appearing. It’s happening again—check if the disk is properly mounted and ensure no conflicting drivers are active.
S
Sahvoz
03-16-2016, 09:33 AM #15

Removed CMOS and turned off XMP settings. Windows 10 was reinstalled to the incorrect drive, but kernel power events keep appearing. It’s happening again—check if the disk is properly mounted and ensure no conflicting drivers are active.

B
Bring_It
Senior Member
423
03-16-2016, 06:30 PM
#16
Kernel-Power Event ID 41 indicates an unexpected shutdown. This can occur due to power loss, freezes, BSODs, or holding the power button. Any unintended power cut-off. The event name doesn't provide diagnostic meaning unless you're unaware it was a restart or shutdown. Share the dump files.
B
Bring_It
03-16-2016, 06:30 PM #16

Kernel-Power Event ID 41 indicates an unexpected shutdown. This can occur due to power loss, freezes, BSODs, or holding the power button. Any unintended power cut-off. The event name doesn't provide diagnostic meaning unless you're unaware it was a restart or shutdown. Share the dump files.

M
MegaDJ
Member
64
03-17-2016, 04:16 PM
#17
I resolved the issue by executing the command in cmd with powercfg -restoredefaultschemes
M
MegaDJ
03-17-2016, 04:16 PM #17

I resolved the issue by executing the command in cmd with powercfg -restoredefaultschemes

Pages (2): Previous 1 2