Guest lforbes Posted August 17, 2007 Posted August 17, 2007 OK, I have 3 laptops. 2 Dell, 1 Sony. One is running Vista and two are running XP SP2. After the most recent Microsoft Updates on Tuesday they are all displaying the Blue Screen of Death randomly. So far the Dells 1x and the Sony 2x? Has anyone else found this? No new hardware or anything and the hardware is different in all of them. Also, it is a different group of software running at the time.
Guest Newbie Coder Posted August 17, 2007 Posted August 17, 2007 Re: BSOD after Tuesday MS Updates? IForbes, What is the BSOD code to the left of the brackets? Example: 0x0000000D (memory address here, & here, & here) Forget the memory addresses though -- Newbie Coder (It's just a name) "lforbes" <lforbes@discussions.microsoft.com> wrote in message news:0C0BBE9D-0B7E-47FA-8A23-CD816F751CCA@microsoft.com... > OK, I have 3 laptops. 2 Dell, 1 Sony. One is running Vista and two are > running XP SP2. > > After the most recent Microsoft Updates on Tuesday they are all displaying > the Blue Screen of Death randomly. So far the Dells 1x and the Sony 2x? > > Has anyone else found this? No new hardware or anything and the hardware is > different in all of them. Also, it is a different group of software running > at the time. >
Guest HEMI-Powered Posted August 17, 2007 Posted August 17, 2007 Re: BSOD after Tuesday MS Updates? =?Utf-8?B?bGZvcmJlcw==?= added these comments in the current discussion du jour ... > OK, I have 3 laptops. 2 Dell, 1 Sony. One is running Vista and > two are running XP SP2. > > After the most recent Microsoft Updates on Tuesday they are > all displaying the Blue Screen of Death randomly. So far the > Dells 1x and the Sony 2x? > > Has anyone else found this? No new hardware or anything and > the hardware is different in all of them. Also, it is a > different group of software running at the time. > I did my updates in 3 different groups because, as is my normal mode of operation, I lurk first, saw some possible problems for myself, they evaporated, so I updated. No problems whatsoever, certainly no BSOD. To help anyone help you, what do these BSOD notices tell you is failing, i.e., what failed and what is the error code(s)? What does Event Manager say was happening just prior to the crash? And, what special HW or SW might you have on these 3 (?) PCs that may make them especially vulnerable? Please provide details, maybe somebody will brighten your day, I know how frustrating and angry I get when I get BSOD problems and cannot determine the cause. One other question, did YOU set your own RP prior to updating? If yes, or if you used the one that MS sets for you, did rolling your system back completely work? I'm speaking next broadly to people who find themselves unexpectedly in a MAJOR crisis after a large - I think it was 9 or 10 - update install, not necessarily just you: use the rule of binary divide to find out which one(s) caused it. What that means uninstall them all and/or roll back to the RP, then take half of them, the 1st 4 or 5 or the last 4 or 5, run the updates and see if it crashes. If it does, you've narrowed the culprit down to 4 or 5. If not, install the other half. Whichever half has the BSOD, uninstall all of that half, and install only 2 or may 3. That will narrow it down almost surely to the main culprit in only 3 tries. Trying to nail down the errant update with that many in play is perhaps futile, but is certainly frustrating. Hope you find a solution very soon. -- HP, aka Jerry
Guest lforbes Posted August 18, 2007 Posted August 18, 2007 Re: BSOD after Tuesday MS Updates? Hi, It was all zeros with a 50 on the end. 0x00000050 (0xff55d000, 0x00000000, 0x926d82b3, 0x00000000). I haven't got the other laptop with me as it is at my Dads. I will have to look at that system log too. His happened 2x and mine 1x all within the same day. As my laptop running Vista is pretty much left alone it was just weird. I never installed anything. I am not going to worry about it unless it becomes a habit. We all run Shaw Secure as our Virus checker and I noticed it came out with an update today so maybe that was what the problem was. Otherwise the software is pretty basic. Cheers, Lara "HEMI-Powered" wrote: > =?Utf-8?B?bGZvcmJlcw==?= added these comments in the current > discussion du jour ... > > > OK, I have 3 laptops. 2 Dell, 1 Sony. One is running Vista and > > two are running XP SP2. > > > > After the most recent Microsoft Updates on Tuesday they are > > all displaying the Blue Screen of Death randomly. So far the > > Dells 1x and the Sony 2x? > > > > Has anyone else found this? No new hardware or anything and > > the hardware is different in all of them. Also, it is a > > different group of software running at the time. > > > I did my updates in 3 different groups because, as is my normal > mode of operation, I lurk first, saw some possible problems for > myself, they evaporated, so I updated. No problems whatsoever, > certainly no BSOD. > > To help anyone help you, what do these BSOD notices tell you is > failing, i.e., what failed and what is the error code(s)? What > does Event Manager say was happening just prior to the crash? > And, what special HW or SW might you have on these 3 (?) PCs that > may make them especially vulnerable? > > Please provide details, maybe somebody will brighten your day, I > know how frustrating and angry I get when I get BSOD problems and > cannot determine the cause. > > One other question, did YOU set your own RP prior to updating? If > yes, or if you used the one that MS sets for you, did rolling > your system back completely work? > > I'm speaking next broadly to people who find themselves > unexpectedly in a MAJOR crisis after a large - I think it was 9 > or 10 - update install, not necessarily just you: use the rule of > binary divide to find out which one(s) caused it. What that means > uninstall them all and/or roll back to the RP, then take half of > them, the 1st 4 or 5 or the last 4 or 5, run the updates and see > if it crashes. If it does, you've narrowed the culprit down to 4 > or 5. If not, install the other half. Whichever half has the > BSOD, uninstall all of that half, and install only 2 or may 3. > That will narrow it down almost surely to the main culprit in > only 3 tries. Trying to nail down the errant update with that > many in play is perhaps futile, but is certainly frustrating. > > Hope you find a solution very soon. > > -- > HP, aka Jerry >
Recommended Posts