• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1997
  • Last Modified:

Blue screen after bringing down a syspreped ghost onto a new IBM T60 (Ultra SATA)

Hello,  I am trying to bring down a syspreped Ghost image (that works on all of our other hardware) onto a T60 (PN: 2007-49U).  On the first boot after loading the image, I get a bluescreen during the windows splash screen.  I think the issue is with the Ultra SATA driver not being present in our image.  

This is for an enterprise solution, so I don't want to have to create a new ghost out of the T60 for several reasons I won't go into.   I know I can change the SATA setting in the T60 BIOS to COMPATIBILITY mode, which will allow the machine to build without bluescreening, but I would prefer to use the actual SATA drivers if possible.

I was  able to get the drivers (Intel Matrix Storage Manager v5.5.0.1035) from the web and do the following:
1. Integrate Ultra SATA support into our WinPE boot CD.
2. Integrate Ultra SATA support (slipstream) into an XP SP2 CD.

Using the updated WinPE CD I can access the hard drive with no issues, and using the slipstream CD, I can build XP SP2 from CD with no errors.

I have access via WinPE to edit the syspreped image without actually booting it up.  I am thinking I need to write/edit the new T60 Ultra SATA .sys, .inf etc files to the image, but I don't know where.  I have tried adding the T60 iastor.sys, .inf and other files to just about every place I could logically think of putting them or followed from other site's directions.  It seems like even though the files are present XP doesn't know where they are.

So the main question is:  Is it possible to add Ultra SATA drivers to a syspreped image without actually having to build the image on the T60?  Is there a way to inject/edit the drivers/files into the existing image?

Note:  I know I have the right HAL (ACPI Mulitprocessor PC), so I don't think that's an issue.
0
undsioux7
Asked:
undsioux7
1 Solution
 
cpc2004Commented:
The crash may be caused by faulty ram or device driver error (ie video, sound card, modem and etc). The system event log and the minidump has the most useful diagnostic information. When Windows crashes with blue screen, it writes a system event 1001 or 1003 and a minidump to the folder \windows\minidump. Check system event 1001 and 1003 and it has the detail of the blue screen.

Event ID: 1001
Source: Save Dump
Description:
The computer has rebooted from a bugcheck.The bugcheck was : 0xc000000a (0xe1270188, 0x00000002, 0x00000000, 0x804032100).
Microsoft Windows..... A dump was saved in: .......

Event Source: System Error
Event Category: (102)
Event ID: 1003
Description:
Error code 1000007f, parameter1 0000000d, parameter2 00000000, parameter3 00000000, parameter4 00000000

Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001/1003. Copy the content and paste it back here

Zip 5 to 6 minidumps to a zip file and attach it at any webspace. I will study the dump and find out the culprit. If you can't provide the minidumps, run memtest to stress test the ram. Make sure that your windows is not infected with spyware, adware adn chkdsk /r.
http://www.memtest86.com/.

Get public webspace
Use a free service like rapidshare to attach the minidumps and post the url of the mimidumps at this thread.
http://www.rapidshare.de/
0
 
undsioux7Author Commented:
Thanks for the reply, but I can build the T60 with a windows xp sp2 (slipstreamed w/ the Ultra SATA drivers) CD from scratch and it functions properly. It boots up just fine into windows and runs ok.  The hardware is working properly, not my ghost image (this is a previous ghost from an older piece of hardware that has been syspreped.

The issue is I need an enterprise solution since we use just 1 ghost image for many different pieces of hardware.  My last resort would be to build an image on the T60 as mentioned above, add ALL of the security patches, sysprep and other cleanup of the image before even being able to create a ghost to replace the one we have now.  Plus, I would then need to regression test on 12 different pieces of hardware with this new ghost instead of just the T60 using the current ghost we have now if I were able to get the correct drivers into the current ghost.  

This has never been an issue in the past with the current ghost since if there was new hardware (cd-rw for example) It didn't effect windows from booting, and then our process continued and loaded all of the correct drivers off of our ramdrive that we copy down from a server based on type of hardware and loaded at that point.  The problem here is the new hardware is a new controller (Ultra SATA) that is effecting the Harddrive access and the operating system is blue screening before we can apply the correct drivers.
0
 
gav46Commented:
I just received my first T60 and encounter the same issue when running my standard syspreped ghost (which work on all previous images)..

What needs to be done is before running the ghost, is to go into BIOS -> Config -> Serial ATA (SATA) and change the setting from AHCI to Compatibility. After running the ghost, restore this setting to AHCI
0
 
ViperZ2000Commented:
Any new info? We just received 2 T60P notebooks. Same issue as 1st post. I'm working on integrating the driver into sysprep but will try the suggestion that "gav46" gave above and report back.
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now