P35 Neo2-F Sata2 Raid1 problems

hello
i have some problems with MSI P35 Neo2-F mb...
I can't make it work with 2 sata2 Hard Drives in RAID1 mode
Last BIOS update done,
The install of the OS (win xp prof sp2/sp3) is ok, but if you want to format last partition of RAID drive it cames with blue screen and restart - after restart it said that the Raid Matrix is demaged - and won't boot... "please select PROPER BOOT DEVICE"
VOLUMES
ID NAME LEVEL STRIP SIZE STATUS BOOTABLE
0 VOLUME0 RAID1 (MIRROR) N/A 149GB FAILED NO
PHYSICAL DISKS:
PORT DRIVE MODEL SERIAL # SIZE TYPE/STATUS (VOL ID)
2 ST3160813AS 149.1GB ERROR OCCURED(0)
3 ST3160813AS 149.1GB ERROR OCCURED(0)
Raid Volume = 160x2 = RAID1 MODE 149GB - split in 3 parts (50Gb each)
Any suggestion is welcome...
Proc Intel Dual Core E5200 (2,5Ghz/800fsb/2mb)
Memories: Desktop Memory KVR800D2N5/2G KINGSTON (DDR2,2GB,800MHz,Non-ECC CL5) or
KVR800D2N5K2/4G KINGSTON (DDR2,4GB 2x2gb DC,800MHz,Non-ECC CL5)
VGA: WinFast PX8400 GS Silent
HDD: 2 x SEAGATE Barracuda 7200.10 (3.5",160GB,8MB,SATA II-300) ST3160813AS
RAID 1
POWER COOLER MASTER Extreme Power Plus 460W
fdd DRIVE - for instaling with F6 - raid drivers
Optical LG DVDRW DL ata/ide

Hello,
How old are the drives?
Try a full write 0 on both drives and see what happens after.
http://hddguru.com/content/en/software/2006.04.12-HDD-Low-Level-Format-Tool/
You will need a working pc to do this.
Take both drives out and run HDDGURU LLF tool on them, this will do the write 0.

Similar Messages

P35 Neo2-FR / Marvell Controller problem. - DVD/CD Burning

I think this is hardware related and more like limitation of the model rather than one faulty motherboard.
My setup is
P35 Neo2-FR / E8400 / WinXP
I have all 4 intel SATA for RAID so I've used Marvell controller for my DVDRW. 1st was NEC drive IDE and while it read disc fine it couldn't burn any CD/DVDs
I thought it was faulty DVDRW so I've bought a new samsung SATA burner. It has SAME exact problem. Cannot start burning.
I've tested the same unit with different computer, and of course it works.
I'm sure not many people have similar spec as mine (4 SATA HD RAIDS) so this might go unnoticed but I find it a very serious problem.

Quote from: larciel on 12-February-08, 07:08:08
I just found out that it is actually reported as SCSI.
SCSI\CDROM&VEN_TSSTCORP&PROD_CDDVDW_SH-S203B&REV_SB02\5&2A9ABE04&0&040
That's the DEVICE_ID for the Drive.
You might be right. This might be issue with Raid and Marvell conflicting.
I use Lastest driver for all of them. I actually use DriverPacks from DriverPacks.net
Just trying to see if anyone have same config as mine so I can know that this is driver issue and not hardware issue.
You could disconnect your raid setup and attach your burner to a Intel SATA port and see what the Intel controller thinks about your burner. Bios in none raid mode and fast boot disabled so you can see whats going on.
Boy there is another possible problem. I would never use the DriverPacks on hardware that I can get drivers for manually. Did you slipstream the DriverPack into your XP disk? I have seen the wrong drivers used and or mis configured when doing so.

P35 Neo2-FR OS Install Problem

Ok this is gonna be long so bear with me...
I recently purchased a new board, CPU and RAM for a long overdue upgrade. I installed all the components and the machine booted up fine, other than the dreaded dual boot. The problem I am having is a freeze or reboot during OS install. At first it was freezing during copy of system files, usually at the same spot of around 47%, but I have seen it all over the place. It won't let me do a regular format of disk without freeze or reboot, only a quick. After many tries and 3 different Win Pro disks, the other 2 with SP2 instead of 3, I have gotten as far as the 2nd copy of files in the XP GUI. Now I have tried to install IDE to IDE, SATA to IDE, IDE to SATA and SATA to SATA. One of either sticks of RAM in all slots. Purchased new PSU thinking that my old one wasn't powerful enough. Reseated CPU and cooler, added extra thermal grease. Reset BIOS settings to default. Cleared CMOS. I even tried installing Vista and Ubuntu just for kicks and got notta. The reboot comes out of nowhere and I have even had the thing freeze on me in BIOS once. I figured before I packed up the new items for RMA to Newegg I would ask here, after many searches, to see if anyone had any input.
Rig is as follows-
MSI P35 Neo2-FR LGA 775 Intel P35 ATX Intel Motherboardwith 1.8 Bios
Intel Core 2 Quad Q6600 Kentsfield 2.4GHz LGA 775 Quad-Core Processor
G Skill 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory
SAPPHIRE 100162L Radeon X1300XT 256MB 128-bit GDDR2 PCI Express x16
Ultra LSP 650 Pro +12v=38A 650 watts

I am trying with only one HDD and a CD-ROM.
I've been trying with one of each of the two sticks of RAM in ever slot. Just got done trying with different voltage on RAM and also tried different voltage on the CPU, no luck. Either freezes or reboots.

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

MSI P35 Neo2-FR S3/USB Problems & Remote Desktop Video Problem

I recently received a new board back from RMA (my old one wouldn't post at all) and decided to re-install Windows XP back on it after verifying that it was working, and now I'm having a few issues with the board that were fine and working with the old board.
Firstly, I used to wake the system up from sleep using my USB keyboard when hitting "enter". Now it won't wake up with usb, and occasionally when waking it up with the power button, either my mouse or keyboard will not respond (both are USB). I then need to put the system back to sleep using the power button (I have xp set to sleep when pushed) and wake it up again to get the USB devices working. I have re-installed Windows XP, changed the ACPI BIOS settings to wake up using all devices, enabled/disabled legacy USB, downgraded the BIOS to 1.8 which I was running on my old board, and tried every USB slot on the board, all while running the exact same hardware that was on my previous board. Any help?
Secondly, I have the board/windows set to wake from S3 when attempting to reach it remotely. I can login fine, but when I get home to check the system, the screen is black. It's still running, and I can reach it again through RDC, but I can't seem to wake it up locally. The only way to correct the screen is by hitting the power button to put it to sleep, and then hitting it again to get it out of S3. This seems like a videocard issue, and I have tried using older versions of the nvidia driver but I always seem to have the same problem. Oddly, when I run tests at home using my laptop everything is fine and the video is displayed after logging off, but it seems to only be happening when I'm using it from my work computer. I would need to run some more tests to verify this though, and I assume that after some time using my laptop it would do the same thing. (the tests were run going outside of the lan and coming back in, from an S3 state). Video card drivers I tried were, 178.24 (oct. 15th), 178.13 (sep. 25th), 175.16 (may 13th).
Any help would be greatly appreciated. Thank you.
kk
MSI Neo2-FR (BIOS 1.9 & 1.8)
Core2Quad Q6600
Geforce 8800GT
Mushkin 2x1GB 9200 (running at 1066)
Antec Neo HE 550 watt PS
Windows XP Pro SP3

Thanks for the reply kourosh. I have used both the 1.9 (latest) and downgraded to the 1.8 BIOS that I was using on the board pre-RMA as stated in my initial post. It just doesn't make sense that I had everything working properly with the old board, and with the new board that I received back from MSI, things just don't work. I'm using the exact same hardware and have done multiple re-installs with different drivers etc.
I doubt that part two is a networking problem as I stated in my initial post that I'm testing by going outside of the LAN and coming back in from outside. I think it has more to do with waking it up remotely multiple times (eg. wake up remotely-->sleep-->wake up again-->sleep again-->possible black screen error), but I haven't had the time to do all of the testing.
I just find it strange that these things are not working as they were, and I'm beginning to blame the board again as I know how they SHOULD be working on the same exact board.
Anyway... thanks again for the reply.
kk

MSI P35 NEO2-FR start up problem

Problem on start up. Power up PC,PC posts but loads the CMOS menu rather than booting the OS (Vista). Then, from the CMOS menu, if I press the escape key OS (Vista) loads and PC is fine. I'm sure this should not happen, should I see the CMOS load during boot process without me pressing the delete key? Any ideas?
Thanks in advance.
Griffin

Thanks for that BOSSKILLER. I had tried that and the safe defaults.
I had trouble loading Vista in the begining and was covinced I had a dammaged install disc, something was wrong with the SATA driver or some other issue that was going to take a lot of sorting out. The Vista installation seemed to be going in a loop, after choosing the drive to install to the install would start but at first reboot it would say there was no HDD present and go back to the CMOS menu. I eventually got around that problem and installed Vista but, the PC still booted to the CMOS menu and I would then have to press the escape key to make it carry on and boot into Vista.
I eventually tracked the problem down to a duff keyboard - unplugged the keyboard and booted without it. Hey, presto, the PC booted to Vista no problem.
It turns out that my kids had spilt some juice into the keyboard. On closer inspection I found the "." key on the number pad was glued solidly in the down satate.
T/Y
Griffin

Bios Update Problem P35 Neo2 - MS 7345 V 1.1

Hello
I've update my board bios because a "hard disk not present" problem and since it I was having several problems:
I'm running Windows XP SP2 and it takes a very long time to start (in bar and loading windows screen).
The major problem I have is when power on the computer it is alwayls showing the red font message that says it was a problem overclocking, so everytime I need to go into setup and to save changes whitout changing anything.
I suspect the bios I've installed is not the right one since the start screen says "MSI Neo Patinum" instead Neo2, but I've used Live Update ... so it should be the rigth one.
Can anybody help me please with this?

Quote from: Jack t.N. on 30-April-09, 06:32:24
Hi,
first of all, can you please provide full system specs for comparison? Read the >>Posting Guide<< to get an idea of what we need to know.
Hello Again, first of all I want to thank you for answering so fast. Also I have to apologize for my "not so good" english.
# CPU brand, model and speed (eg AMD Athlon64 X2 5600+ 'Brisbane' core)
DualCore Intel Pentium E2160, 1800 MHz (9 x 200)
# Motherboard model (eg K9A2 Platinum, NOT just MS-7376!!)
P35 Neo2 - MS 7345 V 1.1
http://www.msi.com/index.php?func=proddesc&maincat_no=1&cat2_no=&cat3_no=&prod_no=1261
# Memory brand, type/speed, size, number of sticks (eg 2x1GB Crucial DDR2-800)
2x1GB Supertalent DDR2-800 DDR2 SDRAM (5-5-5-15 @ 400 MHz) (4-4-4-10 @ 266 MHz) (3-3-3-8 @ 200 MHz)
# Video card brand, chipset type, memory size (eg Gainward Geforce 8800GT 512MB PCI-E)
XFX NVIDIA GeForce 8600 GT (256 MB)
# Hard drive(s) brand, size, type, speed (eg 2x Seagate 200gb SATA150)
WDC WD3200AAKS-00VYA0 (298 GB, SATAII)
# Any other peripheral cards and devices (eg MSI TV@nywhere Plus TV card, MSI PC54G2 Wireless LAN PCI card)
Multi Flash Reader USB Device
Realtek RTL8185 802.11a/b/g Wireless LAN Network Adapter   PCI
# Operating system and version (eg Microsoft Windows Vista Home Premium SP1 32bit)
MICROSOFT Windows XP Pro SP2 32bit
# Power Supply Unit brand and output in watts and DC output (amps)
Vistuba 550W Power Supply
+3.3 V   35A
+5 V     30A
+12 V   20A
Quote from: Jack t.N. on 30-April-09, 06:32:24
Three important questions:
1. Which BIOS Version were you using before the update.
2. Which Version did you update to?
3. Did you clear CMOS with main A/C power cable removed from PSU after the Update?
1. I'm not sure what bios version come with the board (my misstake) but it was older than I've now.
2. I'm actually using AMI 1.10 Build Date: 11/10/2008
3. Yes I did
Quote from: Jack t.N. on 30-April-09, 06:32:24
Did that problem disappear after the update?
The hard disk problem didn't show any more
Quote from: Jack t.N. on 30-April-09, 06:32:24
What kind of hard drive are you using and what port is it connected to?
WDC WD3200AAKS-00VYA0 (298 GB, SATAII)
it is connected to SATA 5 port acording to Board manual diagram
I've checked hard disk SMART and health and it is ok
Quote from: Jack t.N. on 30-April-09, 06:32:24
- If you have an IDE/PATA Hard Drive:
.....What kind of cable are you using? (40 or 80 wire)
.....Is there any other drive connected to the IDE cable (how are the jumper settings for each drive (MASTER/SLAVE/CABLE Select)?
I Haven't IDE/PATA Hard Drive
I will tell you the story:
I bought the computer and I was using the Blue (Marvel) sata port for the hard disk.
Then a normal day I began to have a very low Windows start so I changed the sata plug to a purple one and the problem disappeared.
Then I began to have the same problem again so I changed the plug again but problem was there anyway so decide to update bios to 1.8 version.
The problem come back randomly and sometimes it disappeared just changing the sata port to wich the plug is connected to.
After that I began to have the "No hard disk present" error and I cleared the CMOS and tried several things until it come to work again.
Few time ago I noticed that was a newer bios version, so then I used Live Update to update bios and drivers again.
Now I'm having the "slow" problem again. I'have been trying several configurations and testing programs but I just didn't find anything wrong.
Edit:
I'm having the first post problem (overcloking message after power on)
I also had a very rare issue few time ago when shutdown the pc: few minutes later it power on by It self !! until I have disabled every wake up event from setup.
I hope you can understand, and thanks again for your help.
Gabriel.

MSI P35 Neo2 (MS-7345) strange BIOS problem

Hi all,
My first post here - just wondering if someone could help me.
I recently 'accidentally' flashing my bios version from 1.8 to 1.C on my MS-7345 (P35 Neo 2) board, after deciding to install live update. While I know it's often considered a bad idea to flash the bios when everything's working, but I did it anyway. Since doing it I got many many BSODs. I'm running XP Pro 32 bit btw. I got these BSODs mostly when the computer was working hard, but not always. I'd barely be able to do anything sometimes. Occasionally Windows would even crash on start-up.
I made sure that i was running the latest drivers for all my components, peripherals, etc, including motherboard and graphics card. I even reformatted my HDD and reinstalled Windows from scratch just in case it was a virus. However, the problem has continued, and I even got a few BSODs during my reinstallation of Windows XP Pro.
Another thing I tried was reverting back to the old bios version (1.8), but this made no difference, so I eventually returned to the latest 1.C.
I've written down all the error message codes somewhere, though I've currently misplaced the sheet I wrote them on. If you need to know the exact codes I can locate it and add it to this thread. I probably got about 30 BSODs per day. Often they were IRQL_NOT_LESS_OR_EQUAL type ones, but definitely not just that. Each code I got I researched thoroughly to see if I could work out the problem. Some pointed to RAM Failure, some to HDD problems, some to bad Graphics card, some to corrupt drivers. Pretty much anything you can think of, the errors 'blamed'. However, I had a hunch regarding the bios / motherboard.
I eventually discovered (by chance) after re-flashing the bios (which I'm doing in DOS using the suggested AFUD after a reboot) that if I...
1. Switch on the computer
2. Enter BIOS Setup by pressing Del
3. Turn of the boot sector protection (in order to flash bios) and set USB stick to be the first boot device
4. Boot to DOS from my USB stick and flash the bios in DOS
5. Reboot
This is the critical bit...
6. When when I get the 'Bad checksum, Press F1 to enter BIOS setup or F2 to use default values' PRESS F2 (it won't work if you go into bios setup as this will then require another reboot before loading windows).
7. Let Windows XP load as normal.
If I follow all the above steps (I discovered this by mistake), the computer is 100% stable. I even tried some burnout tests and played some cpu & gpu intensive games with settings on full to give it a real workout, which previously would have ended up in a BSOD within seconds.
However....
If I then reboot the computer (or shut down and switch it back on the next day) and let windows load, it will be unstable again, just as before!
In other words, I'm currently having to flash the bios every time I switch on my PC or reboot it in order to get a stable system.
So this problem isn't fixed - but I've found a workaround at least for now.
Incidentally I've tried installing a new CR2032 bios battery, since I thought it might be losing settings on reboot, but this didn't make any difference.
I personally don't think it's actually the BIOS Reflashing that's making it work - just something weird in the bios settings. It's as if 'erasing the checksum' (cleaning out these dodgy bios settings), which forces the PC to load the defaults the next time it boots, is helping. I have to just mention that going into bios set-up and choosing 'Load Fail-Safe Defaults' does NOT help, since the computer reboots when you 'Save Settings and Exit'. It's as if the bios settings corrupt every time on boot, which causes the crashes.
Does anyone have any suggestions?

To return to the previous bios, just download the one you want and use the forums tool.
http://www.msi.com/product/mb/P35-Neo2-FR---FIR.html#/?div=BIOS
>>Use the MSI HQ Forum USB flasher<<
Before you do that, try to boot and enter bios. Hit f6 for optimized defaults save and exit see if the problem persists.

P35 Neo2-FR: Problems with 1066 MHz RAM speeds

I have the following PC components:
Intel Core 2 Duo E6750
MSI P35 Neo2-FR LGA 775 Intel P35 ATX Intel Motherboard
OCZ Platinum 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500)
In order to get the memory to run at 1066 MHz, I need to set the FSB／Memory Ratio to 1:1.6 correct? When I do that, it shows it running at 1066 MHz but after doing that, I got a BSOD IRQL_NOT_LESS_OR_EQUAL five minutes into a game. I then changed that ratio to 1:1.2 so it runs at 800 MHz and I played for several hours after that without any problems.
That memory should be capable of running at that ratio correct? Possibly defective RAM? OCZ provides a utility to update the SPDs on their chips and when trying to update the one in the first slot, it gives several messages, something like "expected FF got 00," and will not update. The second DIMM updates fine. I am using manual settings for the memory in the BIOS and not the SPD but I'm wondering if the SPD update errors are indicative of a bigger problem.

Quote
Does the memory voltage also need to increase when changing this?
It depends on the modules you are using. In most cases the answer is "YES".
Look for the specific part number of your modules and check on the OCZ Produkt Page to find out what DRAM Voltage is recommended for 1066 MHz.
http://www.ocztechnology.com/
EXAMPLE:
For OCZ DDR2 PC2-8500 SLI-Ready Edition (OCZ2N1066SR1G) OCZ recommends 2.3 Volts. BIOS Standard is usually 1.8-1.9V.
http://www.ocztechnology.com/products/memory/ocz_ddr2_pc2_8500_sli_ready_edition
Quote
n order to run 1066 MHz, I need to set it at 1:1.6
Yes:
333 MHz x 1.6 ~ 533 MHz (~1066 MHz DDR2)

Weird artefacts, mobo(P35 Neo2-FR) or gfx card problem?

Recently I was playing a game when some weird artefacts appeared on the screen before just completely freezing up.
I rebooted and saw this:
The desktop/login screen was all ****ed up too (pardon my French!)
I ran ATI Tool and saw my gfx was 40'c which was about normal considering I was just playing a game so don't think the gfx had overheated.
Then suddenly the PC froze.
Rebooted and got the same problems so I left it for several hours just in case it was overheating. (unlikely though since I've got plenty of fans, all of which are working and no alarms went off etc)
Few hours later, same problems but I noticed my IDE cable wasn't in all the way so I pushed unplugged/plugged it in and it worked fine!
Fast forward through 4 days of normal usage (although no games) with no problems to today.
Left the PC for a while before coming back and seeing the screensaver was all screwed up and the desktop was running at a lower resolution that it should have.
Shut down and restarted but nothing showed up on the monitor (LCD via a DVI->VGA adapter) not even the POST or BIOS messages.
Tried my TV which has DVI and an image was displayed:
Managed to login but again it was all ****ed up.
So at first I thought it was my graphics card but after it started working again I'm not so sure.
BTW, all the parts are only 2-3 months old and have worked flawlessly together since I built the PC.
I haven't been able to try any parts in any other PC's as I don't know anyone with a PCI-E mobo or even anyone with a PCI gfx card (only AGP and onboard!)
What do you guys think is the source of the problem?
Mobo (P35 Neo2-FR)
gfx card (PowerColor HD3850)
RAM (2gb geil Black dragon)
Thanks

It's been working fine for the last few days now, until today of course when I have an important report due in!!!
Quote from: NovJoe on 26-April-08, 14:19:59
I would suggest that you run the system under stress test with graphics intensive games and see how it goes for a week.
I have done this.
I've run ATI Tool artefact scan for over an hour and got no errors.
Yesterday I was playing STALKER for several hours on high settings on my 1680x1050 monitor/TV via DVI and the other monitor connected via VGA showing ATI Tools and CPU temps.
No problems at all after a few hours gaming.
(I recorded all temp data to a log and the maximum temp reached was 56'c)
Today I was working on a uni assignment so I only had Word, Firefox and Winamp open and some horizontal artefacts appeared.(nowhere near as bad as the above photos though, it was more like specs and dashes)
I opened up ATI Tool and saw the GPU temp was 35'c.
Before I could do anything it froze but the music continued playing. It stayed like this for a few seconds before going black and the music stopped.
So playing games at hi res for several hours did nothing, but having word and firefox open seemed to trigger something and start messing up.
After several restarts (kept crashing at first) I managed to get into Windows (with artefacts similar to the first photo) long enough to recover my assignment and shut down.

P35 Neo2-FR Bios problem

Hello, well the problem being, my system goes like this : system freezes, keyboard stops answering after some period of time. I just build a new system.
My CPU is running stock.
My RAM is running stock.
My VGA is running stock.
My drivers are right.
I did run a memtestx86 & no error reported.
I did not test another CPU
I did not test another GPU
I did not test another MOBO
MSI P35 Neo2-FR PCB v1.2
Intel Pentium 4 E541 @ 3.2GHz
Tuniq Tower 120
OCZ DDR2 PC2-6400 SLI-Ready Edition Dual Channel 2x1GB
Galaxy 9600GSO 384M 192BIT GDDR3 (driver v175.16)
Maxtor 200GB SATA & Samsung & Maxtor 160GB SATA
Lite-On & BenQ DVD-RW
Huntkey Green Star 550W PSU
Cooler Master Centurion 590
WinXP SP3
everything running default speed & settings.also, i just fresh install my winxp. winxp installation running fine. but when i log-on,after some period of time the system crash. i tried flashing beta build bios.also no luck.but suprisingly, my system seems fine when flashed to A7360IMS.182T bios! no freeze,no crash! is there something wrong with my system here? is it my mobo?

At this time, i'm using A7360IMS.182T bios. my system will crash in windows when flashed to A7345IMS.xxx bios.even the oficially one.
Quote from: flobelix on 29-June-08, 02:53:27
nightmare's right. The bios you flashed is not for P35 Neo2/Plat. Sure it's that bios and sure you have a Neo2
I know it's not for P35 Neo2/Plat. I'm sure i have Neo2.It's written everywhere: the box,mobo,manual,CD, etc... Do i need to post a picture of my mobo here???

P35 NEO2-FR startup problems, cannot get into BIOS

Hello!
So i recently bought new parts for my computer:
CPU: Intel Core 2 Duo E8500 3.16GHz 1333Mhz
Motherboard: MSI P35 NEO2-FR
RAM: 2x Corsair TWIN2X 2048MB 6400 DDR2
PSU: Corsair Powersupply 550W (3.3v/30A, 5v/28A, 12V/41A)
Graphics Card: GeForce 7800 gtx (this part was not new, so i dont have any more details for it)
I start up my computer with only the CPU, graphics card and one RAM module installed, and a keyboard attached to the ps2 slot (using a converter) for simplicity. The problem is that the computer freezes up when the MSI screen comes up, and i cannot get into the BIOS. The LED lights on the motherboard is indicating the state "Testing base and extended memory". And b/c i go straight into the MSI start-up screen i am unable to find out what BIOS version i am running, though i am fairly sure (i have talked with another person that bought the same motherboard from the same shop as me at about the same time, and he is running BIOS v1.8) that it is 1.8 and it is therefore compitable with my cpu. I have also tried several different types of RAM with the same results. I am also very certain that i have all the cables plugged in correctly (have also tried resetting CMOS ALOT of times) but still the same result.
Does anyone have any clue what could be the problem ?

Quote
i am unable to find out what BIOS version i am running
Have a look at the sticker on the BIOS Chip of the board to check the factory BIOS Version. The following picture shows the location of the chip on your board (it is actually a P35 Platinum, but it has the same PCB as the P35 Neo2-FR):
Quote
CPU: Intel Core 2 Duo E8500 3.16GHz 1333Mhz
If you have an E8500, E0 (and not an E8500, C0) you will need BIOS v1.9 [A7345IMS.190] to have full support for your processor. You can identify your processor model by checking its sSpec number (on the CPU itself or on the box):
E8500, C0 ---> sSpec#=SLAPK {Supported since BIOS v1.6 [A7345IMS.160]}
E8500, E0 ---> sSpec#=SLB9K {Supported since BIOS v1.9 [A7345IMS.190]}

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

P35 Neo2-F Sata2 Raid1 problems

Similar Messages

Maybe you are looking for