No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


VM BSOD Caused by a User Configuration File Error

Publication Date:  2014-05-06 Views:  184 Downloads:  0

Issue Description

 After a user logs in to a VM using a domain account, black screen of death (BSOF) occurs and no operation can be performed.
 After the user logs in to the VM using another account, the system can be used properly.

Alarm Information


Handling Process

1. Log in to the VM using the administrator account.
2. Go to C:\Users, rename the folder that is named after the abnormal account. For example, if the user account is Test001, there will be a Test001 folder. You are advised to add the letter a after the folder name, that is, Test001a.
3. Open the registry editor, find the key value of the user configuration file, and rename it:
Key value: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
According to the ProfileImagePath value of the abnormal domain accounts, find the related key S-X-X-XX on the left, and rename the key by adding the letter a to the end.

4. Close the registry editor and restart the VM.
5. Use the abnormal account to log in to the VM. The login is successful.

Root Cause

According to the fault symptom, the fault is caused by a user configuration file error.


 If the VM login is successful using another account, you can generate a new configuration file to quickly rectify the fault.
 After generating a new user configuration file, you need to manually restore certain personalized configuration data.