F5F Stay Refreshed Software Operating Systems You're getting a BSoD, please help!

You're getting a BSoD, please help!

You're getting a BSoD, please help!

D
DINfire99
Junior Member
17
07-19-2024, 03:05 AM
#1
Your system has been running smoothly for several years, but recently you've experienced random BSOD errors. The codes you've encountered include KERNEL_SECURITY_CHECK_FAILURE, IRQL_NOT_LESS_OR_EQUAL, and CRITICAL_PROCESS_DIED. You've tried reinstalling the OS, cleaning partitions, and rebooting after deleting all drives, but the issue persists with varying stop messages. No recent changes have resolved the problem.
D
DINfire99
07-19-2024, 03:05 AM #1

Your system has been running smoothly for several years, but recently you've experienced random BSOD errors. The codes you've encountered include KERNEL_SECURITY_CHECK_FAILURE, IRQL_NOT_LESS_OR_EQUAL, and CRITICAL_PROCESS_DIED. You've tried reinstalling the OS, cleaning partitions, and rebooting after deleting all drives, but the issue persists with varying stop messages. No recent changes have resolved the problem.

C
CommonGamers75
Junior Member
11
08-03-2024, 02:08 PM
#2
These problems indicate serious memory or malware issues. Verify your RAM arrangement and condition. Run memtest86 to test stability. This suggests a graphics driver problem. Which card is installed? What drivers are active? Ensure they were fully removed and reinstalled via DDU. The situation may stem from damaged Windows components. Likely linked to the two points mentioned. What hardware details do you have? Did updates or hardware changes occur recently? Have you refreshed your motherboard’s BIOS?
C
CommonGamers75
08-03-2024, 02:08 PM #2

These problems indicate serious memory or malware issues. Verify your RAM arrangement and condition. Run memtest86 to test stability. This suggests a graphics driver problem. Which card is installed? What drivers are active? Ensure they were fully removed and reinstalled via DDU. The situation may stem from damaged Windows components. Likely linked to the two points mentioned. What hardware details do you have? Did updates or hardware changes occur recently? Have you refreshed your motherboard’s BIOS?

E
Eragon1512
Member
94
08-04-2024, 09:04 AM
#3
You've already reset the system, which isn't ideal if you're unsure about the issue. Next, review your memory settings—it's a wise move. Consider turning off overclocking and using MSI Afterburner to lower your GPU clock speed. Even after a memory test, keep a single RAM stick for safety. It depends on how often you encounter BSODs. Another option is running AdwCleaner and checking Autoruns to see what starts up. Since you reset, chances of malware are low. Also, remove any manufacturer tools (like Asus or MSI utilities) that claim to boost performance.
E
Eragon1512
08-04-2024, 09:04 AM #3

You've already reset the system, which isn't ideal if you're unsure about the issue. Next, review your memory settings—it's a wise move. Consider turning off overclocking and using MSI Afterburner to lower your GPU clock speed. Even after a memory test, keep a single RAM stick for safety. It depends on how often you encounter BSODs. Another option is running AdwCleaner and checking Autoruns to see what starts up. Since you reset, chances of malware are low. Also, remove any manufacturer tools (like Asus or MSI utilities) that claim to boost performance.

N
nooneepic27
Member
227
08-09-2024, 08:46 PM
#4
I7 7700k with 4x8 GB DDR4 RAM, Corsair Vengeance M.2 SSD, MSI Z-170A Pro GTX 1060, 3GB Corsair RM650X, Samsung 850 EVO (1TB), Seagate Barricuda 2TB, no hardware updates. Recently upgraded to the latest version; a BSOD appeared after installation. It's difficult to test because such an event is rare, but it seems to happen every few days. Prior to the reset, it was quite common.
N
nooneepic27
08-09-2024, 08:46 PM #4

I7 7700k with 4x8 GB DDR4 RAM, Corsair Vengeance M.2 SSD, MSI Z-170A Pro GTX 1060, 3GB Corsair RM650X, Samsung 850 EVO (1TB), Seagate Barricuda 2TB, no hardware updates. Recently upgraded to the latest version; a BSOD appeared after installation. It's difficult to test because such an event is rare, but it seems to happen every few days. Prior to the reset, it was quite common.