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

XP keeps crashing after a few minutes


  • Please log in to reply

#1
schmelfhelp

schmelfhelp

    Member

  • Member
  • PipPip
  • 12 posts
Hi

Windows keeps crashing - it sends an error report with the following
BCCode : 10000050 BCP1 : E1719FF0 BCP2 : 00000000 BCP3 : F7B7F495
BCP4 : 00000001 OSVer : 5_1_2600 SP : 3_0 Product : 256_1

Any ideas what this means?

Thanks
Tara
  • 0

Advertisements


#2
rev_olie

rev_olie

    Member

  • Member
  • PipPipPip
  • 532 posts
Hi Tara

Welcome to GeeksToGo :)

Please download VEW and save it to your Desktop:

Setting up the program
Double-click VEW.exe then under Select log to query, select:
  • Application
  • System
Under Select type to list, select:
  • Critical (Vista only)
  • Error
  • Click the radio button for Number of events
  • Type 20 in the 1 to 20 box
  • Then click the Run button.
  • Notepad will open with the output log.
Load the log
  • In Notepad, click Edit > Select all
  • Then press Edit > Copy
  • Press Ctrl+V on your keyboard to paste the log to your next reply.

  • 0

#3
schmelfhelp

schmelfhelp

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
sorry for the slow reply - I left for holiday just after this message.
I have some stop errors now - so i don't know if that helps -
here are the stop codes

0x0000008E
0xC0000005, 0xBF8011CA, 0XF7576A48, 0X00000000
win32k.sys address BF800000


Here is the error log.

Vino's Event Viewer v01c run on Windows XP in English
Report run at 29/09/2009 10:02:38

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 29/09/2009 9:23:18
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application wuauclt.exe, version 7.2.6001.788, faulting module msvcrt.dll, version 7.0.2600.5512, fault address 0x000435e7.

Log: 'Application' Date/Time: 29/09/2009 9:22:59
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application fsdfwd.exe, version 6.22.109.0, faulting module FSMA32.DLL, version 8.0.14008.0, fault address 0x00003230.

Log: 'Application' Date/Time: 29/09/2009 9:22:27
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application FSMB32.EXE, version 8.0.14008.0, faulting module FSMB32.EXE, version 8.0.14008.0, fault address 0x00010397.

Log: 'Application' Date/Time: 17/09/2009 19:50:50
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application Illustrator.exe, version 14.0.128.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 14/09/2009 19:58:09
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application Illustrator.exe, version 14.0.128.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 14/09/2009 13:35:01
Type: error Category: 0
Event: 103 Source: F-Secure Anti-Virus
The event description cannot be found.

Log: 'Application' Date/Time: 10/09/2009 18:56:37
Type: error Category: 0
Event: 20 Source: Google Update
The event description cannot be found.

Log: 'Application' Date/Time: 10/09/2009 15:45:24
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application eclipse.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 10/09/2009 13:49:03
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application eclipse.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 09/09/2009 17:10:02
Type: error Category: 0
Event: 11316 Source: MsiInstaller
Product: Internet Explorer Developer Toolbar -- Error 1316. A network error occurred while attempting to read from the file: C:\Program Files\Internet Explorer Collection\IEDevToolBarSetup[1].msi

Log: 'Application' Date/Time: 09/09/2009 16:54:52
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application iTunes.exe, version 8.2.1.6, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 09/09/2009 16:38:02
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application eclipse.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 09/09/2009 12:23:47
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application iexplore.exe, version 7.0.5730.13, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 09/09/2009 11:14:26
Type: error Category: 0
Event: 103 Source: F-Secure Anti-Virus
The event description cannot be found.

Log: 'Application' Date/Time: 07/09/2009 17:32:26
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application eclipse.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 03/09/2009 9:08:06
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application FSM32.EXE, version 8.0.14008.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 03/09/2009 9:08:05
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application FSM32.EXE, version 8.0.14008.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 03/09/2009 9:08:05
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application FSM32.EXE, version 8.0.14008.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 01/09/2009 16:12:55
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application iexplore.exe, version 7.0.5730.13, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 01/09/2009 12:17:36
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application iexplore.exe, version 7.0.5730.13, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/09/2009 10:00:57
Type: error Category: 0
Event: 8009 Source: BROWSER
The browser was unable to promote itself to master browser. The computer that currently believes it is the master browser is YKSI.

Log: 'System' Date/Time: 29/09/2009 10:00:57
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 29/09/2009 9:55:47
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 29/09/2009 9:50:37
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 29/09/2009 9:45:27
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 29/09/2009 9:40:55
Type: error Category: 102
Event: 1003 Source: System Error
Error code 1000007e, parameter1 c0000005, parameter2 b0cdb46a, parameter3 baf22cb0, parameter4 baf229ac.

Log: 'System' Date/Time: 29/09/2009 9:40:17
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 29/09/2009 9:40:03
Type: error Category: 102
Event: 1003 Source: System Error
Error code 100000d1, parameter1 a2a0a6fc, parameter2 00000002, parameter3 00000000, parameter4 a2a0a6fc.

Log: 'System' Date/Time: 29/09/2009 9:29:50
Type: error Category: 102
Event: 1003 Source: System Error
Error code 100000d1, parameter1 a2a0a6fc, parameter2 00000002, parameter3 00000000, parameter4 a2a0a6fc.

Log: 'System' Date/Time: 29/09/2009 9:29:32
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 29/09/2009 9:28:46
Type: error Category: 2
Event: 55 Source: Ntfs
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:.

Log: 'System' Date/Time: 29/09/2009 9:22:08
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 29/09/2009 9:17:08
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 17/09/2009 20:03:53
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 17/09/2009 19:58:43
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 17/09/2009 19:53:33
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 17/09/2009 19:48:23
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 17/09/2009 19:43:13
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 17/09/2009 19:38:03
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 17/09/2009 19:32:53
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.
  • 0

#4
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
this ...

The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume

go here..download the following file: rc.iso....then run chkdsk /r from the rc.iso cd...be sure the bios is set to boot from the cd drive first...

if you don't have a burning program that will burn .ISO files go here and get burncdcc ..a small FAST no frills iso burning program...

NOTE...do not put a blank cd in until burncdcc opens the tray for you
1. Start by clicking on BurnCDCC.exe
2. Browse to the ISO file you want to burn on cd/dvd ....in this case its rc.iso
3. Select the ISO file
4. click on Start

make sure in the bios the cd drive is the first boot device....put the cd in the cd drive..boot your computer....

boot from the rc.iso cd....
type in chkdsk /r press enter
note the single space before the /

Chkdsk will display the specific stage it is checking as well as the percentage of completion of the stage. You cannot do anything else on your computer while chkdsk is running. When chkdsk is finished, it will automatically reboot your computer.
NOTE this can take a long time to complete..it may even appear to hang or get stuck at a certain % for a couple of hours...then complete
it may even back up and go over the same area...this is normal...let it run...there are 5 stages
DO NOT TURN OFF YOUR COMPUTER WHILE RUNNING CHKDSK or you can have severe problems...
  • 0

#5
schmelfhelp

schmelfhelp

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
hi

Ok I ran chkdsk... should I see any messages now or is there a log file to see if that fixed the problem?
  • 0

#6
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
Go to Start... Run...and type in eventvwr.msc /s... press enter
When Event Viewer opens, click on Application...
then scroll down to Winlogon and double-click on it. This is the log created after running Checkdisk.
copy and paste it here...
are you still crashing after running chkdsk...is so then run VEW again but only put 5 in the box for number of events
  • 0

#7
schmelfhelp

schmelfhelp

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
here it is thanks:)

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 6 unused index entries from index $SII of file 0x9.
Cleaning up 6 unused index entries from index $SDH of file 0x9.
Cleaning up 6 unused security descriptors.
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.

36869143 KB total disk space.
29709204 KB in 167187 files.
89728 KB in 28505 indexes.
0 KB in bad sectors.
280987 KB in use by the system.
65536 KB occupied by the log file.
6789224 KB available on disk.

4096 bytes in each allocation unit.
9217285 total allocation units on disk.
1697306 allocation units available on disk.

Internal Info:
00 25 03 00 77 fc 02 00 e0 ec 04 00 00 00 00 00 .%..w...........
3c 03 00 00 02 00 00 00 a4 04 00 00 00 00 00 00 <...............
34 0f 62 05 00 00 00 00 a0 a7 f3 f0 00 00 00 00 4.b.............
96 88 1d 0f 00 00 00 00 78 da a7 82 05 00 00 00 ........x.......
e4 aa f4 94 00 00 00 00 90 6d 72 24 07 00 00 00 .........mr$....
99 9e 36 00 00 00 00 00 98 38 07 00 13 8d 02 00 ..6......8......
00 00 00 00 00 50 4e 15 07 00 00 00 59 6f 00 00 .....PN.....Yo..

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


For more information, see Help and Support Center at
  • 0

#8
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
are you still crashing after running chkdsk...if so run VEW again
  • 0

#9
schmelfhelp

schmelfhelp

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
hi yep it's crashing again

here is the log from vew
Vino's Event Viewer v01c run on Windows XP in English
Report run at 08/10/2009 11:21:26

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 08/10/2009 11:14:24
Type: error Category: 0
Event: 103 Source: F-Secure Anti-Virus
The event description cannot be found.

Log: 'Application' Date/Time: 08/10/2009 11:08:19
Type: error Category: 0
Event: 103 Source: F-Secure Management Agent
3 2009-10-06 10:22:20+03:00 thinkcentre SYSTEM F-Secure Management Agent The module F-Secure Automatic Update Agent monitored by F-Secure Management Agent has stopped responding or was terminated. An attempt to restart it will be made later. If you see this message frequently, contact the system administrator or reinstall F-Secure products.

Log: 'Application' Date/Time: 08/10/2009 11:08:19
Type: error Category: 0
Event: 103 Source: F-Secure Management Agent
2 2009-10-06 10:22:20+03:00 thinkcentre SYSTEM F-Secure Management Agent The module F-Secure ORSP Client monitored by F-Secure Management Agent has stopped responding or was terminated. An attempt to restart it will be made later. If you see this message frequently, contact the system administrator or reinstall F-Secure products.

Log: 'Application' Date/Time: 08/10/2009 11:08:19
Type: error Category: 0
Event: 103 Source: F-Secure Management Agent
1 2009-10-06 10:22:20+03:00 thinkcentre SYSTEM F-Secure Management Agent The module F-Secure Anti-Virus Firewall Daemon monitored by F-Secure Management Agent has stopped responding or was terminated. An attempt to restart it will be made later. If you see this message frequently, contact the system administrator or reinstall F-Secure products.

Log: 'Application' Date/Time: 06/10/2009 4:00:59
Type: error Category: 0
Event: 103 Source: F-Secure Anti-Virus
The event description cannot be found.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 08/10/2009 11:21:06
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 08/10/2009 11:16:34
Type: error Category: 102
Event: 1003 Source: System Error
Error code 00000019, parameter1 00000020, parameter2 e16f7df0, parameter3 e16f7e20, parameter4 0c060201.

Log: 'System' Date/Time: 08/10/2009 11:15:56
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 08/10/2009 11:13:43
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 08/10/2009 11:08:33
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.
  • 0

#10
schmelfhelp

schmelfhelp

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
one more thing is last week after chkdsk we defragged the hard drive (It took about 6 hours)

I looked at the windows event viewer and there are lots of errors

ones from today are in system errors

Error code 1000007f, parameter1 0000000d, parameter2 00000000, parameter3 00000000, parameter4 00000000.

and

The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

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


and in application errors there is

The description for Event ID ( 103 ) in Source ( F-Secure Anti-Virus ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 4 2009-10-08 11:14:23+03:00 thinkcentre THINKCENTRE\Tara F-Secure Anti-Virus
Crash detected.
\Device\HarddiskVolume1\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83\comctl32.dll \Device\HarddiskVolume1\WINDOWS\system32\psapi.dll

3 2009-10-06 10:22:20+03:00 thinkcentre SYSTEM F-Secure Management Agent
The module F-Secure Automatic Update Agent monitored by F-Secure Management Agent has stopped responding or was terminated. An attempt to restart it will be made later. If you see this message frequently, contact the system administrator or reinstall F-Secure products.

(this last one is repeated)


F-secure is the antivirus software we are using.
  • 0

#11
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
for starters uninstall F-Secure and the folder it lived in and try a different free anti-virus like AVG...
avast!...OR Avira ...
if your crashing stops we will know it was F-Secure
  • 0

#12
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
I have to agree with Happyrock on this one. Everything looks to be pointing at F-Secure as the main problem.
His suggestions for a AV are sound and it will most likely stop the issue from happening.
:) :) :)
  • 0

#13
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
welcome back... SLACKER.. :) :) :)
  • 0

#14
schmelfhelp

schmelfhelp

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
Hi again
Ok so this is my work computer and we use f-secure so I can't change that. I reinstalled F-secure though and this seemed to fix things for a while but it's starting to crash again.. anyone have some links to information that avg is as good as f-secure (or better)

anyway the windows event log keeps mentioning netBT as a problem
here is the VEW log
Vino's Event Viewer v01c run on Windows XP in English
Report run at 28/10/2009 10:50:53

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 21/10/2009 10:24:44
Type: error Category: 0
Event: 103 Source: F-Secure Anti-Virus
The event description cannot be found.

Log: 'Application' Date/Time: 21/10/2009 10:16:40
Type: error Category: 0
Event: 103 Source: F-Secure Anti-Virus
The event description cannot be found.

Log: 'Application' Date/Time: 15/10/2009 18:08:51
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application eclipse.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 14/10/2009 15:35:57
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application eclipse.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 14/10/2009 12:48:38
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application Illustrator.exe, version 14.0.128.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 12/10/2009 13:10:32
Type: error Category: 0
Event: 103 Source: F-Secure Anti-Virus
The event description cannot be found.

Log: 'Application' Date/Time: 12/10/2009 12:17:44
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application iTunes.exe, version 9.0.0.70, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 12/10/2009 11:17:14
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application iTunes.exe, version 9.0.0.70, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 08/10/2009 11:14:24
Type: error Category: 0
Event: 103 Source: F-Secure Anti-Virus
The event description cannot be found.

Log: 'Application' Date/Time: 08/10/2009 11:08:19
Type: error Category: 0
Event: 103 Source: F-Secure Management Agent
The event description cannot be found.

Log: 'Application' Date/Time: 08/10/2009 11:08:19
Type: error Category: 0
Event: 103 Source: F-Secure Management Agent
The event description cannot be found.

Log: 'Application' Date/Time: 08/10/2009 11:08:19
Type: error Category: 0
Event: 103 Source: F-Secure Management Agent
The event description cannot be found.

Log: 'Application' Date/Time: 06/10/2009 4:00:59
Type: error Category: 0
Event: 103 Source: F-Secure Anti-Virus
The event description cannot be found.

Log: 'Application' Date/Time: 06/10/2009 3:49:55
Type: error Category: 0
Event: 103 Source: F-Secure Management Agent
The event description cannot be found.

Log: 'Application' Date/Time: 06/10/2009 1:53:38
Type: error Category: 0
Event: 103 Source: F-Secure Anti-Virus
The event description cannot be found.

Log: 'Application' Date/Time: 06/10/2009 1:48:38
Type: error Category: 0
Event: 103 Source: F-Secure Anti-Virus
The event description cannot be found.

Log: 'Application' Date/Time: 06/10/2009 1:48:38
Type: error Category: 0
Event: 103 Source: F-Secure Anti-Virus
The event description cannot be found.

Log: 'Application' Date/Time: 05/10/2009 10:03:34
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application fsdfwd.exe, version 6.22.109.0, faulting module fsdfwd.exe, version 6.22.109.0, fault address 0x0004c80b.

Log: 'Application' Date/Time: 01/10/2009 14:47:09
Type: error Category: 0
Event: 103 Source: F-Secure Anti-Virus
The event description cannot be found.

Log: 'Application' Date/Time: 01/10/2009 14:45:07
Type: error Category: 0
Event: 103 Source: F-Secure Anti-Virus
The event description cannot be found.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 28/10/2009 10:48:15
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 28/10/2009 10:43:05
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 28/10/2009 10:42:59
Type: error Category: 102
Event: 1003 Source: System Error
Error code 1000008e, parameter1 c0000005, parameter2 bf80560b, parameter3 aff0e320, parameter4 00000000.

Log: 'System' Date/Time: 28/10/2009 10:38:46
Type: error Category: 102
Event: 1003 Source: System Error
Error code 1000007f, parameter1 00000008, parameter2 80042000, parameter3 00000000, parameter4 00000000.

Log: 'System' Date/Time: 28/10/2009 10:38:09
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 28/10/2009 10:37:57
Type: error Category: 102
Event: 1003 Source: System Error
Error code 1000008e, parameter1 c0000005, parameter2 bf80568a, parameter3 af0f5ba0, parameter4 00000000.

Log: 'System' Date/Time: 28/10/2009 10:36:12
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 28/10/2009 10:30:20
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 26/10/2009 16:54:14
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 26/10/2009 16:49:04
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 26/10/2009 16:43:54
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 26/10/2009 16:38:44
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 26/10/2009 16:33:34
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 26/10/2009 16:28:24
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 26/10/2009 16:23:14
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 26/10/2009 16:18:04
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 26/10/2009 16:12:54
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 26/10/2009 16:07:44
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 26/10/2009 16:02:34
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.

Log: 'System' Date/Time: 26/10/2009 15:57:24
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP :1d" could not be registered on the Interface with IP address 192.168.1.231. The machine with the IP address 192.168.1.11 did not allow the name to be claimed by this machine.
  • 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