I've never been great at handling anything hardware related, but figured I should really build my own computer for once and have been running into countless problems on my latest build.
I finally got my 2.5" to 3.5" converter in for my SSD, and I kept trying to get it to show up in my windows install, and ended up giving up to just directly plug the sata and power cable into the SSD itself by taking it out of the enclosure.
It showed up in my BIOS, but didn't allow me to create a partition for windows (it said there was no harddrive registered). It showed up for once and as I was installing windows, the computer bluescreened and had an error code with a bunch of 0's and 124 at the end. I took out the SDD and installed windows on my regular HDD and now the computer won't boot at all
I'm currently running a diskcheck on the HDD since every google page that I saw had windows 7 freezing on the startup page, it's usually a harddrive error.
I have this sinking feeling it's my CPU or GPU, but I have no idea tbh. I read it could also be the SATA cables, so I'm going to try out different cables and reformat all my drives before trying to reinstall windows again...
these art the parts
http://pcpartpicker.com/user/JonTalbain/saved/2mcX
I've never been great at handling anything hardware related, but figured I should really build my own computer for once and have been running into countless problems on my latest build.
I finally got my 2.5" to 3.5" converter in for my SSD, and I kept trying to get it to show up in my windows install, and ended up giving up to just directly plug the sata and power cable into the SSD itself by taking it out of the enclosure.
It showed up in my BIOS, but didn't allow me to create a partition for windows (it said there was no harddrive registered). It showed up for once and as I was installing windows, the computer bluescreened and had an error code with a bunch of 0's and 124 at the end. I took out the SDD and installed windows on my regular HDD and now the computer won't boot at all
I'm currently running a diskcheck on the HDD since every google page that I saw had windows 7 freezing on the startup page, it's usually a harddrive error.
I have this sinking feeling it's my CPU or GPU, but I have no idea tbh. I read it could also be the SATA cables, so I'm going to try out different cables and reformat all my drives before trying to reinstall windows again...
these art the parts
http://pcpartpicker.com/user/JonTalbain/saved/2mcX
did it ever boot properly? check vid card/mobo for warning lights. does it fail to post? if it fails are there any components that maybe dont have their fans turn on or somethinhg?
did it ever boot properly? check vid card/mobo for warning lights. does it fail to post? if it fails are there any components that maybe dont have their fans turn on or somethinhg?
i didnt see you explicitly say that you formatted both drives properly at the beginning
otherwise craig is spot on
i didnt see you explicitly say that you formatted both drives properly at the beginning
otherwise craig is spot on
my mobo doesn't have any warning lights light up
it did at the beginning because i didn't secure my RAM in place
also i couldn't format my ssd because it wouldn't display in the windows installer, unless there's a different way to format it before installing the OS
also i have no idea if my cpu is supposed to be idling at 40-45 celcius
my mobo doesn't have any warning lights light up
it did at the beginning because i didn't secure my RAM in place
also i couldn't format my ssd because it wouldn't display in the windows installer, unless there's a different way to format it before installing the OS
also i have no idea if my cpu is supposed to be idling at 40-45 celcius
1) Make sure everything is plugged in, and correctly (I've forgotten a PCI-e power connector once)
2) Check what's missing in BIOS, and see if you need to flash a newer BIOS because of any errors. Here's the BIOS page, though you should avoid this for now. It's a last resort if everything should be fine.
3) If you can, try putting stuff into an older mobo if it supports it (RAM/GPU/etc). If it works, chances are it's your setup.
For the SSD, swap cables, try different ports, and maybe do the BIOS update.
40-45 C is fine for idling.
1) Make sure everything is plugged in, and correctly (I've forgotten a PCI-e power connector once)
2) Check what's missing in BIOS, and see if you need to flash a newer BIOS because of any errors. [url=https://www.asus.com/Motherboards/SABERTOOTH_Z87/#support]Here's the BIOS page[/url], though you should avoid this for now. It's a last resort if everything should be fine.
3) If you can, try putting stuff into an older mobo if it supports it (RAM/GPU/etc). If it works, chances are it's your setup.
For the SSD, swap cables, try different ports, and maybe do the BIOS update.
40-45 C is fine for idling.
so i went to a computer tech guy to help me get a second opinion
the error code i get for my blue screens are 124, which signifies a hardware problem
i flashed my BIOS and still got the blue screens during idle (just booting windows and not touching anything)
i ran memtest all night yesterday with no problems
the computer instantly crashed whenever i ran the benchmarking setting for uniengine's valley software, so i thought it was the gpu and grabbed the latest nvidia drivers, and it still crashed
so i swapped out the card with an old hd 5870 after removing the nvidia drivers, and after installing the ati drivers, it still instantly blue screened during the benchmarking
the IT dude went to go check if he has a spare processor to test if it's the processor, but at this point i think it might be my motherboard
idk what would cause a computer to crash during the initial windows install and crashes on idle
so i went to a computer tech guy to help me get a second opinion
the error code i get for my blue screens are 124, which signifies a hardware problem
i flashed my BIOS and still got the blue screens during idle (just booting windows and not touching anything)
i ran memtest all night yesterday with no problems
the computer instantly crashed whenever i ran the benchmarking setting for uniengine's valley software, so i thought it was the gpu and grabbed the latest nvidia drivers, and it still crashed
so i swapped out the card with an old hd 5870 after removing the nvidia drivers, and after installing the ati drivers, it still instantly blue screened during the benchmarking
the IT dude went to go check if he has a spare processor to test if it's the processor, but at this point i think it might be my motherboard
idk what would cause a computer to crash during the initial windows install and crashes on idle
at this point it could be the motherboard, cpu or power supply.
i've seen people bring in those corsair plats to RMA citing similar issues. try a known working psu that is haswell compatible.
make sure your sata controller is in AHCI mode too when installing windows (but u already gotten past that point).
grab hwmonitor (http://www.cpuid.com/softwares/hwmonitor.html) and run prime95 to load up the cpu, check the temperatures and voltages. the sabertooth series are enthiast grade motherboards and may have some settings done manually that you may need to tweak to get working (even with stock settings).
at this point it could be the motherboard, cpu or power supply.
i've seen people bring in those corsair plats to RMA citing similar issues. try a known working psu that is haswell compatible.
make sure your sata controller is in AHCI mode too when installing windows (but u already gotten past that point).
grab hwmonitor (http://www.cpuid.com/softwares/hwmonitor.html) and run prime95 to load up the cpu, check the temperatures and voltages. the sabertooth series are enthiast grade motherboards and may have some settings done manually that you may need to tweak to get working (even with stock settings).
Foxso i went to a computer tech guy to help me get a second opinion
the error code i get for my blue screens are 124, which signifies a hardware problem
i flashed my BIOS and still got the blue screens during idle (just booting windows and not touching anything)
i ran memtest all night yesterday with no problems
the computer instantly crashed whenever i ran the benchmarking setting for uniengine's valley software, so i thought it was the gpu and grabbed the latest nvidia drivers, and it still crashed
so i swapped out the card with an old hd 5870 after removing the nvidia drivers, and after installing the ati drivers, it still instantly blue screened during the benchmarking
the IT dude went to go check if he has a spare processor to test if it's the processor, but at this point i think it might be my motherboard
idk what would cause a computer to crash during the initial windows install and crashes on idle
Edit- Nevermind, going to ask off here first
[quote=Fox]so i went to a computer tech guy to help me get a second opinion
the error code i get for my blue screens are 124, which signifies a hardware problem
i flashed my BIOS and still got the blue screens during idle (just booting windows and not touching anything)
i ran memtest all night yesterday with no problems
the computer instantly crashed whenever i ran the benchmarking setting for uniengine's valley software, so i thought it was the gpu and grabbed the latest nvidia drivers, and it still crashed
so i swapped out the card with an old hd 5870 after removing the nvidia drivers, and after installing the ati drivers, it still instantly blue screened during the benchmarking
the IT dude went to go check if he has a spare processor to test if it's the processor, but at this point i think it might be my motherboard
idk what would cause a computer to crash during the initial windows install and crashes on idle[/quote]
Edit- Nevermind, going to ask off here first
so the tech guy that came over has been entirely useless
i think i'm just going to try send back my psu/cpu/mobo since they all came from the same source and i can't test any of it
so the tech guy that came over has been entirely useless
i think i'm just going to try send back my psu/cpu/mobo since they all came from the same source and i can't test any of it
Oh man I feel bad for you, All 4 PC builds I've done have all been DOA/problem free with the exception of buying a psu that was missing a sata cable, which I just ordered online.
Oh man I feel bad for you, All 4 PC builds I've done have all been DOA/problem free with the exception of buying a psu that was missing a sata cable, which I just ordered online.