F5F Stay Refreshed Hardware Desktop Do you experience multiple BSODs each day?

Do you experience multiple BSODs each day?

Do you experience multiple BSODs each day?

Pages (2): 1 2 Next
G
gamer2hokv
Member
198
04-30-2025, 09:15 PM
#1
I've been experiencing several BSODs daily based on what I use my PC for that day. It began a few months ago with CRITICAL_PROCESS_DIED errors. After a fresh installation of the boot drive, a week passed and the BSODs returned without flashing long enough for me to notice the error. I reviewed the event logs and saw criticals errors, but they only mentioned Kernel-Power 41 (63) followed by a critical event after reboot indicating Diagnostics-Performance Event ID: 100. I think the problem comes from the kernel BSOD or the events leading up to it, but I need guidance on diagnosing which hardware might need replacement from these errors.

I've tried CHKDSK, mdsched.exe, SFC scans, a clean install, and BIOS updates, but haven't been able to identify the issue.

If anyone can assist, it would be a great help.

Regards,
Dabsie
G
gamer2hokv
04-30-2025, 09:15 PM #1

I've been experiencing several BSODs daily based on what I use my PC for that day. It began a few months ago with CRITICAL_PROCESS_DIED errors. After a fresh installation of the boot drive, a week passed and the BSODs returned without flashing long enough for me to notice the error. I reviewed the event logs and saw criticals errors, but they only mentioned Kernel-Power 41 (63) followed by a critical event after reboot indicating Diagnostics-Performance Event ID: 100. I think the problem comes from the kernel BSOD or the events leading up to it, but I need guidance on diagnosing which hardware might need replacement from these errors.

I've tried CHKDSK, mdsched.exe, SFC scans, a clean install, and BIOS updates, but haven't been able to identify the issue.

If anyone can assist, it would be a great help.

Regards,
Dabsie

G
Gladiador70
Senior Member
698
04-30-2025, 10:33 PM
#2
Speaking of hardware;
Full system specs, including PSU make and model (or part number) is? Also, how old the PSU is, and was the PSU bought new or used/refurbished?
G
Gladiador70
04-30-2025, 10:33 PM #2

Speaking of hardware;
Full system specs, including PSU make and model (or part number) is? Also, how old the PSU is, and was the PSU bought new or used/refurbished?

U
UnKnown_MBE
Junior Member
7
05-11-2025, 07:05 PM
#3
PC Specifications -
Motherboard: Gigabyte Z390 AORUS PRO WIFI (Intel)
Storage: Samsung 970 EVO Plus
Hard Drive: Seagate ST2000DM008-2FR102 2TB SATA Drive
Graphics Card: NVIDIA GeForce RTX 2080
Processor: Intel® Core™ i7-9700K @ 3.6GHz (Liquid Cooled)
Memory: Trident G-Skill Z 2x 8GB DDR4 3000MHz
Power Supply: 650W Coola Master (likely Bronze 80 or silver)
All components were purchased new.
The construction date was 2019, so the system is holding up well.
U
UnKnown_MBE
05-11-2025, 07:05 PM #3

PC Specifications -
Motherboard: Gigabyte Z390 AORUS PRO WIFI (Intel)
Storage: Samsung 970 EVO Plus
Hard Drive: Seagate ST2000DM008-2FR102 2TB SATA Drive
Graphics Card: NVIDIA GeForce RTX 2080
Processor: Intel® Core™ i7-9700K @ 3.6GHz (Liquid Cooled)
Memory: Trident G-Skill Z 2x 8GB DDR4 3000MHz
Power Supply: 650W Coola Master (likely Bronze 80 or silver)
All components were purchased new.
The construction date was 2019, so the system is holding up well.

N
226
05-11-2025, 09:19 PM
#4
You can receive complete PSU information upon request. Just let me know.
N
n_tiffanyblue_
05-11-2025, 09:19 PM #4

You can receive complete PSU information upon request. Just let me know.

T
Titanz
Junior Member
35
05-11-2025, 09:29 PM
#5
This issue arises following an unexpected restart. Upon startup, Windows executes a report and detects irregularities from the prior shutdown, triggering this event. It is considered a reaction rather than a cause. The Volume Manager handles storage devices, which may refer to the C drive or an HDD. Consider running Magician on your SSD via the provided link. For HDDs, refer to the support page at the given URL.

The BSOD codes are numerous—over 255 entries exist, prompting further investigation. If the critical process has already failed, it would be noteworthy as such errors typically stem from Windows crashing, including boot files.

Follow the instructions in option one on the linked page, then proceed with the next steps: create a small memory dump during a BSOD using Windows File Explorer, locate the generated mini-dump files on your Desktop, transfer them to a cloud storage service, and share the link for review.
T
Titanz
05-11-2025, 09:29 PM #5

This issue arises following an unexpected restart. Upon startup, Windows executes a report and detects irregularities from the prior shutdown, triggering this event. It is considered a reaction rather than a cause. The Volume Manager handles storage devices, which may refer to the C drive or an HDD. Consider running Magician on your SSD via the provided link. For HDDs, refer to the support page at the given URL.

The BSOD codes are numerous—over 255 entries exist, prompting further investigation. If the critical process has already failed, it would be noteworthy as such errors typically stem from Windows crashing, including boot files.

Follow the instructions in option one on the linked page, then proceed with the next steps: create a small memory dump during a BSOD using Windows File Explorer, locate the generated mini-dump files on your Desktop, transfer them to a cloud storage service, and share the link for review.

K
KAI_CANADIAN
Member
62
05-12-2025, 04:27 AM
#6
Feel free to verify whenever you're done with this test!
K
KAI_CANADIAN
05-12-2025, 04:27 AM #6

Feel free to verify whenever you're done with this test!

A
audi497mks
Senior Member
601
05-17-2025, 04:13 AM
#7
I've completed a similar task before and can share a zip file of all crashes after the memtest. I've also set up an action in the registry to log every BSOD. Once my PC is back online, I'll attach the log files immediately! Thank you for your prompt response!
A
audi497mks
05-17-2025, 04:13 AM #7

I've completed a similar task before and can share a zip file of all crashes after the memtest. I've also set up an action in the registry to log every BSOD. Once my PC is back online, I'll attach the log files immediately! Thank you for your prompt response!

Z
ZexyZeke
Member
166
05-17-2025, 01:52 PM
#8
Yes, it's necessary because Cooler Master units may vary greatly in quality, depending on the model. That's why the model name or part number matters a lot.
Also, a faulty PSU could cause this issue.
Z
ZexyZeke
05-17-2025, 01:52 PM #8

Yes, it's necessary because Cooler Master units may vary greatly in quality, depending on the model. That's why the model name or part number matters a lot.
Also, a faulty PSU could cause this issue.

T
thomasladd907
Member
57
05-17-2025, 04:26 PM
#9
41 63 doesn't automatically mean a bad PSU, it's just a restart.
It's also not an error—it's just an event.
T
thomasladd907
05-17-2025, 04:26 PM #9

41 63 doesn't automatically mean a bad PSU, it's just a restart.
It's also not an error—it's just an event.

P
pa55w0rd
Member
181
05-17-2025, 08:28 PM
#10
Isn't it about energy waste?
🤔
If the loss is brief, the system will restart. But if it's more significant, the PC will completely power off.
P
pa55w0rd
05-17-2025, 08:28 PM #10

Isn't it about energy waste?
🤔
If the loss is brief, the system will restart. But if it's more significant, the PC will completely power off.

Pages (2): 1 2 Next