P31 Neo-F V2 Overclock error - (constant) turn on / turn off

First excuse my english.
System was running fine since Sep. 2008. Today when i turned on the PC it started for a few secs and then powered down. I thought maybe the power went down for a split second (but it didn't). Turned on again and then i got the overclocking error in red. I never did overclock anything. Entered BIOS and loaded default (optimized settings) and somehow managed to get in windows. I turn up speedfan to see the temps and see the GPU 78C when it was 66 just yesterday (and that with 40C outside). Same with CPU 36C idle but it was 32-33 yesterday. Everything got hotter. So it probably is connected with that error and i search the net, read here and there on the topic land up here and read the topics of people with similar problems. And from here on the show begins.
I tried everything mentioned in the MSI video Clean CMOS and everything mentioned in the topics here with no luck. Between one hundred turn ons and turn offs i got the luck to actually power up the pc and enter BIOS to load the defaults, twice even managed to go back in windows but everything goes in the same loop over and over just after restart. I even tried the same method (as in the video) on the jumpers on JFSB 1-2 (dont know if i should've done that but...) with no results. It powered up instantly when i removed the memory modules but there was only a black hole on my screen.
I spent whole day trying this and that. Whenever i press the power button it just goes into TURN ON - TURN OFF endless cycle and thats it . Help is REALLY appreciated.
Tech Specs:
BIOS: v02.61 (probably)
MB: P31 Neo V2 (MS-7392 V 1.2) (red one)
CPU: Core 2 Duo E4600 2.4 GHz
RAM: 2X Sycron 1GB DDR II 800 MHz (DIMM 1 / DIMM 3)
GPU: Gigabyte / nVidia GeForce 8600 GT 256 MB
HDD: Samsung SATA 250 GB / 7200 RPM / 16 MB
PSU: Delux ATX-450W P4
OS: Win XP SP3 + all updates

I sent my pc on repair.
For anyone else that will (hopefully not) have this sort of problem it's the boards fault. If your MB isn't roasted i.e. doesn't show visible signs of damage (as in my case) then there might be a small possibility of getting it fixed (manually ripping the bios chip from the MB, reset/test it, replace it with another). If there isn't a viable fix it's time to dig for another MB.
(*BAD MSI* )

Similar Messages

  • C5550 printer gives error message "Turn off power, then on again" with all flashing lights

    This printer all of the sudden in constanty jamming up and gives error message "Turn off power, then on again", makes a lot of noise, and does it again.  Can't get any printing done!  I'm about to throw it out the window.  Any suggestions?

    Hey,
    I have been looking around trying to find the error that is associated with the blue blinking light above the memory card slots on the lower, right-hand side of the front of the printer. I have found that it is called the photo light; but, in regards to the flashing of it, I can't seem to find what that means.
    I recommend removing all memory cards from the slots, unplugging the power and leaving the printer unplugged for a while. Hopefully when you plug it all back in, everything will be ok. If not, let me know. In the meantime I'll keep looking and when I hear back from you I'll hopefully have some more information for you.
    Thanks for your detailed reply, have a great day, Look forward to hearing back from you.  
    I worked for HP.

  • Error 49 turn off and ON

    We are ussing two diffrent HP Laserjet Pro 1536 DNF at two diffrent location and both are connect through network .Yesterday sudenly got error same error at both printer (Error 49 turn off and On)Please suggest what to do now as both loaction user are unable to use printers

    Does the same thing happen if you disconnect the printer(s) from the network and power-cycle them? If you still get the erorr, it would indicate a problem with the printer(s) - perhaps unlikely to affect two at the same time? If you no longer get the error, this indicates that some system on your network is sending a 'bad' print job (or interrogative 'discovery' command) which the firmware in the device(s) can't handle (the firmware 'crashes', leading to reboot). Identifiying the source of such a job is not easy - you'll probably have to disconnect all systems, then reconnect them one by one until the fault reoccurs - then investigate what print jobs are queued on that system , or what else that system is sending.

  • Error when turning off Windows XP

    Hi
    I from chile, I don't speak much English but I will attempt
    when I turn off the PC he appears me the following error:
    DRIVER_IRQL_NOT_LESS_OR_EQUAL
    STOP: 0x000000D1 (0x00000048, 0x0000000A, 0x00000001, 0xF9F26D9C)
    CX88AUD.SYS - ADDRESS F9F26D9C BASE AT F9F26000, DATE STAMP 3DDD9283
    I already downloaded the it finishes version of the driver, but it doesn't pass anything  
    also the operating system one this updated
    please help.
    thank you

    I posted about this a long time ago. If you use the search engine here (provided it works currently) you'll see what I did.
    As mentioned, it's an IRQ issue. This card and it's drivers, do not like IRQ sharing in some configurations. Some share without problems, and other configurations simply wont tolerate it.

  • My phone was doing system update.  will not turn on now gives me a startup error and turns off

    my phone did a system update to lollipop now it will not turn on and gives me an error message 1740 and 1790 then turns off

    Oh boy! Like stef7 mentioned, I am also curious to know which device you are using so I can assist you and get the device working for you again.
    TamaraH_VZW
    Follow us on Twitter @VZWSupport
    If my response answered your question please click the "Correct Answer" button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!!

  • Panic error message, turn off and turn on by itself, restart error

    HELP PLEASE!!! I'm having this message on my macbook pro 15, 8 Gb ram, 1T HDD, intel i7 2.66ghz
    Interval Since Last Panic Report:  24194 sec
    Panics Since Last Report:          1
    Anonymous UUID:                    22EFFA86-8018-473F-A807-F5220883931C
    Thu Aug  8 02:14:24 2013
    panic(cpu 3 caller 0xffffff8008ca2448): "pmap_pv_remove(0xffffff80092bdb70,0xffffff811e949000,0x38f3b, 0x38f3b262, 0xfffffe9af0a11a48): empty hash"@/SourceCache/xnu/xnu-2050.7.9/osfmk/i386/pmap_internal.h:807
    Backtrace (CPU 3), Frame : Return Address
    0xffffff80f165b950 : 0xffffff8008c1d5f6
    0xffffff80f165b9c0 : 0xffffff8008ca2448
    0xffffff80f165ba80 : 0xffffff8008ca2b25
    0xffffff80f165bad0 : 0xffffff8008c669bc
    0xffffff80f165bbc0 : 0xffffff8008c6a890
    0xffffff80f165bbf0 : 0xffffff8008c82d07
    0xffffff80f165bc30 : 0xffffff8008d28928
    0xffffff80f165bd20 : 0xffffff8008efad7f
    0xffffff80f165bdb0 : 0xffffff8008d11cfd
    0xffffff80f165be00 : 0xffffff8008d07e49
    0xffffff80f165be50 : 0xffffff8008f76a5e
    0xffffff80f165bef0 : 0xffffff8008f76882
    0xffffff80f165bf50 : 0xffffff8008fe17da
    0xffffff80f165bfb0 : 0xffffff8008ccecf3
    BSD process name corresponding to current thread: coreservicesd
    Mac OS version:
    12A269
    Kernel version:
    Darwin Kernel Version 12.0.0: Sun Jun 24 23:00:16 PDT 2012; root:xnu-2050.7.9~1/RELEASE_X86_64
    Kernel UUID: 8D5F8EF3-9D12-384B-8070-EF2A49C45D24
    Kernel slide:     0x0000000008a00000
    Kernel text base: 0xffffff8008c00000
    System model name: MacBookPro6,2 (Mac-F22586C8)
    System uptime in nanoseconds: 33425535008
    last loaded kext at 31876873264: com.apple.driver.AudioAUUC     1.60 (addr 0xffffff7f8a607000, size 32768)
    loaded kexts:
    com.apple.driver.AudioAUUC     1.60
    com.apple.iokit.IOBluetoothSerialManager     4.0.9f8
    com.apple.driver.AppleTyMCEDriver     1.0.2d2
    com.apple.driver.AGPM     100.12.69
    com.apple.filesystems.autofs     3.0
    com.apple.driver.AppleMikeyHIDDriver     122
    com.apple.driver.AppleHDAHardwareConfigDriver     2.3.0f2
    com.apple.driver.AppleHDA     2.3.0f2
    com.apple.iokit.IOBluetoothUSBDFU     4.0.9f8
    com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport     4.0.9f8
    com.apple.driver.AppleBacklight     170.2.3
    com.apple.driver.AppleIntelHDGraphics     8.0.0
    com.apple.driver.AppleIntelHDGraphicsFB     8.0.0
    com.apple.iokit.IOUserEthernet     1.0.0d1
    com.apple.driver.AppleMikeyDriver     2.3.0f2
    com.apple.driver.AppleUpstreamUserClient     3.5.10
    com.apple.driver.AppleMCCSControl     1.0.33
    com.apple.GeForce     8.0.0
    com.apple.Dont_Steal_Mac_OS_X     7.0.0
    com.apple.driver.AppleSMCPDRC     1.0.0
    com.apple.driver.AppleSMCLMU     2.0.2d0
    com.apple.driver.AppleMuxControl     3.2.6
    com.apple.driver.ApplePolicyControl     3.2.6
    com.apple.driver.AppleLPC     1.6.0
    com.apple.driver.ACPI_SMC_PlatformPlugin     1.0.0
    com.apple.driver.SMCMotionSensor     3.0.2d6
    com.apple.driver.AppleUSBTCButtons     235.4
    com.apple.driver.AppleUSBCardReader     3.1.0
    com.apple.driver.AppleUSBTCKeyEventDriver     235.4
    com.apple.driver.AppleIRController     320.15
    com.apple.driver.AppleUSBTCKeyboard     235.4
    com.apple.driver.AppleFileSystemDriver     3.0.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless     1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib     1.0.0d1
    com.apple.BootCache     34
    com.apple.iokit.SCSITaskUserClient     3.5.1
    com.apple.driver.XsanFilter     404
    com.apple.iokit.IOAHCIBlockStorage     2.2.0
    com.apple.driver.AppleUSBHub     5.1.6
    com.apple.driver.AirPort.Brcm4331     600.15.20
    com.apple.iokit.AppleBCM5701Ethernet     3.2.5b3
    com.apple.driver.AppleFWOHCI     4.9.5
    com.apple.driver.AppleAHCIPort     2.4.0
    com.apple.driver.AppleUSBUHCI     5.1.5
    com.apple.driver.AppleUSBEHCI     5.1.5
    com.apple.driver.AppleEFINVRAM     1.6.1
    com.apple.driver.AppleSmartBatteryManager     161.0.0
    com.apple.driver.AppleACPIButtons     1.6
    com.apple.driver.AppleRTC     1.5
    com.apple.driver.AppleHPET     1.7
    com.apple.driver.AppleSMBIOS     1.9
    com.apple.driver.AppleACPIEC     1.6
    com.apple.driver.AppleAPIC     1.6
    com.apple.driver.AppleIntelCPUPowerManagementClient     196.0.0
    com.apple.nke.applicationfirewall     4.0.39
    com.apple.security.quarantine     2
    com.apple.driver.AppleIntelCPUPowerManagement     196.0.0
    com.apple.iokit.IOSerialFamily     10.0.6
    com.apple.kext.triggers     1.0
    com.apple.driver.DspFuncLib     2.3.0f2
    com.apple.iokit.IOAudioFamily     1.8.9fc9
    com.apple.kext.OSvKernDSPLib     1.6
    com.apple.iokit.AppleBluetoothHCIControllerUSBTransport     4.0.9f8
    com.apple.iokit.IOSurface     86.0.2
    com.apple.iokit.IOBluetoothFamily     4.0.9f8
    com.apple.driver.AppleSMBusController     1.0.10d0
    com.apple.iokit.IOFireWireIP     2.2.5
    com.apple.driver.AppleHDAController     2.3.0f2
    com.apple.iokit.IOHDAFamily     2.3.0f2
    com.apple.driver.AppleSMBusPCI     1.0.10d0
    com.apple.driver.AppleBacklightExpert     1.0.4
    com.apple.driver.AppleGraphicsControl     3.2.6
    com.apple.nvidia.nv50hal     8.0.0
    com.apple.NVDAResman     8.0.0
    com.apple.iokit.IONDRVSupport     2.3.4
    com.apple.iokit.IOGraphicsFamily     2.3.4
    com.apple.driver.IOPlatformPluginLegacy     1.0.0
    com.apple.driver.IOPlatformPluginFamily     5.2.0d16
    com.apple.driver.AppleSMC     3.1.3d11
    com.apple.iokit.IOSCSIBlockCommandsDevice     3.5.1
    com.apple.iokit.IOUSBMassStorageClass     3.5.0
    com.apple.driver.AppleUSBMultitouch     235.7
    com.apple.iokit.IOUSBHIDDriver     5.0.0
    com.apple.driver.AppleUSBMergeNub     5.1.5
    com.apple.driver.AppleUSBComposite     5.0.0
    com.apple.iokit.IOSCSIMultimediaCommandsDevice     3.5.1
    com.apple.iokit.IOBDStorageFamily     1.7
    com.apple.iokit.IODVDStorageFamily     1.7.1
    com.apple.iokit.IOCDStorageFamily     1.7.1
    com.apple.iokit.IOAHCISerialATAPI     2.5.0
    com.apple.iokit.IOSCSIArchitectureModelFamily     3.5.1
    com.apple.iokit.IOUSBUserClient     5.0.0
    com.apple.iokit.IO80211Family     500.15
    com.apple.iokit.IOEthernetAVBController     1.0.2b1
    com.apple.iokit.IONetworkingFamily     3.0
    com.apple.iokit.IOFireWireFamily     4.5.5
    com.apple.iokit.IOAHCIFamily     2.2.0
    com.apple.iokit.IOUSBFamily     5.1.6
    com.apple.driver.AppleEFIRuntime     1.6.1
    com.apple.iokit.IOHIDFamily     1.8.0
    com.apple.iokit.IOSMBusFamily     1.1
    com.apple.security.sandbox     220
    com.apple.kext.AppleMatch     1.0.0d1
    com.apple.security.TMSafetyNet     7
    com.apple.driver.DiskImages     344
    com.apple.iokit.IOStorageFamily     1.8
    com.apple.driver.AppleKeyStore     28.18
    com.apple.driver.AppleACPIPlatform     1.6
    com.apple.iokit.IOPCIFamily     2.7
    com.apple.iokit.IOACPIFamily     1.4
    com.apple.kec.corecrypto     1.0
    Model: MacBookPro6,2, BootROM MBP61.0057.B0C, 2 processors, Intel Core i7, 2.66 GHz, 8 GB, SMC 1.58f16
    Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB
    Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 512 MB
    Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x029E, 0x434D33583447534431303636202020202020
    Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x029E, 0x434D33583447534431303636202020202020
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.81.20)
    Bluetooth: Version 4.0.9f8 10405, 2 service, 18 devices, 1 incoming serial ports
    Network Service: Wi-Fi, AirPort, en1
    Serial ATA Device: ST1000LM024 HN-M101MBB, 1 TB
    Serial ATA Device: MATSHITADVD-R   UJ-898
    USB Device: hub_device, 0x0424  (SMSC), 0x2514, 0xfa100000 / 2
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0236, 0xfa120000 / 5
    USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 4
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8218, 0xfa113000 / 8
    USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfa130000 / 3
    USB Device: hub_device, 0x0424  (SMSC), 0x2514, 0xfd100000 / 2
    USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0xfd110000 / 4
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 3

    That panic was not caused by third-party software. If the problem is recurrent, the possibilities are:
    A stale or corrupt kernel cache
    A damaged OS X installation
    A fault in a peripheral device, if any
    Corrupt non-volatile memory (NVRAM)
    An internal hardware fault (including incompatible memory)
    An obscure bug in OS X
    You may already have ruled out some of these.
    Rule out #1 by booting in safe mode and then rebooting as usual. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
    You can rule out #2 and #3 by reinstalling the OS and testing with non-essential peripherals disconnected and aftermarket expansion cards removed, if applicable. Sometimes a clean reinstallation (after erasing the startup volume) may solve a problem that isn't solved by reinstalling in place, without erasing.
    Corrupt NVRAM, which rarely causes panics, can be ruled out by resetting it.
    If your model has user-replaceable memory, and you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications for your model. Memory that is either slower or faster than specified may be incompatible.
    The Apple Hardware Test or Apple Diagnostics, though generally unreliable, will sometimes detect a fault. A negative test can't be depended on. Run the extended version of the test.
    In the category of obscure bugs, reports suggest that FileVault may trigger kernel traps under some unknown conditions. Most, though not all, of these reports seem to involve booting from an aftermarket SSD. If those conditions apply to you, try deactivating FileVault.
    Connecting more than one display is another reported trigger for OS X bugs.
    If your system is not fully up to date, running Software Update might get you a bug fix.
    In rare cases, a malformed network packet from a defective router or other network device can cause panics. Such packets could also be sent deliberately by a skillful attacker. This possibility is something to consider if you run a public server that might be the target of such an attack.
    If none of the above applies, make a "Genius" appointment at an Apple Store to have the machine tested. You may have to leave it there for several days. There isn't much point in doing this unless you can reproduce the panic, or if you can't, it happens often enough that it's likely to be repeated at the store. Otherwise you may be told that nothing is wrong.
    Print the first page of the panic report and bring it with you.
    Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you know how to restore, and you have at least  two independent backups.) Don’t erase the recovery partition, if present.
    Keeping your confidential data secure during hardware repair
    *An SSD doesn't need to be zeroed.

  • HT201263 i cant restore my phone, I keep getting a message to turn off find my iphone, cant get into it b/c my daughter change the password and doesn't remember the password

    help, i need to restore my phone, I keep getting an error to turn off find my iphone,  I can't get into the phone b/c my daughter change the password and doesn't remember what she changed it to.

    Remove an iOS device or Mac on which you can’t turn off Find My iPhone
    If you can’t turn off Find My iPhone on the device, turn off the device so it goes offline, then remove it from Find My iPhone on iCloud.com.                        
    Note:   If you have an iOS device, you can also remove your device by first erasing it—just follow the instructions below to remove a device you don’t have. You can later restore the device from an iCloud or iTunes backup.                            
                               Turn off the device.                       
                               Sign in to icloud.com/#find on another computer with your Apple ID (the one you use with iCloud).                                                      If you’re using another iCloud app, click the app’s name at the top of the iCloud.com window, then click Find My iPhone.                       
                               Click All Devices, select the offline device, then click Remove from Account. If you don’t see Remove from Account, click All Devices again, then click the Delete (x) button next to the device.                                                      If the device comes online again, it will reappear in Find My iPhone. To make sure your device doesn’t reappear, turn off Find My iPhone on the device (follow the instructions above to remove an iOS device or Mac), or if you have an iOS device, you can erase it, then remove it (follow the instructions below to remove an iOS device you no longer have).                          

  • MSI P31 Neo-F V2 - Fails to Boot

    I've got an MSI P31 Neo-F V2 motherboard that I've had for about about 16 months now. Unfortunately today it's just started failing to boot correctly.
    I turned the machine on and was greeted with a red error message just after the usb controller was initalized. The message said "Warning !!! The previous performance of overclocking is failed and the system is restored to the default settings. Press any key except "DEL" to enter SETUP......."
    I haven't overclocked the machine (don't know how) so I'm not quite sure why that error message was coming up. Anyway, I pressed space, that prompted me to restore settings which I did, then took me to setup where I saved and exited. Then tried to restart the machine. From this point on (about 30 restarts) I've had that message twice. Normally it does one of the following:
    a) Powers up, no bleeps, no video output. Sits there waiting.
    b) Powers up for a few seconds, then powers straight back down. Waits about 10 seconds, then repeats. Eventually after enough retries it will reach the some point as (a).
    I've tried disconnecting power, I've tried taking the CMOS battery out. The last time I got to the error message my USB keyboard wouldn't even work so I couldn't do anything but restart. If anyone has any suggestions on what to do then fire away, as I'm really stuck now 
    I don't know what version of the BIOS I'm running as I can't get that far anymore. Apart from the CPU which I'm not sure is important? (Intel Duo 3Ghz) I'm not sure on much more info on my system.
    Thanks.
    Ian

    Ok, I've managed to find an old photo of the Bios.
    Bios: A7392IMS V2.1 080608 is the number top left.
    CPU : Intel Core 2 Duo E8400 3.0Ghz
    Gfx : 512Mb NiVidia GeForce 9800GTX+
    Mem:  2 X 2GB DDR 2 800 MHz (will try and find out brand).
    H/D : 2 * 160Gb drives. One is Seagate, the other Western Digital, both SATA 2.
    OS : XP not that it's really relevant...
    PSU : 800W. Don't know brand and DC current output. Will try to get these.

  • P31 Neo V2 fails to boot.

    My son got A P31 Neo V2 motherboard witch started a couple of days ago with the message overclocking failed (never had overclocking done)
    By now the bios start up screen is not even shown.
    After power on the system powers of and on several times (sometimes 1 sometimes up to 10 times)
    Then power stays up but no video output.
    BIOS: Ami WF971497 (from sicker on mainboard)
    RAM: 4x 1GB DDR666 (kingston)
    MB: MS-7392 Ver 1.2 8816209876
    CPU: Intel core2 duo 2.66 Ghz
    GFX: 512Mb NiVidia Ge-Force 9800GT
    OS: Windows 7 (64 bit)
    ERP: 070
    things done so far.
    Checked CPU (in other mb) OK
    Checked GFX (in other mb) OK
    Checked RAM (in other mb) OK
    Fresh CMOS Battery (and clear CMOS)
    1 piece of ram in mb
    Booted up 1 time and fails after that (tried other slots and ram modules)
    never got a second good boot-up.
    problems are the same as https://forum-en.msi.com/index.php?topic=138245.0

    @salaac: Start your own Topic and provide full system specs. >>Posting Guide<<
    Quote
    Result of mine going to the shop was that after plugging in some form of diagnostics card the error codes didn't mean anything to them
    What is that supposed to mean?  The shop has no idea how to interpret the information of a diagnostic card?  The card basically does nothing else than to forward/show the respective AMI BIOS P.O.S.T. Checkpoints the system cycles through after start-up.  If the system halts after turning it on because of a system error it will halt at a certain checkpoint which can be monitored with a diagnostic card.
    A full list of all relevant AMI P.O.S.T. Checkpoints (in run-time order) can be found here:
    http://www.ami.com/support/doc/AMIBIOS8_Checkpoint_and_Beep_Code_List_PUB.pdf

  • Cant boot MSI P31 Neo v2

    Hi. First of all sorry for my bad english.
    So I have this PC for 1,5 years now, never had this problem before.
    One day I start my pc and it shows "Warning!!! The previous performance of overclocking is failed and the system restored to the default settings...." Press del to enter setup.
    So I press del and enter setup, then i use fail safe deafaults settings and exit bios. Pc starts normaly. Next time I turn it off same message came up, so i did the same fails safe deafaults, but no effect, it just restarted and again same message. So i decided to try optimized deafaults and pc started. And again next time i turned it un same message, i tried fail safe deafaults, then optimized and no effect. After about 10 times trying those setting pc started, so i googled the problem and the suggestion was to flush cmos by removing batteri. So i did. After that pc isnt starting at all, just nothing on screen, no signal. No error beeps or something like that. All coolers, cd room ect is powered, just no signal on monitor. Checked the monitor with another pc, runs normaly.
    So the system specs-
    Intel core E7300 2.66ghz
    Msi p31 neo-f v2
    A-data 1gb ddr2
    A-data 1gb ddr2 (tried with one ddr only, nothing)
    samsung f1 750gb sata2 7200rpm
    Giga byte 512mb gddr3 pcie16 hd4850
    Fortron psu atx 400w
    bios - A7392IMS200
    I have checked all the wire contacts,ddr slots, vga slot, removed and inserted back CPU too, no help.
    Any ideas?

    I would check the CPU/Ram. this system was overclocked?

  • Advanced Host Controller Interface (AHCI) support on a "P31 NEO-F"

    hi all.. does my mainboard ( msi p31 neo-f ) supports native Advanced Host Controller Interface (AHCI) to use hdd hotplug with one sata>esata bracket?

    Quote
    not having a "safely remove hardware and eject media" its always a bit scary! some cached files will not be dumped to the hdd and cause errors.
    Again, as long as you do not remove the hard drive (or plug it in) while the system is running, there will be no problem.

  • MOVED: MSI P31 Neo and FSB/DDR ratio

    This topic has been moved to Overclockers & Modding Corner.
    https://forum-en.msi.com/index.php?topic=116635.0

    Hello Aacko,
    the P31 Neo is a budget board that is not really designed for overclocking (notice the red PCB).  The P31 chipset supports DDR2-667 and DDR2-800 memory modules.  With a FSB-200-MHZ-CPU installed, 1:1.66 and 1:2 are exactly the ratios you need to get your RAM to 667 MHz or 800 MHz.
    Quote
    Can I do something about this or should I swap P31 Neo to some P35-chipset mobo that would allow more flexible FSB/DDR ratio settings?
    If you really want to overclock, you should go for a P35 Platinum or P35 Neo2-FR/FIR board.

  • Problems with MSI P31 Neo mobo

    Hello all,
    I just received my new MSI P31 Neo motherboard today and have spent nearly the whole day trying to get it to work.
    My problem is that when you turn the system on about 4/5 times there is no graphics displayed what so ever. When the graphics do come on and you can go through the BIOS it quite often jams. If occasionally you do get past that, when the Windows XP disc starts to load the files for the installer, it Jams and you need to restart, restarting this long process.
    My CPU is supposed to be supported, it's a 3.6ghz Intel Pentium 4 chip. I am using 4 x Samsung Original 1024MB DDR2 PC5300 RAM though it only shows 2gb of it in the BIOS. The graphics card is a NVIDIA GeForce 7300 GT 512MB PCI-E.
    Can anyone tell me how to get this mobo to work? Things to try? Otherwise I think I will just have to send it back...
    techie5487

    Quote from: techie5487 on 24-January-08, 07:34:41
    UPDATE:
    I tried booting with 2 RAM Chips and it works great! This seemed to be the problem.
    The ram IS double sided which would explain it.
    If you are wanting some more system specs, just ask and I will try and get the most I can.
    Del UK:
    If I could run 4gb it would be great but I cannot seem to find the SPD in bios. My BIOS is American Megatrends Inc. v02.61 so it would be great if you could help me with that!
    If all else fails I might either just settle with 2GB or buy some new RAM chips. Can anyone please tell me some Ram chips which would be able to give this mobo 4GB?
    Thanks
    techie5487
    Done
    2 Gb in
    Into bios
    SPD off
    Set to 5-5-5-15
    Save settings
    Power off
    Install extra 2 x 1Gb modules into slots 2 & 4
    Power system up
    4Gb detected................. slow post not fast
    3.25Gb checked
    1 second delay
    4096Mb
    3.25Gb extend
    768Mb in +4Gb
    System sees 3.25Gb

  • Fsb/dram ratio on p31 neo

    hi,
    i have p31 neo board. in bios the only option for fsb/dram ratio is 1.1.66 and 1.2. with this option overclock is almost imposible (fsb <240)
    a bios update will resolve problem or i can't do anithing.
    thanks
    msi p31 neo
    pentium dual core 2160
    2*1 gb ddr2 pc 6400
    wd 3200aaks
    gainward 8600gt
    corsair vx450
    case asus

    Actually, the system should start even with DDR2-1066 memory installed, but it should recognize it as DDR2-800. You will not have additional memory dividers when inserting DDR2-1066 RAM.  You even be able to increase memory speed beyond DDR2-800 MHz by increasing FSB Clock Speed.  However, there is no guarantee that you can successfully make your RAM operate its rated speed.
    If you are really planning to overclock your system, you may be better of looking for a board that is more up to this task (P35 Neo2/P35 Platinum would be a much better choice in this case.)

  • P31 Neo-F - I don't have 1:1 FSB\memory ratio

    MSI P31 Neo-F (Bios 1.2) Rev 1.0
    Corsair 6400XMS2 2 x 1Gb (Dimm1 & Dimm3)
    Core2Duo 4300
    Core2Duo 6300
    The BIOS sees both sticks of RAM. I have tried slots 2 & 4 in desperation as well.
    I can not get 1:1 memory ratio.
    With the 4300 I get AUTO\1:1.66\1:2. Set to Auto it runs at 1:1.6
    With the 6300 I get AUTO\1:1.25\1:1.5 (if my memory servers me right). Set to Auto it runs at 1:1.25
    I have cleared the BIOS many times. What am I doing wrong?

    Quote
    The Corsair memory is DDR2-800 isn't it?
    Quote
    Corsair 6400XMS2 2 x 1Gb (Dimm1 & Dimm3)
    Yes, and there should be no problem making your RAM operate @800 Mhz by choosing the proper FSB/DRAM ratio in BIOS.
    Quote
    My MSI P35 Plat runs with the same memory at 1:1 fine with the same processor. So are you saying the P31 can not do the same?
    I know, this matter is complicated, but I will try to explain and to give you at least a partial answer.  P31 and P35 chipsets do not use the same memory controllers.  Have a look at the Intel Datasheets for both memory controllers:
    P31 / 82P31 Memory Controller Hub (MCH)  --> DATASHEET
    Page 21:
    Quote
    Supports Front Side Bus (FSB) at the following Frequency Ranges: - 800/1066 (200/266MHz)
    and Page 25:
    Quote
    Differential Host clock of 200/266 MHz (HCLKP/HCLKN). Supports transfer rates of
    800/1066 MT/s.
    Compare to:
    P35 / 82P35 Memory Controller Hub (MCH)  --> DATASHEET
    Page 27:
    Quote
    Supports Front Side Bus (FSB) at 800/1066/1333 MT/s (200/266/333 MHz)
    and Page 31:
    Quote
    Differential Host clock of 200/266/333 MHz (HCLKP/HCLKN). Supports transfer
    rates of 800/1066/1333 MT/s.
    As you can see, according to Intel specs, the P31 chipset itseld does not offer native support for CPUs that operate @333 (1333) MHz FSB Clock Speed.  That is why, from a chipset point of view, the number and variety of possible dividers is less compared to the P35 chipset.  Looking at the differential between FSB and Memory Clock speed you can also see that 1:1.25/1.1.5 (E4300) and 1:1.66/1:2 (E6300) are the native chipset ratios to match DDR2-667 and DDR2-800 RAM with FSB/200 MHz and FSB/266 MHz processors.
    Of course, in practice chipset limitations can be exceeded by BIOS programming to a certain degree. That is why P31 boards actually do support FSB/333 MHz CPUs, but the support is not native. Have a look >>here<< as well.
    The only situation in which you actually need the 1:1 memory divider is overclocking, but since this a budget board not meant to be put to excessive OC use, BIOS implementation of memory dividers that go beyond Intel specs is limited. After all, it is a matter of price/performance.  The MSI P31 Neo-F matches the Intel specs and exceeds them when it comes to FSB/333 MHz processors, there is no real mistake here. I can find nothing in the Intel specs nor in the MSI Product information that says there has to be a 1:1 ratio implemented at all costs.
    There is a chance, of course, that MSI will implement more memory dividers in a future BIOS release.  Try contacting MSI, maybe they can give you a more definate answer this one:
    http://ocss.msi.com.tw/
    Quote
    The Intel chipset is capable of offering 1:1
    Capable: yes, native support: no.
    Quote
    The issue is MSIs implementation of it = BIOS.
    You are most likely right about BIOS implementation in general, but I don't see a reason to call it an issue at this point. 

Maybe you are looking for