ITpro Posted December 16, 2006 Share Posted December 16, 2006 (edited) The message on Blue screen is :****stop : 0x000000BB (0x00000003,0xC00000C0,0x00000000,0x00000000)an initialization failure occured while attempting to boot from networkif this is the first time you've seen this, stop error screen, restart your computer,if this screen appears again (yes screen appears again)follow these steps :check to make sure any new hardware or software is properly installed if this is a new installation, ask your hardware or software manufacture for any windows 2000 update you might need if the problem continue, disable or remove any newly installation hardware or softwaredisable bios memory option such as caching or shadowing.if you need to use safe mode to remove or disable components, restart your computer press F8 to select advanced startup option and then select safe mode refer to your getting started manual for more information on troubleshooting stop errors.SOLUTION:---don't waste anymore time troubleshooting this generic message---This is nothing more than a corrupted DHCP lease causing the blue screen that can sometimes happen when booting in PXE/RIS due to DC, DHCP and RIS timing issues.To clean things up, delete DHCP lease first then you must force renewal of a completely different IP.1. Search DHCP server for IP, delete the lease and statically assign that same IP address to a live machine on the network. The lease expires by default in 8 days, you don't want to wait this duration if you need to restore an image.Number of ways to force renewal from desktop but the IP you want to release is Pre-Winows.2. Configure a live machine with the static IP that is being assigned to the computer giving you the blue screen. You can determine the IP by booting the problem machine and writing down the IP assigned during PXE.Why assign the static IP to another machine?You will get the BSOD all over again if you don't...Simple if you understand DHCP remember D.O.R.A? Discover, offer, request, acknowledge.Clients request the same IP during renegotiation process at the end of any lease. By default DHCP will offer the same IP (remembers your MAC). That said, with the lease deleted and the IP statically assigned to another machine DHCP server will then ping the address and see that it is currently being used by another machine. It will then provide a new IP address and new lease to avoid any conflict, exactly what we want. No need to do anything else...once the problem computer obtains a new lease with different IP from DHCP, the system will boot into a RIS or WinPE environment with no problem.R,ITProMCSA 2003 Edited December 16, 2006 by ITpro Link to comment Share on other sites More sharing options...
gsxr Posted December 21, 2006 Share Posted December 21, 2006 Had the same message and this was caused by the broadcom driver i added.The fix is already posted on this forum about changing the inf file from broadcom.Cheers Link to comment Share on other sites More sharing options...
benowen187 Posted March 7, 2007 Share Posted March 7, 2007 Spot on with the lease issue, thanks a million, saved me a heap of time!! Cheers Ben Link to comment Share on other sites More sharing options...
TheMustangMan Posted July 25, 2007 Share Posted July 25, 2007 (edited) This actually works!! Edited July 25, 2007 by TheMustangMan Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now