MSFN Forum: ****stop 0x000000BB an initialization failure occured***** blue screen - MSFN Forum

Jump to content



Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

****stop 0x000000BB an initialization failure occured***** blue screen RIS or RIS integrated with WinPE Rate Topic: -----

#1 User is offline   ITpro 

  • Group: Members
  • Posts: 2
  • Joined: 15-December 06

Posted 15 December 2006 - 10:54 PM

The message on Blue screen is :
****stop : 0x000000BB (0x00000003,0xC00000C0,0x00000000,0x00000000)
an initialization failure occured while attempting to boot from network

if 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 software
disable 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. :yes:


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,
ITPro
MCSA 2003

This post has been edited by ITpro: 16 December 2006 - 04:46 PM



#2 User is offline   gsxr 

  • Group: Members
  • Posts: 6
  • Joined: 15-June 05

Posted 21 December 2006 - 08:01 AM

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

#3 User is offline   benowen187 

  • Newbie
  • Group: Members
  • Posts: 18
  • Joined: 18-July 06

Posted 07 March 2007 - 02:42 AM

Spot on with the lease issue, thanks a million, saved me a heap of time!! :thumbup

Cheers

Ben

#4 User is offline   TheMustangMan 

  • Group: Members
  • Posts: 1
  • Joined: 25-July 07

Posted 25 July 2007 - 03:37 AM

This actually works!! :thumbup :thumbup :thumbup

This post has been edited by TheMustangMan: 25 July 2007 - 03:38 AM


Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy