Hi!

I have problems with my QX6700 and the Revs. 2.2A & B.
With Rev. 1.41 and 2.2 I didn't had this problems...

I use WinXP Home.
And Boinc V5.3.12.tx36

After ~11h Boinc is frozen. (I had two times this problem after this time!)
The icon is in the "Task border"/"Info. range" shown.
But when I want to click with "right-Mouse" nothing is happen.

In the Task-Manager:
S@H is not running.
boinc.exe use 25% of the whole CPU.
(this mean that 1 complete thread is 100% in use and the 3 other threads are in idle (Quad Core! :-) )

The only thing what I can do is to reboot the system.
Then two messages are shown:

----------------------------------
Close program: boincmgr.exe
The program don't react
(Finish now) (Abort)
----------------------------------

----------------------------------
Close program: boinc.exe
The program don't react
(Finish now) (Abort)
----------------------------------

Have other people the same probs?

What is going wrong?

THANX !

---

My C2Q is remaining with 2.2 Chicken Soup, and has not, to my knowledge, produced any of the errors that 2.2A and B were coded to resolve.

I recommend that if these problems persist, then you revert to the 2.2 version!

---

It's good to be back amongst friends and colleagues

Hi Capt,

No problems here, the new app is running smoothly in both my rigs (P4 and PD) and I'm planning to install it in my dad's machine. Since you're using a customized BOINC client, and Windows is having problems with both of their main components (the Mgr and the daemon), have you tried running the standard version (5.8.11)? Or maybe reinstall your BOINC client. Maybe it got corrupted somehow. Just a though.

Regards,
Wander

---

My C2Q is remaining with 2.2 Chicken Soup, and has not, to my knowledge, produced any of the errors that 2.2A and B were coded to resolve.

I recommend that if these problems persist, then you revert to the 2.2 version!

OTOH, my clovertowns (with BOINC 5.8.15) have not had any problem with 2.2B, so I'm not entirely sure this is the root cause of the problem.

I've also got 2.2B running with 5.3.12tx36 on three single-core machines, again without problems.

Thanx for the replies!

Now I got the prob after ~3h... :-(

Now I went back to Rev. 1.41... :-(

O.K., with Rev. 1.41 I get sometimes invalid results (and it's little bit slower) , but not so often like with Rev. 2.0...

Now I'm little bit confused...


I have probs now with my new QX6700...? But he isn't OC!



BTW. I have the QX6700 on an Intel D975XBX2 Motherboard.
With the Intel program I can see only the negative temp. to the max. (death) temp...
(I see for example -22°C (-7.6°F) (it's the "normal" temp. under full load) , when it'll be less (more) ~ -20°C (~ -4°F) the fan is running faster to cool the CPU to ~ -22°C (~ -7.6°F) back)
Other people with other Motherboards see this like I, or they see the real temp.?
(In BIOS is see only negative temps. too)

How I can see the real temp.?
I used SpeedFan and MotherboardMonitor but it's don't function...

And what is the max. (real) temp. for the CPU "for running good" and at which temp. the CPU is damaged?

---

John Clark:

My C2Q is remaining with 2.2 Chicken Soup, and has not, to my knowledge, produced any of the errors that 2.2A and B were coded to resolve.

I recommend that if these problems persist, then you revert to the 2.2 version!

Your result 480062023 shows:

Spikes Pulses Triplets Gaussians Flops
17 - - - 2 - - - 0 - - - - 2 - - - - 12977558867117

</stderr_txt>
]]>
Validate state Invalid
Claimed credit 50.3180812556047
Granted credit 0

I recommend you upgrade to 2.2B!

Even a system which didn't have any invalid results because of the bug will have reported some spikes with incorrect time and position, thereby causing only "weakly similar" validation. The project is trying to identify the positions of signals which persist, using an application which has an admitted defect in reporting positions is not a good practice.

Note that 2.2A only changed the reporting of CPU features, it has the same bug as the original 2.2. If someone has an insoluble problem with 2.2B I recommend using 2.0.

                                                              Joe

Thanx for the replies!

Now I got the prob after ~3h... :-(

Now I went back to Rev. 1.41... :-(

O.K., with Rev. 1.41 I get sometimes invalid results (and it's little bit slower) , but not so often like with Rev. 2.0...

Now I'm little bit confused...


I have probs now with my new QX6700...? But he isn't OC!



BTW. I have the QX6700 on an Intel D975XBX2 Motherboard.
With the Intel program I can see only the negative temp. to the max. (death) temp...
(I see for example -22°C (-7.6°F) (it's the "normal" temp. under full load) , when it'll be less (more) ~ -20°C (~ -4°F) the fan is running faster to cool the CPU to ~ -22°C (~ -7.6°F) back)
Other people with other Motherboards see this like I, or they see the real temp.?
(In BIOS is see only negative temps. too)

How I can see the real temp.?
I used SpeedFan and MotherboardMonitor but it's don't function...

And what is the max. (real) temp. for the CPU "for running good" and at which temp. the CPU is damaged?

------------------------------------------------------------------
Little error:

O.K., with Rev. 1.41 I get sometimes invalid results (and it's little bit slower) , but not so often like with Rev. 2.2...
------------------------------------------------------------------




Can anybody explain where my problem is?

---

I have probs now with my new QX6700...? But he isn't OC!



BTW. I have the QX6700 on an Intel D975XBX2 Motherboard.
With the Intel program I can see only the negative temp. to the max. (death) temp...
(I see for example -22°C (-7.6°F) (it's the "normal" temp. under full load) , when it'll be less (more) ~ -20°C (~ -4°F) the fan is running faster to cool the CPU to ~ -22°C (~ -7.6°F) back)
Other people with other Motherboards see this like I, or they see the real temp.?
(In BIOS is see only negative temps. too)

How I can see the real temp.?
I used SpeedFan and MotherboardMonitor but it's don't function...

And what is the max. (real) temp. for the CPU "for running good" and at which temp. the CPU is damaged?

You need to update your BIOS to fix the temps. You could also use CoreTemp or Everest to monitor your temps. Temps under load shouldn't be higher than 60C (should be around 50C-55C). CPU shuts off at 85C.

---

Probs with Simons S@H V5.15 Rev.2.2A and B

system (BOINC) shuts down all by itself - can't connect etc . . . disgardin' all now . .. goin' back to 5.8.11 simple . . .

John Clark:

My C2Q is remaining with 2.2 Chicken Soup, and has not, to my knowledge, produced any of the errors that 2.2A and B were coded to resolve.

I recommend that if these problems persist, then you revert to the 2.2 version!

Your result 480062023 shows:

Spikes Pulses Triplets Gaussians Flops
17 - - - 2 - - - 0 - - - - 2 - - - - 12977558867117

</stderr_txt>
]]>
Validate state Invalid
Claimed credit 50.3180812556047
Granted credit 0

I recommend you upgrade to 2.2B!

Even a system which didn't have any invalid results because of the bug will have reported some spikes with incorrect time and position, thereby causing only "weakly similar" validation. The project is trying to identify the positions of signals which persist, using an application which has an admitted defect in reporting positions is not a good practice.

Note that 2.2A only changed the reporting of CPU features, it has the same bug as the original 2.2. If someone has an insoluble problem with 2.2B I recommend using 2.0.

                                                              Joe

That may be due to me trying to install VR software, which will not complete the setup routine. I used the restore feature a considerable number of times over the last several days.

I need convincing that I get more than 1 invalid result before I move to 2.2B.

This week end I was particularly heavy with this install, or lack of it, using many approaches.

---

It's good to be back amongst friends and colleagues

Probs with Simons S@H V5.15 Rev.2.2A and B

system (BOINC) shuts down all by itself - can't connect etc . . . disgardin' all now . .. goin' back to 5.8.11 simple . . .

< everythings fine after NEW INSTALL of v5.8.15

That may be due to me trying to install VR software, which will not complete the setup routine. I used the restore feature a considerable number of times over the last several days.

I need convincing that I get more than 1 invalid result before I move to 2.2B.

This week end I was particularly heavy with this install, or lack of it, using many approaches.

You missed the point, it's not whether you get invalidated results or not, 2.2 and 2.2A have the potential to compromise the science, due to misreporting certain result output data. That's why he was suggesting to not use them.

That may be due to me trying to install VR software, which will not complete the setup routine. I used the restore feature a considerable number of times over the last several days.

I need convincing that I get more than 1 invalid result before I move to 2.2B.

This week end I was particularly heavy with this install, or lack of it, using many approaches.

You missed the point, it's not whether you get invalidated results or not, 2.2 and 2.2A have the potential to compromise the science, due to misreporting certain result output data. That's why he was suggesting to not use them.

I've heard of 2.2 and I'm using 2.2B, But 2.2A? When did that get out?
In any case I only had an error 5 with 2.2B and I have no idea what 5 is? Does anybody? And yes I googled It too.

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

I hadn't noticed A either, but according to Joe's post here it changed the CPU feature reporting.

Alinator

I have probs now with my new QX6700...? But he isn't OC!



BTW. I have the QX6700 on an Intel D975XBX2 Motherboard.
With the Intel program I can see only the negative temp. to the max. (death) temp...
(I see for example -22°C (-7.6°F) (it's the "normal" temp. under full load) , when it'll be less (more) ~ -20°C (~ -4°F) the fan is running faster to cool the CPU to ~ -22°C (~ -7.6°F) back)
Other people with other Motherboards see this like I, or they see the real temp.?
(In BIOS is see only negative temps. too)

How I can see the real temp.?
I used SpeedFan and MotherboardMonitor but it's don't function...

And what is the max. (real) temp. for the CPU "for running good" and at which temp. the CPU is damaged?

You need to update your BIOS to fix the temps. You could also use CoreTemp or Everest to monitor your temps. Temps under load shouldn't be higher than 60C (should be around 50C-55C). CPU shuts off at 85C.

You mean the CoreTemp program from here? :

http://www.alcpu.com/CoreTemp


Now I had done the BIOS Update and the only changing is that the "-" is away... ;-)
I don't see the real temp.!
I see only the whole CPU- temp. (processor thermal margin) (idle= around 40°C, full load= 22°C)(when the temp. rise more (less) the fan run faster to cool the CPU to 22°C back) and not the 4 temps from the Cores.
(with the Intel Desktop Utilities)
So the Intel Deskotp Utilities show me the temp to the "death"?

When I use AIDA, FanSpeed (nothing) and EVEREST I see only the temp. from the HDD and from graphic card.

I used the CoreTemp Beta V0.94 and saw the temp from the 4 Cores vary from 71°C (159.8°F) to 79°C (174.2°F) under full load (room 22.2°C (71.6°F))

This program is made special for the Dual and Quad Core CPUs and the alarm is at 100°C.
This is correct that the "death" temp. is at 100°C (212°F) ?
It's good to know, because in the future maybe I'll OC a little... ;-)

What see other users of the QX6700: the real temp. or the "temperature stretches"?




...people, please don't forget my "main" problem ;-) :

I have problems with my QX6700 and the Revs. 2.2A & B.
With Rev. 1.41 and 2.2 I didn't had this problems...

I use WinXP Home.
And Boinc V5.3.12.tx36

After ~11h Boinc is frozen. (I had two times this problem after this time!)
The icon is in the "Task border"/"Info. range" shown.
But when I want to click with "right-Mouse" nothing is happen.

In the Task-Manager:
S@H is not running.
boinc.exe use 25% of the whole CPU.
(this mean that 1 complete thread is 100% in use and the 3 other threads are in idle (Quad Core! :-) )

The only thing what I can do is to reboot the system.
Then two messages are shown:

----------------------------------
Close program: boincmgr.exe
The program don't react
(Finish now) (Abort)
----------------------------------

----------------------------------
Close program: boinc.exe
The program don't react
(Finish now) (Abort)
----------------------------------

Have other people the same probs?

What is going wrong?

---

@ Captain Future . . .

Have other people the same probs?

What is going wrong?

something similar - though all got 'corrupted' (or whatever) - i un-installed and re-booted with Install of v5.8.15 . . . seems to be workin' fine so far (fingers crossed) ;) ps - didn't COPY any of the INFO either . . .

You missed the point, it's not whether you get invalidated results or not, 2.2 and 2.2A have the potential to compromise the science, due to misreporting certain result output data. That's why he was suggesting to not use them.

Yes I had. So, I will move to the 2.2B optimised client tomorrow, whe I have time from work.

I am assuming it is OK to leave the 2.2 client on my dual Prescot Xeon, or is the move to 2.2B confirmed for all Intel SSE, SSE2 and SSE3 rigs?

---

It's good to be back amongst friends and colleagues

I'm using the first 2.2 and haven't had any errors or invalid results.

Should i change apps or stay put?

---

I'm using the first 2.2 and haven't had any errors or invalid results.

Should i change apps or stay put?

Like "Josef W. Segur" said (& he must know it, because he is in the team who optimize the apps :-) )

I recommend you upgrade to 2.2B!

Even a system which didn't have any invalid results because of the bug will have reported some spikes with incorrect time and position, thereby causing only "weakly similar" validation. The project is trying to identify the positions of signals which persist, using an application which has an admitted defect in reporting positions is not a good practice.

---

I think I'm the only one who have problems with the Rev.2.2B and the QX6700...

So what have the others on their system and I have not...

I use this PC (QX6700) only for S@H.
I have WinXP Home SP2 on him and didn't make an update from the Microsoft-homepage,
because I think if I don't make "safetyneedy" work... I don't need an update... or?
I have a Firewall and this is all...

Maybe I need "Microsoft .NET Framework"?
The other users used the "Automatic installer - Full package" (because for this it's needed) and that's the reason that they don't have the probs?

Or what need my PC to let run the Rev.2.2B?

HELP PLEASE !!!!!

---