T410s (integrated) overheat and shutdown

Is that just me or someone else has this problem too? I know it's a known problem for T410s with discrete graphics but mine has only integrated graphics and it still suffers from overheat. It normally happens while playing games. Sudden shutdown without notice.

Yep, getting about three to four unexpected shutdowns per day if in a graphics intensive game -- heat seems excessive from the vents. There is a thread on T410s unexpected shutdowns. I'll seek and link..
T410s, X60, Z60, T41, Lenovo S10, Lenovo K-Series IdeaCentre tower

Similar Messages

  • G405s overheat and shutdown

    hi all..
    i just bought this laptop 2 weeks ago.. since bought i got this overheat problem and tends to shut my laptop down.. my laptop BIOS right now ver 3.7 but still got this problem.. by using HWMonitor with idle states the temperature are around 80~90 C.. and while i play games it rose up until 120C before shutdown.. is it the hardware problem or the software? can sombody help me plz.. 

    Download and install this AMD Overdrive 4.2.6.0659.In newest version is stupid termal margin no real temperature of cpu.hwinfo is good too.You may consider buy cooling pad and performance thermal paste.

  • Why does my mac overheat and shutdown when i play games?

    It used to happen when i had windows on bootcamp, i got fed up with this and stoped using it.
    However yesterday i was using it to play a simple game of pool on facebook, full screen, and it turned off.
    I touched the top left and it was way too hot like almost too hot to touch.
    I just clicked my mouse and it came back on and i closed everything down and just let it cool off and it stayed on.
    Anything i can do to help the problem?
    Cheers
    Jay

    Make sure the vents at the bottom of the screen are clear of dust (shut it down and vacuum).
    When running, bring up Activity Monitor to see if anything is driving CPU usage to excess, say consistently greater than 25% to 30% or more
    Install iStat Pro to monitor what is generating heat.
    Run the Apple hardware test to see if it spots any obvious hardware issues that could contribute to the problem. You'll need your original OS X disk to run it.

  • ZV6000 Overheats and shuts down

    My ZV6100 has started to overheat and shutdown. I have noticed the cooling fans are not coming on as the computer gets hot. However after overheating and shutting down if I wait a few minutes and restart the computer both fans come on and stay on. So it's like this, when I start the computer and its cold the cooling fans come on for a short time (at startup) and then go off. As the computer warms up and then gets hot the fans do not come on as they should to cool it back down. Any ideas?
    This question was solved.
    View Solution.

    Try a hard reset of the bios, power down, unplug the power cord, remove the battery, hold the power button down for 30 seconds, insert battery and connect power cord, power up, see if anything changes.

  • Incredible overheats and shuts down using GPS.

    My phone overheats and gets in a shutdown reboot loop when using GPS. It did this while plugged into car charger. I concluded it was overcharging. Today I tried using GPS without charger. There was direct sun hitting the screen (I'm in Florida). It soon shut down and got in the Terrible Loop. I've read a lot about this online and there are many different experiences and views. The phone does not do this inside the house with a wall charger.
    Does anyone know if Verizon has a definitive answer for this. I've read of other customers with this problem getting replacement phones that do the same thing. Someone speculated it was the original screen used for the Incredible (made by Samsung).
    I checked on getting a Garmin navigation system and read they also can overheat and shutdown. I prefer to use my phone but don't want to have to drive holding it in front of the air conditioner with an umbrella over it to use Google navigation.
    Any info and advice are appreciated.
    Thanks to all.

    marchhare wrote:
    My phone overheats and gets in a shutdown reboot loop when using GPS. It did this while plugged into car charger. I concluded it was overcharging. Today I tried using GPS without charger. There was direct sun hitting the screen (I'm in Florida). It soon shut down and got in the Terrible Loop. I've read a lot about this online and there are many different experiences and views. The phone does not do this inside the house with a wall charger.
    Does anyone know if Verizon has a definitive answer for this. I've read of other customers with this problem getting replacement phones that do the same thing. Someone speculated it was the original screen used for the Incredible (made by Samsung).
    I checked on getting a Garmin navigation system and read they also can overheat and shutdown. I prefer to use my phone but don't want to have to drive holding it in front of the air conditioner with an umbrella over it to use Google navigation.
    Any info and advice are appreciated.
    Thanks to all.
    Marchare, you will want to make sure that you have the right fuse in your car for your cigarette lighter, also are you using the charger meant for the phone or some third party charger? Sometimes the charger can go faulty and cause problems, usually not sending power, but occasionally it can send too much. Also , the phone will shut down if the battery is overheating, usually you will get a orange-green blinking  before it gets to this point.
    Personally, I don't plug my phone in while using the GPS until it starts getting low on the battery. While they sell the carmount, it isn't advised to use the gps in direct sunlight either, contradictory I know. When your phone overheats and shuts off, you will want to let it cool down before trying to turn it on again. If this doesn't solve the problem then you likely need a new battery or perhaps even a new phone.

  • Clock problem and shutdown problem! Are they related?

    Having a problem with my Dual 2 GHz Power Mac G5
    A few days ago I noticed that my clock was not showing in the menu bar in the upper right corner of my desktop.
    I went into System Preferences and went to Date & Time. Under the clock tab “Show Date and Time in Menu Bar” the box was not checked off. I checked it off and went to the “Date and Time” tab. The date and time was correct. I then checked the box “Click the lock to prevent further changes” to lock it. The date and time did not show up in the menu bar. I then went back to the tab “Show Date and Time in Menu Bar” and the box I checked was not checked off even thought the lock was still locked.
    I then moved my cursor up to the menu bar in the upper right corner to see what would happen and the spinning beach ball started up but only for the original icons such as Bluetooth, Mobile Me (which I do not use), Time Machine, Spaces (doesn’t indicated the number when I switch Spaces, etc. The icons Norton Anti Virus and Tech Tool Pro in the menu bar are okay.
    Also, when I attempt to shut down my computer the system clears the icons from my desktop except for a picture I have on my desktop and I get a gray wheel spinning and the system just hangs until I press and hold the on/off switch. I don’t know if the clock and shutdown problems are related.
    The only new software I loaded recently was Skype with Logitech WebCam for the Mac and Quicken 2007 (Had a problem with Quicken 2006). They both are working okay.
    And ideas on why I cannot get my clock to show up and my computer to shutdown?

    You may have to consider a new post in the Hardware forum area for the computer
    model and build/year; if there is a possibility of some basis the matter could be in
    the machine and not the software running within it.
    Your last two/three posts are in the Leopard 10.5(.8) forum area and do indicate
    some kind of problem where troubleshooting the computer to discover if the matter
    at hand would be either hardware or software based, may be the way to go.
    The link to the 10.6 Snow Leopard forum won't be of help if your computer is a
    PPC-based G5 tower, or other older pre-Intel configuration. And I remember
    your earlier questions about the iMac G4 and some other issues in the past.
    You may ask the moderators to put your post in a new thread of its own, in the
    Leopard 10.5 area; so as to not 'piggy-back' another topic; even though some
    of the odd issues you've had seem similar to this OP's topic line and appear to
    be in the same general series of hardware. {The question here seems valid.}
    The routine suggestions to check, test, verify, and perhaps repair or replace
    the system; save a bootable clone to suitable external standalone device if
    testing a suspect computer's viability is recommended; and the basics if not
    already tried to help isolate the issue(s) as you've posted elsewhere, may be
    of some help to try and do; so in that matter, a new thread of your own is best
    for your own directed feedback. Since this kind of advice applies to most any
    situation, including troubleshooting what may be hardware or software, I'm
    adding my two and three-tenths cents worth here.
    Your original included Apple Hardware Test may be of some help, in the process
    of elimination; but is not conclusive, so other methods would be also suggested.
    Some ideas appear to cover the same ground. However, system corruption or
    disc failure can also manifest itself in odd ways & affect things indirectly for a time.
    • OS X Maintenance And Troubleshooting
    http://www.macattorney.com/ts.html
    • Mac OS X BASIC TROUBLESHOOTING & MAINTENANCE
    http://www.gballard.net/macrant/osx_troubleshooting.html
    • Troubleshooting Tips for computers:
    http://www.stcdio.org/offices/cem/mediaandtechnology/cem-computer-classes/troubl eshooting.html
    So, at the risk of inadvertently alienating the OP, I am posting this as
    a general help to following readers at some later time; and it may not
    be too simple for a refresh course.
    Some software issues can be resolved by repairing disk permissions,
    and re-applying the last OS X update Combo file over the same one
    already in the system; or if not up-to-date already, check & repair all
    the general items and then apply the last Combo update.
    A too-full hard disk drive can compromise the system integrity, so that
    is a matter of course to keep up on what resources exist and remain
    for the OS X to function correctly and for apps to multi-task together.
    However that works out...
    Good luck & happy computing!

  • T410S Integrated Overheating

    When I run anything CPU intensive (eg, Skype, Matlab etc), my  T410s (integrated graphics) appears to be overheating and crashing.
    It gets very hot and then the screen goes black and it turns off. See the attached chart of heat, 90C seems far too high:
    http://img191.imageshack.us/i/speedfanreadings.png/
    Any suggestions on what I should do? I just updated the bios, but it doesn't seem to have changed anything.
    FWIW I just reinstalled onto an OCZ Vertex and I'm using Windows 7 x64 drivers not Lenovo drivers. Overheating didn't seem to be a problem before the reinstall, using the same setup but with a normal hard disk.

    The Power Management driver is absolutely essential. Windows installs a slightly older driver anyway by default I believe.
    Try taking off the keyboard and cleaning out the fan. If that doesn't work, tighten the screws on the heatsink.
    Power Manager works fine for me on my T400, as does the switchable driver except for the Intel GPU issue; works perfectly fine elsewhere. Power Manager just launches slowly.
    Lenovo's Intel wireless drivers seem to be just repackaged Intel drivers with some fluff removed.
    Mind posting your machine type?
    W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
    X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
    Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen

  • Z10 Overheats and packs up

    I had an issue over the weekend where my phone would overheat and show a blue screen. I would be on Skype video call and within 5 minutes, the phone would overheat, go from a streaked line to a full blue screen (anyone remember windows blue screen of death?). Then my phone will shutdown and go into reboot. this happened for a few times until it packed up and would not reboot again. I plugged it into DC Power, and the red light would come on and once I put the battery in, it will go off. I called tech support and they told me that it was the battery. I never imagined that few months into my switch to BB Z10, I would have to dust off my old 9930 and start using it until I get the new battery.
    Has anyone encountered this issue or am I alone on this???

        @Ebere,
    Having a reliable phone is definitely a must! I apologize for the inconvenience this has caused. I'm sure the new battery will resolve all these concerns.
    Keep me posted if you need further assistance.
    JohnB_VZW
    Follow us on Twitter @VZWSupport

  • Macbook Air 2011 CPU Maxes Out then Overheats and Shuts Down...

    I've been having this problem for a while now but have learned to deal with it with SMC Fan Control to basically keep my fans maxed out at all times. This is obviously not ideal.
    The problem is that at any given time some small, random task in activity monitor shows CPU usage that is very high, often at least 50% CPU and other times as high as 120% It has happened with the tasks like dock, safari web content and virtually any other task you can imagine.
    For example, I just tried emptying my recycling bin and it hung half way through then my computer shut down. What is going on here?
    Details:
    - Macbook Air mid-2011 running Mavericks
    - Never have more than one app open at any given time, usually just Safari with about 5 tabs, max
    - 3rd party applications running in background include Dropbox, Copy, Backblaze, Flux, Sophos anti virus, Jumpcut, Caffeine and that's it
    If I'm doing something like a Time Machine backup, I have to disable Wifi, max out the fans and only then will the Macbook Air remain cool enough to complete the backup, otherwise the Time Machine process maxes out the CPU, overheats and shuts down. This happens with virtually everything now.
    How can I start trouble shooting this problem? I've run the hardware and system repair checks with no results, done an SMC reset, etc.
    This really seems like a software issue more than anything, like something related to the way tasks/processes are handled...any ideas anyone? This is such an annoying problem!

    Do the problems also occur in "Safe Mode"?
    Safe Mode or "Safe Boot" is a troubleshooting mode that bypasses all third party system extensions and loads only required system components. Read about it: Starting up in Safe Mode
    You must disable FileVault before you can start your Mac in Safe Mode.
    Starting your Mac in Safe Mode will take longer than usual, graphics will not render smoothly, audio is disabled on some Macs, and some programs (iTunes for example) may not work at all.
    Merely starting your Mac in Safe Mode is not intended to resolve the problem, it's to observe its performance without certain additional components.
    To end Safe Mode restart your Mac normally. Shutdown will take longer as well.

  • IOP startup and shutdown as windows services

    Hi,
    Is there a way can we have IOP startup and shutdown as windows services instead of running the bat files?
    Thanks,
    Hari Devarapalli

    Yes. You can install IOP as NT service and start/stop it.
    Please refer to "Installing Integrated Operational Planning as an NT Service" in the IOP install guide.

  • Startup and shutdown of standby database

    Hi
    Expert,
    i want to know step by step process of startup and shutdown of standby oracle 10g database on windows and linux server.
    thanks

    Any form of integration with standard oracle startup/shutdown scripts for a dataguar configuration?
    Or this is targeted by the broker perhaps?
    For example putting Y inside /etc/oratab but also with other flags inside it or any other files around?
    Or something like this:
    - make a startup mount
    - select switchover_status from v$database
    in case output is "TO PRIMARY"
    alter database recover....
    otherwise if it is "TO STANDBY"
    alter database open
    or somethjngi similar...

  • Using launchd to send an email on startup and shutdown

    Hello All !
    I'd like to get an email whenever my Mac starts up and shuts down, since I have to leave it unattended for quite some long periods of time (and even with the help of a UPS, power goes out anyway...). My Mac runs under Mac OS X Lion.
    I found some help on the Internet, mainly from this page : http://www.syntaxtechnology.com/2009/06/email-on-shutdown-and-restart/ , which applies to Linux, and hoped it could work on Mac OS X (I thought at first I could just drop a script in something like /etc/init.d/ or /etc/rc.d/rc5.d but well... we have launchd instead...).
    The first method listed in the page above worked well, but sends an email only on startup (for a reminder: you add a line that starts with @reboot in your crontab, and a command that sends directly an email).
    I then tried to adapt the second method to Mac OS X, and succeeded partially: I wrote a small script based on what was shown on that page (a start and stop function, start gets called when the script is started, and stop gets called based on a trap on various kill signals, with an infinite wait loop: see below). I also wrote the plist file, loaded it in launchd and rebooted my Mac several times to test everything.
    I get an email on each startup (yeah!), but the shutdown mail gets sent only at the next startup. So I guess that postfix gets killed by the shutdown process *before* being able to send my shutdown email :-(
    So here are my main questions, if someone can help me:
    1. is there a way to precisely call a script during the shutdown process, meaning giving it a priority so it gets called before postfix dies ? (like the rc directories and the naming conventions (KnnScriptName and SnnScriptName) found on some Linux/Unix).
    2. is it possible to do that with launchd ? if not, what would be the Mac OS X sanctionned way of doing this ?
    Other things:
    3. my shell script writing ability is kind of rusty, so maybe I made some "very bad shell writingTM": l'm not sure putting an infinite while loop with a 15 second pause in it is the best way of telling a script to do nothing. There might other things in there that would make an Unix guru jump out of his chair: please tell me :-)
    This is my plist:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC “-//Apple Computer//DTD PLIST 1.0//EN” “http://www.apple.com/DTDs/PropertyList-1.0.dtd”>
    <plist version=“1.0”>
    <dict>
    <key>Disabled</key>
    <false/>
    <key>Label</key><string>org.amarante.startshutemail</string>
    <key>ProgramArguments</key>
    <array>
    <string>/Library/Scripts/startshutemail-launchd.sh</string>
    <string>start</string>
    </array>
    <key>RunAtLoad</key><true/>
    </dict>
    </plist>
    And this is the script that does the job:
    #!/bin/bash
    # PHL 20120604 startshutemail-launchd.sh
    # Send an email on startup and shutdown (version for launchd)
    # Based on script and explanations found here:
    # http://www.syntaxtechnology.com/2009/06/email-on-shutdown-and-restart/
    # Modification history
    # PHL 20120604 v01 First version
    # Environment variables #################################################
    DEST_EMAIL="[email protected]"
    SRV_NAME=Amarante
    EVENT_TIME=$(date +%Y/%m/%d-%H:%M:%S)
    RESTART_SUBJECT="[$SRV_NAME] $EVENT_TIME : System Startup"
    RESTART_BODY="This is an automated message to notify you that $SRV_NAME started successfully at $EVENT_TIME."
    SHUTDOWN_SUBJECT="[$SRV_NAME] $EVENT_TIME : System Shutdown"
    SHUTDOWN_BODY="This is an automated message to notify you that $SRV_NAME is shutting down now ($EVENT_TIME)."
    # Functions ##########
    stop()
    echo "$SHUTDOWN_BODY" | mail -s "$SHUTDOWN_SUBJECT" $DEST_EMAIL
    return 0
    start()
    echo "$RESTART_BODY" | mail -s "$RESTART_SUBJECT" $DEST_EMAIL
    return 0
    # Main part #########
    case $1 in
    stop)
    stop
    start)
    start
    esac
    # trap kill signals to send an email
    trap stop HUP INT QUIT ABRT KILL ALRM TERM TSTP
    # sleep until killed
    while :
      do
        sleep 15
      done
    Thanks for your help, and any comment :-)
    Paul-Henri

    Thanks a lot for your answer, Camelot, even if it sorts of confirm what I suspected. Pinging a machine from an external observer is a solution, but it will also report broken links problems and not only a computer shutting down, and it raises the next tier of problems, general network reliability after individual system reliability. It's something I'll have to look at for sure.
    It's weird there isn't any way to access the way the shutdown process works.
    One of the commenters (#14) on the page from Syntaxtechnology had a similar problem: he added a "sendmail -q" in his script to force sendmail to go to work and service the queue before shutting down, which I can try, but he also added a delay to the stop process of sendmail, which is something I'm not sure I can do on Mac OS X (and that might disappear one day with one of the OS updates).
    Unless there is a way to change the launchd.plist file for postfix and add an ExitTimeOut option in it (I found this idea here : https://discussions.apple.com/message/17229690#17229690 )
    Cheers,
    Paul-Henri

  • 10.6.1 Slow Startup and Shutdown

    Did anyone notice the difference between the 10.6.1 startup and shutdown times and the 10.6 times ?
    I had to do a clean install of 10.6 and ignore the 10.6.1 update to get back speed in startup and shutdown.
    Is there anyway to solve this.
    Thanks.

    I had the same problems, and I figured out the cause. It seems that somehow the ownership of my root directory (/) wasn't assigned to the root account anymore, but to myself instead. This made the kernel prelinking fail since it requires that root is the owner. This is how you solve this after launching the Terminal app:
    {quote:title=terminal commands}sudo chown root:admin /
    sudo kextcache -system-prelinked-kernel
    sudo kextcache -system-caches{quote}
    You'll have to enter your password after the first command.
    Hope this helps someone, since it was really frustrating to have these slower startup/shutdown times for me.

  • I can't forcequit firefox and shutdown my computer, nor can I open up any other programs or applications. Does anyone know how to fix this? please help this poor soul.

    I can't forcequit firefox and shutdown my computer, nor can I open up any other programs or applications. Does anyone know how to fix this? please help this poor soul.

    You can force quit applications
    >Force quit
    if that does not work you can force quit a computer shut down by hold the power button for an extended period.

  • HOWTO: Create a Boot Configuration That Has No Driver Signature Checks. Disable Driver Integrity Checks and Install a Custom Non-Signed Driver

    Hello,
    Recently, I had a task where I needed to install a custom non-signed driver onto my Windows 8 64-bit setup. As it is known, Windows has driver enforcement policies that, as a security measure, do not allow you to install non-signed drivers.
    I did not want to alter my current boot configuration so I decided to create a separate boot entry that would have driver signing policies disabled. For some reason I did not find any good source that would contain a step-by-step instruction on completing
    this task, so I decided that I'd better share my experience here.
    Lastly, there are multiple ways how you could turn off driver enforcement policies, but I find the way to do this via boot manager.
    Here's how you can do that.
    1. Press WindowsKey and type 'cmd' (without quotes) to find Command prompt, then click Command prompt icon. If you have User Account Control turned on, hold Ctrl+Shift keys pressed when clicking the icon.
    This will force Windows to ask you for elevation of command prompt. Elevation is necessary for editing Boot Configuration Database (BCD), the database used by Windows boot manager to store boot settings.
    2. In the User Account Control window click Yes to confirm elevation of command shell.
    3. At the command prompt type
    bcdedit
    to list your BCD entries.
    This will give you an output like:
    Windows Boot Manager
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\bootmgfw.efi
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    integrityservices Enable
    default {current}
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    {a329b5cc-fb29-11e1-a74d-f2c962d62240}
    {a329b5ca-fb29-11e1-a74d-f2c962d62240}
    {a329b5c2-fb29-11e1-a74d-f2c962d62240}
    {current}
    {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    toolsdisplayorder {memdiag}
    timeout 30
    Windows Boot Loader
    identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8prowmc01.vhdx
    path \Windows\system32\winload.efi
    description Windows 8
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5d1-fb29-11e1-a74d-f2c962d62240}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8prowmc01.vhdx
    systemroot \Windows
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    The section that starts with Windows Boot Manager lists current settings for the boot menu. Here you find what boot entry is chosen by default, this is the one what you will boot into if you do not select any boot entry in the
    boot menu.
    The following record
    default {current}
    indicates that by default my Windows boots into configuration which I use at the moment (currently booted Windows configuration).
    To find out what exactly is current configuration, look into the list of boot entries, records that contain boot loader configuration and are titled as Windows Boot Loader in the bcdedit output.
    For example, the entry shown above is one of my boot configurations. This is one of the boot entries listed on the boot manager screen when I start my PC and it looks like:
    Windows Boot Loader
    identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8prowmc01.vhdx
    path \Windows\system32\winload.efi
    description Windows 8
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5d1-fb29-11e1-a74d-f2c962d62240}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8prowmc01.vhdx
    systemroot \Windows
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    This record has a unique GUID identifier that can be used to reference this boot entry, which is:
    identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    If we look at the Windows Boot Manager settings, we'll see this entry is the first in order to be displayed in the boot menu on OS start (I marked the unique bits):
    displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    {a329b5cc-fb29-11e1-a74d-f2c962d62240}
    It references my VHD drive, a virtual hard drive where my Windwos 8 setup is residing:
    device vhd=[D:]\win8prowmc01.vhdx
    And it also specifies that the boot manager must use UEFI BIOS extension code to access my Windows boot partition:
    path \EFI\Microsoft\Boot\bootmgfw.efi
    3. Now locate the current boot entry.
    Current boot entry contains boot settings used to boot into Windows configuration to which you are currently booted. It is referenced in the list of boot entries as a Windows Boot Loader record that has the {current} keyword inside and may
    look like:
    Windows Boot Loader
    identifier {current}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description Windows 8 Enterprise RTM
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    Because we are more than happy with current configuration and want to base our new boot configuration on these settings, we need to copy this boot entry ({current}) to a new boot entry.
    This is done by running the following command:
    C:\Windows\system32>bcdedit /copy {current} /d "No Driver Signature Check"
    Parameter /d here indicates that the following sequence of characters specifies the display name for the new boot entry that we are creating. The name inside the double quotes will be displayed in the boot menu when you boot your Windows.
    In other words, if you know restart your system, you'll see the new No Driver Signature Check in the boot menu.
    When copied, the entry is automatically given a new GUID identifier, so upon running the command above, you'll see the following line returned (you'll have an other GUID since these are unique identifiers):
    The entry was successfully copied to {a329b5d8-fb29-11e1-a74d-f2c962d62240}.
    4. Make sure the entry has been successfully created.
    Run the same bcdedit. (You may specify /enum or /v, or both /enum /v parameters at the prompt to get more detail about boot entries, but simple bcdedit is just enough to see the new entry):
    C:\Windows\system32>bcdedit
    Windows Boot Manager
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\bootmgfw.efi
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    integrityservices Enable
    default {current}
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    {a329b5cc-fb29-11e1-a74d-f2c962d62240}
    {a329b5ca-fb29-11e1-a74d-f2c962d62240}
    {a329b5c2-fb29-11e1-a74d-f2c962d62240}
    {current}
    {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    toolsdisplayorder {memdiag}
    timeout 30
    Windows Boot Loader
    identifier {current}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description Windows 8 Enterprise RTM
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    Windows Boot Loader
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description No Driver Signature Check
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    The entry has been created and given a unique a329b5d8-fb29-11e1-a74d-f2c962d62240 ID. It now has exactly same boot settings as the boot entry we used to boot into current configuration of Windows.
    5. Modify created  No Driver Signature Check entry and specify that Windows must have driver integrity checks disabled when booted using this boot entry.
    Any modifications to boot entries are made using /set parameter. To indicate that we modify a specific boot entry, we must specify the GUID for the No Driver Signature Check record, which is:
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    In other words, to edit (add or change) an option for the boot entry, we need to use the following command syntax:
    C:\Windows\system32>bcdedit /set GUID <boot_option> [<option_value>]
    First, we must specify that we don't want integrity checks be made. This is done by adding the loadoptions option and setting it to DISABLE_INTEGRITY_CHECKS value:
    C:\Windows\system32>bcdedit /set {a329b5d8-fb29-11e1-a74d-f2c962d62240} loadopti
    ons DISABLE_INTEGRITY_CHECKS
    The operation completed successfully.
    6. Verify that load option has been added.
    Run the bcdedit command:
    Windows Boot Loader
    identifier {current}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description Windows 8 Enterprise RTM
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    Windows Boot Loader
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description No Driver Signature Check
    locale en-US
    loadoptions DISABLE_INTEGRITY_CHECKS
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    7. Add the option that turns on test signing mode and disables checks of driver signature.
    Adding the testsigning option and setting it to ON does the trick for us:
    C:\Windows\system32>bcdedit /set {a329b5d8-fb29-11e1-a74d-f2c962d62240} TESTSIGNING ON
    8. Now we have a boot entry that enables Windows not to do integrity checks and digital signature validation.
    We check it by running bcdedit:
    Windows Boot Loader
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description No Driver Signature Check
    locale en-US
    loadoptions DISABLE_INTEGRITY_CHECKS
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    testsigning Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    9. Type 'exit' without quotes to exit from command prompt, and restart Windows.
    Upon booting you will be present with a new boot option to start Windows in configuration that allows you to install custom non-signed drivers.
    Hope this will help anybody to create their own custom boot configurations.
    Well this is the world we live in And these are the hands we're given...

    Hi,
    Thank you for sharing the solutions & experience here. It will be very beneficial for other community members who have similar questions. 
    Regards,
    Kelvin hsu
    TechNet Community Support

Maybe you are looking for