Unable to start Windows 7 after recovering from an image

Dear community!
In our office, we frequently use Windows 7 on our Mac computers. Windows 7 is installed on a Bootcamp partition.
The HDD of one of our MacBooks crashed today and I recovered data from a previously made full image of that MacBook to another MacBook.
When pressing the ALT button during start up, the MacBook only displays the Mac partition, which can be started perfectly, but not the Windows 7 Bootcamp partition. Under System Preferences -> "Startup Volume" I can see and select the Winodws 7 Bootcamp partition, but it won't let me start Windows 7 from it after rebooting. I get the message "NO BOOTABLE DEVICE - INSERT BOOT DISC AND PRESS ANY KEY". Also, I'm able to access the Bootcamp partition (and all files under Windows) when I start up Mac.
Any ideas on how to fix that? Sry I can't provide you with diskutil list, gpt and fdisk right now because I don't have the MacBook with me. I will do that later!).

I was stuck with a similar situation...
http://discussions.apple.com/message.jspa?messageID=13329327#13329327

Similar Messages

  • Unable to start OSX after reload from restore disks

    Hi,
    I was having a bunch of crashing issues with my eMac. After trying to repair permisssions and the file system and applying the most recent updates, decided to restore.
    After reformating the drive and installing OSx from the restore disks, the system hangs at some point of the initial install dialogues. Of the few times that i've tried its usually when trying to create the initial user account or pull the info from the .Mac profile. I've tried both creating it manually and having it query .Mac for the profile. I also tried both formating the drive manually and letting the install program do it.
    Any thoughts on the source of the issue and next steps I might consider?
    Thx,
    CMV

    After further research, looks to be a capacitor issue on that vintage of eMAC, thx.

  • Unable to start clusterware after upgrading from 10.2.0.4 to 11.1.0.6

    We are running on Solaris 10 and
    After upgrading my clusterware home to 11.1.0.6 and running $CRS_HOME/install/rootupgrade I get the following errors:
    ld.so.1: cemutlo.bin: fatal: libclntsh.so.11.1: open failed: No such file or directory
    The /oracle/product/10g/crs/bin/cemutlo command failed with exit code: 137
    Looks like the libclntsh.so.11.1 was not generated. Checked $CRS_HOME/lib/clntsh.fileslist and see the following error :
    Undefined first referenced
    symbol in file
    nnfoboot /oracle/product/10g/crs/lib/libn11.a(nnfgt.o
    ld: fatal: Symbol referencing errors. No output written to /oracle/product/10g/c
    rs/lib/libclntsh.so.11.1
    ld is faling. Anyone run into an issue like this before? Any suggestions on how to troubleshoot/debug an issue like this?
    Thanks in advance for any help.

    ldd bin/cemutlo.bin
    ls -l $ORACLE_HOME/lib/libclntsh*
    ls -l $ORACLE_HOME/lib32/libclntsh*
    do it like Toni Lazarin told you ;) metalink 443696.1
    it's about genclntsh script ... change -Dfiles to -Bsymbolic in LD command line
    comment the line :
    #LD="ld -m -Dfiles -i -G -z text -L${ORACLE_HOME}/${LIB}" # shared library link command
    and add the following line :
    LD="ld -m -Bsymbolic -i -G -z text -L${ORACLE_HOME}/${LIB}" # new shared library link command
    and Run "relink all"and run rootupgrade
    Another IDEA:
    Apply Solaris SPARC 10 kernel patch 120011-14 or latest kernel patch for Solaris 10 SPARC
    to update ld version
    SUNWtoo package provides ld utility .
    NOTE: Please reboot server after installing kernel patch 120011-14 or latest kernel patch for Solaris 10 SPARC
    and then "relink all" again ... and run rootupgrade
    Good Luck

  • Unable to install iTunes after converting from Windows Vista to Windows 7.  Am told installation was successful, then "iTunes was not installed correctly", followed by "Error 7 (Windows error 193).

    Unable to install iTunes after converting from Windows Vista to Windows 7.  Am told installation was successful, then "iTunes was not installed correctly", followed by "Error 7 (Windows error 193).  I have my iPod plugged into my computer via USB port.  What am I doing wrong?

    i have the only account on my laptop so have checked and am the account administrator
    i run windows 7 home premium
    I have the same problem and
    have followed the link uninstalling in the correct order,
    then restarted as per instructions,
    went to Apple to download itunes,
    hit download now,
    Visit the iTunes download page. Click Download Now to download the iTunes installer. When prompted, click Save (instead of Run).
    did not get a save instead of run prompt
    Right click on iTunesSetup or iTunes64Setup (the installer you downloaded in step 3).
    If you have Windows Vista, Windows 7, and Windows 8: Choose "Run as administrator."
    i can only click run as administrator from right clicking the shortcut on my desktop screen
    If iTunes fails to install or repair, it might be necessary to remove components left from a previous installation of iTunes and then reinstall.
    sick of doing this
    at least 7 or 8 times i have re installed itunes to no avail
    troubleshooting no better
    please help. pulling my hair out at this stage
    it was working fine until 2 days ago when i opened itunes it offered to update to 12.1
    not working since i clicked yes
    also i have gone to restore previous point and ffs there are no restore points before my multiple reinstalls
    really dont want to have to restore factory settings

  • Image creation with MDT task sequence- "Windows has recovered from an unexpected shutdown"

    I'm using MDT 2012 U1 to build and capture a Windows 7 x86 image for deployment with ConfigMgr 2012 SP1.  I'm using the standard client task sequence in MDT.
    The MDT task sequence consistently fails after the reboot in the "Postinstall" group.  The install OS, Copy Scripts, Configure, Inject Drivers, Next Phase, and Restart Computer tasks all execute successfully, then the MDT-initiated reboot
    completes successfully.  There is nothing else helpful in the SMSTS.LOG, these are the last entries in the log:
    Successfully complete the action (Restart Computer) with the exit win32 code 0
    Sending status message
    Executing in non SMS standalone mode.  Ignoring send a task execution status message request
    Set a global environment variable _SMSTSLastActionRetCode=0
    Set a global environment variable _SMSTSLastActionSucceeded=true
    Expand a string %_SMSTSMDataPath%\Logs
    Deleting file without retrying
    The error message on the reference computer says, "Windows has recovered from an unexpected shutdown" along with "An existing in-progress deployment was found but is not in an expected state.  Would you like to ignore this in-progress
    deployment and start a new one?"
    I have found one post that suggested modifying customsettings.ini with  HideShell=Yes, which I tried.  It didn't help.
    I am not sure why MDT thinks the reboot was unexpected?  Has anybody run into this?  What steps can I take to narrow down the problem?
    Any help/suggestions are appreciated.
    Thanks,
    FP

    Thanks for your reply Phil.
    Setuperr.log is empty, zero bytes.  Setupact.log looks good to me, it has these entries at the end:
    OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_UNDEPLOYABLE] --> [Image_State_Complete]
    OOBELdr.exe exiting with code [0x0]...
    Process exited with exit code [0x0]
    c:\windows\panther\SetupInfo succeeded.
    c:\windows\panther\setupinfo.
    Windeploy.exe exiting with code [0x0]
    SetupSQM Started
    Panther path is C:\windows\Panther
    SQM not opted in
    SetupSQM is finished
    Our image environment was created during an MCS Engagement, so we have the solution pack and there are many variables in customsettings.ini.  I will need to find out how to narrow this down but I'm not finding a log file that tells me where it's choking... 
    Any suggestions are appreciated.
    Thanks,
    FP

  • Windows has recovered from a serious error

    Hi all, I've been reading a lot about overclocking and I finally started today. I have set my FSB to 233, and I have been trying to find the lowest voltage I can run it at. 1.6 works fine but I tried going lower. This resulted in a spontaneous reboot. After windows booted back up when I increased the voltage, the windows error reporting dialog came up and said "windows has recovered from a serious error..." So I send the report... and internet explorer opens with a little info. It says the crash was due to a problem with a driver but does not mention a specific driver. does this osund familiar to anyone? are there any drivers i should investigate or replace? thanks a lot for your help!

    often with overclocking you will see 'file not found' BSODs on startup. It is reasonable to assume that our overclock may have upset a driver, driver component or driver associated file.
    Don't sweat it, as long as your not on that vCore now there should be no damage done to Windows.
    Have to admit I've had "Windows has...serious error" before following a vCore increasment on an AMD board.

  • I can't start windows 7 normally from Boot Camp

    I can't start windows 7 normally from Boot Camp.
    It was running fine since I have installed it 7 months ago, but now it can't start or (restart) normally (safe mode is ok). It displays a black screen after showing the logo, and I have to shut down the machine. My Mac system is working fine. Mac technician (Genius Bar) has run a surface scan to verify hd integrity and proofed ok, but could not give any advice on Windows issues.
    Please advice if anything I should do before cleaning up my partition and reinstall Windows.

    I would guess and sorry for asking but you already tried booting from Windows 7 DVD and doing auto repair?
    There are dozens of things to look at and do, and begin with chkdsk in Windows, yes but that only looks at one aspect. You can't really check for bad sectors on a drive's sectors. The best? to use the drive vendor's own utility actually, often with a linux boot CD or Windows program (they don't make Mac OS versions, one reason I first installed Vista over 5 yrs ago)
    Restore check points
    Uninstall last update or driver
    Clean the system of debris temp files, caches, registry errors, fonts and left overs
    make sure you have 20% and 12GB free space or more
    A hard shutdown can create more problems.

  • HP m8430f stuck on "Starting Windows" after April 10, 2012 Microsoft Updates

    HP m8430f stuck on "Starting Windows" after April 10, 2012 Microsoft Updates.  Upgraded to Windows 7 X64 from Vista X64 almost two years ago.  Have never had any problems until morning of April 12th.  I will cut to the final resolution to help anyone else who is going through this or will in the future.  After trying to repair Win7, restoring back to factory recovery (got code purple), installing clean Vista 64 and trying upgrade to Windows 7 again, formatting drive using /p:2 option of writing 0's twice to whole drive and then doing a clean install of Win7 only to get to the same place of being stuck at "Starting Windows", I tried a trick I had read about.  Boot to safe mode, you will get an error that you can complete install from safe mode. Don't close window but hit Shift-F10 and a cmd prompt will open.  Type in compmgmtlauncher and choose Device Manager.  Disable the Visx PureTV-U 48B0 under Sound, Video and Game controllers.  Reboot computer and Win7 complete installation.  Since I was able to get into Safe mode back on April 12th, I should have tried disabling everything then, but since it was working without problems before the updates, I couldn't believe that it was any of the devices.  I have not been able to get around this issue with the tv-tuner, but I don't have a need for it right now for it.  I saw a tip to try moving it to another pci slot and I will try that if I ever have a need to open the computer.  Just wanted to document what to do to save others weeks of searching.  If this is a driver issue, I can't believe HP or Windows hasn't come up with a more current driver.  During all of the installs, I never get a yellow triangle for that device or any indication in Event log or anywhere that there was a problem with this device.

    I had a similar issue with mine not working properly running Windows 7 Ultimate.   Mine was working just fine for quite some time and then I moved my system into our TV room and hooked it up to the television, and used it there.   Everything worked fine, I then returned it to the normal location but did not plug the IR sensor back in.
    I had issues with it, I then plugged it back in and it seemed to be working fine, then started to freeze while we were working on it, it would do this all the time.  I was thinking I had virus, I tried restoring windows to a previous working state.  Upgrading my Virus software and everything.   This was all back in October 2011.  I finally just thought my system was going out after a number of years. 
    Then the other day for some reason I moved the IR sensor from one plug to the other.  It is currently plugged into the bottom right USB port next to the RJ45 port.   It seems to be working just fine now and I don't have the device you suggested disabled, though I will keep that in mind.
    Thanks for you post, Hope mine helps too.

  • Stuck at "Starting Windows" after Deployment

    Hello. I recently updated my MDT to 2013 as well as added the Windows assessment and deployment kit for Windows 8.1. Since then, I have one particular .wim image that I can't seem to deploy using MDT. It continuously gets stuck at "Starting Windows"
    after it's first reboot from the deployment window. I have enabled logging and see this error appear quite often, but I'm not sure if that helps. I can provide the logs if needed.
    Any help would be greatly appreciated!!
    <![LOG[Error executing web service http://(SERVERNAME):9800/MDTMonitorEvent/PostEvent?uniqueID=&computerName=LENOVOT530&messageID=41017&severity=1&stepName=&currentStep=0&totalSteps=0&id=B1CAF581-522F-11CB-863C-9D12A921BFEC,3C:97:0E:7F:F3:3C&message=LTI initiating task sequence-requested reboot.&dartIP=&dartPort=&dartTicket=&vmHost=&vmName=: The operation timed out"

    Turns out it was something in the BIOS causing the issue. This linked helped me out.
    http://social.technet.microsoft.com/Forums/windows/en-US/c0b9719c-657d-4366-b922-409561bb16c6/window-7-hang-up-at-starting-windows-screen-while-installing-with-uefi-mode?forum=w7itproinstall

  • Blue screen error "windows has recovered from a unexpected shutdown"

    Hi guys
    I am using laptop & everyday it will unexpectedly shutdown and shows Blue screen error "windows has recovered from a unexpected shutdown"...Pls help me to resolve this issue.
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7600.2.0.0.256.48
      Locale ID: 1033
    Additional information about the problem:
      BCCode: d1
      BCP1: 00000030
      BCP2: 00000002
      BCP3: 00000000
      BCP4: 8F2DA8A5
      OS Version: 6_1_7600
      Service Pack: 0_0
      Product: 256_1
    Files that help describe the problem:
      C:\Windows\Minidump\062614-23836-01.dmp
      C:\Users\Venkateshwara swamy\AppData\Local\Temp\WER-74552-0.sysdata.xml
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

    It could be some driver compatibility issues.
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff560244(v=vs.85).aspx
     http://blogs.technet.com/b/askcore/archive/2008/11/01/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners.aspx
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • Unable to start the weblogic server from windows environment

    Hi All,
    In our training system we have installed the SOA 11g and it worked fine till today afternoon. We have logged off the admin user in windows account and logged with our login credentials into windows after that we are unable to start the weblogic server.
    - Earlier in the DOS command prompt we used to navigate to the path where the startWeblogic.cmd file located and then we execute the command, after that we will able to see the status message as RUNNING MODE in the bottom of the screen, and when ever we deploy an project using Jdeveloper in the weblogic server window some messages will appended based on the action.
    - Only when we issue the command to shut down the weblogic server at that time only the command will be back to the path from where we started the server.
    - After login to windows with our account, when we tried to start the weblogic server, it didn't throw any error instead of that after running few lines in the command window the prompt was back in to the (D:\Middleware\.....\Domains\bin)path from where we ran the command to start the server.
    Please help us to resolve the issue asap.
    Thanks in advance.
    Regards,
    Sathyaseelan

    Hi,
    Make sure that the user which you are using to start weblogic server should be part of Administrator group or the group to which your admin user belongs to.
    Regards,
    Kishore

  • Unable to start Oracle Process Manager from the windows services for OBIEE

    Hi,
    I have OBIEE 11g installed on a 32-bit windows machine. Of the two windows services installed, I am unable to start the Oracle Process Manager. When I try to start it I get the following error:
    Error 1053: The service did not respond to the start or control request  in a timely fashion.
    At the back end, this service is calling the file opmn.exe which is placed at MIDDLEWAREHOME\Oracle_BI1\opmn\bin. On trying to execute this file the error we get is:
    The procedure entry point longjmp could not be located in the dynamic link library orauts.dll
    I have tried replacing the orauts.dll file, but to no avail.
    Please let me know if you have any clue regarding what is to be done.
    Thanks
    Naman

    Hi Naman,
    This error occurs for the following reasons,
    *Path variable is not set properly
    *Multiple Oracle homes exists in the same machine.
    Follow the below steps and let me know if it works,
    1. Select My Computer -> Right Click -> Properties
    2. In the System Properties screen go to Advanced Tab
    3. Click on Environment Variables
    4. In the System Variables section select PATH variable & Click edit
    5. Now you will find that it will contain invalid directories. Remove the incorrect entries. This may happen when you have multiple oracle homes in the same machine
    6. Restart the service.
    Rgds,
    Dpka

  • Unable to start Workshop after upgrading JRockit from R5 to R28

    I have Workshop 10.3 installed together with the bundled JRockit 1.6.0 R5. Recently, I upgraded the JRockit version to 1.6.0 R28 and have been unable to start Workshop.
    Here is the error I get after trying to run workshop.exe:
    JVM terminated. Exit code=13
    D:/Program Files/Java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1/jre/bin/javaw.exe
    -Xms384m
    -Xmx768m
    -XX:MaxPermSize=256m
    -XX:PermSize=192m
    -XX:NewRation=3
    -Xss256k
    -DprodMode=production
    -Dweblogic.deployer.debug=all
    -Dweblogic.debug.DebugConnection=true
    -Dweblogic.debug.DebugMessaging=true
    -Dweblogic.debug.DebugDeployment=true
    -Dweblogic.home=D:/Oracle/Middleware/wlserver_10.3
    -Dsun.lang.ClassLoader.allowArraySyntax=true
    -Dnitrox.boot.jar=file:D:/Oracle/Middleware/wlserver_10.3/nitrox-boot.jar
    -Dosgi.install.area=D:/Oracle/Middleware/tools/eclipse_pkgs/2.0/eclipse_3.3.2/eclipse
    -Dosgi.instance.area.default=E:/BeaApps/MgmtPortal/workspaces/default
    -Dosgi.configuration.area=D:/Oracle/Middleware/workshop_10.3/workshop4WP/eclipse/configuration
    -Declipse.product=com.bea.workshop.product.workshop
    -Dosgi.splashPath=file:D:/Oracle/Middleware/workshop_10.3/workshop4WP/eclipse/plugins/com.bea.workshop.product
    -jar D:/Oracle/Middleware/tools/eclipse_pkgs/2.0/eclipse_3.3.2/eclipse/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20080118awtswtbridge.jar
    -os win32
    -ws win32
    -arch x86
    -showsplash
    -launcher D:\Oracle\Middleware\workshop_10.3\workshop.exe
    -name Workshop
    --launcher.library D:/Oracle/Middleware/tools/eclipse_pkgs/2.0/eclipse_3.3.2/eclipse/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20080118\eclipse_1023.dll
    -startup D:/Oracle/Middleware/tools/eclipse_pkgs/2.0/eclipse_3.3.2/eclipse/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20080118awtswtbridge.jar
    -exitdata 143c_70
    -vm D:/Program Files/Java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1/jre/bin/javaw.exe
    -Xms384m
    -Xmx768m
    -XX:MaxPermSize=256m
    -XX:PermSize=192m
    -XX:NewRation=3
    -Xss256k
    -DprodMode=production
    -Dweblogic.home=D:/Oracle/Middleware/wlserver_10.3
    -Dsun.lang.ClassLoader.allowArraySyntax=true
    -Dnitrox.boot.jar=file:D:/Oracle/Middleware/wlserver_10.3/nitrox-boot.jar
    -Dosgi.install.area=D:/Oracle/Middleware/tools/eclipse_pkgs/2.0/eclipse_3.3.2/eclipse
    -Dosgi.instance.area.default=E:/BeaApps/MgmtPortal/workspaces/default
    -Dosgi.configuration.area=D:/Oracle/Middleware/workshop_10.3/workshop4WP/eclipse/configuration
    -Declipse.product=com.bea.workshop.product.workshop
    -Dosgi.splashPath=file:D:/Oracle/Middleware/workshop_10.3/workshop4WP/eclipse/plugins/com.bea.workshop.product
    -jar D:/Oracle/Middleware/tools/eclipse_pkgs/2.0/eclipse_3.3.2/eclipse/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20080118awtswtbridge.jar
    I've tried changing the vm to java.exe and to the jrockit-jre folder, but both give similar errors.

    Hi,
    Check the following link for more reasons.
    http://www.ehow.com/how_4784069_terminated-exit-code-error-eclipse.html
    It seems that current version is not matching and mostly not supported to the current version of workshop.
    Regards,
    Kal.

  • Unable to start xorg after latest nvidia update

    Hi,
    I have NVIDIA GeForce GTX 750 card. I did update to version 346.47 of nvidia driver and figured out that after reboot SDDM dont start. I disabled login manager and tried to start xorg server manually but without success. I see that there is segmentation fault in log but don't understand where it comes from exectly.
    Output of /var/log/Xorg.0.log:
    [ 18.250]
    X.Org X Server 1.17.1
    Release Date: 2015-02-10
    [ 18.251] X Protocol Version 11, Revision 0
    [ 18.251] Build Operating System: Linux 3.18.6-1-ARCH x86_64
    [ 18.251] Current Operating System: Linux lolik-pc 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64
    [ 18.251] Kernel command line: \boot\vmlinuz-linux rw root=UUID=d0592c05-2ed2-4bd2-be47-6a2762e5c3c3 rootfstype=ext4 initrd=boot\initramfs-linux.img
    [ 18.252] Build Date: 22 February 2015 12:50:32PM
    [ 18.253]
    [ 18.253] Current version of pixman: 0.32.6
    [ 18.254] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 18.254] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 18.255] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 28 13:33:14 2015
    [ 18.260] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 18.261] (==) No Layout section. Using the first Screen section.
    [ 18.261] (==) No screen section available. Using defaults.
    [ 18.261] (**) |-->Screen "Default Screen Section" (0)
    [ 18.261] (**) | |-->Monitor "<default monitor>"
    [ 18.261] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 18.261] (==) Automatically adding devices
    [ 18.261] (==) Automatically enabling devices
    [ 18.261] (==) Automatically adding GPU devices
    [ 18.267] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
    [ 18.267] Entry deleted from font path.
    [ 18.267] (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
    [ 18.271] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 18.271] Entry deleted from font path.
    [ 18.271] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 18.272] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 18.272] Entry deleted from font path.
    [ 18.272] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 18.272] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 18.272] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 18.272] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 18.272] (II) Loader magic: 0x815d80
    [ 18.272] (II) Module ABI versions:
    [ 18.272] X.Org ANSI C Emulation: 0.4
    [ 18.272] X.Org Video Driver: 19.0
    [ 18.272] X.Org XInput driver : 21.0
    [ 18.272] X.Org Server Extension : 9.0
    [ 18.273] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
    [ 18.273] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 18.273] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
    [ 18.273] (II) xfree86: Adding drm device (/dev/dri/card1)
    [ 18.273] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 9 paused 0
    [ 18.274] (--) PCI: (0:0:2:0) 8086:0412:1458:d000 rev 6, Mem @ 0xf7400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
    [ 18.274] (--) PCI:*(0:1:0:0) 10de:1380:1462:3102 rev 162, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
    [ 18.274] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 18.274] (II) LoadModule: "glx"
    [ 18.275] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 18.342] (II) Module glx: vendor="NVIDIA Corporation"
    [ 18.342] compiled for 4.0.2, module version = 1.0.0
    [ 18.342] Module class: X.Org Server Extension
    [ 18.343] (II) NVIDIA GLX Module 346.47 Thu Feb 19 18:09:07 PST 2015
    [ 18.343] (II) Applying OutputClass "nvidia" to /dev/dri/card0
    [ 18.343] loading driver: nvidia
    [ 18.343] (==) Matched nvidia as autoconfigured driver 0
    [ 18.343] (==) Matched nouveau as autoconfigured driver 1
    [ 18.343] (==) Matched nv as autoconfigured driver 2
    [ 18.343] (==) Matched intel as autoconfigured driver 3
    [ 18.343] (==) Matched nouveau as autoconfigured driver 4
    [ 18.343] (==) Matched nv as autoconfigured driver 5
    [ 18.343] (==) Matched modesetting as autoconfigured driver 6
    [ 18.343] (==) Matched fbdev as autoconfigured driver 7
    [ 18.343] (==) Matched vesa as autoconfigured driver 8
    [ 18.343] (==) Assigned the driver to the xf86ConfigLayout
    [ 18.343] (II) LoadModule: "nvidia"
    [ 18.344] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 18.349] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 18.349] compiled for 4.0.2, module version = 1.0.0
    [ 18.349] Module class: X.Org Video Driver
    [ 18.350] (II) LoadModule: "nouveau"
    [ 18.350] (WW) Warning, couldn't open module nouveau
    [ 18.350] (II) UnloadModule: "nouveau"
    [ 18.350] (II) Unloading nouveau
    [ 18.350] (EE) Failed to load module "nouveau" (module does not exist, 0)
    [ 18.350] (II) LoadModule: "nv"
    [ 18.350] (WW) Warning, couldn't open module nv
    [ 18.350] (II) UnloadModule: "nv"
    [ 18.350] (II) Unloading nv
    [ 18.350] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 18.350] (II) LoadModule: "intel"
    [ 18.350] (WW) Warning, couldn't open module intel
    [ 18.350] (II) UnloadModule: "intel"
    [ 18.350] (II) Unloading intel
    [ 18.350] (EE) Failed to load module "intel" (module does not exist, 0)
    [ 18.350] (II) LoadModule: "modesetting"
    [ 18.350] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
    [ 18.350] (II) Module modesetting: vendor="X.Org Foundation"
    [ 18.350] compiled for 1.17.1, module version = 1.17.1
    [ 18.350] Module class: X.Org Video Driver
    [ 18.350] ABI class: X.Org Video Driver, version 19.0
    [ 18.350] (II) LoadModule: "fbdev"
    [ 18.350] (WW) Warning, couldn't open module fbdev
    [ 18.350] (II) UnloadModule: "fbdev"
    [ 18.350] (II) Unloading fbdev
    [ 18.350] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 18.350] (II) LoadModule: "vesa"
    [ 18.350] (WW) Warning, couldn't open module vesa
    [ 18.350] (II) UnloadModule: "vesa"
    [ 18.350] (II) Unloading vesa
    [ 18.350] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 18.350] (II) NVIDIA dlloader X Driver 346.47 Thu Feb 19 17:47:18 PST 2015
    [ 18.350] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 18.351] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
    [ 18.351] (++) using VT number 1
    [ 18.351] (--) controlling tty is VT number 1, auto-enabling KeepTty
    [ 18.351] (II) Loading sub module "fb"
    [ 18.351] (II) LoadModule: "fb"
    [ 18.351] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 18.352] (II) Module fb: vendor="X.Org Foundation"
    [ 18.352] compiled for 1.17.1, module version = 1.0.0
    [ 18.352] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 18.352] (II) Loading sub module "wfb"
    [ 18.352] (II) LoadModule: "wfb"
    [ 18.352] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 18.353] (II) Module wfb: vendor="X.Org Foundation"
    [ 18.353] compiled for 1.17.1, module version = 1.0.0
    [ 18.353] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 18.353] (II) Loading sub module "ramdac"
    [ 18.353] (II) LoadModule: "ramdac"
    [ 18.353] (II) Module "ramdac" already built-in
    [ 18.354] (II) modeset(G0): using drv /dev/dri/card1
    [ 18.354] (WW) Falling back to old probe method for modesetting
    [ 18.354] (II) NVIDIA(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 18.354] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
    [ 18.354] (==) NVIDIA(0): RGB weight 888
    [ 18.354] (==) NVIDIA(0): Default visual is TrueColor
    [ 18.354] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 18.354] (**) NVIDIA(0): Enabling 2D acceleration
    [ 18.948] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
    [ 18.948] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 750 Ti (GM107-A) at PCI:1:0:0 (GPU-0)
    [ 18.948] (--) NVIDIA(0): Memory: 2097152 kBytes
    [ 18.948] (--) NVIDIA(0): VideoBIOS: 82.07.32.00.18
    [ 18.948] (II) NVIDIA(0): Detected PCI Express Link width: 16X
    [ 18.952] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 750 Ti at PCI:1:0:0
    [ 18.952] (--) NVIDIA(0): CRT-0
    [ 18.952] (--) NVIDIA(0): DELL U2211H (DFP-0) (boot, connected)
    [ 18.952] (--) NVIDIA(0): DFP-1
    [ 18.952] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
    [ 18.952] (--) NVIDIA(0): DELL U2211H (DFP-0): Internal TMDS
    [ 18.952] (--) NVIDIA(GPU-0): DELL U2211H (DFP-0): 330.0 MHz maximum pixel clock
    [ 18.952] (--) NVIDIA(0): DFP-1: Internal TMDS
    [ 18.952] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
    [ 18.952] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 18.952] (**) NVIDIA(0): device DELL U2211H (DFP-0) (Using EDID frequencies has
    [ 18.952] (**) NVIDIA(0): been enabled on all display devices.)
    [ 18.953] (==) NVIDIA(0):
    [ 18.953] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
    [ 18.953] (==) NVIDIA(0): will be used as the requested mode.
    [ 18.953] (==) NVIDIA(0):
    [ 18.953] (II) NVIDIA(0): Validated MetaModes:
    [ 18.953] (II) NVIDIA(0): "DFP-0:nvidia-auto-select"
    [ 18.953] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
    [ 18.983] (--) NVIDIA(0): DPI set to (101, 101); computed from "UseEdidDpi" X config
    [ 18.983] (--) NVIDIA(0): option
    [ 18.983] (==) modeset(G0): Depth 24, (==) framebuffer bpp 32
    [ 18.983] (==) modeset(G0): RGB weight 888
    [ 18.983] (==) modeset(G0): Default visual is TrueColor
    [ 18.983] (II) Loading sub module "glamoregl"
    [ 18.983] (II) LoadModule: "glamoregl"
    [ 18.983] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
    [ 18.995] (II) Module glamoregl: vendor="X.Org Foundation"
    [ 18.995] compiled for 1.17.1, module version = 1.0.0
    [ 18.995] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 18.995] (II) glamor: OpenGL accelerated X.org driver based.
    [ 19.024] (EE)
    [ 19.024] (EE) Backtrace:
    [ 19.025] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x119) [0x5949c9]
    [ 19.026] (EE) 1: /usr/lib/libc.so.6 (__restore_rt+0x0) [0x7fc93cef353f]
    [ 19.028] (EE) 2: /usr/lib/libX11.so.6 (_XSend+0x2b) [0x7fc932e6a0bb]
    [ 19.028] (EE) 3: /usr/lib/libX11.so.6 (_XFlush+0x15) [0x7fc932e6a575]
    [ 19.028] (EE) 4: /usr/lib/libX11.so.6 (_XGetRequest+0x65) [0x7fc932e6d055]
    [ 19.028] (EE) 5: /usr/lib/libX11.so.6 (XQueryExtension+0x4d) [0x7fc932e605ed]
    [ 19.028] (EE) 6: /usr/lib/libX11.so.6 (XInitExtension+0x32) [0x7fc932e54392]
    [ 19.028] (EE) 7: /usr/lib/libXext.so.6 (XextAddDisplay+0x4f) [0x7fc932c2338f]
    [ 19.028] (EE) 8: /usr/lib/libnvidia-glsi.so.346.47 (_nv016glsi+0x5f3f7) [0x7fc93322c3d7]
    [ 19.028] (EE) 9: /usr/lib/libnvidia-glsi.so.346.47 (_nv016glsi+0x804) [0x7fc93316ebf4]
    [ 19.028] (EE) unw_get_proc_name failed: no unwind info found [-10]
    [ 19.028] (EE) 10: /usr/lib/libEGL.so.1 (?+0x804) [0x7fc933417ef4]
    [ 19.028] (EE) unw_get_proc_name failed: no unwind info found [-10]
    [ 19.028] (EE) 11: /usr/lib/libEGL.so.1 (?+0x804) [0x7fc933418924]
    [ 19.028] (EE) 12: /usr/lib/libEGL.so.1 (NvEglRegClientApi+0x4f36) [0x7fc933425866]
    [ 19.028] (EE) 13: /usr/lib/xorg/modules/libglamoregl.so (glamor_egl_init+0x99) [0x7fc935930539]
    [ 19.029] (EE) 14: /usr/lib/xorg/modules/drivers/modesetting_drv.so (_init+0x29ce) [0x7fc935fc7e9e]
    [ 19.029] (EE) 15: /usr/lib/xorg-server/Xorg (InitOutput+0xbcc) [0x47b63c]
    [ 19.029] (EE) 16: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x22a) [0x43c9da]
    [ 19.029] (EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7fc93cee0800]
    [ 19.029] (EE) 18: /usr/lib/xorg-server/Xorg (_start+0x29) [0x427039]
    [ 19.029] (EE) 19: ? (?+0x29) [0x29]
    [ 19.029] (EE)
    [ 19.029] (EE) Segmentation fault at address 0x0
    [ 19.029] (EE)
    Fatal server error:
    [ 19.029] (EE) Caught signal 11 (Segmentation fault). Server aborting
    [ 19.029] (EE)
    [ 19.029] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 19.029] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 19.029] (EE)
    [ 19.031] (EE) Server terminated with error (1). Closing log file.
    Output of command "lspci -k | grep -A 2 -i "VGA""
    00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
    Subsystem: Gigabyte Technology Co., Ltd Device d000
    Kernel driver in use: i915
    01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2)
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device 3102
    Kernel driver in use: nvidia
    Output of command "modinfo nvidia"
    filename: /lib/modules/3.18.6-1-ARCH/extramodules/nvidia.ko.gz
    alias: char-major-195-*
    version: 346.47
    supported: external
    license: NVIDIA
    alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00*
    alias: pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00*
    alias: pci:v000010DEd*sv*sd*bc03sc02i00*
    alias: pci:v000010DEd*sv*sd*bc03sc00i00*
    depends: drm,i2c-core
    vermagic: 3.18.6-1-ARCH SMP preempt mod_unload modversions
    parm: NVreg_Mobile:int
    parm: NVreg_ResmanDebugLevel:int
    parm: NVreg_RmLogonRC:int
    parm: NVreg_ModifyDeviceFiles:int
    parm: NVreg_DeviceFileUID:int
    parm: NVreg_DeviceFileGID:int
    parm: NVreg_DeviceFileMode:int
    parm: NVreg_RemapLimit:int
    parm: NVreg_UpdateMemoryTypes:int
    parm: NVreg_InitializeSystemMemoryAllocations:int
    parm: NVreg_UsePageAttributeTable:int
    parm: NVreg_MapRegistersEarly:int
    parm: NVreg_RegisterForACPIEvents:int
    parm: NVreg_CheckPCIConfigSpace:int
    parm: NVreg_EnablePCIeGen3:int
    parm: NVreg_EnableMSI:int
    parm: NVreg_MemoryPoolSize:int
    parm: NVreg_RegistryDwords:charp
    parm: NVreg_RmMsg:charp
    parm: NVreg_AssignGpus:charp
    In addition, in order to disable sddm I downloaded latest Arch linux installation CD (2015.02.01) but I was unable to start PC with this version. Loading stuck after first 3 lines, after "triggering udevevents".
    I had old version 2014.08 and it worked ok.
    Thanks,
    Alexey

    I just wanted to echo eugeneyche's comment. I ran the same steps mentioned by ElectricPrism but that didn't really fix them. I had to add nomodeset to my kernel parameters. I now want to know what's really going on. For the record, this was my backtrace:
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (**) NVIDIA(0): device Ancor Communications Inc ASUS VE278 (DFP-1) (Using
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (**) NVIDIA(0): EDID frequencies has been enabled on all display
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (**) NVIDIA(0): devices.)
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (==) NVIDIA(0):
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (==) NVIDIA(0): will be used as the requested mode.
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (==) NVIDIA(0):
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (II) NVIDIA(0): Validated MetaModes:
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (II) NVIDIA(0): Virtual screen size determined to be 3600 x 1080
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (--) NVIDIA(0): DPI set to (90, 88); computed from "UseEdidDpi" X config
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (--) NVIDIA(0): option
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (==) modeset(G0): Depth 24, (==) framebuffer bpp 32
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (==) modeset(G0): RGB weight 888
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (==) modeset(G0): Default visual is TrueColor
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (II) Loading sub module "glamoregl"
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (II) LoadModule: "glamoregl"
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (II) Module glamoregl: vendor="X.Org Foundation"
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: compiled for 1.17.1, module version = 1.0.0
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: ABI class: X.Org ANSI C Emulation, version 0.4
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (II) glamor: OpenGL accelerated X.org driver based.
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE)
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) Backtrace:
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x119) [0x5949c9]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 1: /usr/lib/libc.so.6 (__restore_rt+0x0) [0x7fad6053a53f]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 2: /usr/lib/libxcb.so.1 (xcb_writev+0x0) [0x7fad56046100]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 3: /usr/lib/libX11.so.6 (_XSend+0x19e) [0x7fad564b122e]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 4: /usr/lib/libX11.so.6 (_XFlush+0x15) [0x7fad564b1575]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 5: /usr/lib/libX11.so.6 (_XGetRequest+0x65) [0x7fad564b4055]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 6: /usr/lib/libX11.so.6 (XQueryExtension+0x4d) [0x7fad564a75ed]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 7: /usr/lib/libX11.so.6 (XInitExtension+0x32) [0x7fad5649b392]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 8: /usr/lib/libXext.so.6 (XextAddDisplay+0x4f) [0x7fad5626a38f]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 9: /usr/lib/libnvidia-glsi.so.346.47 (_nv016glsi+0x5f3f7) [0x7fad568733d7]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 10: /usr/lib/libnvidia-glsi.so.346.47 (_nv016glsi+0x804) [0x7fad567b5bf4]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) unw_get_proc_name failed: no unwind info found [-10]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 11: /usr/lib/libEGL.so.1 (?+0x804) [0x7fad56a5eef4]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) unw_get_proc_name failed: no unwind info found [-10]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 12: /usr/lib/libEGL.so.1 (?+0x804) [0x7fad56a5f924]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 13: /usr/lib/libEGL.so.1 (NvEglRegClientApi+0x4f36) [0x7fad56a6c866]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 14: /usr/lib/xorg/modules/libglamoregl.so (glamor_egl_init+0x99) [0x7fad58f77539]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 15: /usr/lib/xorg/modules/drivers/modesetting_drv.so (_init+0x29ce) [0x7fad5960ee9e]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 16: /usr/lib/xorg-server/Xorg (InitOutput+0xbcc) [0x47b63c]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 17: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x22a) [0x43c9da]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 18: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7fad60527800]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 19: /usr/lib/xorg-server/Xorg (_start+0x29) [0x427039]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) 20: ? (?+0x29) [0x29]
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE)
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) Segmentation fault at address 0x0
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE)
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: Fatal server error:
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) Caught signal 11 (Segmentation fault). Server aborting
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE)
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE)
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: Please consult the The X.Org Foundation support
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: at http://wiki.x.org
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: for help.
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) Please also check the log file at "/dev/null" for additional information.
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE)
    Mar 09 19:57:56 dexter gdm-Xorg-:5[448]: (EE) Server terminated with error (1). Closing log file.
    Mar 09 19:57:56 dexter systemd-coredump[449]: Process 448 (Xorg) of user 0 dumped core

  • ITunes 10.1.2 makes laptop unable to start windows

    I recently updated to the new iTunes 10.1.2 and when prompted to restart and went ahead and let it happen. It is now stuck on the starting windows logo during POST and will not complete it. I restart the laptop and had to use a restore point to fix the issue. After reinstalling what I have lost I verified that I was able to restart the laptop with no issues.
    I then went ahead and installed iTunes straight from the site and once again when I restarted the laptop it gets stuck on the starting windows logo. Like before I had to use a restore point. My desktop is not having this issue, I think, but has anyone else ran into this issue?

    Restarting iTunes resolves the issue in the majority of cases, if it doesn't my second guess would be your security software.
    What really seems strange here is that there have been no updates since well before Xmas, so after initially setting it up, the first update would have brought you right up to the most recent (and indeed the very last) .
    Agh, how silly of me, I see it's iTunes you have updated.
    If that's about all you've changed, you might want to try reinstalling iTunes and bonjour.
    Message was edited by: Winston Churchill

Maybe you are looking for