Main Forum > Tweaking.com Support & Help
Scan Interrupted, Can No Longer Boot to Visible Logon Screen
lmitchell:
One last thing to mention is that I have permissions set so that users don't have to enter their user name to log on, just their password. Thus the logon windows shows four icons/avatars with user names - Administrator, two Guest accounts (decoys) and my user account (which has admin rights). *If* my user account were corrupted (and I won't be able to confirm until the D: drive scan is over) would that alone be enough to disrupt the logon screen common to all accounts?
I could probably open another cmd windows and work on the MBR (since it's on another partition) but will play itsafe and wait until chkdsk is done, as well as weigh in you thoughts on the scan results and bluescreen log (once I,m told where to find it).
lmitchell:
I,ve read the MBR restore info and it's readable an understandable, but just to clarify --
As far as i can tell the system is booting. Where the logon screen is nothing but black and a mouse cursor. Moving the cursor sometimes.effects the black "brightness". I hear all the normal drive activity as if something is happening, just can't see anything. I've even blindly pushed the button sequence to select my user avatar, enter my password and logon. I hear the activity that is customary to my desktop loading, but still nothing but black and a cursor. I can even bring up the Sticky Keys prompt and the monitor selector in the customary places prior to logon.
By contrast, the true non-boot might be the black screen with the blinking line cursor in the upper left corner. This is defrinitely not that. I see the swirl startup, the goes to black screen where the intro screen and logon would normally come up.
Another reason I think the boot may be functional (although not visible) is because from the start Last Known Good Configuration has completed by going to the black / mouse cursor screen. If the boot was broken shouldn't LKGC be presenting a result different than what has already occured?
Boggin:
If the backlight or the inverter had gone, you wouldn't even see the white cursor.
The chkdsk x: /r will be scanning all of the disk which will include partitions.
When you have access to the cmd prompt again, enter eventvwr and check to see what Errors there are which may be able to ID what else is going on.
lmitchell:
"Free space verification is complete.
CHJDSK discovered free spqce marked as allocated in the Master File Table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
(Then disk space stats, including
... total disk space
... in ... files
817564 kb in 345263 indexes
8 kb in bad sectors
... in use by the system
... occupied by the log file
3995956 kb available on the disk
4096 bytes in each allocation unit
... total allocation units on the disk
... allocation units available on the disk
Failed to transfer logged messages to the event log with status 50.
Sorry for the late reply. I fell asleep waiting for the scan to finish.
The lst line is new. I don't remember that result in orevious scans.
The bad sectors message is new. Now that I see the results I can recall that the previous message was not bad sectors but something about reallocation
lmitchell:
Boggin, when I did chkdsk I had changed the prompt to D. I didn't know better. I'll scan the boot sector separately.
Julian, I've run net users from the D prompt. It shows the same results as from X, unless I'm doing something wrong:
User accounts for // (the slashes actually go the other way)
___________________________________________________
Administrator Guest (newly created user)
The command completed with one or more error.
So none of my preexisting users are showing. The same message shows whether I use X, C or D prompt.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version