[rshaffer61]

That would really answer for the crashing but no logs showing it.

[Advertisements]

Going to go part out the other computer since the one I have outside of a rig is only 160w (lol) and I should be able to run the machine all night to see if it freezes or no with a new power supply in it.

[Senidol]

Going to go part out the other computer since the one I have outside of a rig is only 160w (lol) and I should be able to run the machine all night to see if it freezes or no with a new power supply in it.

[Senidol]

Well I installed another PSU today, same wattage and got similar results on the speedfan, and similar results on Everest voltage give or take .02-.05 margin of difference. Computer crashed again.

[rshaffer61]

Well lets take a look at the next two options then which would be motherboard and OS.
Go Start and then to Run ("Start Search" in Vista),
Type in: sfc /scannow
Click OK (Enter in Vista).
Have Windows CD/DVD handy.
If System File Checker (sfc) finds any errors, it may ask you for the CD/DVD.
If sfc does not find any errors in Windows XP, it will simply quit, without any message.
In Vista you will receive the following message: "Windows resource protection did not find any integrity violations".

For Vista users ONLY: Navigate to C:\Windows\Logs\CBS folder. You'll see CBS.log file.
Usually, it's pretty big file, so upload it to Flyupload, and post download link.


If you don't have Windows CD....
This applies mostly to Windows XP, since Vista rarely requires use of its DVD while running "sfc"
Note This method will not necessarily work as well, as when using Windows CD, because not always ALL system files are backed up on your hard drive. Also, backed up files may be corrupted as well.

Go Start and then Run
type in regedit and click OK


Navigate to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup

You will see various entries Values on the right hand side.

The one we want is called: SourcePath

It probably has an entry pointing to your CD-ROM drive, usually D and that is why it is asking for the XP CD.
All we need to do is change it to: C:
Now, double click the SourcePatch setting and a new box will pop up.
Change the drive letter from your CD drive to your root drive, usually C:
Close Registry Editor.

Now restart your computer and try sfc /scannow again!


Thanks to Broni for the instructions

[Senidol]

The blue screen windows chkdsk started for the first time.

"corrected error in index $i30 for file 62740"
"sorting index $i30 in file 62740"

recovered quite a few orphaned files.

Interesting that this is the first time it has run on its own on this computer.

Edited by Senidol, 06 March 2010 - 07:51 PM.

[rshaffer61]

Is this when attempting to run my previous instructions?

[Senidol]

Nope just on start up trying to run the scannow, I ran a scannow earlier without the disc, and now when I go to run it I only get a DoS box that flashes and nothing runs.

[rshaffer61]

That would mean it has found nothing that needs to be corrected.
At this point we have checked all the hardware and nothing is showing a problem.
We have tested the System Files and ran chkdsk
Memory has been tested
The only thing we have not tried is a Repair installation or a Parallel installation.
Either would mean you need a OS disk.

[Senidol]

A few things before I go ahead and reformat. Looking at the event viewer I see a few errors, and a few warnings.

Error #1= "sr" Event 1

The System Restore filter encountered the unexpected error '0xc0000243'
while processing the file 'EraseUtilDrvl9' on the volume 'Harddisk volume 1'. It has stopped monitoring the volume.

I think this is the first time I have seen this one so I assume it came about from all the HD tests and cleaning I ran earlier.

Error #2= "Service Control Manager" Event 7023

The Help and Support service terminated with the following error: The specified module could not be found.

This is the most common error in the Log the times do not coincide with the actual time of the crashes though. Very frequent though.

Warning #1: "Dhcp" Event 1007

Your computer has automatically configured the IP adress for the Network Card with the network adress 001921D7480D.

This warning happens frequently, and often right before a crash takes place.

Warning #2: "Server" Event 2504

The server could not bind to the transport \device\NeTBT_TCIP_{insert long number here blah blah blah

Any ideas as to if any of these could cause a chronic hard freezing problem?

[Senidol]

Another version of the Service Control Manager error:

Error event = 7001

"The DHCP Client service depends on the NetBios over Tcpip service which failed to start because of the following error: A device attached to the system is not functioning"

I can assume this is only in Safe Mode without networking?

[Senidol]

4 Hours in Safe Mode and no crashes, beginning to suspect a driver/program/bios

[rshaffer61]

Reboot back to normal mode and then do this.
Lets see what you have in your startup

Please click on
Start and then to Run
Type in msconfig and press Enter
Now click on Startups
Then uncheck everything and restart.
IMPORTANT! In case of laptop, make sure, you do NOT disable any keyboard, or touchpad entries.
If system boots correctly and is running smoothly and faster then we have a startup problem
Try going back into msconfig and check one item and reboot
Keep doing that till you have found the problem or all are finally checked.
Post back with the results

[Senidol]

So I unchecked everything in startup, computer ran alright for awhile and then I crashed again after about 2 hours.

[rshaffer61]

Run a new WhoCrashed
This will give us the most recent cause.

[Senidol]

nothing in who crashed again, just like before.