Wednesday, January 07, 2009
Deployment Forum HomeDeployment Forum ArticlesDeployment Forum Download LibraryDeployment Forum Member BlogsDeployment Forum Community Forums
Community   »   Forums  
Member Login
StandardLiveID


Register
Forgot Password ?

Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Forums > Deployment Solutions > Lite Touch
Subject: Deployment blue screens on bootup error 7B
Prev Next
You are not authorized to post a reply.

AuthorMessages
philUser is Offline

Posts:3

Send Message
10/10/2008 4:59 AM  

I am trying to integrate SP3 into our litetouch image and so far the only image i can get to work is the windows source files with SP3 integrated. 

I have successfully managed to capture an image, but whenever i deploy the image when windows boots up it blue screens with 0x0000007B error message.

after some investigation i found that this is supposed fixed by enabling the Set Diskpart BIOS Compatibility Mode in the task sequence, however this just crashes the deployment.

Is there anything else that causes this error?  I am using Dell GX150, GX240, GX280, D600, D610's and have never had this problem before when i was deploying and capturing SP2 images with the same task sequence.

any help would be much appreciated.

Phil

bn2huntUser is Offline

Posts:94

Send Message
10/10/2008 9:14 AM  
Whenever I have gotten the 7b BSOD it has been my sata drivers are out of date. Try downloading the latest from, I would guess intel since they are dells, and try that. We had to upgrade ours for sp3 in our dell gx280 custom image.
C BarrettUser is Offline

Posts:19

Send Message
10/11/2008 5:42 AM  
The 7B error is usually a mass storage driver issue - the best post I found on the internet for dealing with this issue is from Ben Hunter - click here to read the post - follow the steps and you should be up and running again in a few hours.

You can make the change in the BIOS if you want a quick fix but this will affect disk performance as you are essentially turning off a feature you have paid for.

Another fix would be to start using Vista which can handle the injection of mass storage drivers into the build process...XP can't and you have to rebuild your reference system, make the mass storgae drivers available on the build, sysprep and re-capture....but this is all described in Ben's post....

HTH

Carl

philUser is Offline

Posts:3

Send Message
10/16/2008 7:25 AM  

I have read through Ben's blog and successfully integrated the drivers (or at least i believe i have) and i have syspreped a new image with the drives added to the 
[SysprepMassStorage] section, but i am still getting the blue screen error 7B when i try and install the image on a GX280!

What i don't get is that all these blogs and posts relate to SP2 images but it was working fine with SP2 its only now im trying the rollout SP3 in the images that its messing up.

 

PS as easy as vista sounds to integrate into WDS the specs of the PC's we are using would not be able to cope with vista so thats not an option.

KonradUser is Offline

Posts:67

Send Message
10/16/2008 5:20 PM  
I had a problem recently when I added a 64bit Intel Sata driver into MDT that started causing problems with my 32bit XP builds. The .inf file included with the Intel driver tells you that it's for 32 and 64 bit XP, when it's actually just for 64 bit so my XP builds were trying to use this driver at which point they'd blue screen with 7B. If you're getting desperate you could try to check all the drivers that are being applied.

As an aside, I personally don't manually update the Sysprep's mass storage sections myself, I let MDT's ZTIStorageDriversSysprep.wsf do it for me. It works nice <img src=
philUser is Offline

Posts:3

Send Message
10/20/2008 8:53 AM  

I have checked the driver versions and as far as i can tell they are all for 32-bit or 64-bit.  What i don't get is that all the posts i have been reading are in relation to SP2 and needing the new driver but this problem occur when i was using SP2 its only since i've started using SP3.  and i think i am using a newer version of the driver as the names in the txtsetup.oem are different to the ones posted onall the forums.

also in Ben Hunter's blog it states to get the PnP ID's from the [Control Flags] section but my inf's just have the line ExcludeFromSelect=*

and later on states:

[Manufacturer]
%INTEL%=INTEL_HDC,ntamd64

[INTEL_HDC]
%PCI\VEN_8086&DEV_2681&CC_0106.DeviceDesc% = iaStor_Inst, PCI\VEN_8086&DEV_2681&CC_0106
%PCI\VEN_8086&DEV_27C1&CC_0106.DeviceDesc% = iaStor_Inst,PCI\VEN_8086&DEV_27C1&CC_0106
%PCI\VEN_8086&DEV_27C5&CC_0106.DeviceDesc% = iaStor_mobl_Inst,PCI\VEN_8086&DEV_27C5&CC_0106
%PCI\VEN_8086&DEV_2821&CC_0106.DeviceDesc% = iaStor_Inst, PCI\VEN_8086&DEV_2821&CC_0106
%PCI\VEN_8086&DEV_2829&CC_0106.DeviceDesc% = iaStor_mobl_Inst, PCI\VEN_8086&DEV_2829&CC_0106
%PCI\VEN_8086&DEV_2922&CC_0106.DeviceDesc% = iaStor_Inst, PCI\VEN_8086&DEV_2922&CC_0106
%PCI\VEN_8086&DEV_2929&CC_0106.DeviceDesc% = iaStor_mobl_Inst, PCI\VEN_8086&DEV_2929&CC_0106
%PCI\VEN_8086&DEV_3A02&CC_0106.DeviceDesc% = iaStor_Inst, PCI\VEN_8086&DEV_3A02&CC_0106
%PCI\VEN_8086&DEV_3A22&CC_0106.DeviceDesc% = iaStor_Inst, PCI\VEN_8086&DEV_3A22&CC_0106

[INTEL_HDC.ntamd64]
%PCI\VEN_8086&DEV_2681&CC_0106.DeviceDesc% = iaStor_Inst, PCI\VEN_8086&DEV_2681&CC_0106
%PCI\VEN_8086&DEV_27C1&CC_0106.DeviceDesc% = iaStor_Inst,PCI\VEN_8086&DEV_27C1&CC_0106
%PCI\VEN_8086&DEV_27C5&CC_0106.DeviceDesc% = iaStor_mobl_Inst,PCI\VEN_8086&DEV_27C5&CC_0106
%PCI\VEN_8086&DEV_2821&CC_0106.DeviceDesc% = iaStor_Inst, PCI\VEN_8086&DEV_2821&CC_0106
%PCI\VEN_8086&DEV_2829&CC_0106.DeviceDesc% = iaStor_mobl_Inst, PCI\VEN_8086&DEV_2829&CC_0106
%PCI\VEN_8086&DEV_2922&CC_0106.DeviceDesc% = iaStor_Inst, PCI\VEN_8086&DEV_2922&CC_0106
%PCI\VEN_8086&DEV_2929&CC_0106.DeviceDesc% = iaStor_mobl_Inst, PCI\VEN_8086&DEV_2929&CC_0106
%PCI\VEN_8086&DEV_3A02&CC_0106.DeviceDesc% = iaStor_Inst, PCI\VEN_8086&DEV_3A02&CC_0106
%PCI\VEN_8086&DEV_3A22&CC_0106.DeviceDesc% = iaStor_Inst, PCI\VEN_8086&DEV_3A22&CC_0106

 

so i have been using these, would deleting all the ntamd64 entries dfrom the inf's stop them from being loaded or just crash the whole thing?

You are not authorized to post a reply.
Forums > Deployment Solutions > Lite Touch > Deployment blue screens on bootup error 7B



ActiveForums 3.7
Forum Policies
Minimize

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

  • We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
  • Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
  • Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
  • Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
  • Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
  • Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.
Privacy Statement  |  Terms Of Use
© 2007 Jerry Honeycutt