Computer not booting into Windows 7 after update.

Hey, it's me Jesus again. After this update,

Update for Windows 7 for x64-based Systems (KB974431)

Installation date: ‎10/‎17/‎2009 9:24 AM

Installation status: Successful

Update type: Important

This is a reliability update. This update resolves some reliability issues in Windows 7. By applying this update, you can achieve better reliability in various scenarios. After you install this item, you may have to restart your computer.

More information:
An update is available to improve the stability and reliability of Windows 7 and of Windows Server 2008 R2

Help and Support:
Microsoft Help and Support

I am not able to boot into windows. I get to the Windows loading screen, and the computer doesn't start. It apparently is not liking my overclocked computer all of a sudden, which was working fine in Windows 7 for MONTHS! I did not change the clock speed. It was still the 3.2Ghz for my Q9450. The ram is set on auto timing. Disabling or enabling EIST and C1E doesn't help. The computer boots just fine at the default clock of 2.66Ghz or when I revert to before the update. The computer was booting just fine before that stability update.


Specs of computer.

------------------
System Information
------------------
Time of this report: 10/19/2009, 16:07:59
Machine name: CHRIS-PC
Operating System: Windows 7 Professional 64-bit (6.1, Build 7600) (7600.win7_rtm.090713-1255)
Language: English (Regional Setting: English)
System Manufacturer: OEM
System Model: OEM
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz (4 CPUs), ~3.2GHz
Memory: 2048MB RAM
Available OS Memory: 2046MB RAM
Page File: 1109MB used, 2983MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7600.16385 32bit Unicode

Jesus said:

The computer boots just fine at the default clock of 2.66Ghz ...

So let's recap: when you don't use the hardware in a way which pushes it outside its design envelope, then everything is fine. But when you do overclock, then it all goes belly-up.

Hmm.

Jesus said:

The computer was booting just fine before that stability update.

Your dad works in mysterious ways.

Disable the OC, boot, then...

Option 1 - rollback the update and repeat orig OC settings.

Option 2 - keep the update and re-do a new set of OC settings.

H2SO4 said:

Jesus said:

The computer boots just fine at the default clock of 2.66Ghz ...

So let's recap: when you don't use the hardware in a way which pushes it outside its design envelope, then everything is fine. But when you do overclock, then it all goes belly-up.

Hmm.

I definitely understand this, but the OC was working great in Windows 7 for months, the update seems to have,for whatever reason, made 7 not boot with my OC.

H2SO4 said:

Jesus said:

The computer was booting just fine before that stability update.

Your dad works in mysterious ways.

Maybe I'll speak to him.

Jesus said:

I definitely understand this, but the OC was working great in Windows 7 for months, the update seems to have,for whatever reason, made 7 not boot with my OC.

Kudos for absorbing my pre-caffeine "I-was-woken-prematurely" customer service manner without flinching :)

Because of various inter-dependencies, updates like this one tend to bring a whole heap of reworked code with them. You can see from the list of what's included in the update that there's like at least a dozen new files.

Their processing and memory requirements will be subtly different to the executables they've just replaced. In some cases, that's sufficient to expose flaws in underlying hardware. For example, if memory address "8" is unreliable but the code only ever uses 1 through 7, then you can go for years without encountering a problem. Now change that code to use 1 to 3 and 6 through 9 and - boom!

Despite Antman's optimism (@Antman: thanks for being nice for me :)), I don't think you've got much choice - you have to revert back to known-safe (non-OCed) settings. Every update from now on which includes any of those files is likely to include most or even all of them, thereby bringing with it a repeat of the problem should you choose to install the update. Therefore, a reworked version of "Antman's Options" would look like this:

Option 1 - Roll back the update and stay away from any and all future updates involving those files, at least until SP1 (and perhaps even afterwards), in order to protect your ability to OC.

Option 2 - lose the OC, install the update, and have a more stable and safer OS.

I think I have pig flu. My sudden sense of mortality has tempred my broadened my world view and tempered my tongue. Thank you, acidic one, for giving detail to the obvious.

Antman said:

I think I have pig flu. My sudden sense of mortality has tempred my broadened my world view and tempered my tongue. Thank you, acidic one, for giving detail to the obvious.

I hope you feel better soon. The whole situation has me quite concerned for my family.