NoPaste

stress.txt

von willy4711

Dein Code:
  1. STRESS TESTING YOUR COMPUTER
  2.  
  3. BACKGROUND
  4. ----------
  5.  
  6. Today's computers are not perfect.  Even brand new systems from major
  7. manufacturers can have hidden flaws.  If any of several key components such
  8. as CPU, memory, cooling, etc. are not up to spec, it can lead to incorrect
  9. calculations and/or unexplained system crashes.
  10.  
  11. Overclocking is the practice of increasing the speed of the CPU and/or
  12. memory to make a machine faster at little cost.  Typically, overclocking
  13. involves pushing a machine past its limits and then backing off just a
  14. little bit.
  15.  
  16. For these reasons, both non-overclockers and overclockers need programs
  17. that test the stability of their computers.  This is done by running
  18. programs that put a heavy load on the computer.  Though not originally
  19. designed for this purpose, Prime95 is an excellent way of placing a heavy
  20. load on a computer system and includes a "torture test" to allow users to do
  21. so without interfering in the prime search.
  22.  
  23.  
  24. RESOURCES
  25. ---------
  26.  
  27. This program is a good stress test primarily for CPUs and RAM, as well as
  28. cooling systems and power supplies.  The torture tests run continuously, checking
  29. the calculations are within certain parameters while they are in progress and
  30. comparing your computer's final results to results that are known to be correct.
  31. Any mismatch and you've got a problem!
  32.  
  33. You'll need other programs to stress test other system components, monitor
  34. the state of the system while testing and help identify the source of any faults
  35. that arise.
  36.  
  37. Other stress tests for CPUs, memory, graphics cards etc:
  38.         OCCT - http://www.ocbase.com
  39.         Linpack - http://www.techpowerup.com/download/linpack-xtreme/
  40.         Realbench - http://rog.asus.com/tag/realbench/
  41.         MemTest64 - http://www.techpowerup.com/memtest64/
  42.         FurMark - http://geeks3d.com/furmark/
  43.         GpuTest - https://www.geeks3d.com/gputest/
  44.         PassMark BurnInTest - https://www.passmark.com/products/bit.htm
  45.         Aida64 - https://www.aida64.com/
  46.  
  47. Utilities and monitoring software:
  48.         Intel XTU - https://downloadcenter.intel.com/download/24075
  49.         Ryzen Master - https://www.amd.com/en/technologies/ryzen-master
  50.         Afterburner - https://www.msi.com/page/afterburner
  51.         HWiNFO - https://www.hwinfo.com/
  52.         CPU-Z - https://www.cpuid.com/softwares/cpu-z.html
  53.         GPU-Z - https://www.techpowerup.com/gpuz/
  54.  
  55. Useful websites and forums with pertinent information:
  56.         http://www.overclockers.com
  57.         http://www.overclock.net
  58.         http://www.anandtech.com
  59.         http://www.tomshardware.com
  60.         http://www.hardocp.com
  61.         http://linustechtips.com/main/
  62.         http://ark.intel.com
  63.         http://www.amd.com/en/products/specifications/processors
  64.  
  65. A number of subreddits exist where assistance may be found - please make sure
  66. you understand the scope of each and read their rules before posting:
  67.         http://www.reddit.com/r/pchelp
  68.         http://www.reddit.com/r/buildapchelp
  69.         http://www.reddit.com/r/techsupport
  70.         http://www.reddit.com/r/overclocking
  71.         http://www.reddit.com/r/Intel
  72.         http://www.reddit.com/r/AMD
  73.  
  74.  
  75. WHAT TO DO IF A PROBLEM IS FOUND?
  76. ---------------------------------
  77.  
  78. The exact cause of a hardware problem can be very hard to find.
  79.  
  80. If you are not overclocking, the most likely cause is memory.  It is not uncommon
  81. for memory to not run correctly at its rated speed (incorrectly "binned").  This is
  82. most easily tested by swapping it with memory from another compatible computer and
  83. retesting.  If that is not possible you can try underclocking memory or increasing
  84. memory voltage a tiny bit.  Overheating is another possible source of problems.
  85. You can check the temperatures using monitoring software like HWiNFO to make sure
  86. the CPU is below it's rated temperature limit.  If not, the cooler may be incorrectly
  87. mounted or disconnected from the system while in transit, or the thermal paste
  88. between the CPU and the cooler may not have been applied properly - YouTube is an
  89. excellent place to find videos demonstrating correct cooler/paste application methods.
  90. Occasionally, the power supply is incapable of supplying sufficient power to the
  91. system under heavy load, you can often diagnose this by monitoring the 12v, 5v and
  92. 3.3v voltages - you will typically observe a substantial drop in these voltages when
  93. putting the system under load and generally means the PSU itself needs to be replaced
  94. with a more capable unit.
  95.  
  96. If you are overclocking, the most likely problems are either the CPU core
  97. voltage being set too low or drooping too far under heavy low.  You should
  98. either increase the voltage or adjust the load line calibration to deal
  99. with these issues.  Another frequently seen issue is the motherboard failing
  100. to set a suitable voltage for the memory controller when an XMP profile is
  101. enabled.
  102.  
  103. The above causes are far from a comprehensive list of possible causes.  Diagnosing
  104. the exact cause can be a very difficult process.
  105.  
  106. ***NB:*** You should always thoroughly research the voltage tolerances of any
  107. specific component before you start changing it.  Memory controllers integrated
  108. into modern CPUs in particular are very sensitive to increased running voltages
  109. and can functionally degrade very quickly if set too high.  Also make sure you
  110. have accurate temperature monitoring in place while stress testing with increased
  111. voltages and clock speeds as heat outputs increase exponentially - 1st generation
  112. Ryzen CPUs specifically develop heat-related stability problems when running at
  113. temperatures above 70degC.
  114.  
  115.  
  116. CAN I IGNORE THE PROBLEM?
  117. -------------------------
  118.  
  119. Ignoring the problem is a matter of personal preference.  There are
  120. two schools of thought on this subject.
  121.  
  122. Most programs you run will not stress your computer enough to cause a
  123. wrong result or system crash.  If you ignore the problem, then certain
  124. workloads may stress your machine resulting in a system crash.  Also,
  125. stay away from distributed computing projects where an incorrect calculation
  126. might cause you to return wrong results.  Bad data will not help these
  127. projects! In conclusion, if you are comfortable with a small risk of an
  128. occasional system crash then feel free to live a little dangerously!  Keep in
  129. mind that the faster prime95 finds a hardware error the more likely it is that
  130. other programs will experience problems.
  131.  
  132. The second school of thought is, "Why run a stress test if you are going
  133. to ignore the results?"  These people want a guaranteed 100% rock solid
  134. machine.  Passing these stability tests gives them the ability to run
  135. CPU intensive programs with confidence.
  136.  
  137.  
  138. FREQUENTLY ASKED QUESTIONS
  139. --------------------------
  140.  
  141. Q)  My machine is not overclocked.  If I'm getting an error, then there must
  142. be a bug in the program, right?
  143.  
  144.         A)  The torture test is comparing your machines results against
  145.         KNOWN CORRECT RESULTS.  If your machine cannot generate correct
  146.         results, you have a hardware problem.  HOWEVER, if you are failing
  147.         the torture test in the SAME SPOT with the SAME ERROR MESSAGE
  148.         every time, then ask for help at http://mersenneforum.org - it is
  149.         possible that a recent change to the torture test code may have
  150.         introduced a software bug.
  151.  
  152. Q)  How long should I run the torture test?
  153.  
  154.         A)  I recommend running it for somewhere between 6 and 24 hours.
  155.         The program has been known to fail only after several hours and in
  156.         some cases several weeks of operation.  In most cases though, it will
  157.         fail within a few minutes on a flaky machine. When overclocking it is
  158.         entirely feasible to run short 10-15min tests at each increase in
  159.         clock speed to quickly assess the feasibility of running at those
  160.         speeds, then run longer tests later.
  161.  
  162. Q)  Prime95 reports errors during the torture test, but other stability
  163. tests don't.  Do I have a problem?
  164.  
  165.         A)  Stability tests are not equal in their ability to detect problems.
  166.         Some don't apply a heavy enough load for their results to be reliable,
  167.         while others apply loads so heavy that only extremely edge-case
  168.         real-world workloads would compare.  There also may be significant
  169.         differences between stress tests regarding the CPU features they make
  170.         use of, so specific tests that don't make use of them may not be valid
  171.         for specific use cases where those features are required (e.g. AVX
  172.         instructions, virtualization technologies).
  173.  
  174. Q)  A forum member said "Don't bother with prime95, it always pukes on me,
  175. and my system is stable!.  What do you make of that?"
  176.  
  177.         or
  178.  
  179. "We had a server at work that ran for 2 MONTHS straight, without a reboot
  180. I installed Prime95 on it and ran it - a couple minutes later I get an error.
  181. You are going to tell me that the server wasn't stable?"
  182.  
  183.         A)  If a system can be easily crashed or made to generate incorrect
  184.         results to mathematical functions simply by running a program on it,
  185.         it is impossible to argue that it is reliable.  The consequences of
  186.         that unreliability are up to the user to be aware of, but many faults
  187.         go unnoticed for a long time.  Glitches in games may be assumed to be
  188.         bugs in the programming.  Vital data in long term storage may already
  189.         have been corrupted without anyone knowing about it.  The question to
  190.         ask yourself is whether or not the responsibilities of that system are
  191.         unimportant enough to make continuing without remedial action worth
  192.         the risk.

Quellcode

Hier kannst du den Code kopieren und ihn in deinen bevorzugten Editor einfügen. Alternativ kannst du den gesamten Eintrag auch als Datei herunterladen.