Re: PC reboot because of CPU overheating?

Thanks, this helped a lot. Since I had the MemDump files for both restarts,
I've checked the event logs to see what happened before and after this dump
file was created.

There were no errors or warnings during 4 hours pereceding the creation of
this MemDump file, not in Application, nor in System event logs, which
suggests that there were no software errors involved in this reboot.

There are only 5 System entries before eventlog Dump file was created (not
counting those thatoccured 4 hours apart):

1) nvatabus - devide identified.
2) nvatabus - decide identified.
3) nvatabus - devide identified.
4) eventlog - The eventlog Service was started
5) eventlog - Microsoft (R) Windows (R) - Microprocessor Free

Then comes the DumpFile and rest of the events, which I see on all other
Window Startups. There was no "eventlog - The eventlog Service was stopped"
before those, which suggested a hard restart. Exactly the same thing was in
both "reboot" cases.

I've tried holding the shut-down button for 4 seconds while I was logged
into Windows, which should initiate a clean shutdown, to see if something
will appear in the log on normal system shutdown. Then I've pressed the
"reset" button and waited for the System to boot.

After system booted up, the same warning Windows was displayed as in other 2
cases, telling me about system restart and a Dump file been created.

In the System event logs, I found one event about a Popup-Window with a
Windows Shutdown question, telling me that a user is logged in and Windows
Shutdown wouldn't be a good idea (or something like that). After this entry,
there were no more entries for about 20 seconds, which was the time needed
for my PC to reboot after I pressed the "reset" button.

And then comes the surprise ... after the pop-up window, I now have exactly
the same entries in my event log, starting a few seconds before my system
completely booted up.

1) nvatabus - devide identified.
2) nvatabus - decide identified.
3) nvatabus - devide identified.
4) eventlog - The eventlog Service was started
5) eventlog - Microsoft (R) Windows (R) - Microprocessor Free

So, one part of the mistery is now solved :)

The log file was now created AFTER system restart, not before. I guess, this
also means that this PC has experienced a hard reset in both other cases
too, with a log file created by Windows after boot-up (for whatever reason).
This also means that it was a hardware-related issue, probably as a
precausion to save the system from "breaking".

Now I just have to start the test again, leave the Windows open to get
enough cooling in that room and leave it running for about a Week (which is
twice as long as two last times before it restarted) and see what happens
:o)

--
Danijel Tkalcec
http://www.deltasoft.hr/rtc/author.htm

RealThinClient components
-------------------------------------------
* The Easiest way to build Internet-enabled applications
- Clients, Stand-alone Servers, ISAPI extensions -
> Write and Call Remote Functions
> Download and Upload Files
> Single- and Multi-Threaded mode
> Firewall friendly - all over HTTP
> Stress-tested for highest stability

http://www.realthinclient.com
or www.deltasoft.hr/rtc


.

Loading