Aangemaakte reacties

15 berichten aan het bekijken - 91 tot 105 (van in totaal 8,865)
  • Auteur
    Berichten
  • In reactie op: [TK] Club3D ATI Radeon 9600 256MB #409732
    nelis44nelis44
    Deelnemer
    15

    sphinx heb je deze kaartn og?

    In reactie op: Blauw scherm #414743
    nelis44nelis44
    Deelnemer
    15

    prime knalt direct uit maargoed mmm kan ik trouwens gewoon stekkers uithalen zonder dat ik erprobs mee krijg?

    In reactie op: Blauw scherm #414741
    nelis44nelis44
    Deelnemer
    15

    rofl ok;)

    In reactie op: Blauw scherm #414739
    nelis44nelis44
    Deelnemer
    15

    mmm men externe hd kank wel ff uit halen wat nog meer .. grafische kaart neem ik aan van niet?

    In reactie op: Blauw scherm #414736
    nelis44nelis44
    Deelnemer
    15

    mm zou dvd rom en brander genoeg zijn om uit te halen?

    In reactie op: Blauw scherm #414733
    nelis44nelis44
    Deelnemer
    15

    mm als ik bij bios bij booten dvd en zo uitschakel krijgt hij dan nog wel stroom?

    In reactie op: Blauw scherm #414731
    nelis44nelis44
    Deelnemer
    15

    mja ma hoe kan ik voeding testen?

    In reactie op: Gevraagd: Geheugen #414706
    nelis44nelis44
    Deelnemer
    15

    hoe duur zijn ze normaal?

    In reactie op: Blauw scherm #414728
    nelis44nelis44
    Deelnemer
    15

    veel blaat:

    STRESS TESTING YOUR COMPUTER

    BACKGROUND


    Today’s computers are not perfect. Even brand new systems from major

    manufacturers can have hidden flaws. If any of several key components such

    as CPU, memory, cooling, etc. are not up to spec, it can lead to incorrect

    calculations and/or unexplained system crashes.

    Overclocking is the practice of increasing the speed of the CPU and/or

    memory to make a machine faster at little cost. Typically, overclocking

    involves pushing a machine past its limits and then backing off just a

    little bit.

    For these reasons, both non-overclockers and overclockers need programs

    that test the stability of their computers. This is done by running

    programs that put a heavy load on the computer. Though not originally

    designed for this purpose, this program is one of a few programs that

    are excellent at stress testing a computer.

    RESOURCES


    This program is a good stress test for the CPU, memory, L1 and L2 caches,

    CPU cooling, and case cooling. The torture test runs continuously, comparing

    your computer’s results to results that are known to be correct. Any

    mismatch and you’ve got a problem! Note that the torture test sometimes

    reads from and writes to disk but cannot be considered a stress test for

    hard drives.

    You’ll need other programs to stress video cards, PCI bus, disk access,

    networking and other important components. In addition, this is only one

    of several good programs that are freely available. Some people report

    finding problems only when running two or more stress test programs

    concurrently. You may need to raise prime95’s priority when running two

    stress test programs so that each gets about 50% of the CPU time.

    Forums are a great place to learn about available stability test programs

    and to get advice on what to do when a problem is found.

    The currently popular stability test programs are (sorry, I don’t have

    web addresses for these):

    Prime95 (this program’s torture test)

    3DMark2001

    CPU Stability test

    Sisoft sandra

    Quake and other games

    Folding@Home

    Seti@home

    Genome@home

    Several useful websites for help (look for overclocking community or forum):

    http://www.overclockers.com

    http://www.arstechnica.com

    http://www.hardocp.com

    http://www.anandtech.com

    http://www.tomshardware.com

    http://www.sharkyextreme.com

    Also try the alt.comp.hardware.overclocking Usenet newsgroup.

    Utility programs you may find useful (I’m sure there are others – look around):

    Motherboard monitor from http://mbm.livewiredev.com

    Memtest86 from http://www.memtest86.com

    Cpuburn by redelm: http://pages.sbcglobal.net/redelm/

    TaskInfo2002 from http://www.iarsn.com/

    WHAT TO DO IF A PROBLEM IS FOUND?


    The exact cause of a hardware problem can be very hard to find.

    If you are not overclocking, the most likely cause is an overheating CPU

    or memory DIMMs that are not quite up to spec. Another possibility is

    you might need a better power supply. Try running MotherBoard monitor

    and browse the forums above to see if your CPU is running too hot.

    If so, make sure the heat sink is properly attached, fans are operational,

    and air flow inside the case is good. For isolating memory problems, try

    swapping memory DIMMs with a co-worker’s or friend’s machine. If the errors

    go away, then you can be fairly confidant that memory was the cause of

    the trouble. A power supply problem can often be identified by a significant

    drop in the voltages when prime95 starts running. Once again the overclocker

    forums are a good resource for what voltages are acceptable.

    If you are overclocking then try increasing the core voltage, reduce the

    CPU speed, reduce the front side bus speed, or change the memory timings

    (CAS latency). Also try asking for help in one of the forums above – they

    may have other ideas to try.

    CAN I IGNORE THE PROBLEM?


    Ignoring the problem is a matter of personal preference. There are

    two schools of thought on this subject.

    Most programs you run will not stress your computer enough to cause a

    wrong result or system crash. If you ignore the problem, then video games

    may stress your machine resulting in a system crash. Also, stay away from

    distributed computing projects where an incorrect calculation might cause

    you to return wrong results. Bad data will not help these projects!

    In conclusion, if you are comfortable with a small risk of an occasional

    system crash then feel free to live a little dangerously! Keep in mind

    that the faster prime95 finds a hardware error the more likely it is that

    other programs will experience problems.

    The second school of thought is, “Why run a stress test if you are going

    to ignore the results?” These people want a guaranteed 100% rock solid

    machine. Passing these stability tests gives them the ability to run

    CPU intensive programs with confidence.

    FREQUENTLY ASKED QUESTIONS


    Q) My machine is not overclocked. If I’m getting an error, then there must

    be a bug in the program, right?

    A) The torture test is comparing your machines results against

    KNOWN CORRECT RESULTS. If your machine cannot generate correct

    results, you have a hardware problem. HOWEVER, if you are failing

    the torture test in the SAME SPOT with the SAME ERROR MESSAGE

    every time, then ask for help at http://mersenneforum.org – it is

    possible that a recent change to the torture test code may have

    introduced a software bug.

    Q) How long should I run the torture test?

    A) I recommend running it for somewhere between 6 and 24 hours.

    The program has been known to fail only after several hours and in

    some cases several weeks of operation. In most cases though, it will

    fail within a few minutes on a flaky machine.

    Q) Prime95 reports errors during the torture test, but other stability

    tests don’t. Do I have a problem?

    A) Yes, you’ve reached the point where your machine has been

    pushed just beyond its limits. Follow the recommendations above

    to make your machine 100% stable or decide to live with a

    machine that could have problems in rare circumstances.

    Q) A forum member said “Don’t bother with prime95, it always pukes on me,

    and my system is stable!. What do you make of that?”

    or

    “We had a server at work that ran for 2 MONTHS straight, without a reboot

    I installed Prime95 on it and ran it – a couple minutes later I get an error.

    You are going to tell me that the server wasn’t stable?”

    A) These users obviously do not subscribe to the 100% rock solid

    school of thought. THEIR MACHINES DO HAVE HARDWARE PROBLEMS.

    But since they are not presently running any programs that reveal

    the hardware problem, the machines are quite stable. As long as

    these machines never run a program that uncovers the hardware problem,

    then the machines will continue to be stable.

    In reactie op: Blauw scherm #414726
    nelis44nelis44
    Deelnemer
    15

    w8 ik stress zelf wel ff tot 100% en post dan ff

    [img]http://img119.imageshack.us/img119/3149/speefan29ar.jpg[/img]

    In reactie op: Blauw scherm #414724
    nelis44nelis44
    Deelnemer
    15

    Intel(R) Pentium(R) 4 CPU 2.40GHz

    CPU speed: 2399.53 MHz

    CPU features: RDTSC, CMOV, Prefetch, MMX, SSE, SSE2

    L1 cache size: 8 KB

    L2 cache size: 512 KB

    L1 cache line size: 64 bytes

    L2 cache line size: 128 bytes

    TLBS: 64

    Prime95 32-bit version 24.13, RdtscTiming=1

    Best time for 512K FFT length: 23.862 ms.

    Best time for 640K FFT length: 31.009 ms.

    [Mon Aug 08 18:37:18 2005]

    FATAL ERROR: Rounding was 0.5, expected less than 0.4

    Hardware failure detected, consult stress.txt file.

    FATAL ERROR: Rounding was 0.5, expected less than 0.4

    Hardware failure detected, consult stress.txt file.

    In reactie op: Blauw scherm #414722
    nelis44nelis44
    Deelnemer
    15

    hek gedaan ma deed ie niet veel

    :|

    In reactie op: Blauw scherm #414720
    nelis44nelis44
    Deelnemer
    15

    mja temps zijn super goed zo maar ja idd scheelt wel 0,7 volt (maar is die wel voor geheugenchip)?

    http://www.mersenne.org/bench.htm

    That web page also contains instructions on how your results can be included.

    Intel(R) Pentium(R) 4 CPU 2.40GHz

    CPU speed: 2399.89 MHz

    CPU features: RDTSC, CMOV, Prefetch, MMX, SSE, SSE2

    L1 cache size: 8 KB

    L2 cache size: 512 KB

    L1 cache line size: 64 bytes

    L2 cache line size: 128 bytes

    TLBS: 64

    Prime95 32-bit version 24.13, RdtscTiming=1

    Best time for 512K FFT length: 23.601 ms.

    Best time for 640K FFT length: 30.945 ms.

    Best time for 768K FFT length: 37.552 ms.

    Best time for 896K FFT length: 43.102 ms.

    Best time for 1024K FFT length: 49.452 ms.

    Best time for 1280K FFT length: 63.796 ms.

    Best time for 1536K FFT length: 81.084 ms.

    Best time for 1792K FFT length: 93.555 ms.

    Best time for 2048K FFT length: 106.147 ms.

    Best time for 2560K FFT length: 138.981 ms.

    Best time for 3072K FFT length: 177.190 ms.

    Best time for 3584K FFT length: 211.743 ms.

    Best time for 4096K FFT length: 232.100 ms.

    Best time for 58 bit trial factors: 12.130 ms.

    Best time for 59 bit trial factors: 12.262 ms.

    Best time for 60 bit trial factors: 12.128 ms.

    Best time for 61 bit trial factors: 12.169 ms.

    Best time for 62 bit trial factors: 13.182 ms.

    Best time for 63 bit trial factors: 13.228 ms.

    Best time for 64 bit trial factors: 16.166 ms.

    Best time for 65 bit trial factors: 16.140 ms.

    In reactie op: Blauw scherm #414717
    nelis44nelis44
    Deelnemer
    15
    In reactie op: Gevraagd: Geheugen #414702
    nelis44nelis44
    Deelnemer
    15

    is het een goed merk dan

15 berichten aan het bekijken - 91 tot 105 (van in totaal 8,865)

Naar boven