F5F Stay Refreshed Software Operating Systems : Experiencing crashes twice daily, then smooth operation after adjusting the RAM clock speed.

: Experiencing crashes twice daily, then smooth operation after adjusting the RAM clock speed.

: Experiencing crashes twice daily, then smooth operation after adjusting the RAM clock speed.

E
EqaulCrazy
Junior Member
9
02-22-2023, 01:05 AM
#1
Hi@everybody,
ok since about a week I get the strangest crashes and I can not find out why.
Do you have any idea how I can find out what is not working and causing the crashes?
+ How to fix it?
The situation:
After updating nearly all drivers, windows 11 and preparing for the Cyberpunk launch I get in game crashes. Playing Cyberpunk or Rainbow Six Siege will result in a loss of signal for all displays. Audio is fine for around 30 seconds. Than the system is totally unresponsive or a automatic reboot is initalized, The graphic card is not very hot when the crash occures (70c)
After the reboot there is about a 50% chance that when booting Win11 I'll only see some graphic artifacts (some blue dots in the lower left corner of the screen). -> than I'll hit the power button and reboot again, I'll always get these artefacts after that till I proceed to the next step. The motherboard cycles so fast through error messages that I can not read them clearly.
After I can not boot I'll go into UEFI and switch the RAM clock speed from 6000 to default 4800 or visa versa . Save & quit and restart.
After that the system will reboot I can play Cyberpunk on with full raytracing and the graphic card at around 82c and everything is fine till the next shutdown. After the next shutdown the same sequence of crashes and reboots will happen.
The system:
- i5-13600K 3.50 GHz
- Z 690 Aurus Pro
- RTX 4070 Ti
- G.Skill DIMM 32 GB DDR5-6000 Kit
- Seasonic Prime TX-750
- Win11
was running absolutly stable since January.
Already done:
-
Googled (Graphic card crashes Cyberpunk, win11 crashes, system monitoring after crash ....)
- Checked this forum
- Reversed graphic driver installation (clean)
- Reverted to UEFI default settings.
- Troubleshooting, nothing found.
- Checked System logs
: ("The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." -> most likely due to me pressing the power button for 5 seconds. Got a lot of nvlddmkm errors too, but not after every crash)
- Ran FurMark as a full load test (went fine, no crash)
- All Windows updates in queue
- checked windows minidump, found reboot entries but nothing I could interprete as cause of the crash
Minidump file in Google Drive
)
- flashing the newest version of UEFI
- disk check (
chkdsk)
What I'm doing now:
- Done everything I could think of
My guess:
I feel it's a graphic card issue and it was caused by the newest patches (537.42) but reversing them did not help.
Also thought it might be a power problem, overloading the power supply, but it's a 750watt system and even under full load the crash is not caused consistently. Rainbow six Siege is definitly not using the full performence of the system.
I'm very thankfull for any ideas, system monitoring tools or anything else what could help finding the cause or fixing it! =)
edit: added PSU and corrected max power draw
E
EqaulCrazy
02-22-2023, 01:05 AM #1

Hi@everybody,
ok since about a week I get the strangest crashes and I can not find out why.
Do you have any idea how I can find out what is not working and causing the crashes?
+ How to fix it?
The situation:
After updating nearly all drivers, windows 11 and preparing for the Cyberpunk launch I get in game crashes. Playing Cyberpunk or Rainbow Six Siege will result in a loss of signal for all displays. Audio is fine for around 30 seconds. Than the system is totally unresponsive or a automatic reboot is initalized, The graphic card is not very hot when the crash occures (70c)
After the reboot there is about a 50% chance that when booting Win11 I'll only see some graphic artifacts (some blue dots in the lower left corner of the screen). -> than I'll hit the power button and reboot again, I'll always get these artefacts after that till I proceed to the next step. The motherboard cycles so fast through error messages that I can not read them clearly.
After I can not boot I'll go into UEFI and switch the RAM clock speed from 6000 to default 4800 or visa versa . Save & quit and restart.
After that the system will reboot I can play Cyberpunk on with full raytracing and the graphic card at around 82c and everything is fine till the next shutdown. After the next shutdown the same sequence of crashes and reboots will happen.
The system:
- i5-13600K 3.50 GHz
- Z 690 Aurus Pro
- RTX 4070 Ti
- G.Skill DIMM 32 GB DDR5-6000 Kit
- Seasonic Prime TX-750
- Win11
was running absolutly stable since January.
Already done:
-
Googled (Graphic card crashes Cyberpunk, win11 crashes, system monitoring after crash ....)
- Checked this forum
- Reversed graphic driver installation (clean)
- Reverted to UEFI default settings.
- Troubleshooting, nothing found.
- Checked System logs
: ("The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." -> most likely due to me pressing the power button for 5 seconds. Got a lot of nvlddmkm errors too, but not after every crash)
- Ran FurMark as a full load test (went fine, no crash)
- All Windows updates in queue
- checked windows minidump, found reboot entries but nothing I could interprete as cause of the crash
Minidump file in Google Drive
)
- flashing the newest version of UEFI
- disk check (
chkdsk)
What I'm doing now:
- Done everything I could think of
My guess:
I feel it's a graphic card issue and it was caused by the newest patches (537.42) but reversing them did not help.
Also thought it might be a power problem, overloading the power supply, but it's a 750watt system and even under full load the crash is not caused consistently. Rainbow six Siege is definitly not using the full performence of the system.
I'm very thankfull for any ideas, system monitoring tools or anything else what could help finding the cause or fixing it! =)
edit: added PSU and corrected max power draw

Z
ZazaPanda
Member
151
02-24-2023, 09:03 AM
#2
Didn't specify the make and model of your PSU. If it's been used for a while, mention the unit's age. What BIOS version is installed on your motherboard? If you've updated the BIOS to the newest release, proceed by resetting CMOS and then continue with the operating system while keeping BIOS set to UEFI.
Z
ZazaPanda
02-24-2023, 09:03 AM #2

Didn't specify the make and model of your PSU. If it's been used for a while, mention the unit's age. What BIOS version is installed on your motherboard? If you've updated the BIOS to the newest release, proceed by resetting CMOS and then continue with the operating system while keeping BIOS set to UEFI.

C
cladff
Junior Member
24
03-12-2023, 03:09 PM
#3
Thank you for your response. I included the PSU (Seasonic TX-750) and adjusted the 1200 to 750 watts. My BIOS version is F23 as far as I recall, but I plan to update it to the latest version 27 tomorrow.
C
cladff
03-12-2023, 03:09 PM #3

Thank you for your response. I included the PSU (Seasonic TX-750) and adjusted the 1200 to 750 watts. My BIOS version is F23 as far as I recall, but I plan to update it to the latest version 27 tomorrow.

T
Tonkinesequeen
Junior Member
9
03-13-2023, 12:22 AM
#4
I'm keeping a cautious outlook at the moment. The QFlash to version F27 appears to resolve the problem. I need to check it over the next couple of days. However, if you come across this message and experience crashes with a similar configuration, update your BIOS to the latest release, even though the previous update is only six months old. I'll revise the post in a few days if this was truly the source of the issue.
T
Tonkinesequeen
03-13-2023, 12:22 AM #4

I'm keeping a cautious outlook at the moment. The QFlash to version F27 appears to resolve the problem. I need to check it over the next couple of days. However, if you come across this message and experience crashes with a similar configuration, update your BIOS to the latest release, even though the previous update is only six months old. I'll revise the post in a few days if this was truly the source of the issue.

Y
yalo29
Senior Member
641
03-13-2023, 01:00 AM
#5
The issue remains unchanged. Anyone with a suggestion would be helpful. I updated the BIOS to the latest release and reset everything, but the system continues to crash.
Y
yalo29
03-13-2023, 01:00 AM #5

The issue remains unchanged. Anyone with a suggestion would be helpful. I updated the BIOS to the latest release and reset everything, but the system continues to crash.