I dont know what to do anymore

[AlphaJaegerX]

First of my specs are i5 6600k with a msi z170 G45-gaming motherboard with a gtx 1070 (removed from motherboard) with 16 gigs of ram.

My computer abosolutly will not start, it is a half a year old custom computer I built and it was running just fine. Now I cant get out of BIOS because of one of many blue screen errors, half the time I cant see the errors because the screen looks corrupted itself. I really need help, please.

I've plugged my boot drive into another computer and it booted up just fine, so I don't think its my ssd, I removed my graphics card, I didnt have any extra ddr4 ram laying around so I tried reconfiguring my ram and reseating it, it wont let me use the install disc because I get a blue screen when I try and load it up. ive unplugged things from my power supply to see if that would help but no, the automatic repair sometimes shows up but ends up spinning for a whole day with nothing accomplished, but BIOS starts just fine I can get into BIOS and view anything there, but if I go anywhere past BIOS to do anything, it says no.

I hope this give even a clue to try and fix it.

 

[Colif]

what are some of the errors you are getting? Any like Whea errors or Clock watchdog timeout?

try making this on another PC: http://www.howtogeek.com/howto/windows-vista/use-ubuntu-live-cd-to-backup-files-from-your-dead-windows-computer/ and see if PC works in linux - this will reduce odds of it being hardware and just windows instead

why not put hdd into another PC and wipe windows off it to remove any chance its the reason it won't install.

I assume its not overclocked?

 

[AlphaJaegerX]

what are some of the errors you are getting? Any like Whea errors or Clock watchdog timeout?

try making this on another PC: http://www.howtogeek.com/howto/windows-vista/use-ubuntu-live-cd-to-backup-files-from-your-dead-windows-computer/ and see if PC works in linux - this will reduce odds of it being hardware and just windows instead

why not put hdd into another PC and wipe windows off it to remove any chance its the reason it won't install.

I assume its not overclocked?

It was overclock before, but i ran it on prime 95 for a couple of hours and it was completely fine. As for errors i've gotten a bunch of them, Machince check exeption, Watch dog timeout, Kernal security check failure, crypto library internal failure. Those are the ones i can think of off the top of my head, I'm not sure if there is any more than that though.

 

[Colif]

MCE & Watchdog timeout are both CPU errors. I have never seen Crypto Library internal failure before?

I have only seen this once, it'seems not common but it's the cpu. Usually when voltage is unstable and the motherboard and ram are the culprit.

http://www.tomshardware.com/answers/id-3055167/crypto-library-internal-error-bsod.html

Try making this on another PC and run it on yours - http://www.tcsscreening.com/files/users/IPDT_LiveUSB/index.html
try running memtest86 on your ram, 1 stick at a time. Any errors are too many. LIke the link above, this also creates a bootable USB so don't need windows

What power supply do you have?

 

[AlphaJaegerX]

MCE & Watchdog timeout are both CPU errors. I have never seen Crypto Library internal failure before?

I have only seen this once, it'seems not common but it's the cpu. Usually when voltage is unstable and the motherboard and ram are the culprit.

http://www.tomshardware.com/answers/id-3055167/crypto-library-internal-error-bsod.html

Try making this on another PC and run it on yours - http://www.tcsscreening.com/files/users/IPDT_LiveUSB/index.html
try running memtest86 on your ram, 1 stick at a time. Any errors are too many. LIke the link above, this also creates a bootable USB so don't need windows

What power supply do you have?

I have a EVGA 750 supernova NEX, and ill try these out. Also i am typing this off a laptop so its impossible to test parts on this computer unfortunately.

 

[Saga Lout]

Are you not seeing the StartUp Repair options when you power up the machine? If not, it's almost certainly not a Windows issue but nore likely, hardware.

If you create a USB stick of a Windows 10 ISO from Microsoft's site and use Rufus to make the drive bootable, then you get an option to Repair or Install. Select Repair and if it doesn't find anything wrong you know it's not software. Go for Command Prompt and at the prompt, type
SHUTDOWN /R /O -T 00
and hit the Enter key. When it comes up after restarting, invoke the system Admnistrator account to eliminate permissions issues. Run chdsk /r and sfc /scannow and see what happens.

The Linux suggestion above should get the hardware off the suspects list but sadly, not Windows drivers.

 

[AlphaJaegerX]

Are you not seeing the StartUp Repair options when you power up the machine? If not, it's almost certainly not a Windows issue but nore likely, hardware.

If you create a USB stick of a Windows 10 ISO from Microsoft's site and use Rufus to make the drive bootable, then you get an option to Repair or Install. Select Repair and if it doesn't find anything wrong you know it's not software. Go for Command Prompt and at the prompt, type
SHUTDOWN /R /O -T 00
and hit the Enter key. When it comes up after restarting, invoke the system Admnistrator account to eliminate permissions issues. Run chdsk /r and sfc /scannow and see what happens.

The Linux suggestion above should get the hardware off the suspects list but sadly, not Windows drivers.

I'll give it a go and let you guys know

 

[AlphaJaegerX]

Are you not seeing the StartUp Repair options when you power up the machine? If not, it's almost certainly not a Windows issue but nore likely, hardware.

If you create a USB stick of a Windows 10 ISO from Microsoft's site and use Rufus to make the drive bootable, then you get an option to Repair or Install. Select Repair and if it doesn't find anything wrong you know it's not software. Go for Command Prompt and at the prompt, type
SHUTDOWN /R /O -T 00
and hit the Enter key. When it comes up after restarting, invoke the system Admnistrator account to eliminate permissions issues. Run chdsk /r and sfc /scannow and see what happens.

The Linux suggestion above should get the hardware off the suspects list but sadly, not Windows drivers.

just an update from the last post. I've copied an iso file and put on a flash drive using rufus and the first time i tried it booted to a blue screen with an error machine check error. but then the second time using the ssd. it booted up and the automatic repair poped up and it's running a diagnostics on my memory. Its a start, thank you all for giving me these helpful advice

It finished doing the diagnostics and it tried booting and gave the error
kmode exception not handled" and "System service exception" also "system PTE misuse" And tons others. This is definitely hardware Malfunction

 

[Colif]

IF you manage to get into windows, I would run https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool - I have already given you a link to the linux version as I assumed you wouldn't get into windows

the crypto library internal error is so rare that the only mentions I have found all mention the CPU, though description above mentions ram and motherboard so its why I suggested memtest86 as well.

https://www.reddit.com/r/techsupport/comments/5162fk/windows_10_crypto_library_internal_error_bsod/
https://answers.microsoft.com/fr-fr/windows/forum/windows_10-performance/help-crypto-library-internal-errorfreeze-au/09a72595-983a-4faa-aa59-2ce7601788d3 (in french)

 

[Colif]

It finished doing the diagnostics and it tried booting and gave the error
kmode exception not handled" and "System service exception" also "system PTE misuse" And tons others. This is definitely hardware Malfunction

these can all be driver errors as well

System service exception
System PTE Misuse
Kmode exception not handled

but MCE and the others are showing signs of hardware.

its odd it gives an MCE off the USB

if windows can't boot cause it gets other errors, it will eventually break the install as it will corrupt it from all the restarts. Once you fix the hardware problems, you probably need to reinstall win 10 again.

 

[AlphaJaegerX]

It finished doing the diagnostics and it tried booting and gave the error
kmode exception not handled" and "System service exception" also "system PTE misuse" And tons others. This is definitely hardware Malfunction

these can all be driver errors as well

System service exception
System PTE Misuse
Kmode exception not handled

but MCE and the others are showing signs of hardware.

its odd it gives an MCE off the USB

if windows can't boot cause it gets other errors, it will eventually break the install as it will corrupt it from all the restarts. Once you fix the hardware problems, you probably need to reinstall win 10 again.

Probably, i wish i knew which part i need to replace. i think i am just going to need a motherboard, ram, and cpu, unfortunetly. RIP my pc

 

[Saga Lout]

I trust you have disconnected everything except basic KVM; keyboard, video and mouse. Anything else is getting in the way.

 

[Colif]

at the moment, i would narrow that down to CPU as 3 of the errors you mentioned are CPU errors. especially that crypto error as if I search for it google seems to link it to WHEA which is Windows Hardware Error Architecture, another name for MCE. MCE & WHEA are pretty much the same thing.

I would contact Intel and arrange an RMA, I would hold off on the other two.

Or you can take to a shop and get a professional opinion - much saner than swapping out parts that might be fine.

 

[AlphaJaegerX]

I trust you have disconnected everything ecept basic KVM; keyboard, video and mouse. Anything else is getting in the way.

Yes i very much did pull every cable off that wasn't needed, i suspect cpu and motherboard sadly.

 

[AlphaJaegerX]

at the moment, i would narrow that down to CPU as 3 of the errors you mentioned are CPU errors. especially that crypto error as if I search for it google seems to link it to WHEA which is Windows Hardware Error Architecture, another name for MCE. MCE & WHEA are pretty much the same thing.

I would contact Intel and arrange an RMA, I would hold off on the other two.

Or you can take to a shop and get a professional opinion - much saner than swapping out parts that might be fine.

I agree, i probably will get another opinion and another from a professional before i do anything. Thank you all, sadly my pc isn't starting anytime soon🙁

 

[Saga Lout]

You may be right but I wouldn't condemn either until I'd pulled it out of the case and found it behaved just as badly sitting on a piece of cardboard.

 

[AlphaJaegerX]

You may be right but I wouldn't condemn either until I'd pulled it out of the case and found it behaved just as badly sitting on a piece of cardboard.

you mean pull everything out of the case and attempt to boot it on carboard?

 

[Karadjgne]

Have you reset the bios to factory default, or when coming off that OC did you just downclock the multiplier? From what I see, it's an actual voltage issue from the cpu. Entering bios is entirely cpu independent, you aren't using the cpu yet at all other than for recognition. You don't start using the cpu until leaving bios, that's when cmos starts organizing drivers to begin OS workup. This is where I'm thinking your error is coming from, something leftover from the OC. Apart from resetting bios to default (don't forget to save on exit), I'd also pull the power cord, pull the cmos battery, hold down the power button for 20 seconds to drain all the power capacitors, replace (a new battery would be better) the cmos battery and reboot. This'll invalidate any prior timestamps and force a clean full bios/cmos boot. I'd also do all that breadboarded, no drives at least installed, no mouse, no kb, no gpu. Just monitor. Hopefully, you'll get past cmos and get to C prompt asking for an OS drive.

 

[Karadjgne]

A case is just a box to hold all the components together. Unnecessary to pc operation. It's called breadboarding. Psu, mobo, cpu, cooler+fan, 1 stick of ram, system speaker. All you need. If you get a single bleep, your pc just made it past POST and is waiting for OS. No bleep, swap ram stick, try again. Still no bleep then either cpu or mobo failed. Generally it's the motherboard, cpus that aren't driven excessively past thermal limits are very, very hard to kill, the motherboard (especially the VRM's/mosfets) will fail long before the cpu gets roasted.

 

[Saga Lout]

You may be right but I wouldn't condemn either until I'd pulled it out of the case and found it behaved just as badly sitting on a piece of cardboard.

you mean pull everything out of the case and attempt to boot it on carboard?

If I had a pound for every time I've assembled a new build on the bench or some cardboard and it worked first time then failed once it's in the case, I'd be quite well off.

 

[Karadjgne]

Yep. Many cases come with painted motherboard offset screws already installed and ppl forget or don't think about them and install a different board, that ends up grounding out the mobo. It's also possible that some mobo's shouldn't have passed QC, and have long solder tips on the back of the board that touch the case. Or, some cases, the tray behind the mobo gets warped with handling and touches the back of the mobo.

Pulling out the mobo and breadboarding us a good time to check both the mobo and the case tray for any scorch or scratches or long tips.

 

[AlphaJaegerX]

The Problem was a Faulty motherboard, nothing else i could have done program wise. Thank you for all of the help and i hope nobody else has the same problems as i did.