If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
KB891711 - problems??
Sorry for the cross-post, but this (hopefully) may be important.
I'm attempting to correlate some data to find out the cause of people's problems with this patch Current advice from MS, is for those affected by the problem to either uninstall the patch (Add/Remove Programs) or prevent it from running at startup (use MSCONFIG|Startup) What I'd like is for everyone (and anyone!) affected by this problem to email me (my addy here is valid) with a copy of their Everest Home Edition (or AIDA32) report. To do this, please read the following carefully Download and install Everest Home Edition from www.lavalys.hu and install it. Run the program, and once it's up and running, click on Report Quick report - All Pages (here you can pick your choice - I'd prefer HTML, but if you're worried about your privacy, then Text is a better option) When the report is complete (please don't click on anything until it is complete!) Save it!!! Remove any information that you may consider sensitive - but please put something in its place! (I suggest removed) so that I know that something is missing Save the (amended) file as "Report your email" then email it to me as an attachment at I can't promise to respond - but I'll try to at least acknowledge receipt, particularly if you put some detail into the covering email. Many thanks for your patience in reading this - I hope it makes sense!! -- Noel Paton (MS-MVP 2002-2005, Windows) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm In fond memory of one of life's Gentlemen - Alex Nichol http://www.aumha.org/alex.htm Please read http://dts-l.org/goodpost.htm on how to post messages to NG's |
#2
|
|||
|
|||
I request that users with the KB891711 problem run this simple test.
First, temporarily disable KB891711.EXE by using msconfig/Startup to uncheck the box which launches it at boot. Reboot. Then replace the current video adapter/driver with the MS plain-vanilla SVGA driver, using the wizard in Device Manager. Reboot and confirm that all is well. When satisfied that the machine and the browser work fine, use msconfig to reenable the KB891711 "patch", reboot, and see if the problems return, or remain absent. Revert to the original video driver when desired, while disabling the "patch", if necessary. Please report all results to Noel. -- Jack E. Martinelli 2002-05 MS MVP for Shell/User / DTS Help us help you: http://www.dts-L.org/goodpost.htm http://www.microsoft.com/athome/secu...t/default.aspx In Memorium: Alex Nichol http://www.microsoft.com/windowsxp/e...ts/nichol.mspx Your cooperation is very appreciated. ------ "Noel Paton" wrote in message ... Sorry for the cross-post, but this (hopefully) may be important. I'm attempting to correlate some data to find out the cause of people's problems with this patch Current advice from MS, is for those affected by the problem to either uninstall the patch (Add/Remove Programs) or prevent it from running at startup (use MSCONFIG|Startup) What I'd like is for everyone (and anyone!) affected by this problem to email me (my addy here is valid) with a copy of their Everest Home Edition (or AIDA32) report. To do this, please read the following carefully Download and install Everest Home Edition from www.lavalys.hu and install it. Run the program, and once it's up and running, click on Report Quick report - All Pages (here you can pick your choice - I'd prefer HTML, but if you're worried about your privacy, then Text is a better option) When the report is complete (please don't click on anything until it is complete!) Save it!!! Remove any information that you may consider sensitive - but please put something in its place! (I suggest removed) so that I know that something is missing Save the (amended) file as "Report your email" then email it to me as an attachment at I can't promise to respond - but I'll try to at least acknowledge receipt, particularly if you put some detail into the covering email. Many thanks for your patience in reading this - I hope it makes sense!! -- Noel Paton (MS-MVP 2002-2005, Windows) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm In fond memory of one of life's Gentlemen - Alex Nichol http://www.aumha.org/alex.htm Please read http://dts-l.org/goodpost.htm on how to post messages to NG's |
#3
|
|||
|
|||
In article , Noel Paton says...
Sorry for the cross-post, but this (hopefully) may be important. I'm attempting to correlate some data to find out the cause of people's problems with this patch snip What I'd like is for everyone (and anyone!) affected by this problem to email me (my addy here is valid) with a copy of their Everest Home Edition (or AIDA32) report. To do this, please read the following carefully Download and install Everest Home Edition from www.lavalys.hu and install it. Run the program, and once it's up and running, click on Report Quick report - All Pages snip Save the (amended) file as "Report your email" then email it to me as an attachment at snip Done. I also noted the fact that my computer runs fine with the KB891711 patch as long as I am not running Mercury Mail. I used 'msconfig' to disable MM from loading on startup. As long as MM is not running, this computer, and its sister, run KB891711 with no problem. As soon as I enable MM on this computer, trying to launch any browser causes a blue screen. -- Norman ~Win dain a lotica, En vai tu ri, Si lo ta ~Fin dein a loluca, En dragu a sei lain ~Vi fa-ru les shutai am, En riga-lint |
#4
|
|||
|
|||
In article , Jack E Martinelli
says... I request that users with the KB891711 problem run this simple test. First, temporarily disable KB891711.EXE by using msconfig/Startup to uncheck the box which launches it at boot. Reboot. Then replace the current video adapter/driver with the MS plain-vanilla SVGA driver, using the wizard in Device Manager. Reboot and confirm that all is well. When satisfied that the machine and the browser work fine, use msconfig to reenable the KB891711 "patch", reboot, and see if the problems return, or remain absent. Revert to the original video driver when desired, while disabling the "patch", if necessary. Please report all results to Noel. I don't have to run your test. As you recall, I have two mostly identical HP Pavilion 6745C computers; Megumi crashes, Naomi doesn't. I tried this little test: Run 'msconfig'. Disable just one item in the startup list: Mercury Mail. Reboot. Rename 'Kb891711.DLL.dud' to 'Kb891711.DLL'. Rename 'Kb891711.EXE.dud' to 'Kb891711.EXE'. Double-click on 'Kb891711.EXE'. Check the "Close Programs" list to verify that 'Kb891711' is in the list. Launch any browser. Computer works just fine. Load Mercury Mail manually. Launch any browser. Blue screen on browser launch. It seems pretty clear that I can run Kb891711 on my troublesome computer; if I don't run the Mercury Mail Transport application. I did, finally, set up the Everest Home program, and sent a copy of the report to Noel. I think I will send him a copy from Naomi, as well. -- Norman ~Win dain a lotica, En vai tu ri, Si lo ta ~Fin dein a loluca, En dragu a sei lain ~Vi fa-ru les shutai am, En riga-lint |
#5
|
|||
|
|||
Norman,
Are you now saying that the version of the Intel drivers makes no difference? Previously I thought that you had said the difference between the two PCs was that the one that was crashing had Intel driver version 4.13.01.3196 and that which didn't had version 4.13.01.3004. Does this mean that you have now eliminated the difference in driver version as being a factor? -- Mike Maltby MS-MVP N. Miller wrote: Done. I also noted the fact that my computer runs fine with the KB891711 patch as long as I am not running Mercury Mail. I used 'msconfig' to disable MM from loading on startup. As long as MM is not running, this computer, and its sister, run KB891711 with no problem. As soon as I enable MM on this computer, trying to launch any browser causes a blue screen. |
#6
|
|||
|
|||
Thanks, Norman - that's good data, and the reports have arrived safely
-- Noel Paton (MS-MVP 2002-2005, Windows) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm In fond memory of one of life's Gentlemen - Alex Nichol http://www.aumha.org/alex.htm Please read http://dts-l.org/goodpost.htm on how to post messages to NG's "N. Miller" wrote in message om... In article , Jack E Martinelli says... I request that users with the KB891711 problem run this simple test. First, temporarily disable KB891711.EXE by using msconfig/Startup to uncheck the box which launches it at boot. Reboot. Then replace the current video adapter/driver with the MS plain-vanilla SVGA driver, using the wizard in Device Manager. Reboot and confirm that all is well. When satisfied that the machine and the browser work fine, use msconfig to reenable the KB891711 "patch", reboot, and see if the problems return, or remain absent. Revert to the original video driver when desired, while disabling the "patch", if necessary. Please report all results to Noel. I don't have to run your test. As you recall, I have two mostly identical HP Pavilion 6745C computers; Megumi crashes, Naomi doesn't. I tried this little test: Run 'msconfig'. Disable just one item in the startup list: Mercury Mail. Reboot. Rename 'Kb891711.DLL.dud' to 'Kb891711.DLL'. Rename 'Kb891711.EXE.dud' to 'Kb891711.EXE'. Double-click on 'Kb891711.EXE'. Check the "Close Programs" list to verify that 'Kb891711' is in the list. Launch any browser. Computer works just fine. Load Mercury Mail manually. Launch any browser. Blue screen on browser launch. It seems pretty clear that I can run Kb891711 on my troublesome computer; if I don't run the Mercury Mail Transport application. I did, finally, set up the Everest Home program, and sent a copy of the report to Noel. I think I will send him a copy from Naomi, as well. -- Norman ~Win dain a lotica, En vai tu ri, Si lo ta ~Fin dein a loluca, En dragu a sei lain ~Vi fa-ru les shutai am, En riga-lint |
#7
|
|||
|
|||
Thank you, Norman. Your results are very interesting. I've read one other
recent report from Jeff Richards, in win98. gen_discussion, where using the MS video drivers, instead of the third-party ones, avoided the KB891711 problem on at least one machine. I still haven't found a machine exhibiting the problem. -- Jack E. Martinelli 2002-05 MS MVP for Shell/User / DTS Help us help you: http://www.dts-L.org/goodpost.htm http://www.microsoft.com/athome/secu...t/default.aspx In Memorium: Alex Nichol http://www.microsoft.com/windowsxp/e...ts/nichol.mspx Your cooperation is very appreciated. ------ "Noel Paton" wrote in message ... Thanks, Norman - that's good data, and the reports have arrived safely -- Noel Paton (MS-MVP 2002-2005, Windows) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm In fond memory of one of life's Gentlemen - Alex Nichol http://www.aumha.org/alex.htm Please read http://dts-l.org/goodpost.htm on how to post messages to NG's "N. Miller" wrote in message om... In article , Jack E Martinelli says... I request that users with the KB891711 problem run this simple test. First, temporarily disable KB891711.EXE by using msconfig/Startup to uncheck the box which launches it at boot. Reboot. Then replace the current video adapter/driver with the MS plain-vanilla SVGA driver, using the wizard in Device Manager. Reboot and confirm that all is well. When satisfied that the machine and the browser work fine, use msconfig to reenable the KB891711 "patch", reboot, and see if the problems return, or remain absent. Revert to the original video driver when desired, while disabling the "patch", if necessary. Please report all results to Noel. I don't have to run your test. As you recall, I have two mostly identical HP Pavilion 6745C computers; Megumi crashes, Naomi doesn't. I tried this little test: Run 'msconfig'. Disable just one item in the startup list: Mercury Mail. Reboot. Rename 'Kb891711.DLL.dud' to 'Kb891711.DLL'. Rename 'Kb891711.EXE.dud' to 'Kb891711.EXE'. Double-click on 'Kb891711.EXE'. Check the "Close Programs" list to verify that 'Kb891711' is in the list. Launch any browser. Computer works just fine. Load Mercury Mail manually. Launch any browser. Blue screen on browser launch. It seems pretty clear that I can run Kb891711 on my troublesome computer; if I don't run the Mercury Mail Transport application. I did, finally, set up the Everest Home program, and sent a copy of the report to Noel. I think I will send him a copy from Naomi, as well. -- Norman ~Win dain a lotica, En vai tu ri, Si lo ta ~Fin dein a loluca, En dragu a sei lain ~Vi fa-ru les shutai am, En riga-lint |
#8
|
|||
|
|||
In article , Mike M says...
Are you now saying that the version of the Intel drivers makes no difference? Previously I thought that you had said the difference between the two PCs was that the one that was crashing had Intel driver version 4.13.01.3196 and that which didn't had version 4.13.01.3004. Does this mean that you have now eliminated the difference in driver version as being a factor? I though that I had posted a correction. When I ran that test, I failed to restart, so the Kb891711 patch was not running during the test. I re-ran things. With older version of the Intel drivers, Kb891711 causes crashes on Megumi, but not on Naomi. With the newer version of the Intel drivers, Kb891711 causes crashes on Megumi, but not on Naomi. When I stop the Mercury Mail MTA from running in the startup group, neither driver causes crashes on Megumi; only the combination of Mercury Mail and Kb891711 running causes crashes on Megumi. Oddly, the crashes only occur while launching browsers. It is a puzzle; and I am considering additional tests by changing the modules running when the Mercury Mail MTA is launched. I will go to a bare bones startup; minimal, if you will. If it doesn't cause crashes I will add back the modules, one by one, until the crashes resume. -- Norman ~Win dain a lotica, En vai tu ri, Si lo ta ~Fin dein a loluca, En dragu a sei lain ~Vi fa-ru les shutai am, En riga-lint |
#9
|
|||
|
|||
Thanks for your persistence, Norman - this type of help is invaluable to us!
-- Noel Paton (MS-MVP 2002-2005, Windows) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm In fond memory of one of life's Gentlemen - Alex Nichol http://www.aumha.org/alex.htm Please read http://dts-l.org/goodpost.htm on how to post messages to NG's "N. Miller" wrote in message om... In article , Mike M says... Are you now saying that the version of the Intel drivers makes no difference? Previously I thought that you had said the difference between the two PCs was that the one that was crashing had Intel driver version 4.13.01.3196 and that which didn't had version 4.13.01.3004. Does this mean that you have now eliminated the difference in driver version as being a factor? I though that I had posted a correction. When I ran that test, I failed to restart, so the Kb891711 patch was not running during the test. I re-ran things. With older version of the Intel drivers, Kb891711 causes crashes on Megumi, but not on Naomi. With the newer version of the Intel drivers, Kb891711 causes crashes on Megumi, but not on Naomi. When I stop the Mercury Mail MTA from running in the startup group, neither driver causes crashes on Megumi; only the combination of Mercury Mail and Kb891711 running causes crashes on Megumi. Oddly, the crashes only occur while launching browsers. It is a puzzle; and I am considering additional tests by changing the modules running when the Mercury Mail MTA is launched. I will go to a bare bones startup; minimal, if you will. If it doesn't cause crashes I will add back the modules, one by one, until the crashes resume. -- Norman ~Win dain a lotica, En vai tu ri, Si lo ta ~Fin dein a loluca, En dragu a sei lain ~Vi fa-ru les shutai am, En riga-lint |
#10
|
|||
|
|||
N. Miller wrote:
In article , Mike M says... I though that I had posted a correction. You probably did. It's far more likely that I missed your post. When I ran that test, I failed to restart, so the Kb891711 patch was not running during the test. I re-ran things. With older version of the Intel drivers, Kb891711 causes crashes on Megumi, but not on Naomi. With the newer version of the Intel drivers, Kb891711 causes crashes on Megumi, but not on Naomi. So Naomi doesn't blue screen regardless of the driver version but Megumi crashes regardless of driver version. Thanks for the clarification. I'd hoped you might have been bringing us closer to a possible reason there. When I stop the Mercury Mail MTA from running in the startup group, neither driver causes crashes on Megumi; only the combination of Mercury Mail and Kb891711 running causes crashes on Megumi. Oddly, the crashes only occur while launching browsers. It is a puzzle; and I am considering additional tests by changing the modules running when the Mercury Mail MTA is launched. I will go to a bare bones startup; minimal, if you will. If it doesn't cause crashes I will add back the modules, one by one, until the crashes resume. -- Mike Maltby MS-MVP |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
KB891711 trouble seems to be graphic issue | N. Miller | General | 24 | March 23rd 05 02:59 AM |
KB891711 and Microsoft unresponsiveness/(ir)responsability | Paul (Bornival) | General | 5 | March 19th 05 03:25 AM |
BSOD and BSON, so removed 'buggy' Mar 8 05 security update kb891711 (WinMe) | [email protected] | General | 2 | March 15th 05 06:55 AM |
kb891711 and netgear wg511 | nvstewar | General | 1 | March 13th 05 12:57 PM |
Lots of Problems all of a Sudden | Chris | Improving Performance | 1 | May 27th 04 10:00 AM |