winlogon error - BSOD
Author
Discussion

FunkyGibbon

Original Poster:

3,863 posts

294 months

Tuesday 10th October 2006
quotequote all
Peeps at work are having intermittent winlogon errors that lead to BSOD...

Application popup: winlogon.exe - Application Error : The instruction at "0x74ef400e" referenced memory at "0x00000000". The memory could not be "written".

it is only intermittent and happens both on the Sony Viao laptops and Dell desktops.

I've had a quick search of Micro$oft site and can't find anything useful.

Now we do run multiple logon servers - could this be the cause of the intermittent effect?

Any ideas from the PH collective?

many TIA.

FG

greenlandy

1,635 posts

261 months

Tuesday 10th October 2006
quotequote all
I've just done a quick google and nothing seems concrete on how to fix it! Sorry. I take it you have run full AV/Malware sweeps?

FunkyGibbon

Original Poster:

3,863 posts

294 months

Tuesday 10th October 2006
quotequote all
greenlandy said:
I take it you have run full AV/Malware sweeps?

we should have AV/malware done automatically every day - but I'll double check, thanks

FG

aldi

9,292 posts

267 months

Tuesday 10th October 2006
quotequote all
I'd check for any other strange entries in the event logs, any warnings or anything thats occouring on the problem laptops that isnt on the others.

thepassenger

6,962 posts

265 months

Tuesday 10th October 2006
quotequote all
Bad update being pushed out by a vendor that's not hit all the machines?
Poke in to event log and take a look, also look at what these laptops run on boot/login and see what's different about them compared to the other working machines. This sounds sarcastic but what ever is different will usually be the cause for whatever reasons.

BliarsGoing

72,863 posts

269 months

Tuesday 10th October 2006
quotequote all
Set the machines in question to do a full memory dump and then once they're back up run the debug tools with !analyse -v

Tripps

5,814 posts

302 months

Tuesday 10th October 2006
quotequote all
I see that type of error from one of the 3rd party systems, it runs as a service and can get the hump at times.

As mentioned check the logs, specifically the system log, as that will record any services that won't start or terminate unexpectedly.

R1 GTR

2,152 posts

243 months

Tuesday 10th October 2006
quotequote all
This PC does that too. And its a stand-alone system at home!