Dear CIG Support Team, I am submitting this report because my computer frequently performs a complete system reboot while playing Star Citizen. Initially, I suspected that the issue might be related to the well-known Intel 13th/14th Generation CPU stability concerns that have been widely discussed over the past year. Because of this, I began troubleshooting from the BIOS and CPU side first, assuming that CPU voltage behavior or degradation might be responsible. However, after extensive testing, the issue continues to occur even under default BIOS settings, which is why I am reporting it here. ## System Specifications Operating System: Windows 10 64-bit CPU: Intel Core i5-14600KF Motherboard: ASUS ROG STRIX B760-G GAMING WIFI BIOS Version: 1820 GPU: NVIDIA GeForce RTX 4070 Ti SUPER Memory: Gloway DDR5-6400 16G*2 Power Supply: GTR750 750W 80+ Gold ATX 3.0 Game Installation: ZHITAI Tiplus7100 1Tb ## Issue Description While playing Star Citizen, the entire computer suddenly reboots. When the issue occurs: * No Blue Screen of Death (BSOD) * No Star Citizen crash dialog * No application error message * System immediately restarts Most occurrences happen within approximately 30 minutes of gameplay. In rare cases, the game can run for a significantly longer period without issues. ## Temperature Monitoring CPU temperature remains approximately 60°C during gameplay. Because of the relatively low operating temperature, overheating does not appear to be the cause of the reboot. ## Windows Event Viewer Findings Windows Event Viewer records: * Kernel-Power Event ID 41 * WHEA-Logger Event ID 1 An important observation is that the WHEA event appears several seconds after the Kernel-Power event rather than before it. This may indicate that the WHEA entry is being generated during system recovery after the reboot rather than being the original trigger. ## Troubleshooting Performed ### BIOS Default Testing I restored BIOS defaults and tested with: * No CPU overclocking * No CPU undervolting * No manual voltage adjustments * No custom power limits Result: The issue still occurs. ### XMP Testing I tested with: * XMP Enabled * XMP Disabled Result: The system reboots in both configurations. ### CPU Undervolting Testing I also tested: * IA VR Voltage Limit set to 1.30V *CPU Core Voltage = 1.265V * P-Core 5.2 GHz * E-Core 4.0 GHz Result: The issue still occurs. ### P-Core Only Testing To rule out E-Core related scheduling issues, I tested the game using only Performance Cores. Result: The issue still occurs. ### Graphics API Testing I tested both rendering APIs: * Vulkan * DirectX 11 Result: The issue occurs with both APIs. ### Graphics Quality Testing I reduced graphics quality settings to Medium. Result: The issue still occurs. ## Version Comparison An important observation is that I do not recall experiencing this issue during Star Citizen 4.7. The problem appears to have become significantly more frequent after updating to Star Citizen 4.8. Because of this timing, I am concerned that the issue may be related to changes introduced in the 4.8 update. ## Request for Investigation Since I have already tested: * BIOS defaults * XMP disabled * CPU undervolting * P-Core only operation * Vulkan and DirectX 11 * Reduced graphics settings I would appreciate any guidance regarding whether this behavior may be associated with: * A known Star Citizen 4.8 issue * Easy Anti-Cheat * Rendering pipeline changes * Resource streaming changes * CPU scheduling behavior * Intel 13th/14th Generation processor compatibility * Known reboot or hardware-instability reports introduced after 4.8 Any information or recommendations would be greatly appreciated. Thank you for your time and assistance. Star Citizen is currently the only application that consistently reproduces this issue. Other games and daily workloads have not triggered similar system reboots.