Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Screen will freeze after approx 24 hrs of operation..


  • Please log in to reply

#16
rriche

rriche

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
Hi...
I have run the pc pitstop process and as per your request here is the URL for aalysis:

http://pcpitstop.com...?conid=24362925

Thx...
Await your thoughts

Rich
  • 0

Advertisements


#17
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Your log looks pretty good with no driver or software issues. There was some small issues with the OS but nothing that would indicate the issue you are having. I want to start with the OS first and then move on to maybe the video card. One way to check the video is to boot into Safe Mode With Networking for a day or so and see if the issue happens then. If not it may indicate a driver. This will allow you to still reply here while in Safe Mode. :)


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



Revised and Simplified:


Do you have a valid XP CD?

If so, place it in your CD ROM drive and follow the instructions below:
  • Click on Start and select Run... type sfc /scannow (note the space) (Let this run undisturbed until the window with the blue progress bar goes away)

SFC
- Which stands for System File Checker,
retrieves the correct version of the file from %Systemroot%\System32\Dllcache or the Windows installation source files, and then replaces the incorrect file.
If you want to see what was replaced, right-click My Computer and click on Manage. In the new window that appears, expand the Event Viewer (by clicking on the + symbol next to it) and then click on System.
  • 0

#18
rriche

rriche

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
Hi Mr Shaffer..
I ran the computer in safe mode for a few days and it did not go into freeze mode...
I then ran the scannow process in normal operation mode... I initially adopted your modified settings of changing source path...but it seemed to have no effect...Still kept asking for CD...
Then I used an XP Disk (I dont think it was the original but is the same version) and had to keep pressing retry but it did eventually go through the complete scannow process (completed blue bar...). There appeared to be no mention of any problems as it quit with no message...
One day later operating in normal mode after completing your tests....The computer froze again.

Await your thoughts/directions...And once again thankyou for your assistance..

Rich
  • 0

#19
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Lets see if there is a event for the last freeze. Please run a new WhoCrashed report.


  • Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
  • Double-click VEW.exe
  • Under 'Select log to query', select (as appropriate):
    • Application
    • System
  • Under 'Select type to list', select (as appropriate):
    • Error
    • Information
    • Warning
Then use the 'Date of events' or 'Number of events' as follows:

Either:
  • Click the radio button for 'Number of events'
    Type 3 in the 1 to 20 box (or any number from 1 to 20)
    Then click the Run button.
    Notepad will open with the output log.

  • Click the radio button for 'Date of events'
    In the From: boxes type today's date (presuming the crash happened today) 15 05 2011
    In the To: boxes type today's date (presuming the crash happened today) 17 05 2011
    Then click the Run button.
    Notepad will open with the output log.
Please post the Output log in your next reply


Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Reboot after your done running chkdsk /r...
then Go to Start...Run and type: eventvwr.msc press Enter
When Event Viewer opens, click on Applications... then scroll down to [b]Winlogon]/b] and double-click on it. This is the log created after running Checkdisk...copy and paste the log back here


We will advise after studying the log.
  • 0

#20
rriche

rriche

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
Hi..
As per your requests:

Whocrashed Report

System Information (local)
--------------------------------------------------------------------------------

computer name: HP
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel® Pentium® 4 CPU 2.80GHz Intel586, level: 15
1 logical processors, active mask: 1
RAM: 1064812544 total
VM: 2147352576, free: 2047488000



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Wed 26/08/2009 3:40:36 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082709-01.dmp
This was probably caused by the following module: eappkt.sys (EAPPkt+0x91A)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x1, 0xFFFFFFFF804EDE7E)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\eappkt.sys
product: Windows ® 2000 DDK driver
company: Windows ® 2000 DDK provider
description: NDIS User mode I/O Driver
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: eappkt.sys (NDIS User mode I/O Driver, Windows ® 2000 DDK provider).
Google query: eappkt.sys Windows ® 2000 DDK provider CUSTOM_ERROR




On Wed 26/08/2009 1:46:50 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082609-01.dmp
This was probably caused by the following module: eappkt.sys (EAPPkt+0x91A)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x1, 0xFFFFFFFF804EDE7E)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\eappkt.sys
product: Windows ® 2000 DDK driver
company: Windows ® 2000 DDK provider
description: NDIS User mode I/O Driver
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: eappkt.sys (NDIS User mode I/O Driver, Windows ® 2000 DDK provider).
Google query: eappkt.sys Windows ® 2000 DDK provider CUSTOM_ERROR





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

eappkt.sys (NDIS User mode I/O Driver, Windows ® 2000 DDK provider)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.



VEW Output Log


Vino's Event Viewer v01c run on Windows XP in English
Report run at 18/05/2011 11:26:00 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 16/05/2011 7:27:04 PM
Type: error Category: 0
Event: 5000 Source: MPSampleSubmission
EventType mptelemetry, P1 8007043c, P2 beginsearch, P3 search, P4 3.0.8107.0, P5 mpsigdwn.dll, P6 3.0.8107.0, P7 microsoft security essentials (edb4fa23-53b8-4afa-8c5d-99752cca7094), P8 NIL, P9 NIL, P10 NIL.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 18/05/2011 11:15:49 PM
Type: information Category: 3
Event: 3044 Source: Windows Search Service
The gatherer index resumed.

Context: Application, SystemIndex Catalog


Log: 'Application' Date/Time: 18/05/2011 11:15:45 PM
Type: information Category: 0
Event: 0 Source: iPod Service
The event description cannot be found.

Log: 'Application' Date/Time: 18/05/2011 11:15:44 PM
Type: information Category: 1
Event: 1003 Source: Windows Search Service
The Windows Search Service started.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 11/05/2011 5:22:43 PM
Type: warning Category: 52
Event: 4354 Source: EventSystem
The COM+ Event System failed to fire the StartScreenSaver method on subscription {3651B1EE-5427-4D80-9EFD-86B21B19CBFF}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The subscriber returned HRESULT 800706BB.

Log: 'Application' Date/Time: 11/05/2011 5:22:43 PM
Type: warning Category: 52
Event: 4354 Source: EventSystem
The COM+ Event System failed to fire the StopScreenSaver method on subscription {3651B1EE-5427-4D80-9EFD-86B21B19CBFF}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The subscriber returned HRESULT 800706BB.

Log: 'Application' Date/Time: 11/05/2011 5:22:42 PM
Type: warning Category: 52
Event: 4354 Source: EventSystem
The COM+ Event System failed to fire the StopScreenSaver method on subscription {3651B1EE-5427-4D80-9EFD-86B21B19CBFF}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The subscriber returned HRESULT 800706BB.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 18/05/2011 8:36:13 PM
Type: error Category: 0
Event: 10010 Source: DCOM
The server {4EB61BAC-A3B6-4760-9581-655041EF4D69} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 17/05/2011 3:13:26 PM
Type: error Category: 0
Event: 10010 Source: DCOM
The server {4EB61BAC-A3B6-4760-9581-655041EF4D69} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 17/05/2011 3:11:58 PM
Type: error Category: 0
Event: 10005 Source: DCOM
DCOM got error "%1084" attempting to start the service EventSystem with arguments "" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF}

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 18/05/2011 11:21:29 PM
Type: information Category: 0
Event: 7035 Source: Service Control Manager
The cpuz134 service was successfully sent a start control.

Log: 'System' Date/Time: 18/05/2011 11:16:00 PM
Type: information Category: 0
Event: 7035 Source: Service Control Manager
The MpKsl1a560018 service was successfully sent a start control.

Log: 'System' Date/Time: 18/05/2011 11:15:52 PM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The IMAPI CD-Burning COM Service service entered the stopped state.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 18/05/2011 11:15:48 PM
Type: warning Category: 0
Event: 4 Source: b57w2k
Broadcom NetXtreme Gigabit Ethernet for hp: The network link is down. Check to make sure the network cable is properly connected.

Log: 'System' Date/Time: 18/05/2011 8:35:45 PM
Type: warning Category: 0
Event: 4 Source: b57w2k
Broadcom NetXtreme Gigabit Ethernet for hp: The network link is down. Check to make sure the network cable is properly connected.

Log: 'System' Date/Time: 18/05/2011 6:31:49 AM
Type: warning Category: 0
Event: 36 Source: W32Time
The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized.



CHKDSK REPORT:
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 15 unused index entries from index $SII of file 0x9.
Cleaning up 15 unused index entries from index $SDH of file 0x9.
Cleaning up 15 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

78123007 KB total disk space.
48676468 KB in 86498 files.
37328 KB in 8994 indexes.
0 KB in bad sectors.
268899 KB in use by the system.
65536 KB occupied by the log file.
29140312 KB available on disk.

4096 bytes in each allocation unit.
19530751 total allocation units on disk.
7285078 allocation units available on disk.

Internal Info:
50 a6 02 00 10 75 01 00 bf 23 02 00 00 00 00 00 P....u...#......
45 24 00 00 04 00 00 00 15 03 00 00 00 00 00 00 E$..............
7c 09 de 05 00 00 00 00 a6 45 d2 55 00 00 00 00 |........E.U....
f8 99 4f 0f 00 00 00 00 be 5e 05 ca 04 00 00 00 ..O......^......
0c 13 81 0c 03 00 00 00 24 00 35 44 08 00 00 00 ........$.5D....
99 9e 36 00 00 00 00 00 98 38 07 00 e2 51 01 00 ..6......8...Q..
00 00 00 00 00 d0 f9 9a 0b 00 00 00 22 23 00 00 ............"#..

Windows has finished checking your disk.
Please wait while your computer restarts.


For more information, see Help and Support Center at http://go.microsoft....ink/events.asp.


Thx...I do hope my work is accurate
If you require any further info...let me know..


Rich
  • 0

#21
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Lets see what you have in your startup services area

Please click on
Start and then to Run
Type in msconfig and press Enter
Now click on Services
Click on the Hide All Microsoft Services
Then uncheck everything and restart.
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
  • 0

#22
rriche

rriche

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
Hello Mr Shaffer,
I hid all microsoft services and disabled all other services...
System appeared to reboot as normal with no real change..

I have not really had a problem in the past with rebooting or starting up the computer. The problem is only that the system will freeze after being in use for 24 hrs..

I tried rechecking the first few items in startup in msconfig...Appeared to make no noticable difference in start-up operations..All is good..

Do you wish me to continue with all rechecking items and if so...just what am I looking for?

Thx...
Rich
  • 0

#23
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
I am looking at one or two of thee nonessential services that may be causing the freezing. one being Itunes.
  • 0

#24
rriche

rriche

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
Hi Mr Shaffer,
Just an update....still going through the deductive process...but as it takes up to 24 hrs to freeze, it is a long process to go through all the services..
I initially ran the computer with all system services isolated (bar windows) and there appeared to be no freezing after 3 days...
I have been slowly going through a dedecutive method and may have found a couple of services that may be attributing to freeze..
However, I am still going through the process to ensure they are not due to freezing for volume or other service dependencies..
Not much to go...

Rich
  • 0

#25
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Thanks for the update and great detective work on your part.
:)
  • 0

Advertisements


#26
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Are you still having problems with your issue?
It has been 18 days since your last response and I was wondering if the issue has been resolved?
If so can you explain how it was resolved so others may be able to fix it if they have the same issue.
If not please let us know and we can continue with helping you to resolve the issue.
  • 0

#27
rriche

rriche

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
Dear Mr Shaffer...

Good timimg as have been on a break...
I have finally completed all the process as directed above..
In safe mode computer not freeze for over 3 days...
Next I unchecked the services and computer did not freeze
I then ran the individual tests by adding each item and waited 24hrs for freeze..
Initially I thought I had found the problem with what I thought were culprits...
However when I did a final check with all services unchecked again...The troublesome compter decided this time it will freeze...

In summary...Safe mode no freeze...
Computer will freeze in normal mode even if all services left unchecked...
Grrrrr..Thankyou for your patience...

Kind regards

Rich
  • 0

#28
devper94

devper94

    Member

  • Member
  • PipPipPip
  • 817 posts
I have an idea...

Does the freeze come exactly after 24 hours?
  • 0

#29
rriche

rriche

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
Not exactly....but usually 24 hrs give or take a couple of hours...

Rich
  • 0

#30
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Safe Mode no freeze indicates a driver or startup issue then.

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 and let system run for a minimum of 24 hours with everything unchecked.
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 and test for 24 hours each time.
Keep doing that till you have found the problem or all are finally checked.
Post back with the results
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP