Microsoft Hotfixes Windows 7 Memory Leak

Toggle sidebar Toggle sidebar
Status
Not open for further replies.
lol, it closes ANOTHER port?? wouldn't that be a bigger concern?

does it close the port on another computer? like "its ok dude, I'll save you from a memory leak, I'll take one for the team."
 
[citation][nom]matt87_50[/nom]lol, it closes ANOTHER port?? wouldn't that be a bigger concern?does it close the port on another computer? like "its ok dude, I'll save you from a memory leak, I'll take one for the team."[/citation]

It's an ALPC port, are you thinking of regular data ports or something? It would take an exceptionally large amount of time (or an insanely high amount of power requests) for this to show up in standard use, since each ALPC port takes approximately 4KB of memory. Assuming the port never closes, and assuming new ones are opened at (the default) of one every 30 minutes, it would take 6 days straight for 1MB of memory to leak, and it would take almost 40 years (straight) for the system to bluescreen because of it, under normal circumstances.

I'm not saying this isn't an issue, but is an extreme edge-case scenario really worth making an entire news posting for? It's just another bug fix that would never have shown up in standard testing - I expect this only even manifests itself if you have software installed that polls power status far often than normal is healthy.
 
[citation][nom]andy5174[/nom]Do I have to download it manually? Can you get it using windows update?[/citation]

You can request the hotfix from http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=979444&kbln=en-us.

This kind of hotfix, as it does not cover a security threat or affects many people, will not be on Windows update, but will instead be rolled into the next Service pack release. You need to request it using the above link, and you can then install the .msu manually.
 
[citation][nom]ossie[/nom]What about the battery leak? Yeah, that's "a feature, not a bug"...[/citation]

The explanation for that seems very reasonable, since Microsoft found no link relating Windows 7 to the actual problems - Far more people are upgrading from XP (which did not have battery warning systems built in) to Windows 7, on laptops they did not perform adequately using Vista.

People are assuming that because these warnings are only showing up now (as in, yes, a new feature of Windows 7), and didn't on Windows XP, that Windows 7 is the cause of the problems. Instead, it's simply that Windows 7 has the ability to detect these failures by default, whereas Windows XP cannot (without additional software).
 
[citation][nom]kikireeki[/nom]What about a hotfix for x64? because the link shows only the x86 version.[/citation]

Click the link that says "show hotfixes for all platforms and languages", and it'll show the x64 and IA64 versions as well. It only shows 32-bit by default because almost everyone will be using 32-bit browsers even on 64-bit systems, and that's what it uses to try to detect the current platform.
 
My computer BSOD'd last night. First time I've gotten one since I installed demo win 7 a year ago. It was immediately after I went to change a setting in power manager.

Looks like I'll be needing the hotfix. Thanks so much for the article Toms.
 
This remember me a certain XFX 9600GT causing "IRQL_NOT_LESS_OR_EQUAL" after a maximum of 30 minutes in a game (Direct X)(probably a memory bug on the video card). Support from XFX is so crappy on problem like this (they don't have any applications to test the memory of their own card...)...

I finally just bought a new card (I have no trouble since) but this bug bring me... a little "chill" when I hear about "IRQL_NOT_LESS_OR_EQUAL" errors.
 
I've seen this error (exactly this one) on several ACER with Intel hardware (grahics+processor).. I bet it was hardware related issue, not just a memory leak. Why? Cuz all AMD Acer that I've installed Win7 this error wouldn't occur at all. Weird, but it's true. But it's nice to know that MS fixed it.
 
Yep I just saw this error last week. Only had win7 x64 installed for 2 wks now. Walked away from the computer for a few hours and when the system tried to wake up, bsod and reboot. Logs showed the error described and ntoskrnl the offending program. Interestingly, at the time MS had NO information on this BUT google had quite a few hits on it. The suggested fix was to disable hibernation by running a dos window as admin and typing powercfg -h off to shut down hibernation. FYI: you may "think" you don't have hibernation set (as I did) but check for the hibernation file hiberfil.sys in C:\. IF you see it there then it is active in some form or another. When it is truly turned off that file will be removed by the os. (You may have to reboot).
 
I get this exact BSOD A few times a day. Trying to install hotfix (Fix302249) from KB Article Number 979444; the installer claims "The update is not applicable to your computer." but it should be as I am running a 64-bit x64 Windows 7.
 
[citation][nom]omoronovo[/nom]It's an ALPC port, are you thinking of regular data ports or something? It would take an exceptionally large amount of time (or an insanely high amount of power requests) for this to show up in standard use, since each ALPC port takes approximately 4KB of memory. Assuming the port never closes, and assuming new ones are opened at (the default) of one every 30 minutes, it would take 6 days straight for 1MB of memory to leak, and it would take almost 40 years (straight) for the system to bluescreen because of it, under normal circumstances.I'm not saying this isn't an issue, but is an extreme edge-case scenario really worth making an entire news posting for? It's just another bug fix that would never have shown up in standard testing - I expect this only even manifests itself if you have software installed that polls power status far often than normal is healthy.[/citation]

If it takes so long to crash, explain how Microsoft found this problem. Why would they even be concerned with such a rare event?
 
[citation][nom]NewJohnny[/nom]If it takes so long to crash, explain how Microsoft found this problem. Why would they even be concerned with such a rare event?[/citation]

Read the last line. If an application is polling power status, say, once a second - the crash will manifest itself within 3 weeks. More if the info is being polled more often. This is how edge cases are found, in the (fairly substantial) amount of windows 7 installs, it only takes a few reports with similar issues for a problem to be found and a fix to be issued if necessary.

That's what the Error Reporting feature is for.
 
Heys guys it is giving me an error that the class is not registered error? im using windows 7 64 bit 7600 build....

What to do?
 
Status
Not open for further replies.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom