After BOINC have run for about 1 - 2 hours I usually get this error: http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/6077.mspx?mfr=true
that results in a "blue screen of death".

What to do?

---

After BOINC have run for about 1 - 2 hours I usually get this error: http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/6077.mspx?mfr=true
that results in a "blue screen of death".

What to do?

What project triggers it?

Just a quick glance at the MS page makes it look like it might be something much lower level than BOINC. Check your drivers.

---

Kathryn :o)

After BOINC have run for about 1 - 2 hours I usually get this error: http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/6077.mspx?mfr=true
that results in a "blue screen of death".

What to do?

What project triggers it?

Just a quick glance at the MS page makes it look like it might be something much lower level than BOINC. Check your drivers.

I got a rash of these when I built a Q9300 onto a cheap mobo recently. The stop error (in Win XP) also listed the file name where the problem ocurred, and in my case it was a NVidia graphics card device driver.

A concentrated session tracking down all the latest drivers, and an updated installation of DirectX 9.0c, seems finally to have reached stability - touch wood.

it is the climateprediction.net who causing it. And I don't think it's a driver because:

1. Now I start getting "PAGE_FAULT_IN_NONPAGED_AREA" too. http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/6093.mspx?mfr=true

2. it only happens when BOINC is running

If it only happens when BOINC is running, then I would suspect hardware that has problems. Defective RAM comes to mind, as does a CPU that doesn't run quite as it should, but a hard drive corruption is also a possibility.

A faulty driver somewhere on your system may be the cause of the Interrupt layer error you got first, while it could be faulty because it is read wrong, on a corrupted partition on the HDD or loses information when loaded into the RAM. A faulty motherboard could also give these errors.

Check in Event Viewer what is causing these errors.

---

I can't find anything in the eventlog about just that time. Just a lot of DCOM errors at the wrong times.

I knowed it happened 30/4 at around 5 pm.

But I can't find anything with a STOP message or anything

Try running a stress test - I personally like 24 hours of Prime95's torture test (one copy per core using the -A flag).

Take a look at the 'hardware' section of the following post:
http://www.climateprediction.net/board/viewtopic.php?t=5896


If the stress-test passes OK, then it indicates that the issue might be with the drivers, O/S, disk or malware, whereas if it fails it indicates it might be with cpu, ram, cooling, motherboard or PSU.

---

If the stress-test passes OK, then it indicates that the issue might be with the drivers, O/S, disk or malware, whereas if it fails it indicates it might be with cpu, ram, cooling, motherboard or PSU.

BOINC is a stress-test by itself... :D

---

If the stress-test passes OK, then it indicates that the issue might be with the drivers, O/S, disk or malware, whereas if it fails it indicates it might be with cpu, ram, cooling, motherboard or PSU.

BOINC is a stress-test by itself... :D

Especially CPDN :-)

---

Kathryn :o)

After 1 hour and 3 min it returns: FATAL ERROR: Rounding was 0.5, expected less than 0.4. Does that mean The RAM is faulty or what?

Run one of the Memtest programs for 24 hours and find out.

Run one of the Memtest programs for 24 hours and find out.

Well I did but after 1 hour it ran into a fatal error and it stops after fatal errors

Sounds like your PC has hardware problems.

Is it within guarantee?

If not...

* Open it up and make sure that all the fans are running, and that there is no dust on the system

* Try swapping out individual sticks of RAM to see if the problem is specific to one stick of RAM.

* If you have a spare CPU, try swapping it

* Try reducing overclock (if you have overclocked it). Similarly, relax memory timings (if you had tightened them up previously).



Does memtest86+ have an option to keep running after errors?

---

Does memtest86+ have an option to keep running after errors?

Last time I ran MemTest, it continued to run even when it found errors. Granted, it's been over a year since I did it last...

I wonder if the OP was taking about Prime95 stopping. I can't speak for that because I've never used it.

---

Kathryn :o)

Run one of the Memtest programs for 24 hours and find out.

Well I did but after 1 hour it ran into a fatal error and it stops after fatal errors

Did you run this one?

MemTest86+

---

Kathryn :o)

Sounds like your PC has hardware problems.

Is it within guarantee?

If not...

* Open it up and make sure that all the fans are running, and that there is no dust on the system

* Try swapping out individual sticks of RAM to see if the problem is specific to one stick of RAM.

* If you have a spare CPU, try swapping it

* Try reducing overclock (if you have overclocked it). Similarly, relax memory timings (if you had tightened them up previously).



Does memtest86+ have an option to keep running after errors?

It is in guarantee yet I think. I gonna reinstall my comp this today to make sure it isn't something like that. When the problem started I called them and they said I should reinstall windows but I haven't had time yet but now I have.

And I ran prime95 but if the things keeps happening after the reinstall I run the other one and call the support.

Ok I reinstalled the comp now and now it fails after just 1 min so I gonna test the other one too.

I really would have liked to help with the SETI project but I too am having problems with computer lock-ups/hangs that have only started occuring since installing the BOINC software.
I have been running the program for about five hours and in that time my machine has locked up solid three times.
I am sure it is not a hardware problem as I do run many other processor intensive applications with no problems at all so it would be nice if the "experts" could offer some other advice than "you must have a crap computer because our software is perfect".

I am sure it is not a hardware problem as I do run many other processor intensive applications with no problems at all so it would be nice if the "experts" could offer some other advice than "you must have a crap computer because our software is perfect".

Not saying the software is perfect, not saying your hardware is perfect either. IRQL_NOT_EQUAL_OR_LESS means primarily that you have a drivers problem, but it can also point to some flaky RAM. Have you dusted out the system anytime lately? It could also be due to heat

Can you tell me the full error message that you get? Look in Event Viewer or Dr Watson for clues.
Can you tell me on what system? Which BOINC version? Which Windows version?

---