Problem with XP scheduler?
in [Win32 Kernel]
|
From: Boba on 23 Dec 2009 18:19 "Pavel A." <pavel_a(a)12fastmail34.fm> wrote in message news:uT5IjS8gKHA.3792(a)TK2MSFTNGP02.phx.gbl... > ... > "Rest of the system" includes 3rd party drivers (video is especially > troublesome, but others as well), for which you can not blame MS. and Pavel, do not forget, please, that it is ms who charges tons of money for those drivers to be tested properly. > Yes, they've architected OS that makes possible for 3rd party drivers to > crash or hang the entire system, but this architecture was state of the > art when it was created. are you telling me that mcl tests those drivers against outdated core? > The OP has been adviced to get the dump and help finding the > exact reason of the problem, but he was not enough motivated to do this. > So the whole issue is moot. Another Windoze crash, yeah. the op has found the problem: it is 3rd party user level software that freezes pc. and my post was to point out to ya'll a shoddy statement from a respecful source: "A software problem cannot cause your machine to lock up so hard that even mouse and keyboard stop." - this is what i do not except. it is not about just another winblows, it is about how the people who know what windows is better than i do respond to the problem. > Replace XP with win7. Same h/w, same user, same application - the problem > is gone. "same application"? what do you mean? there is no 100% downward compatibility. the application must be rethought, restructured, recompiled, and installed first. only after that it might run with no problem - and if it does - it does not mean that w7 is better than xp (all it means i'm getting better in it :) > Now, has MS & industry made some progress, or not? if you, Pavel, think "MS & industry" is the way to put it - i am really sorry for you. to me, there is ms, and there is industry. aint't gonna publish a list of cases when the industry's steps forward 'accidently coincide' with ms' losts in the court of law.
From: Boba on 23 Dec 2009 18:28 "Leo Davidson" <leonudeldavidson(a)googlemail.com> wrote in message news:ce7f76e7-36c3-45f6-94f1-ad33c2f1392c(a)n35g2000yqm.googlegroups.com... >That's a silly thing to say. > >It's like concluding that a car isn't a true "moving-forwards machine" >because it stops working if fitted with bad tyres which blow out and >cause it to crash into a tree. not a good example at all, Leo, if it is based on the '90 case of ford explorer (what a lucky coincidence!) and forestone: the problem was the flaw in vehicle's suspension design covered up ford and poorely blamed on tires maker (those same tire performed fine on other cars).
From: Don Burn on 23 Dec 2009 18:35 "Boba" <Boba(a)somewhere.net> wrote in message news:uL0OsZChKHA.2164(a)TK2MSFTNGP02.phx.gbl... > > the op has found the problem: it is 3rd party user level software > that freezes pc. and my post was to point out to ya'll a shoddy > statement from a respecful source: "A software problem cannot cause > your machine to lock up so hard that even mouse and keyboard stop." - > this is what i do not except. it is not about just another winblows, > it is about how the people who know what windows is better than i do > respond to the problem. > No you are speculating what you describe is a symptom, not a cause. I raised the point earlier Microsoft spends a lot of time researching problems like this when they occur. Now you are stating the problem is Windows with no data other than the system hangs on this computer when a certain application is run, where is your data to show it is not a third party driver or even a driver embedded in the application. Lets stick to facts, of which there are very little about the specific problem. -- Don Burn (MVP, Windows DKD) Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr Remove StopSpam to reply __________ Information from ESET NOD32 Antivirus, version of virus signature database 4713 (20091223) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
From: Boba on 23 Dec 2009 19:23 "Don Burn" <burn(a)stopspam.windrvr.com> wrote in message news:%23Y9FRiChKHA.5608(a)TK2MSFTNGP05.phx.gbl... > ... > Now you are stating the problem is Windows with no data other than the > system hangs on this computer when a certain application is run, where is > your data to show it is not a third party driver or even a driver embedded > in the application. what type of data do you want me to publish? in what form? i will be glad to do it next time dexplore (to add one more to the list) freezes my xp_sp2 box. and i am afraid i know your next reply: oh, that is such and such driver combination that causes the problem. i won't be able to provide any dumps 'cause nothing is created. i can not make that pc accessible from outside - it is a development machine. i'd love to see the problem being solved, but i can not even contact ms regarding the issue because that dexplore ended up installed by the 3rd party.
From: Leo Davidson on 24 Dec 2009 01:38
On Dec 23, 11:28 pm, "Boba" <B...(a)somewhere.net> wrote: > not a good example at all, Leo, if it is based on the '90 case of ford > explorer (what a lucky coincidence!) and forestone: the problem was the > flaw in vehicle's suspension design covered up ford and poorely blamed > on tires maker (those same tire performed fine on other cars). So you're essentially saying the Ford Explorer was not a vehicle? Riiiiiiight. You don't know that all the drivers on this system were WHQL tested. WHQL testing does not, and probably cannot, guarantee the drivers will work in every situation. (WHQL is a series of tests, not a mathematical proof!) Drivers for other OS have issues as well. You're running XP SP2 when SP3 has been out for ages. You refuse to provide any data or do any proper investigation into the problem. You apparently just want us to magic-up an answer for you over the Internet with almost zero information, all of it anecdotal, and until someone can magic-up said answer you're going to point your finger at something you dislike and arbitrarily blame that. (And you could be right that it's Windows, but the fact is you have no evidence and experience shows it's almost always a 3rd party driver issue. We are saying that you can't assign blame without evidence when there are several other possibilities. You refuse to acknowledge the other possiblities because you'd rather blame the thing you hate. Even if it is Windows, which I very much doubt, we're talking about a version that's almost a decade old and isn't even patched to the latest service pack level, yet you're using this problem to make general statements about Windows today.) All of which is a very long-winded way of saying: I give up. Good luck solving your problem yourself as I doubt anyone else will help you (even if they try, like we did) when your mind is so closed and you've apparently already decided what to blame based on prejudice rather than evidence. |