strange phenomenon

[Sydney]

I am playing a chess program or doing anything else. All of a sudden
everything stops as if the computer hangs. Then after a while the
processor (computer ? ) restarts and everything returns to normal.
I am running a windows xp OS and the event observer shows no errors or
warnings.

I wonder what it is ?

 

[Paul]

I am playing a chess program or doing anything else. All of a sudden
everything stops as if the computer hangs. Then after a while the
processor (computer ? ) restarts and everything returns to normal.
I am running a windows xp OS and the event observer shows no errors or
warnings.

I wonder what it is ?

The words here are important. I suspect you don't mean "restart".

Something like:

Computer was working.
Computer stops for X seconds, screen not updated and so on.
After the X seconds has passed, the computer works as if nothing happened.

So there's no "reset", no "POST", no reboot of the computer.

The period of time "X" is important. If X=15 seconds, it
could be that during a paging operation, the disk drive
had a bad sector, and it took 15 seconds to resolve the
storage problem.

If the time was much longer than that, then I can't guess
as to what it might be.

When an operation fails at kernel level (such as the paging
example I just made up), the OS may be unaware of the loss
of time. The OS may not know it has been unresponsive.
If the storage operation did not complete, it might result
in a "delayed write failure". And then there would be an
entry in the Event Viewer.

Paul

 

[Darklight]

The words here are important. I suspect you don't mean "restart".

Something like:

Computer was working.
Computer stops for X seconds, screen not updated and so on.
After the X seconds has passed, the computer works as if nothing
happened.

So there's no "reset", no "POST", no reboot of the computer.

The period of time "X" is important. If X=15 seconds, it
could be that during a paging operation, the disk drive
had a bad sector, and it took 15 seconds to resolve the
storage problem.

If the time was much longer than that, then I can't guess
as to what it might be.

When an operation fails at kernel level (such as the paging
example I just made up), the OS may be unaware of the loss
of time. The OS may not know it has been unresponsive.
If the storage operation did not complete, it might result
in a "delayed write failure". And then there would be an
entry in the Event Viewer.

Paul

i would check your cpu heatsink i know chess programs are very
cpu intesive. that produces heat heance the hang!

 

[VanguardLH]

All of a sudden everything stops as if the computer hangs.

Have you been monitoring temperatures, especially for the CPU? If it is
getting overheated then it throttles down and can even halt.
Overheating could be due to a loose heatsink, fan not spinning (fast
enough or not at all), dust, or restricted air flow.

Then after a while the processor (computer ? ) restarts and
everything returns to normal. I am running a windows xp OS and the
event observer shows no errors or warnings.

If the computer is actually restarting (rebooting) then a driver or
application is crashing and taking the OS with it. It also means you

configured your operating system so it reboots after a crash
instead of stopping at the BSOD screen.

You might also test your system memory. If its contents gets corrupted
then who knows what resultant code actually gets executed. Nothing runs
unless it is in memory. Try running memtest (3 passes is sufficient).​

 

[Sydney]

Le 25/09/2012 10:10, Paul a écrit :

The words here are important. I suspect you don't mean "restart".

Something like:

Computer was working.
Computer stops for X seconds, screen not updated and so on.
After the X seconds has passed, the computer works as if nothing
happened.

So there's no "reset", no "POST", no reboot of the computer.

The period of time "X" is important. If X=15 seconds, it
could be that during a paging operation, the disk drive
had a bad sector, and it took 15 seconds to resolve the
storage problem.

If the time was much longer than that, then I can't guess
as to what it might be.

When an operation fails at kernel level (such as the paging
example I just made up), the OS may be unaware of the loss
of time. The OS may not know it has been unresponsive.
If the storage operation did not complete, it might result
in a "delayed write failure". And then there would be an
entry in the Event Viewer.

Paul

Exact there is no reset nor rebooting.
The period of time is around 25 sec !
I could not monitor the temperatures. Core temp.exe shows no indications
(0 values). Do you have a clue for better software for Win XP ?
System memory was tested and shows no errors.
I hope these data are helpful to resolve the problem

 

[Sydney]

Le 25/09/2012 09:20, Sydney a écrit :

The words here are important. I suspect you don't mean "restart".

Something like:

Computer was working.
Computer stops for X seconds, screen not updated and so on.
After the X seconds has passed, the computer works as if nothing
happened.

So there's no "reset", no "POST", no reboot of the computer.

The period of time "X" is important. If X=15 seconds, it
could be that during a paging operation, the disk drive
had a bad sector, and it took 15 seconds to resolve the
storage problem.

If the time was much longer than that, then I can't guess
as to what it might be.

When an operation fails at kernel level (such as the paging
example I just made up), the OS may be unaware of the loss
of time. The OS may not know it has been unresponsive.
If the storage operation did not complete, it might result
in a "delayed write failure". And then there would be an
entry in the Event Viewer.

Paul

Exact there is no reset nor rebooting.
The period of time is around 25 sec !
I could not monitor the temperatures. Core temp.exe shows no indications
(0 values). Do you have a clue for better software for Win XP ?
System memory was tested and shows no errors.
I hope these data are helpful to resolve the problem

 

[Paul]

Le 25/09/2012 10:10, Paul a écrit :
Exact there is no reset nor rebooting.
The period of time is around 25 sec !
I could not monitor the temperatures. Core temp.exe shows no indications
(0 values). Do you have a clue for better software for Win XP ?
System memory was tested and shows no errors.
I hope these data are helpful to resolve the problem

You could try this program.

http://www.techpowerup.com/realtemp/

The 25 seconds, sounds a little too long for a disk drive problem.
And I don't have any other suggestions for you.

Paul

 

[VanguardLH]

I could not monitor the temperatures. Core temp.exe shows no indications
(0 values). Do you have a clue for better software for Win XP ?

Speedfan
http://www.almico.com/speedfan.php

 

[larrymoencurly]

System memory was tested and shows no errors.

How did you test? I run 2 completely different diagnostics, each overnightand with the memory hot (50 Celcius) because no single diagnostic will detect every error. For example, one person ran a certain respected diagnostic for days, and it found nothing, while a completely different test discovered a single bad bit quickly but then needed almost 10 more hours to find it again.

If you're using memory with a wierd voltage rating (anything above 1.50V for DDR3), has heatsinks, or its chips are overclocked or no-name/house branded, very likely a module is defective.

You may first want to try running the computer with the side panel removed and a table fan blasting into it, to eliminate the possibility of cooling problems (except due to a CPU heatsink not mounted flush).

What CPU, graphics card, motherboard, and brand and rating power supply do you have?

 

[Sydney]

Le 28/09/2012 05:27, (e-mail address removed) a écrit :

How did you test? I run 2 completely different diagnostics, each overnight and with the memory hot (50 Celcius) because no single diagnostic will detect every error. For example, one person ran a certain respected diagnostic for days, and it found nothing, while a completely different test discovered a single bad bit quickly but then needed almost 10 more hours to find it again.

If you're using memory with a wierd voltage rating (anything above 1.50V for DDR3), has heatsinks, or its chips are overclocked or no-name/house branded, very likely a module is defective.

You may first want to try running the computer with the side panel removed and a table fan blasting into it, to eliminate the possibility of cooling problems (except due to a CPU heatsink not mounted flush).

What CPU, graphics card, motherboard, and brand and rating power supply do you have?

I tested using memtest.exe 4.0 program I ran it times then 42 times. It
is a notebook Fujitsu siemens Amilo M series Graphics is by ATI mobility
Radeon 9600 series. mother board and power supply (rating unknown ) are
proprietary .

 

[larrymoencurly]

I tested using memtest.exe 4.0 program I ran it times then 42 times.

Don't use MemTest.exe. Use MemTest86+ or, better yet, MemTest86. Then use Gold Memory, not just ver. 6.92 but also ver. 5.07. Don't trust the memory until it passes GM 5.07 overnight.