COD4 WTF?

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

CoinOperatedBoy

Golden Member
Dec 11, 2008
1,809
0
76
Originally posted by: Atheus
Originally posted by: CoinOperatedBoy
Originally posted by: Atheus
Originally posted by: CoinOperatedBoy
Try resetting your CMOS and posting in the correct forum.

Try removing the stick from your arse and not posting at all.

Just busting your balls. But seriously, did you try resetting your CMOS?

As in reset the jumper and start from scratch? Not exactly - I loaded a slower config in BIOS though. Didn't help. Fairly sure it's a software problem.

That may be, but it would be wise to rule out the overclock as the source before you go digging deeper. If you note/save your settings, it should be trivial to redo them after some troubleshooting.
 

Atheus

Diamond Member
Jun 7, 2005
7,313
2
0
Originally posted by: CoinOperatedBoy
Originally posted by: Atheus
Originally posted by: CoinOperatedBoy
Originally posted by: Atheus
Originally posted by: CoinOperatedBoy
Try resetting your CMOS and posting in the correct forum.

Try removing the stick from your arse and not posting at all.

Just busting your balls. But seriously, did you try resetting your CMOS?

As in reset the jumper and start from scratch? Not exactly - I loaded a slower config in BIOS though. Didn't help. Fairly sure it's a software problem.

That may be, but it would be wise to rule out the overclock as the source before you go digging deeper. If you note/save your settings, it should be trivial to redo them after some troubleshooting.

Okay I'll do it...
 

Atheus

Diamond Member
Jun 7, 2005
7,313
2
0
OMG that bloody fixed it! Cheers!

I have no explaination for this... It can't have been the overclock... that would make the thing crash not run slowly...

Could it have been HPET or something else I disabled in BIOS? And the windows update affected the usage of that hardware?

Ramping up the overclock again to find out...
 

nakedfrog

No Lifer
Apr 3, 2001
63,061
19,366
136
Originally posted by: Atheus
OMG that bloody fixed it! Cheers!

I have no explaination for this... It can't have been the overclock... that would make the thing crash not run slowly...

Could it have been HPET or something else I disabled in BIOS? And the windows update affected the usage of that hardware?

Ramping up the overclock again to find out...

It sure seems like it could have been the O/C...
 

Atheus

Diamond Member
Jun 7, 2005
7,313
2
0
So, having found out it's not the HPET or anything like that, I reloaded my previous overclock settings and guess what? It works fine now...

... I conclude there are tiny little people inside my machine fucking with me. It's the only logical explaination.
 

Atheus

Diamond Member
Jun 7, 2005
7,313
2
0
Originally posted by: nakedfrog
It sure seems like it could have been the O/C...

How could an increase in processor speed, which has been fine for years, suddenly cause a game to run more [/i]slowly[/i], but without a loss in reliability?

I think the windows update is a far more likely candidate as the actual cause, since it happened about 2 minutes before the issue started. Clearly the hardware settings are related in some way though.
 

Atheus

Diamond Member
Jun 7, 2005
7,313
2
0
Originally posted by: HardcoreRobot
intentionally posting in the wrong forum should result in loss of posting privileges

Yes, posting in the right forum is essential, whereas helping people out is completely unimportant...

Oh wait that's backwards...
 

nakedfrog

No Lifer
Apr 3, 2001
63,061
19,366
136
Originally posted by: Atheus
Originally posted by: nakedfrog
It sure seems like it could have been the O/C...

How could an increase in processor speed, which has been fine for years, suddenly cause a game to run more [/i]slowly[/i], but without a loss in reliability?

I think the windows update is a far more likely candidate as the actual cause, since it happened about 2 minutes before the issue started. Clearly the hardware settings are related in some way though.

Beats me, but if it wasn't working when you're overclocked, and works when you're not, it's not too much of a leap to think that it's possible the OC was a contributing factor. Maybe an update changed the power consumption of an item, I don't know. There's a reason I quit poking about with overclocking :p
 

Atheus

Diamond Member
Jun 7, 2005
7,313
2
0
Originally posted by: nakedfrog
Originally posted by: Atheus
Originally posted by: nakedfrog
It sure seems like it could have been the O/C...

How could an increase in processor speed, which has been fine for years, suddenly cause a game to run more [/i]slowly[/i], but without a loss in reliability?

I think the windows update is a far more likely candidate as the actual cause, since it happened about 2 minutes before the issue started. Clearly the hardware settings are related in some way though.

Beats me, but if it wasn't working when you're overclocked, and works when you're not, it's not too much of a leap to think that it's possible the OC was a contributing factor. Maybe an update changed the power consumption of an item, I don't know. There's a reason I quit poking about with overclocking :p

I'd be agreeing with you but I already raised my overclock back where it was and the game is still fine. Basically I fixed this issue by doing a whole bunch of stuff, finding that none of it helped, then putting it all back how it was when the issue started...

... screw it it's working now. Thanks for the help everyone.
 

Phoenix86

Lifer
May 21, 2003
14,644
10
81
Originally posted by: Atheus
Originally posted by: Phoenix86
Originally posted by: Atheus
Originally posted by: DaveSimmons

Blackouts, memory loss -- sounds like it's time for you to cut back on the drinking.

That's a seperate issue :D

Come on people help me out - I am NOT reinstalling windows again.

I know the fix, give me a few minutes...

Now THIS sounds promising...
Hook/line/sinker.

;)

Though I'm not an ass, just wanted to make you wait. Good to see you got it fixed, check your ram timings.