First Time OCing - Issues I've got...

Associate
Joined
19 Feb 2009
Posts
3
Ok, so I'm a first time poster here so please be gentle!

I've posted this in the OC forum as these queries relate to my first attempt at OCing but if the mods feel it would do better elsewhere, please move it!

Right, so after reading various forums and reviews I purchased the components for my first home build.* I'd done a bit of reading about Ocing and figured I'd get suitable components that would hopefully allow me to have a bit of a play around at a later date.* In the end I went for:

MSI P43
E7300
2 x 2GB Corsair xms2 DDR2 6400
Arctic Freezer 7 pro
WD 500GB hardrive
4830 Graphics card
Arctic Cooling PSU (650w I think)
Mhel case (one rear fan and one side)
Vista ultimate

The build went well considering it was my first and was happy with the results but after a couple of months, I thought I'd have a crack at getting it to run a bit faster.

I'll also point out that right before I started to try OCing, I installed the 160GB hard drive from my old PC (complete with XP) into the new case to copy some of the data over.* I'm not sure this is relevant to the problems I'm having but figured I might as well tell you good people everything in
case there's something I haven't considered!

So my pal came round who OCed his rig a while ago to help me out (I'd read the stickies here which were very helpful too) and we disabled the EITS (is that what it's called? The speedstep thing) and increased the speed up to 275 and 280, running prime 95 and all was going well (reducing the memory speed to below 800 each time).* My pal who has a short attention span googled to see what others were getting with the same chip and went straight to 3.4.* Running Prime at that speed caused the second core to crash almost immediately.* Lesson learnt!

I think the next bit is in the right order (there have been a lot of restarts!).* After it crashed I think he had to load the optimised settings in the BIOS and start from scratch and we went back to 2.9 and went up in intervals of 0.05 up to 3.3, testing prime for 30 mins (CPU temp from core temp is maxing out at about 44).* At 3.3 the other core crashed almost immediately.* After this happened, at startup, it said "overclocking attempt failed, do you want to restart with optimised settings or the last settings" (words in red to that effect anyway, I'm sure you folks have seen that screen before!) and I went with "last settings" and reduced it to 3.25 and ran prime for longer and the first core crashed again after about 75 minutes.* I tried to start again from the "last settings" when the screen came up but then it froze with the power and HDD lights on.* After a hard reset it wouldn't boot at all so I powered down, moved the jumpers to clear the CMOS, left them for a few seconds, moved them back and rebooted and it booted back into windows (slowly) and the speeds appear to have been reset (although the EITS was still disabled)

I've now got a few problems which have started at different times in this process (not exactly sure when I'm afraid)

1 The date and time in the BIOS resets itself almost every power down (not every time though)
2 When I save and exit from the BIOS it freezes again (with no video input but power & HDD lights are on) and I have to power down from the button (once it went straight into the windows sequence and another time it went off as soon as I touched the button rather than it having to be held for the 4 seconds or whatever).* Sometimes it needs two goes to get it back up and running and one time it froze in the BIOS screen and needed a hard reset.
3 I'm unable to restart from windows, it logs off then freezes with no input to the monitor but power and HDD lights are on and needs a hard reset.* I've taken to shutting down and then powering up which is a bit annoying. I have changed the relevant settings in Vista.
4 After a couple of the hard resets I've left it to see if it will boot windows up and it's booted up XP from the other drive as it's changed the boot order (the new drive is SATA and the old one is IDE, would the BIOS prioritise the IDE drive?)

I guess the first question is, does it sound like I've overcooked one/some of the components or can these things be fixed in the BIOS/somewhere else?
Any other suggestions for the issues above?

I can adjust the CPU multiplier (down) but I didn't establish the max FSB for the chipset, I just went straight to increasing the speed on the CPU (and changing the RAM multiplier accordingly).* Will this have had an impact on the results?*

I was originally just hoping to increase the speed a bit to feel like I got some extra performance for nothing but I find the whole thing quite interesting (and frustrating!)!

Many thanks if you've got to the end of this essay!* Would really appreciate any help on offer from those with more experience than me!

Cheers
 
Welcome to the OcUK Forums mate :D

Take a look at this:

http://forums.overclockers.co.uk/showthread.php?t=17612922

Whilst I have a good look at you details.

Right then:

Have you tested you RAM using Memtest? Might be a RAM problem.
Have you tried a BIOS update if there is on available (Manufacturer's website)
Reseat and repaste the CPU & HSF
Return all settings back to stock
increase the FSB in 5MHz increments until you hit instability. ONLY then should you start fiddling with voltages :D

Some useful tools for you:

http://www.cpuid.com/cpuz.php

http://www.memtest86.com/

http://www.alcpu.com/CoreTemp/

More in the OcUK Forums Overclocking Guide at the top of this reply :D

See how you get on with that and yell if you need us :D
 
Good man, thanks for the welcome & quick reply!

I've been using cpu-z and core temp but don't really know what I'm looking for apart from high temps (cores are 43 & 44 currently - prime95 has been running for about 2.5 hours @ 3.15). Will try memtestest and see what happens (Jokester's sticky suggests prime blend is better..?)

Will report back once I've had had a play around!
 
When you overclock and get a failed attempt it means your CPU is giving out the wrong information. This can (although almost never does) cause issues with Windows. A fresh install on a stable overclock should fix this.

The bios issues sound odd - have you tried loading optomised defaults directly from the BIOS menu?
 
You guys are gonna regret talking to me...

AndyOcUK:

Ok - Memtest, made a dvd from the iso image and booted up with it in - it cycles round, rebooting. The screen with the text isn't up long enough for me to establish if anything's different from the time before though.. Is this normal? Went into the config screen to see if there was anything in there and then it froze. WOuld my wireless keyboard and mouse make a difference? I'm guessing not as it recognised the keystroke to get into that menu in the first place...

Attempted a BIOS update but MSI's Live Monitor comes up with a "updatemonitor MFC application has stopped working" messgae from windows. Did a quick search on here and it would appear that it's not a good idea to try this through windows so tried the manual download and the web. The text document is confusing- AMI or award bios, how do I tell?

On the plus side - cheers to Chris too - I optimised the defaults in the bios and it appears to have fixed the booting up issue after saving and exiting the bios. Incidentally, the long boot into windows only happened the once so hoping it was just a hiccup!

No thermal paste here at the moment so can't reseat currently...

Any thoughts/suggestions gratefully received! Cheers
 
I am not at all familiar with your board, but....
Firstly, I would not recomment updating your BIOS via windows. Always do it DOS mode or use a flash utility such as AWDFLASH or whatever program is supported by your board.

Secondly, when flashing your BIOS only have your bare minimum installed, i.e. 1 stick of ram etc.

I had some wierd BIOS issues with my Striker II Extreme. I "think" it was because I flashed my BIOS from windows using ASUS utility. Whenever I crashed, the motherboard would entirely corrupt my OS boot hard drive, and fail to recognize it completely.

I am not suggesting flashing the BIOS, I am merely saying that I had wierd issues with my board, and a clean flash did the trick for me anyway.
 
Back
Top Bottom