Windows 10: Multiple BSODs, now can't load Windows

Hey guys! I'm really hoping you can solve a problem that I've spent the past 16 hours wrestling with. This morning my PC hard crashed,. I didn't think anything of it, restarted and got back to work. About an hour later it hard crashed again, eventually BSODing within minutes of logging in. These are just some of the errors:
IRQL null less or equal
System Service Exception
Bad Pool Header
Kmove exception not handled
And a few others. I could never stay on long enough to google these errors so I ran CHKDSK from the advanced boot screen which came back fine. I decided "screw it" and just did a System Restore since my last point was a few days ago. Then it BSOD during the system restore, and it made it so that it would crash after the Windows logo. I decided to use the Reset to reinstall Windows 10 but keep my files, and, you guessed it! BSOD during that. Now it doesn't even ask for my password in the advanced boot screen like it used to. If I try to do the Reset again it gives me an error and says it can't be done.
If I power on, there's a 90% chance it either hard crashes or BSOD at the Windows logo. On the off-chance that it makes it beyond that, it runs a repair tool, but it always fails.
I made a Windows 10 USB installer but it just prompts for a serial key which I don't have because I used the automatic upgrade from Windows 8.1 a few weeks ago.
I spent hours searching for answers, and even resorted to making a USB Linux installer just to access my HDD and transfer some important files to an external HDD, but I couldn't grab them all. For some reason some of my folders were inaccessible.

I'm really hoping you guys can solve this for me because it's 5:20am and my brain has turned to mush. And, if possible being able to recover those last few files I'm missing.

If you need any more info from me, just ask, for now, I'm going to grab a couple hours sleep. Good luck!

:)

 

Constant BSOD Loop (Never-Ending)

The Windows Operating System (along with the Blue Screen of Death) is constantly loading, which means that I can't turn it off. (normally at least). It has been churning for 18 hours now, with the BSOD having loaded some 20+ times.

 

problem with loading Windows 10 after using driver vertfier

I ran a driver verifier and now Windows 10 will not load up and getting BSOD message SCSIPORT.SYS HELP PLEASE!!!!

 

Diagnostics Test

HDD & SSD TEST


Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums



Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk Disk Check - Windows 7 Help Forums

 

I'm not sure what exactly has happened since my last post, but now I can't even access the advanced boot screen to run CHKDSK. It now immediately BSODs after the BIOS, or gives me various error info and asks me to use a recovery tool.

If I change the boot device to the USB where I have Linux, (I have no experience with Linux,) I can still access the majority of my files, so they seem to be in good working order.

 

You are posting via another pc?

 

Yes. A borrowed laptop. Sorry for the confusion.

 

That is a good thing *Smile
Is Windows 10 installed on it?

 

Use the link below for creating recovery media, it is needed to proceed.

Recovery Drive - Create in Windows 10 - Windows 10 Forums

 

OK, I've made the Recovery Drive, but I had to uncheck the Back up system files to the recovery drive box. Otherwise it would say there was a problem. Is that going to be an issue?
How should I proceed from here?

 

Boot from the USB, go to the advanced troubleshooting options and open command prompt.
In command prompt enter the chkdsk command and wait until it is finished.


Note It may take hours until chkdsk completes, let it run until it is finished.


Warning Aborting the test may cause (more) damage to your hard drive

 

Chkdsk ended after about a minute saying:
Errors found. CHKDSK cannot continue in read-only mode

The full scan says:
Code: Stage 1: Examining basic file system structure... 446720 file records processed. File verification completed. 33405 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage... Errors detected in encrypted file record segment 265947. Errors detected in reparse point file record segment 265947. An invalid filename x86_microsoft-windows-i...ntrolpanel-option8l_3dbf3e56a1364.35_41.0 (269051) was found in directory 45336. Minor file name errors were detected in file 269051. Index entry x86_microsoft-windows-i...ntrolpanel-optional_31bf3856ad364e35_11.0.10240.16384_none_5d536d65249bd25d.manifest in index $I30 of file 45336 is incorrect. Progress: 471109 of 562458 done; Stage: 83%; Total: 77%; ETA: 0:00:19... 562458 index entries processed. Index verification complete. Errors found. CHKDSK cannot continue in read-only mode. Failed to transfer logged messages to the event log with status 50.[/quote]
For reference, I ran CHKDSK before I tried to Reset my PC and it did the hour-long scan and everything came back fine. Clearly something has changed.
Hopefully you can make more sense of this than I can.

 

You'll need to get back in Windows, in any way, in a chance to fix the errors chkdsk has found.
Are you able to boot in safe mode?
If you don't know, try it as followIn command prompt enter the command
Code: start msconfig[/quote] In msconfig, go to the boot tab, click the box of safe mode, click apply > ok and reboot.

 

I get the error:
Windows cannot find 'msconfig'.

 

Try running SeaTools for DOS
SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums