W540: BSOD during CD boot

I just received a new W540 and I am unable to boot from CD/DVD. Any attempts result in a BSOD indicating the BIOS is not APCI compatible
Link to picture
There is no UEFI/BIOS options to set the 'SATA Controller Mode' accordingly, nor does the [F7] text mode option work.
I am hoping someone in the community can shed some light onto this issue.
Moderator note; picture(s) converted to link(s) About Posting Pictures In The Forums
Solved!
Go to Solution.

Hello,
For clarification, which version of Windows are you trying to boot from CD? Can it be possible that your installation media is faulty? I have seen this type of BSOD a couple of times when setting up computers, and what I found out was that it was the installation media that was the culprit with the exeption of a bad RAM chip on one occasion.
But you're correct, the SATA compatibility mode has been removed from BIOS on the latest model ThinkPads.
If installing Windows 7, are you planning on installing it in UEFI or in legacy mode? Because then you'd need to adjust your Secure Boot - UEFI/Legacy boot settings before installation.
ThinkPad W540 (20BG) - i7-4800MQ/24GB // ThinkPad T440s (20AQ) - i7-4600U/12GB
ThinkPad T440p (20AW) - i7-4800MQ/16GB // ThinkPad Helix (3698-6EU) - i5-3337U/4GB
ThinkPad W520 (4282-W4Q) - i7-2720QM/32GB // ThinkPad T400 (2767-W1C) - P9500/8GB
ThinkPad T61 (7665-CTO) - T7700/4GB // ThinkPad T60p (8741-C2G) - T7400/4GB

Similar Messages

BSODs During Install

I been trying to install Windows 8.1 on my desktop custom build for a month and a half. I purchased a Giagbyte 78LMT-USB3 motherboard with an AMDFX-4103 processor and a 4 GB stick of Patriot DDR3 RAM. I purchased a Crucial M500 SSD and also a
new 700 Watt Rosewill PSU. I also have 2 other HDDs, a 2 TB WD Green drive and a 360 GB Samsung drive from an old HP computer that died.
I tried to install to the SSD, and I did get it fully installed once. However, I received BSODs within a minute of boot. Many different codes, DVP WATCHDOG VIOLATION, NFTS FILESYSTEM, MEMORY MANAGEMENT, plus others too numerous to remember.
I updated the MB BIOS with my flash drive, didn't seem to help. I tried to update the MB Drivers but it would always bluescreen before I could do anything.
So I decided to re-install Windows. I tried several times and received several BSODs during the setup itself. I received a CACHE MANAGER BSOD, NTFS FILESYSTEM BSOD and several BSODs without any specific problem listed. I updated the SSD
firmware to the latest version, March 25,2014, and still got BSODs on all install attempts. I then decided to attempt to install on my HDD. I attempted to install on the Samsung drive and received several more of afore mentioned BSODs. I have yet
to get Windows 8.1 installed to a point where it runs more than 1 minute without a BSOD. Right now I can't even get it to install.
I don't have any dump files to upload since it BSODs during the install attempts. Not sure where to go from here.
Edit: I also ran MemTest on it for 4 passes and it came back with 0 errors.

Check the SSD forums. Sometimes there are settings in the BIOS that will greatly affect how well a system tolerates an SSD.
-Noel
Detailed how-to in my eBooks:
Configure The Windows 7 "To Work" Options
Configure The Windows 8 "To Work" Options

Getting BSOD error while booting

Hi,
I am getting BSOD error while booting using bootable pendrive.
Could you guys please provide the possible solution
Regards,
Chandan

Hello,
To troubleshoot the issue, you need review the dump file. We may find out the which file or driver is triggering a BSOD. And in most cases, BSOD is triggered by driver issue.
Are you doing OS deployment via bootable pendeivce? How do you created the boot image?
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

BSOD Error while booting Thinkpad L440

Link to image
Hi All,
I'm getting a BSOD Error while booting my Lenovo Thinkpad L440 system.
Please help.
Moderator note: large image(s) converted to link(s): About Posting Pictures In The Forums

Hello,
To troubleshoot the issue, you need review the dump file. We may find out the which file or driver is triggering a BSOD. And in most cases, BSOD is triggered by driver issue.
Are you doing OS deployment via bootable pendeivce? How do you created the boot image?
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

There is always a blue screen appears after the Apple logo during the booting process. And then everything is back to normal. What is this thing? Is there something wrong with my screen or something?

There is always a blue screen appears after the Apple logo during the booting process. And then everything is back to normal. What is this thing? Is there something wrong with my screen or something?

Nah - that's just the normal boot process.
Clinton

Kernel Panics during system boot, and no kind of network connectivity

I've tried quite a lot of things here, so please read them all before you suggest something - and thanks for taking a look at my question (-:
I recently got my Mac Pro back from the AlaskaMacStore (not an actual apple retail store, and they aren't very good at that), having brought it in for loss of FW800. They sent it to Apple, and I received it back, supposedly with a new motherboard - and my FW800 working. However, it proceeded to kernel panic (complete visual system freeze, not greyscreenofdeath - oddly enough, iTunes would never stop playing during them) at least once a day after that.
Not wanting to deal with them again, I just used it like that and put up with it - but soon enough, I lost any sort of network connectivity as well. With AirPort connected to my Time Capsule's network (which worked fine on my Macbook Air and iPhone and various other devices), I was being told "...Self-Assigned IP address, and thus may not be able to connect to the internet...". Even connected directly via Ethernet to the Time Capsule, or directly via Ethernet to the cable modem, or directly via Ethernet to another Mac, or connected to another Mac's ad-hoc network, I could get absolutely no network communication going on of any sort.
This was too much for me, as all of my work requires frequent and heavy internet access, so I gave in and took it back to the local mac store equivalent - they charged me 100$, and kept it two days, just to tell me they 'couldn't reproduce the problem'. I took the Mac Pro to a friend's house, and went through the same tests - connected to his modem, with his Ethernet cords, and to his wireless and other macs. Same deal, no connection or indication of a networking being connected beyond that blasted 'self-assigned IP' in Network prefs.
Having no desire to be defrauded by the local fools again, I decided I didn't really have anything important on my internal hard drive, and decided to wipe the internals and re-install Leopard. My horrible luck continuing, I found my only Leopard disc to be cracked, prompting me to drive out and purchase a new one. Inserting this into my Mac Pro's drive, I found myself faced with yet another horrible problem.
During the boot to the Leopard DVD, the grey loading screen (with the apple logo and the spinner) simply froze with the spinner pointing left. I left it for a while, expecting this to be part of what I'd previously experienced with the slow boot-from-DVD on a Macintosh... but after 30 minutes of waiting, I got quite worried, and booted back into my normal OS by holding down Option and selecting my RAID.
Now, note this for later - it booted absolutely fine, and though I still had no network connectivity, the system had no problems. I changed the startup-disk to my RAID and then back to the Leopard DVD, naïvely thinking this would solve the problem, and ran into the same problem after restarting and booting to the Leopard DVD again.
Dismissing this as a optical drive problem (haven't had occasion to use optical media in nearly 3 years, don't really trust it in general), I booted the Mac Pro into Firewire Target Disk mode, and connected it to my Macbook Pro, and then booted the Macbook Pro from the installation DVD. Again, note carefully here - there was nothing wrong with the DVD itself, as the Macbook Pro had no trouble booting to the DVD.
I used Disk Utility to preform some planned modifications to the internal drives of my Mac Pro (erasing my previous inefficient RAID setup in favor of a new, faster (but less secure) RAID0 striped setup for my main two 1TB drives), and then proceeded to install a fresh Leopard onto the newly minted RAID. I usually cancel the 'disc checksum' that the Leopard DVD runs on itself, not really worrying about it, but in light of recent possible problems with the DVD, I went ahead and let it run - no problems, it completed and went straight into the normal install.
The install itself completed in a timely manner, and my Macbook Pro re-booted automatically, to the newly Leopard-ed RAIDed internals on the Mac Pro. It booted to the new install without a hitch, played the Leopard intro video, and continued to the setup cube. I opted to shut down (by hitting command-q and selecting the shut down option), so I could set it up on the Mac Pro instead.
Surprised was I, when I experienced the same grey loading screen freeze on the Mac Pro, booting to the newly clean install on the new RAID, that I had seen trying to boot to the Leopard disc. Worrying that my Leopard disc was, infact, corrupted in some way, I tried placing the Macbook Pro into firewire Target Disc Mode, and booting that drive over FW800 on the Mac Pro. Same freezing problem occurred.
Well, now, the only installation that HADN'T kernel panicked on boot was the old install, and that had been erased for the new RAID configuration, so I was left without a way to boot to a working install and test things from the Term. This left me with Single User Mode, which I immediately booted into.
Interestingly enough, there was no problem booting into Single User Mode - so I poked around a bit before mounting, and I had seemingly fine access to the entire filesystem of the new Leopard install, and nothing looked screwed up to my (albiet untrained) eye. After mounting and continuing the boot, it froze - but since this was verbose SUM, and not simple normal boot, I was able to see exactly where it froze: something about 'mDNSResponder starting', and then no input or output was accepted, leaving me assuming it had kernel panicked again.
To test this, I again attempted to boot from the Leopard DVD on the Mac Pro, this time in verbose startup mode, and watched it freeze up at exactly the same point. After a little googling, I found some suggestions to disable the launchd plist for mDNSResponder - I tried SUM again, and did so, then continued with the boot. This time, there was no output relating to mDNSResponder, so the launchd change had worked; however, it still froze - this time, right after three lines, first something along the lines of 'Login Window Application Starting', and then two lines printing Ethernet IDs of some sort. After those Ethernet related lines, it again froze.
What with the DNS and Ethernet bits showing up in the freezing, I was getting worried this was still tied into my NIC in some way, so I unplugged my Ethernet cords and tried the exact same boot again, and again disabled mDNSResponder. This time the only sensible thing before the freeze was the 'Login Window Application Starting' line, which seemed perfectly normal. I doubt there is/was anything wrong with that, so I'm assuming there's still some networking-related process freezing/panicking the computer, and it just doesn't happen to log in a visible way during startup.
Does anybody have any suggestion as to what such a process might be, and how I can at least pause or kill it from SUM, so I can at least finish booting the computer?
If I can't figure out a solution to this, I'll have to buy a new Mac Pro tomorrow morning... I have very, very pressing matters that can't wait for a new Mac Pro to ship, nor can they wait for me to ship this one to Apple and back (I live in Alaska, we have at least a weeks wait if nothing is seriously wrong when sending an Apple product in for repairs on our own), and nor can I wait 2 days for the local Apple store to tell me there's nothing wrong with it and then have to wait another week to, again, send it to Apple myself. I don't want to have to shell out for a new, expensive computer when there's a (most likely) perfectly good one sitting here... so any help would be MUCH appreciated.
If you've read this far, phew, you deserve a cookie. That was one... long... post.
(If you care, this post was cross-posted to my blog, at http://blog.elliottcable.name/posts/macpro_epicfail.xhtml)

Talk about bad luck.
The point at which the system "freezes" with the gray spinner (and just after the login window app starts) is right about the point the accelerated drivers should kick in for the video card.
So a couple things could be going on.
1) bad video card dragging down the bus
2) The system board is fubar - this I think is likely - issues with onboard ethernet, and whats seems to be video card related.
I would hazard to guess that the PCI-express bus has something wrong with it, ethernet and video live on the bus, SATA, and USB live in the southbridge.
So, looks like a trip to a certified apple dealer/repair center is next for your Mac Pro - probably for a new system board, again?
Something tells me that your system really didn't get to Apple for a new board.
You can verify by looking at the serial ID tag on the system board, note the rev and serial # before and after such repairs.

Problem with udev during the boot

Hi guys,
Sorry if I didn't post this message in the good section but I didn't find any support section, so I supposed that this section was the most apropriate.
So, I have a really ennoying problem with udevd since the latest kernel upgrade (3.2.2-1) during the boot.
I have the following error at the boot:
"udevd[37]: No such file or directory." and then the OS is unable to mount the disks and give me the weakest shell ever while saying me "You're on your own". Thank you Arch!
I can't find any informations on google about this error, and I d'ont find a complete explanation of udev debug (specialy because no logs are written at this moment).
Thank you very much guys.

GreenTime wrote:
qaws or someone else:
Could you elaborate on how to just reinstall the kernel? Somehow I'm stuck
Usually, you'll need a live CD (I recommend an ArchLinux Installation CD) or an LTS kernel sitting around on the same machine that can get you more or less into your favored machine. It can also be done, by pxe/diskless booting from an installation (I'm a fan of quick and efficient)! Then you have to mount all the necessary partitions /, /usr (sometimes /var if you need your packages) and most importantly /boot. They have to be mounted underneath the rescue system being used , usually under /mnt. Also needed is a mock-up of your /proc. /sys and /dev. Once they are mounted accordingly, then you chroot into your installation you need to fix. It helps if the rescue system has the same kernel, because the chroot'ed system usually tries to build your kernel based on the rescue system, but if you have your kernel package handy, it will build it with the packages modules & kernel.

Kernel crashing during first boot on VirtualBox

I'm trying to get install Arch Linux on VM running on my Windows 7, I set up the machine and everything else that was in the guide on wiki, but during first boot, I get kernel error and machine freezes.
This is screenshot of error:
http://i.imgur.com/msTUERH.png
I'm new to Linux so I might have missed something obvious, don't be too harsh on me please
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --

Mhm, I only have to suggestions (I am not a kernel-pro though):
Enable PAE/NX at the "System -> Processor" tab in the vbox configuration
If that does not work disable it and try to reconfigure the vm with minimal settings in virtualbox. For example, disable audio, networking, usb, 3d etc... and see wether your machine crashes or not.
Last edited by Resauce (2014-12-08 07:12:47)

Rc.sysinit and btrfs: not show partition during the boot

Hi,
I see, during the boot, that show only partition NOT in btrfs...
e.g i have two partitions: /dev/sda1 for / in ext4 and /dev/sda3 for /home in btrfs
during the boot I see only /dev/sda1 clean but I don't see /dev/sda3...
But partition mounted correctly.
This my fstab
/dev/sda1 / ext4 defaults,relatime,commit=10 0 1
/dev/sda3 /home btrfs defaults,relatime 0 2
/dev/sda2 swap swap defaults 0 0

falconindy wrote:
btrfs's fsck prog doesn't use the same name scheme as every other fsck prog (fsck.FSNAME). I don't know if renaming /sbin/btrfsck would be lethal to other btrfs utilities, so a symlink takes care of it:
# ln -s /sbin/{btrfsck,fsck.btrfs}
uhm...thank's...
I'll try later, now I have experimented with udev, hal, usb device, xfce, default mount options

Token and smart card reader are not detected on Mavericks if not plugged on a USB port during system boot

Well, both token and smart card reader are not detected on OS X 10.9 if not plugged on a USB port during system boot. So, if I am already working within the system and need to use my certificates I have to plug the token or smart card reader on a USB port and restart Mavericks.
Token is a GD Starsign and Smart Card Reader is a SCR3310 v2.
Thoughts?

SCS is a very good app, since I've read that Apple has discontinued support for PC/SC interfaces after the release of Mountain Lion.
(My previous installation was a Mavericks upgrade from Lion)
However, I don't know what and how to debug using Smart Card Services. Do you know any commands to use?
Apparently, the SC reader reports no issues: the LED is blinking blue when no smart card is present and becomes fixed blue when a smart card is inserted – according to the manuals, this shows that there is correct communication between the OS and the CCID reader.
I don't know what to do; I'm beginning to hypothesize it's a digital signer issue. In fact, my smart card only supports one application called File Protector (by Actalis) to officially sign digital documents. This application seems to have major difficulties in identifying the miniLector EVO.
The generic and ambiguous internal error comes when I try to manually identify the peripheral.
Athena CNS is one of the Italian smart cards and is automatically recognized and configured (so it's correct – no doubts about this), while "ACS ACR 38U-CCID 00 00" seems to be the real name of the miniLector.
(I'm assuming this because System Information also returns that the real manufacturer is ACS... bit4id is a re-brander)
However, when I click on it and then tap OK, it returns internal error.
As first attempt, I would try to completely erase&clean File Protector files to try a reinstall. Then, if this still doesn't work, I'd debug using the terminal.
So:
- Do you know any applications to 100% clean files created by an installer?
- Do you have in mind any solutions that I might have forgotten?
Thanks in advance from an OS X fan!

Speaker pop during PowerBook boot

Ever since installing Leopard, my PowerBook makes a rather loud pop noise from the internal speakers. It always happens during the boot process, at the point where the gray screen with the spinning gear changes to the blue screen. At that point, one of my speakers makes a single loud pop. It is usually the right speaker, but it has happened from the left once or twice. I don't have any external speakers connected. Anyone else seeing this?

I also have one of the new iMacs - one of the 20" models. I started having the same problem just a couple minutes ago. It worked without any problems for a solid week and a half, and now this? Puts a damper on the track I was working on in Logic. It just popped 3-4 times and then no sound eventhough my song was still playing and the volume meters on the mixer for each track were showing movement. Tried playing some songs in my iTunes library and still no sound - speaker output meter is at the halfway mark. My first thought was hardware issue, but who knows.

Monitor Signal Drops During XP Boot

Hello All!
This is my first post on this forum, so please forgive me if I make any mistakes. I have recently bought a MSI Motherboard, and all was well until I turned my pc on without the monitor plugged in - now, the monitor signal drops during the boot up (at the xp screen when the bar is moving across the screen).
My system setup is this
Athlon xp 2000+
MSI K7n2G Board
Using the on-board graphics
256mb DDR Kingston RAM 27000 (fully compatible with the board)
120 GB Western Digital hard disk
Liteon cd writer 52x 24x 52x
Pioneer 106 DVD writer
I believe I am running BIOS 3.5
I tried booting up in safe mode and that boots up fine. I did a system restore to the day before I accidentally turned the machine on without the monitor plugged in, and that didn’t make any difference.
I am clueless as to why this doesn’t work, and am hoping someone here could tell me how to solve this problem.
Many thanks for any advice, and thanks for reading,
Regards,
Rupz112

I have come across a similar problem before. The problem was that the monitor couldnt support the default resolution of windows XP so I went in safe mode and lowered the resolution and the problem was solved.

Hi, can iMovie give pronlems during the boot process from my iMac Mine. I have often after working with iMovie that i get during the boot Psi SDXH pause so the boot process stops

hi,
can iMovie give problems during the boot process from my iMac Mini?
I have often, after working with iMovie that i get during the boot Psi SDXH pause
so the boot process stops at this point
I have often reinstall OSX Mavericks
regards,
HenkfromWinterswijk
Netherlands

Hello Federico,
Your EliteBook is a Business model. Your issue would be best answered on the HP Enterprise Business Community Forum
Good luck!
↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

My iMac starts up and then shuts itself down during the boot up process. it shuys down half way through the Apple logo appearing. any ideas how to fix?

My iMac starts up and then shuts itself down during the boot up process. it shuys down half way through the Apple logo appearing. any ideas how to fix?

Hi daveormond,
I'm sorry to hear you are having these issues with your iMac. If you continue to have issues with your Mac shutting down part way through the boot up process, you may find the troubleshooting steps outlined in the following articles helpful (given your description, it sounds like it could be either issue, or a combination of both):
Mac OS X: Gray screen appears during startup - Apple Support
OS X: When your computer spontaneously restarts or displays "Your computer restarted because of a problem." - Apple Support
Regards,
- Brenden

We want essbase to start during server boot via init.d as the essbase user.

We want essbase to start during server boot via init.d as the essbase user.
Do we have any documents for this.
Opereating System : Red Hat Enterprise Linux Advanced Server x86-64 (AMD Opteron Architecture)
Version : 11.1.1.1.00
Regards,
Mink
http://newhyperion-blog.blogspot.com/

We want essbase to start during server boot via init.d as the essbase user.
Do we have any documents for this.
Opereating System : Red Hat Enterprise Linux Advanced Server x86-64 (AMD Opteron Architecture)
Version : 11.1.1.1.00
Regards,
Mink
http://newhyperion-blog.blogspot.com/

W540: BSOD during CD boot

Similar Messages

Maybe you are looking for