M8330f PC won't boot after accidentally having I-pod plugged in prior to booting

My computer won't boot after having my i-pod charge cord inserted in computer prior to booting.  I have tried f8 f9 f10 f11 nothing is getting me to a point where I can actually get the computer to boot.   I realize I may need to provide more info, but don't know what else to provide you right now.   HELP!

I used version 1.B for my motherboard.
Yes i did. I describded what happens, when i run 1 and 2 sticks.
-If these are timings then - 9 9 9 25
-1600mhm before bios update and 1337mhz after update
-Voltage: 1.5V in auto probably
Edit1: I got a response on other forum -
Could this be true:Quote
The Hyper X Fury operate off of PnP and aren't compatible with the P55 chipset natively?
In that case i could try to refund the ram, cause the place where i bought it said its compatible with P55
Edit2: I added some info on what kingston homepage (no P55) says and specification pdf also what my seller says in description of this ram type:
I`am am confused, honestly.
Edit3: Aperrantly its might not support my p55 chipset, found a reply on another similar problem tread replied  by kingston tech support:
Quote
Hi, I'm Jewel with Kingston Technical Support and would like to offer some clarification. Our currently manufactured memory, including the HyperX Fury line, is compatible with Intel 6-series chipsets and later. The DH55TC has an Intel H55 chipset which is part of the Intel 5-series chipsets. As such, the HyperX Fury memory is not compatible with your system and we do not currently offer any memory that would be compatible with your system. You can try looking online for recently discontinued part numbers like KVR1333D3N9HK2/8G or KVR1333D3N9H/4G which are compatible with your motherboard. If you are unable to return the memory to your place of purchase, please contact us and we will do our best to work with you. Please check http://www.kingston.com/company/contacts to reach support in your area.
If that`s the case then - outdated spec information everywhere...

Similar Messages

  • System won't boot after accidentally deleting /private/var/folder

    My Macbook Air is running OS 10.9 Mavericks, and I accidentally deleted the /var folder after seeing it taking lots of GB's from my storage.
    Safari, Mail and a lot of applications f'ed up itself, like safari saying it couldn't connect to the folder.
    I tried to put those folders back, and it gave me an Unauthorized Caller alert. I tried doing it again, and the folders froze, but I can still move my mouse. I restarted my computer by holding power 7 seconds, and tried to restart.
    Somehow, I saw the grey Apple logo startup screen, heard that startup chime, and 10 seconds later, it shut down. I tried doing it again many times, but to no avail.

    mikeearth wrote:
    So here's my problem. I'm using intel iMac and yesterday my Mac didn't boot( grey screen etc). I thought that it was because I used force shutdown. I used (option-cmd-r-p) to reset and after that, Mac booted up into some kind of "first time startup screen"... So I used installation DVD and restored my previous backup of the system by using the TM. After that the Mac booted and now all I get is folder with a question mark? Now what....?
    your profile suggests that you are running Tiger. if that is so, you shouldn't even be able to use time machine (introduced with Leo).
    can you please clarify ...

  • Mac mini won't boot after accidental loss of power during firmware upgrade

    i accidentally hit the power switch on the wall during an upgrade (might even have been a firmware upgrade, I didn't really look at what was going on).  Anyway, now it hangs on the silver Apple logo screen with a spinny wheel on reboot.  It's only 3 months old, it's the $599 model.
    What to do?  I see that you can download firmware restoration disks but they appear to be limited to earlier versions of the Mac mini.

    I took it to the Mac store today and they fixed it for free by booting from an external drive and finishing the half-baked system update.  Now that I know how to do that, I can fix it myself next time.
    Thanks to Alan at the Salem, NH store!!

  • Macbook Won't Start After Accidentally Interrupted Software Update

    Hey all
    I'm in need of HELP!! For the first time yesterday since my macbook purchase earlier this year, I tried installing the software updates.
    After the computer downloaded the updates, it prompted me to restart the computer and so I did. As follows, the computer restarted and began to install the updates after restarting itself (the screen's background was blue displaying only the (bar) progress of the installation, which I accidentally interrupted and shut down).
    Today, I've been trying to turn it on and even consulted the troubleshooting resolutions including restarting the computer with the control-command-power key combination, 'resetting the PRAM', and 'resetting the Power Manager'. I did this a couple of times just to be sure, let the screen load for awhile and still the screen won't go pass the gray apple logo with the loading circle.
    What should I do now guys??

    It is a very good idea to do a complete backup (clone) of your hard drive to an external drive before installing new software. That way, if it goes amiss for any reason, and they sometimes do, you can get right back to the exact state you were before the install or upgrade.
    An external hard drive for making a routine (daily) backup of your computer's drive will be the best spent $100 or so you will ever spend on your computer. Even if your hardware gets corrupted or your drive burns out or your computer gets stolen; in all cases you do not lose your computer's data if you keep a current, duplicate external drive.

  • MacBook won't boot after trying to repair with Disk Utility. Cannot boot in Safe Mode. Just powers down after about 5 minutes. Apple Hardware Test says error 4SNS/1/40000001:IG0C-0.265 But I cannot find anything on the net about it. MacBook 4,1 Intel.

    Hello Everyone,
    I am in dire need of assistance I am hoping someone could provide. I have a MacBook 4,1 with Intel Core 2 Duo processor 4GB Ram. It is taking over 10 minutes to boot up past the gray apple screen when I turn it on. First I cleared the PRam (?) then I checked the disk using Disk Utility Verify, and it said the disk needed repairs. So I ran the disk repair and it said it was unable to fix the errors on the HD.
    I did a little research and tried booting into the Single User mode, then running /sbin/fsck -fy. It said that it found errors but could not fix them. I ran it two more times as suggested and got the same result each time. I then tried rebooting and now instead of taking 10 minutes to boot up, it takes about 5 minutes on the gray apple screen and then just turns off. I started in Verbose mode to try to troubleshoot the error and it appears the last thing to come across the screen before power down is a message "Apple Yukon 2: RxRingSize <= 1024....etc".
    I decided next I would run the Apple Hardware Tester. The test came back with an error code "4SNS/1/40000001:IG0C-0.265". I am very good at searching the web but I could not find any errors that had the IG0C or IGOC or any combination at the end, but plenty of 4SNS/1/40000000(1) errors with different endings. From what I can tell people are saying anything with 4SNS/1/4000000 is a logic board failure, but this computer was literally just booting this morning until I did the /sbin/fsck -fy.
    Any suggestions are welcome and appreciated.
    Thank you for your time.

    You've a couple of issues .... when Disk Utility tells you it can't repair a drive, if the error is a soft error, like an invalid tree or node, Disk Warrior (or TechTool Pro) can handle it. However, if Disk Warrior (or TechTool Pro) can't handle it, you can erase and write zero's to the hard drive and restore to it, or you can buy a new hard drive. Sometimes running SMART Utility can provide additional insight into the health of the hard drive. 
    THe 4SNS error is a sensor error.  You could install iStat Pro to see if something is indeed getting too hot or remaining room temp or less.  You may need to take it into an Apple shop so they can use their thermal diagnostics to test and isolate it further.

  • Mavericks won't install after accidentally deleting recovery partition on 10.6.8

    I have been searching for hours for a solution and found none.
    Essentially, I was running 10.8 on my MBA which originally came with 10.6. Wishing to perform a clean install of Mavericks, I accidentally deleted the recovery partition. Installing Mavericks would then always crash midway; so eventually I reinstalled my original OS from the bootable disc from apple. Then I figure I had to create a bootable disc for Mavericks, which I did, and the result is the same, the installation crashes midway.
    Any other way I could install 10.9?
    Thanks

    Mavericks creates a recovery partition while installing.
    So, no previous recovery partition needed.
    But playing whith partitions could be a mess.
    Try a clean reinstall.

  • No booting after 10.6.7 update : progress bar on grey boot screen

    Hello,
    I have a big problem with my 2006 Mac Pro.
    I have installed the 10.6.7 update and after the installation the computer shut down.
    Since this time, each time I power it on, i see the grey boot screen with a progress bar ... the hard drive stop spinning, the progress bar goes to 10 % and then to 0% ... after this the computer shut down ..
    Nothing to do ..
    Who knows this problem and how to solve it ?

    Ok it's good !
    I've find the solution : starting when holding the shift key !
    Have a good day !

  • Not booting after creating a fat32 partition from windows 8 from boot camp

    I have windows 8.1 on a boot camp partition. I created a  fat32 partition from windows looking forward to be able to share files to Yosemite OSX. But now, neither the OSX or the windows are booting. When pressing options key is only abailable one option, a disk tagged as "windows", and after trying to use it, it refers to a error message "UNMOUNTABLE_BOOT_VOLUME". I really really appreciate any help regarding this issue.

    Your entire disk is a MBR disk. You will need to erase the disk, and start from the beginning and install Yosemite/Mavericks, and then use BC Assistant to create  a Windows partition and install Windows. If you have a Time Capsule/Time Machhine backup, you can restore it after your erase using the command below.
    You can erase the disk as follows
    diskutil eraseDisk JHFS+ OSX disk0
    Here is the Usage help syntax.
    diskutil erasedisk
    Usage:  diskutil eraseDisk format name [APM[Format]|MBR[Format]|GPT[Format]]
            MountPoint|DiskIdentifier|DeviceNode
    Completely erase an existing whole disk.  All volumes on this disk will be
    destroyed.  Ownership of the affected disk is required.
    Format is the specific file system name you want to erase it as (HFS+, etc.).
    Name is the (new) volume name (subject to file system naming restrictions),
    or can be specified as %noformat% to skip initialization (newfs).
    You cannot erase the boot disk.
    Example: diskutil eraseDisk JHFS+ UntitledUFS disk3

  • Can't Boot After New HD + Time Machine Restore

    So a couple days ago my 27" iMac running Snow Leopard started making some weird noises and stalling out. Annoyed, I talked for a couple hours with apple tech support which eventually lead me to run an Apple Hardware Test. This test returned the error
    "Alert! Apple Hardware Test has detected an error.
    4HDD/11/40000000 SATA(0,0)"
    I scheduled an appointment at the Genius Bar, and they replaced the hard drive.
    After that I got it home and did a System restore from my time machine backup. It finished fine, but when I restarted it got stuck on the grey apple screen with the spinning dial thing.
    I called apple back and they had me do a couple things like repair disk, verify disk, and one person had me reboot into this command line mode and type some stuff in. Nothing worked. After that They had me try to reinstall the OS first from archive, and next by erasing the hard drive and doing it. Both times the install fails with a big yellow exclamation point saying that it couldn't install support files and the OS couldn't be installed.
    Any ideas how to fix this?
    I'm currently trying to restore from my time machine backup again, but I'm not hopeful.

    Here's what I got - apologies for any formatting peculiarities.
    The problem: 10.6.6 mac won't boot after time machine restore to disk.
    Further symptoms: Booting with Command-v shows several errors: usually blued and loginwindow collapse with errors from launchd. Errors will be of the style "dyld: Symbol not found: CSSMOID_APPLE_TP_MACAPPSTORERECEIPT" and other CommerceKit / CommerceCore framework errors.
    A solution: Your Framework Security library may be an older version (possible cause with Time Machine below). The easiest way to fix this is to find another, working 10.6.6 Mac, and update the Security library on the broken machine.
    Identifying if you're affected:
    1) Boot the broken machine into "target" mode - hold "Command-t" during boot until the [Firewire|http://itunesu.utah.edu/terms/images/Firewire_Icon.png] icon appears.
    2) Connect the broken machine to the working 10.6.6 machine with a firewire cable.
    3) On the working machine, the disk of the broken machine should mount.
    4) Open Terminal
    5) Run "ls /Volumes" - the name of disk you mounted should be there (in this example, we'll use "Macintosh HD".)
    6) Typing in the path of the broken machine, run:
    <pre>
    nm /Volumes/Macintosh HD/System/Library/Frameworks/Security.framework/Versions/A/Security | grep random_fd | cut -d. -f2
    </pre>
    (this does a dump of the library, looking for the version value)
    If this comes back with the value 22457 (or less?), your Mac is not booting because it does not have the updated version of the Security library, which is required in 10.6.6 since Snow Leopard added the Appstore / Commerce framework.
    Fixing if you're affected:
    1) First, make sure the working 10.6.6 Mac has a correct version of the framework:
    <pre>
    nm /System/Library/Frameworks/Security.framework/Versions/A/Security | grep random_fd | cut -d. -f2
    </pre>
    For 10.6.6, this should be at least "22458"
    2) *Be extremely careful at this point* - Make sure on the mounted disk (not the machine you are working on!) run the following
    <pre></pre>
    2a) Make a backup of the broken library
    <pre>
    mkdir /Volumes/Macintosh HD/savedLibrary
    cp /Volumes/Macintosh HD/System/Library/Frameworks/Security.framework/Versions/A/Security /Volumes/Macintosh HD/savedLibrary
    </pre>
    2b) Copy the working version over the non-working version:
    <pre>
    cp /System/Library/Frameworks/Security.framework/Versions/A/Security /Volumes/Macintosh HD/System/Library/Frameworks/Security.framework/Versions/A/Security
    </pre>
    3) Eject the mounted disk from the working Mac, disconnect the firewire cable, and reboot the "broken" Mac. It should come up.
    If it doesn't, you have problem(s) that are probably outside the scope of this. I'd also suggest restoring your original security library that you saved off.
    Suspected cause:
    It appears that Time Machine never recorded the change to the Security library after the update. If the library hadn't changed, the machine should have failed to boot like it did after restore the moment a 10.6.6 update was applied.
    Inspecting the contents of my Time Machine backups before and after updating shows that Time Machine never updated the Security Framework library - why is still not 100% determined, but restoring from it is definitely broken. Combing through the backup databases on my Time Machine disk:
    (I upgraded to 10.6.6 on January 6)
    <pre>
    for name in 2010-12-30-093337 2011*
    do
    echo -n "In backup on ${name}, version of Security library is: "
    nm "${name}/Macintosh HD/System/Library/Frameworks/Security.framework/Versions/A/Security" | grep random_fd | cut -d. -f2
    done
    </pre>
    In backup on 2010-12-30-093337, version of Security library is: 22457
    In backup on 2011-01-04-100707, version of Security library is: 22457
    In backup on 2011-01-05-082402, version of Security library is: 22457
    In backup on 2011-01-06-092846, version of Security library is: 22457
    In backup on 2011-01-07-094827, version of Security library is: 22457
    In backup on 2011-01-10-093559, version of Security library is: 22457
    In backup on 2011-01-11-110542, version of Security library is: 22457
    In backup on 2011-01-12-094137, version of Security library is: 22457
    In backup on 2011-01-13-103238, version of Security library is: 22457
    In backup on 2011-01-14-113145, version of Security library is: 22457
    In backup on 2011-01-18-112856, version of Security library is: 22457
    In backup on 2011-01-20-114953, version of Security library is: 22457
    In backup on 2011-01-21-103642, version of Security library is: 22457
    In backup on 2011-01-24-102321, version of Security library is: 22457
    In backup on 2011-01-27-002508, version of Security library is: 22457
    In backup on 2011-01-27-011931, version of Security library is: 22457
    In backup on 2011-01-27-104406, version of Security library is: 22457
    In backup on 2011-01-27-114322, version of Security library is: 22457
    In backup on 2011-01-27-123928, version of Security library is: 22457
    In backup on 2011-01-27-134523, version of Security library is: 22457

  • [SOLVED] Arch won't boot after I created a separate /var parition

    Arch won't boot after I created a separate /var parition on an existing installation.And let me confess: it was maybe stupid trying to do it on an existing install.
    I edited the fstab correctly, copied the files using rsync preserving permissions. Then I kept a backup of /var using tar. Then went on to delete everything under /var, ie /var/*, the /var folder is still there. All this I did from a live CD. After that I booted into my arch linux. Here I get messages about systemd successfully finishing fsck on each of my partitions, then the screen starts blinking. And there is no more output. Pressing Ctrl+Alt+Delete causes systemd to stop its services and reboot.
    Having realized I had borked my system, I removed the /var line from fstab and restored /var from the tar file I made earlier. Again I did this from a live cd. Rebooted into my arch system, and again similar issues, namely that after fsck and messages informing a few services had started, the screen keeps blinking.
    The live cd I used for reorganizing my partitions was elementary OS freya. They have GParted in there. I also have an arch install iso lying aroung from May 2013. If necessary, I can download the latest version. I am currently typing from a Windows installation I dual boot from.
    I don't know how to extract any boot logs as I am locked out of the system. Here is my fstab in any case:
    # Filesystem information
    # /dev/sda5 LABEL=fs_root
    UUID=b9d739cf-fd8c-46dd-a919-bd827dc47c66 / ext4 rw,noatime,data=ordered 0 1
    # /dev/sda9 LABEL=fs_var
    UUID=ec0f7a49-dccd-43ab-8651-9aa3fdb41cc7 /var ext4 rw,noatime,data=ordered 0 2
    # /dev/sda2 LABEL=fs_boot
    UUID=0e8ab31a-3bda-4b85-a901-a36f21b1583d /boot ext2 rw,noatime 0 2
    # /dev/sda6 LABEL=fs_home
    UUID=d9e63c47-274e-447f-ad01-0d97afe0fd34 /home ext4 rw,noatime,data=ordered 0 2
    # /dev/sda7 LABEL=fs_swap
    UUID=7301227c-e9f3-41b8-9d0f-4cf3c159491c none swap defaults 0 0
    # /dev/sda3 LABEL=fs_win
    UUID=12B639D1B639B5D7 /fs_win ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,nofail,noauto,x-systemd.automount 0 0
    # /dev/sda3 LABEL=fs_share
    UUID=D272269772268079 /fs_share ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,noauto,nofail,x-systemd.automount 0 0
    I would greatly appreciate any help.
    Last edited by richcocoa (2015-05-03 18:04:44)

    Have you moved everything from /var to /new_var (i named it for learning purpose)? You shoud copy content from /var but not on the fly but booting from arch iso cd, and than you shoud mount your / into arch-chroot environement, mount all of your mount points and than copy content from default /var to new /var. The copying should be done with this
    cp -rax
    and you can add -v switch to verbose output. I have my own /var moved the same way.
    The simples way is:
    -boot the arch iso cd
    -mount all of your mount point (i created here in this step /new_var to move /var to a new place, and this /new_var i put in /etc/fstab as /var later)
    -copy /var to /new_var with -rax or -vrax (recursive, archive, this filesystem or verbose, recursive, archive, this filesystem switches)
    -umount all of it
    -reboot.
    Last edited by firekage (2015-05-02 07:49:20)

  • My MacAir 1st gen. won't boot after latest OS X Lion update.

    My MacAir 1st gen. won't boot after latest OS X Lion update. tried safe boot(didn't work) tried disk repair, said it was successful, but my mac won't start up. Just get white screen.  Also been having trouble with it overheating. Fan seems to work. But when it get too hot whole interface slows down.

    Yikes, I hope you have AppleCare on it still, I think it needs to be taken in, but as a last ditch effort...
    Have you done a PRAM reset, CMD+Option+p+r...
    http://support.apple.com/kb/HT1379
    In fact, do 3 in a row, takes a bit of time.

  • Im having trouble getting my macbook pro to boot up after a fail safe boot, im getting as far as the grey screen with the apple loggo. so im trying to run a disk repair but is saying the disk is locked, how do i unlock disk??

    Im having trouble getting my macbook pro to boot up after a fail safe boot, im getting as far as the grey screen with the apple loggo. so im trying to run a disk repair but is saying the disk is locked, how do i unlock disk??

    Some clarification may help.
    You say you cannot boot normally.  It shows a gray screen with the Apple logo.
    Did you say it will boot successfully in Safe Mode (boot, then hold down the Shift key)?
    How did you boot the machine to run Disk Utility?  (Which keyboard combinations)?

  • I have a Mac, IPad, I phones, and 2 Windows Vista Pcs and I'm having trouble with the Windows Laptop staying connected.  I have to re-boot after and extended period of time please help

    I have a Mac, IPad, I phones, and 2 Windows Vista Pcs and I'm having trouble with the Windows Laptop staying connected.  I have to re-boot after an extended period of time please help.  Thanks!

    I have a Mac, IPad, I phones, and 2 Windows Vista Pcs and I'm having trouble with the Windows Laptop staying connected.  I have to re-boot after an extended period of time please help.  Thanks!

  • GRUB won't start after installation. Boots direktly to Windows 7

    Hello,
    I am having a hard time installing Arch next to Windows 7 on an UEFI Notebook.
    The partitions of the HDD (GPT) looks like this:
    sda1 Boot partition, fat32, 400 MiB. Mounted as GRUB Wiki says at /boot/efi
    sda2 swap
    sda3 Arch
    sda4 Windows 7
    First I install Windows 7 which workes without problems.
    After that is done I start installing Arch. All goes well without any errors till the end.
    For installing GRUB I use
    grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch_grub --recheck
    and
    grub-mkconfig -o /boot/grub/grub.cfg
    Both finish without errors.
    First problem is os-prober never mangaged to find Windows 7 by itself. Not once in 6 installation retries.
    Second problem. After I finished installtation and rebooting, GRUB doesn't show. It direktly starts to boot Windows.
    I'm following the Beginners Installation Guide step by step (except the GRUB part). What am I doing wrong?
    Are the Mountpoints wrong?
    I don't know which config files you need to help.
    Last edited by Peikko (2013-08-13 11:08:55)

    It did change but only for this session. After a reboot, the order was reset again.
    But this is not the problem anymore.
    I have found the solution for this problem here: http://www.jsravn.com/2013/06/26/thinkp … -arch.html
    The only problem that still exists is that os-prober is not able to detect the existing Windows 7 partition and add it to the GRUB menu.

  • Macbook pro won't boot after installing update 10.9.3

    macbook pro won't boot after installing update 10.9.3

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode.
    Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
    Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
    The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    Test while in safe mode. Same problem?
    After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

Maybe you are looking for