blanalex Posted January 25, 2011 Share Posted January 25, 2011 (edited) At work, we've got a new batch of netbooks and I am tasked to adapt our current XP-based image to it. After adding the necessary mass storage driver to sysprep.inf and checking that the correct HAL is installed, the netbooks always give a BSOD 0x0000007E.Netbook model is Lenovo ThinkPad X100e.I've tried many things, removing anything from my that might conflict. I'm down to the following procedure and still getting the same BSOD.Install Windows XP SP3 from a USB key (usb key made with WinSetupFromUSB). The AMD ahcix86 had been patched into the setup prior to WinSetupFromUSB.Once Windows installed, I added my driver library from a USB key and everything got detected. No exclamation or question marks in the device manager.I ran sysprep to reseal the machine.After the machine shut down, I ghosted the resulting image to a VMWare machine.After imaging, both the X100e and the VMWare machine are running perfectly.I sysprep/reseal the VMware machine with the exact same sysprep configuration as in step 3.Ghost over the sysprep'd image to the X100eSTOP: 0x0000007E (0xC0000005,0xF76A2756,0xF79B942C,0xF79B9128) on the X100e, VM is fine.This is the sysprep.inf I used:;SetupMgrTag[Unattended] OemSkipEula=Yes InstallFilesPath=C:\sysprep\i386 TargetPath=\WINDOWS; UpdateHAL = ACPIPIC_UP,%WINDIR%\inf\hal.inf; UpdateHAL = ACPIAPIC_UP,%WINDIR%\inf\hal.inf[GuiUnattended] AdminPassword=* EncryptedAdminPassword=NO OEMSkipRegional=1 TimeZone=35 OemSkipWelcome=1 AutoLogon = Yes AutoLogonCount = 1[GuiRunOnce] Command0="reg add HKLM\SYSTEM\CurrentControlSet\Control\CrashControl /V AutoReboot /t REG_DWORD /d 0 /f" Command1="cmd /c del %windir%\system32\$winnt$.inf"[UserData] ProductKey=ABCDE-FGHIJ-KLMNO-PQRST-XYZ12 FullName="Company name" OrgName="Company Name" ComputerName=*[TapiLocation] CountryCode=107 AreaCode=450[RegionalSettings] LanguageGroup=1 SystemLocale=00000c0c UserLocale=00000c0c InputLocale=0c0c:00001009[Identification] JoinWorkgroup=MASTER; JoinDomain=domain.company.local; DomainAdmin=sysprep; DomainAdminPassword=confidential[Networking] InstallDefaultComponents=Yes[Sysprep][SysprepMassStorage]; Bunch of lines removed to keep this short; generated with sysprep -bmsd; and cleaned up to remove unused; SCSI and exotic devices PCI\VEN_8086&DEV_2681&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_27C1&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_27C5&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_2821&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_2829&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_2922&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_2929&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_3A22&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_3A02&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_3B29&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_3B2F&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_3B22&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_3B29&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_3B2F&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_3B22&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_1C02&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_1C03&CC_0106=c:\drivers\intelsata\iaahci.infPCI\VEN_8086&DEV_2682&CC_0104=c:\drivers\intelsata\iastor.infPCI\VEN_8086&DEV_27C3&CC_0104=c:\drivers\intelsata\iastor.infPCI\VEN_8086&DEV_27C6&CC_0104=c:\drivers\intelsata\iastor.infPCI\VEN_8086&DEV_2822&CC_0104=c:\drivers\intelsata\iastor.infPCI\VEN_8086&DEV_282A&CC_0104=c:\drivers\intelsata\iastor.infPCI\VEN_1002&DEV_4380&SUBSYS_280A103C=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_2814103C=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4392=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4391=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4393=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_101E1462=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_10221462=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_10201462=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_305817AA=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_305717AA=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_2A89103C=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_00421B0A=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_00431B0A=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_3054103C=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_3055103C=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_0184107B=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_0FFF0FFF=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_B0051458=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_B0031458=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_02131025=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_02111025=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_02161025=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_6B311462=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_6B321462=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_021D1025=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4381&SUBSYS_43811002=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_43821002=c:\drivers\amdahci\ahcix86.infPCI\VEN_1002&DEV_4380&SUBSYS_43811002=c:\drivers\amdahci\ahcix86.inf[Display] BitsPerPel=32 Xresolution=1024 YResolution=768 Edited January 28, 2011 by blanalex Link to comment Share on other sites More sharing options...
cdob Posted January 25, 2011 Share Posted January 25, 2011 Long shot: don't use iastor.sys version 9.x. Link to comment Share on other sites More sharing options...
blanalex Posted January 26, 2011 Author Share Posted January 26, 2011 (edited) Long shot: don't use iastor.sys version 9.x.I already have version 10.1 in my driver library, but I'll give it a try without iaStor. Edited January 26, 2011 by blanalex Link to comment Share on other sites More sharing options...
blanalex Posted January 26, 2011 Author Share Posted January 26, 2011 Nope, it didn't work. I removed all the non-microsoft drivers and I upgraded the AMD AHCI driver with the one supplied on Lenovo's website. Link to comment Share on other sites More sharing options...
Tripredacus Posted January 26, 2011 Share Posted January 26, 2011 So basically you only experience a problem after you capture the image from the VM and apply it to the notebook? Is this a normal procedure for imaging (VM to hardware)? I never used VM for any imaging so I have no idea Link to comment Share on other sites More sharing options...
Ponch Posted January 27, 2011 Share Posted January 27, 2011 Is this a normal procedure for imaging (VM to hardware)?Exactly. What happen if you jump from point 4 to 7 ? (What's the idea behind points 5-6?) Link to comment Share on other sites More sharing options...
blanalex Posted January 27, 2011 Author Share Posted January 27, 2011 (edited) Well, I've also tried copying the image to a real PC, booting it up, reseal it, transfer it back to the netbook and it gives me a BSOD. The point of all this is I want my image to be universal across different models. I never counted how many models my current image supports, but I guess I can install it at least on 12-15 different models without needing to add any drivers afterwards.In the procedure I described at the top of the thread, I could've created the original master on a VM or on another model of computer, but then I wouldn't be sure if it's because the source machine is incompatible with the netbook.EDIT: Creating a new master image on a X100e and using it only on other X100e's works, but I already have a standard image with a ton of customization work done on it. I'd like to avoid to start a master image from scratch. The procedure described here is to show how much I've tried to isolate the problem. My hope is to find a solution to this puzzle with this context and I would be able to fix my current master image so it will work on this model of netbook. Edited January 27, 2011 by blanalex Link to comment Share on other sites More sharing options...
Ponch Posted January 28, 2011 Share Posted January 28, 2011 Netbook model is Lenovo ThinkPad X100e.Lenovo says it has AMD processor ... that is probably your problem. You can't mix them Intel and AMD sysprepped images. Link to comment Share on other sites More sharing options...
cdob Posted January 28, 2011 Share Posted January 28, 2011 but I already have a standard image with a ton of customization work done on it.Does this image load intelppm.sys at default?http://support.microsoft.com/kb/953356/Set driver intelppm to demand start=3. Link to comment Share on other sites More sharing options...
blanalex Posted January 28, 2011 Author Share Posted January 28, 2011 but I already have a standard image with a ton of customization work done on it.Does this image load intelppm.sys at default?http://support.microsoft.com/kb/953356/Set driver intelppm to demand start=3.OMFG! YES! This is it! It's working now! I can finally sleep! Link to comment Share on other sites More sharing options...
cdob Posted January 28, 2011 Share Posted January 28, 2011 Can you clarify: which part did include intelppm.sys?Did you boot standard image at AMD processors only? Did you boot standard image at a Intel processor?Did you include intelppm.sys manually? Link to comment Share on other sites More sharing options...
blanalex Posted January 29, 2011 Author Share Posted January 29, 2011 My standard image is made on Intel computers, so it did include intelppm.sys.Also, when I took a basic, made from scratch, image from a X100e and copied it to another computer or a VM emulating an Intel CPU, the PnP detection part of the mini-setup added intelppm.sys. So, when I copied back the basic image to a X100e, intelppm.sys was now present and active.Setting the intelppm service to on-demand start did fix the problem. Link to comment Share on other sites More sharing options...
cdob Posted January 29, 2011 Share Posted January 29, 2011 Thanks for explanation. Yes, this explains it: running at Intel CPU adds intelppm.sys.Sorry to ask again, can you clarify this once more.I haven't run a VMWare machine at AMD CPU so far, hence I'm curious.image from a X100e and copied it to another computer or a VM emulating an Intel CPUDidn't you used a VMWare machine? Does a VMWare machine emulate a CPU?Did you run this VMWare machine at a host AMD CPU machine or a host Intel CPU machine?Back from 2005 http://communities.vmware.com/message/165289 VMware vPlatform do not emulate CPU so you will see the host CPU.Did this changed in the last years?Some more image settings, e.g. agp, PS/2 and USB mouse and keyboardhttp://www.911cd.net/forums//index.php?showtopic=22092 Link to comment Share on other sites More sharing options...
blanalex Posted January 29, 2011 Author Share Posted January 29, 2011 Didn't you used a VMWare machine? Does a VMWare machine emulate a CPU?Did you run this VMWare machine at a host AMD CPU machine or a host Intel CPU machine?Back from 2005 http://communities.vmware.com/message/165289 VMware vPlatform do not emulate CPU so you will see the host CPU.Did this changed in the last years?You're right, VMWare didn't emulate the CPU, it expose the host CPU. In my case the Xeon W3680 of my MacPro.Some more image settings, e.g. agp, PS/2 and USB mouse and keyboardhttp://www.911cd.net/forums//index.php?showtopic=22092My image is running great, but I'll look into this to see what can be tweaked. 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