F5F Stay Refreshed Hardware Desktop Help!

Help!

Help!

F
FCRemedy
Member
63
02-02-2023, 04:17 AM
#1
Your PC experiences crashes after starting games, it restarts itself and the display loses signal. You’ve noticed Windows sounds when you press Shift to trigger keys, and you tried Alt+F4 to fix a driver issue. Your system specs are solid but you’re facing recurring problems with drivers and startup failures. Someone should assist you in resolving this issue.
F
FCRemedy
02-02-2023, 04:17 AM #1

Your PC experiences crashes after starting games, it restarts itself and the display loses signal. You’ve noticed Windows sounds when you press Shift to trigger keys, and you tried Alt+F4 to fix a driver issue. Your system specs are solid but you’re facing recurring problems with drivers and startup failures. Someone should assist you in resolving this issue.

A
AguaViva
Junior Member
5
02-05-2023, 03:21 AM
#2
It appears the drivers are still in effect. Could you confirm the current version?
A
AguaViva
02-05-2023, 03:21 AM #2

It appears the drivers are still in effect. Could you confirm the current version?

S
Shanie167
Junior Member
3
02-05-2023, 11:39 AM
#3
25.4.1
S
Shanie167
02-05-2023, 11:39 AM #3

25.4.1

A
Atyrio
Junior Member
49
02-05-2023, 04:30 PM
#4
25.4.1 came after 23.10.2 and probably didn’t fully resolve the issue. They likely just moved you back to 23.10.2. AMD should have kept a record of older drivers on their website. Searching for driver 23.0 for a RX 6600 online should provide guidance. I’d stick to official sources rather than GitHub or similar sites.
A
Atyrio
02-05-2023, 04:30 PM #4

25.4.1 came after 23.10.2 and probably didn’t fully resolve the issue. They likely just moved you back to 23.10.2. AMD should have kept a record of older drivers on their website. Searching for driver 23.0 for a RX 6600 online should provide guidance. I’d stick to official sources rather than GitHub or similar sites.

R
Roycie_Bear
Member
181
02-06-2023, 12:10 AM
#5
I don't support games requiring Directx12 in older versions.
R
Roycie_Bear
02-06-2023, 12:10 AM #5

I don't support games requiring Directx12 in older versions.

M
MessiasCraft
Member
153
02-08-2023, 12:19 AM
#6
They installed a specific driver during the repair. Just revisit that option.
M
MessiasCraft
02-08-2023, 12:19 AM #6

They installed a specific driver during the repair. Just revisit that option.

C
CatGotNoName
Junior Member
2
02-08-2023, 01:31 AM
#7
I didn't interfere with drivers upon their return, and it's the 25.4.1 release.
C
CatGotNoName
02-08-2023, 01:31 AM #7

I didn't interfere with drivers upon their return, and it's the 25.4.1 release.

K
KingSmylie
Member
156
02-09-2023, 10:16 PM
#8
Yes, I can guide you through checking the Event Viewer. Make sure to do it immediately once the screen is back up after a restart.
K
KingSmylie
02-09-2023, 10:16 PM #8

Yes, I can guide you through checking the Event Viewer. Make sure to do it immediately once the screen is back up after a restart.

S
superphilly123
Junior Member
23
02-10-2023, 03:09 AM
#9
Multiple issues occurred within a two-hour period, including problems with Hyper-V-Hypervisor, kernel boot failures, TPM-WMI conflicts, and WHEA-Logger errors.
S
superphilly123
02-10-2023, 03:09 AM #9

Multiple issues occurred within a two-hour period, including problems with Hyper-V-Hypervisor, kernel boot failures, TPM-WMI conflicts, and WHEA-Logger errors.

G
62
02-10-2023, 04:46 AM
#10
Event IDs are needed for analysis. Hyper-V-Hypervisor is standard, but the ID helps identify boot issues. Kernel Boot indicates activity during startup. TPM-WMI relates to BIOS and secure boot—ensure it's enabled in Windows 10+. WHEA-Logger involves hardware data without an ID, so check settings individually. Adjust one at a time; verify Secure Boot status. Test again and proceed to further troubleshooting.
G
greatcanada123
02-10-2023, 04:46 AM #10

Event IDs are needed for analysis. Hyper-V-Hypervisor is standard, but the ID helps identify boot issues. Kernel Boot indicates activity during startup. TPM-WMI relates to BIOS and secure boot—ensure it's enabled in Windows 10+. WHEA-Logger involves hardware data without an ID, so check settings individually. Adjust one at a time; verify Secure Boot status. Test again and proceed to further troubleshooting.