MSI P35 NEO2 FIR voltage problems!!

Let's start:
 I have MSI P35 NEO2 FIR ,e5200,2 x Geil ultra plus 1066+,as us 2900CT,lcpower 6550g and...rest- not so important for my questions.
1.My problem is next: default voltage values for my RAM is ~2.2-2.4 every time I check in windows (speedfun,sisoft Sandra, everest..)shows me 2.0 or some time even 1.8v  . When i change voltage in bios and went to win voltage on RAM is still unchanged (2.0v)  .
Same thing happen with NB voltage. But CPU voltage I can change freely with no problem.
When I change fsb(try to overclock) suddenly memory voltage rises how i do not now  , but only to 2.35 and no more.
Can anyone help me fix this problem because my memory is not stable at 2.0 or 1.8 sometimes and system crashes?
2.When i change cpu settings from 12.5*200 to (example)10*300 in windows even in system properties see that my current clock is 12.5*300=3750 and not 10*300=3000 like it should be .
Is it bios problem?
My bios version is 1.9.
Thanks!

same problem with the Neo2 FR (like mine). After quite of bit of researching and testing i reckon that software can not correctly read the vRAM on these MSI boards. I found that Speedfan, Everest, and HardwareMonitor all gave an incorrect reading for my RAM's voltage. Also, if i increased the cpu voltage in the BIOS then the voltage monitoring programs would show an increase in CPU voltage and RAM voltage (even though i had not changed the latter).

Similar Messages

  • MOVED: MSI P35 NEO2 FIS voltage problems!!

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

    same problem with the Neo2 FR (like mine). After quite of bit of researching and testing i reckon that software can not correctly read the vRAM on these MSI boards. I found that Speedfan, Everest, and HardwareMonitor all gave an incorrect reading for my RAM's voltage. Also, if i increased the cpu voltage in the BIOS then the voltage monitoring programs would show an increase in CPU voltage and RAM voltage (even though i had not changed the latter).

  • MSI P35 Neo2 Fir Patriot Memory Problems.

    Hi, 
    Having problems with my Patriot Performance PC2-6400 Low Latency Memory DDR2 (800mhz) 4-4-4-12, 2,2v, 2 * (2gb(2*1GB)kit) =4gb total
    on a MSI P35 Neo2 Fir moderboard with Intel Q6600 cpu)
    When i check the memory with CPU-Zv1.44 the memory only goes with the frequencys of 
    DRAM Frequenzy 399.5mhz
    FSb : Dram 2:3
    Cas# latency 5.0 clocks
    Ras# to Cas# delay 5 clocks
    Ras# Precharge 5 clocks
    Cycle Time 16 clocks
    Why doesn't they go in 4-4-4-12 frequencys ???
    Have tried to manually change dram timing in bios but no success
    so i went back to auto dram timing.
    What can i do to get the 4-4-4-12 timings.
    Please help. 
    thanks in advance swefin

    Quote
    When i check the memory with CPU-Zv1.44 the memory only goes with the frequencys of
    DRAM Frequenzy 399.5mhz
    ~400 MHz is the correct frequency for your modules.  CPU-Z shows real clock speed.  DDR means Double Data Rate (two transactions per clock cycle).  Multiply 399.5 MHz by two in your head and you have your effective DDR(2) rating of 800 MHz.  There is no problem here.
    Quote
    Why doesn't they go in 4-4-4-12 frequencys Huh
    Have tried to manually change dram timing in bios but no success
    so i went back to auto dram timing.
    What can i do to get the 4-4-4-12 timings.
    CL5 is the standard latency for DDR2-800 modules.  It ensures that they are able to operate @JEDEC standard voltage settings @1.8V (+/-0.1V).  The board is supposed to set memory timings to CL5, otherwise your system would not be able to boot at standard voltage.  Check the "SPD" tab in CPU-Z and look for the standard timings that were programmed into the SPD chips of your modules (400 MHz), I am absolutely sure that you won't see 4-4-4-12 @400 MHz @1.8V being part of the SPD tables.
    You have to manually adjust memory timings in BIOS to 4-4-4-12 AND also increase memory voltage to the value the manufacturer recommends for CL4/DDR2-800 MHz.  The voltage is usually 2.0-2.2V depending on the brand and type of RAM in use.

  • P35 Neo2-FIR boot problem (GRRR - no video)

    Hi.
    A have a problem with my Neo2-FIR. But first my system's specs:
    MSI P35 Neo2-FIR (PCB 1.2, BIOS 1.9 or 1.A - the first one supporting my CPU. I don't remember and there's no video, so I can't check it)
    Intel E8400 E0 stepping (SLB9J) cooled by Thermalright Ultima-90.
    2x2GB DDR2 A-Data 800MHz 4-4-4-12 2T
    PowerColor HD4850 PCS+ (512 MB)
    Enermax Pro82+ 385 W (Click for more)
    WD AACS 640 GB (irrelevant)
    It has been working well since fall 2008. Suddenly, I turn on the PC to see "No input signal" on my monitor..
    Diagnostic LEDs report GRRR (from top to bottom), which translates into "Initializing video interface. This will start detecting CPU clock , checking type of video onboard. Then detect and initialize the video adapter". No signals form the speaker.
    The full sequence after an restart is GRRR (for a split second) -> RRGR (Mem. detection test) -> RRGG (Decompressing BIOS image to RAM) -> RGGR (Processor initialization) -> GRRR.
    After hardware changes (like different RAM configuration - in this case detecting RAM), it can freeze on some other stage. But an restart helps, and clearing CMOS before start up prevents this. Normally it's the above sequence.
    What I've tried:
    - Tested all the voltages with an Voltmeter. They're fine. The PSU was always rock solid.
    - Detached everything that's not crucial (HDD, DVD, fans etc)
    - Checked all the connectors.
    - Cleared the CMOS (with the button, by removing the battery etc.). It worked, because the dual boot issue was reintroduced.
    - Booting with the video card in the second (yellow) PCI-e slot.
    - Booting with an old, PCI videocard. (Same symptoms as with the new one). I've also tried booting without and video card - it was the same, but there was an beep from the speaker.
    - Booting with one RAM stick, in various configurations.
    - Reseating the CPU (it looks fine, so does the socket BTW).
    - Reseating the motherboard in the case (to make sure there are no shorts). No shorts on Ultima's backplate.
    - probably some other stuff that I don't remember
    - (edit) various FSB jumper configurations.
    Of course the video card was checked on an different PC and it works fine. I can't check the CPU, but it's rather unlikely that it is its fault.
    What I haven't tried is an blind BIOS update. A bit risky. Is it worth trying?
    Any ideas? I probably have to RMA the board, but maybe someone knows the answer or had an similar problem.
    I've also had some problems with CRC errors with the HDD. Windows reported problems with writing on it (don't remember the error codes). It was moths ago and replacing the SATA connector and changing the port helped.
    There were some (rare!) BSoDs, mostly caused by Realtek drivers. RAM was tested with Memtest86+, it was fine. Anyway nothing special and most probably nothing related to the current problem.
    Regards,
    Dr.

    Hi,
    Thanks for your help.
    They've actually sent me the P35 Platinum Combo mainboard. It the same as normal Platinum, but supports both DDR 2 and DDR3. I don't mind really, though I also don't need it It does have a slightly different PCB and a different BIOS (at least it has it's own number, everything else looks the same).
    I have a problem though with the BIOS. It's impossible to set the proper CPU voltage. On Neo2-FIR the minimal voltage was equal to CPU VID (1.1 V). There were some problems with EIST (when it was enabled, the minimal voltage was higher - 1.25 V I think. I've just disabled it).
    On this mainboard, with exactly the same CPU, I'm unable to set the voltage below 1.25 V and the CPU overheats  It works, but gets really hot. EIST was disabled on default. Rather annoying, this is supposed to be a quite build, which won't be possible with an overvolted CPU
    The BIOS is the newest version, but I'll double check.
    I'll probably create a topic about this issue after some more research and testing (when I'll find time for it ). Though I'm afraid it's a bug that cannot be resolved. Apart from that everything looks fine.

  • MSI P35 NEO2-FIR, Traces of fire...

    Hello,
    During dust cleanup of my PC. I noticed a burned part of my MSI P35 Neo2-FIR mobo, i wonder if it is still save to use now, maybe someone have any idea what does that 'chip?' is responsible for ?
    Photos:

     It looks like it's a resistor in the +5V power circuit to JUSB1. Must have been something plugged into it at one time or another that short circuited/overloaded it it and fried the resistor. What was plugged into the JUSB1 header? If all else is OK if you need to use any front panel USB device you can use JUSB2 or 3 instead. Get a volt meter and check the PSU for correct voltage of +5V to see if PSU is still OK as whatever caused that damage may have also damaged PSU.

  • P35 NEO2-FIR Controler problems

    Specs new pc:
    Intel Core 2 Duo E8400 3.00 GHz, 1333 MHz, 6 MB
    MSI P35 NEO2-FIR (stock bios, not at home so I can't check which bios version it currently has)
    Sapphire Radeon HD 4870 512MB, PCI-e 16x
    Corsair TWIN2x4096-6400C4DHX PC6400, 800 MHz, cas 4, Kit of 2
    Antec Earthwatts 500 Watt, 80 Plus Rating
    Samsung SpinPoint F1 1TB, 720 Rpm, 32 MB Cache, S-ATA II/300
    Lite-On DVD-RW LH-20A1S S-ATA
    Everything on STOCK speeds. (no overclocking)
    While building the pc I inserted my DVD-player from my previous pc (IDE interface) and connected it properly to the pc. (jumper on master and connected to the master connector on the IDE cable)
    It gave me an error during windows installation that the disk would be corrupted or something similar while the disk was in the IDE drive. Then I placed the Windows disk into the S-ATA Lite-On drive and then it didn't have any problem and continued installation of windows. After installation I noticed windows didn't recognize the IDE player. I checked the bios and it wouldn't show up there either.
    Then I inserted two of my IDE harddrives (320GB Maxtor and 120GB Maxtor) and they wouldn't show up on the bios or in windows either.
    This all happened 1 week ago.
    Today I booted my pc to find out it didn't have any internet/network connection so I thought my housemates did something with the router but soon I found out my pc was the problem. Reinstalled windows to check if it was a driver issue. Nothing helped so now my IDE controller and LAN controller both seem to be broken.
    Would this be possible because of an unstable bios version or is my motherboard dying slowly?
    Thanks in advance for reactions.

    I highly doubt another IDE drive would work, it's worth a shot though. Might try it tonight when I get home.
    About the LAN driver: I installed Windows XP Pro twice, installed all drivers and the hardware manager wasn't showing any unknown hardware. So I guess it's safe to say it wasn't a driver issue since it just stopped working after a week and I didn't change the software or hardware setup in any way.

  • P35 NEO2 FIR boot problems

    Hi,
    I'm another unlucky MSI P35 NEO2 FIR user whose mainboard does not boot. My config is as follows -
    mainboard: MSI P35 NEO2 FIR
    cpu: E6750
    ram: OCZ Platinum Rev.2 800 2x1G
    gfx card: MSI 8600GT
    psu: Corsair VXEU450W
    In the beginning it worked flawlessly for about 4 months. Then the boot problems started to appear. After turning on, the mainboard status leds configuration was red-red-green-red, the system kept rebooting and I had to wait several minutes before successful boot occured. (The whole procedure involved additional amount of hassle for me because I had to open the case and disconnect the harddisk during the "warm-up" time.) Gradually the time before successful boot increased. At one time I was not able to boot for several hours. Then I changed FSB jumpers configuration, moved memory to different slots, reseted BIOS and I don't even remember what I tried before eventually miraculously booting the system. After this accident I had to wait 0.5-1.5h for successful boot. In the meantime I upgraded BIOS to v1.8. Nothing changed. This lasted few weeks, and now the big problem reoccured. Initially, the behaviour after turning on slightly changed. Instead of red-red-green-red leds, I got 4 reds. The big additional disadvantage of this was that the system was not rebooting automatically after a few seconds. I had to manually turn it off then turn on again and repeat it until I got red-red-green-red leds, after which automatic reboots started. It's been getting worse and worse since then and now the situation is that I haven't been able to boot the system for a few days. Each of those days I tried for several hours without success (still trying while writing this post).
    The one thing I haven't tried is using the 667 memory, I read that it might help. But even if 667 memory will help, does it solve the problem once and for all, or it's possible that the problem will reoccur later (note that my mainboard worked fine for 4 months)?
    Also, do you have any other suggestions?
    Thanks for help.

    Quote from: Jack the Newbie on 14-March-08, 04:44:40
    Try to boot your system with only one stick of RAM installed in Slot 1 (test both stick seperately).
    Tried this today, though not too long (<20 manual reboots).
    Quote from: Jack the Newbie on 14-March-08, 04:44:40
    Also, clear CMOS with main A/C power cable removed from PSU before next start-up attempt.
    I did something similar today - I removed the battery completely (and rebooted without a battery since then).
    Quote from: Jack the Newbie on 14-March-08, 04:44:40
    Your current RAM modules could be faulty.  Do you have different modules to try (different brand/model, if possible)?
    I believe RAM is ok, because when my system worked I ran Orthos a few times for several hours in "blend" mode and no errors occured. Unfortunately I can't easily get 800 or 667 modules.
    I'll try again tomorrow, enough for today.

  • MSI P35 Neo2 - Sleep S3 Problem

    Hello.
    My System:
    CPU: Core2Duo E6850 @ 3.0 Ghz (FSB:1333 | 333 x 4)
    RAM: 4 x Kingstone HyperX DDR2 1Gb ram @ 800mhz
    M/B: MSI P35 Neo2 Fir
    GPU: Gigabyte Radeon HD5770 1024mb
    HDD: Western Digital BlackCaviar 640gb 64mb cache
    SSD: OCZ Agility 3 60gb
    PSU: Fortron BLUESTORM 400w
    O.S: Windows 7 (SP1/Without SP) Ultimate / Hackintosh 10.5.8 / 10.6.8 / 10.7.3 / OpenSuse 11.2 / 12.1
    Recently i decided to enable the sleep mode on my computer (because the power cost, my computer is all the time on).
    So, i go to my bios and i change the suspend mode to S3. I boot my os (windows7) and i tried to sleep.
    The system is going to sleep fine but nevers wakeup, the led of motherboard is flashing fast red-green-reg-green and after random time stops flashing, sometimes all are red and sometimes are all green!
    Before post here i tried to fix the sleep and i read evert post.
    I have try: Flash Bios to (1.8, 1.7, 1.2, 1.C, 1.A, 1.9), update all of my drivers including (lan, gpu, chipset), disconnect every usb includes keyboard (i tried with old ps2 keyboard), disconnect all pci cards, disconnect all RAM's (except one), i tried another Graphics Card (Gigabyte 8600GT), another PSU (Premier 400w), Bios Settings (ACHI/IDE, Recall GPU, PCI express x4, clear cmos), change DVI connector port on gpu, change to analogue RGB D-SUB, reinstall windows to ide disk/sata disk with S3 Enabled!
    I tried to sleep from my Hackintosh 10.7 with the same error and with linux (openSuse) with the same error.
    I have notice coz when i remove rams and i downclock the cpu and rams the leds are stop flashing in 2-3 secs (normaly tooks 10-40 secs)
    Also the mb never wake with keyboard key press event!
    Please experts, i need your help...      

    @NovJoe
    Thanks for reply!
    I have test with one piece of ram. also i tested with another cpu (Intel Celeron 1.6 - i cant remember the model).
    My motherboard version is 1.2 (MS-7345 V1.2)
    (i dont know if it helps but hibernation working really good! working on windows and mac)
    before a hour i test to reprogram bios with floppy disk! first i destroy my bios (i edited with ami tools to corrupt and the mobo start the recovery process, i put a floppy with the last bios renamed to AMIBOOT.ROM and the recovery worked! but sleep not)
    i dont want to talk with msi for a too old mobo, so if anyone knows whats is happen please help.

  • P35 NEO2 FIR voltage

    Is it possible to change voltage (cpu, fsb, pci-e, chipset) through bios menu?
    Thx in advance.

    Quote from: Frankenputer on 20-August-07, 22:16:28
    According to your manual, no.
    Exactly.  Here it is straight from the manual:
    CPU Voltage / Momory Voltage / VTT FSB Voltage / NB Voltage / SB I/O
    Power / SB Core Power
    These items dispaly the power status of CPU, Memory, FSB and chipset. Read-only.

  • MSI P35 Neo2-FIR: red LEDs after BIOS upgrade

    I upgraded the BIOS to version 1.6, since I had a Highpoint IDE controller card that wouldn't work, so I thought upgrading might resolve the problem (it didn't, but that's a separate thread  ).
    However, after upgrading, all the status LEDs are red (they were previously all green), but the system works just fine! I can boot into the OS and everything works. But the LEDs are still red (and obviously there's nothing wrong with the CPU).
    In other words, this is in no way a showstopper. But it's annoying, and I thought someone might have an idea about the cause for this. I have tried clearing the CMOS but without any effect.
    Br,
    Per

    Quote from: voidvoid on 17-January-08, 06:53:16
    Del UK: I updated the BIOS using afud408 that is in the BIOS zip file, booting from a USB stick. I have a Highpoint IDE controller card that wouldn't work with the original BIOS. Unfortunately, it doesn't work with the newest BIOS either.
    KelticDaz: I just reverted to the 1.5 BIOS, and the LEDs are green again! Now they change during POST also. Thanks for the suggestion!
    I think I will stick to the 1.5 BIOS, apart from the above also because it seems like a couple of the BIOS setup options have been removed in the 1.6 BIOS.
    Just wondering if you had a bad flash. Nothing removed in my update from 1.4 to 1.6, in fact I noticed an extra option!

  • MSI P35 NEO2 FIR : shared PCIEX ?

    if I populate the SECONDARY PCIEx16 will it disable the PCIEx1 slots  ?
    thanks.

    No. PCIE x1 slots are not running concurrently to the PCIE x16 slots.

  • P35 Neo2-FIR New Build Problems

    Hi there,
    Just finished new build (specs below), but get the full row of red LEDs on power up. Cycles through this endlessly. Cleared CMOS to no effect.
    No idea what BIOS I have as system has never been on.
    Any ideas?
    Antec P182
    MSI P35 Neo2-FIR
    Q9300
    Corsair 2 x 2Gb  XMS2 PC-6400
    Gigabyte 9600GT 512Mb
    Corsair HX520W PSU
    TIA

    The lights are not the final word as I have gotten that indication when my video card was not properly seated on an other board even tho it was supposed to mean processor failure for that board too.  Maybe the vendor of the board can lend you an other cpu to flash bios.  An other alternative would be to RMA for reflash if possible once you are sure it's the processor and the bios.
    Presumably Balloonshark has the same processor.  Good luck to both of you.  Let us know how it works out.   

  • Wireless problems P35 Neo2-FIR

    Hello,
    I hope someone can help me with a PCI card issue.  I have a Netgear WG311T wireless card that I want to use with my new PC which has an MSI P35 Neo2-FIR motherboard.  When I install the card after installing the drivers the LED next to the PCI slot does not light up and the card isnt recognised my the board.  I have tried disabling most of the onboard devices such as the LAN controller and Extra IDE controller but its still not working.  The card works perfectly i have tried it in another pc and in both of the PCI slots on the motherboard.
    Hope someone can help me out.
    PC Specs: (nothings overclocked)
    Intel Q6600 G0
    P35 Neo2-FIR
    2Gb PC2 6400 RAM
    2 HDD's
    Videomate T750 TV card (PCI)
    Sata DVD drive
    Corsair 450 watt PSU

    Quote
    When I install the card after installing the drivers the LED next to the PCI slot does not light up
    That is normal, if there is a gap on Pin #12 (count pins from the left):
    Only if there is a Pin in the 12th position (from the left), the LED will get a signal and light up.  However, this should not affect the functionality of the card.
    Quote
    and the card isnt recognised my the board
    Have you tested both PCI slots?  Try setting "PCIeX4 Speed Controller" to "x4" (instead auf "AUTO" in BIOS (Cell Menu)).
    Quote
    Videomate T750 TV card (PCI)
    Remove the TV Card for testing and see if that changes anything.
    Also, which BIOS-Version are you using?

  • P35 Neo2-FIR - slow USB

    USB ports on this board have max transfer about 33MB/s. It should be about 60MB/s - 480Mbps (as I have on AMD NF4 board).
    I've checked this on 2 MBs, 3 external HDDs, 1.1, 1.8, 1.9B1 BIOSes, all USB ports and a few USb cables.
    My ext HDD is WD Passport 2 160GB and on NF4 board I've got 45-60MB/s of real transfer (Total Commander). On Neo2-FIR it's 33MB/s.
    It' clear that USB is limiting my HDD because transfers from begining and ending of HDD are the same (should be higher on the beggining).
    Is there any fix to this? Maybe BIOS fix is necessary.
    Intel E2160
    2GB 1066MHz RAM
    MSI P35 Neo2-FIR
    GF 8800GT
    RAID0 1TB
    Chieftec 450W
    Windows XP x64

    Hello
    I've exactly same problem. I was testing external WD 500GB USB 2.0  Hard Drive and WD 320GB on different usb ports. Maximum transfer was 33.7MB/s. I think should be more.
    Bios 1.3
    Intel E8400
    2x2Gb 800MHz ram
    Msi P35 Neo2-FIR
    GF 8800GT
    Raid0
    Corsair 520W
    Vista Ultimate 64

  • P35 Neo2 FIR does not boot at all

    Pretty similar to another topic, however my problem is with MSI p35 Neo2 FIR...
    Mobo doesnt start - it stops on the welcome screen, where it says to hit "del" to enter bios setup. Hiting keyboard keys doesnt do anything (yes, keyboard is fully operational a proprely connected:), and the mobo stops. The first time I ran the system i went a little bit farther - i've seen the bios version (1.8) and a proper CPU recognition (C2D 8400) - than mobo stopped as well... Now each time i try ro stary the system it sops on teh welcome screen...
    My config is (all hardware is brand new, nothing has been overclocked):
    - mentioned mobo
    - Corsair CMPSU-620HXEU
    - 2 x ADATA VITESTA 2x2GB Extreme Edition DDR2 800+MHz CL4 (4-4-4-12)
    - Gigabyte GTX 260
    - C2D 8400 45nm
    Tested with another graphics (Radeon 1950 Pro) another RAM modules and a diffrent PSU - still nothing...
    Any ideas how to solve the problem?

    If I am not mistaken the new E8400 E0's require the 1.9 BIOS.  If the S-Spec # on the box and on the front of the chip is SLB9J, then you do, which is mixed news.  The E0's are great overclockers; however, you'll need to flash that BIOS.
    Here's a thread about that problem, if, indeed, you have an E0:
    https://forum-en.msi.com/index.php?topic=119827.0
    If you have a USB thumbrive, you can flash it with this:
    https://forum-en.msi.com/index.php?topic=108079.0
    Instructions:
    https://forum-en.msi.com/index.php?topic=116721.0
    Otherwise, you'll have to do the floppy method.  You'll need a different chip to place in there to get to that stage.
    Other options:
    #1) Try to get a BIOS replacement ship from MSI.
    #2) Return the board and find something that will work with that chip, if it is an E0.
    If it isn't an E0, then my intuition is incorrect.

Maybe you are looking for