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?

Similar Messages

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.

MSI K8N Neo3-F + MSI NX 6200LE-TD128E (PCX) - won't boot

Last time I bought 2 things:
Mobo - MSI K8N Neo3-F
Graphic Card - MSI NX 6200LE-TD128E with TC (PCX)
When I start PC I have seen only black screen and hear noise from PC Speaker
Mobo didn't see graphic card. To check graphic card I install it on second mobo (MSI K8N Neo4 Platinium) and when I start it,it work fine.
To check PCX slot on mobo i install second graphic card (MSI NX6600 GT) and when I start it, it work fine too.
Next step was mobo BIOS update but it nothing change and PC with K8N Neo3 + NX6200LE still won't boot.
Graphic card BIOS is newest.
Anyone have idea why K8N Neo3-F + NX6200LE doesn't want work together.
PS1. sorry for my english
PS2. K8N Neo3-F + Geforce MX 400 on AGP work fine.

Quote from: kakarocht on 05-February-06, 09:59:11
Gives more specs / details on your hardware especially on your PSU!! I'm worried that your psu problem as it need more power in order to boot up. Regards.
PROCESOR AMD SEMPRON 3000+
MSI K8N NEO3-F
ELIXIR 512MB DDR400
DVD-REC LITEON SHM-165P6S
WD CAVIAR 80GB (WD800JB)
MSI NX6200LE TC 128MB
I tried with 2 PSU
1- Modecone 400W
2- Chiftec 420W
With both don't boot
but mobo + NX6600GT with Modecon PSU work fine.

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)

MDD Won't boot unless CD tray is out

I've got a strange problem I've never seen before. I've got a dual gig MDD with combo drive that won't boot correctly unless the CD tray is out/ejected. If the tray is empty and closed, the system won't boot. If it's open, it does. Simple as that.
Can anyone point me to the solution? I don't know if I need a firmware update or what. I'm running 10.3.9. Norton's Systemworks 3.0 was run on it recently. I know that's a really bad idea, but I didn't do it. Just thinking it might be once cause of the problem.
Any help is appreciated.

OK, the Norton "thang" has been beaten to death...
I would not trust the uninstaller. Many uninstallers fail to remove EVERYTHING. Whenever I run an uninstaller, I perform a manual search for any remaining software "parts." Search for anything with "Norton," "Symantec," and "Works" in its name, and, if it is in any /library or /System/Library folder, (of the /Users/Home counterparts), and if its name remotely suggests a connection to the old System Works software, move it to your desktop (so you can put it back, if necessary). Then test for the malfunction.
Still, your drive drawer issue sure seems to suggest a hardware problem, such as a short, or something (I'm hardly an electrician.:)
If you're feeling brave, why not remove the Combo Drive. If the problem goes away, you can just replace that drive (with an upgrade?).

My Pavillion dv9700 notebook won't boot unless I first...

My Pavillion notebook won't boot unless I first boot to a cd. Here's the problem:
I have a dv9700 notebook. It wouldn't power up. A local shop said I needed a new motherboard. I ordered one and installed it. Now when I try to boot it gets to the part where the hard drive starts to spin and suddenly shuts down only to power up again and endlessly continue this loop. I have found that if I first boot to a bootable cd and then at the cd menu choose "Start Windows" instead of "Boot to cd" the computer will start Widows Vista and run normally.
I have reseated the RAM and tried only one card at a time and switched slots. The BIOS is up to date. I have booted on ac adapter only. Battery only. Tried another ac adapter.
The BIOS hard drive diagnostic fails, showing no hard drive installed. I have tried the hard drive in a USB enclosure. It read fine. I have tried another hard drive in this computer, still reboots over and over.
I can't figure out why I need to boot to a CD first then switch to Windows Vista on the hard drive.
Any ideas? Thanks

http://h30434.www3.hp.com/t5/Display-and-video/HP-Pavilion-dv9700-should-also-be-on-the-list-but-it-...

G4 MDD 1.25 Dual won't boot unless door is left open.

G4 MDD 1.25 Dual won't boot unless door is left open.
If you shut the door, the power switch light turns off and the computer freezes. I'm running a house fan over the board to keep it cool. It's not running hot, was not running hot.
Reset PMU, checked all cables for pinching, inspected the power switch cable, reseated power plug on main board, removed optical drive,
tested ram...
Otherwise the machine is rock solid. I'm stumped, but thinking power supply......
G4 MDD 1.25 Dual Mac OS X (10.4.9)

Had the exact same problem myself. After looking at this topic I noticed that one of the 5V cables was getting jammed in the bottom left hand corner of the door. The case had cut the insulation open and was obviously causing short circuit when the case closed. I put some tape around the damaged cable and tucked it inside the case. Problem solved!

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.

System won't boot with incorrect date/time

Hey, I setup a computer back home for VNC, however there was a power outage and now the BIOS has reset. Unfortunately it defaults the date to 2099 for some reason, anyway now the computer won't boot (I can't remember the exact error). Anyway the trouble is I can't access that computer now, and it has no monitor hooked up, is there anyway I can force a boot with just keyboard and without setting the correct date in the BIOS (no one with access to the computer could do this).
Appreciate any help.

You can try to just press F1.
I have a similar issue with my home server, the battery on the motherboard is dead so when the pc is powered off for a while it will not remember the clock. When trying to boot the system in such a case it spits out an error where it offers to "ignore" the error if you press F1.
In my case I need to wait until my pc beeps before pressing F1, basically you need to get past the BIOS stage.
With a bit of luck it might work for you too.
Also I hope you have some ntp service running on your system to make sure the date gets set correctly on your system on bootup.
Last edited by Neburski (2014-02-19 12:35:00)

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

[SOLVED] System won't boot (boots fine in fallback mode)

HI guys,
I just rebooted my headless server for the first time in a while, but it won't boot up.
I just sits at this screen:
Please note the system does boot using fallback mode.
(also, nothing to do with the latest boot problem - systemd-sysvcompat is installed and boots fine in fallback)
Last edited by kaipee (2013-05-18 21:23:13)

That screen shot looks like its booted to me? I see a login prompt

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

Similar Messages

Maybe you are looking for