P35 neo cold boots twice when powered on or warm booted

Hi, I'm trying to figure out  what is happening with this board, when I turn on my computer it automatically shutsdown again for a sec or two and then comes back and boots ok. It does that also in a warm reboot.
I've seen similar issues in other forum threads, but it's unclear the reason, I found opinions saying it's a power supply issue, others a boot check in the chipset does, and also bios related issues. I tried it in every possible way, the only fixed configuration was:
- power cooler 500w psu
- msi p35 neo
- intel e4400 core 2 duo
with combinations of:
- memory
         - ocz ddr2 800 system elite (4 sticks 1gb each)
         - single ocz 1gb stick
         - two sticks
         - no memory
- video
         - pcie msi nvidia 6200tc
         - old trident pci graphics card
         - no grachips card at all
- hard disk
         - western digital 80gb sata2
         - no disk
Also tried all the BIOS settings available to be enabled/disabled, hopelessly lost some more time with bios rev. 1.2, (other tests where with rev 1.0)
The board is stable once it's up and running, but it's the first time I own a computer that has that strange behaviour and I don't know if I should return it or it is normal.
Can someone please help me understand what's going on and point me to a solution?
Thanks,
Sebastian.

Quote
what should i do...
First of all: Start your own topic. 
Quote
.i updated the bios from live update 3 utility
You should not use MSI Live Update to update your BIOS.  That is very risky.  Next time, use this tool instead:
>>Use the MSI HQ Forum USB flasher<<
That is in your own best interest, believe me. 

Similar Messages

  • P35 Neo Combo, boot problem? [FIXED]

    ** PROBLEM SOLVED - Tech support told we that if there was any way to update the BIOS to version 1.3 then I should do that. I found a way and after that everything have been running smoothly.
    I would like to thank everyone that helped me in here and hope that my experience and the solution might come in handy to someone else. **
    **This thread have been updated with more information and an alteration of the story as my experience with the board/BIOS grew larger, and some information was given to me by at kind person in this thread**
    Hello everyone. 
    Some days ago I got some new hardware and put it all together but I ran into a big problem.
    Specs of the new machine:
    Case: Arctic Cooling T2 Pro, Miditower, 500W
    Psu name: AX-500F, specs:
    +12v: 14 A (15 A peak)
    +12v2: 16 A (19 A peak)
    +5v: 25 A
    +2.3v: 30 A
    -12v: 0.5 A
    +5vSB: 2.0 A (3.0 A peak)
    This information is a direct quote from Artic Cooling's homepage:
    Power Supply
    The AX-500F is a power supply optimized for high end PC's and complies with Intel's ATX12V version 2.0. The continuous output power fulfils gaming system requirements based o­n multiple VGA boards.
    The AX-500F was tested with the following configurations:
    AMD Athlon FX-62 CPU
    2 GB Ram
    2x ATI X1950 XTX (Cross Fire)
    Intel Core 2 Extreme CPU
    2 GB Ram
    2x NVIDIA 7950 Gx2
    I also did try booting with a more powerful PSU but still no luck, and from what I can see then this one should be powerful enough
    Mobo: MSI P35-NEO-Combo-F, Intel P35, Ver. 1.0, BIOS ver. 1.2
    CPU: Intel Core 2 Duo E6750, BOX
    Ram: Corsair TWIN2X2048-6400C4, 2x1024MB 2.1v
    Graphics card: Inno3D GeForce 8800GTS, 320MB, PCI-E
    CD-rom: Lite-On DVD/CD
    HDD: Western Digital Raptor 74GB
    OS: Windows XP 32bit
    When I turned it on for the first time nothing happend, no picture no error sounds although I could see and hear that the computer was on. I turned it off and then on again, nothing, I turned it off and then on again and something happend.
    I got a red text message saying that my overclocking attempt was unsuccessful, which I found pretty odd cause this was the first time the computer was on. I have now been informed that it's a fail safe build into the BIOS to prevent a melt down if you overclock it too hard, which is kinda smart. I then had the option to go into the BIOS, so I looked at every setting to see if things were OK and if it was somehow overclocked or had some wrong settings.. Everything looked and still looks alright when I save and exit. When I do save and exit, be it with the settings I think is okay, the fail safe or optimized settings then the screen just goes black.
    So now for the 'clearing the CMOS' part When I reset the CMOS with the jumper I can get further than the error message about overclocking. I get two options:
    1. To enter BIOS setup to configure the bios.
    2. To automatically load some default settings and continue booting.
    First I tried option 1, after doing a save and exit the screen went black again, got the overclocking message and had to clear the CMOS one more time.
    Then I choose option 2, windows started to load, I got into safe mode and windows started to find all the new hardware and so on. When that was done I was kinda forced to reboot, screen went back and yes you guessed it... I had to clear the CMOS and choose options 2. I got as far as getting into windows and installed some of the stuff from the CD-rom's that came with the motherboard, again I was doomed to reboot and clear the CMOS. Once again option 2 needed to be selected to get the system up and running, and I got as far as to the "Want to activate windows" option, and couldn't do that cause the network card was not installed so I had no internet connectivity. Apparently if windows detect too much hardware being replaced then the activation thing pops up, and I later learned that I can't activate my windows anymore cause I used my activation quota and I have to get a new key
    What I learned from my brief time in windows normal mode:
    Everything seemed to work nicely, and freaking fast too....swiiing!
    2gb of ram was detected, running dual channel and at the desired voltage.
    The CPU was running at normal speed and voltage.
    All in all everything seemed normal until I rebooted.
    The only thing I can conclude is that something goes horribly wrong when I clear the CMOS, load some default settings and then reboot. I have seen that I am able to get into the system with my current hardware, but only after a CMOS clear, so what the heck is wrong, what goes wrong after the reboot?
    And this is as far as I can get with my own knowledge of computers :(
    So now I hope to go that I can get some help from some of you guys, any thoughts on this or anyone know of such a problem and maybe know a solution?
    If I missed some information you guys need to solve this puzzle then just ask.
    On a side note, if I somehow get the chance to flash my BIOS to version 1.3 in hope that if will solve my problem, then will it erase my chances to send it in for RMA and get a new board? Do I break any rules by doing that?
    Best Regards
    Mads, Denmark

    Quote from: Maesus on 24-August-07, 23:29:25
    ok, when you turn it off and on and off and on, the BIOS will think it's an overclocking failure event, and hence display the overclock error message.
    usually this is due to the memory settings was set incorrectly (by the BIOS itself). You may need to manually change the memory settings and see if that helps. And, please make sure that your BIOS can support FSB1333 processor like E6750 out of the box. If not, try flashing to the latest BIOS.
    Hello and thanks for the quick anwser.
    I did check if memory/cpu settings were okay and the seem to be on the right defaut setting. I save and exit and the screen just goes black. I forgot to add the motherboard and BIOS versions but they are there now: Mobo: MSI P35-NEO-Combo-F, Intel P35, Ver. 1.0, BIOS ver. 1.2
    I don't see how I will be able to flash the bios when I can't get into windows and do it, and there is no way else for me to do it. If it was the case that the BIOS didn't support FSB1333, then I would never have gotten as far as getting into windows and getting the activation message would I?

  • [SOLVED] P35 Neo - Slow boot

    Hi,
    On a P35 Neo, the computer takes a lot of time to boot (around 2mn to see the windows logo indicating that the OS is starting). When the windows logo appears, the start up times is normal.
    It seems that it takes times to check devices then it's ok
    I've checked my devices (hdd, mermory ..) no problems detected. May be a bios config.
    Any help is welcome
    Thanks
    Config
    Motherboard: MSI P35 Neo MS-7360
    CPU: Core2 E7400
    Memory: 2x 2Gb Corsair XMS2
    PSU: Cosair TX750W
    Video: MSI N260GTX (GForce GTX 260)
    Drives: WD HDD 160Gb SATA, Samsung DVD player SATA

    2 minutes is a lot of time for window to appear??
    are memories in slot1 and slot3 ??
    what is your bios latest or the first bios.
    if memories in slot1&3 then go into bios then default setting click on it then click yes then save and exit then test.
    if prob still persist then as wonka has suggested strip to bear, test,  then add one hardware then test start time..and so on,  from this you should be able to identify the hardware which is causing it.
    if prob persist your last option is flashing bios safely

  • MSI K8T-NEO won't post from a cold boot

    Alrighty here is my strange problem.  I have my system connected to a surge protector powerstip.  When I power my machine down I also shut off the powerstrip which cuts wall power off from the machine.  When I turn the power back on the and then fire up the computer every single time it will not POST on the first try.  The drive lights cd-roms come on but the HD's never start.  So I hold the power button in for 6 seconds, then hit it a second time, and it boots every time.  Shutting down and restarting is no problem, so long as the power is never disconnected from the system.
    Here is my configuration
    MSI K8T NEO Bios version 1.2
    Athlon 64 3200+ not overclocked
    1 512meg stick of Geil Ultra PC3200 slot 1
    1 512meg stick of Coarsair XMS3200 slot 2
    memory is running at 333mhz 2-3-3-7 all setting are set to auto
    Radeon 9500 in the AGP slot
    Sound Blaster Audigy
    Promise 100 TX4 Raid controller
    2 WD 80 gig SE HD's connected to promise controller
    1 Pioneer PD-115 16X DVD drive
    1 Liteon 411-s I believe 4x DVD Writer
    1 Zip Drive
    Using AMD boxed CPU fan
    Powered by an Antec true 430 +3.3V 28A +5V 36A +12V 20A
    According to core center +3.3 is at 3.31V, +5V is at 5.03V, +12V is at 11.76V
    So anyway its prime stable etc.  But when ever the system has been powered off, and unplugged the first time I power on it always fails to post with the d-link indicator lights indicating a CPU failure.  Hold down the power button and it reboots.  Power the machine off, but don't disconnect wall power powers back on just fine.
    This is strange, since I use the surge protector to turn off speakers, etc!  Its also annoying, I used to have a MSI K7D-L Master 2xXP CPU's with the same hardware witht eh exception of the Geil RAM, and of course cpu, and mobo and never had any problems with a cold boot.  any suggestions?

    Yeah I tried having only one stick of ram in the machine, and it hangs on a cold boot when its been unplugged/or powersupply switched off.  Reboot again and no problems.  I tried just having the geil installed, and the corsair stick installed same problem.  I have ordered a second Geil Ultra PC3200 stick so I'll have matched sticks and will be able to run at 400mhz FSB.  The lack of a manual memory speed setting overide in the bios is frustrating.  Yes I know the speed is more or less set by the CPU but there must be some override mechinism if you can slow it down....  
    I have also tried with just a video card installed, and one stick of ram to see if the problem would go away.  No GO.  One thing to mention is I had a Radeon 9700pro that I got from new egg refurbed that I had to send back becasue the card would not power on when the system was booted, unless you disconnected the power lead got the warning message, and then powered off and reconnected the power lead.  Possibly this card may have damaged something else?  OR the mobo was bad and damaged the card?  The mobo was new, the ram (geil), CPU, and 9700pro were all refurbs.  Everything else was from a previous dual processor system and was working fine.
    Both of the Western digitals are set as masters and each are on their own seperate ide channels.  The Promise FastTrack100 TX4, has 4 IDE channels and the HD's are connect to channel 1 and channel 2 on the FastTrack controller.
    Specifically what happens is if the power has been off, I turn the power on, hit the power button.  Lights come on, the cd-rom drives lights start blinking, fans come on, and I hear this kinda of poping sound out of the speakers like the kind of sound you get when you first power on the machine but it happens a second time about 2 seconds after powering on the machine, and it just sits in this kind of hung up state, hitting the reset button does nothing.  Then I power off power back on and it POSTS, and back to normal.  So long as the system is never disconnected from the power source while it is off, it will power back on the first time.  This is really strange I've never had a system do this before.  I'm beginning to wonder if I just have a bad/faulty board and ought to RMA it?

  • P35 Neo does not boot

    Hi,
    I have just bought a P35 neo F and a Code 2 Duo E6550 processor.
    When I switch the power on, the cpu fan starts and stop and then start again which looks OK for this motherboard - My problem is that the system does not boot after this - I have tried different combinations (with or without memory, with or without hard drive, with or without graphic card, I have tried 2 different graphic cards, 2 different power supply... no result - Could someone help me ?
    My config :
    MB P35 Neo F
    Proc Intel core 2 duo E6550
    Power supply Enermax extreme power 500W
    Graphic card Asus EN 8600 GTS
    Thanks

    Quote from: gatebill on 25-January-08, 22:06:15
    I've tried a Kingston PC2 6400 CL5 - the system still do not boot up - I can see the keybord blinking at the beginning of the boot process but the screen noes not receive any signal - I get a bip after about 20 sec and another one again after 20 sec.
    The processor or the mother board must be faulty...but how to know which  ?
    MSI P35 Neo2-FIR (bios v1.5)
    Intel E2180
    Tuniq Tower 120
    2 x 1GB Ballistix PC2-8500
    XFX GeForce 8600GT
    Maxtor 80GB
    Seagate 250 GB
    Advance 550 watt PSU
    I just finished building this rig, and had exactly the same "no boot" issue using Ballistix RAM. The board powered up, then it did the auto shutdown thing which is normal, and then it started up for real, the diagnostic LEDs on the mobo light up, the CPU fan spins, I get a single beep but then just a blank screen, no POST screen, can't enter the BIOS
    I tried a minimal build outside the case using just the graphics card, monitor, keyboard, and a single stick of Ballistix RAM in four different slots, re-setting the CMOS at each attempt, But still no POST
    I was advised the Ballistix may be the problem as they're rated at 2.2v and the MSI board sets 1.8v until you change the voltages in BIOS, so I ordered 2 sticks Kingston Value RAM  667MHz rated at 1.8v, Inserted a single stick then powered up, but still no POST, Inserted the second stick and the board fired up!  I needed both sticks inserted to boot,  glad I ordered 2 sticks of Kingston instead of one, I'm keeping them as a backup if the Ballistix fail. Inserted the Ballistix and they're running fine @ 1160 MHz  CAS 5: 5: 5: 15: 2T  2.3v

  • Ms-7360 P35 Neo wo't boot with full 8GB DDR2

    Let's begin with me stating my problem:
    I recently bought these ddr2 modules: http://www.ocztechnology.com/products/memory/ocz_ddr2_pc2_6400_vista_performance_gold_4gb_dual_channel (2x2GB OCZ Gold PC2-6400)
    I already had 2x2gb Patriot ddr2 (http://www.patriotmemory.com/products/detailp.jsp?prodline=5&catid=2&prodgroupid=38&id=658&type=1) installed on my mainboard (ms-7360 P35 Neo).
    Now i can't boot Windows 7 64-bit with the full 8GB memory, it gives a blue screen or just keeps looping the boot sequence. If i use 6 GB my rig works, but is still a bit unstable.
    I have tried placing the new memory modules in another rig and they work. I also tried swapping the modules:
    A1 + B1: Patriot memory
    A2 + B2: OCZ memory         ---> doesn't work, turn out in a blue screen
    A1 + B1: OCZ memory
    A2 + B2: Patriot memory  --> this doesn't work, because i it has something to do with BIOS remembering previous setup.
    A1 + B1: Patriot Memory
    A2: OCZ memory module 1 --> works, but when i was loading files to a separate hdd i got the blue screen.
    A1 + B1: Patriot Memory
    A2: OCZ memory module 2 --> works too, but like above it's only 6GB and i want the full 8GB.
    A1 + B1: Patriot Memory
    B2: OCZ memory module 1 --> works
    A1 + B1:Patriot Memory
    B2: OCZ memory module 2 --> works
    Oh, i almost forgot to say this: During the boot i also see that, when all 4 slots are full, i see 8GB
    Now if anyone can help me get the full 8GB working, I'd be a very happy person

     Get all 4 matching modules. It works when you have 3 of them installed because they would be in single channel mode and single channel can tolerate miss-matched RAM much better than dual channel can. 2.2V Patriot 4-4-4-12, 1.8V OCZ    CL 5-5-5-18

  • P35 Neo: Freezes on Boot Screen HELP!

    Hi, I need help.
    I took some of my old parts and bought some new ones to make a cheap computer for my dad.
    The mobo I used, used to be in my old pc, and ran great with an intel e8400 in it.
    I put together today:
    P35 Neo
    Intel e3400
    Corsair XMS2 2GB ( 2 X 1GB )
    Zotac 8400GS
    420 Watt psu
    I put everything together, tried both mem sticks, 1 at a time each slot, same outcome.
    It boots to the sceen asking to press del or tab, and then freezes. The cpu fan slows down a bit, when it freezes.
    The BIOS chip thinggy says something like a7360 ms 160, but i dont think the bios matters because i used to run a e8400 on this exact motherboard
    PLEASE HELP THANKS A LOT!

     Celeron E3400 is not in the supported CPU list for P35 Neo (G33 Neo) with 1.x BIOS. G33 is the correct CPU list for your P35 MB with 1.x BIOS.
          http://www.msi.com/product/mb/G33-Neo.html#/?div=CPUSupport
     You can ask MSI tech support.
          >> How to contact MSI <<

  • MSI K8t NEO + Audigy Boot Problem only when power is unplugged on the PSU

    I ran into a really weird problem today.
    I switched the ps off by reaching back and pressing the button. I repress the button to power on the ps, then I click on the button in the fron of the case to power up the machine. System keeps rebooting itself every 1 sec. Bracket shows 4 red lights. In the manual, it says it means bad cpu. I remove the audigy and it boots fine. I install the audigy, 4 red lights.
    So, This time instead of turning the puter off by using the button on ps. I used the button on the case by holding it down for 5 seconds. I reboot and puter boots normally.
    So the problem is, if i turn the puter off by using the button on the PS and with audigy in the syste. Nothing on screen, and puter keeps rebooting itself every one second. Solution is to turn the puter off by using the button on the case.
    Has anyone ran into this problem? I have never had this kind of problem. It is really weird. Any feedback is apreciated.
    Oh and it is only with audigy. I tested this with original live, and also other PCI cards like nic, and another cheap sound card. Non of these cards showed this problem.

    Cavemankr!
    I never knew you could shut down the computer by holding down the start button for 5 seconds.... well I've never really had the need to...until I got this K8T Neo job. I wondered why it wouldn't turn off when I just pushed it. I've been using the PSU switch with these problems.
    Yep! She booted right up. Audigy back in action. I also realized I had my PC hooked straight in the wall (while checking to see if my surge protector was working this weekend), so turning off the surge protector wasn't cutting power to the cheapo PSU.
    So put me in your camp!
    I'll just plug the PC straight into the UPS and keep power fed to the Enermax. I hope that was the cause of my keyboard/mouse cold boot problem also.
    I'll assume the cheapo PSU will behave similarly. I don't really want to go through the swap again.  
    I wonder why that happens!
    Buddy
    Vor uns liegt ein weites tal
    Die sonne scheint mit glitzerstrahl

  • P35 Neo ram problems. Does not boot with 4 sticks

    Greetings!
    This thread is little related to: https://forum-en.msi.com/index.php?topic=110095.0
    Okey so I bought this rig last friday(will post specs later). 4x 1gb ram sticks, shows up as 3.3gb. Was gona install 64-bit Vista today, but got some problems.
    I left my computer on during night just to check if it runs fine. I wake up around 6am, turn power on to my monitor. Screensaver, move mouse, desktop and BOOM: Bluescreen(something about memory). Ok so I shutdown my comp, try to reboot got no signal. Removed 2 ram sticks(A2,B2) and yey it works. I plug them back in and again nothing. I test them 1 by 1 on both of the free slots, no problems detected.
    Why won't my P35 Neo boot with 4 gigs of ram? And why did it work for 2days? :P
    My guess is that the bios is still not ready yet(using 1.2v).
    Specs: OCZ 700W GameXStream, P35 Neo-FI, C2D E6750, 4X PQI 1024Mb DDR800Mhz, Leadtek 8800 Gtx

    Quote from: NovJoe on 07-August-07, 10:18:34
    If I understand correctly, you are saying that you can install Vista and XP to the system but not able to boot into the OS'es when you have 4GB of RAMs installed?
    I would recommend you to test the RAMs with Memtest86.
    Yes, I could install Vista and XP just fine. Also at first I could boot them with 4gigs just fine. Now my system won't POST with 4 gigs.
    I've tested each one of the ram sticks and they are error free.

  • Cant boot P35 Neo-F

    Hey..
    I just got my new system. MSI P35 Neo F, Intel C2D E8400 and 2x 2GB ram.
    But when I boot up with all 4GB ram installet the system wont boot, but when I only use 2 GB the system works perfectly.
    Someone got an Idea?
    Best Regards

    Quote
    2x Corsair XMS2 extreme 2GB
    I mentioned the serial number because that really helps to ID your memory.  Please find your modules on the Corsair product site and post the link to the datasheet.
    http://www.corsairmemory.com/

  • P35 Neo FR wont boot with 1066 Ram

    Hi Guys,
    I have a problem with a new build.  The specs are
    P35 Neo FR
    E8400 (not overclocked)
    2 gb Crucial Balistax tracer 1066 Ram
    XFX 7900GS card
    450W PSU
    It will boot and I have been into windows to which all seems fine, however I have an issue.
    1. The BIOS and CPU-Z are showing my ram at 667.  I have manually adjusted it to 5-5-5-15 and set the divider so it should be running 1066.  However it wont boot and goes into the re-boot over and over and over and over and over again "mode".  This can only be rectified by re-setting the CMOS and then it will boot with its origional 4-4-4-24 timing @ 667.  I have checked the voltages and they make no difference.  It will only boot when the LED's on both ram sticks are lighting up on first power up.  Ram has been tested in another PC and doesnt seem an issue. 
    Bios is 1.5 I think.  Should I flash and go to 1.8?
    I will also try the Mobo, PSU, HD and GPU without anything else attatched to see if there is a problem
    Also, 1 stick of ram at a time to see if thats causing an issue.
    I would appreciate any suggestions 
    Thanks

    Quote from: Jack the Newbie on 19-March-08, 22:28:13
    Which FSB/Memory Ratio did you choose in BIOS?
    Does it work, if you choose the divider for DDR2-800 MHz?
    What is the memory voltage recommended for these modules @1066 MHz effective speed?
    Did you try with one stick of RAM only?
    Thanks for the quick reply
    I think the divider was 1.1-6?  I will confirm in a couple of hours once I am home. It works at 1-1 but the speed was 400mhz.  It also ran at 667. Whatever that divider was.
    I am going to try the one memory module test tonight and I will also report on that and the DDR800 settings.
    http://www.crucial.com/uk/store/partspecs.aspx?IMODULE=BL2KIT12864AL1065  Is my ram and its rated at 2.2V
    Thanks in advance and I will update in the next few hours.

  • P35 NEO-2 FR won't boot. One beep every few seconds.

    Hello, I hope someone can help me
    Out of the nothing my computer crashed. There was a blue screen, but only for a split second, so I couldn’t get any information from that. After I tried to turn it back on I only got a black screen.
    Messages from my PC:
    One beep every few seconds. -- Means: DRAM refresh failure.
    The LEDs on the board have the combination red-red-green-green. -- Means: Decompressing BIOS Image to RAM for fast booting.
    Obviously I tried another RAM module. But it didn’t help. I don’t know what I should do, because I can’t even get to the BIOS. The screen just stays black.
    PS: I didn’t OC or try to flash a new Bios version.
    My system:
    P35 NEO-2 FR, BIOS v. 1.8, S/N: 601-7345-100B0805092463
    Intel Q9300
    G.Skill 2 GB DDR2 PC2-6400 CL5-5-5-15 (also tried brand new Corsair XMS2 DDR2 800 MHz CL5-5-5-18)
    MSI N460GTX Hawk
    beQuit Straight Power 600W

    Okay, please have a look at this document:
    http://www.ami.com/support/doc/AMIBIOS8_Checkpoint_and_Beep_Code_List_PUB.pdf
    As you can see, there are two main routines going on after you hit the power-on button:
    1. Bootblock Initialization
    __ and __
    2. POST Code
    Your problem description ...
    Quote
    The LEDs on the board have the combination red-red-green-green. -- Means: Decompressing BIOS Image to RAM for fast booting.
    ... indicates that your system halts in the first of the two main routines I just mentioned. To be more precise, it hangs at Bootblock Initialization Checkpoint D5, which is defined as follows:
    Quote
    Bootblock code is copied from ROM to lower system memory and control is given to it. BIOS now executes out of RAM. Copies compressed boot block code to memory in right segments. Copies BIOS from ROM to RAM for faster access. Performs main BIOS checksum and updates recovery status accordingly.
    In the last two phases of this checkpoint:
    Quote
    Copies BIOS from ROM to RAM for faster access. Performs main BIOS checksum and updates recovery status accordingly.
    The actual BIOS Code is copied into RAM and checked for integrity. When BIOS corruption is detected (=wrong BIOS checksum), the system will automatically jump into BIOS Recovery Mode (which is a sub-routine of the Bootblock Initialization routine).
    Now, this brings us to the actual meaning of the beep(s) you hear:
    Quote
    One beep every few seconds. -- Means: DRAM refresh failure.
    The BIOS Recovery mode (which is not part of the actual P.O.S.T. Routine, but a sub-routine of the Bootblick Intialization Routine) has its own set of Beep Code definitions which are described on page 15 of the document I linked you to:
    Quote
    Boot Block Beep Codes
    Number of Beeps -- Description
    1 -- No media present. (Insert diskette in floppy drive A:)
    2 -- ‘AMIBOOT.ROM’ file not found in root directory of diskette in A:
    3 -- Insert next diskette if multiple diskettes are used for recovery
    4 -- Flash Programming successful
    5 -- File read error
    7 -- No Flash EPROM detected
    10 -- Flash Erase error
    11 -- Flash Program error
    12 --‘AMIBOOT.ROM’ file size error
    13 -- BIOS ROM image mismatch (file layout does not match image present in flash device)
    Consequently, the meaning of that single beep, that repeats every few settings is not "DRAM refresh failure" (this would be its meaning in the P.O.S.T. Routine, but we are looking at the Recovery Routine), but it actually means:
    Quote
    1 -- No media present. (Insert diskette in floppy drive A:)
    What you have to do is this:
    1. Hook up an internal (!!) floppy drive to your mainboard
    2. Prepare an AMI BIOS Recovery disk:
    --> Download the latest BIOS Archive for your board from the product site
    --> Extract the actual BIOS File and rename it to AMIBOOT.ROM
    --> Copy the renamed BIOS File to an empty & formated floppy disk
    3. Put the disk that contains the AMIBOOT.ROM file into the internal floppy drive that you connected to the mainboard.
    4. Pray that the system finds the disk, reads the file on it and performs a recovery flash

  • On my PC, iTunes 11.0.3.42 causes it to hang when attempting to view a .MOV (1.6GB) requiring a cold boot. What could be causing this?

    On my PC running windows XP Service Pack 3, iTunes 11.0.3.42 causes it to hang when attempting to view a .MOV (1.6 GB) requiring a cold boot. What could be causing this? Corrupted .MOV? Too little RAM? It successfully plays a 162 MB .MOV.

    Hello David,
    Thank you for providing all that information about the iTunes issue you are experiencing.  We would first want to rule out any software issues before we can determine if it has to do with RAM.  I found an article that will help you isolate and troubleshoot software issues that could be causing iTunes to behave this way:
    iTunes for Windows XP: Troubleshooting unexpected quits, freezes, or launch issues
    http://support.apple.com/kb/TS1421
    I hope this helps you get back on track with watching movies in iTunes! 
    Best,
    Sheila M.

  • Reboot when cold booting

    Hi.
    I encrypted my MBP harddrive with the new FileVault feature. Recently my MBP developed an issue where it would hang a while on the spinner when cold booting, then just reboot - and then boot just fine.
    This requires me to type in my decryption password two times. Doesn't seem healthy. I tried restoring file permissions from Disk Utility but this didn't help.
    Do you know what is causing this and perhaps how I could fix it?
    Jorijn

    It seems to be a problem with paralles desktop.
    http://www.cultofmac.com/113981/parallels-desktop-7-update-fixes-file-fault-full -disk-encryption-problems-get-it-now/
    Chris

  • P965 platinium - Boot squence is lost when mashine is cold booted

    Hi, I hope someone can help me out here...
    When I cold boot my PC the bootsequence is lost and set to 1: floppy, 2: sata disk 1 in raid 5, 3: sata disk 2 in raid 5.
    Now I don't have a floppy and the raid array is not a system disk. Then I have to re-enter my boot seq. to: 1: P0 500 GB system disk,2: None, 3: None) and save with F10. - but after a new cold-boot my sequence is lost again...
    Please help me
    My System:
    MSI P965 platinium mother board, bios 1.6
    500 gb system disk with dual boot on sata 0, Vista and XP.
    3 250 gb disks to a raid 5 array on sata port 3,4 and 5.
    Pioneer DVD-R (IDE) on jmicron
    IN bios:
    Onboard RAID Controller: is set to [IDE] <- this is the jmicron (I think) to my Pioneer DVD-R drive.
    under On-chip ATA devices ->
    PCI IDE BusMaser:       is set to [Enabled]
    configure SATA#1 as : is set to [ACHI]
    The raid array works fine in Vista and XP. (Both system was installed on sata disk on port 0 with ACHI enabled.

    Quote from: aabenraa on 20-September-07, 14:54:46
    I try and add a USB stick, then remove it , and the cold-boot. Hope it works.
    Did it work? Actually, I wasn't suggesting this as a workaround. I was only telling you what I sometimes (inadvertently, of course) do to make the BIOS overwrite my normal boot sequence: boot with a usb stick plugged in.

Maybe you are looking for