Winlogon Error

I'm using Windows XP, Media Edition and have had the PC for about a year. It has never had a glitch until yesterday. When my signon screen appears, I (owner) can sign on, but when my wife chooses here name I get an error window:

"SAS Window: Winlogon.exe application error
The required data was not placed into memory because of an I/O error status "

The computer then reboots. It does the same thing no matter who logs in other than me.

Any suggestions?

 

Still having problem

I tried to recreate another logon name, but still not working. I am also having problems with Microsoft Office 2003, Word, Excel, Access, PowerPoint, the whold suite, nothing will come up. Errors mainly refer to msiexec.exe errors. Have tried reloading office, tried reloading the msiexec.exe, but nothing is working

 

Error Message

This is the error when I choose a user other than Owner (myself)

SAS Window: Winlogon.exe Application Error
The instruction at "0x5ad862ca" referenced memory at "0x01758000 ". the required data was not placed into memory because of an I/O error status of 0xc000009c


This occurs every time, the reboots the PC.

 

Hi, purdyc. Welcome to Windows BBS!

I Googled Winlogon.exe "I/O error status of 0xc000009c " and got 5 results. One of those results suggests the possibility of a virus. Unfortunately, there was no follow-up response so we have know way of knowing what turned out to be the cause.

I searched the Microsoft Knowledge Base for I/O error status of 0xc000009c which lists some possibilities (including a possible virus).

I suppose it's possible a virus is "compatible" (for lack of a better term) with your Owner account but is "incompatible" with other users' accounts.

Have you scanned your computer with updated reputable anti-virus software since the problem started occurring? A couple online virus scanners are suggested here.

==========

Event Viewer might shed some light on your issue.

Instructions About How to Access and Use "Event Viewer ":

• Click Start.
• Right-click My Computer.
• Select "Manage" to open the "Computer Management" window.
  (Event Viewer will be displayed under the "System Tools" directory item.)
• Expand "Event Viewer" and then select "Application ", "Security ", and "System" to view the logs.
• Look for "error" events that occurred around the time your problem occurred. These events will be displayed as icons with either a white X on red background or a black exclamation point on yellow background. In the security section of Event Viewer, events of possible concern are ones that display a padlock icon instead of a key icon.
• Double-click on an individual event to open the "Event Properties" window which shows details about the event.
  • You can use the up/down arrow buttons in the "Event Properties" window to move your focus to other events in the list.
  • Use the button below the up/down arrows to copy the details for an event to your clipboard for pasting elsewhere.
  • Click on the "http://go.microsoft.com/fwlink/events.asp" link in the "Event Properties" window to view more information from Microsoft about the event.

Alternatively, Event Viewer may be accessed as follows.

• Click Start > Run...
• Type [FONT= "Courier New"][SIZE= "3"]eventvwr.msc[/SIZE][/FONT] in the "Open:" field.
• Click the OK button.

==========

If you could produce DebugWiz-generated dump logs for the crashes/reboots, that information might be helpful too.

Please carefully follow all the instructions in this link and then paste a few of your most recent DebugWiz-generated BSOD dump log analysis reports in this thread.

The DebugWiz application should be run while connected to the Internet so your Windows Debugging Tools can retrieve the proper "symbols ". The additional information the DebugWiz-generated reports provide might help us narrow down the culprit more quickly.

For critical program errors, the DUMP file will be found in \Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp

For "Blue Screen Of Death" (BSOD) system crashes (such as you appear to be experiencing), the DUMP file will probably be found at C:\WINDOWS\Minidump\Minixxxxxx-xx.dmp (mini-model setting: The x's before the dash represent the date of the crash and other two x's represent the crash count for that day.) or be found for large model settings at C:\MEMORY.DMP

==========

If you find your system won't let you install and run the applications in the link I just provided, then your 2nd-best option might be to see if we can at least get your machine to display a "Blue Screen of Death" (BSOD) instead of automatically rebooting. Then, when a BSOD appears, copy down the exact error code information and provide that here. You'll have to write the information on paper. (I don't think there is a convenient way to simply print the info or save it to disk.) It might not be enough information to go on but it might be worth a shot.

Here is how to configure your machine to display a BSOD for a system crash instead of automatically rebooting.

• While holding down your Windows Key, press your Pause Key to bring up your "System Properties" window.
• Click the Advanced tab.
• In the Startup and Recovery section, click the Settings button.

Make the following settings in the "System failure" section:

1. Check mark: "Write an event to the system log "
2. Check mark: "Send an administrative alert "
3. NO check mark: "Automatically restart "
   (You should be able to read your BSOD screens after making this setting.)
4. Write debugging information: Kernel memory dump
5. Dump file: %SystemRoot%\MEMORY.DMP
6. Check mark: "Overwrite any existing file "
7. Click on the OK buttons until you are back to your normal screen.

If you want to keep backups of your MEMORY.DMP files, then (after each BSOD crash) rename the MEMORY.DMP file (keeping the .DMP extenstion) and/or copy the c:\MEMORY.DMP file to another folder and rename as desired (keeping the .DMP extension).

The next time your system crashes, you should see a BSOD with error information. If you post that exact information here, someone might have an idea about how to proceed.