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