Win 7 can't boot but start-up repair can't detect anything

[Lennardson]

Since the 11th of Jan I have been experiencing a black screen with just the mouse courser shown when booting my computer, as of reading other threads I tried holding f8 and manually starting start-up repair which did not work, (On the first attempt I got that start-up repair couldn't fix it details below) I was stupid enough not to create any back-ups so that didn't work, I also tried the SFC -SCANNOW to get a clean test. If you require any information in order to help me put your question down below and I will get back to you.

Thanks,
Aaron (Lennardson)

PS. This is the problem in all safe modes.

Details

Problem Event Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: Unknown
Problem Signature 04: 21199997
Problem Signature 05: AutoFailover
Problem Signature 06: 17
Problem Signature 07: CorruptVolume
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

 

[Kaktussoft]

After F8 advanced boot options->repair your computer, you did a startup repair.
Do "command prompt" instead of startup repair. Then:

diskpart
list vol
exit

Do you see all the partitions you expected? I'm not interested in DVD/CD or external stuff now. Detach external drives anyway if testing.
What drive letters are pointing to the internal disk?

DIR C:\
DIR D:\
DIR E:\

What is the drive letter of the win7 volume?

 

[Lennardson]

Forget this was here.

 

[Lennardson]

After F8 advanced boot options->repair your computer, you did a startup repair.
Do "command prompt" instead of startup repair. Then:

diskpart
list vol
exit

Do you see all the partitions you expected? I'm not interested in DVD/CD or external stuff now. Detach external drives anyway if testing.
What drive letters are pointing to the internal disk?

DIR C:\
DIR D:\
DIR E:\

What is the drive letter of the win7 volume?

Well C is labeled TI30908000A and D is system

 

[Kaktussoft]

0 E
1 C
2 D
3 F

Hope that helps

All on internal hard disk? I don't wat you to list DVD/CD. Anyway now do in "command prompt":

chkdsk/f  C:
chkdsk/f  D:
chkdsk/f  E:
chkdsk/f  F:

Problems on any of the volumes? Repaired? What kind of errors?
Eventually run chkdsk/f again to prove it's fixed

 

[1fsmed]

I am having the same issue, so please continue with potential resolution methods. Thx

 

[Kaktussoft]

After F8 advanced boot options->repair your computer, you did a startup repair.
Do "command prompt" instead of startup repair. Then:

diskpart
list vol
exit

Do you see all the partitions you expected? I'm not interested in DVD/CD or external stuff now. Detach external drives anyway if testing.
What drive letters are pointing to the internal disk?

DIR C:\
DIR D:\
DIR E:\

What is the drive letter of the win7 volume?

Well C is labeled TI30908000A and D is system

DIR C:\
DIR D:\
etc. Which drive letter has a windows folder and users folder, so is the win7 volume?

 

[Kaktussoft]

I am having the same issue, so please continue with potential resolution methods. Thx

Also "Problem Signature 07: CorruptVolume"? Make a new thread please

 

[Lennardson]

After F8 advanced boot options->repair your computer, you did a startup repair.
Do "command prompt" instead of startup repair. Then:

diskpart
list vol
exit

Do you see all the partitions you expected? I'm not interested in DVD/CD or external stuff now. Detach external drives anyway if testing.
What drive letters are pointing to the internal disk?

DIR C:\
DIR D:\
DIR E:\

What is the drive letter of the win7 volume?

Well C is labeled TI30908000A and D is system

DIR C:\
DIR D:\
etc. Which drive letter has a windows folder and users folder, so is the win7 volume?

C and when I did the chkdsk it said that it failed to transfer logged messages to the event log with a status 50

 

[Kaktussoft]

failed to transfer logged messages to the event log with a status 50 .. quite normal in recovery envrionment.

chkdsk/f C:

no errors at all, or did it fix them?
Same for D,E, F?

Are you very sure C is drive letter of win7 in recovery environment?

 

[Lennardson]

failed to transfer logged messages to the event log with a status 50 .. quite normal in recovery envrionment.

chkdsk/f C:

no errors at all, or did it fix them?
Same for D,E, F?

Are you very sure C is drive letter of win7 in recovery environment?

Looking back it says that windows has made corrections and on the second test it found no problems should I try to re-boot?

 

[Kaktussoft]

failed to transfer logged messages to the event log with a status 50 .. quite normal in recovery envrionment.

chkdsk/f C:

no errors at all, or did it fix them?
Same for D,E, F?

Are you very sure C is drive letter of win7 in recovery environment?

Looking back it says that windows has made corrections and on the second test it found no problems should I try to re-boot?

Look better next time! C,D,E,F fine now? Reboot normally and post results

 

[Lennardson]

Sorry about that, I tried all the outher drives to find them invalid but when I re-booted it still showed the black screen

 

[Lennardson]

Oops when doing the command I typed it wrong, sorry I will try again

 

[Lennardson]

Corrected f: but still just shows cursor

 

[Kaktussoft]

Corrected f: but still just shows cursor

C,D,E,F : chkdsk fixed the errors? Errors were on C only?

Try startup repair again and post results. You can click "view diagnostics details" there. Post what tests don't have status code 0x0

 

[Lennardson]

They all have 0x0

 

[Kaktussoft]

Any idea when this problem started? What did you do just prior to that that could have caused it?

 

[Kaktussoft]

They all have 0x0

So startup repair didn't find an error?

When is the black screen with cursor, I mean:
Do you see the win7 logo?
Is it animated?
You see the usernames to logon?
you actually can logon?

 

[Lennardson]

Well I was installing an update to a game, but I doubt that was it since no one else who I know had the the same problem, then my computer froze I could ctrl alt del or anything, I could still open windows from my task bar but I couldn't interact with them so I manually shut it down and got this.