Re: KT6V New system won't boot.

Similar problem here...
I got new (bought in one week) KT6V, installed Sempron 2500+ and 256MB DDR400 but I never boot it successfully.
No video signal seen in monitor, monitor led always stays orange. I removed all PCI card and also unconnect HDD and CDROM powers to test, but it is same... 
I donot know what the problem is, and donot know what I can do next
Because of the no screen, I donot enter BIOS, I checked many times my video card...It's tested on another machine, no problem with that...
Waiting your comments urgently...
Thanks...

SaVaTaGe: "...MSI K4AV
                    AMD Athlon XP 2000+
                    128+256 SDRAM 133Mhz
                    With 300W Power..."
Your Mobo isn't the same of first post, so it's possible you could get wrong or less advises than you could get with a new post. Also, it seems that you named it wrong: Shouldn't it KT4AV ? Your'e using 2 Difs. memory. Better take the 128 out at least during troubleshoot. 300W P.S. may be too poor, that's why you have beeing asked to tell it's specs.
Off Topic: Grayone: Remember what I said ?
                   

Similar Messages

  • KT6V New system won't boot.

    I have a new system witha KT6V LSR,  AMD Athlon 2600+, Barton,  133/266FSB, 512K cache.  ATI Radeon 7200 video card.  PNY PC 3200 - 512MB. OKIA Power suppley 450W, 3.3V 28A, 5V - 50A,  12V - 18A.    
    This system hangs immediately.  Never shows me the CMOS screen.  D - bracket shows 4 red lights > defective or improperly installed CPU.  Both the MB and CPU have been returned once.  Is this CPU and MB combination incompatible?  What am I missing?

    Man, I had a MSI KT6V and i got the same problems, 4 Red Leds. Did you set the Fast Command of the memory to FAST or ULTRA?. My problem was for it.
    I had to Change the mobo, and in the store i changed it for a MSI KT6 DELTA but i don´t want to set the fast command, just normal and no more. Try disconnecting 12V Cable of the Mobo, Power Cable, Battery, and reset CMOS, then Connect everything again and proof it. Try with another memory, it can solve the problem, if the problem dissapears, then reinstall your other memory again.

  • PT880 New system won't boot to any drive

    I am putting together a new system:
    Case:  Aspire X-Superalien
    Power Supply:  500w (came w/case) which says:
                           AC INPUT:  115V/230V~  10/5A   50-60HZ
                           DC OUTPUT:  +3.3V     +5V     +12V     -5V     -12V     +5VSB
                                                28A       30A      34A     0.3A     0.8A      2.0A
                           +5V    +3.3V    COMBINED LOAD: 200W
                           +12V   +5V    +3.3V    COMBINED LOAD: 480W
                           TOTAL POWER: 500W
                          (no idea what all that means, but you guys seem to)
                          The PS also has 2 blue 80 mm lighted fans
    Motherboard:  PT880 NEO LSR
    Processor:  Intel P4 2.8 GHZ 800MHZ bus 1MB L2 cache (HT) Prescott
    Video Card:  GeForce 2 MX400
    Disk Drives:  Western Digital 200GB hard drive (formatted on another computer,
                                  no OS yet)
                        LiteOn DVD rewritable drive
                        Mitsumi 3.5 in. floppy drive
    Operating System:  none yet, will use Windows XP as soon as I can get to my
                                 drives.
    I can get to my BIOS.  All my drives appear in BIOS and show up as the correct slave, master settings.  I have disabled all the SATA RAID stuff.  When I try to boot up, it does a memory test,  lists all my drives and stuff...then freezes.  I have tried changing the boot up order of my drives into all possible orders.  The four lights on the back give me different messages each time.  Nothing consistent there.  What could be keeping me from booting to my drives?

    Your PSU looks to be quite capable of handling a Prescott, so as Raidahs said, all you need is the BIOS flash.  I asked you for your rail by rail currents in another post, but as I see them here, never mind.  Unfortunately, since Intel kept making changes to the Prescott, the earliest BIOS that will run the Prescott for this board is v1.4.  The boards are shipped with v1.1, which is rather aggravating.  If you don't have access to a Northwood chip (P4 with 'C' after it's speed, ie. 2.8C), I would suggest contacting either MSI or whoever you purchased your board from, and ask them to update your BIOS.  Do not let them talk you into paying for this service, as the board's packaging plainly states that it is designed for the Prescott, despite the fact that it does not support it out of the box.
    If you have any problems, just let us know.  Heck, keep us posted no matter what happens

  • New system won't boot

    I installed a athlon 64 in a k8t neo  board. The fan starts on the cpu but the monitor and the computer does not boot. It shows all 4 LEDS on the D bracket which says the cpu is the problem. I am tring to determine if it is the cpu or motherboard . I purchased everthing online.

    Hi
    4 red leds, can be Mobo, CPU, PSU or RAM. unlikely to be mobo or CPU, unless you have a groud somewhere, for instance an extra pillar on backplate, not lined up with shielded hole will cause short and 4 red leds, or complete cutout.
    The PSU is marginal at 18 amps on the +12v, may be the cause.
    Ram is controlled by CPU, so if it does not start then you get 4 red leds. is there any beeps. If you can find a stick to try it would help, DDR2100 is good,
    Could be CPU, say a bent pin or heatsink not seated correctly.
    Just need to work your way through them, better reset CMOS with the JBAT1 jumper, remopve power cable first.  I would think RAM or PSU are most likely, if you have not shorted the mobo.
    cheers
    jocko

  • System won't boot-no chime.

    Despite repeated attempts and resetting the CUDA button, the system won't boot when start button is pressed. In the first few seconds it seems to make normal sounds; but no chime and settles into simply fan noise. This is true even if using C (with an Install CD). or Shift key. Is there anything else I can try? (I know it's actually a G3 B&W Motherboard; but I had nowhwere else to post it)

    I do not remember exactly what was happening when it stopped. It may have been executing something , hung up, and wouldn't respond to the Command-Opt-Esc or I do remember one incident when it was booting up and stopped when it was partly thru "searching for local discs.
    I checked the ref. article and tried to measure the voltages on the power connector. I was never quite sure what pin was what, since the colors did not jive with those in the article. At any rate 2 were approx. + 5 V (one was 4.85), the rest were essentially zero (I believe 1 or 2 were about 300 mv). I did notice that when the power connector is reconnected and start up is attempted, 3 little green lights come on on the motherboard. One goes off after a while.
    I have tried the old Sonnet upgrade and have tried reseating all the RAM modules. All to no avail.
    The Hard drive and all other parts seemed to be working fine prior to the failure.

  • System won't boot. INIT: No inittab file found Enter runlevel:

    After the latest update that changed how intel ucode is updated, my system won't boot.
    I think I missed a line when I edited "/etc/grub.d/10_linux" and ran grub-mkconfig -o /boot/grub/grub.cfg.
    Any ideas on how to fix this?
    I can't run grub-mkconfig from another machine, as it uses the live kernel info.
    Any help would be greatly appreciated. Otherwise I'll have to reinstall

    TheSaint wrote:
    SyXbiT wrote:
    But I still get the error:
    system won't boot. INIT: No inittab file found
    Enter runlevel:
    It seems to me that you've an old Arch version. inittab is deprecated AFAIK.
    What is the Arch iso version?
    That would probably be mid-2012 at the very latest I think as that's when I remember completely moving over to systemd...
    @SyXbiT: Are you using the current Arch install ISO?

  • System won't boot up

    Help please. I have a kt6 delta running an athlon 2700+ xp chip, 512 mb ddr 400.
    When I set the fsb at the correct speed for the chip (166) the system won't boot hard drive led lights up constant. dvd drive  and cd-r drive each run but the system won't boot.  system seems to run fine at default and 133 mhz but the chip is incorrectly identified in windows (xp pro sp1) Any Ideas whats wrong?

    Hi -   I have the same board with the same processor, I have not problems rebooting after changing the bus speed. But I have had problems rebooting after adding in any card PCI or AGP. the system seems to have trouble clearing the Cmos, I would try clearing the CMOS with  the JBAT. it doesn’t always seem to work but I have had some luck, though I have also pulled out the battery a couple of time too..
    Good luck!

  • Upgrade from snow leopard 10.6.8 to montain lion on a iMac system won't boot getting a crossed out circle

    Upgrade from snow leopard 10.6.8 to montain lion on a iMac system won't boot getting a crossed out circle

    Clean install OS.10.6.8 update it completly. May be you ignored some firmware update.
    I have two incedents.
    My thunderbolt port stopped working after upgrading to ML 10.8. I booted from external 10.6 , 10.7 still didnt work. Then i clean installed 10.6.8 and ran software update it updated the thunderbolt firmware and all is well now. This firmware update for some reason didnt show up in ML 10.8.
    Secondly , when i upgraded my Brother's Macbook from 10.5 to 10.6.3 it would install but stuck with crossed out circle. Then i downgraded checked for update found an efi update , then the 10.6.3 worked fine.

  • [SOLVED] Switch to systemd - Now system won't boot

    I saw that todays update upgrade included the installation of systemd. I looked the wiki and did the necessary changes (I already had made the /etc/hostname etc. files). So I added the
    init=/bin/systemd
    line to grub and now my system won't boot. I get an error saying something about syslog service not enabled and then a black screen. I can boot my machine fine without the "init=/bin/systemd" line but I want to run a pure systemd system since Arch is moving to it anyway. In the wiki it mentions to install systemd-sysvcompat but it conflicts with initscripts it says. What am I doing wrong or missing?
    Last edited by fettouhi (2013-12-08 14:42:04)

    fettouhi wrote:
    Thanks for the clarification about the DAEMONS list. My DAEMONS list is:
    DAEMONS=(!hwclock ntpd syslog-ng !network netfs crond @alsa dbus networkmanager ufw cupsd avahi-daemon samba)
    when I try to enable alsa and dbus I get this
    [root@andre ~]# systemctl enable alsa-store.service
    The unit files have no [Install] section. They are not meant to be enabled using systemctl.
    [root@andre ~]# systemctl enable alsa-restore.service
    The unit files have no [Install] section. They are not meant to be enabled using systemctl.
    [root@andre ~]# systemctl enable dbus.service
    The unit files have no [Install] section. They are not meant to be enabled using systemctl.
    Is LVM handled automatically by systemd? The reason I ask is because I have the USELVM= set to YES in rc.conf.
    I made the permanent transition to systemd and did not start alsa at all - sound works fine - so I never bothered with the alsa-store/alsa-restore service files at all - it just works! Also dbus gets handled by default in systemd so you don't need any starting of dbus service at all... it just works.

  • Btrfs: System won't boot anymore after unclean shutdown

    Hi,
    I have a problem with my ArchLinux (kernel 3.19.2-1-ARCH).
    I have my root partition as BTRFS and no /boot partition.
    After an unclean shutdown the system won't boot anymore.
    GRUB loads the kernel and the kernel starts but it hangs saying: Mounted /dev/sda3 on real root.
    Then, I have to start a Live CD and do:
    btrfsck /dev/sda3
    After that the system boots correctly.
    I've tried adding fsck to the HOOKS in the mkinitcpio.conf file and in fact it tries to fsck the filesystem (but with BTRFS, fsck.btrfs doesn't work...)
    What can I do?
    Thanks

    I'm also having this problem. I tried booting up the netinstall image to debug it, but I can't mount my btrfs volume from there either: mount just hangs. After a while, the kernel goes:
    [...] INFO: task mount:612 blocked for more than 120 seconds.
    [...] Not tainted 3.19.2-1-ARCH #1
    [...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [...] INFO: task btrfs-transacti:636 blocked for more than 120 seconds.
    [...] Not tainted 3.19.2-1-ARCH #1
    [...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    From this post I guessed that I might just need to wait so that I could defrag the volume once it was mounted, but it's been hanging for over 15min now (the message above continues to come up periodically).
    Like the OP in the thread I linked to above, my btrfs volume is inside an LVM volume (which is on dm-crypt). Don't know whether that's relevant.
    Output of btrfs-check:
    Checking filesystem on /dev/pixie/btrfs
    UUID: e04cc661-e31a-4dbf-870d-664bc913e34a
    found 76855677062 bytes used err is 1
    total csum bytes: 72928436
    total tree bytes: 2092515328
    total fs tree bytes: 1888452608
    total extent tree bytes: 104644608
    btree space waste bytes: 357251032
    file data blocks allocated: 181197139968
    referenced 109440282624
    btrfs-progs v3.19
    dmesg output:
    [ 36.824998] Btrfs loaded
    [ 36.826713] BTRFS: device fsid e04cc661-e31a-4dbf-870d-664bc913e34a devid 1 transid 98618 /dev/dm-3
    [ 46.219014] BTRFS info (device dm-3): disk space caching is enabled
    [ 46.259830] BTRFS: detected SSD devices, enabling SSD mode
    [ 240.333313] INFO: task mount:539 blocked for more than 120 seconds.
    [ 240.335542] Not tainted 3.19.2-1-ARCH #1
    [ 240.337795] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [ 240.340263] mount D ffff8800cf2837f8 0 539 453 0x00000000
    [ 240.340277] ffff8800cf2837f8 ffff8800cf2331b0 0000000000013f00 ffff8800cf283fd8
    [ 240.340286] 0000000000013f00 ffffffff81818540 ffff8800cf2331b0 ffff8802094f67a8
    [ 240.340291] 0000000000000004 ffff8800cf283758 ffffffffa0a2fc91 ffff8802094f67a8
    [ 240.340298] Call Trace:
    [ 240.340335] [<ffffffffa0a2fc91>] ? set_extent_buffer_dirty+0x71/0xc0 [btrfs]
    [ 240.340357] [<ffffffffa0a05796>] ? btrfs_buffer_uptodate+0x56/0x80 [btrfs]
    [ 240.340366] [<ffffffff8155e999>] schedule+0x29/0x70
    [ 240.340389] [<ffffffffa0a47745>] btrfs_tree_lock+0x65/0x200 [btrfs]
    [ 240.340396] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
    [ 240.340410] [<ffffffffa09e5cd9>] btrfs_search_slot+0x799/0xaa0 [btrfs]
    [ 240.340425] [<ffffffffa09e79f5>] btrfs_insert_empty_items+0x75/0xd0 [btrfs]
    [ 240.340446] [<ffffffffa0a47a37>] btrfs_insert_orphan_item+0x67/0xa0 [btrfs]
    [ 240.340465] [<ffffffffa0a4a12e>] insert_orphan_item+0x5e/0x90 [btrfs]
    [ 240.340482] [<ffffffffa0a4c531>] replay_one_buffer+0x361/0x380 [btrfs]
    [ 240.340504] [<ffffffffa0a2f244>] ? alloc_extent_buffer+0x34/0x370 [btrfs]
    [ 240.340523] [<ffffffffa0a488f3>] walk_down_log_tree+0x1d3/0x410 [btrfs]
    [ 240.340540] [<ffffffffa0a48bfb>] walk_log_tree+0xcb/0x1d0 [btrfs]
    [ 240.340558] [<ffffffffa0a507f7>] btrfs_recover_log_trees+0x1e7/0x490 [btrfs]
    [ 240.340575] [<ffffffffa0a4c1d0>] ? replay_one_dir_item+0xf0/0xf0 [btrfs]
    [ 240.340596] [<ffffffffa0a08b3e>] open_ctree+0x17ae/0x2030 [btrfs]
    [ 240.340609] [<ffffffffa09dd633>] btrfs_mount+0x843/0x920 [btrfs]
    [ 240.340618] [<ffffffff8117b7aa>] ? pcpu_alloc+0x35a/0x680
    [ 240.340628] [<ffffffff811d5d68>] mount_fs+0x38/0x1c0
    [ 240.340634] [<ffffffff8117bb05>] ? __alloc_percpu+0x15/0x20
    [ 240.340641] [<ffffffff811f116b>] vfs_kern_mount+0x6b/0x120
    [ 240.340647] [<ffffffff811f4184>] do_mount+0x224/0xb40
    [ 240.340653] [<ffffffff811f4dae>] SyS_mount+0x7e/0xe0
    [ 240.340661] [<ffffffff81562809>] system_call_fastpath+0x12/0x17
    [ 240.340671] INFO: task btrfs-transacti:561 blocked for more than 120 seconds.
    [ 240.342927] Not tainted 3.19.2-1-ARCH #1
    [ 240.345175] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [ 240.348473] btrfs-transacti D ffff88020b88bd98 0 561 2 0x00000000
    [ 240.348483] ffff88020b88bd98 ffff880211edc590 0000000000013f00 ffff88020b88bfd8
    [ 240.348491] 0000000000013f00 ffff8802162289f0 ffff880211edc590 ffff8802094a70c8
    [ 240.348496] ffff8802094d8000 ffff880200000000 ffff8802094d8000 ffff880200000033
    [ 240.348501] Call Trace:
    [ 240.348511] [<ffffffff811b5d1a>] ? kmem_cache_alloc+0x16a/0x180
    [ 240.348525] [<ffffffffa09e07ca>] ? btrfs_free_path+0x2a/0x40 [btrfs]
    [ 240.348543] [<ffffffffa0a64213>] ? __btrfs_run_delayed_items+0xf3/0x1d0 [btrfs]
    [ 240.348550] [<ffffffff8155e999>] schedule+0x29/0x70
    [ 240.348568] [<ffffffffa0a0b555>] btrfs_commit_transaction+0x2a5/0xbe0 [btrfs]
    [ 240.348573] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
    [ 240.348590] [<ffffffffa0a06fc5>] transaction_kthread+0x1d5/0x240 [btrfs]
    [ 240.348605] [<ffffffffa0a06df0>] ? btrfs_cleanup_transaction+0x5a0/0x5a0 [btrfs]
    [ 240.348611] [<ffffffff81091748>] kthread+0xd8/0xf0
    [ 240.348617] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
    [ 240.348624] [<ffffffff81562758>] ret_from_fork+0x58/0x90
    [ 240.348629] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
    Last edited by ouroboros8 (2015-04-02 12:37:25)

  • New GTX 770 in existing system won't boot

    So I thought I upgrade my PC with a brand new MSI GTX770. The system just won't start. Screen shows B2 in lower right hand corner and a solid cursor upper right. After a while the cursor starts blinking and B2 dissapears. Still a black screen. No possibility to enter bios, no bleeping, all fans are spinning.
    When I put back in my good old MSI GTX580 all is fine again.
    I am an advanced (MSI) user but never ever experienced this before. Highly frustrating and surely no plug and play experience. What to do? Underneath you'll find my systems components:
    OS: Microsoft Windows7 64bit Home Premium Gold (SP1)
    SSD (boot): Samsung SSD 840 EVO 250GB
    Memory: Corsair Vengeance BLUE,1600-8GB KIT
    PSU: Cooler Master Silent Pro M2 720WATT
    Mobo: MSI Z77A-GD65, s1155, 4x DDR3, 4x SATA-300, 4x SATA-600
    BIOS Version Mobo V10.1/21020208
    VGA (new): MSI Geforce GTX 770 2Gb
    VGA (old): MSI Geforce GTX 580 1,5Gb
    CPU: Intel Core i5 3570K, 1155, 3,4GHz, Box
    CPU Cooler: Scythe Mugen 2 Rev. B
    HDD: Seagate Barracuda 2TB - 3.5inch
    SSD: Crucial m4 , 128GB, 2.5", SATA 600, SSD
    DVD: Sony Optiarc DVR DL 24X,SATA
    Casing: Corsair Graphite 600T
    PS: I did not manage to find a similar problem on this forum let alone a solution to it. I tried BIOS A vs BIOS B to no avail. Somewhere else I read I may have to flesh the new cards BIOS but how to do so if I cannot even get it to work?
    Any help is welcome!

    Today I received the following I was like really???!!!!
    "Dear Sir/Madam,
    Thanks for contacting MSI Technical Support Team!
    Regarding your concern, there are many possibilities on why the system could
    not boot up. Therefore, would you kindly please refer to the suggestions below to
    troubleshoot the issue?
    1) Unplug all the components and devices on the MB, and then reinstall the CPU,
    RAM (one piece), VGA card and power supply only. Please add some thermal
    gel on the CPU, and then reinstall the CPU fan correctly and tightly.
    2) Clear CMOS (How to clear CMOS, you could refer to the manual), and then
    enter bios to Load Optimized Defaults->Save & Exit.
    3) Try to boot up the minimum system. If it still cannot boot up, please change
    another more powerful power supply for a try;
    4) If the problem still persists, please change another RAM with different brand to
    try.
    5) Please confirm the processor installed is compatible with the MB as well as
    the BIOS.
    6) If these attempts above does not work, we have to suggest you contact your reseller (The place you bought this MB from) and have them test the MB completely for you to check if this MB is faulty or not, then ask for some help.
    If the reseller for some reason can not help, you could try to contact MSI distributor from below http://www.msi.com/service/wheretobuy/ near your place or MSI office from below http://www.msi.com/about/contact-us/
    Best wishes,
    MSI Technical Support Team!"
    So adding a MSI card to my MSI Board mean I have to brake down all of my system, even remove my CPU (running fine) and buy some thermal gel. And while I am in the store buy a more powerful powersupply (mine already meets the specs) and/or ask my reseller to help me out checking if my motherboard (working fine) is faulty?
    Well I just RMA'd my 770. So much for plug and play; even MSI parts are not compatible. A real bummer.

  • My system won't boot past POST after I plugged in my new SATA drive. (SATA noob

     
    I have a MSI K8n Neo 2 Platinum mobo with a Athlon64 +3500 and 1gig dual channel DDR 400. I currently have 2 drives set up a IDE primary (MAxtor 6Y120) and a IDE slave (Maxtor 6L080).
    I recently purchased a Maxtor DiamondMax 10 6L300S0 300GB Serial ATA 7200RPM Hard Drive w/16MB Buffer.
    It is my first SATA drive ever so non the less I am a newb. I want to use it as a non Raid media storage device while my primary IDE remains my boot OS drive.
    I plugged the SATA in to the sata one port and powered it. I enabled the SATA in the bios with RAID disabled. When the system boots up it does the memory chech and lists all the IDE devices. Then it says "Detecting IDE drives..." and just hangs there. The new drive spins so it definatly has power but occasionaly it make occasional clicking sounds.
    Once it actually booted up and windows detected it. I decided to reboot it just to play it safe but it never would get past post screen again. I can boot up the system normally when I unplug the SATA cable.
    Please help I need to know if I am doing something wrong or I should RMA the drive. THANK YOU!

    Got the same problem:
    pata Maxtor Diamond Max =9 200 (40/160) Boot drive
    AMD 64 x2 3800
    Bios 1.2 090905 using MSi online auto update utility
    2x 512 DDR double sided
    X850 pro 128mb
    PSU Sweetex 650w
    Switched power supply
    110/220 V switchable (220 V: 5 Amp/ 110V:10 Amp)   
    + 3.3 V    28 Amp
    +    5 V    45 Amp
    +  12 V    25 Amp
    -5 V    0.5 Amp
    -12 V    0.8 Amp
    - 5 Vsb  2 Amp PEAK 2.5
    Max. 650 Watt
    CE, FC
    Boots perfectly with 1 pata, adda sata to sata 1 or 2 or 3 or 4
    Boot stalls in bios at Raid setup. Tried enable raid with no drives enable , system booted twice, turned off overnight, then failed to start the next day. Will only restart with a cold reboot. Hot reboot produces a long BEEEEEP & power is on but nothing happens no post nothing.
    SATA drive was taked from a working system (ECS 755a  - AMD 64 3000 - PATA 200 / SATA 200), configured 40/160 40=OS Winxp 64 / 160 = data. System will not boot if this is the sole drive connected.

  • Please Help: Installed new CPU (i7) now system won't boot.

    I'm hoping someone can help.
    I have an MSI H55M-P31 (MS-7636) motherboard, and I updated the BIOS to 1.A0.
    But when I installed the new CPU, I get 3 Long beeps, and then my computer won't boot.
    I have 4Gigs of Memory
    Current CPU: (working 100%)
    3.07 gigahertz Intel Core i3 540
    64 kilobyte primary memory cache
    256 kilobyte secondary memory cache
    4096 kilobyte tertiary memory cache
    64-bit ready
    Multi-core (2 total)
    Hyper-threaded (4 total)
    500watt PSU
    Please Help, I don't know what to do now. (did check CPU compatibility on website - i7870)

    What PSU is that and what are the ratings of that PSU ? See the label on the side.
    Are you trying to use the onboard graphics?
    That CPU does not have integrated graphics.  http://ark.intel.com/products/41315

  • System won't boot. Could really use some help here.

    I have the K8T-Neo FISR2 mobo. When I set up the system, the SATA drive was set up as drive F: (onto which I installed Windows XP Home). I added a 2nd SATA drive later, and it became C:. Both drives are plugged into the Promise SATA ports. The system has been running fine for about a year now.
    I was having a problem with a program not running properly. I stopped the process and tried to restart it, but it didn't work. It was a program that drives my Logitech gaming keyboard (with LCD screen). After I rebooted, the system would load windows, then after Windows was loaded, it would load up a program when I went into it and crash. It looked like it would crash on PXHELP.DLL (something like that). I booted up into safe mode, renamed the file so it wouldn't load, and now it won't boot at all. It starts to show the Windows logo and then instantly reboots. I can't even get into Safe Mode as it does the same thing.
    I tried booting from an XP CD to do a repair, but when it boots, it doesn't see the hard drives. I downloaded the Promise drivers, put them onto a floppy, and load them as Windows is booting from the CD. It seems to load the drivers, but when I choose to do a repair (or even a new install), Windows comes back and tells me that I have no hard drives attached to the computer. I just can't seem to get Windows to see those hard drives!
    I could really use some advice here......

    Quote from: Tiresmoke on 04-January-06, 01:36:35
    Try swapping the Drive Cables. You may have one that is not engaging as well as it should.
    When I let the PC boot up like normal (without booting from the CD), it sees the drives and Windows tries to load, so I don't think it's the cables. I'll make sure they're reset, but I really don't think that's it.

  • New HD won't boot internally; fine externally

    I'm trying to swap out the hard drive on my wife's late-2008 Macbook with a new Western Digital hard drive (regular style, not a solid-state drive). Cloning the drive with Carbon Copy Cloner seems to have worked fine (including the hidden Recovery partition) as it can be booted from in an external USB case on startup. The problem starts when I switched out the old drive and placed the WD inside. All of a sudden the Macbook won't boot up and I get the flashing folder icon instead. Switching the drives back and everything's fine; I can again boot up from either drive by holding the option key on startup.
    I've read that some older Macbook Pros have an issue with SATA II data transfer rates and need to be slowed down from 3.0 Gbps to SATA speeds of 1.5. Unfortunately, it according to WD's site you can't do that with WD's 2.5" drives, only their 3.5"s. I've tried it anyways with a jumper and it doesn't seem to work for me.
    I've also read elsewhere that there is a limit to the size of the drive that can be placed in: 500 GB. The drive I bought is 750 GB, so if this is true, that could be what the problem is. However, I can't find any mention of this supposed limitation anywhere on Apple's site. Does anyone have a reputable source for if this is true for this model of Macbook?
    Late 2008 13 inch Aluminum MacBook running Lion
    Western Digital Scorpio Blue (WD7500BPVT) 750GB SATA 5400 RPM 8MB Cache 2.5" Laptop Hard Disk (OEM)

    Hi Dave, I am having the same issues with a WD Blue. Thanks for your suggestions, but doesn't work for me.
    When the WD is in the MBP (15" 2010 Unibody), and I boot from an external HD, firstly the MPD says it can't recognise the WD and offers me the choice to Initialise, ignore or eject. I select initialise and disk utility reports that there is only a FAT partition of 58.2 GB on the WD. Err?
    When I put the original HD (an ST950032 500GB) back in the MBP and boot off it, all is fine. I then put the WD in an external exclosure, and the MBP sees it fine and Disk Utility correctly reports a MacOS Journalled GUID partition of 465.8GB.
    All the data is there (from doing an earlier clone). I just can't boot off it - weird.
    Surely there is a fix for this? Have tried all the SMC / PRAM reset stuff.
    The box even says that the WD Blue is 'Suitable for all operating systems (except XP) out of the box". How can you be sure that a drive you but will work in a MBP before you spend your money?
    Help? Glum

Maybe you are looking for