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).

Similar Messages

  • 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).

  • 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.

  • MOVED: MSi P35 Neo2-FR & Windows 8?

    This topic has been moved to Intel Core 2 Duo/Quad boards.
    https://forum-en.msi.com/index.php?topic=164044.0

    Unlike for Win7 MSI does not support Win 8 for that board nor does it provide drivers.  Using Win 8 would be up to your trying. Most likely it would do since most drivers should be provided by Win 8 as generic out of the box but if it will work fine is not guaranteed. Win7 on the other hand would be a sure thing with official drivers support: http://www.msi.com/product/mb/P35-Neo2-FR---FIR.html#/?div=Driver&os=Win7%2064

  • MOVED: MSI P35 Neo2-FR

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

    Quote
    I don't think so. If it's long in stock at the reseller's, then the end-user wouldn't have any waranty left.
    Yes that is the default warranty set up, I believe if it is within 24 months purchased by the end user from the reseller MSI might make an adjustment on thie system and honnor it.  In the UK the reseller is obligated for 12 months warranty and manufacturer warrnaty is a bonus.  If it was purchased from a large reseller I would contact them first, if you have to send to MSI UK thier will be a delay while they get enought faulty product to send over to the repair centre in poland, larger resellers have direct RMA accounts and send faulty product straight to the poland repair centre.

  • MOVED: MSI P35 Neo2

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

    Quote
    I don't think so. If it's long in stock at the reseller's, then the end-user wouldn't have any waranty left.
    Yes that is the default warranty set up, I believe if it is within 24 months purchased by the end user from the reseller MSI might make an adjustment on thie system and honnor it.  In the UK the reseller is obligated for 12 months warranty and manufacturer warrnaty is a bonus.  If it was purchased from a large reseller I would contact them first, if you have to send to MSI UK thier will be a delay while they get enought faulty product to send over to the repair centre in poland, larger resellers have direct RMA accounts and send faulty product straight to the poland repair centre.

  • MOVED: MSI K8T Neo2 Onboard Sound Problem

    This topic has been moved to AMD64 ATI/SiS/VIA based board.
    https://forum-en.msi.com/index.php?topic=108589.0

    About the exclamation marks:
    Goto Device Manager -> View -> Show hidden devices (enable)
    Goto the multimedia-section (where the exclamation marks are) and uninstall all devices marked with an exclamation mark LEAVE THE OTHERS!
    ==> Note: if you see two of the same installed devices of which one is installed wrongly (excl. mark) and the other is grayed out, uninstall them both. Note to leave all other things, like codecs, alone. If you don't, you ruin your Windows <==
    Now, reboot Windows and when the hardware install wizard pops up, cancel that and install the audio drivers manually.
    Then the JAUD-pin header: open your case. The JAUD pins are at the bottom left of your board. JAUD1 should be printed next to it. It looks like this:
    o o o x o
    o o o o o
    The x is the place where a pin is missing. now, both pins next to that one should be connected with a jumper
    o o | o |
    o o | o |
    The two | show the pins to be connected.

  • MOVED: MSI K8T Neo2 slow SATA problem

    This topic has been moved to Retired motherboards.
    https://forum-en.msi.com/index.php?topic=154087.0

    Thank you.
    Does this mean in praxis I dont get 150 MB/s ?
    Is this general or only MSI specific?

  • MOVED: MSI k9n ultra-2f voltage problem

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

    Quote from: BOSSKILLER on 01-November-08, 04:22:10
    Look for extra vcore option in Cell Menu.
    oO ok i see it , thanks

  • MOVED: MSI P35 NEO 2 motherboard problem !! help !!

    This topic has been moved to Intel Core 2 Duo/Quad boards.
    https://forum-en.msi.com/index.php?topic=137413.0

    >>Posting Guide<<

  • 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.

  • Msi p35 neo2 fr problem

    Alright, I have been using this board for quite sometime and today it gives me problem.
    When i tried to boot up this morning, the board just keeps on restarting. This happened once b4 but the problem solved after I pressed on the reset button on the board.
    whereas for today, after resetting, the board did stop restarting itself, but it hangs when the LED is at (red, red, green, red)from top to bottom. I refered to the user guide and it shows that there is a problem during memory detection.
    Can anyone pls help?
    This is what I have
    Mobo: MSI P35 Neo2-FR
    CPU: Intel Core 2 Duo E6750 2.66 1333mhz/4mb
    RAM: Kingston Hyperx 2x2GB DDR2-800
    Video Card: Nvidia Geforce 8500GT
    HDD: 1xHitachi Deskstar 1TB SATA 3.0gb/s, 1 Samsung 160GB(SATA), 1 Seagate IDE 80GB(IDE)
    OS: Microsoft Windows Vista Ultimate SP2
    PSU: AcBell 400W DC Output (There are a few of them.. didnt know which one.. the highest is 28Amps)

    Okay.  About the memory issue:  I believe a BIOS Update to the latest version may fix the problem with your DDR2-800 modules.  BIOS v1.2, v1.3 and v1.4 had known problems with DDR2-800 modules. In case you decide to do that, please >>Use the MSI HQ Forum USB flasher<< and avoid MSI Live Update or any other Windows based flasher.
    About the video card:  I is not necessarely defective.  Your PSU is not only a low-end poor quality device but also rather weak in the first place.  Try a stronger one with your original video card and see if that changes anything.

  • 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-FR/FIR wont overclock

    This might be a simple question but here it is. My new MSI p35 bios v 1.34 wont allow me to overclock my q66oo. I think the problem is windows xp pro 64. I cant install the MSI dual core center or the live monitor. When I am in the bios I canot change these setting inside the cell menu,
    cpu fsb frequency
    adjust cpu ratio
    cpu voltage
    memory voltage
    vtt fsb voltage
    nb voltage
    sb i/o power
    sb core power
    Any ideas?
    MSI P35 Neo2-Fr
    intel q6600
    evea 8800 gt
    g. skill 1 gig pc2 6400 2 sticks
    corsair hx620w

    Keep us updated on your progress.

  • 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.

Maybe you are looking for