I have what would normally be considered a fully functioning copy of UBCD4WIN. I have tested it on:
- Multiple IBM laptops (boots perfectly - wireless works too btw)
- HP DC7100 Workstation (boots perfectly)
- HP D530C Workstation (boots perfectly)
- IBM xSeries 330 8674-41X Server (boots perfectly)
So what's the problem?
Well most of my current servers are IBM xSeries X330 8837-11U & 8837-15U machines and I get a Blue screen when trying to boot to it. The previous UBCD4WIN that I created works fine on that platform. I was using a pre-3.0 version of UBCD4win built in conjunction with pebuilder319. The only difference I can think of is that I used a Windows Server 2003 Std disk as source files for the disk. I had to change from the Windows 2003 Server source disk to the Windows XP Pro disk due to workstation errors I experienced (see previous thread). Here is the information from the Blue Screen:
---
A Problem has been detected and Windows has been shut down to prevent damage to your computer
blah blah blah
Technical information:
*** STOP: 0x0000008E (0xC0000005,0x804031AD,0xF7475600,0x00000000)
---
The built in RAID for this system is NOT recognized during boot-up from the Windows XP Pro disk that I used to build the ubcd4win disk I'm using. I suspect that adding the additional RAID drivers from my Server2003 disk to the Windows XP files on my harddrive will solve this issue. Can someone tell me exactly which files to put where? Can this even be done or are there other issues adding these RAID drivers to the XP Pro files?
Thanks in advance for the assistance.
Snewo
Full Version: Blue Screen @ startup - system dependent
Bzzzzt....guess I was wrong. I pressed F6 during boot-up and used the latest version of the driver for the LSI Logic RAID and it still Blue Screened. There is some other problem with this. I still suspect that this is due to my using the WindowsXP Pro SP2 disk and not the Windows Server 2003 disk. Does anyone know how to get this working with Server 2003? When using Server 2003 I was getting Workstation errors and the networking didn't work.
If anyone has any ideas on merging various components of the disks I'll give it a try. Can I put the workstation service from my XP Pro SP2 disk in the directory with my 2003 files or something? I'll keep messing with it, but I'd appreciate any info or advice you can provide.
Snewo
PS - Not that it matters much, but I have a correction to the post above. My new systems are x336 8837-11U & 8837-15U servers NOT x330's.
If anyone has any ideas on merging various components of the disks I'll give it a try. Can I put the workstation service from my XP Pro SP2 disk in the directory with my 2003 files or something? I'll keep messing with it, but I'd appreciate any info or advice you can provide.
Snewo
PS - Not that it matters much, but I have a correction to the post above. My new systems are x336 8837-11U & 8837-15U servers NOT x330's.
there is a posable bug in the preshell program that is being worked on. It seems to be a timing issue during the boot process that is causing the bsod & it only seems to happen on fast systems. None of us working on this project have access to hardware that is causing the issue, so it is taking longer to get the problem isolated. There is a post here somewhere that had a script using sleep.exe that was a work around. Joshua is almost done with the fix & it will be posted as soon as it is viable.
If you need imediat acces to the systems that you are having trouble with, search for sleep.exe & you should find the answer on how to do it yourself. Otherwise a fix will be provided soon.
You still need to address the driver issue. If the driver is not included in the download, please add it to your build. Post another question if you need help adding a driver & the part of our team that does the driverpacks will respond when they check the forum.
Thanx
Sorry, it was not a public post.....
If you need imediat acces to the systems that you are having trouble with, search for sleep.exe & you should find the answer on how to do it yourself. Otherwise a fix will be provided soon.
You still need to address the driver issue. If the driver is not included in the download, please add it to your build. Post another question if you need help adding a driver & the part of our team that does the driverpacks will respond when they check the forum.
Thanx
Sorry, it was not a public post.....
QUOTE
It exhibits it self as a STOP 0x71 message just before the PreShell would launch.
Actually message:
SESSION5_INITIALIZATION_FAILED
STOP 0x71
I was running under VMWare with the ISO connected to a virtual machine. If the ISO file was stored on a very fast disk subsystem then the stop message would happen. Copying the ISO to a slower disk subsystem resulted in the VM booting correctly.
I also duplicated the fault with a real CD-ROM image of the ISO on a HP DL580 series computer.
The issue seems to be one of timing. The PreLogon.exe launches and tries to do something before all the necessary (supporting) services have started (at a guess), this results in the stop message.
To fix the problem I created a simple batch file which relies on the Windows Resource Kits sleep.exe file.
The batch file simply sleeps for 10 seconds and then launches the PreLogon.exe program.
Result -> Perfect boot every time, no more stop 0x71 in virtual or real machines.
Alterations:
edit file oem1\Joshuas-PreShell\PreLogon.inf
under [SourceDisksFiles] add
PreDelay.cmd=2,,1
Sleep.exe=2,,1
under [SetupReg.AddReg] change to
0x2, "Setup", "CmdLine", "PreDelay.cmd"
Create a file called PreDelay.cmd in oem1\Joshuas-PreShell directory with the contents:
@echo off
Title Waiting for services to start...
echo:
echo Delaying to ensure all services have started before launching the shell
echo:
sleep 10
PreLogon
Also copy the sleep.exe program from the Windows Resource Kit into the oem1\Joshuas-PreShell directory.
Obviously this is a workaround, and should be fixed by a programming change to the PreLogon code.
This problem also showed up when connecting the ISO to a virtual machine running on one of my ESX v3 servers (Quad Opteron, 32GB RAM == Fast).
On slower disk subsystem servers the same ISO allows the identical VM to boot correctly. (ISO images compared used MD5SUM to ensure they were identical). Issue observed over multiple systems.
Actually message:
SESSION5_INITIALIZATION_FAILED
STOP 0x71
I was running under VMWare with the ISO connected to a virtual machine. If the ISO file was stored on a very fast disk subsystem then the stop message would happen. Copying the ISO to a slower disk subsystem resulted in the VM booting correctly.
I also duplicated the fault with a real CD-ROM image of the ISO on a HP DL580 series computer.
The issue seems to be one of timing. The PreLogon.exe launches and tries to do something before all the necessary (supporting) services have started (at a guess), this results in the stop message.
To fix the problem I created a simple batch file which relies on the Windows Resource Kits sleep.exe file.
The batch file simply sleeps for 10 seconds and then launches the PreLogon.exe program.
Result -> Perfect boot every time, no more stop 0x71 in virtual or real machines.
Alterations:
edit file oem1\Joshuas-PreShell\PreLogon.inf
under [SourceDisksFiles] add
PreDelay.cmd=2,,1
Sleep.exe=2,,1
under [SetupReg.AddReg] change to
0x2, "Setup", "CmdLine", "PreDelay.cmd"
Create a file called PreDelay.cmd in oem1\Joshuas-PreShell directory with the contents:
@echo off
Title Waiting for services to start...
echo:
echo Delaying to ensure all services have started before launching the shell
echo:
sleep 10
PreLogon
Also copy the sleep.exe program from the Windows Resource Kit into the oem1\Joshuas-PreShell directory.
Obviously this is a workaround, and should be fixed by a programming change to the PreLogon code.
This problem also showed up when connecting the ISO to a virtual machine running on one of my ESX v3 servers (Quad Opteron, 32GB RAM == Fast).
On slower disk subsystem servers the same ISO allows the identical VM to boot correctly. (ISO images compared used MD5SUM to ensure they were identical). Issue observed over multiple systems.
FWIW that didn't seem to fix my issue. Since it sounds as if a possible fix is coming out soon, I'll give that one a shot. I'm not in a pinch since the older UBCD4WIN still works on this platform. I just need to keep 2 disks around instead of one. Thanks for the help.
BTW, if you need me to test anything out let me know.
Snewo
BTW, if you need me to test anything out let me know.
Snewo
QUOTE(Snewo @ Oct 6 2006, 03:45 PM) 
FWIW that didn't seem to fix my issue. Since it sounds as if a possible fix is coming out soon, I'll give that one a shot. I'm not in a pinch since the older UBCD4WIN still works on this platform. I just need to keep 2 disks around instead of one. Thanks for the help.
BTW, if you need me to test anything out let me know.
Snewo
I will keep you in mind if we need outside testing.BTW, if you need me to test anything out let me know.
Snewo
I think your problem may be driver related. It could be a duplicate file name in an existing driver causing the bsod. If you can isolate the driver you need and remove all others, we could narrow the issue down to an exact cause.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.