Win7 Hotfixes

I came across a repository of Windows 7 hotfixes here. I do not recall exactly where I saw it but I also found a list of all Pre-SP2 (i.e. Post-SP1) hotfixes, that looked like this:

  • Windows6.1-KB2495523-x64
  • Windows6.1-KB2495655-x64
  • Windows6.1-KB2495786-x64
  • Windows6.1-KB2496290-x64
  • Windows6.1-KB2496820-x64
  • Windows6.1-KB2498993-x64
  • Windows6.1-KB2502789-x64

There was no description so, I created a simple Powershell script that attempts to scrape the title of relevant KB articles. It seems to work OK, so posting it here.

# Get-HotFixTitles
## I saved the file with a list of hotfixes in the current folder as hotfixes.txt
$no=gc .\hotfixes.txt |%{$null,$kbno,$null=$_ -split '-';$kbno} | %{$_ -replace 'KB',''}
$wc=New-Object System.Net.WebClient

$result = $no | % { 
            $url= $kb+$_
            $regex=[RegEx]'<h1 class="title">(.*?)</h1>'
            $title=$regex.Matches($content) | % { $_.Groups[1].Value }            
            new-object PSObject -Property @{ 
                kb    = "KB"+$_
                url   = $url
                title = $title
      $result |select kb,title| ft -a

###   or you may pipe the results to a csv if you prefer that
      $result |export-csv .\results.csv

I like dot sourcing when working with such stuff so I can slice and dice it further on the command line using the Custom Object I built:

. .\get-HotfixTitles

Then simply use $result. E.g.
$result | ?{$_ -match "GP"} |select kb,title | out-gridview


Windows 7 SP1 does not want to sleep

I received my Systemax machine a couple of days ago. It came with Windows 7 x64 Home Premium Edition. I downloaded Windows 7 x64 SP1 from MSDN and installed it. Last night, I wanted to put it into sleep and suddenly got a BSOD  "Internal_Power_Error"

I immediately suspected SP1 to be the cause b/c it had shutdown just fine the night before I installed SP1. There was not anything in the system logs to give me a clue. A bit of search on Microsoft sites shows that some people are seeing the exact same behavior after installing SP1 with similar specs[1]

At work, I use RSAT. So reading it in Directory Service blog that it was NOT possible to install RSAT after SP1 was already bad news for SP1, this just added to that bad taste.

There is documentation here to troubleshoot Internal_Power_Error. Interestingly, first param stops at x08 while in my case it was x09.

The other interesting bit was that crash dump file was not generated. This hotfix is supposed to fix that. I installed it and noticed that I could now put the machine into sleep. Problem was that it did not come back up from it.

Another suggested workaround was to disable "Allow Hybrid Sleep" in Power Options (see screenshot above). I tried that and and also changed the Bios Power setting so that 'hitting "space bar" would Power up the machine'. That seems to work for me. I can now put the machine to sleep and bring it back up by hitting space bar.

[1] Here are my specs:

  • Asus Sabertooth x58 Motherboard (common)
  • Intel core i7-950 3.06GHz 8M 1366 CPU
  • 12GB DDR3 1600MHz PC3-12800 Memory
  • 2 x 1GB Radeon 5770 Card in ATI Crossfire
  • 24x DVD-RW w/ Lightscribe
  • 1 TB 7200RPM SATA 3Gb/s Hitachi HD

Update (03/05/2011):
Microsoft now has a KB article titled 'Windows 7 does not go to Sleep'. It does not cover BSOD I had but has some good suggestions. I especially liked the Powercfg command line query and disable methods:

To see the list of all devices that can wake the computer, run the following command:
> Powercfg -devicequery wake_armed

HID-compliant mouse
HID Keyboard Device
HID Keyboard Device (003)
Realtek PCI GBE Family Controller

To disable a specific device from waking the computer, run the following command, or use Device Manager:

> Powercfg -devicedisablewake "devicename"


nVidia GTX 460, but which one?

A couple of days ago, I mentioned that my eVGA GTS 8800 512 had gone corrupted. Falcon Northwest techs replied to my e-mail (I love how informative and friendly their responses are) and confirmed that eVGA tech recommendation on GTX 460 would be a great replacement, it would fit in just fine if I got with a <9" card and my Power Supply Unit (PSU) should be able to carry the load just fine (It's 500Watts).

So, I started reading reviews on these cards. This review from is a bit dated but talks in great details about several GTX 460 cards and is a good read to understand the landscape.

Maybe conventional wisdom would dictate I go with a different brand than the one I had problem with. I did not. I loved how quite the card was. The fact that Falcon NW guys chose eVGA over others gave me more confidence. Plus, there is no such thing as never-failing-hardware-manufacturer.

For example, I liked the output options of PNY video cards and used several in the past but most of them developed fan-noise after a year or two. So, I gave up on them. If a company is using cheap mats and lowering the quality, they lose in the long run. PNY is still around, so maybe it was just that series, or it was my (lack of) luck. I am sure there are millions of PNY users out there with no issue whatsoever (and in full disclosure I still have a PNY card running on one of my much less used PCs after 9 years - oh yes sometimes I have to endure the fan-noise but it goes away after a while!).

Again, I wanted to go with a card, that is silent, performant and has good warranty. I learned that eVGA has lifetime warranty on some series (oh I am sure I will remember to register this time). Even these did not make the choice easy, as there are several eVGA cards that fit the bill.

Then I decided that I did not want an overclocked one, it's not need that for my use-case and I believe it taxes both the system (need more power / more heat) and the life of card. Finally, my choice is a non-overclocked eVGA GTX 460 1 GB card in the -AR series from which seems to have the best deal (hmm, it's really annoying me that they have a typo in the tile. It says "INVIDIA" instead of "NVIDIA". How could they miss that???).


I wish I had a BSOD

I never thought I would say that but after my PC froze today, I found myself looking at a garbled boot screen and realized my video card had gone bad  as well as bad sectors on the boot disk. If this was a BSOD, it would probably be a driver issue which would not be too hard to fix but now I have to replace the video card in the minimum. Bah!

I opened up my PC (Fragbox from Falcon Northwest I bought  mid-2008) to see if anything got loose (I know... it's wishful thinking), but of everything was seated properly. Then checked out serial number of the video card (nVidia GTS 8800) and called EVGA. To my surprise, someone picked up the phone. I had already read on their web site that my card had a lifetime warranty. So, I asked about it and was told that I was out of luck b/c card had to be registered in the first 30 days of purchase. Apparently, Falcon Northwest had not done it of course, neither did I...

I sent an e-mail to Falcon Northwest support to ask what would be a good replacement card. Because of the shape of Fragbox, I want to make sure I buy a card that would fit in seamlessly.

Then, I started looking for a replacement PC (Cannot keep Cho'gall waiting :p). Ever since I had issues with my Fragbox last year, I had that on the back of my mind. I was thinking about new Talon from Falcon NW. It's pretty decent and had great reviews. This time though, I acted like an impulse buyer and did all my shopping in about two hours. Here is what I ordered: Systemax Sys CrossFire. Looking forward to it.