Blue Screen of Death on Restart
|
|
Thread rating:  |
Gene van Troyer - 15 Jun 2004 01:17 GMT VPC 6.0 (Connectix) updated to MS VPC (most recent) / Win2K Pro (Connectix OS Pack, modified with Additions from stadard W2K Pro)
Imac 20" Flatpanel, 1.25 GHz, 1 GB RAM)
Recently, when restarting Win2K after application updates (Widows Updates, McAfee VirusScan updates), Win2K goes into an endless Blue Screen of Death loop. OS launch starts, then goes to Death Screen, then OS launch resumes and repeats the cycle.
The only way to launch Win2K is to turn off the PC and reboot from the VPC List, after which start-up proceeds normally.
The Death Screen only lasts about a second, so it's difficult to read the error message, but it seems to be a missing DLL of some kind that is preventing a normal restart.
I supplemented the Connectix Win2K Pro OS with language options on my full version Win2K Pro CDs (I needed the Japanese, Chinese, and Korean IMEs).
Anyone have any ideas as to what the problem may be?
Gene van Troyer
Walt Basil - 15 Jun 2004 02:23 GMT On 6/14/04 18:17, in article BCF46F3F.3AEE%gevantry@nirai.ne.jp, "Gene van Troyer" <gevantry@nirai.ne.jp> wrote:
> VPC 6.0 (Connectix) updated to MS VPC (most recent) / Win2K Pro (Connectix > OS Pack, modified with Additions from stadard W2K Pro) [quoted text clipped - 19 lines] > > Gene van Troyer This won't help you out any, but that is the reason I switched to Mac OS X. ;-)
This is the only computer I have ever owned that has never crashed on me and I've had it about 2 years.
/me hugs his iBook. -- Walt Basil www.basilweb.net
My Office site: <http://www.basilweb.net/macoffice/office.html>
You can email me at (firstname)AT(lastname)web.net
Gene van Troyer - 15 Jun 2004 14:06 GMT On 6/15/04 10:23 AM, in article BCF3ABAA.3807%see_signature_for_real_email@address.com, "Walt Basil" <see_signature_for_real_email@address.com> wrote:
> This won't help you out any, but that is the reason I switched to Mac OS X. > ;-) > > This is the only computer I have ever owned that has never crashed on me and > I've had it about 2 years. Well, that is why I hug my little Macs, too, Walt, and why I have VPC to wow the smirking Windoze users who surround me. Windoze? You want Windoze? Here it is! And before their sometimes thunderstruck eyes, the alternate Windoze universe opens in one corner of the Mac.
But you're right, it doesn't answer the question.
Gene van Troyer
Walt Basil - 15 Jun 2004 18:25 GMT On 6/15/04 7:06, in article BCF5236E.3AFF%gevantry@nirai.ne.jp, "Gene van Troyer" <gevantry@nirai.ne.jp> wrote:
> On 6/15/04 10:23 AM, in article > BCF3ABAA.3807%see_signature_for_real_email@address.com, "Walt Basil" [quoted text clipped - 14 lines] > > Gene van Troyer Is there any way for you to read what DLL it claims is missing?
-- Walt Basil www.basilweb.net
My Office site: <http://www.basilweb.net/macoffice/office.html>
You can email me at (firstname)AT(lastname)web.net
Gene van Troyer - 17 Jun 2004 00:02 GMT On 6/16/04 2:25 AM, in article BCF48D2A.385C%see_signature_for_real_email@address.com, "Walt Basil" <see_signature_for_real_email@address.com> wrote:
> Is there any way for you to read what DLL it claims is missing? I managed to grab a screen capture before the screen blinked away:
> STOP: c0000135 {Unable To Locate DLL} > The dynamic link library winserv could not be found in the specified Default > Load Path. As I said, this happens *only* when I click the RESTART button. If I turn the VPC off and then start it, it loads and runs as it should.
Gene van Troyer
Walt Basil - 17 Jun 2004 02:14 GMT On 6/16/04 17:02, in article BCF7008A.3B46%gevantry@nirai.ne.jp, "Gene van Troyer" <gevantry@nirai.ne.jp> wrote:
> On 6/16/04 2:25 AM, in article > BCF48D2A.385C%see_signature_for_real_email@address.com, "Walt Basil" [quoted text clipped - 12 lines] > > Gene van Troyer No suggestions here, other than maybe taking this to a Windows forum. You may want to withhold the fact that you're running it under VPC. ;-)
Usually, Windows will tell you exactly what DLL(s) is/are missing. If that were the case you search and download it, and manually install it, or clear it out of the registry. Obviously you can't do the latter in this case.
-- Walt Basil www.basilweb.net
My Office site: <http://www.basilweb.net/macoffice/office.html>
You can email me at (firstname)AT(lastname)web.net
Gene van Troyer - 17 Jun 2004 02:57 GMT On 6/17/04 10:14 AM, in article BCF64CA1.3935%see_signature_for_real_email@address.com, "Walt Basil" <see_signature_for_real_email@address.com> wrote:
> No suggestions here, other than maybe taking this to a Windows forum. You > may want to withhold the fact that you're running it under VPC. ;-) > > Usually, Windows will tell you exactly what DLL(s) is/are missing. If that > were the case you search and download it, and manually install it, or clear > it out of the registry. Obviously you can't do the latter in this case. It turns out there are two messages. The one I posted is the message that appears after the first restart attempt fails. The FIRST Restart failure alert, which is even more dramatic, is:
> STOP: c000021a {Fatal System Error} > The Session Manager Initialization system process terminated unexpectedly > With a status of 0xc0000005 (0x00000000 0x00000000). > The system has been shut down. Then it goes into the Restart/Death Screen loop. Turning the VPC of and then clicking the Start-up button on the VPC list window initiates a normal, successful launch.
Gene van Troyer
Tim Murray - 18 Jun 2004 16:22 GMT > Recently, when restarting Win2K after application updates (Widows Updates, > McAfee VirusScan updates), Win2K goes into an endless Blue Screen of Death [quoted text clipped - 3 lines] > The only way to launch Win2K is to turn off the PC and reboot from the VPC > List, after which start-up proceeds normally. My VPC has the same situtation, and mime came just after some Windows updates (no virus updates). If I have time ... which means I probably won't do it ... I will start with a fresh VPC instance, and install hot fixes one at a time to see which one it is.
I'm getting around it now simply by never "restarting"; I only shut down.
dano - 18 Jun 2004 23:11 GMT > > Recently, when restarting Win2K after application updates (Widows Updates, > > McAfee VirusScan updates), Win2K goes into an endless Blue Screen of Death [quoted text clipped - 10 lines] > > I'm getting around it now simply by never "restarting"; I only shut down. We've had the problem also and narrowed it down to being caused by the Sasser update/patch.
Any VPC MVPs have specific information on how to deal with this?
 Signature Why isn't the quarter of the State of Texas bigger than all the other quarters? Because then it wouldn't fit into the parking meter slots.
<http://www.chron.com/cs/CDA/ssistory.mpl/metropolitan/2621391>
Steve Jain - 18 Jun 2004 23:27 GMT As far as I know, there aren't any VPC-Mac MVPs.
>> > Recently, when restarting Win2K after application updates (Widows Updates, >> > McAfee VirusScan updates), Win2K goes into an endless Blue Screen of Death [quoted text clipped - 15 lines] > >Any VPC MVPs have specific information on how to deal with this? Steve Jain, Microsoft MVP for Virtual PC for Windows Website: http://www.essjae.com *** All posts are provided AS-IS, no warranty, no QoS ***
Robert Comer - 19 Jun 2004 01:52 GMT > Any VPC MVPs have specific information on how to deal with this? Since I don't have a Mac to test with and I just wanted to help, I made the only recommendation I could to deal with the sasser patch problem, and that was to either use a firewall on the PC to black any sasser type attacks, or to not allow the Windows VM access to the internet.
- Bob Comer <MS MVP VPC2004 for Windows.>
> > > Recently, when restarting Win2K after application updates (Widows Updates, > > > McAfee VirusScan updates), Win2K goes into an endless Blue Screen of Death [quoted text clipped - 15 lines] > > Any VPC MVPs have specific information on how to deal with this? Tim Murray - 20 Jun 2004 04:28 GMT > We've had the problem also and narrowed it down to being caused by the > Sasser update/patch. Do you know that what the KBxxxxx name is?
Robert Comer - 20 Jun 2004 13:40 GMT KB835732 Bulletin MS04-011.
- Bob Comer
> > We've had the problem also and narrowed it down to being caused by the > > Sasser update/patch. > > Do you know that what the KBxxxxx name is? Tim Murray - 20 Jun 2004 19:59 GMT > KB835732 Bulletin MS04-011. Thanks. I deleted that hotfix, and now I can reboot.
Robert Comer - 20 Jun 2004 21:06 GMT No problem, glad to help.
Just watch out for sasser type crashes and infection.
Maybe someone here could call PSS and report the problem, if it's a clear bug in the way either VPC for the Mac, or the OS's themselves when running on VPC for Mac, it wouldn't be a chargeable item and then at least Microsoft would have to deal with the report.
- Bob Comer
> > KB835732 Bulletin MS04-011. > > Thanks. I deleted that hotfix, and now I can reboot. Gerry Simmons - 21 Jun 2004 18:33 GMT I opened an On-line support case on this specific problem about a month ago. Microsoft is aware of the problem. Don't know about any impending fixes.
-Gerry
> No problem, glad to help. > [quoted text clipped - 10 lines] >> >>Thanks. I deleted that hotfix, and now I can reboot. Robert Comer - 21 Jun 2004 18:37 GMT At least they know.
It's kind of a nasty problem as it's not really good to be without that patch...
- Bob Comer
> I opened an On-line support case on this specific problem about a month > ago. Microsoft is aware of the problem. Don't know about any impending [quoted text clipped - 16 lines] > >> > >>Thanks. I deleted that hotfix, and now I can reboot. Gene van Troyer - 27 Jun 2004 06:23 GMT On 6/22/04 2:37 AM, in article #41ppZ7VEHA.2996@TK2MSFTNGP12.phx.gbl,
> It's kind of a nasty problem as it's not really good to be without that > patch... Well, this was helpful, even if it doesn't lead immediately to a real fix. I'll leave everything as is, and just shut down the VPC Guest and start it up. I don't want to leave the OS vulnerable--though with the recent announcement about the Worm from Russia that exploits Internet Explorer (which never seems to get fixed, no matter how often it is "fixed").
Gene van Troyer -------------------------------------------
| Office 2004 | OSX.3.4 | PBG4 | iMac 20" | -------------------------------------------
gartmann@immunbio.mpg.de - 28 Jun 2004 16:37 GMT We have exactly the same problem. We opened a case with Microsoft. But there they didn't seem to know that this is already a known problem. I think more people should open a case.
Regards, Christoph Gartmann
|
|
|