Change username and logout problem - not supported

When the user switching or disconnection of the screen becomes black and unsupported is in big letters white, it restarts the computer, I start windows normally, then a box just telling me I was expectantly stop and windows will search for a solution, I have 3 users myself as an administrator and two others, if I start it in safe mode, you can switch or disconnect any problems. I uninstalled the last program which had been installed and tried to do a restore of the days different samples about 5 times each time I also unplugged my external hard drive in case that was the problem

Can anyone help please

Each of the three towers of programs, services, and drivers in increasing amounts. So restrict the possible culprits.

Clean boot

Click Start - all programs - Accessories - run and type
 
msconfig
 
Then go to the Startup tab uncheck everything. Then go to the Services tab check hide all Microsoft Services and uncheck everything that is left.
 
Reset. If this resolves your wake problem ½ of services / of startup items until you find that one.

Tip clean boot

If the above does not help.

Download Autoruns http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx

Start the program by right-clicking and choosing run as administrator and click on the menu Options - Filter Options and check hide Microsoft entries and disable include the empty slots. Go to the all tab and uncheck everything to the left.

Reset. If this resolves your wake problem half of the items until you find the one that.

Blue screens are caused by defective material or defective hardware drivers.

To see if a fix is available

In Control Panel (and select Classic discovered in the left pane) select reports on the problems and Solutions (problem of type in the START search box), go to historical problem, right-click of your error and choose check for the Solution. You can also right-click and choose Details for more information. Post these details here.

To see if any recent system change caused it

In Control Panel (and select Classic discovered in the left pane) choose Administrative Tools and then choose reliability and performance monitor and choose the monitoring tools then the reliability monitor (type reliability in research on Start). This list is a chart of the software installs, uninstalls, updated Windows and crashes by date (scroll left to see earlier dates). See if your plant has started to happen after you installed or uninstalled something.

 
Standard hardware troubleshooting
 
 
First to test we can the material. Material defects can appear as many software defects, that's why we need to test the material first...
 

Follow these steps in order. Defects of memory can cause disk corruption, disk failures can cause corruption of the disk. Damaged disc causes corrupted files (which SFC may be able to fix). If you get a stop error and after return. Do not run chkdsk with faulty memory.

 
Diagnosis of memory
If you have not run a diagnosis of memory, please do. Click on Start - Control Panel - choose Classic view in the left pane - choose Administrative Tools - then memory diagnostic tool.
 

S.M.A.R.T
Start - All Programs - Accessories - right on command prompt and choose run as administrator. Type (or copy and paste by clicking in the command prompt window and choose Paste).
 
Disk in Windows drives monitor for impending failure. The function is called S.M.A.R.T. It detects an imminent failure, 30% of the time. In a type elevated command prompt (it's a single line)
 
WMIC PATH MSStorageDriver_FailurePredictStatus /namespace:\\root\wmi get active, predictfailure, reason List
 
If it is on will be true, otherwise on enable in the BIOS of the computer.
 
Predict the failure must be False if everything is ok.
 
In Vista and later if SMART failure predicted Windows prompts the user to run the backup.
 
Run chkdsk
In computer all your drives right click and choose Properties, then the Tools tab, and then click check now. Check the TWO boxes and then start. Reset. This will take from one day to the next.

 
SFC
Check the alteration of the file by clicking on Start - All Programs - Accessories - right on command prompt and choose run as administrator. Type (or copy and paste by clicking in the command prompt window and choose Paste).
 
sfc/scannow
 
Heat
Heat can lead to problems of this kind, and sudden restarts without crashing. Make sure that your fans are not clogged with dust.
 
For memory diagnostic results
Click on Start - Control Panel (and select Classic view in the left pane), select Administrative Tools and then Event Viewer , and then look in the event (Local) - Applications and Services - Microsoft - Windows - MemoryDiagnostic-results Viewer entered.
 
Look for EventID is 1201 or 1101 and Source is MemoryDiagnostic-results

 
Double-click the entry for more details on this entry.

For results of Chkdsk

Click on Start - Control Panel (and select Classic view in the left pane) choose Administrative Tools and then Event Viewer , and then look at the Application and the System will connect (under Windows logs) for entries.
 
Look for EventID is 7 and Source disk
Look for EventID is 11 and the Source disk
Look for EventID is 51 and Source disk
Look for EventID is 52 and Source disk
Look for EventID 55 and Source is NTFS
Look for EventID is 130 and Source is NTFS

Look for EventID 1001 and Source is Autochk
Look for EventID 1001 and Source is Winlogon
Look for EventID 1001 and Source is WinInit
Look for EventID 1001 and Source is Chkdsk
Look for EventID is 26212 and Source is Chkdsk
 
Double-click the entry for more details on this entry.
 
PS 7 and 55 are auto repair codes where windows repair disk errors silently on the fly. 52 is the SMART warning.

 
For the results of the SFC
Start - All Programs - Accessories - right on command prompt and choose run as administrator. Type (or copy and paste by clicking in the command prompt window and choose Paste).
 
findstr/c: "[SR] cannot" %windir%\logs\cbs\cbs.log|more "
 
It will be able to see which files are corrupted.
 
To see if there
 
findstr/c: "[SR] repair" %windir%\logs\cbs\cbs.log|more

 
There are often false positives for small text files that Windows uses like settings.ini and desktop.ini. Ignore these.
 
 
Dump files
 
Dump files are files containing the status of the machine when it crashed. We can analyze the file to identify the driver (or program) causing the accident. See the last section on how to get them analyzed by a volunteer.
 
Analyze dump files
If you want to analyze your own dump files.
 
You need start exploring as an administrator to access the files in C:\windows\Minidump. Explore a right click and choose run as administrator.

Download and install the debugging tools for Windows
Install Windows SDK, but simply choose the debugging tools.

Create a folder called symbols in C:\

Start Windbg. Menu file - path to the symbol file and enter


SRV * C:\symbols* http://msdl.microsoft.com/download/symbols
 
Close, and then reopen WinDbg. Menu file - Open Crash Dump

It will analyze the crashdump. You must close and reopen WinDbg for each analyzed dump file. Because you download symbols from the internet WinDbg seems to be to do nothing. But it's the download. Be patient.

 
Looking for a driver or a library system that the incident occurred at the end of the list. Find the file, do a right click then Properties - Details tab. If it shows a driver, you will need to update the driver identified. Most of the pilots are in c:\windows\system32\drivers.
 
Look for the drive for a file.
Click Start - All Programs - Accessories - right on command prompt and choose run as administrator. Type by replacing drivername.sys by the name of the file (or copy and paste by clicking in the command prompt window and choose Paste).

dir c:\ drivername.sys/a/s

 
If it has a file system see if you can get a program to analyze - v.

Type in the theWinDbg command prompt

 
! analyze - v
 
-v means Verbose and if the accident was created by a program, as opposed to hardware or a driver, it will appear in the middle of the list.
 
for example
 
Nom_processus: java.exe
Nom_image: ntkrnlmp.exe
 
Nom_processus does not appear in the output of v - analyze and only if a program is from the call that was blamed.
 
Download them for analysis
 
Or download files minidump to your Public SkyDrive folder and copy the link in the address bar, and I'm going to do an analysis.
 
SkyDrive is the download file from Microsoft, Windows Live, at https://skydrive.live.com/site.  Read about it at http://explore.live.com/skydrive.

If you downloaded one of the Live applications or a web site based Live mail account, you already have access to your Skydrive.

Put your list of events in the Public folder and copy the link in the address bar.

Tags: Windows

Similar Questions

Maybe you are looking for

  • Partitioned hard drive share info?

    I followed the instructions of Eric Root (thanks), partitioned the hard drive and installed El Capitan.  El Capitan works completely separate or shared information with the original Mountain Lion?  (I did not migrate about Mountain Lion.) My reason f

  • Is there something for the protection of the screen?

    HeyHave tryid to look around for something protecting my screen with when I wriding on it. Cause he was only 2 months old now and already had a few scratchses. Then I wanted to know that there is any kind of protection 'film' for her as offer what nu

  • Wireless driver for HP ProBook 470 G1

    Hello guys,. The other day I installed primary OS on my laptop. I can not connect to wireless internet. The problem persisted on Debian and OpenSUSE. Also, I have seen that HP provides drivers for SUSE, but I can't install it on OpenSUSE. Thank you!

  • no pre installed games

    games like spider and other

  • Limits of motherboard memory

    Hello, I helped myself with a question of processor recently here and have one of more to ask. My pc is a HP Pavilion p6300uk, it hasan Athlon 2 x 2, I recently ordered a Phenom 2 x 4 The motherboard is a card mother M2N68-(Narra6). In the report on