Winlogon error

Started by Rik, Mar 13, 2009, 15:57:46

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Rik

Since I applied this week's MS updates to my Sammy NC10, I've started to get a problem with Winlogon errors.

At startup, if I get a 'Winlogon encountered an error and had to quit', I can hit the 'send to MS' button and the machine operates normally, and will shut down normally.

However, on the next boot, I don't get the Winlogon error, but when I power off, I get a BSOD fatal error - too briefly to catch the number - and the machine re-starts, with the Winlogon error again.

Initially, I thought it was down to the patches so rolled back and then re-installed. Windows had installed a .NET 1.1 service patch, which was odd as .NET is not installed (must pay more attention :)). Leaving that off, all seemed to be well again. However, the machine's just done it again, but only once.

I've done the usual virus & spyware sweeps, which covers many of the suggestions I Googled, and I do only have one copy of the file, in Sys32. I've now turned off auto-restart, so that I can note the error code - but, of course, it's behaving perfectly atm.

Does anyone have any thoughts on this please?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

cavillas

It's BT at it again. ;D  I blame them for everything these days it's easier that way. :evil:
------
Alf :)

Rik

I know what you mean, Alf, and if it's not BT it's the Govt. ;D
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

trophymick

Mick

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Simon

I've been getting a strange runtime error each time I start my Windows XP PC for the last few days.  Have to admit, I've turned a blind eye to it, but will grab a screenshot next time.  I wonder if there's been a dodgy Windows Update?
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Steve

I never did get to the source of the Advent 4211 errors and bsod. Removing the additional memory had no effect either. Mine's still at the menders but I will say it was completely stable for about 4 months I too blamed netframework 1.1 and 3.0 etc but never solved the problem with destructive re installs which in themselves were always an error ridden process using a combination of the EISA partition and USB stick. I hope yours is not going the same way.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Quote from: Simon on Mar 13, 2009, 16:49:13
I've been getting a strange runtime error each time I start my Windows XP PC for the last few days.  Have to admit, I've turned a blind eye to it, but will grab a screenshot next time.  I wonder if there's been a dodgy Windows Update?

It's happened before. Curiously, WinUpdate tried to put the same .NET patch on the notebook and failed. Weird.  :shake:
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

zappaDPJ

Hmmm, one of the many Vista updates I've received over the last 48 hours had catastrophic effects on this PC.

It shut down my primary monitor and transfered the Desktop to a secondary device. It removed all but the basic functionality of my mouse and acted as if my PC had been unplugged from the network. All the devices were present and correct with drivers in System Properties but I could not get any of them to work.

I've rolled back and blocked a number of updates but I need to work out which one caused the issue.
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

The joys of 'patch Tuesday'. :sigh:
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

JB

Quote from: Rik on Mar 14, 2009, 07:56:12
The joys of 'patch Tuesday'. :sigh:

Being a suspicious soul I always make a quick Acronis backup of my c: drive before downloading M$ upgrades.

Other than that Rik, how are you getting on with the Sammy? I would dearly love one.
JB

'Keyboard not detected ~ Press F1 to continue'

Rik

It's great, JB (and I too backed up first :)). The keyboard is pretty much the same size as a notebook and has a similar feel, the screen is excellent, very crisp and bright enough to use outside. WiFi performance is good, speed is surprisingly good though I wouldn't want to run Photoshop on it. My only gripe is the touchpad, but then I always use a mouse anyway. Thoroughly recommended.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

JB


Thanks Rik. Just need to flog some stuff on Ebay to gather the pennies for one.
JB

'Keyboard not detected ~ Press F1 to continue'

Rik

Consider switching to 2GB RAM if you go for it, Alan, it makes a big difference. Unfortunately, it's switch rather than add 1GB, but it's worth it. Also, don't buy a case for it, it comes with one, but no-one mentions the fact. It has 3 x USB posts, ethernet, headphone & mike plus a VGA out. The internal speakers are adequate, but if you want to listen to music or watch DVDs, you need to use headphones or external speakers, imo. There's no optical disc, but I just used the LAN to share one, works fine. The Bluetooth seems very effective and Samsung supply an XP recovery CD plus their own software on DVD in case you need to re-install. When you first start up, it will register Windows and then go on to create a recovery partition and two partitions for use (C/D). Battery life is around 6.5 hours in my tests.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Simon

Reversing back up the drive to the original topic, this is the error I get on most startups.  Although, helpfully, it doesn't say to which program it refers, when minimised to taskbar, the Nokia PC Suite icon is displayed, so I guess it has to be something to do with that.

[attachment deleted by admin]
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

Any information in the Event log?
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Don't you just love helpful error messages. :sigh:
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Ann

Quote from: Rik on Mar 14, 2009, 07:56:12
The joys of 'patch Tuesday'. :sigh:

I always wait till the following Saturday  ;)

Rik

Very wise - I was just testing for the members here you understand.  ;D
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

vitriol

A friend of mine has been getting the Winlogon error (but it was BSOD) on each boot.  Only cure was a reinstall of Windows. :( 

I had to take out his hard drive and put it in my PC to get the documents and pictures that he wanted ; why don't people backup regularly?  10GB of stuff !!!!!!!!

Steve

It odd this, I was talking to a colleague at work this evening and he said out of the blue " I am sure MS is deliberately sabotaging XP by releasing faulty updates I've had terrible problems recently." Paranoid he maybe but it does make me wonder at the quality of the recent updates as there does seem to be a few people with issues on once very stable systems.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

I wouldn't put it past them, Steve, and yet they are specifically targeting XP Home at netbooks.  :dunno:
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

That was my reply although I did mention a cut down version of 7 is expected.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Ann

Well I did updates yesterday and no logon problems so I'm guessing that if there was a problem MS sorted it out in the meantime.   :phew: