Computer hanging/freezing with NetBt Stop Error EventID: 4307

shocker · 11-11-2007

I'm runing 3GB memory and I have plenty of disk space on Windows Server 2003.
I haven't added any new hardward in months.

Originally I was getting this error

***********************************
Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4307
Date: 11/10/2007
Time: 3:04:03 PM
User: N/A
Computer: WSEDU01
Description:
Initialization failed because the transport refused to open initial Addresses.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 01 00 58 00 ......X.
0008: 00 00 00 00 d3 10 00 c0 ....Ã“..Ã€
0010: 01 00 00 00 07 02 00 c0 .......Ã€
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
***********************************

I did some searching on Google and found suggestions about running
netsh int ip reset reset.log

I also deselected WINS

After this, the computer is still crashing (not as frequently). Now the
Event that is generated is as follows...

***********************************
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 11/10/2007
Time: 8:50:17 PM
User: N/A
Computer: WSEDU01
Description:
Error code 0000004e, parameter1 00000099, parameter2 0002211d, parameter3
00000000, parameter4 00000000.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 34 0000004
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 39 39 2c 20 000099,
0038: 30 30 30 32 32 31 31 64 0002211d
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000

Dave Patrick · 11-11-2007

These articles may help.

http://support.microsoft.com/kb/895473/en-us
http://support.microsoft.com/kb/894061/en-us
http://support.microsoft.com/kb/244617/en-us

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"shocker" wrote:
> I'm runing 3GB memory and I have plenty of disk space on Windows Server
> 2003.
> I haven't added any new hardward in months.
>
>
> Originally I was getting this error
>
> ***********************************
> Event Type: Error
> Event Source: NetBT
> Event Category: None
> Event ID: 4307
> Date: 11/10/2007
> Time: 3:04:03 PM
> User: N/A
> Computer: WSEDU01
> Description:
> Initialization failed because the transport refused to open initial
> Addresses.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 00 00 00 00 01 00 58 00 ......X.
> 0008: 00 00 00 00 d3 10 00 c0 ....Ã“..Ã€
> 0010: 01 00 00 00 07 02 00 c0 .......Ã€
> 0018: 00 00 00 00 00 00 00 00 ........
> 0020: 00 00 00 00 00 00 00 00 ........
> ***********************************
>
> I did some searching on Google and found suggestions about running
> netsh int ip reset reset.log
>
> I also deselected WINS
>
> After this, the computer is still crashing (not as frequently). Now the
> Event that is generated is as follows...
>
>
> ***********************************
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 11/10/2007
> Time: 8:50:17 PM
> User: N/A
> Computer: WSEDU01
> Description:
> Error code 0000004e, parameter1 00000099, parameter2 0002211d, parameter3
> 00000000, parameter4 00000000.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 53 79 73 74 65 6d 20 45 System E
> 0008: 72 72 6f 72 20 20 45 72 rror Er
> 0010: 72 6f 72 20 63 6f 64 65 ror code
> 0018: 20 30 30 30 30 30 30 34 0000004
> 0020: 65 20 20 50 61 72 61 6d e Param
> 0028: 65 74 65 72 73 20 30 30 eters 00
> 0030: 30 30 30 30 39 39 2c 20 000099,
> 0038: 30 30 30 32 32 31 31 64 0002211d
> 0040: 2c 20 30 30 30 30 30 30 , 000000
> 0048: 30 30 2c 20 30 30 30 30 00, 0000
> 0050: 30 30 30 30 0000
>

shocker · 13-11-2007

Thanks Dave for responding.

I began by referring to the driver verification program in this KB
http://support.microsoft.com/kb/244617/en-us

after running the program and rebooting the computer is in a boot loop,
never progressing passed the Windows start up screen. There is blue screen
that flashes (but not long enought to read it) before the computer attempt to
boot again.

I'll probably have to Safe Mode to get the computer to boot.

Is there anything you can add to shed some light on this?

"Dave Patrick" wrote:

> These articles may help.
>
> http://support.microsoft.com/kb/895473/en-us
> http://support.microsoft.com/kb/894061/en-us
> http://support.microsoft.com/kb/244617/en-us
>
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "shocker" wrote:
> > I'm runing 3GB memory and I have plenty of disk space on Windows Server
> > 2003.
> > I haven't added any new hardward in months.
> >
> >
> > Originally I was getting this error
> >
> > ***********************************
> > Event Type: Error
> > Event Source: NetBT
> > Event Category: None
> > Event ID: 4307
> > Date: 11/10/2007
> > Time: 3:04:03 PM
> > User: N/A
> > Computer: WSEDU01
> > Description:
> > Initialization failed because the transport refused to open initial
> > Addresses.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: 00 00 00 00 01 00 58 00 ......X.
> > 0008: 00 00 00 00 d3 10 00 c0 ....Ã“..Ã€
> > 0010: 01 00 00 00 07 02 00 c0 .......Ã€
> > 0018: 00 00 00 00 00 00 00 00 ........
> > 0020: 00 00 00 00 00 00 00 00 ........
> > ***********************************
> >
> > I did some searching on Google and found suggestions about running
> > netsh int ip reset reset.log
> >
> > I also deselected WINS
> >
> > After this, the computer is still crashing (not as frequently). Now the
> > Event that is generated is as follows...
> >
> >
> > ***********************************
> > Event Type: Error
> > Event Source: System Error
> > Event Category: (102)
> > Event ID: 1003
> > Date: 11/10/2007
> > Time: 8:50:17 PM
> > User: N/A
> > Computer: WSEDU01
> > Description:
> > Error code 0000004e, parameter1 00000099, parameter2 0002211d, parameter3
> > 00000000, parameter4 00000000.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: 53 79 73 74 65 6d 20 45 System E
> > 0008: 72 72 6f 72 20 20 45 72 rror Er
> > 0010: 72 6f 72 20 63 6f 64 65 ror code
> > 0018: 20 30 30 30 30 30 30 34 0000004
> > 0020: 65 20 20 50 61 72 61 6d e Param
> > 0028: 65 74 65 72 73 20 30 30 eters 00
> > 0030: 30 30 30 30 39 39 2c 20 000099,
> > 0038: 30 30 30 32 32 31 31 64 0002211d
> > 0040: 2c 20 30 30 30 30 30 30 , 000000
> > 0048: 30 30 2c 20 30 30 30 30 00, 0000
> > 0050: 30 30 30 30 0000
> >
>

Dave Patrick · 14-11-2007

Yes, I'd try the 'Safe Mode' boot. You might also try a boot floppy with the
/sos and /basevideo switches in boot.ini

http://support.microsoft.com/kb/833721

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"shocker" wrote:
> Thanks Dave for responding.
>
> I began by referring to the driver verification program in this KB
> http://support.microsoft.com/kb/244617/en-us
>
> after running the program and rebooting the computer is in a boot loop,
> never progressing passed the Windows start up screen. There is blue screen
> that flashes (but not long enought to read it) before the computer attempt
> to
> boot again.
>
> I'll probably have to Safe Mode to get the computer to boot.
>
> Is there anything you can add to shed some light on this?

shocker · 14-11-2007

I've recovered from the boot loop by boot to safe mode and turing off the
verifier tool.

What does this mean if I can't run the tool? Something must certainly be
wrong.

Do you have a suggestion on how to proceed?

"Dave Patrick" wrote:

> Yes, I'd try the 'Safe Mode' boot. You might also try a boot floppy with the
> /sos and /basevideo switches in boot.ini
>
> http://support.microsoft.com/kb/833721
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "shocker" wrote:
> > Thanks Dave for responding.
> >
> > I began by referring to the driver verification program in this KB
> > http://support.microsoft.com/kb/244617/en-us
> >
> > after running the program and rebooting the computer is in a boot loop,
> > never progressing passed the Windows start up screen. There is blue screen
> > that flashes (but not long enought to read it) before the computer attempt
> > to
> > boot again.
> >
> > I'll probably have to Safe Mode to get the computer to boot.
> >
> > Is there anything you can add to shed some light on this?
>

shocker · 15-11-2007

I'm posting my minidump to a web directory

http://www.musikdebu.com/najib/Minidump.rar

I hope you can shed some light on this.

"Dave Patrick" wrote:

> Yes, I'd try the 'Safe Mode' boot. You might also try a boot floppy with the
> /sos and /basevideo switches in boot.ini
>
> http://support.microsoft.com/kb/833721
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "shocker" wrote:
> > Thanks Dave for responding.
> >
> > I began by referring to the driver verification program in this KB
> > http://support.microsoft.com/kb/244617/en-us
> >
> > after running the program and rebooting the computer is in a boot loop,
> > never progressing passed the Windows start up screen. There is blue screen
> > that flashes (but not long enought to read it) before the computer attempt
> > to
> > boot again.
> >
> > I'll probably have to Safe Mode to get the computer to boot.
> >
> > Is there anything you can add to shed some light on this?
>

Dave Patrick · 15-11-2007

This might suggest some bad hardware and or driver corruption. I suppose I'd
start with RAM, network interface, and graphics adapter.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"shocker" wrote:
> I've recovered from the boot loop by boot to safe mode and turing off the
> verifier tool.
>
> What does this mean if I can't run the tool? Something must certainly be
> wrong.
>
> Do you have a suggestion on how to proceed?