MS-7360 (P35 NEO-F) bios ver 1.10 + INTEL Q8400 CPU

hello
i cant find q8400 in the supported cpu list for this mainboard, however the q8300 cpu is in the list
i just need to make sure what 7360 (1.xx) is supported q8400 cpu, it is really weird - MB support almost all quads, but not q8400
upd.
is there any way to get codes of supported processors directly from the MB BIOS?
I ordered a processor from the store and until tomorrow I need either pay or cancel my purchase.

Quote from: Namistai on 20-January-11, 11:25:04
ok.
MS-7360 bios ver 1.1A (1.10) supports q8400. Everything fine, thanks.
Thanks for reporting back.

Similar Messages

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

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

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

Black screen after P35 NEO-F BIOS Flash to v2.1

Hey Out There
I just upgraded my motherboard P35 Neo-F to bios version 2.1. With the tool from this forum.
After that the PC shows a black screen when booted, I have then tryed to clear the CMOS by removing the battery and switching the jumpers place.
After that i booted, and came up with wrong CMOS. F1 to run setup, F2 to load defaults CMOS settings. I then pressed F2 and booted into Windows.
I then found out that my 3Ghz processor was only running at 2Ghz. I then rebooted to check the bios settings, but it only shows a black screen when it tryes to boot.
I have to clear the CMOS to get into windows...
What could be wrong???
Hope one out there can help me.
Regards
Rantzaus

Quote from: Rantzaus on 07-October-11, 13:21:21
Hey.
Sorry for that.. I will then flash my bios back to 1.A..
But since it is that way that P35 Neo-F uses the bios from G33 Neo-F it should go wrong a lot of times. I dont know how many of the P35 Neo-F users that knows that.
MSI should make a discription on the P35 Neo-F site, that tells: PCB rev.x uses bios xxxx and so on.
But thanks for the help.
So far arround 10 users/cases crashed to the same.
Quote
But since it is that way that P35 Neo-F uses the bios from G33 Neo-F it should go wrong a lot of times. I dont know how many of the P35 Neo-F users that knows that.
Not a lot as 2.xx BIOSes are normally not available for manual download, but only from "Live Update"
Quote
MSI should make a discription on the P35 Neo-F site, that tells: PCB rev.x uses bios xxxx and so on.
I notice them many times, but they don't listen

MS 7360 P35 Neo F V1.00 Capacitors

Just saw another thread on another board where this guys P35 had started playing up because the capacitors started bulging next to the CPU. Searching google images there are a number of P35 board images with Polymer caps fitted next to the CPU (High quality) and some with Electrolytics (some good some bad). My board has blue Electrolytics (not bulging) does anyone know the Make and Series of these caps so I can look them up, or if anyone has an old P35 v1 with blue caps lying around could they see the make of them mines all screwed in and dont want to disturb it. Having just repaired two two year old routers with bulging Caps that kept rebooting I was wondering about my motherboard. Thanks.

If your capacitors are not bulging, and you have no problems with your board, then you have nothing to worry about, so please stop looking for a problem that is not there.

8kn neo platinum & bios vers 1.9

Has anybody out there been brave enough to try 1.9, and if so.... hows it working for you?

Quote from: sswilson on 10-September-05, 22:03:12
Thanks for the info. (Think I'm still going to wait a little while before flashing as everything seems to be working well)
It has been said.... "If it ain't broke, don't fix it"

P35 Neo Combo DDR3 1066MHz

Hi Guys,
I would like to upgrade (increase) memory size on the following system:
MSI P35 Neo Combo (bios ver. 1.3)
CPU Intel Core 2 Duo E6750
VGA Radeon HD 5770 1GHz
current memory 2x1 GB DDR2 800 Mhz
It is a few years old system and I wanted to put extra memory there. The mobo only supports up to 4GB (DDR2 or DDR3). As the DDR3 modules are cheaper today than DDR2, I bought 2x2GB DDR3 1066MHz (PC3-8500 CL7 Kingston) that should be supported by this mobo. But when I place the new moduls into slots the system does not boot . Of course, I took out the DDR2 modules before applying the new ones.
Do you have any clues where could be a problem? Manual BIOS settings of some parameters? Or to update BIOS to the newest version 1.7?
Thanks a lot in advance for any hints...

Quote from: beethoven on 21-January-13, 20:18:18
Voltage is set to auto - I will try to set it manually on 1.55 or 1.60V and will se if it helps. Just a short question - if deafult setting for RAM module is 1.5V, can voltage of let's say 1.60V somehow harm it?
Regarding the timings: at the moment the timings are set automatically by SPD. If I look at the specification of these modules (http://www.micron.com/parts/modules/ddr3-sdram/mt8jtf12864az-1g6) they have native CL10 but it is probably for default speed 1600MHz. Is CL7 for speed 1066MHz "overclocking" for this module?
Anything below 1.65V is ok for a DDR3 module.
Also, it's highly recommended to use 1.55-1.60V (instead of 1.50V) on older mainboards (and not only).
Now talking about timings.
7-7-7-20 are the default timings for DDR3-1066
9-9-9-24 are the default timings for DDR3-1333
You cannot use the SPD profiles of a DDR3-1600 module, if you want to make it run at 1066MHz.
So you need to manually change the RAM/FSB ratio, timings and voltage.

I need bios compatible with celeron E3200/E3300 for P35 neo-f

I need the bios compatible with Celeron E3200 for P35 neo-f, my motherboard is running the latest version of bios

There are 2 P35 Neo MB's. One w/BIOS 2xx and the other w/BIOS 1xx. G33 Neo also has the same BIOS & CPU support as P35 Neo w/BIOS 1xx. From what I see the one w/BIOS 2xx supports it but the one w/BIOS 1xx does not. Best would be to contact MSI with your question and specify which BIOS your MB has. >> G33 Neo <<
This list also shows the difference: >> P35 Neo <<
>> Contact MSI <<

P35 Neo-F

Beta BIOS for P35 Neo-F (MS-7360, PCB 1.0) BIOS ver. V1.1B7
BIOS Sign-on message: A7360IMS V1.1B7 051807 (Date: 05/18/2007)
Attachment name: P35 Neo-F V1.1B7.zip
Make and ensure PC is stable before proceed. Remove any OC if you have it.flash BIOS from USB key, by using our Tool(easy & safe way to flash):
MSI Forum HQ USB Flashing Tool
Use Beta or Modded BIOSes at own risk!

Quote from: uid313 on 07-June-07, 22:05:29
Where is the changelog?
I see no reason to do the risky process of flashing to a new BIOS, especially a beta BIOS, if there is nothing to motivate me why, if there is no reason todo so, what does this version do? What does it improve? What does it change?
There is no descriptions on the Beta versions..

P35 Neo-FI CPU compatability?

Can anyone tell me if the P35 NEO-FI mainboard is compatible with Q9400?

Quote from: Jack the Newbie on 08-March-09, 21:20:56
Ah, I see. They have messed up that other list then, skipping the v1.xx-BIOS Releases and/or somebody forgot to update it properly:
http://global.msi.eu/index.php?func=prodcpu2&prod_no=1215&maincat_no=1&orderby=cpu_name%20ASC#menu
Yep, there are two types of MS-7360, one of them are using BIOS 1.xx, other one is using BIOS 2.xx.
Model MS-7360 ==> P35 Neo-F/P35 Neo-FI/G33 Neo-F , using BIOS 1.xx
Model MS-7360 ==> P35 Neo-F/P35 Neo-FI/G33 Neo-F , using BIOS 2.xx
At MSI web, as P35 Neo-FI is shown only the second one who use BIOS 2.xx
P35 Neo-FI who use BIOS 1.xx is named at MSI web as G33 Neo:
http://global.msi.com.tw/index.php?func=prodcpu2&prod_no=1224&maincat_no=1#menu
1.A0:
P35 Neo-F/P35 Neo-FI/G33 Neo-F (MS-7360) V1.10 BIOS Release
1. This is AMI BIOS release
2. This BIOS fixes the following problem of the previous version:
- Update CPU Micro Code.
- Fixed BIOS report incorrect CPU ratio during POST.
3. 2008/11/11

P35 Neo Combo crash problem

Hi all,
Recently my computer has started to crash with a BSOD (Stop 0x00000124), it happens almost every day but I haven't been able to reproduce the crash, it seems to occur completely randomly. It even crashed when I was away for a day and didn't use the computer - I left it running to see if the crash would happen without me running any programs.
System:
Mainboard: MSI P35 Neo Combo, Bios version 1.7
CPU: Intel Core2 E6750
Memory: 2x2GB DDR2 800MHz
3 hard drives
Graphics: Radeon 4850
Sound Blaster X-Fi Fatality Pro
I am running Windows 7 Ultimate trial (64 bit), however the same crash happened under Vista Home Premium (64bit) so everything including the error code seems to point to a hardware error.
- disk checks return no errors
- memtest86 returns no errors
Not sure what to try, googling the problem leads me to believe the problem is with the mainboard. I'd like to know if there's something I could try before replacing the board. I have never overclocked anything on this system, mainboard and CPU are about three years old, memory about two, graphics card a year, hard disks 0-3 years. Before this problem happened everything was stable.
Some more info I can think of below. Any ideas/suggestions/assistance welcomed. Thank you!
Mainboard info:
CPU info:
Crash info from BlueScreenView:
Crash List
Created by using BlueScreenView
Dump File      Crash Time      Bug Check Code    Parameter 1      Parameter 2      Parameter 3      Parameter 4    Caused By Driver    Caused By Address    File Description
070110-25546-01.dmp   1.7.2010 15:25:17       0x00000124   00000000`00000000   fffffa80`04b7f038   00000000`b2000018   00000000`06000e0f   hal.dll   hal.dll+12903
070110-25171-01.dmp   1.7.2010 0:25:05       0x00000124   00000000`00000000   fffffa80`04b90038   00000000`b2000040   00000000`00000800   hal.dll   hal.dll+12903
063010-24921-01.dmp   30.6.2010 10:59:54       0x00000124   00000000`00000000   fffffa80`04b64038   00000000`00000000   00000000`00000000   ntoskrnl.exe   ntoskrnl.exe+4a5f3c   NT Kernel & System
062910-25765-01.dmp   29.6.2010 20:21:40       0x00000124   00000000`00000000   fffffa80`04b96038   00000000`b2000040   00000000`00000800   hal.dll   hal.dll+12903
062710-29781-01.dmp   27.6.2010 15:44:03       0x00000124   00000000`00000000   fffffa80`04b6e038   00000000`b2000040   00000000`00000800   hal.dll   hal.dll+12903
062610-134281-01.dmp   26.6.2010 18:51:01       0x00000124   00000000`00000000   fffffa80`04bad038   00000000`b2000040   00000000`00000800   hal.dll   hal.dll+12903
062610-32218-01.dmp   26.6.2010 14:31:57       0x00000124   00000000`00000000   fffffa80`04b62038   00000000`00000000   00000000`00000000   ntoskrnl.exe   ntoskrnl.exe+4a5f3c   NT Kernel & System

What I have now is 2x1GB and 2x2GB PC6400, all are A-Data. There was a crash with one of the 2GB sticks, trying the other now.
I might get DDR3 as replacement, as I'll be buying a new system towards the end of the year - my current board supports DDR3 as well and then I could use the memory in the new system. Or I'll just run with 3GB and no dual channel for the time being (the board has 2xDDR2 and 2xDDR3 slots, so can't use more than two sticks).
It's just odd that memory checks don't report any errors, and the system only crashes every 24 hours or so.

MSI P35 Neo-F (MS-7360): Computer randomly freezes while playing games

Hi there,
I have reached the end of my technical knowledge right now and I'm not even sure if this area of the forum is appropriate. The problem:
While playing higher-end games like Crysis 2, Anno 1404, Mass Effect 2 etc. my computer randomly freezes and the last few milliseconds of sound are being looped on my speakers (kind of like a buzzing sound).
By "freezing" I mean that my computer becomes unresponsive to any action other than pressing the Reset-Button or holding down the Power-Up-Button (no reaction to Ctrl+Alt+Del, Alt+F4, Alt+Tab, no mouse movement... you get it).
There's no exact timing as to when these freezes occur. The fastest freeze happened after less than a minute of playing a game, slowes one (just today after switching to my newer case with better cooling) took about 2 hours.
This freeze only occurs while my System is under load. No freezes while browsing the web, using office programs, listening to music or watching videos.
System Specs:
Mainboard: MSI P35 Neo-F (MSI-7360)
CPU: Intel Core2Quad Q6600 @2.4GHz
RAM: 4x 1GB DDR2-800 Corsair XMS2
Graphics: Gainward GeForce GTX 560 Ti, 1GB GDDR5 VRAM
PSU: Antec High Current Gamer 620W (upgraded from Xilence XP600, 600W)
New CPU Cooler: Arctic Freezer 13 Pro (upgraded from OEM Intel Boxed Cooler)
New Case: Zalman Z9 Plus w/ 4x 120 mm Fans (Upgraded from a Case with only 1x 250mm side Fan)
2 Western Digital HDD (1x 2TB, 1x320 GB)
1 DVD Reader/Burner (unimportant for that error I guess)
OS: Windows 7 Ultimate 64-Bit
2 Screens: 1x 24" Asus VS248H and 1x 21" LG Flatron Wide W2240T
Since this error is bugging me for quite a while now and since this is not the first forum I'm trying to get help from, here's a list of steps i already took to get rid of it, obviously to no good use:
reinstalled games where the freeze occurred
updated all Drivers (including cleaning old versions in safe mode; also tried older drivers)
updated BIOS to v1.A0
Reinstalled Windows
bought new Case and CPU Cooler to improve Air Flow/Cooling
checked Seating of all components (took out, cleaned, reapplied thermal grease where neccessary, re-inserted)
cleaned old case of dust (obviously no problem in the new case, which is 2 days "old")
ran 7 sequences of Memtes86+ without any errors
ran Prime95 without any errors for about 45 Minutes
ran Furmark for 15 Minutes under full load (burn-in test) without any problems, even though my graphics card hit the 100°C frequency-cut level
ran Furmark and Prime95 simultaneously without any problems
took records of component temperatures and system voltages without noticing anything unusual (at least not after i switched to the newer PSU, which is about 1 Month old - yet didn't resolve the problem)
tested with cyclic removal of 1 RAM device to further rule out RAM malfunction
tested with only 2 RAM devices in dual channel mode (Slots 1 and 3)
tried to reduce RAM clock (800 MHz --> 667 MHz) to no avail
checked S.M.A.R.T. values of HDDs, no issues reported
tested without any background programs
raised/lowered voltages to RAM, CPU and Chipset in BIOS to increase logic circuit stability/decrease heat production
I need to mention: After I transferred my system to the new case, i was able to play longer than average compared to my old case. So I am guessing that improper cooling was part of the problem, yet improving cooling obviously didn't resolve it.
Since these freezes are really annoying and nobody could help me resolve this so far, I'm hoping to find some new ways of narrowing down the problem or even getting rid of it here.
Regards
Sebb

Quote from: Bernhard on 10-July-12, 13:15:30
Lets be realistic. A system with a 560TI is recommended to have a around 31Amps under full load, a CX500 would be sufficient.
Have you monitored your CPU and memory utilisation ?
As suggested before, test the GPU in another computer to see if the behaviour is the same.
Whew, I thought for a second there that my common sense had left me when I saw that 60-Amp-Post ^^
Yes, I monitored CPU and RAM usage, there is no recognizeable pattern to be seen and it almost never happens under full load.
I will see if a friend of mine can test my GPU on his computer, and I will test it underclocked right away.
Though one more question regarding that: Should I only underclock GPU Core Clock or both Core and RAM clock?

Multiplier Problem: P35 Neo-F (7360) + e8500 Rev.E0.

Quote from: francis511 on 31-December-08, 02:28:18
I bought an e8500 (eo stepping) and the 9.5 multiplier option is unavailable in the bios of my board. I am running bios 1.9 and neither it nor 1.1a solved this problem. When I tried bios 1.8 , the board refused to boot until I swapped back to another chip.
I have the same problem with a P35 Neo-F (7360) whith a e8500 Rev.E0.
Initially, with native bios v1.7, after assembled the system, it doesn't come ever at the bios . It crashes at splash screen (no Bios, no F11 choice).
I make a update of bios with a "desperate" Ctrl+home at version 1.9, but the bios give a "Cmos checksum error".
However, I succeed to installed the s.o. (win xp sp2) and finally I succeed to flash the bios by usb device.
Now, i enable EIST through the control panel->Minimal Power Management but the multiplier don't increase over 9x in the bios options.
How can i do?
Thanks
P.S. I'm sorry for my little english!

Update your BIOS to the latest Version .
>>Use the MSI HQ Forum USB flasher<<

P35 Neo-FI: after flashing bios, Win XP won't start (BSOD)

Hello board,
I was a moron and did a bios upgrade from Windows, using Live Update 4. The flash seemed to finish normally. However, after the flash my Windows XP install wouldn't start, resulting in a blue screen of death ("Stop: 0x0000007E" etc). I used the rescue floppy to flash back to the (presumably) original bios version, with no change, still BSOD. I have been able to flash the bios again by using a bootable USB stick. (I couldn't use the Forum Flasher from my old notebook, so I used MSI's guide to creating a USB flash stick.)
The version I flashed back to from the rescue floppy is 1.A0 (1.10). I'm not sure what the newer(?) version Live Update offered me was. I was confused with the version numbers and looked for a newer version manually. I ended up flashing to 1.19, downloaded from MSI's server (http://download1.msi.com/files/downloads/bos_exe/7360v19.zip), which is what I have now. Still same the problem. I've cleared up the CMOS several times, after most of these flashes (but not all).
Starting a fresh XP install results in the same BSOD after first reboot (after copying files to the disk). I also booted up (in 1.A0/1.10) an old Linux Ubuntu Live CD, which gave this warning:
"Warning! Your PnP BIOS caused a fatal error. Attempting to continue. You may need to reboot with the "nobiospnp" option to operate stably. Check your vendor for an updated BIOS. get_dev_node: unexpected status 0x28"
I'd be grateful to any suggestions!
The system in question: P35 Neo-FI, Core 2 Duo E4500, 2 * 1 GB Kingston DDR2 800, MSI Radeon HD 4670, Samsung 1614N IDE hard disk, an LG DVD drive, Corsair CX400 PSU.

make sure you change the settings for ide/sata settings in bios.

NEED HELP w/ P35 Neo Combo and Windows XP Install Stop 0x24 error BSOD

First a little background, in case it's relevant:
I was running a 865PE Neo2 with 4 x 1gig Corsair DDR2 6400. Otherwise, same specs as below. Ran it for 2 years without a hitch, then got a virus that corrupted my profile and had trouble booting, logging on, and persistent virus messages. Long story short, I fried the BIOS and decided to replace the mobo and upgrade the memory, keeping the rest of the system intact. I previously had windows installed on both partitions of the HDD but changed the name of the directory for Windows on the C: drive so it would boot from the D: drive.
I have replaced 865PE with the P35 and changed the boot sequence to boot from CD. The BIOS loads fine, and I get to the windows setup screen ok. Whether I opt for Recovery Console, or a new install of Windows, I get a BSOD error message below.
STOP: 0x00000024 (0x001902FA, 0xf7906700, 0xf7906400, 0xf7103bef)
ntfs.sys Address F7103BEF base at F709f00, Datestamp 3d6de5c1
I tried with both new and old memory (in the right slots) and get the same message. I booting with no memory because I read in another post that the system should beep to indicate no memory and there was no beep.
BIOS recognizes the HDD, CPU and Memory so not sure what the problem is. Should I try taking the HDD out and reformatting it on another PC? (not easy since I don't have another desktop pc) Please help with some suggestions. Thank you.
System Specs
P35 Neo Combo Mobo
BIOS ver 1.3
E6400 Intel Dual Core
1 x 2 gig Crucial PC3 8500 DDR3 1066 mhz
nVidia 8800 GTS graphics
WD 250 gig Sata HD w/ 2 partitions of 125 ea.
Antec 500W SmartPower PSU
Installation disk is Windows XP Pro sp1

STOP: 0x00000024 indicates corrupt NTFS file system on the hard drive
Reformat would be the best thing to do. Download WD Data Lifeguard for your HDD, make the disk and run it.
http://support.wdc.com/product/download.asp?level1=6&lang=en
Quote from: FlyingSteve on 18-August-09, 10:29:00
I didn't know that the P35 Neo board ran ddr3...
That's where the 'Combo' part in the name comes into play, 2 DDR2 or 2 DDR3.
From MSI description of MB:
Main Memory
• Supports two unbuffered DIMM of 1.8 Volt DDR2 667/800 SDRAM. (Max: 4GB)
• Supports two unbuffered DIMM of 1.5 Volt DDR3 800/1066 SDRAM. (Max: 4GB)

P35 Neo Combo, boot problem? [FIXED]

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

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

MS-7360 (P35 NEO-F) bios ver 1.10 + INTEL Q8400 CPU

Similar Messages

Maybe you are looking for