Windows 10: Hello, I am having a dual system on a drive and I am having multiple major problems...

I have a NTFS disk 1 SSD that I am able to boot to after doing the following:

1. after pressing on the power the dell logo goes "on" ie, i gotten a POST and all and I have to F12 my way to manually select "UEFI Drive Partition 1 OS..." where my win10 SSF is located every time. Boot to any other location it doesn't work. other locations like CD/DVD Drive or USB or Internal HDD etc..

2. After i boot to that partition I get into automatic maintenance and you will waste your time if you will wait to confirm all hardware is working. You have to shut down.

3. Then you power on, you post, you press F12 and select UEFI Partition.... and you wait. The automatic maintenance goes on so you power off again.

4. Then you power on, you post, you press F12 and select UEFI Partition.... and you wait. The windows logo shows up and you have a successful boot. From there I can normally use windows 10.

The problem that I am facing is that for a very long time my drive became corrupted or maybe just errored, because I cannot boot to the older OS. When I use the system I get randomlydriver page pool faults to other BSOD's that look related to each other, or so i feel. But that old OS is not important as I can just transfer and access my drives normally when I boot in win10. In fact it would have been better to delete it...


However the problem still prevails: What causes my BSOD's? I am going to share the minidumps that I have. If i could have somehow been able to understand the "parameter1" "...2" "..3 and "parameter4" I might have been able to maybe understand what was causing it.


Currently I have uninstalled updated drivers and have all of my drivers in their old versions. I did update my dell bios lately but that is not the cause of the problem it started way before like a few months ago.


Information:

Laptop - Dell Inspiron 15

Windows 10 Home 1909 ; OS Build 18363.1171

Dump FileCrash TimeBug Check StringBug Check CodeParameter 1Parameter 2Parameter 3Parameter 4Caused By DriverCaused By AddressFile DescriptionProduct NameCompanyFile VersionCrash AddressFull PathMajor VersionMinor VersionDump File SizeDump File Time
103120-27000-01.dmp2020/10/31 14:21:01DRIVER_VERIFIER_DETECTED_VIOLATION0x000000c400000000`0000013effffa184`68386f004d82506d`ffffa184ffffa184`8b2fb3e4ntoskrnl.exentoskrnl.exe+1c3b20NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation10.0.18362.1171 WinBuild.160101.0800ntoskrnl.exe+1c3b20C:\Windows\Minidump\103120-27000-01.dmp1518362898,8842020/10/31 15:57:08
103120-27281-01.dmp2020/10/31 10:37:28DRIVER_VERIFIER_DETECTED_VIOLATION0x000000c400000000`0000013effffbd8a`f1c7ef005878106d`ffffbd8affffbd8a`52933ba4ntoskrnl.exentoskrnl.exe+1c3b20NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation10.0.18362.1171 WinBuild.160101.0800ntoskrnl.exe+1c3b20C:\Windows\Minidump\103120-27281-01.dmp1518362907,6922020/10/31 12:15:57
103020-18140-01.dmp2020/10/30 20:06:12SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION0x000000c1ffffbd8f`a7e54ff400000000`0000000800000000`0000000c00000000`00000021ntoskrnl.exentoskrnl.exe+1c3b20NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation10.0.18362.1171 WinBuild.160101.0800ntoskrnl.exe+1c3b20C:\Windows\Minidump\103020-18140-01.dmp15183622,479,1572020/10/30 20:11:06
103020-17281-01.dmp2020/10/30 1:37:58DRIVER_VERIFIER_DETECTED_VIOLATION0x000000c400000000`00000062ffffc184`efdccfd8ffffc184`ecc60ee000000000`00000001win32kfull.syswin32kfull.sys+0Full/Desktop Win32k Kernel DriverMicrosoft® Windows® Operating SystemMicrosoft Corporation10.0.18362.1171 WinBuild.160101.0800ntoskrnl.exe+1c3b20C:\Windows\Minidump\103020-17281-01.dmp1518362921,1002020/10/30 8:58:08
102920-10078-01.dmp2020/10/29 19:11:52SYSTEM_SERVICE_EXCEPTION0x0000003b00000000`c0000005fffff803`4307c99affffc80a`24f95fb000000000`00000000ntoskrnl.exentoskrnl.exe+1c3b20NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation10.0.18362.1171 WinBuild.160101.0800ntoskrnl.exe+1c3b20C:\Windows\Minidump\102920-10078-01.dmp15183621,639,0202020/10/29 19:15:37

the following were from BSOD viewer but I can send over the minidump files.

:)

 

Having issues with new SSD

This is a ongoing problem of installing Win 10 on a system with multiple drives. If you feel up to it, delete the partition, or erase as jboy suggests, the terabyte drive, and unplug it from your system then do a clean install of windows. After thats complete, you can reconnect the terabyte drive without issue.

 

Windows 10 1709 System Restore problems...

That seems to be an attempt at Option 2 in the tutorial, which requires you to
a. Boot to a command prompt (Did you?)
b. You then seem to be mixing steps 3,4 and 5, thus your command is incorrect.

I suggest Option 1 is easier.

If you still have problems, please repost listing each specific step and saying which option from the tutorial you are using. Thanks.

 

Antivirus companies that have made major mistakes....

Please list those as honest as you can. Please provide more then 5 reported news links per vendor to confirm. Please also indicate the problem in full.

Please make sure to also post your honest experience about the problem with the anti-virus software that you have if you have experienced this major problem..

Remember.... This must have been a widespread problem documented in the media.

Thank you and much appreciated.