MSI MegaPC 651 - System Won't Boot (Long Beep)

When I attempt to power on the PC I recieve a continuous beep signal.
The Beep is approx. 8 seconds long, followed by 5 seconds of silence. The signal keeps repeating itself until I turn off the power.
Obviously, the system is not passing POST so I can't get any video or access the bios.
The cpu is a P4 2.4ghz 533fsb.
The memory is a single 512mb DDR 333 chip.
I've plugged the CPU into a second motherboard and it appears to work fine. I've tested the ram in the second mother board and it appears to work fine.
I tried a stick of DDR400 ram from a known-working system and that did not seem to correct the issue.
One thing I noticed in another similar thread is someone mentioned that i should make sure my CPU fan is plugged in.
~ My Fan is plugged in (came with MSI Barebone), but it doesn't spin. I've tried plugging in the fan that came with my CPU and that one doesn't spin either. My Intel Board that i use for my desktop allows me to boot without a system fan plugged in, I've never heard of a mobo that doesn't. The system isn't even on long enough for the CPU to be over heating.
Please Advise.
-Josh

It is a memory issue. There is something weird about this motherboard...
I got the system working, and i couldn't figure out what i had done differently. I then installed windows.
I let it run for a few days until i realized that the RAM that was in there was the DDR 400 ram from my other desktop, instead of the DDR 333 that I had intended to use.
I took the DDR400 out, and put the DDR333 in and again.... BEEEEEEP. (8 seconds)
I put the DDR400 back in and still... BEEEEEEP. (8 seconds)
I know neither stick of RAM is bad because they have both been used successfully in my other desktop system upon the first try. Its like the MSI has some sort of connection problem in the memory bank, and I lucked out on one try and got all the connections to line up.
If anyone has any suggestions, please advise, because I'm back to square one again.

Similar Messages

Pb g4 won't boot - long beep?

Hi,
I mistakenly posted this message in the titanium folder, while it belongs here. So this is a repost - now in the correct forum.
My powerbook g4 (fw800 1.25Ghz 15") won't boot any more. Symptoms: after hitting the power button, it takes a while before it emits a long beep and flashes the sleep led a large number of times (I cannot count exactly how many times). This is different from the POST beeps mentioned on apple's web site: these beeps are shorter. This long beep also has nothing to do with the firmware upgrade procedures on other powerbook models.
When I remove RAM memory, it first beeps and flashes as already mentioned, and then, after a while, gives one short beep and two flashes (this indeed corresponds to the POST messages published by apple). Reseating RAM does not solve the long beep/boot problem.
I also tried the following: resetting pmu, resetting pram, without luck.
Then I opened it, and verified that all cables were seated correctly, unplugged the backup battery (which still has the correct voltage), reassembled everything, also without luck. With/without hard disk or optical drive: makes no difference. Also using it with either or both battery or AC power makes no difference.
Does anyone know what the long beep means? Is the logic board fried? Is there anything that I can try myself (I am somewhat experienced in fixing defective hardware in desktops and laptops). I probably have nothing to loose. I don't want to send it in for repair or spend money on a replacement board.
Thanks in advance
Patrick
powerbook g4 Mac OS X (10.4.8)

Wondering if your Light pulses accordingly with the beep?
The power on self-test resides in the ROM of the computer. This test runs whenever the computer is turned on after being fully shut down (the power-on self-test does not run if the computer is only restarted).
If a fault is detected during the test, you will not hear a normal startup chime. Instead, the system will beep as explained below. If you experience one of these beeps, you may call your Apple Authorized Service Provider for additional troubleshooting assistance.
1 beep = no RAM installed
2 beeps = incompatible RAM types
3 beeps = no good banks
4 beeps = no good boot images in the boot ROM (and/or bad sys config block)
5 beeps = processor is not usable
In addition to the beeps, on some computers the power LED will flash a corresponding number of times plus one. The LED will repeat the sequence after approximately a 5-second pause. The tones are only played once.
Note: In this case, a flash is considered to be 1/4 second or 250 ms or greater in length.
Joe

Powerbook g4 won't boot - long beep

Hi,
My powerbook g4 (fw800 1.25Ghz 15") won't boot any more. Symptoms: after hitting the power button, it takes a while before it emits a long beep and flashes the sleep led a large number of times (I cannot count exactly how many times). This is different from the POST beeps mentioned on apple's web site: these beeps are shorter. This long beep also has nothing to do with the firmware upgrade procedures on other powerbook models.
When I remove RAM memory, it first beeps and flashes as already mentioned, and then, after a while, gives one short beep and two flashes (this indeed corresponds to the POST messages published by apple). Reseating RAM does not solve the long beep/boot problem.
I also tried the following: resetting pmu, resetting pram, without luck.
Then I opened it, and verified that all cables were seated correctly, unplugged the backup battery (which still has the correct voltage), reassembled everything, also without luck. With/without hard disk or optical drive: makes no difference. Also using it with either or both battery or AC power makes no difference.
Does anyone know what the long beep means? Is the logic board fried? Is there anything that I can try myself (I am somewhat experienced in fixing defective hardware in desktops and laptops). I probably have nothing to loose. I don't want to send it in for repair or spend money on a replacement board.
Thanks in advance
Patrick
powerbook g4 Mac OS X (10.4.8)

Hi pwambacq,
Welcome to Apple Discussions.
You're much more likely to get the help you need in the Aluminum PB folder, which is what you own (this is the Titanium folder).
FWIW, you've tried most of what I can think of. Not sure if you've done this or not, but give it a try if you haven't: in case one of the RAM modules is bad, try just one module at a time, and try it in both slots.
Will it boot to the install disc?
If it's not RAM, HD, or connections, seems likely it's the LB.
Good luck.

MSI P965 Platinum, system won't boot only when ICH8R is in RAID

So I couldn't get my system to boot properly when I have the ICH8R in RAID 1 mode.
I have the boot drive on a single, non-raid Wester Digital 250gb Cavair HD on the ICH8R.
Installed XP Pro SP2 with the ICH8R in IDE mode. I installed in IDE mode beceause I was unable to install XP on my single drive when ICH8R was in RAID mode. I installed XP in IDE mode, did all driver updates, then put the ICH8R into RAID 1 mode for my other data drives and the system will post, start to boot and get to the Windows XP boot screen then the system just restarts before the boot completes. It does it in normal boot mode and safe mode as well.
With the ICH8R in IDE mode everything boots/runs fine.
The problem is, I need the 6 SATA RAID controllers on the ICH8R as I have 3 RAID1 arrays.
I've done all the updates to windows, motherboard bios, Highpoint RocketRaid bios update, tried every mode on the ICH8R, unplugged the Highpoint Rocket Raid, left it plugged in with no drives plugged in, disabled the Jmicron controller, everything I can think of.
Any help would be appreciated.
I did not do the windows floppy driver install for the ICH8R when I installed XP, but I have not had to do that in the past with the ICH7 on my old motherboard so I assumed I wouldn't here as I've been told it's just if you are installing windows on a RAID.
System:
MSI P965 Platinum
Intel Core 2 Duo 6400 CPU
(4) 1gb OCZ Gamer Extreme DDR2 PC6400 RAM
Windows XP SP2
High Point Rocket RAID 2300 PCI Express x1 RAID card
Asus nVIDIA GS7300 PCI Express Video card
Drives on ICH8R Controller:
Boot Drive: WD Cavair 250gb SATA2
DVD: Some sony 16x DVD - SATA
RAID1: (2) Seagate Barracuda 320gb SATA2 HD's (setup on previous motherboard on Intel ICH7 Controller)
(2) Seagate Barracuda 500gb SATA2 HD's
High Point Rocket RAID 2300 Controller:
(2) Seagate Barracuda 500gb SATA2 HD's

The problem that you are having has nothing to do with your mainboard.
Once you decide to install Windows XP SP2 when the ICH8R controller is in IDE mode, Windows will give you a bluescreen once you switch to RAID mode after the installation is done because it is to stupid to change to the proper driver. Consider this as normal behaviour.
You have basically three possibilities:
1. Reinstall XP with integrated SP2 and integrate the Intel ICH8R RAID drivers using a floppy disk
The latest drivers can be found here.
As I understand, you have already tried that. I if you don't feel like trying this again, have a look at this:
2. Slipstream Intel ICH8R SATA RAID drivers using NLITE or XP ISO BUILDER and try to install again with a self-made install CD that already includes the proper drivers (no floppy needed)
Use google to find one of the tools I mentioned. The procedure is free, perfectly legal and easy to do. Guides for this can be found all over the internet
3. Switching to RAID mode without having to re-install Windows XP
If you are still using your existing installation, that was done when the controller was in IDE mode, the follwing trick may work for you.
I posted a little guide on how to switch from IDE to AHCI mode without having to re-install XP. Have a look at the guide. The procedure is essentially the same for RAID. The only difference is the content of the REG-File that you have to make.
Guide: HOW TO switch from IDE to AHCI mode without having to reinstall Win XP (GUIDE)
Use the following content for the REG file instead of the one I put up in the above thread:
Quote
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2822&cc_0104]
"Service"="iaStor"
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor]
"Type"=dword:00000001
"Start"=dword:00000000
"Group"="SCSI miniport"
"ErrorControl"=dword:00000001
"ImagePath"="system32\\drivers\\iaStor.sys"
"tag"=dword:00000019
"DisplayName"="Intel RAID Controller"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters]
"queuePriorityEnable"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters\oromVersion]
"MajorVersion"=dword:00000006
"MinorVersion"=dword:00000000
"HotfixNumber"=dword:00000000
"BuildNumber"=dword:000003fe
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Enum]
"0"="PCI\\VEN_8086&DEV_2822&SUBSYS_B0001458&REV_02\\3&13c0b0c5&0&FA"
"Count"=dword:00000001
"NextInstance"=dword:00000001
The procedure works perfectly well in most cases (but not always).
I hope one of these three "methods" will work for you.

HELP NOW, PLEASE... MSI KM2M Combo-L Won't boot...!!!

HELP NOW, PLEASE... MSI KM2M Combo-L Won't boot...!!!
1) System was running fine...
2) Plugged in Split Mini-Jack from daughter card slot, to Line-In Minijack (where it was before)...
3) Sound from speakers blurted out loud...
4) Screen Froze up... no Ctl-Alt-Delete...
5) Power button... No response...
6) Reset Button... No Response...
7) Unplugged...
8) Try to power on...
RES:: No signal to monitor... LED Light on case turns on for about 10 seconds... CD-rom LED turns on as if BIOS... Then computer turns off... Fans Still working...
THOUGHTS:: Since the speakers are powered through the sound card (and were on at time), then when the Split Mini-Jack Dongle from daughter card, was plugged back into the Line-In Mini-jack port (where it was origionally)... Something shorted out... Any Ideas on what, exactly...?? Anyone heard of this before...?? I've never seen something like this before, and PC's have changed SOOO much over the last few years, that I'm kinda in the dark... But this is my girlfriend's computer, and she has a Mid-Term paper due on Monday (today being Saturday), and I'm in serious trouble right now... PLEASE HELP...!!!
The company that built the computer, doesn't seem to be in business anymore...!!!
(But the waranty sticker is still intact on the case, she doesn't want me to cut it unless the builder is definitely out of business...)
Basically... I'm Screwed...!!! I need your help...!!! SOON...!!!
THANK YOU SO MUCH IN ADVANCE...!!!
-RudeBoy
[email protected]

Danny perhaps better to delete this thread as there is another one already in here.
and the trouble shooting have already started there.

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)

MSI MegaPC 651 and two audio streams at the same time

Running Showshifter Time Shifting playback through 5.1 SPDIF, I get the sound of the live stream and the playback stream at the same time, any ideas on how to fix this?
Spec:
MSI MegaPC 651
P4 2.66GHz
512Mb DDR 333MHz
Seagate 120GB 7200rpm 8mb
LiteOn LDW-401S DVD+RW
MS8606M TV@nywhere
Windows XP Home
Showshifter v2.10.2235

Hi, I don't know this for a fact, but I suspect Video will, & Audiowill not.

P35 NEO-2 FR won't boot just beep beep every 10 seconds

What's wrong with my system, My system won't boot and I get a beep beep every 10 seconds. I was updating my bios using the approved USB flash drive procedure, all I got was a blinking cursor. I rebooted and now my computer won't boot. Is my motherboard dead? I have successfully used the bios flashing tool in the past.

Quote from: Hans Gruber on 11-March-08, 21:47:41
That's a good question.
Another problem has come up. I get CMOS bad check sum error. Press F1 for "can't remember" but it sends me to bios or F2 for default settings. Basically, I can't overclock because of this bad checksum error. Everything runs at stock speed. How do I fix this? On the bright side, I now have bios version 1.8
On a side note for Remus, I never made it to the load new bios screen. The cursor "_" was blinking non stop for several minutes. According to the admins, another user in Germany had the exact same problem that had.
Now, how do I fix the CMOS bad checksum error message?
"Another problem has come up. I get CMOS bad check sum error. Press F1 for "can't remember" but it sends me to bios or F2 for default settings. Basically, I can't overclock because of this bad checksum error. Everything runs at stock speed. How do I fix this? On the bright side, I now have bios version 1.8"
Enter in BIOS and "LOAD BIOS OPTIMIZED DEFAULTS", then "SAVE AND EXIT"
If you still get "CMOS bad checksum error" at next reboot, do this:
Login in your windows, then adjust USB key geometry. Do this:
Quote from: Jack the Newbie on 11-December-07, 05:41:45
Format your USB Flash Drive with >>this<< tool and then retry with "MSI Forum HQ USB Flashing Tool".
And update BIOS via Forum Tool (Re-flash with the same BIOS 1.8) will fix the problem.

MSI G31M3 V2 Motherboard - System won't boot unless Vid Card Reseated

Strange issue
MSI G31M3 V2 Motherboard Nvidia 8400gs graphics card
PC won't boot unless you reseat the video card. The box is not moving so this constant need to reseat is wierd. Is there an issue with this motherboard and Nvidia Cards?

Quote
Bios is loaded default - I haven't made any changes yet
The BIOS Version depends on the date the board left the factory. There is no default version. Please check your current Version for comparison.
Quote
480w PS Sunbeam I believe
Please check the sticker on it and write down the current limits (A) on all main voltage rails (12V, 5 V and 3.3V).
Have you tested a different video card at any point?

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.

MSI MegaPC 651 - System Won't Boot (Long Beep)

Similar Messages

Maybe you are looking for