Odd OC problem -- Not for noobs

[Thor86]

1.35Vcore is pretty high load for any boards with i7s. You need to make sure you have ample mobo cooling (Spot cooling fan comes to my mind, pointing it directly on the chokes/nb).

 

[Gillbot]

Could it be a corrupt OS due to the crash?

 

[Spikesoldier]

Could it be a corrupt OS due to the crash?

im leaning towards this as well

sometimes windows can take a shit whenever OC limits are pressed and corrupts the OS.

I would suggest a HDD test since that has not been done yet and then a new XP load and see if it is still screwing up.

 

[Gillbot]

Yeah, toss a spare drive in if you have one and reload the OS. that would tell you if it's the OS causing the crash.

 

[Rubycon]

Yeah, toss a spare drive in if you have one and reload the OS. that would tell you if it's the OS causing the crash.

This is why I have a velociraptor in the drawer with a good copy of 7 running on it. I also have the good running version on a TIB file (Acronis) in case it gets hosed. It's also nice for testing to get back up and running fast as the SAS BIOS takes a bit of time to initialize.

Just grab a SATA drive, load your fav OS on it with a folder with all your testing goodies and you're golden. I like Win 7 because I can switch hardware and it does not mind much particularly if going between ATA and AHCI mode, etc.

 

[TJCS]

@Markfw900

I also have the ASRock x58 Extreme, and it seems like we are experiencing a similar lockup issue. I found a solution that worked for me, which is to downgrade the bios to v1.20.

I actually started a post not too long concerning this issue with much more details here.


​

 

[Gillbot]

This is why I have a velociraptor in the drawer with a good copy of 7 running on it. I also have the good running version on a TIB file (Acronis) in case it gets hosed. It's also nice for testing to get back up and running fast as the SAS BIOS takes a bit of time to initialize.

Just grab a SATA drive, load your fav OS on it with a folder with all your testing goodies and you're golden. I like Win 7 because I can switch hardware and it does not mind much particularly if going between ATA and AHCI mode, etc.

I'm still old school, I keep a spare drive and winXP images in ghost format!

 

[Rubycon]

I'm still old school, I keep a spare drive and winXP images in ghost format!

Ghost is good but I converted to Acronis a few years ago when (Ghost) would not support partitions > 999GB. I ran a fairly early version in DOS. It also stop recognizing high end hosts.

 

[Kyanzes]

Could be due to a failing capacitor on the motherboard.

You could try and set the Vcore to 1.35 and try to run the CPU at stock speed. If the board is able to sustain the Vcore then it should work flawlessly without any lockups.

 

[DominionSeraph]

This is why I have a velociraptor in the drawer with a good copy of 7 running on it. I also have the good running version on a TIB file (Acronis) in case it gets hosed.

I just load a copy into long-term memory. When my rig goes down... I reminisce.

 

[Markfw]

OK, well just for grins.... I am at 3.33 for 6 hours and counting, everything @ stock except 166 blck.

 

[DrMrLordX]

any aftermarket software that checks that ? Also, it will run even 3.9 for 12-18 hours before it locks up

Speedfan should be able to monitor PWM temps if your mobo has a sensor for that. The fact that you have stability for such a long period of time is certainly interesting . . . but until we can get some feedback on PWM temps @ load (at any speed), it'll be hard to make any further assumptions.

 

[Gillbot]

Ghost is good but I converted to Acronis a few years ago when (Ghost) would not support partitions > 999GB. I ran a fairly early version in DOS. It also stop recognizing high end hosts.

My old version of Ghost doesn't support vista or 7 either.

 

[Rubycon]

I don't know of any software that shows VRM temp outside of the EVGA software. That (Classified) is the only board that I've used that reads VRM temp in BIOS as well.

 

[Markfw]

OK, here is a speedfan screenshot, and the latest. I left everything in bios alone, except blck to 166, so I have been at 3.33 ghz for a day now, no worries. And coretemp says my cpu temps range from 49 to 53.

I think I wait for a day and try 180. Maybe it didn;t like the vtt (1.3) and pll(1.86) that aigo told me to add....

 

[Rubycon]

[IMP]http://pics.bbzzdd.com/users/markfw/speedfan_920_333.JPG[/IMG]

OK, here is a speedfan screenshot, and the latest. I left everything in bios alone, except blck to 666, so I have been at 3.33 ghz for a day now, no worries. And coretemp says my cpu temps range from 49 to 53.

I think I wait for a day and try 180. Maybe it didn;t like to vtt and pll that aigo told me to add....

I'm sure you mean 166 as 666 would be a record setter.

 

[Markfw]

I'm sure you mean 166 as 666 would be a record setter.

Fixed...

So what do you think ???

 

[Rubycon]

Fixed...

So what do you think ???

I usually don't touch PLL. At that OC VTT should be 1.25, no more. Too much VTT will cause instability as well. You may want to stress it more using Linpack.

 

[mav451]

Ah this is great news. Yeah I thought 920's could do 3.6Ghz in their sleep with no voltage changes, so this sounds like things are back to normal

Agree with Rubycon, I don't think I've ever touched PLL either.

 

[zagood]

Maybe it didn;t like the vtt (1.3) and pll(1.86) that aigo told me to add....

Can't say from personal experience (I'm still on 775), but vtt looks pretty high to me. From OC guide here, "absolute maximum" is recommended at 1.21 (but I've seen higher from a lot of people).

edit - looks like Ruby beat me to it. Good to have backup though!

 

[Markfw]

Can't say from personal experience (I'm still on 775), but vtt looks pretty high to me. From OC guide here, "absolute maximum" is recommended at 1.21 (but I've seen higher from a lot of people).

edit - looks like Ruby beat me to it. Good to have backup though!

Maybe that was the whole problem....After a few days, will try 3.6.

 

[DrMrLordX]

OK, here is a speedfan screenshot, and the latest. I left everything in bios alone, except blck to 166, so I have been at 3.33 ghz for a day now, no worries. And coretemp says my cpu temps range from 49 to 53.

I think I wait for a day and try 180. Maybe it didn;t like the vtt (1.3) and pll(1.86) that aigo told me to add....

You're running a different version than I have (mine is older), but I'd hazard to guess that Temp 3 is tracking the PWM temp sensor provided you're getting PWM sensor readings in your BIOS (my Abit nf-m2 nview reports PWM temps).

Is that at load or idle? That's pretty hot either way.

 

[Markfw]

ok, here is the latest. I wne to 3.6, but F@H was looking unstable. I had manually set the memory to 1440 (its rated 1600). I changed the memory to auto, and it decided that 1080 was what it should be, and I upped the vcore a shade(1.3 from 1.2375), now 3.6 seems stable.

Seems like it was a memory problem all along. It doesn't want to run @ rated speed. Not sure why it was fine for months,

 

[BTRY B 529th FA BN]

Seems like it was a memory problem all along. It doesn't want to run @ rated speed. Not sure why it was fine for months,

How do you test a DDR3 kits rated speed? I know how to do it on a 775 system. e.g. 500fsb will be synced with a DDR2 1000Mhz kit or aka 1:1 but what about DDR3?

 

[Markfw]

How do you test a DDR3 kits rated speed? I know how to do it on a 775 system. e.g. 500fsb will be synced with a DDR2 1000Mhz kit or aka 1:1 but what about DDR3?

In the bios, there is a setting for the memory divider. I got 1600 memory (runs 200 x 4 I think) rated, but right now its only running 135 x 4 I think (shows ddr 1080). Its all a little confusing to me, maybe someone else can set me straight if I am wrong.