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 | Rate Thread | Display Modes |
#1
|
|||
|
|||
"Welcome" for ever -- RAM ?
"When you log on to a computer that is running Windows Server 2008 R2 or
Windows 7, the logon process stops responding and a blue swirl is shown on the Welcome screen indefinitely." says http://support.microsoft.com/?kbid=2578159 "This issue occurs because of a race condition between the Windows Event Log service and the Event Tracing for Windows (ETW) tracing functions. When the race condition occurs, it causes a deadlock situation. This deadlock situation then causes the Winlogon.exe process to become unresponsive.." Other web sites suggest the prime cause is the many drivers Win7 loads (and tucks away as if to discourage customization for more speed.) --If so, more RAM may cure the problem. It seemed to do so in my case (Gateway NV57H50u, regularly updated, 2 Gb RAM added to total 4 Gb. I downloaded the hotfix from MS, but it said on extraction "not for this computer." -- Don Phillipson Carlsbad Springs (Ottawa, Canada) |
Ads |
#2
|
|||
|
|||
"Welcome" for ever -- RAM ?
Is this Darrell or is this Chuck?
Don Phillipson wrote: "When you log on to a computer that is running Windows Server 2008 R2 or Windows 7, the logon process stops responding and a blue swirl is shown on the Welcome screen indefinitely." says http://support.microsoft.com/?kbid=2578159 "This issue occurs because of a race condition between the Windows Event Log service and the Event Tracing for Windows (ETW) tracing functions. When the race condition occurs, it causes a deadlock situation. This deadlock situation then causes the Winlogon.exe process to become unresponsive.." Other web sites suggest the prime cause is the many drivers Win7 loads (and tucks away as if to discourage customization for more speed.) --If so, more RAM may cure the problem. It seemed to do so in my case (Gateway NV57H50u, regularly updated, 2 Gb RAM added to total 4 Gb. I downloaded the hotfix from MS, but it said on extraction "not for this computer." -- Don Phillipson Carlsbad Springs (Ottawa, Canada) -- The Grandmaster of the CyberFROG Come get your ticket to CyberFROG city Nay, Art thou decideth playeth ye simpleton games. *Some* of us know proper manners Very few. I used to take calls from *rank* noobs but got fired the first day on the job for potty mouth, Bur-ring, i'll get this one: WHAT'S YOUR PROBLEM JERK!!? We're here to help you dickweed, ok, ok give the power cord the jiggily piggily wiggily all the while pushing the power button repeatedly now take everything out of your computer except the power supply and *one* stick of ram. Ok get the next sucker on the phone. Deirdre Straughan (Roxio) is a LIAR (Deirdre McFibber) There's the employer and the employee and the FROGGER and the FROGEE, which one are you? Hamster isn't a newsreader it's a mistake! El-Gonzo Jackson FROGS both me and Chuckcar (I just got EL-FROG-OED!!) All hail Chuckcar the CZAR!! Or in F-R-O-Gland Chuckcar laCZAR, ChuckCZAR!! I hate them both, With useless bogus bull**** you need at least *three* fulltime jobs to afford either one of them I'm a fulltime text *only* man on usenet now. The rest of the world downloads the binary files not me i can't afford thousands of dollars a month VBB = Volume based billing. How many bytes can we shove down your throat and out your arse sir? The only "fix" for the CellPig modem is a sledgehammer. UBB = User based bullFROGGING Master Juba was a black man imitating a white man imitating a black man Always do incremental backups of your data or you'll end up like the A-Holes at DSL Reports. Justin says i made a boo-boo. Yeah boo-who. Updates are for idiots. As long as the thing works there's no reason to turn schizophrenic and develop a lifelong complex over such a silly issue. Adrian "jackpot" Lewis is a mama's boy! Jimmy Fricke is good for the game of poker Using my technical prowess and computer abilities to answer questions beyond the realm of understandability Regards Tony... Making usenet better for everyone everyday This sig file was compiled via my journeys through usenet |
#3
|
|||
|
|||
"Welcome" for ever -- RAM ?
"Tony" wrote in message
... Is this Darrell or is this Chuck? No. Why? DP |
#4
|
|||
|
|||
"Welcome" for ever -- RAM ?
Don Phillipson wrote:
"When you log on to a computer that is running Windows Server 2008 R2 or Windows 7, the logon process stops responding and a blue swirl is shown on the Welcome screen indefinitely." says http://support.microsoft.com/?kbid=2578159 "This issue occurs because of a race condition between the Windows Event Log service and the Event Tracing for Windows (ETW) tracing functions. When the race condition occurs, it causes a deadlock situation. This deadlock situation then causes the Winlogon.exe process to become unresponsive.." Other web sites suggest the prime cause is the many drivers Win7 loads (and tucks away as if to discourage customization for more speed.) --If so, more RAM may cure the problem. It seemed to do so in my case (Gateway NV57H50u, regularly updated, 2 Gb RAM added to total 4 Gb. I downloaded the hotfix from MS, but it said on extraction "not for this computer." Any chance the hotfix was for the original OS release, and you already have SP1 installed. Maybe SP1 also has the fix, invalidating the need for the hotfix. Paul |
Thread Tools | |
Display Modes | Rate This Thread |
|
|