Greetings football crazy people,

I watched seven -- count 'em, seven -- games last week. Two were awful (Stanford-Oregon State, Michigan-Michigan State), two were semi-good (Arizona-WSU, ASU-Washington), and three were fantastic (UCLA-Colorado, Penn State-Ohio State, and USC-Utah). My right hand is suffering from feverishly taking notes on absurdly small slips of paper. I do not recommend this.

This week we're going to play Yea or Nay, using my guesses from last week as a springboard to discuss this week's results. (Guesses from last week in italics.)

Oregon @ Cal: Unfortunately for Cal, Oregon is hitting its stride. If Mark Helfrich had no conscience and was willing to let Oregon's starters play the entire 60 minutes, the Ducks could put up 80 points. Easily.

Yea or Nay: YEA (mostly)

Oregon 59, Cal 41

Yes, Oregon put up its requisite 40/50/60 points. What is concerning is that Cal almost kept pace in this game. It was 52-35 entering the 4th quarter -- difficult, but not insurmountable (if you don't believe me, ask Colorado and Penn State, who trailed UCLA and Ohio State by 17 points, respectively, in the second half this weekend, only to force overtime in both games). Cal recorded 30 first downs (30???) and 560 yards of offense.

It's a win for Oregon, but the defense is a question mark. The offense scored 59 to bail out the defense this time. The offense isn't scoring 59 points against Stanford this weekend.

The winner in this game? Vegas. They had Oregon as 18-point favorites. I'm impressed.

Michigan State 35, Michigan 11: so long, Brady Hoke.

(Yes, I'll sprinkle in a few results from around the country just for variety.)

UCLA @ Colorado: The Bruins should win, but they've been turning it over with alarming frequency recently. If CU can find an interception here and there....

Yea or Nay: YEA

UCLA 40, Colorado 37 (2 OT)

I had a bad feeling about this game. UCLA had been dodging bullets while underperforming all season, while Colorado had been building toward a breakthrough game for the past year and a half. If the Bruins didn't play intelligently, CU had a shot at the upset.

Sure enough, UCLA did what it could to keep the Buffaloes in the game. Despite a strong start, the Bruins made several mistakes in the first half:

• On a third-and-goal play, UCLA forced an incompletion, but a roughing penalty allowed Colorado a first and goal at the 4, leading to a touchdown instead of a field goal attempt.

• Defensive holding negated two consecutive interceptions (!) and led to another Colorado touchdown.

• Another Brett Hundley fumble should have led to at least three more CU points, but the Buffaloes mismanaged the clock at the end of the half and came away with nothing.

The Bruins were up 24-14 at the half, and extended the lead to 31-14 with about two minutes left in the third quarter. It is at this point that good teams slam the door shut so that upstart underdogs don't sniff any chance at an upset.

UCLA, by this definition, is not a good team.

Colorado converted on 4th down to score a long touchdown, then scored again to cut the lead to 31-28. UCLA's offense disappeared in the 4th quarter, and when Colorado forced another punt midway through the period and had the ball near midfield, it looked for all intents and purposes like the Buffaloes were going to ride the momentum to a glorious victory.

But then, Marcus Rios -- for the second straight week -- saved the day. He intercepted Sefo Liufau to give the Bruins the ball with a few minutes remaining. The offense did not need another score; they simply needed to rack up a few first downs and run out the clock.

They did not.

I usually filter my in-game commentary before doing the weekly writeup, but in this case I'm going to give you my raw thoughts, as it may help you envision the steam coming out of my head as the game was progressing:

UCLA's offense didn't look good in the second half. Should have put this game away by halftime, or at least by the third quarter; did not. Fortunate CU did not get a field goal to end the first half. Fortunate Rios intercepted with CU having momentum midway through the fourth quarter. Fortunate to get roughing the passer penalty on failed 3rd down conversion to extend drive in late fourth quarter. Fortunate not to lose game as a result of offense [read: coaching] after too predictable 4th and 1 call at Colorado 21 was stuffed for a loss -- the same play formation vs. USC last year on 4th and short -- UCLA ran right into the teeth of the defense from a bunch formation. No space. MATH, people. Fortunate Colorado dropped a 3rd and 2 pass late in the game from the UCLA 18, forcing only a game-tying field goal attempt with 36 seconds to go. 31-31, overtime.

With game on the line, offense had a chance to seal it. Didn't. Defense had a chance to seal it. Didn't. Overtime.

UCLA fortunate their field goal in the first overtime just made it. Finally won in double overtime after two Hundley runs. This was an escape.

You get the picture: UCLA was fortunate (yes I like that word) to win this game.

Oregon State @ Stanford: Bad timing for the Beavers, as Stanford is coming off the deflating loss to ASU. I expect this game to be low scoring and spectacularly ugly, but with Stanford coming out victorious.

Yea or Nay: TOTALLY YEA

Stanford 38, Oregon State 14

Time for a math equation: BSSSPA = 1000 x ES.

Didn't figure that one out? OK, let me help you. Beautiful, sun-splashed Saturday at Palo Alto equals thousands of empty seats.

Welcome to northern California, where we take fair weather to a whole different level.

Unlike UCLA (the recalcitrant teenager who needs a good sharp kick in the pants), Stanford is the unwanted puppy who requires lots of care and attention. "Good Stanford!" I was murmuring to myself after the Cardinal scored on their first drive. "Oh, Stanford," I lamented when Kevin Hogan threw an interception on the next possession. "Bad Stanford, bad Stanford!" I yelled when Hogan threw a second straight interception that led to a 7-7 tie in the first quarter.

Hogan atoned for this with a nice QB run for a touchdown, though, and Stanford eventually got its offense going in the second quarter to go up 28-7 (!) at the half. Stanford's defense forced a Beaver punt early in the third quarter, which was taken by Ty Montgomery at midfield.

Montgomery had a bad game against Arizona State last week, but that was when he was trying to field punts over his shoulder. This one he fielded normally. Oregon State punted to him because...well, I suppose because they wanted to be put out of their misery as quickly as possible.

Touchdown Stanford, game over.

So what did we learn, class?

Stanford's defense is still great; Oregon State isn't very good at all. The Cardinal outgained Oregon State 344 to 84 in the first half. This game was similar (in score and feel) to USC's 35-10 thrashing of the impotent Beavers at the Coliseum earlier this month.

Football experts might attribute the Cardinal's improvement on offense to a simplified approach, but the real reason? The recent de-tonguing of the Stanford Tree. By maintaining a modicum of decency, the Tree has allowed Stanford's offense to focus on the fundamentals of football. Anyone who advances an alternative opinion does not understand the mystical element of the game.

Speaking of mystique: next up for Stanford is.............Oregon.

Can Stanford do it again?

Probably not -- it's Oregon, Mariota is healthy, and it's at Autzen -- but here are three reasons why it could happen:

• Stanford's defense will keep the Cardinal in the game against anybody.

• Oregon's defense just gave up 41 points to Cal.

• Stanford has scored two straight huge upsets over the Ducks and won't be intimidated.

• The Tree is no longer indecently exposed.

Hey -- how did that fourth one get in there?

Please, for the love of all that is good and pure, Oregon: DON'T BLOW IT AGAIN. I don't like rooting for you (it feels almost evil), but you have to win this one.

TCU 82, Texas Tech 27: 82? 82??????????

Arizona @ WSU: A horrible draw for the Wildcats. WSU will be desperate, and Arizona's defense has hardly been airtight this season. Then again, this is Washington State....

Yea or Nay: mostly NAY

Arizona 59, WSU 37

I should have focused on "then again, this is Washington State."

WSU was down 31-0 in the second quarter, so you know I was happy. Arizona extended the lead to 52-16 before three window dressing touchdowns made the final score more respectable, but make no mistake: this game was all Wildcats -- offense, defense, and special teams.

Anu Solomon (who is certainly not playing like a freshman) went 26 of 38 for 294 yards, five (!) touchdowns, and no interceptions. Meanwhile, Scooby Wright III had eight tackles, three sacks (!), and a ridiculous three forced fumbles -- WOW!

This weekend, the Wildcats get UCLA at the Rose Bowl. Arizona has already beaten mighty Oregon at Autzen and just put up a bazillion points against WSU. UCLA barely survived against Cal and Colorado the past two weeks.

Conclusion: UCLA will crush Arizona.

Say what?

OK. Let me first preface this by saying that this is a gut feeling, not a "scientific expectation." UCLA should be favored by about a touchdown (and is); the odds makers are expecting a reasonably close game (which it may well be). But my hunch is that Arizona has already hit its peak (win over Oregon) and had its share of good fortune (Hail Mary win over Cal) and favorable scheduling (UNLV, Texas San Antonio, WSU) while UCLA has reached its low point (losses to Utah and Oregon) and has survived a rough stretch (narrow wins over Cal and Colorado). UCLA has yet to put all the pieces together this season, but when they do, it will be bad news for their opponent.

My gut tells me that opponent will be Arizona, and if UCLA lets loose like I'm expecting, they will score early and often, and the game will be over fast. UCLA dominated their last two games but allowed their opponents to stay close due to miscues. If the Bruins start fast, this time I think they will slam the door. I also believe Arizona is due for a "mystery" game. We shall see.

Ohio State 31, Penn State 24 (2 OT): Close, Penn State. I don't know how you scored 24 points in this game, but you made OSU earn it.

ASU @ UW: The Fraudulent Bowl. We'll see if ASU can handle success (win vs. Stanford) or if UW can bounce back from a tough loss (vs. Oregon). I'm not sure if the battle will be strength vs. strength (ASU offense vs. UW defense) or weakness vs. weakness (UW offense vs. ASU defense). I'm actually hoping both teams lose. Somehow. No? Fine, I'll root for Washington. You can tell my heart is in it.

Yea or Nay: YEA

Arizona State 24, Washington 10

This was indeed a terrible game; both teams should have lost. Unfortunately, that didn't happen.

The Sun Devils led 10-0 at the half. With wind swirling everywhere, passing and kicking were, shall we say, an adventure.

The second half, however, was interesting -- albeit for all the wrong reasons. Following a forced fumble, ASU had the ball first and goal on the Washington 1 yard line. The one. I said the one yard line people. First and goal. From the one.

NOTHING. On fourth and goal, Arizona State ran RIGHT AT UW -- like the Bruins earlier in the day, ASU was in a bunch formation -- and, surprise! They suffered the same fate.

I am so disgusted with coaches making this stubborn, stupid call -- first David Shaw (numerous times), then Jim Mora (vs. Colorado), and now Todd Graham -- that I am seriously considering putting together a math workshop, free of charge, to Pac-12 football head coaches. How hard can it be to understand that when the defense has 11 people stacked in a tiny area, you are better off running AWAY from those 11 people instead of RIGHT AT them???? You have no space! The field is over 50 yards wide. USE IT! And stop tipping your hat to the defense, which makes their job far easier!

Grrrrrrrrrrrrrrrr.

The result of ASU's 4th down play was not only predictable, it was comical. The running back tried a dive, but he didn't even get to jump: the defense had already converged on him before he could get any elevation!

Thus, instead of finishing the game early in the third quarter with a 17-0 lead, ASU allowed UW a glimmer of hope. Washington took advantage on ASU's next possession when a poorly thrown ball by Taylor Kelly resulted in an interception that was returned, untouched, for a score.

Suddenly, it's 10-7 and we have a game.

Washington tried to give the game back to ASU by throwing an interception of their own, but the Devils had a bad snap on a 27-yard field goal and didn't even get to attempt it. As a result of this ugliness, UW somehow managed to tie the score at 10 with 7:14 to play.

The Devils ended up winning the game with a late touchdown drive followed by a clinching pick six, but I had seen enough. My final note during this game: FRAUDULENT CITY. Washington is 5-3 but should have a losing record. ASU, despite just 14 first downs and under 300 yards of offense in this game, is miraculously 6-1 and unfortunately, somehow, controls its destiny in the South.

Please, Utah, find a way to beat the Sun Devils on Saturday.

USC @ Utah: If you're only going to watch one game this weekend, this is the one to watch. On a neutral site I'd probably lean toward USC, but at Utah...oh boy, this is going to be a good one. Whoever avoids major mistakes should win. Both teams have solid defenses. I don't think Utah can play a second near-perfect game like they did against UCLA; furthermore, the Utes are facing some offensive challenges (who's the QB?). USC looked great at Arizona but has had problems closing out games. Can you tell I'm uncertain? WATCH THIS GAME!

Yea or Nay: BINGO!!!!

Game of the Week

Utah 24, USC 21

I TOLD YOU TO WATCH THIS GAME! All the wonderful things I had hoped would happen came to pass, and then some:

• Both teams made major mistakes, but they were distributed evenly throughout the contest. Thus, although it may not have been the cleanest game, it was wildly entertaining.

• Both defenses came to play.

• Utah did not play a near-perfect game like they did against UCLA, but their "C" game was good enough (barely) against USC's "C" game.

• Yeah, I nailed that one: USC continues to have problems closing out games.

• I was uncertain about the winner for good reason: the winning score occurred with eight seconds to play!

So far, at least in my opinion, this was the game of the season in the Pac-12. If you missed the game but you've read this far, you're in luck: it's time for my frenzied play-by-play notes, along with my commentary on my commentary. (Yes, I have a habit of talking to myself. That's my sister's influence.)

CRAZY first half! USC's second play from scrimmage: a dropped pass. No, a lateral! The ball is live! Why is everyone standing around? No whistle! SOMEONE GET THE BALL! Oh, it's Utah? Kessler runs after him...too late! Touchdown!

What a way to start the game!

USC: nice drive to tie it at 7. Utah: nice drive in response, but two fumbles inside the 5 yard line by Booker -- second one lost -- resulted in no points. Oooo, bad. 7-7 after one.

USC drives to Utah 27. 4th and 1: Kessler fumbles the snap; no conversion -- due perhaps to going under center after going the rest of the game in shotgun. But no matter: Utah drives to the USC 8 and fumbles FOR THE THIRD TIME (this time by Bubba Poole). Recovered by Utah, but only a field goal. 10-7 Utes.

Major mistake count: USC 2 (lateral, fumbled snap), Utah 2 (two fumbles inside the 10 yard line).

USC response: Adoree Jackson, six yards deep in the end zone, ignores #9's advice to down it, and promptly scampers 100 yards UNTOUCHED for a TD!

Exhilarating!

14-10 Trojans at the half.

Third quarter: punt fest. Kaelin Clay (to whom USC never should have punted) returns one punt to the USC 16. Then, on 3rd and 6 from the 12, one of the plays of the game: Utah passes complete, down to the 1 yard line. The receiver is ruled down, but the call is (correctly) overturned on replay: Adoree Jackson (!) forces the fumble and recovers for a touchback.

Adoree Jackson played lights out in this game for USC. With huge plays on defense and special teams, he nearly won the game for the Trojans on his own.

Utah: 3 red zone possessions, 3 points.

Yikes! Those numbers are eerily similar to the debacle which befell Stanford against USC early in the season. At this point, I was thinking SC was going to win the game.

But then: Kessler throws behind Agholor on a 3rd down play. Tipped -- intercepted! Utah converts turnover into a TD. 17-14 Utah after three.

How would Kessler react?

With a magnificent, courageous 75 yard TD drive that included two near-miraculous completions as he was being crushed by the Utah defense. Buck Allen chipped in with several good runs, but it was Kessler -- especially on third down -- who allowed the Trojans to reclaim the lead at 21-17 with 10:18 to play.

Kessler was astounding in this game, but that should not surprise anyone: he has played well all season. He deserved to win the ASU game, but his defense -- and coach -- let him down. Would they be able to hold up their end of the bargain this time around?

USC's special teams bailed out Sarkisian when the Trojans, incomprehensibly, elected to kick off to Kaelin Clay following the touchdown -- after he had returned the previous punt over 50 yards to set up the previous score. Clay had a shot at a long runback but was tripped up at the 32.

If Clay had returned the kick for a score (or set up a TD with a long runback), the coach would have been vilified -- and for good reason. I warned Trojan fans last week that although I was sold on Kessler, I wasn't sold on Sarkisian, particularly in close conference games....

Utah punted; USC took over at the 11; Kessler completed another clutch 3rd down to extend the drive.

My Kessler-ometer was going crazy.

Utah finally got it back at the 28 with 2:08 to play after USC nearly missed on both 3rd and 4th down.

Note: given the circumstances surrounding USC's kicker (not 100%) and the fact that a first down would have won the game, I agreed with the decision to go for it on 4th and 2. I further liked the play call: fake the inside handoff (i.e. NOT into the teeth of the defense -- learn the lesson, coaches), pitch outside to Agholor for a speed rush to the corner. The play call should have worked; it was only Agholor's lack of field awareness (he stepped out of bounds before getting the first down) that prevented USC from sealing the win.

I still thought USC had it, but I was wrong. Utah, as they had done to UCLA, executed their final drive flawlessly, putting in the winning TD with 8 seconds left.

A miserable loss for the Trojans -- but all is not lost [see USC's remaining schedule]. Utah can find two more losses, and if USC beats WSU and Cal, it could still be USC-UCLA for the South. We shall see....

Indeed we shall.

Coming Up

Washington @ Colorado: Don't be surprised if this is the game the Buffs break through.

USC @ WSU: Here's hoping the Trojans put WSU out of their misery and kill their dreams of bowl eligibility once and for all.

Stanford @ Oregon: I'm a bit surprised that Oregon is only an 8-point favorite here. But after the last two seasons, I should know not to talk about Stanford in this game, so...I won't.

Cal @ Oregon State: Who wants a bowl game? Both teams need this one to get a crucial 5th win.

Arizona @ UCLA: As stated earlier, I have a gut feeling that this will be a Bruin blowout. Wishful thinking, or rational enthusiasm?

Utah @ Arizona State: Stanford at Oregon will get the headlines due to the history, but this game is every bit as significant in the Pac-12 race. This might end up being the Game of the Week.

And this definitely ends up being the last sentence in the writeup.