IRQL_NOT_LESS_OR_EQUAL blue screen

just an info text:

stress.txt

            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.

so weird, it says "CPU speed: 2008.53 MHz, 2 cores" tho i got 2x 3.2 ghz :x.. what ever

and this is the results.txt:

[Wed Nov 17 11:27:52 2010]

FATAL ERROR: Rounding was 0.5, expected less than 0.4

Hardware failure detected, consult stress.txt file.

[Wed Nov 17 11:40:34 2010]

FATAL ERROR: Rounding was 0.5, expected less than 0.4

Hardware failure detected, consult stress.txt file.

[Wed Nov 17 12:48:13 2010]

FATAL ERROR: Rounding was 0.484375, expected less than 0.4

Hardware failure detected, consult stress.txt file.

[Wed Nov 17 12:58:26 2010]

FATAL ERROR: Rounding was 0.5, expected less than 0.4

Hardware failure detected, consult stress.txt file.

[Wed Nov 17 13:11:40 2010]

Compare your results to other computers at http://www.mersenne.org/report\_benchmarks

AMD Athlon(tm) 64 X2 Dual Core Processor 6400+

CPU speed: 2008.53 MHz, 2 cores

CPU features: RDTSC, CMOV, Prefetch, 3DNow!, MMX, SSE, SSE2

L1 cache size: 64 KB

L2 cache size: 1 MB

L1 cache line size: 64 bytes

L2 cache line size: 64 bytes

L1 TLBS: 32

L2 TLBS: 512

Prime95 32-bit version 25.11, RdtscTiming=1

Best time for 768K FFT length: 22.763 ms.

Best time for 896K FFT length: 27.715 ms.

Best time for 1024K FFT length: 30.528 ms.

Best time for 1280K FFT length: 39.060 ms.

Best time for 1536K FFT length: 47.437 ms.

Best time for 1792K FFT length: 57.957 ms.

Best time for 2048K FFT length: 64.460 ms.

Best time for 2560K FFT length: 84.581 ms.

Best time for 3072K FFT length: 102.820 ms.

Best time for 3584K FFT length: 124.531 ms.

Best time for 4096K FFT length: 138.985 ms.

Best time for 5120K FFT length: 181.216 ms.

Best time for 6144K FFT length: 219.542 ms.

Best time for 7168K FFT length: 268.728 ms.

Best time for 8192K FFT length: 307.348 ms.

Timing FFTs using 2 threads.

Best time for 768K FFT length: 14.370 ms.

Best time for 896K FFT length: 17.462 ms.

Best time for 1024K FFT length: 19.486 ms.

Best time for 1280K FFT length: 26.516 ms.

Best time for 1536K FFT length: 31.095 ms.

Best time for 1792K FFT length: 37.856 ms.

Best time for 2048K FFT length: 42.228 ms.

Best time for 2560K FFT length: 56.382 ms.

Best time for 3072K FFT length: 67.398 ms.

Best time for 3584K FFT length: 81.496 ms.

Best time for 4096K FFT length: 89.862 ms.

Best time for 5120K FFT length: 100.129 ms.

Best time for 6144K FFT length: 124.414 ms.

Best time for 7168K FFT length: 160.960 ms.

Best time for 8192K FFT length: 210.139 ms.

Best time for 58 bit trial factors: 3.716 ms.

Best time for 59 bit trial factors: 3.718 ms.

Best time for 60 bit trial factors: 3.716 ms.

Best time for 61 bit trial factors: 3.710 ms.

Best time for 62 bit trial factors: 3.714 ms.

Best time for 63 bit trial factors: 6.793 ms.

Best time for 64 bit trial factors: 6.789 ms.

Best time for 65 bit trial factors: 8.604 ms.

Best time for 66 bit trial factors: 8.568 ms.

Best time for 67 bit trial factors: 8.553 ms.

FATAL ERROR: Rounding was 0.5, expected less than 0.4

Hardware failure detected, consult stress.txt file.

[Wed Nov 17 13:24:52 2010]

FATAL ERROR: Rounding was 0.5, expected less than 0.4

Hardware failure detected, consult stress.txt file.

[Wed Nov 17 17:10:54 2010]

FATAL ERROR: Rounding was 0.4921875, expected less than 0.4

Hardware failure detected, consult stress.txt file.

[Wed Nov 17 17:20:05 2010]

FATAL ERROR: Rounding was 0.5, expected less than 0.4

Hardware failure detected, consult stress.txt file.

[Thu Nov 18 10:49:44 2010]

FATAL ERROR: Rounding was 0.484375, expected less than 0.4

Hardware failure detected, consult stress.txt file.

Looks like your Athlon(tm) 64 X2 Dual Core Processor 6400+ is damaged. How hot is the CPU?

---

"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Looks like your Athlon(tm) 64 X2 Dual Core Processor 6400+ is damaged. How hot is the CPU?

---

"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Prozessor AMD Athlon 64 X2 :    Sensor DTS

Core 1 :    57 °C

Core 2 :    58 °C

 :   

ATI Radeon HD 3800 Series :    ATI Catalyst Driver

GPU Temperatur :    61 °C

GPU Temperatur (Diode) :    61 °C

GPU Lüfter :    13.0%

 :   

Hard Disk Monitoring :    S.M.A.R.T

Festplatte WDC WD3200AAKS-75L9A0 :    32 °C

Festplatte SAMSUNG HD321KJ :    25 °C