F5F Stay Refreshed Hardware Desktop Faulty driver leading to BSOD code 0x000000c4

Faulty driver leading to BSOD code 0x000000c4

Faulty driver leading to BSOD code 0x000000c4

M
Mprs
Junior Member
Find
18
01-25-2021, 10:15 PM
#1
Details: CPU – Ryzen 7 3700X, RAM – 32GB G.SKILL 3200MHz DDR4, Motherboard – ASUS TUF GAMING X570 PLUS (WiFi), PSU – 700W EVGA 80+ GOLD, GPU – AMD RX 6600, Keyboard – Razer BlackWidow, Mouse – Razer DeathAdder v2. I’ve tried resetting the PC, cleaning via Device Manager, and reinstalling Synapse. The BSOD still appears when using the driver verifier. Can you help fix it so I can play games like Osu! again? Best regards, Deathly.
Reply
Reply
M
Mprs
01-25-2021, 10:15 PM #1

Details: CPU – Ryzen 7 3700X, RAM – 32GB G.SKILL 3200MHz DDR4, Motherboard – ASUS TUF GAMING X570 PLUS (WiFi), PSU – 700W EVGA 80+ GOLD, GPU – AMD RX 6600, Keyboard – Razer BlackWidow, Mouse – Razer DeathAdder v2. I’ve tried resetting the PC, cleaning via Device Manager, and reinstalling Synapse. The BSOD still appears when using the driver verifier. Can you help fix it so I can play games like Osu! again? Best regards, Deathly.

Reply
Reply
C
Craftery
Member
Find
207
01-25-2021, 10:49 PM
#2
It looks odd that the driver corrupts the core kernel. Reset the PC, perform a fresh format instead of using Windows settings, and back up your data. Try a different driver, or reach out to Razer support if it doesn’t work.
Reply
Reply
C
Craftery
01-25-2021, 10:49 PM #2

It looks odd that the driver corrupts the core kernel. Reset the PC, perform a fresh format instead of using Windows settings, and back up your data. Try a different driver, or reach out to Razer support if it doesn’t work.

Reply
Reply
M
MapSurviver
Junior Member
Find
25
01-26-2021, 01:38 AM
#3
You're asking about the new layout or design change. It seems the update affected the operating system since the verification tool detected it as an internal command.
Reply
Reply
M
MapSurviver
01-26-2021, 01:38 AM #3

You're asking about the new layout or design change. It seems the update affected the operating system since the verification tool detected it as an internal command.

Reply
Reply
E
Eusebio06
Senior Member
Find
595
01-26-2021, 05:12 AM
#4
Create a bootable USB drive or opt for an 11 USB stick. Wipe all existing partitions on HDD/SSD down to the unallocated area, then reinstall Windows 10 or 11. Enjoy a clean installation.
Reply
Reply
E
Eusebio06
01-26-2021, 05:12 AM #4

Create a bootable USB drive or opt for an 11 USB stick. Wipe all existing partitions on HDD/SSD down to the unallocated area, then reinstall Windows 10 or 11. Enjoy a clean installation.

Reply
Reply
J
jonas1708
Member
Find
70
01-27-2021, 08:48 AM
#5
I found the fix was quite tricky, but eventually I succeeded. What I needed to do was unplug my keyboard and remove the driver from the system32 folder. I also had to delete the device manager entry. Once those steps were done, the issue disappeared completely—no more blue screens!
Reply
Reply
J
jonas1708
01-27-2021, 08:48 AM #5

I found the fix was quite tricky, but eventually I succeeded. What I needed to do was unplug my keyboard and remove the driver from the system32 folder. I also had to delete the device manager entry. Once those steps were done, the issue disappeared completely—no more blue screens!

Reply
Reply