PC Unresponsive after log in

[Giltintur]

I really need some help.
I have yesterday set up my Windows 10 PC's calendar to sync with my company schedule, and had - without giving it much thought - accepted all group policies. After that I went to work, and my fiance - using the pc - had to enter a password to the single account in accordance with the group policy.
Now, today when switching on the PC she had been somewhat vague about what our new password is, so it took quite a few tries to enter the correct one.

Now what happens is that when I enter the correct password, I get through log-in and from that point nothing works.

• 
  ■ I see my desktop (the desktop folder is on a different drive than the system), however the default icons show for my computer and the recycle bin, I guess because these Icons are on the system drive.
  ■ The cursor moves, but pointing to the start menu it just shows the blue circle loading sign.
  ■ The lights on the keyboard work (numlock, capslock) but I can't get any combinations to work.

So I guess my windows drive is locked, but I can't do anything.

So I tried restarting, waiting, and fixing wiht the install disk.

• 
  ■ If restarting the error is fully identical.
  ■ If I wait, the desktop goes black after a while, the cursor keeps working... well moving, but the start menu icon is unresponsive and the toolbar doesn't load.
  ■ I inserted my windows 10 dvd, and got to command prompt, but I can't even run chkdsk on the locked drive.
  

  Update: the command prompt from the windows dvd doesn't even see the system drive.

Any ideas what I can do?

The only idea I have is to install Windows on a different drive, but I'd much prefer to get back to my current install.

Update I have Installed windows to one of my other drives, the old system (lets call it OCZ) sometimes shows up, sometimes doesn't... chkdsk /f co,pleted without error, the previous troubles persist.

Update 2 C:\>chkdsk /f /v /r /b /offlinescanandfix h:

Spoiler

The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
186880 file records processed.
File verification completed.
6635 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
254322 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
33722 data files processed.
CHKDSK is verifying Usn Journal...
8839072 USN bytes processed.
Usn Journal verification completed.
Removing 6 clusters from the Bad Clusters File.

Stage 4: Looking for bad clusters in user file data ...
Windows replaced bad clusters in file 28985
of name \PROGRA~3\MICROS~1\Windows\WER\REPORT~1\NO21F0~1\Report.wer.
Windows replaced bad clusters in file 80373
of name \PROGRA~3\MICROS~1\DIAGNO~1\events00.rbs.
Windows replaced bad clusters in file 82171
of name \PROGRA~3\MICROS~1\DIAGNO~1\events01.rbs.
Windows replaced bad clusters in file 82172
of name \PROGRA~3\MICROS~1\DIAGNO~1\events11.rbs.
Windows replaced bad clusters in file 82554
of name \Users\Sünök\AppData\Local\Comms\Unistore\data\3\k\10000F~1.DAT.
Windows replaced bad clusters in file 84086
of name \Users\Sünök\AppData\Local\MICROS~1\Windows\NOTIFI~1\appdb.dat.
Windows replaced bad clusters in file 103406
of name \Users\Sünök\AppData\Local\Comms\Unistore\data\3\n\20000F~1.DAT.
Windows replaced bad clusters in file 133192
of name \PROGRA~3\MICROS~1\Windows\WER\REPORT~1\NO3D14~1\Report.wer.
Windows replaced bad clusters in file 151225
of name \SYSTEM~1\{EED36~1.
Windows replaced bad clusters in file 163495
of name \PROGRA~3\MICROS~1\Windows\WER\REPORT~1\CRE7AB~1\Report.wer.
Windows replaced bad clusters in file 164772
of name \Users\Sünök\AppData\Local\Comms\Unistore\data\3\j\30000F~1.DAT.
186864 files processed.
File data verification completed.
An unspecified error occurred (766f6c756d652e63 461).

 

[Giltintur]

Update yet again: It seems, turning of fastboot is a solution. Weird, considering I have been using fastboot since I have this hardware and since I have windows 10.