Rotating Carousel of BSoD Errors

nasaldischarge

Prominent
Jan 25, 2018
7
0
510
Hello all, I will GREATLY appreciate any help you can provide because I am exhausted.

This all started with a Windows 10 update. Blue screen after blue screen I decided to go back to previous version. Windows wouldn't even boot. Downloaded a version of Windows 10 to an external and tried to reinstall. I carefully backed up essential files through command prompt first.

Once I tried to install from the external, it kept saying there were issues with the hard drive. Googled the issues and it led to a disk check of some sort that said the disk was failing.

I bought a new HDD and installed it. Did a full format from cmd and tried to install Windows but it'd fail for no apparent reason. I found a post somewhere online where someone claimed that Windows 10 freaks out if the clean hard drive is big, and that I should partition it.

I partitioned the HDD and Windows installed perfectly without issue. I expanded the partition and I thought the saga was finally over. Nope.

Windows now starts up, the only program I have installed is Chrome, and I get blue screen after blue screen still.

I get the following errors in a seemingly random rotation:
1. memory_management
2. kernel_security_check_failure
3. (didn't get the underscored name but it said): fltmgr.sys failed
4. something about a display driver issue but I think I managed to update that driver between blue screens

It should be noted that Windows 10 is not up to date. It says updates are needed but I get BSoDs before they can download and install.

Again, any help would be deeply appreciated. Thanks in advance.
 
Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)


have you checked motherboard web site for latest drivers? Almost all BSOD caused by drivers
 
You say you partitioned and it worked fine. What were the partition sizes? Can you boot in safe mode?
The kernel_security_check_failure usually indicates some sort of critical corruption of your system. The first one is curious though cause it points to memory issues. From your dump, also the parameter 1 would suggest a memory access violation (https://answers.microsoft.com/en-us/windows/forum/windows_7-system/stop-0x0000007e/946745f6-d891-427a-a22c-4cda76888615?auth=1)
So check if you can
1) boot in safe mode
2) check your memory, either getting windows to do it for you if you can boot up in safe mode or removing one of the two sticks and seeing if you have the same issue still, and trying different memory slots.
3) you said it worked fine with separate partitions. Try re-doing it that way and using one partition for system and the other for data. You might need to do this anyway if you can't boot into windows even in safe mode to check the memory in the first place.
 


It appeared to work fine after the partition. I partitioned 125Gb to get Windows to install. Once it installed I expanded the hard drive out to the full 2TB. I would have left it alone but I didn't know how to make the remaining 1.875TB a separately named drive. It wasn't showing up, just a 125GB C: drive.

I can boot just fine. I can boot into safe mode as well. The problem is these BSoDs come sooner or later. Also, Windows still won't update further no matter what I do.

You suggested I get Windows to check my memory for me, can you provide a reference for how to do that? I would like to avoid removing memory sticks if possible.
 
Er wait...was the remaining space not formatted? Was it an actual partition or just unallocated raw space? Cause I can imagine that causing major issues if you just expanded into it. Though it shouldn't have let you do that really if that was the case but maybe that's just wishful thinking on my part and it actually doesn't check that for you. How were you partitioning and expanding?
Ok here's how to do some checks. Go to Windows->Windows Administrative Tools (assuming you see list of apps when you click on windows icon)->Computer Management->Disk management
It should show 3 partitions, and one should say C:, be formatted NTFS, and the others are EFI system and Recovery Partition. All 3 should say Healthy. Check that it does. Incidentally when you right click on each, it should give you a menu with an option to assign it a drive letter, for future reference. If you right click on C: and go Properties->Tools->Check, let it do its thing and make sure it reports that everything is ok.
Next go Windows->Windows Administrative Tools->Windows Memory Diagnostic and let it run.
If no definitive answer, I'd try Memtest86 next, with at least 8 passes.

 


It only shows 1 in disk management. Here's a pic:
j3jSER

(Image isn't showing so here is link) https://ibb.co/j3jSER

Oh, and yes I did a full format before partitioning/installing.
 
Oh...that's not good. That's not what a windows 10 is supposed to look like. Should look like this:

It automatically creates the two other partitions. I frankly don't quite understand how it can do safe mode without an efi partition. I'm not sure what to tell you other than to completely scrub and reinstall but then, I'm not sure how it's running at all at the moment. Do you see in disk management on the bottom, the totality of your 1TB apportioned to your C? Or is there unallocated space? Did you run a disk check?
 


Yes the full 2TB is there (or, 1,865GB or so.) I appreciate the help by the way.

When I booted up the first time, and discovered my C: drive was 125GB, I believe I went to the disk management page, and it looked exactly the same as it does now, except it was only 125GB. I right-clicked and hit extend if I recall correctly, and that's where I am now.

Can I somehow construct it the way it should be? If I shrink the volume and make it the system partition, then make a recovery, etc. I've really never done any of this so I'm just throwing ideas out there. I'm worried about starting over and ending up with the same result.
 
Here's the thing. Maybe with system repair it might do it for you from the windows cd but...I suspect the data is there else windows wouldn't boot but...either not partitioned or the partitions aren't correctly registering. So I'm not certain what scannow repair would actually do. Create new partitions and duplicate the info? I don't know...
Run the disk check. It'll be the first thing to pick up if something is not registering correctly and it'll auto repair it if it finds something wrong.
http://www.thewindowsclub.com/disk-error-checking-windows-8
When you were installing with windows 10 cd, did it not list partitions/space, give you the option to set the format to NTFS? This is where the other two automatically created partitions should have shown up once you created and partition and formatted it, long before windows actually booted up post install. During install it should have shown full 2TB. The window would have looked something like this:
https://www.tenforums.com/attachments/tutorials/23420d1436124824-clean-install-windows-10-a-uefi.jpg
 


Disk check said no errors found.

When I was installing windows, if I remember correctly, it showed the automatically created partitions but the windows install kept failing. I think I then cleaned the disk attempting to start fresh and created the 125 gb partition which ended up working. Maybe this is where I made the error? I can't recall specifically if from that point it showed multiple partitions when I selected the 125gb partition for install. I feel like they were there but I can't say for sure.

I'm worried that maybe expanding the partition was not the right thing to do, or not done correctly, but at that point there were no other drives shown.

Thanks again.
 
Ok well before nuclear option, try this:
https://www.tenforums.com/tutorials/2895-run-sfc-command-windows-10-a.html
with understanding that in your case your boot and system files are probably on the same drive as you're missing your partitions somehow.
The boot command prompt you get by inserting usb key with windows 10 install, rebooting into it and then choosing troubleshooting, advanced and command prompt.
 
Solution