Update on "Question on ASUS A7N8X Deluxe motherboard and compatible processor "

On Sep 8, 11:01 am, Paul <nos...@needed.com> wrote:
> amanda...@gmail.com wrote:
> > On Sep 7, 10:23 am, Paul <nos...@needed.com> wrote:
> >> amanda...@gmail.com wrote:
> > [ ]
> >> Rather than messing around, I have a second alternative. Uninstall Prime95.
> >> Download Orthos here, and try it. It has an easy Start button in the upper
> >> right of the dialog. It also incorporates some MBM code, and will print the CPU
> >> temperature into the log area of the window (once a minute). If it
> >> starts beeping and flashing red, it has detected an error, so the CPU
> >> is not stable. (I just tried it, and my machine is acting up. Looks like
> >> I have some testing to do...)
>
> >>http://sp2004.fre3.com/beta/beta2.htm
>
> >> Paul
>
> > I just started testing with Ortho. Mine is flashing too though not
> > continuously. But no sound. So I checked the volume and it was mute;
> > so I un-mute it but still no sound. I'll wait to hear from you what
> > to do next.
>
> Orthos does two things for you. It should make the CPU get hot. If you are
> having problems with a CPU overheating and shutting off, a program like
> Orthos proves whether or not your computer has enough cooling or not.
>
> When you run Orthos, you should see "GO" in the display. The log area
> in the bottom of the screen, will show the same progress messages as
> you'd get with Prime95. If your processor has more than one core,
> Orthos will run more than one copy of Prime95.

I see all that.

>
> The second thing Orthos does for you, is determine whether your CPU
> and memory work error free or not. If a computing error is detected,
> you'll see "STOPPED" in the upper part of the screen, "FATAL ERROR"
> and details in the lower part of the screen, and the "computer case
> speaker" will beep once every six seconds or so. The "Scroll Lock"
> LED on my keyboard is also flashing.

Earlier today, I had it run for some time. After I clicked "Start", at
first, I saw the word "PAGING" in red background. At about 1 min, the
red went away and saw "0". Then it continue to happen like that for
some, i.e red backgroung with the word "PAGING" and "0" in clear
background alternating. No sound at all.

I left it run for, say 30-45 mins then stopepd it when I left home at
8:50AM.

I just started again after reading your post, and so far it is doign
the same thing. No sound. I guess it is normal.

How long do I let it run?

It's been 9 mins now and it is showing this in the bottom windew:

Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 767
Time: 15
CPU: 1293MHz FSB: 100MHz [107MHz x 12.0 est.]
9/8/2007 3:26 PM
Launching 1 thread...
Using CPU #0
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT
length.

>
> Clicking Exit will stop all that.
>
> Orthos also contains a copy of MBM (Motherboard Monitor), a program
> which is no longer supported by its author. MBM accesses the hardware
> monitor chip and reads temperatures from the chip. As long as MBM can
> figure out what kind of motherboard is involved, the readout should
> be as accurate as running MBM version 5 by itself.

> For example, just
> before I got a FATAL ERROR by starting Orthos, my CPU was reading
> about 46C, which is not very hot. (The temperature is printed into the
> log window, if MBM can figure out the motherboard type.)

I ddidn't and don't see the tme information in the log window

> If I turn the frequency of my CPU down just a little bit, Orthos will stay in the
> "GO" state.

>

How do you do that?

> So while I don't have an overheat problem, it appears my
> overclock is a little too aggressive.

> The input clock to my CPU is 230MHz,
> and if I turn it down to 225MHz (via ClockGen, while I'm sitting in Windows),
> that is enough to make it stable again. The normal input clock is 200MHz.

How do you turn down the input clock to the CPU?

>
> Paul

>- Hide quoted text -
>
> - Show quoted text -

wrote:
> On Sep 8, 11:01 am, Paul <nos...@needed.com> wrote:
>> amanda...@gmail.com wrote:
>>> On Sep 7, 10:23 am, Paul <nos...@needed.com> wrote:
>>>> amanda...@gmail.com wrote:
>>> [ ]
>>>> Rather than messing around, I have a second alternative. Uninstall Prime95.
>>>> Download Orthos here, and try it. It has an easy Start button in the upper
>>>> right of the dialog. It also incorporates some MBM code, and will print the CPU
>>>> temperature into the log area of the window (once a minute). If it
>>>> starts beeping and flashing red, it has detected an error, so the CPU
>>>> is not stable. (I just tried it, and my machine is acting up. Looks like
>>>> I have some testing to do...)
>>>> http://sp2004.fre3.com/beta/beta2.htm
>>>> Paul
>>> I just started testing with Ortho. Mine is flashing too though not
>>> continuously. But no sound. So I checked the volume and it was mute;
>>> so I un-mute it but still no sound. I'll wait to hear from you what
>>> to do next.
>> Orthos does two things for you. It should make the CPU get hot. If you are
>> having problems with a CPU overheating and shutting off, a program like
>> Orthos proves whether or not your computer has enough cooling or not.
>>
>> When you run Orthos, you should see "GO" in the display. The log area
>> in the bottom of the screen, will show the same progress messages as
>> you'd get with Prime95. If your processor has more than one core,
>> Orthos will run more than one copy of Prime95.
>
> I see all that.
>
>> The second thing Orthos does for you, is determine whether your CPU
>> and memory work error free or not. If a computing error is detected,
>> you'll see "STOPPED" in the upper part of the screen, "FATAL ERROR"
>> and details in the lower part of the screen, and the "computer case
>> speaker" will beep once every six seconds or so. The "Scroll Lock"
>> LED on my keyboard is also flashing.
>
> Earlier today, I had it run for some time. After I clicked "Start", at
> first, I saw the word "PAGING" in red background. At about 1 min, the
> red went away and saw "0". Then it continue to happen like that for
> some, i.e red backgroung with the word "PAGING" and "0" in clear
> background alternating. No sound at all.
>
> I left it run for, say 30-45 mins then stopepd it when I left home at
> 8:50AM.
>
> I just started again after reading your post, and so far it is doign
> the same thing. No sound. I guess it is normal.
>
> How long do I let it run?
>
> It's been 9 mins now and it is showing this in the bottom windew:
>
> Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 767
> Time: 15
> CPU: 1293MHz FSB: 100MHz [107MHz x 12.0 est.]
> 9/8/2007 3:26 PM
> Launching 1 thread...
> Using CPU #0
> Beginning a continuous self-test to check your computer.
> Press Stop to end this test.
> Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT
> length.
>
>> Clicking Exit will stop all that.
>>
>> Orthos also contains a copy of MBM (Motherboard Monitor), a program
>> which is no longer supported by its author. MBM accesses the hardware
>> monitor chip and reads temperatures from the chip. As long as MBM can
>> figure out what kind of motherboard is involved, the readout should
>> be as accurate as running MBM version 5 by itself.
>
>> For example, just
>> before I got a FATAL ERROR by starting Orthos, my CPU was reading
>> about 46C, which is not very hot. (The temperature is printed into the
>> log window, if MBM can figure out the motherboard type.)
>
> I ddidn't and don't see the tme information in the log window
>
>> If I turn the frequency of my CPU down just a little bit, Orthos will stay in the
>> "GO" state.
>
>
> How do you do that?
>
>> So while I don't have an overheat problem, it appears my
>> overclock is a little too aggressive.
>
>> The input clock to my CPU is 230MHz,
>> and if I turn it down to 225MHz (via ClockGen, while I'm sitting in Windows),
>> that is enough to make it stable again. The normal input clock is 200MHz.
>
> How do you turn down the input clock to the CPU?
>
>> Paul
>
>> - Hide quoted text -
>>
>> - Show quoted text -
>
>

I wonder if Orthos has a minimum amount of memory it will use ?
When I run the "Blended" test, Task Manager (ctrl-alt-delete) shows
Otthos using 750MB. When I switch to the "Small FFT" test, memory
usage is around 5MB or so.

OK, in the "Test" pulldown, select "Small FFTs - Stress CPU", and
while that won't do as good a job testing the system memory, it
will still make the CPU hot. Then click the "Start" button.

The temperature readout will only work, if the Motherboard Monitor
DLL can figure out what kind of motherboard it is. If running the standalone
MBM5 program doesn't work on the computer, then I wouldn't expect to see
temperature readings printed in the Orthos log window. An alternative
would be to use Speedfan from almico.com , as a standalone temperature
readout. Speedfan has the neat feature, that it can read disk drive temperature
(but only for disk drives that have a sensor inside, and only if the
disk drive is connected to a storage interface, where the SMART information
can be extracted).

The Clockgen program is from cpuid.com , the same site that supplies the
CPUZ program. Clockgen only knows about a limited number of PLL types,
and I'm lucky in that my ICS952607 happens to be supported. (This is one
of the benefits of buying the same board as is popular with the overclockers.)
For some of the Nvidia chipsets, the clock generator function is in the
chipset, and as a result, any motherboard using certain of the Nvidia
chipsets, gets supported as well.

There are perhaps, thousands of clock generator chips. The supported ones
are only a handful, and are listed on the left hand column of this web
page:

http://www.cpuid.com/clockgen.php

This web page gives a list of the clock generators made by one company.
ICS Technology was bought by IDT, and so I use an archived listing when I
need to look one of these up.

http://web.archive.org/web/200604260....icst.com/pdf/

Paul

On Sep 8, 5:21 pm, Paul <nos...@needed.com> wrote:
> amanda...@gmail.com wrote:
> > On Sep 8, 11:01 am, Paul <nos...@needed.com> wrote:
> >> amanda...@gmail.com wrote:
> >>> On Sep 7, 10:23 am, Paul <nos...@needed.com> wrote:
> >>>> amanda...@gmail.com wrote:
> >>> [ ]
> >>>> Rather than messing around, I have a second alternative. Uninstall Prime95.
> >>>> Download Orthos here, and try it. It has an easy Start button in the upper
> >>>> right of the dialog. It also incorporates some MBM code, and will print the CPU
> >>>> temperature into the log area of the window (once a minute). If it
> >>>> starts beeping and flashing red, it has detected an error, so the CPU
> >>>> is not stable. (I just tried it, and my machine is acting up. Looks like
> >>>> I have some testing to do...)
> >>>>http://sp2004.fre3.com/beta/beta2.htm
> >>>> Paul
> >>> I just started testing with Ortho. Mine is flashing too though not
> >>> continuously. But no sound. So I checked the volume and it was mute;
> >>> so I un-mute it but still no sound. I'll wait to hear from you what
> >>> to do next.
> >> Orthos does two things for you. It should make the CPU get hot. If you are
> >> having problems with a CPU overheating and shutting off, a program like
> >> Orthos proves whether or not your computer has enough cooling or not.
>
> >> When you run Orthos, you should see "GO" in the display. The log area
> >> in the bottom of the screen, will show the same progress messages as
> >> you'd get with Prime95. If your processor has more than one core,
> >> Orthos will run more than one copy of Prime95.
>
> > I see all that.
>
> >> The second thing Orthos does for you, is determine whether your CPU
> >> and memory work error free or not. If a computing error is detected,
> >> you'll see "STOPPED" in the upper part of the screen, "FATAL ERROR"
> >> and details in the lower part of the screen, and the "computer case
> >> speaker" will beep once every six seconds or so. The "Scroll Lock"
> >> LED on my keyboard is also flashing.
>
> > Earlier today, I had it run for some time. After I clicked "Start", at
> > first, I saw the word "PAGING" in red background. At about 1 min, the
> > red went away and saw "0". Then it continue to happen like that for
> > some, i.e red backgroung with the word "PAGING" and "0" in clear
> > background alternating. No sound at all.
>
> > I left it run for, say 30-45 mins then stopepd it when I left home at
> > 8:50AM.
>
> > I just started again after reading your post, and so far it is doign
> > the same thing. No sound. I guess it is normal.
>
> > How long do I let it run?
>
> > It's been 9 mins now and it is showing this in the bottom windew:
>
> > Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 767
> > Time: 15
> > CPU: 1293MHz FSB: 100MHz [107MHz x 12.0 est.]
> > 9/8/2007 3:26 PM
> > Launching 1 thread...
> > Using CPU #0
> > Beginning a continuous self-test to check your computer.
> > Press Stop to end this test.
> > Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT
> > length.
>
> >> Clicking Exit will stop all that.
>
> >> Orthos also contains a copy of MBM (Motherboard Monitor), a program
> >> which is no longer supported by its author. MBM accesses the hardware
> >> monitor chip and reads temperatures from the chip. As long as MBM can
> >> figure out what kind of motherboard is involved, the readout should
> >> be as accurate as running MBM version 5 by itself.
>
> >> For example, just
> >> before I got a FATAL ERROR by starting Orthos, my CPU was reading
> >> about 46C, which is not very hot. (The temperature is printed into the
> >> log window, if MBM can figure out the motherboard type.)
>
> > I ddidn't and don't see the tme information in the log window
>
> >> If I turn the frequency of my CPU down just a little bit, Orthos will stay in the
> >> "GO" state.
>
> > How do you do that?
>
> >> So while I don't have an overheat problem, it appears my
> >> overclock is a little too aggressive.
>
> >> The input clock to my CPU is 230MHz,
> >> and if I turn it down to 225MHz (via ClockGen, while I'm sitting in Windows),
> >> that is enough to make it stable again. The normal input clock is 200MHz.
>
> > How do you turn down the input clock to the CPU?
>
> >> Paul
>
> >> - Hide quoted text -
>
> >> - Show quoted text -
>
> I wonder if Orthos has a minimum amount of memory it will use ?
> When I run the "Blended" test, Task Manager (ctrl-alt-delete) shows
> Otthos using 750MB. When I switch to the "Small FFT" test, memory
> usage is around 5MB or so.
>
> OK, in the "Test" pulldown, select "Small FFTs - Stress CPU", and
> while that won't do as good a job testing the system memory, it
> will still make the CPU hot. Then click the "Start" button.

Okay. I am strarting that now. Earlier, it wa stestign CPU and Memory,
obviously the default setting. I went out and was left it for 2 hr and
50 mins. I didn't see red backgroudn with the word "PAGING" when I
came back.

>
> The temperature readout will only work, if the Motherboard Monitor
> DLL can figure out what kind of motherboard it is.

I see.

> If running the standalone MBM5 program doesn't work on the computer, then I wouldn't expect to see
> temperature readings printed in the Orthos log window.

> Got it.

>An alternative would be to use Speedfan from almico.com , as a standalone temperature
> readout. Speedfan has the neat feature, that it can read disk drive temperature
> (but only for disk drives that have a sensor inside, and only if the
> disk drive is connected to a storage interface, where the SMART information
> can be extracted).

When you say disk drive, what does it refer to? Hard drive? If so, I
don't beleive the two hard drives I have have sensor. They are regular
5400 RPM drive.

>
> The Clockgen program is from cpuid.com , the same site that supplies the
> CPUZ program. Clockgen only knows about a limited number of PLL types,
> and I'm lucky in that my ICS952607 happens to be supported. (This is one
> of the benefits of buying the same board as is popular with the overclockers.)

> For some of the Nvidia chipsets, the clock generator function is in the
> chipset, and as a result, any motherboard using certain of the Nvidia
> chipsets, gets supported as well.

I see.


>
> There are perhaps, thousands of clock generator chips. The supported ones
> are only a handful, and are listed on the left hand column of this web
> page:
>
> http://www.cpuid.com/clockgen.php

I don't know what mine is.

>
> This web page gives a list of the clock generators made by one company.
> ICS Technology was bought by IDT, and so I use an archived listing when I
> need to look one of these up.
>
> http://web.archive.org/web/200604260....icst.com/pdf/
>
> Paul


This is what Ortho is showing in 12 1//2 min:

Type: Small FFTs - stress CPU Min: 8 Max: 32 InPlace: Yes Mem: 8 Time:
15
CPU: 1293MHz FSB: 100MHz [107MHz x 12.0 est.]
9/8/2007 6:17 PM
Launching 1 thread...
Using CPU #0
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
Test 2, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.

I see "PAGING" on and off; it this nromal?

> Hide quoted text -
>
> - Show quoted text -

amandaF wrote:

>
> This is what Ortho is showing in 12 1//2 min:
>
> Type: Small FFTs - stress CPU Min: 8 Max: 32 InPlace: Yes Mem: 8 Time:
> 15
> CPU: 1293MHz FSB: 100MHz [107MHz x 12.0 est.]
> 9/8/2007 6:17 PM
> Launching 1 thread...
> Using CPU #0
> Beginning a continuous self-test to check your computer.
> Press Stop to end this test.
> Test 1, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
> Test 2, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
>
> I see "PAGING" on and off; it this nromal?
>

This is "Small FFTs" on my P4 3.2GHz with 1GB total memory.
The processor has hyperthreading, so looks like two cores to the program.
That is why there are two "CPU" entries in the log window.
And the word "Paging" does not appear when doing Small FFTs.
Where the "Paging" would go, is the "Rounds 0/0" field, which
keeps track of how many passes of the test have been done.

************************************************** *******
Type: Small FFTs - stress CPU Min: 8 Max: 32 InPlace: Yes Mem: 8 Time: 15
CPU: 3219MHz FSB: 230MHz [229MHz x 14.0 est.]
CPU: 3219MHz FSB: 230MHz [229MHz x 14.0 est.]
Starting MBMStarter.dll...
Started MBMStarter.dll: 1
9/8/2007 11:26 PM 0/0
Temperature: Case: 30.00
Temperature: CPU: 42.00
Temperature: Sensor 3: 26.00 <--- My room temp sensor
====================

Launching 2 threads...
Using CPU #0
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
1 minute
Temperature: CPU: 47.00
====================
3 minutes
Temperature: CPU: 48.00
====================
Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
4 minutes
Temperature: CPU: 47.00
====================
5 minutes
Temperature: CPU: 48.00
====================
7 minutes
Temperature: CPU: 49.00
====================
************************************************** *******

When I select "Blended", the word PAGING appears in a red rectangle,
but does not change or disappear. So the "rounds" counter underneath
it is not visible. And this is what the log looks like:

************************************************** *******
Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 766 Time: 15
CPU: 3219MHz FSB: 230MHz [229MHz x 14.0 est.]
CPU: 3219MHz FSB: 230MHz [229MHz x 14.0 est.]
Starting MBMStarter.dll...
Started MBMStarter.dll: 1
9/8/2007 11:38 PM 0/0
Temperature: Case: 30.00
Temperature: CPU: 44.00
Temperature: Sensor 3: 26.00
====================

Launching 2 threads...
Using CPU #0
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
1 minute
Temperature: CPU: 47.00
************************************************** *******

I suppose it is possible we're using different versions of the program.
The "About" on mine says:

StressPrime 2004 ORTHOS
v0.41.110.18
Copyright 2004-2006
Johnny Lee <email address>

Mersenne Number Tests - Ver 24.14

StressCPU source code
2002 Oct24

HTH,
Paul

On Sep 8, 8:50 pm, Paul <nos...@needed.com> wrote:
> amandaF wrote:
>
> > This is what Ortho is showing in 12 1//2 min:
>
> > Type: Small FFTs - stress CPU Min: 8 Max: 32 InPlace: Yes Mem: 8 Time:
> > 15
> > CPU: 1293MHz FSB: 100MHz [107MHz x 12.0 est.]
> > 9/8/2007 6:17 PM
> > Launching 1 thread...
> > Using CPU #0
> > Beginning a continuous self-test to check your computer.
> > Press Stop to end this test.
> > Test 1, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
> > Test 2, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
>
> > I see "PAGING" on and off; it this nromal?
>
> This is "Small FFTs" on my P4 3.2GHz with 1GB total memory.
> The processor has hyperthreading, so looks like two cores to the program.
> That is why there are two "CPU" entries in the log window.

I see.

> And the word "Paging" does not appear when doing Small FFTs.

Mine does, at the beginning but not when I came back to my PC this
time and checked it but then again just now when I checked though just
once.
BTW, we are using the same version. I checked; I downloaded formt he
link you gave.

> Where the "Paging" would go, is the "Rounds 0/0" field,
Yes, hat's whre it is appearing.

> which keeps track of how many passes of the test have been done.

Mine is at round 1 for this Small FFTs - stress CPU ...

I am pasting what my log window says at the bottown of this post; mine
doesn't show temperature at all.

>
> ************************************************** *******
> Type: Small FFTs - stress CPU Min: 8 Max: 32 InPlace: Yes Mem: 8 Time: 15
> CPU: 3219MHz FSB: 230MHz [229MHz x 14.0 est.]
> CPU: 3219MHz FSB: 230MHz [229MHz x 14.0 est.]
> Starting MBMStarter.dll...
> Started MBMStarter.dll: 1
> 9/8/2007 11:26 PM 0/0
> Temperature: Case: 30.00
> Temperature: CPU: 42.00
> Temperature: Sensor 3: 26.00 <--- My room temp sensor
> ====================
>
> Launching 2 threads...
> Using CPU #0
> Beginning a continuous self-test to check your computer.
> Press Stop to end this test.
> Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
> 1 minute
> Temperature: CPU: 47.00
> ====================
> 3 minutes
> Temperature: CPU: 48.00
> ====================
> Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
> 4 minutes
> Temperature: CPU: 47.00
> ====================
> 5 minutes
> Temperature: CPU: 48.00
> ====================
> 7 minutes
> Temperature: CPU: 49.00
> ====================
> ************************************************** *******
>
> When I select "Blended", the word PAGING appears in a red rectangle,
> but does not change or disappear.

Hamm..when I was doing blended, mine was "PAGING" on and off. Mine
didn't show MBM stuff..

> So the "rounds" counter underneath
> it is not visible. And this is what the log looks like:
>
> ************************************************** *******
> Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 766 Time: 15
> CPU: 3219MHz FSB: 230MHz [229MHz x 14.0 est.]
> CPU: 3219MHz FSB: 230MHz [229MHz x 14.0 est.]
> Starting MBMStarter.dll...
> Started MBMStarter.dll: 1
> 9/8/2007 11:38 PM 0/0
> Temperature: Case: 30.00
> Temperature: CPU: 44.00
> Temperature: Sensor 3: 26.00
> ====================
>
> Launching 2 threads...
> Using CPU #0
> Beginning a continuous self-test to check your computer.
> Press Stop to end this test.
> Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
> 1 minute
> Temperature: CPU: 47.00
> ************************************************** *******
>
> I suppose it is possible we're using different versions of the program.
> The "About" on mine says:
>
> StressPrime 2004 ORTHOS
> v0.41.110.18
> Copyright 2004-2006
> Johnny Lee <email address>
>
> Mersenne Number Tests - Ver 24.14
>
> StressCPU source code
> 2002 Oct24
>
> HTH,
> Paul


Same version and this is what mine is showing for Small FFTs -
stress CPU - BTW, it's been 3 hours; my PC's RAM is 1GB total.

(PAGE is not showing as often as when I was doing blended test.)

Type: Small FFTs - stress CPU Min: 8 Max: 32 InPlace: Yes Mem: 8 Time:
15
CPU: 1293MHz FSB: 100MHz [107MHz x 12.0 est.]
9/8/2007 6:17 PM
Launching 1 thread...
Using CPU #0
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
Test 2, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
Self-test 8K passed!
Test 1, 560000 Lucas-Lehmer iterations of M208897 using 10K FFT
length.
Test 2, 560000 Lucas-Lehmer iterations of M204799 using 10K FFT
length.
Self-test 10K passed!
Test 1, 460000 Lucas-Lehmer iterations of M245281 using 12K FFT
length.
Test 2, 460000 Lucas-Lehmer iterations of M243713 using 12K FFT
length.
Self-test 12K passed!
Test 1, 380000 Lucas-Lehmer iterations of M282625 using 14K FFT
length.
Test 2, 380000 Lucas-Lehmer iterations of M280335 using 14K FFT
length.
Self-test 14K passed!
Test 1, 340000 Lucas-Lehmer iterations of M339487 using 16K FFT
length.
Test 2, 340000 Lucas-Lehmer iterations of M335393 using 16K FFT
length.
Self-test 16K passed!
Test 1, 270000 Lucas-Lehmer iterations of M420217 using 20K FFT
length.
Test 2, 270000 Lucas-Lehmer iterations of M409601 using 20K FFT
length.
Self-test 20K passed!
Test 1, 210000 Lucas-Lehmer iterations of M501041 using 24K FFT
length.
Test 2, 210000 Lucas-Lehmer iterations of M496943 using 24K FFT
length.
Self-test 24K passed!
Test 1, 180000 Lucas-Lehmer iterations of M580673 using 28K FFT
length.
Test 2, 180000 Lucas-Lehmer iterations of M573441 using 28K FFT
length.
Self-test 28K passed!
Test 1, 160000 Lucas-Lehmer iterations of M662593 using 32K FFT
length.
Test 2, 160000 Lucas-Lehmer iterations of M659457 using 32K FFT
length.
Self-test 32K passed!
Test 1, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
Test 2, 800000 Lucas-Lehmer iterations of M153599 using 8K FFT length.

What happens when the test is done? Get a message displayed?



> - Hide quoted text -
>
> - Show quoted text -

amandaF wrote:

>
> What happens when the test is done? Get a message displayed?
>

Basically, the longer it runs, without error, the more stable
your computer is. I don't normally run it for that long (maybe
four hours is all I can tolerate), so I don't know if it ever
stops or not.

Paul

On Sep 9, 2:52 am, Paul <nos...@needed.com> wrote:
> amandaF wrote:
>
> > What happens when the test is done? Get a message displayed?
>
> Basically, the longer it runs, without error, the more stable
> your computer is. I don't normally run it for that long (maybe
> four hours is all I can tolerate), so I don't know if it ever
> stops or not.
>
> Paul

Well, after 8 3/4 hours - I just checked it after waking up, it's at
round 3 w/ the result shown below:
(I realized that the first round for this test was round 0, not 1 like
I was assuming after the blended test, when Small FFT test started).
I am stopping it now. It seems fine, right?

So, why my test doesn't show the temperature info? Because the chipset
is not supported and there is no sensor HD?

Type: Small FFTs - stress CPU Min: 8 Max: 32 InPlace: Yes Mem: 8 Time:
15
CPU: 1293MHz FSB: 100MHz [107MHz x 12.0 est.]
9/8/2007 6:17 PM
Launching 1 thread...
Using CPU #0
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
Test 2, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
Self-test 8K passed!
Test 1, 560000 Lucas-Lehmer iterations of M208897 using 10K FFT
length.
Test 2, 560000 Lucas-Lehmer iterations of M204799 using 10K FFT
length.
Self-test 10K passed!
Test 1, 460000 Lucas-Lehmer iterations of M245281 using 12K FFT
length.
Test 2, 460000 Lucas-Lehmer iterations of M243713 using 12K FFT
length.
Self-test 12K passed!
Test 1, 380000 Lucas-Lehmer iterations of M282625 using 14K FFT
length.
Test 2, 380000 Lucas-Lehmer iterations of M280335 using 14K FFT
length.
Self-test 14K passed!
Test 1, 340000 Lucas-Lehmer iterations of M339487 using 16K FFT
length.
Test 2, 340000 Lucas-Lehmer iterations of M335393 using 16K FFT
length.
Self-test 16K passed!
Test 1, 270000 Lucas-Lehmer iterations of M420217 using 20K FFT
length.
Test 2, 270000 Lucas-Lehmer iterations of M409601 using 20K FFT
length.
Self-test 20K passed!
Test 1, 210000 Lucas-Lehmer iterations of M501041 using 24K FFT
length.
Test 2, 210000 Lucas-Lehmer iterations of M496943 using 24K FFT
length.
Self-test 24K passed!
Test 1, 180000 Lucas-Lehmer iterations of M580673 using 28K FFT
length.
Test 2, 180000 Lucas-Lehmer iterations of M573441 using 28K FFT
length.
Self-test 28K passed!
Test 1, 160000 Lucas-Lehmer iterations of M662593 using 32K FFT
length.
Test 2, 160000 Lucas-Lehmer iterations of M659457 using 32K FFT
length.
Self-test 32K passed!
Test 1, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
Test 2, 800000 Lucas-Lehmer iterations of M153599 using 8K FFT length.
Self-test 8K passed!
Test 1, 560000 Lucas-Lehmer iterations of M200705 using 10K FFT
length.
Test 2, 560000 Lucas-Lehmer iterations of M196607 using 10K FFT
length.
Self-test 10K passed!
Test 1, 460000 Lucas-Lehmer iterations of M235519 using 12K FFT
length.
Test 2, 460000 Lucas-Lehmer iterations of M233473 using 12K FFT
length.
Self-test 12K passed!
Test 1, 380000 Lucas-Lehmer iterations of M278527 using 14K FFT
length.
Test 2, 380000 Lucas-Lehmer iterations of M274335 using 14K FFT
length.
Self-test 14K passed!
Test 1, 340000 Lucas-Lehmer iterations of M331681 using 16K FFT
length.
Test 2, 340000 Lucas-Lehmer iterations of M329727 using 16K FFT
length.
Self-test 16K passed!
Test 1, 270000 Lucas-Lehmer iterations of M401407 using 20K FFT
length.
Test 2, 270000 Lucas-Lehmer iterations of M393217 using 20K FFT
length.
Self-test 20K passed!
Test 1, 210000 Lucas-Lehmer iterations of M487423 using 24K FFT
length.
Test 2, 210000 Lucas-Lehmer iterations of M471041 using 24K FFT
length.
Self-test 24K passed!
Test 1, 180000 Lucas-Lehmer iterations of M565247 using 28K FFT
length.
Test 2, 180000 Lucas-Lehmer iterations of M557057 using 28K FFT
length.
Self-test 28K passed!
Test 1, 160000 Lucas-Lehmer iterations of M655359 using 32K FFT
length.
Test 2, 160000 Lucas-Lehmer iterations of M644399 using 32K FFT
length.
Self-test 32K passed!
Test 1, 800000 Lucas-Lehmer iterations of M147455 using 8K FFT length.
Test 2, 800000 Lucas-Lehmer iterations of M143361 using 8K FFT length.
Self-test 8K passed!
Test 1, 560000 Lucas-Lehmer iterations of M194561 using 10K FFT
length.
Test 2, 560000 Lucas-Lehmer iterations of M188415 using 10K FFT
length.
Self-test 10K passed!
Test 1, 460000 Lucas-Lehmer iterations of M231183 using 12K FFT
length.
Test 2, 460000 Lucas-Lehmer iterations of M229375 using 12K FFT
length.
Self-test 12K passed!
Test 1, 380000 Lucas-Lehmer iterations of M270335 using 14K FFT
length.
Test 2, 380000 Lucas-Lehmer iterations of M266241 using 14K FFT
length.
Self-test 14K passed!
Test 1, 340000 Lucas-Lehmer iterations of M327681 using 16K FFT
length.
Test 2, 340000 Lucas-Lehmer iterations of M319487 using 16K FFT
length.
Self-test 16K passed!
Test 1, 270000 Lucas-Lehmer iterations of M392119 using 20K FFT
length.
Test 2, 270000 Lucas-Lehmer iterations of M389119 using 20K FFT
length.
Self-test 20K passed!
Test 1, 210000 Lucas-Lehmer iterations of M466943 using 24K FFT
length.
Test 2, 210000 Lucas-Lehmer iterations of M458753 using 24K FFT
length.
Self-test 24K passed!
Test 1, 180000 Lucas-Lehmer iterations of M544767 using 28K FFT
length.
Test 2, 180000 Lucas-Lehmer iterations of M540673 using 28K FFT
length.
Self-test 28K passed!
Test 1, 160000 Lucas-Lehmer iterations of M638977 using 32K FFT
length.
Test 2, 160000 Lucas-Lehmer iterations of M630783 using 32K FFT
length.
Self-test 32K passed!
Test 1, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.
Test 2, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.
Self-test 8K passed!
Test 1, 560000 Lucas-Lehmer iterations of M186369 using 10K FFT
length.
Test 2, 560000 Lucas-Lehmer iterations of M184319 using 10K FFT
length.
Self-test 10K passed!
Test 1, 460000 Lucas-Lehmer iterations of M225281 using 12K FFT
length.

On Sep 9, 2:52 am, Paul <nos...@needed.com> wrote:
> amandaF wrote:
>
> > What happens when the test is done? Get a message displayed?
>
> Basically, the longer it runs, without error, the more stable
> your computer is. I don't normally run it for that long (maybe
> four hours is all I can tolerate), so I don't know if it ever
> stops or not.
>
> Paul


BTW, so mine tested for 32 KB; that refers to the cache in the CPU,
right?

My CUP information is

AMD Athlon(tm) XP
CPU speed: 1923.37 MHz
CPU features: RDTSC,CMOV,Prefetch,3DNow!,MMX,SSE
L1 cache size: 64 MB
L2 cache size: 512 MB

So why did Ortho test only 32 KB?


>On Sep 9, 3:00 am, amandaF <amanda...@gmail.com> wrote:
> On Sep 9, 2:52 am, Paul <nos...@needed.com> wrote:
>
> > amandaF wrote:
>
> > > What happens when the test is done? Get a message displayed?
>
> > Basically, the longer it runs, without error, the more stable
> > your computer is. I don't normally run it for that long (maybe
> > four hours is all I can tolerate), so I don't know if it ever
> > stops or not.
>
> > Paul
>
> Well, after 8 3/4 hours - I just checked it after waking up, it's at
> round 3 w/ the result shown below:
> (I realized that the first round for this test was round 0, not 1 like
> I was assuming after the blended test, when Small FFT test started).
> I am stopping it now. It seems fine, right?
>
> So, why my test doesn't show the temperature info? Because the chipset
> is not supported and there is no sensor HD?
>
> Type: Small FFTs - stress CPU Min: 8 Max: 32 InPlace: Yes Mem: 8 Time:
> 15
> CPU: 1293MHz FSB: 100MHz [107MHz x 12.0 est.]
> 9/8/2007 6:17 PM
> Launching 1 thread...
> Using CPU #0
> Beginning a continuous self-test to check your computer.
> Press Stop to end this test.
> Test 1, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
> Test 2, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
> Self-test 8K passed!
> Test 1, 560000 Lucas-Lehmer iterations of M208897 using 10K FFT
> length.
> Test 2, 560000 Lucas-Lehmer iterations of M204799 using 10K FFT
> length.
> Self-test 10K passed!
> Test 1, 460000 Lucas-Lehmer iterations of M245281 using 12K FFT
> length.
> Test 2, 460000 Lucas-Lehmer iterations of M243713 using 12K FFT
> length.
> Self-test 12K passed!
> Test 1, 380000 Lucas-Lehmer iterations of M282625 using 14K FFT
> length.
> Test 2, 380000 Lucas-Lehmer iterations of M280335 using 14K FFT
> length.
> Self-test 14K passed!
> Test 1, 340000 Lucas-Lehmer iterations of M339487 using 16K FFT
> length.
> Test 2, 340000 Lucas-Lehmer iterations of M335393 using 16K FFT
> length.
> Self-test 16K passed!
> Test 1, 270000 Lucas-Lehmer iterations of M420217 using 20K FFT
> length.
> Test 2, 270000 Lucas-Lehmer iterations of M409601 using 20K FFT
> length.
> Self-test 20K passed!
> Test 1, 210000 Lucas-Lehmer iterations of M501041 using 24K FFT
> length.
> Test 2, 210000 Lucas-Lehmer iterations of M496943 using 24K FFT
> length.
> Self-test 24K passed!
> Test 1, 180000 Lucas-Lehmer iterations of M580673 using 28K FFT
> length.
> Test 2, 180000 Lucas-Lehmer iterations of M573441 using 28K FFT
> length.
> Self-test 28K passed!
> Test 1, 160000 Lucas-Lehmer iterations of M662593 using 32K FFT
> length.
> Test 2, 160000 Lucas-Lehmer iterations of M659457 using 32K FFT
> length.
> Self-test 32K passed!
> Test 1, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
> Test 2, 800000 Lucas-Lehmer iterations of M153599 using 8K FFT length.
> Self-test 8K passed!
> Test 1, 560000 Lucas-Lehmer iterations of M200705 using 10K FFT
> length.
> Test 2, 560000 Lucas-Lehmer iterations of M196607 using 10K FFT
> length.
> Self-test 10K passed!
> Test 1, 460000 Lucas-Lehmer iterations of M235519 using 12K FFT
> length.
> Test 2, 460000 Lucas-Lehmer iterations of M233473 using 12K FFT
> length.
> Self-test 12K passed!
> Test 1, 380000 Lucas-Lehmer iterations of M278527 using 14K FFT
> length.
> Test 2, 380000 Lucas-Lehmer iterations of M274335 using 14K FFT
> length.
> Self-test 14K passed!
> Test 1, 340000 Lucas-Lehmer iterations of M331681 using 16K FFT
> length.
> Test 2, 340000 Lucas-Lehmer iterations of M329727 using 16K FFT
> length.
> Self-test 16K passed!
> Test 1, 270000 Lucas-Lehmer iterations of M401407 using 20K FFT
> length.
> Test 2, 270000 Lucas-Lehmer iterations of M393217 using 20K FFT
> length.
> Self-test 20K passed!
> Test 1, 210000 Lucas-Lehmer iterations of M487423 using 24K FFT
> length.
> Test 2, 210000 Lucas-Lehmer iterations of M471041 using 24K FFT
> length.
> Self-test 24K passed!
> Test 1, 180000 Lucas-Lehmer iterations of M565247 using 28K FFT
> length.
> Test 2, 180000 Lucas-Lehmer iterations of M557057 using 28K FFT
> length.
> Self-test 28K passed!
> Test 1, 160000 Lucas-Lehmer iterations of M655359 using 32K FFT
> length.
> Test 2, 160000 Lucas-Lehmer iterations of M644399 using 32K FFT
> length.
> Self-test 32K passed!
> Test 1, 800000 Lucas-Lehmer iterations of M147455 using 8K FFT length.
> Test 2, 800000 Lucas-Lehmer iterations of M143361 using 8K FFT length.
> Self-test 8K passed!
> Test 1, 560000 Lucas-Lehmer iterations of M194561 using 10K FFT
> length.
> Test 2, 560000 Lucas-Lehmer iterations of M188415 using 10K FFT
> length.
> Self-test 10K passed!
> Test 1, 460000 Lucas-Lehmer iterations of M231183 using 12K FFT
> length.
> Test 2, 460000 Lucas-Lehmer iterations of M229375 using 12K FFT
> length.
> Self-test 12K passed!
> Test 1, 380000 Lucas-Lehmer iterations of M270335 using 14K FFT
> length.
> Test 2, 380000 Lucas-Lehmer iterations of M266241 using 14K FFT
> length.
> Self-test 14K passed!
> Test 1, 340000 Lucas-Lehmer iterations of M327681 using 16K FFT
> length.
> Test 2, 340000 Lucas-Lehmer iterations of M319487 using 16K FFT
> length.
> Self-test 16K passed!
> Test 1, 270000 Lucas-Lehmer iterations of M392119 using 20K FFT
> length.
> Test 2, 270000 Lucas-Lehmer iterations of M389119 using 20K FFT
> length.
> Self-test 20K passed!
> Test 1, 210000 Lucas-Lehmer iterations of M466943 using 24K FFT
> length.
> Test 2, 210000 Lucas-Lehmer iterations of M458753 using 24K FFT
> length.
> Self-test 24K passed!
> Test 1, 180000 Lucas-Lehmer iterations of M544767 using 28K FFT
> length.
> Test 2, 180000 Lucas-Lehmer iterations of M540673 using 28K FFT
> length.
> Self-test 28K passed!
> Test 1, 160000 Lucas-Lehmer iterations of M638977 using 32K FFT
> length.
> Test 2, 160000 Lucas-Lehmer iterations of M630783 using 32K FFT
> length.
> Self-test 32K passed!
> Test 1, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.
> Test 2, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.
> Self-test 8K passed!
> Test 1, 560000 Lucas-Lehmer iterations of M186369 using 10K FFT
> length.
> Test 2, 560000 Lucas-Lehmer iterations of M184319 using 10K FFT
> length.
> Self-test 10K passed!
> Test 1, 460000 Lucas-Lehmer iterations of M225281 using 12K FFT
> length.

amandaF wrote:
> On Sep 9, 2:52 am, Paul <nos...@needed.com> wrote:
>> amandaF wrote:
>>
>>> What happens when the test is done? Get a message displayed?
>> Basically, the longer it runs, without error, the more stable
>> your computer is. I don't normally run it for that long (maybe
>> four hours is all I can tolerate), so I don't know if it ever
>> stops or not.
>>
>> Paul
>
>
> BTW, so mine tested for 32 KB; that refers to the cache in the CPU,
> right?
>

The memory allocation at the start of "Small FFTs", claimed up to
8 megabytes ("Mem: 8"). In Task Manager, I think it looked smaller
than that. The Blended Test, on the other hand, did appear to be
taking the 700+ MB claimed. The Small FFTs should be a bit better
at staying in cache, which means that selection might make the
CPU a degree or two hotter. But in terms of overall system
response, I prefer blended, since most of the time I'm running this,
I'm interested in whether the CPU+memory are working good.

Type: Small FFTs - stress CPU Min: 8 Max: 32 InPlace: Yes Mem: 8 Time: 15

As for "mbmstarter.dll", I think in fact you have to install MBM5,
and then mbmstarter can access and run the install files. I checked
a readme.txt file from the MBM package and that is what it seems to
suggest.

The last version of MBM5 appears to be 5.3.7.0

http://web.archive.org/web/200511260...vewiredev.com/

You can download 5.3.7.0 here:

http://www.majorgeeks.com/download.php?det=311

Once installed, check Start:Programs:MBM5 for a Config Wizard. Maybe
that will make the setup a bit easier. It's been a long time since I
set mine up, so I don't remember the details. When MBM5 is running,
there will be a couple temperatures listed in the task bar. Right
clicking on them, and selecting "Dashboard and Settings", will bring
up both windows, and allow you to look around.

Paul