The Enigma of Power Settings: A Tale of a PC’s Selective Performance


I’ve encountered a perplexing issue with my newly assembled PC, which exhibits unusual behavior when running certain applications. Despite thorough testing and component replacements, the problem persists, leading me to suspect a potential CPU defect. Could you provide your expert analysis on this matter and advise on how to approach the retailer for a resolution? Here’s a detailed account of the challenges I’ve faced:

  • PC Configuration:
  • Intel Core i9-14900K
  • Asus ROG Formula Z790
  • Corsair HX1000i PSU
  • Asus GeForce RTX 4070 Dual OC 12GB
  • Crucial T700 4TB NVMe M.2 SSD
  • 2 x Crucial P3 Plus 4TB NVMe M.2 SSD
  • Creative Sound Blaster AE-5 Plus Sound Card
  • 2 x 32GB Corsair Vengeance 6400MHz DDR5 RAM
  • Dual-boot with Windows 11 and Manjaro
  • Issues Encountered:
  • Certain applications, specifically a Minecraft Modpack called GTNH, fail to load under normal or high-performance power settings in Windows, citing errors related to OpenAL.dll and jvm.dll.
  • The modpack runs under the power saver setting but experiences silent crashes when switching back to higher performance modes.
  • Under Manjaro, the game consistently fails, and package compilation from the AUR results in segmentation faults.
  • Initially, the motherboard’s PCIe 5.0 M.2 slot failed to recognize the T700 SSD after BSOD incidents, leading to RMA processes that returned no faults.
  • Running the modpack in a Virtualbox VM of Manjaro on Windows 11 is successful, albeit slow, and does not cause compilation issues.
  • Currently avoiding the PCIe 5.0 M.2 slot and using PCIe 4.0 slots has prevented further BSODs, but the original issues remain.
  • Given these circumstances, I’m inclined to believe the CPU may be at fault. How would you interpret these symptoms, and what would be the best course of action to take with the retailer?


you for your assistance.


When faced with a high-performance PC that behaves erratically, particularly with specific applications, it’s essential to approach the issue methodically. The symptoms you’ve described suggest a complex interaction between hardware and software, which can be challenging to diagnose. Here’s an expert analysis of the situation and guidance on how to proceed with the retailer.

The issues you’re experiencing, especially the application-specific errors and system instability, point towards a few potential culprits:


Power Management Settings:

The fact that the Minecraft Modpack GTNH only loads correctly under the power saver setting in Windows suggests that power management could be interfering with the application’s operation. This could be due to the CPU not receiving enough power to maintain stability under load, which is less of an issue under power saver mode.


Hardware Compatibility:

The consistent failure of the game under Manjaro and segmentation faults when compiling packages could indicate a compatibility issue with the Linux kernel or a lack of proper driver support for your hardware configuration.


SSD and PCIe Slot Issues:

The recurring problems with the motherboard’s PCIe 5.0 M.2 slot and the T700 SSDs, along with the BSODs, could be symptomatic of a deeper hardware issue, potentially with the motherboard or the SSDs themselves.


CPU Suspicions:

While the CPU is a possible suspect, given the variety of symptoms, it’s not the only potential cause. CPUs are generally robust, and defects are rare, but they can happen. The CLOCK_WATCHDOG_TIMEOUT error is particularly concerning as it often indicates processor-related issues.

Approaching the Retailer:

When engaging with the retailer, it’s crucial to present your findings clearly and concisely:

  • Document Everything:

    Keep a detailed record of all the tests you’ve conducted, the errors encountered, and any steps you’ve taken to resolve the issues.

  • Be Specific:

    Clearly outline the symptoms and why you suspect the CPU might be at fault. Mention the CLOCK_WATCHDOG_TIMEOUT error and the fact that other components have been tested and returned without faults.

  • Request Further Testing:

    Ask if the retailer can conduct their own tests on the CPU or provide a replacement for further diagnosis.

  • Know Your Rights:

    Familiarize yourself with the warranty and return policy. This knowledge will be helpful if you need to negotiate a return or replacement.

  • In conclusion, while the CPU may be at fault, it’s also possible that the issues are due to a combination of factors, including power management, hardware compatibility, and potential defects in other components. By presenting your case effectively to the retailer, you increase the chances of a satisfactory resolution. Remember, persistence and clear communication are key when dealing with complex technical issues and warranty claims.

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    Privacy Terms Contacts About Us