BSOD on boot

I have a p15 s420 that BSODs on boot. I can't boot to a CD to run memtest as it seems to ignore boot order. I have disabled booting to the HDD as well as network boot to force it to see the optical drive. It still however attepts a network boot. The optical drive doesn't seem to be working.
My concern is at the BIOS page it reports: System Memory 640KB Extended Memory 510 MB.
Is 640K the correct amount of system memory? Doesn't seem right.

Where did you get it? Did you try restoring from recovery? Did it include any form of recovery?
And I h8te hard disk backups and paid for OEM Disks they take away what little flexibility you get with installing stuff to different boxes when upgrading! And HDD can fail screwing yourself and OEM isint true install if OEM manufactuer does a crappy job.
laptops- ex satillite l755-s5353 inspiron e1505 desktop dimension 400/300

Similar Messages

Windows 2008 R2 DC Recovery Test BSOD on boot

Hello everyone.
first off i have a perfectly healthy production domain with 2 domain controllers and replication occurring between them, the only issue is there on the same site.
i am in a test environment testing a scenario where both DC's are broken and i need to build a new one on new hardware, and all i have is a system state backup.
following the instructions,
Build a new machine closely matching the original machine hardware, (RAM and HDD size)
install 2008r2. allocate static IP address and reboot in DRM
add windows feature, windows server backup
select restore in WSB and select the system state.
DC then restores the data and askes to be rebooted.
after the reboot i get a BSOD on boot and its seems to occur when to loading CLASSPNP.SYS file any suggestions on how to resolve this?
also is there a way of building a DC, using DCPRMO then restoring the data to another location and then importing it into active directory.
basically i need a plan that can be used in a total disaster scenario with a off site backup of the system state / backup as my only options.
cheers
Gordon

Have you seen? Also make sure to install the exactly same operating system and service pack level
http://support.microsoft.com/kb/249694/
Enfo Zipper
Christoffer Andersson – Principal Advisor
http://blogs.chrisse.se - Directory Services Blog

Sat Pro 4300: BSOD on boot, avoided if delay

Hi
I have a Sat Pro 4300, running W2K SP4. Had it since 2001 with no problems.
Recently I've been getting "unexpected kernel mode trap" and sometimes "ACPI BIOS not fully ACPI compliant" BSODs during boot (before it gets to any kind of graphics). Happens in safe and normal mode.
By experimentation I've found that I get no BSOD and boot normally if I F2 during bootup and just hang arond for a while (five minutes or so), then boot.
If I run a memory test after booting into the Ultimate Boot CD, sometimes I see a lot of bad memory, sometimes not. I think it depends how long I've waited before booting into the CD.
Anyone like to hazard a guess whether this is hardware or software? I rather assume the former. I suppose it could be memory gone bad, or worse power regulation on the mainboard has begun to go.
In either case probably not worth repairing, but I'd appreciate anyone's opinions.

Hello
I do not know for sure what the problem can be but replacement part for this oldie are not so expensive and you can try to make some experiments. Check eBay. There you can find everything possible. I can imagine the whole mainboard for this oldie should not be expensive.
Check the prices and make decision.

Bios Update = BSOD on Boot

Had a new one and I'm in the middle of repairing my windows install right now so I can at least backup.
Updated to the new Bios due to a few minor issues I was experiencing and suddenly I load windows to a BSOD (before boot even completes) to a reboot (before I can even see the BSOD error) and loop.
Tried dropping back to 1.1, no success. Did everything I can think of, but I can't drop to one drive as I'm running RAID 0 and have stuff to back up...
Just one big headache at the moment. I've done thousands of bios updates and never had a situation like this.......
EDIT: Adding System Config since my sig is dead temporarily....
MSI K9A Platinum
AMD X2 4600+ AM2
2 x 1GB Crucial PC-4300 DDR2
2 x 160GB Samsung SATA II in Raid 0 Configuration
PowerColor ATI Radeon X1900XTX 512MB
HP DVD-RW Drive
Dual Samsung 940B LCD Monitors
Logitech DiNovo Media Desktop Laser - Bluetooth

Life is fun. I dumped the system today and went to do a reinstall and believe I now know where the problem started.
During the reinstall I attempted to use my original ATI Raid disk I made when I first recieved the board (based on catalyst 6.8 I believe). BSOD during install with a driver error....
So I tried the ones currently on MSI's site (6.9) and BSOD again during install.
All driver related....
So, I downloaded 6.10 cats from ATI and extracted them to pull the drivers......
Installing fine now.

MB Pro 13 (2010) BSOD in Boot Camp followed by question mark folder

Hello, good folks of the Apple support communities. Let me describe my problem to you guys and maybe you'll help me figure out what's wrong because I'm at my wit's end.
A couple of months ago, my MBP13 randomly gave me a BSOD after which it refused to load - just gave me a blinking cursor. I was able to narrow that down to a somehow-messed up boot sequence. I was able to fix it from the Windows 7 repair console. I thought that this time around my situation would be similar, but I haven't been that lucky. So, let me paint the picture of what happened this time.
Sitting in my kitchen, laptop on the counter, plugged in, having a conversation on Trillian and Skype. I pick it up and move to another room, sit down and try to continue and for a couple of minutes everything is fine, but then the cursor freezes and I get a BSOD, followed by an illuminated dark screen. All my attempts to resuscitate prove futile - any time I press the power button, all I get is that gray screen. I reset the PRAM and then got the white screen that usually appears when I just power on. Unfortunately, no choices of boot (Mac of Windows 7 Ultimate 64-bit which I'm running in Boot Camp) - and then the flashing folder with question mark followed. I was 15 minutes away from driving off to the airport, needing to get on a plane, so I grabbed the MBP, the OSX DVD and the Windows DVD and an external hard drive (2.5 inch SATA) and went to the airport. Started reading support forums and narrowed the issue down to potential HD issues. So I tried first to re-seat the drive - no dice. Then I tried booting from the OSX DVD and going to disk utility - the HD was not being recognized. Same story with the Windows 7 DVD. Mid-flight I disassembled the external drive and swapped the two - the external was being picked up, no problem, so I figured it was a hard drive issue, not a motherboard one, say.
So, I'm thinking, great, my HD is fried. I've got a whole bunch of data on it that I wanted to salvage (primarily on the Boot Camp partition), so I swapped the MBP drive into the enclosure and hooked it up to a buddy's laptop. To my surprise, Windows 7 on his Dell picked it up without a problem (only Boot Camp, not the Mac part, but since Mac isn't formatted for Windows that probably shouldn't have been surprising) and after futzing with the permissions, I was able to start backing stuff up - never finished, though, figuring that if it's being picked up, I'd just do it later. But I needed a functioning laptop, so I went to Best Buy and picked up a Momentus XT 500GB, installed it and thought I'd be able to install an OS on it. Nope. Windows never even saw the drive and OSX tried to format it but couldn't allocate memory, according to the report. So back to BB the Seagate went. I am coming back to school tomorrow and should be able to have our IT people look at it, but what do you guys think are my best and worst case scenarios and options here? If the Mac HD is completely toast, why would it get picked up just like that via USB? And if it's not toast, can I somehow still boot it? Or should I just salvage what files I have and bite the bullet with a new HD? And which one, if that's the case, since the Momentus crapped out on me big time (in fairness, I later read about all its problems and realized I was better off without it). Or should I just cut my losses, sell the MBP and find myself another computer, perhaps an ultrabook?
Any thoughts greatly appreciated! Ideally I would like to spend as little as possible while restoring my pre-BSOD situation as much as possible, as you might surmise, so I really don't want to buy a new laptop quite yet...

Thanks for the detailed explanation! If MacBook supports AHCI/SATA only in native “UEFI mode”, while reverting back to PATA/IDE in legacy “BIOS mode”, then it could make perfect sense to use UEFI to make sure that technology like Native Command Queuing (NCQ) is employed, as it may give noticeable performance improvements for certain operations: www.happysysadm.com/2012/12/intel-g530-nas-performance-part-3.html. I wonder how do you get Windows 8 x64 with EFI bootloader installed on MacBook?
Simply choosing EFI Boot (“Some EFI platforms support both UEFI and BIOS firmware. On some of those systems, it is not always clear if the default DVD boot option is an EFI or BIOS boot option. On these systems, using the EFI shell command may be required. If you do not specifically start Windows Setup by using the EFI boot entry, the default firmware boot entry for BIOS may be used. If Windows Setup starts in BIOS mode on a combined EFI/BIOS system, the ESP and MSR partitions are not created.”) from Win8 x64 DVD when installing on blank HDD would yield “The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed" message. Also, if the hard drive was not in SATA mode during Windows installation, registry tweaking may be required before switching from PATA to SATA. Do you do registry tweaking and EFI bootloader configuration manually after a copy of Windows was installed in its dedicated partition in a regular way?

MSI MPOWER z87 BSOD on boot in RAID mode

Hello, I've just recently added a harddrive and was attempting to set up a raid and encountered this issue. I have 2 ssds - one is the boot drive, second for games, and I have 3 1tb hdd drives which I was attempting to put in a raid5. I installed the third drive today, went in to the BIOS, switched SATA mode to RAID and got an immediate BSOD before even booting to Windows. Previously, I've had the two ssd in a RAID-0 and never had this issue. The ssd are no longer in a RAID, I was hoping to only have the 3 hdd in the raid5. I'm now having to reinstall windows because the error corrupted a system file somewhere and I'm unable to repair it. Any help would be greatly appreciated.
My system is:
Windows 7-64bit
MSI MPOWER z87
Intel i7-4770k
8gb corsair vengeance RAM
2 120gb OCZ Vertex 3 SSD
3 1tb WD10ezex HDD
MSI GTX760 GPU
Rosewill Capstone 750W PSU

You cannot just change SATA modes.
http://www.overclock.net/t/1227636/how-to-change-sata-modes-after-windows-installation
Note: one mistake or missing step and you won't be able to boot again.

G560 PXE error; OneKey Recovery seems to work, but then I get BSOD upon boot

I've got a 3-year old G560 and a few days ago, I ran into a PXE error out of the blue. I didn't really change anything about the computer's setup, and it may have been caused by commuting the laptop.
I already went through the whole F2 setup regimen of disabling network boot, changing over to compatible mode, trying every combination of boot order, etc.
When I was in compatibility mode, I was able to get the OneKey Recovery to work. There's no DVD involved, seems like it's stuck in that partition. I never set a restore point, but I didn't mind a factory reset. So I did the OneKey factory reset and it took about 15 minutes and it seemed to be okay, but then when I try to start the laptop, it will show the Windows logo, freeze there for a few seconds and then it flashes the blue screen of death for a split second (impossible to capture the error codes).
If I try it in safe mode, it shows the files that are being loaded, and it BSODs right after classpnp.sys
Now, I guess my main question is if OneKey will appear to work and yet maybe the HDD (hard drive) does not work. Could it be a matter of just replacing the hard drive? I did pull out the hard drive and re-mount it. Also the motherboard and re-mounted it. Is the OneKey function separate from the hard drive?
The laptop is so old that I wouldn't want to invest much money in its repair (warranty is past expiration date), but it's also been my daily computer, so I wouldn't mind if it was just a case of replacing a hard drive. With these problems, would it just be possible to make Ubuntu into my primary operating system by using an install disc?

hi stophammertime,
Welcome to the Forums.
It looks like you have some bad sectors on the HDD that's why the OKR didn't work or for some reason, OKR worked but the bad sectors corrupted the OS installation files. To verify this, you will need to run diagnostics on the HDD (try ultimatebootcd as it has diagnostic tools for ever brand of HDD's)
Also, the OneKey Recovery runs on a hidden partition on the HDD (usually the last few sectors of the drive). It's possible to trigger the OneKey Recovery if the partition structure isn't damage but if the target drive has bad sectors (i.e. Drive C:\), it may fail to image the drive or corrupt the installation files.
If verified that you have bad sectors on the HDD, you will need to replace the HDD and from here, you can:
1. Use a recovery disc to restore the default OS (this is only psosible if you have created one using this method)
2. If you can still read the COA product key at the bottom, you can burn an ISO copy on this website and use it to clean install Windows into your PC (if you get issues activating Windows, try to activate by phone).
3. Scratch Windows and use Ubuntu as you're primary OS.
Hope thish elps
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

BSoD during boot up

I recently updated my nvidia video drivers and when I restarted my computer I now get the BSoD right before I see my login screen. So, the first thing I thought to do was to rollback the driver. However, I can't boot up on Safe Mode.
This is what my computer is doing:
1. Computer on, initial boot screen comes up
2. Options for Safe Mode or Start Windows normally
a. I am unable to choose Safe Mode because my computer is not responding. This can't be normal.
3. It starts up normally, because I can't choose otherwise.
4. I see the Windows XP logo
5. BSoD
6. Computer reboots.
For whatever reason, my keyboard shuts off for the options to change to safe mode. It shuts off if I want to change my boot sequence. It even shuts off if I want to boot from the CD so I can use my recover disk.
Any help anyone can offer will be greatly appreciated.

On some computers with integrated video chips, its been my experience that updating the chipset drivers might not be a good idea since those drivers are custom for the OEM.
There is a way around this using the repair console found from booting from the Windows XP installation disc, but it requires a little bit of high user level expertise to work with that.
You might have to take it in for data backup and a reinstall of the OS if you cant get it running
*******DISCLAIMER********
I am not an employee of BBY in any shape or form. All information presented in my replies or postings is my own opinion. It is up to you , the end user to determine the ultimate validity of any information presented on these forums.

Tecra M3 PTM30A: BSOD while booting - How to reinstall the Win XP?

Hey
Ive got a Toshiba Tecra M3 model number PTM30A-029002 and iv recently experienced a problem which I think a virus did.
When I start computer normally it goes to XP loading screen then goes to a blue screen saying stop: c000021a (Fatal System Error)' and just stay on the screen till i turn off. This happens every time
When I tried to start in safe mode it bring up all these letter and numbers then it just restarts.
I was told to use recovery from my windows XP CD but I do not know how to reboot from the cd. I press F2 at beginning and red Toshiba logo comes up with these different pictures at the bottom to select and Ive tried all but none work
plz help as I need this fixed as soon as possible as this is not actually my own laptop thanks

As far as I know its not possible to boot from a common external USB CD/DVD drive!!!
You will need an external CD/DVD drive with PCMCIA card which could be more expensive as an internal CD/DVD drive.
Therefore I would recommend choosing the internal, supported CD/DVD drive.
However, I dont know if you have tried to boot from the CD correctly.
The point is that you dont have to press the F2 button but you have to press F12 button to get the boot menu on the screen.
Then choose the ODD (CD/DVD) as a boot source and try to boot from the Toshiba recovery CD.
Check this!!!

Slow restart - blue screen BSOD and Boot Camp restart issue

After Snow Leopard install on Macbook Pro I have experienced a very slow startup and restart. The grey apple screen appears for about 25 secs and then the blue screen hangs for 2mins and 2 secs. Also when restarting from Boot Camp blue screen just stays and restart fails. I waited approx 25 mins and blue screen was still there. I have searched Console system log for clues but am not technically adept. hopefully someone can help. I have copied log below form recent restart (in OSX mode, not boot camp). My Windows Boot camp volume is called ERICGLPC and I can see some issue on the log but unsure what it means.
Aug 29 23:56:02 eric-lawrences-MBP-2 loginwindow[55]: DEAD_PROCESS: 55 console
Aug 29 23:56:03 eric-lawrences-MBP-2 com.apple.kextd[10]: Error reconsidering volume /Volumes/ERICGLPC.
Aug 29 23:56:03 eric-lawrences-MBP-2 shutdown[265]: reboot by ericgl:
Aug 29 23:56:03 eric-lawrences-MBP-2 shutdown[265]: SHUTDOWN_TIME: 1251554163 308941
Aug 29 23:56:03 eric-lawrences-MBP-2 mDNSResponder[19]: mDNSResponder mDNSResponder-212.1 (Jul 24 2009 22:34:12) stopping
Aug 29 23:56:03 eric-lawrences-MBP-2 mDNSResponder[19]: mDNSRegisterinternal: Shutting down, can't register 20 Eric\032Lawrence’s\032MBP.device-info.tcp.local. TXT model=MacBookPro2,2
Aug 29 23:56:03 eric-lawrences-MBP-2 WindowServer[75]: hidd died. Reestablishing connection.
Aug 29 23:56:03 eric-lawrences-MBP-2 DirectoryService[11]: dnssd_clientstub read_all(20) failed 0/28 0
Aug 29 23:56:03 eric-lawrences-MBP-2 DirectoryService[11]: dnssd_clientstub DNSServiceRefDeallocate called with invalid DNSServiceRef 0x10061cc00 FFFFFFFF DDDDDDDD
Aug 29 23:56:03 eric-lawrences-MBP-2 WindowServer[75]: bootstraplookip failed: Unknown service name
Aug 29 23:56:03 eric-lawrences-MBP-2 DirectoryService[11]: dnssd_clientstub read_all(19) failed 0/4 0
Aug 29 23:56:03 eric-lawrences-MBP-2 sudo[269]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/Library/StartupItems/HWNetMgr/HWNetCfg
Aug 29 23:56:19 localhost com.apple.launchd[1]: * launchd[1] has started up. *
Aug 29 23:56:26 localhost mDNSResponder[18]: mDNSResponder mDNSResponder-212.1 (Jul 24 2009 22:34:12) starting
Aug 29 23:56:27 localhost pcscd[27]: Non-smartcard device launched pcscd [Vendor: 0X3F0, Product: 0X5711]
Aug 29 23:56:28: --- last message repeated 1 time ---
Aug 29 23:56:28 localhost configd[15]: network configuration changed.
Aug 29 23:56:28 eric-lawrences-MBP-2 configd[15]: setting hostname to "eric-lawrences-MBP-2.local"
Aug 29 23:56:30 eric-lawrences-MBP-2 configd[15]: network configuration changed.
Aug 29 23:56:43: --- last message repeated 1 time ---
Aug 29 23:56:43 eric-lawrences-MBP-2 /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[55]: Login Window Application Started
Aug 29 23:56:44 eric-lawrences-MBP-2 bootlog[65]: BOOT_TIME: 1251554179 0
Aug 29 23:56:44 eric-lawrences-MBP-2 blued[66]: Apple Bluetooth daemon started
Aug 29 23:56:44 eric-lawrences-MBP-2 fseventsd[59]: checkvol_last_modtime:XXX failed to get mount time (25; &mount_time == 0x1000b5358)
Aug 29 23:56:44 eric-lawrences-MBP-2 fseventsd[59]: log dir: /Volumes/ERICGLPC/.fseventsd getting new uuid: 640F51B0-A701-4DF7-84CD-9DE7DA23AD26
Aug 29 23:56:44 eric-lawrences-MBP-2 sudo[84]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/Library/StartupItems/HWNetMgr/HWNetCfg
Aug 29 23:56:45 eric-lawrences-MBP-2 com.apple.usbmuxd[49]: usbmuxd-167.1 built for iTunesEightTwo on Jul 9 2009 at 14:02:00, running 32 bit
Aug 29 23:56:48 eric-lawrences-MBP-2 mDNSResponder[18]: SIGHUP: Purge cache
Aug 29 23:56:51 eric-lawrences-MBP-2 loginwindow[55]: Login Window Started Security Agent
Aug 29 23:56:52 eric-lawrences-MBP-2 configd[15]: network configuration changed.
Aug 29 23:57:07 eric-lawrences-MBP-2 ntpd[43]: time reset +0.640880 s
Aug 29 23:58:46 eric-lawrences-MBP-2 loginwindow[55]: Login Window - Returned from Security Agent
Aug 29 23:58:46 eric-lawrences-MBP-2 loginwindow[55]: USER_PROCESS: 55 console
Aug 29 23:58:46 eric-lawrences-MBP-2 com.apple.launchd.peruser.501[120] (com.apple.ReportCrash): Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
Aug 29 23:58:57 eric-lawrences-MBP-2 com.apple.launchd.peruser.501[120] (com.apple.Kerberos.renew.plist[138]): Exited with exit code: 1
Aug 29 23:59:00 eric-lawrences-MBP-2 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/fontd[131]: ATSFindFolder timeout. (domain:-32764, dirType:'font', createFolder:false, ATSServer pid:131)
Aug 29 23:59:01 eric-lawrences-MBP-2 ServerScanner[135]: Not scanning because node /Active Directory/All Domains is in searchPath
Look forward to hearing from anyone.
Many thanks
Eric

JoePrairies wrote:
if anyone could perhaps shed some light on why this might have occurred?
Your Mac may have if you didn't erase the log files
Without that, it could have been anything.
-mj

BSOD on boot due to Lenovo Power Manager

I was uninstalling this Power Manager last time on computer. I do not remember what version it was. It was stuck at 94% for long time (half hour), so I shutdown my computer instead of waiting for it.
Now my windows 7 cannot boot at all. Not even safe mode. All I can boot in is the repair tools, but the repair tools did not help at all. I cannot afford to reinstall a system as there r many important files inside C drive and user directory.
Blue screen says: Stop 0x000007B
I cannot believe this application is even more painful than removing a virus on the computer.
Waiting online for solutions as I really need my computer.
Solved!
Go to Solution.

First of all, thank you for replying such old and helpless topic. unfortunately I did not find a way to solve this issue. I highly suspect that is caused by one of sys file that power manger was using. I do not know which one. As a result I have to insert my disk to another computer retrieve all important files then do a reinstall. After reinstall everything works fine.
I am not gonna reinstall power manager again. It was a big disappointment from Lenovo.

X120e - Aftermarket memory causing BSOD, unstable boot

Purchased a 4gb stick of GSkill memory (F3-10600CL9S-4GBSQ, CL9-9-9-24) hoping to get a little extra memory in my system. However, it seems to make my computer extremely unstable - restarting several times before getting to the login screen, flashing BSODS about sytem hangs and a memory error - both with and without the 2gb stick, and in both slots, often after waking from hibernation. I ran Memtest86+ and the windows memory test, and both seemed to pass alright. Since the 2gb stick by itself seems to work, I was planning on returning the new stick, but was wondering if you all knew of a more likely-to-work thing of memory for the computer.
Thanks for your help!

Buy the memory that has a Lenovo FRU number on it. You can buy direct from Lenovo or search for the memory FRU numbers and buy them from online retailers.
An additional advantage to buying a Lenovo FRU is that it's covered under the notebook's warranty, so if the memory goes bad during the warranty period, you can get a replacement from Lenovo without having to ship the bad part back first.

X61 - Can't get sysprep'ed image to boot on it.

Scenario
I am the senior desktop analyst in the offices of an international business travel company.
We recently won the Lenovo account and the employee of our company that manages the account needs to use a Lenovo laptop exclusively so I was sent a brand new X61 to configure for the rep.
X61 originally came with Vista preloaded but I slapped XP SP2 on it using the enclosed bootable Rescue CD and six XP recovery CDs.
Since we already use a single working corporate image for the 6 different non-Lenovo hardware platforms we currently use, I want to deploy the same image to this user.
I was the person that created the image from scratch and I see no problem with it actually working on the X61.
To create an image for the laptop, one of our fastest desktops was imaged with our corporate master image and brought up normally as if the PC was being readied for deployment.
Once everything had completed, the HD in the desktop had the proper Lenovo x61 drivers added to it and the SATA drivers added to the sysprep.inf file as well.
After that it was sysprepped, shutdown and left lying in its original desktop ready to be cloned over to the drive in the X61 where it would be booted up for the first time after sysprep, in the X61.
So I would still be able to keep the preload on the x61's original hard drive, I used a SATA laptop hard drive from one of our current non-Lenovo systems for the image transfer to the x61.
Problem
When I clone the sysprepped image from the desktop hard drive over to the laptop hard drive, it refuses to boot in the IBM.
It just sits at the screen with a blinking cursor doing nothing.
Troubleshooting so far
I have put the corporate image on the x61's original hard drive [with the XP preload] by just replacing the original data partition and leaving the recovery partition alone = blinking cursor.
I have cloned the whole source drive over to the Lenovo preload HD, removing the recovery partition completely = blinking cursor.
I have installed XP from the original CD using a USB-floppy drive and the F6 key to add the SATA driver during startup.
Once completely installed, I figured that it had a valid boot sector and I Ghosted over the sysprepped image without the IB switch and I still get the blinking cursor.
I have researched on the Internet using Google and have found a couple of links that seem to indicate what the problem might be and have listed them below
Predesktop Authentication
This has nothing to do with the issue at hand as this option lies in the BIOS under Security,FingerPrint.
Its BIOS description also states that this option decides whether fingerprint access is required to boot the laptop and this option has been in the disabled state even while the laptop was booting the Factory Preload.
SATA set to Compatibility instead of AHCI
This setting only affects how the OS sees the HD, not how the laptop sees it and I tried it anyway and it has no effect.
If your XP image isnt properly sysprepped to handle the SATA drive using the proper driver, you will need to set it to Compatibility mode to get into Windows.
As it stands, this is not an issue as I have edited the sysprep.inf to add the SATA driver reference for this laptop and if it ever boots the image, I expect it to never BSOD but thats if it ever boots which it hasnt so far.
Ghosting using the IB switch
I was SO sure that this would fix the issue but I get the same blinking cursor.
Booting into DOS and using Ghost 8.3, I ran "ghost -ib" and selected the sysprepped desktop drive as the source and the laptop drive as the destination and it still leaves me at the blinking cursor when I try it in the laptop.
Re-creating the MBR
I have done this two different ways, one using Norton GDISK and one using a regular Windows 98 bootdisk.
The Windows 98 bootdisk kept saying "No fixed disks present" so it never worked.
Nortons GDISK didnt have any issues re-creating the MBR on the laptop or on the laptop HD plugged in the desktop but the drive still doesnt boot.
Signature failure error
I have heard about people having the same issue as me and getting this error but so far I have not received this error.
As of now, I have restored the XP SP2 preload back on to the laptop to get the original boot sector back as I believe that is the key to solving this whole nightmare.
There are other things I have tried as well and since I have been at it exclusively for almost two full business days now, everything is much upstairs right now but I will remember what I have tried if anyone wants to e-mail me any suggestions.
I await and welcome anyones advice.
Solved!
Go to Solution.

Hi all,
Sorry about not updating this thread but here is the solution and the explanation, hopefully, I dont miss anything because I would like this all in one place so it can be referenced in the future.
The Lenovo's and the Dell's and maybe other OEM's [not Fujitsu-Siemens] use a recovery partition and the boot table that references it is based on some form of Linux as also is the recovery partition itself.
As far as I know, all flavors of Linux use 8,192 bytes for a boot table [4 sectors of 2048 bytes each] whereas a standard boot table is only 1 sector and 2048 bytes long.
This is the reason for the problem that happens with OEM laptops like this one.
What you need to do to get the image to boot is the following [BSODs after booting is another issue]
Create the image to a ghost file on whatever platform you want but use the IB switch in Ghost to create the image with the boot table intact.
Deploy the image to the IBM laptop hard drive ALSO using the IB switch
When doing ANY image deployment to the laptop, the hard drive MUST be IN the laptop itself. The laptop writes its boot sector differently so the hard drive must be in it for the image to work. I was doing everything right but this step and I was still having the issue so this is crucial.
If you are testing the image by deploying straight from the test PC to the laptop by using the Ghost Peer-2-Peer TCP/IP option, start Ghost on both ends with the IB switch but remember the destination SATA drive MUST be in the laptop itself.
Thats it.
Hope this helps everyone out.

Repair install... wait... what if I can't boot?

Ok, so here's a two part question:
1. Just say something has gone terribly wrong and I cannot boot into Windows.
Some corrupt Windows file - I’m thinking important things like winload.exe and some vital dll's - or maybe something has gone wrong in the registry.
How do I do a repair install to fix the problem without deleting all of my programs, current registry etc?
I know in XP you could just boot off the disk and do a repair install, but I can't seem to find a similar function with 7.
2. Here is a situation that has led me to be in the above situation many times. You have a perfectly operating Windows 7 installation (and assume this would apply to Vista too) and you go and do something like: change a motherboard, move the HDD from one computer to another... or in some way or another CHANGE THE STORAGE CONTROLLER that the HDD has to boot from.
This results in a BSOD on boot. I would assume this is because the installation doesn’t have the driver for the controller, and if it does - it isn’t installed, and set to boot from that controller (bad wording there, but I am guessing that there is some way that the windows install is set to boot from only the specified storage controller/driver)
Again, in XP, I would just do a repair install booting to CD with the correct storage controller driver. This was tedious, but the only way I knew of to get the HDD booting again.
So, as I cannot seem to find a way of repair installing with 7/Vista (and even if I did find a way, I hope there is some easier thing I can do), what can I do to stop this problem from occurring when the storage controller is changed? Can I pre-install the driver? How do I set it to use that driver to boot? (again, assuming something like this happens)
Sorry for the long winded question(s), I hope you guys can help me out! :)
jt

"2. Here is a situation that has led me to be in the above situation many times. You have a perfectly operating Windows 7 installation (and assume this would apply to Vista too) and you go and do something like: change a motherboard, move the HDD from one computer to another... or in some way or another CHANGE THE STORAGE CONTROLLER that the HDD has to boot from."
That, my friend, is your problem. Unlike older Win9x and some current Linux operating systems, you just can’t arbitrarily change key hardware components. Yes, there are situations in which you can do that; replace a bad motherboard with a replacement that is an exact match—at least has the same chipset and controllers; However, you can’t remove an Abit motherboard, install a Gigabyte replacement and expect everything to be okay. Moving one boot/system hard drive from one system to another with differing hardware is just the same as the replacement motherboard example.
There are a couple of reasons for this. One is to help reduce the instances of piracy. The other, more important reason is for system stability. Bad hardware, computer configurations, and device drivers are responsible for a good majority of blue screen errors. Replacing key hardware components only undermines Windows stability.
What can you do to prevent this problem from occurring when the storage controller is changed? Nothing. If you need to change a storage controller that will be connected to the boot/system drive, then you will need to make preparations and such accordantly.
Outside of the rant . . .
Like Wolfie said, you should be able to boot with the Windows 7 DVD, do an in-place-reinstall. That should fix your boot problem and provide you with a somewhat stable system.
In my opinion, a better option is to do a clean reload so you have no remaining migration artifacts looming in the background.

Windows 7 64 Bit BSOD regarding winsrv.dll

Hi there,
We have got a high number of Windows 7 Enterprise 64 bit machines randomly goingot into BSOD at boot up. The message at the Blue Screen is:
Stop:c0000142 {DLL INITIALIZATION FAILED}
Initialization of the Dynamic Link Library winsrv.dll failed. The process is terminating abnormally
In most cases we can recover the machine by going through Last Known Good Profile. Some machines were not so lucky and a re-image is required.
On the machines that I was able to recovered. I looked at the Windows System Log and I could see these errors:
Event ID:10010
DCOM got error "206" attempting to start the service TrustedInstaller with arguments "" in order to run the server:
{752073A1-23F2-4396-85F0-8FDB879ED0ED}
Event ID: 7000
The Windows Modules Installer service failed to start due to the following error:
The filename or extension is too long.
Also I can't see anything installed from the system log.
Like I said Last Known Good Profile would let me recover the machine but some time after a couple of days the machine will blue screen again and again I had to use Last Known Good Profile.
Anyone would have any idea what has caused that please?
I had tried the followings with no avail:
1. Scandisk did not find anything
2. Windows Startup Repair failed to find any problem
3. Virus scanned with NOD32 and Malwarebyte (with the hard drive out hooked up to other machine) and again nothing was found.
Thanks,
Edmond.

Hello,
please use Microsoft Skydrive to upload dump files (%systemroot%\minidumps like c:\windows\minidumps) and post a link here.
If you want to read dump files without my help, use Windbg and refer to this Microsoft article:
http://support.microsoft.com/kb/315263
You can also contact Microsoft CSS.
You can start by running sfc /scannow
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

BSOD on boot

Similar Messages

Maybe you are looking for