Hello TechNet Forum: Received a Windows solution-suggestion; addressing my previous forum posting, concerning an IRQL - "B.S.E." message / Blue Screen Error / crash event.. The concern (for me), with this specific Hotfix suggestion (please see description in subject line or below this intro. text; Thanks!), it seems not to address my specific Win-7 32-bit OS version, that I am currently operating with (sometimes "co-operational with" - {that is another story!!}). Of course we are able to read the Hotfix purpose and application (if we choose to); determine if "hotfix" seems appropriate to our specific issue. Anyway.... the "main" reason for this posting is: 1.) Throw out here for discussion: If Window's solution suggestion "solutions" for my "Windows OS / system" - dialog - Is it appropriate for everyone... [(if a suggested fix message for Win-7 is to be "in production" / "operation"; via the Public release of Win-7).... (could have some potiential downside to the offering of hotfix's to everyone).... (Not sure about this; just UP for discussion here??) 2.) I believe my one and only "recent" "hotfix" install, has stablized Win-7 for the moment. I am not "currently" not seeing any BSE's (for right now); so not sure why would I want to install this hotfix, even if I somewhat-to fully fit the description message for the "Hotfix". *****Some additional research before proceeding with this "hotfix" - (with my limited in-depth knowledge of this "hotfix" - fixings)****** Again, Thanks for your time and reading! Bye for now, Jim 1:20 PM 4/7/2009 Hotfix Request Important Platform: x86 Language: English (United States) --------------------------------------------------------------------------------Language Platform Release File name Version Build File size (bytes) Modified dateWindows7.0 - Beta All (Global) x86 nosp Fix258548 Beta 6608 447324 2/16/2009 7:55:51 PMLink below this line; to the image ofmy hotfix web page - for hotfix info. referance - (is of poor visual qualityas uploaded - original low res jpg - sorry!)http://jcinq0.web.officelive.com/image7.aspx

Keep in mind that most BSOD's these days tend to be driver related. It could be a question of the driver not quite working properly or the hardware is on it's last leg and may be in the process of dying a slow death.As such, there are some occasions where a genuine bug pops up but it's not something that would affect everyone. It may have to do with a specific combination of hardware and/or software. It may fix your problem, but cause other problems for everyone else. That's generally why Microsoft doesn't makemany patches catagorized as hotfixes broadly available.

4:09 PM 4/7/2009 Thanks Wolfie2k6! For your general insight into "hotffix's" not for everyone or every system. (I agree with you completely!) {GREAT REMINDER!!} _________________________________________________________________________________________________________________ 1.)My main motivation for creating this post was to address the issue of "non-solicited" pushing of fixes out to the Windows 7 OS end-user and presenting them as possible solutions to my: "Win-7 O.S." - "Solve PC issues / flag". ______________________________________________________________________________ A user of this PC with Win-7 operating, may interpret the flag message as; that there is a "hotfix" available and it is from Microsoft, so it must be something important that I need to look-into / up-to perform a action to.... (this is my main reason for my posting). ______________________________________________________________________________________ Suggesting hardware issues with this software patch seems out on a thin limb for me. (my uderstanding as: A software driven - IRQL - Stop - due to: Server Message Blocking). __________________________________________________________________________________________________________________ 2.) A patch received on my "Solve PC issues" - "flag" - for a x86 system, when ny Win-7 is 32-bit. __________________________________________________________________________________________________________________ Thanks again for your reply! Jim

Jim, x86 is 32 bit x64 & IA64 are 64 bit Hope that helps !Asrock K8NF6P, AMD64 3200+, 1.5GB RAM, Palit Geforce 8400GS 256MB, 500GB Maxtor SataII, Asus 1814BLT optical

Ok.. I think I'm following you now. Most of the time, however, a hotfix won't be broadly pushed out - unless it fixes a specific issue that everyone can be/are having. At that point, the hotfix becomes a proper patch that gets pushed out via Windows Update.Even then, it's going to be limited in it's scope to those that have an actual need for it. If, for instance, you've got an AMD processor, and the patch is only applicable to systemsof the Intel variety, it would not make sense to apply that patch.Normally hotfixes aren't advertised. They are posted in the downloads section, andmayhave a page that tells about the patch, lists what the problems are, what the patch fixes, and that youthat you need to contact Microsoft Support to get it. If you're getting emails that are pushing hotfix XYZ, those are not likely to be coming from Microsoft. In fact, if you AREgetting such emails, they're likely to besomething thatwill lead you to a LOT of grief - namely a fake patch that has a trojan, virus or other nastyware loaded into the mix.When Microsoftwants a patch pushed out - they put it into Windows Update and those systems that are set tocheck automatically will go out and find them listedthere. They don't generally send out emails telling you of that fact.

Hello BrowniMFC: Thank you for the "wakeup" - to - "Jim" -- message!!I recalled the x86 was a referance to pre Win-7, like going as farback to Win-95 days.The x86 was the older legacy system referance: Yes? No?Win-7 now comes in two bit releases,as I understand: (theMS patch / hotfix labeled; "x86"; seems a little bit confusing when applied to Win-7 OS speak / words).Since this patch seems now more (to me)address the legacy software / (previously released software)- [(from myinterpretation)], it makes more sense to me now, after your clarification of the x86. Thanks very much for your reply to me posting!! Jim