Windows 8 Won't Boot (Black Screen, No Mouse)

Toggle sidebar Toggle sidebar
MrJak

MrJak

Distinguished
Jun 2, 2013
274
0
18,810
This happened about a week ago, when I was doing a few reboots, timing my startup speed with a program called bootracer.
It was rebooting perfectly until I disabled a few programs, none of which were essential to Windows, and then it didn't fully boot the next time, and it just stayed on the black screen.

I tried Windows Restore, and as it has so many other times, it failed. Though, seeing as it was only hours, if not minutes, behind, it would have been perfect and wholly welcome.

I've heard that sometimes letting it sit will fix it, but I don't think Raid 0 SSDs would have that issue?
(Though I will try it again anyway, and let it sit up to twenty-four hours, as someone said fifteen did it for theirs.)

Any and all suggestions are welcome. :)
I am, however, aware that I probably could easily refresh the install, and lose a minimal amount of data, but I'd rather lose none, and gain the experience of fixing this specific issue.

Added notes:
I also figure it'd might be worth noting that I'm running another install of Windows 8 on a laptop hard drive in the same computer.
I'm also using multiple GPUs (a GTX 570 and a 8600 GTS), and have three displays. They were working fine before this issue, and are working fine with the laptop drive, but I thought I'd share that. (Also the nVidia drivers are up-to-date on both installs)

Also, specs are :
CPU: "Q9400 @3.6Ghz"
GFX: "GTX 570 + 8800GT"
MOBO: "XFX NVIDIA nForce 790i Ultra SLI"
RAM: "Crucial Ballistix 8GB (2 x 4GB) DDR3 1600 CL8"
PSU: "750W ThermalTake"
SSD: "Two SNV425-S2/64GB SSDs in Raid 0"
HDD: "500GB Seagate + 500 GB WD"
BLU: "LG BD-ROM/DVD Rewriter"
DVD: "LightScribe CD/DVD Burner Drive (from oldbuild)"
CPU cooler: "Corsair Hydro H50?"
CASE: "Antec p180"
fans: one intake and two (three with CPU) exhaust"
 
Solution
MrJak
It has been fixed: not an SSD issue, just a broken boot record, it seems.

One of the following commands, or a series of them, fixed the issue:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
bootrec /scanos

I figure it was the first two.

(definitely not putting SSDs in RAID :na:)
Sort by date Sort by votes
MrJak

MrJak

Distinguished
Jun 2, 2013
274
0
18,810


Unfortunately for that idea, it's a Raid 0 array, so the data is split in half on both, and the data is inaccessible from one drive at a time. ^^;

Thanks for the suggestion though.
 
Upvote 0 Downvote
brarboy

brarboy

Honorable
Jan 13, 2014
2,122
0
12,460


i mean you try some other storage device which has OS installed, and make sure if its your raid causing you sych problem.
 
Upvote 0 Downvote
MrJak

MrJak

Distinguished
Jun 2, 2013
274
0
18,810


Such as copying the image to another HDD, such as the one I'm running now?
Or just running another copy of the OS on the same computer?
 
Upvote 0 Downvote
brarboy

brarboy

Honorable
Jan 13, 2014
2,122
0
12,460


then there might be something wrong with your either Raid or hdd. I think re-installing OS and re-configuring your raid is only solution.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
Running raid 0 on a SSD is generally just not a good idea.

SSD do a lot of work in their firmware (garbage collection, TRIM functions)
and they do these functions on their own timing schedules. Also, these internal routines will not be synchronized between the two solid state drives.
I would expect that it would work for a short time, at least until one of the drives needs to reallocate a block or process TRIM functions (done when idle)

I would wipe the drives and reinstall without raid. (not even a mirror)
 
Upvote 0 Downvote
MrJak

MrJak

Distinguished
Jun 2, 2013
274
0
18,810


I've been told that these just don't run at all on SSDs in RAID. Unless you can point to any one place where this is stated as fact, I'll look into other options. Also, I can open the array and move files between it and my current hard drive, so the files are perfectly fine.

Also, as a note, this hard drive that I'm running is also a refreshed Windows 8 that had the same issue, cause by a different person, with no single reason that it had happened. The only thing that can come to mind is Windows updates.
 
Upvote 0 Downvote
MrJak

MrJak

Distinguished
Jun 2, 2013
274
0
18,810
It has been fixed: not an SSD issue, just a broken boot record, it seems.

One of the following commands, or a series of them, fixed the issue:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
bootrec /scanos

I figure it was the first two.

(definitely not putting SSDs in RAID :na:)
 
Upvote 0 Downvote
Solution
brarboy

brarboy

Honorable
Jan 13, 2014
2,122
0
12,460


glad you figured it out and thanks for posting your solution. Hope it could help someone else in future.
good luck :)
 
Upvote 0 Downvote
MrJak

MrJak

Distinguished
Jun 2, 2013
274
0
18,810


Thanks!
It's my pleasure to help! XD
 
Upvote 0 Downvote
MrJak

MrJak

Distinguished
Jun 2, 2013
274
0
18,810
Also, as a note, my computer had problems with drivers afterward, and not able to load some programs, such as Windows 8 apps.
I fixed this with a registry cleaner, specifically the one from Iobit's "Advanced System Care"
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom