Crash Log

Hi,

Is there a log file (or program) where I can try to track down the reason for my system freezing?

The Event Viewer shows nothing........

Thanks,
AK

 

Incompatible hardware drivers, faulty or unsupported hardware, and conflicts between system resources are some of the common causes of driver conflicts that may cause Windows freeze ups.

The best way to identify driver and hardware problems and troubleshoot them is to use the Device Manager. To open the Device Manager, right-click on the My Computer icon and then select the Properties command. Here, on the Hardware tab, select the Device Manager button. In the Device Manager window that opens, problematic devices are displayed with a yellow triangle having a black exclamation mark in between. Right-click on the faulty device, and then select Properties. In the properties dialog box that opens, you can select various options to rollback, uninstall, and update the existing device driver.

 

Thanks - already done and no devices are marked.

Yesterday I saw another post dealing with a faulty WiFi controller. I have turned my WiFi off to see if it still freezes. So far so good.

But, is there any other log hidden in the System which might point to the problem after a freeze and re-boot?

Thanks!

 

You can use Dr Watson to log system problems.

At the Run prompt, type "Drwtsn32" (without the quotes), click OK

After you start Dr. Watson, it saves a snapshot log of your computer's memory and other settings when a system error or application error occurs. The log is created based on the system information available at the time of the problem.

After starting Dr. Watson, you can start your other programs and continue working.

The log file's name is Drwtsn32.log, and the default path to the log file is C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson You can locate this file after an error occurs (and possibly after a required reboot if the error forces your system to freeze) and read it using Wordpad, Notepad or other text editor.

 

That's great - many thanks!

AK

 

Let's hope it records the problem.

 

Yes thanks. I've re-booted and turned on the WiFi and Dr. Watson. It should freeze up soon enough.

Thanks alot for your help!
AK

 

Update - today the computer froze up and required a re-boot 6 times in rapid succession. Dr. Watson was running but created no log. Speed Fan was also running and recorded the following temps: HDD 40C, Temp 1 49C, Core 0 65C and Core 1 65C.

Are these recorded temps considered too high?

Thanks!

 

You may want to check your power supply. Put your hand on the exhaust fan of your PC and see if the air coming out is hot or just warm.

Also, if you have access to a digital voltmeter, check the voltages of the PS.

Power Supply Reference Sheet

Here are the ATX allowances for power supply voltage spec
deviation, measured at the motherboard power connector, negative
test lead on the chassis frame for reference ground.

+12VDC output +/- 5% (11.4V to 12.6V) This rail may deviate up to
+/- 10% if the supply is under peak loading.

+5VDC output +/- 5% (4.75V to 5.25V)
+3.3VDC output +/- 5% (3.14V to 3.47V)
-5VDC output +/-10% (-4.50V to -5.50V)
-12VDC output +/- 10% (-10.80V to -13.20V)
+5VSB +/- 5% (4.75V to 5.25V)

If measurements show that the voltage deviations are outside the
ranges specified above, then it's time to get a new power supply.
Generally when a power supply starts to fail the voltages go up.

 

Thanks for your reply.

The air coming out of the exhaust is barely warm - except when the fan starts to run, then it is quite warm!

I do not have a digital voltmeter - but I will have the PS checked.

Thanks!