Windows will no longer start after many Blue Screen errors, Impossible to reinstall due to possible Corruption

[durrgh]

Hello, recently I ordered the following build:

Intel - Core i7-8700K 3.7GHz 6-Core Processor
be quiet! - Dark Rock Pro 4 50.5 CFM CPU Cooler
MSI - Z370 KRAIT GAMING ATX LGA1151 Motherboard
Team - Vulcan 16GB (4 x 8GB) DDR4-3000 Memory
Samsung - 850 EVO-Series 1TB 2.5" Solid State Drive
Hitachi - Ultrastar 7K3000 3TB 3.5" 7200RPM Internal Hard Drive
Asus - PCE-AC68 PCI-Express x1 802.11a/b/g/n/ac Wi-Fi Adapter
+ Western Digital 1TB Hard Drive from Old PC
with Windows 10 Home OEM 64-Bit.

I installed Windows seemingly without any problems, the PC ran perfectly for a few days (with one broken usb port in the front that I was willing to overlook) as I used photoshop and played several games on there. However, yesterday it began giving me BSODs for seemingly no reason, usually saying "PAGE_FAULT_IN_NONPAGED_AREA," so I ran a bunch of tests to find problems with the memory and hard drives and couldn't find anything wrong. Then I attempted to delete some software and download some drivers in order to fix the problem.

None of it seemed to work however, and this morning I got the same blue screen with the additional message "What failed: FLTMGR.sys". Now Windows won't start at all, and a screen comes up on launch telling me I need to use recovery tools to repair my PC, so I try to use the USB I originally used to install windows to reinstall it. But now it says "The file is possibly corrupt. The file header checksum does not match the computed checksum." All I can do now is access the BIOS from the boot menu.

I tried clearing the SSD I used to launch windows, thinking the data on there may have been corrupt somehow, but nothing changed. How should I proceed?

 

[Colif]

did you run memtest on the ram? was that one of the tests?

the errors could all be drivers, page faults generally are.

FLTMGR is often a file associated with memory management errors. Microsoft Filesystem Filter Manager ensures all files installed on the user PC are stored in their respective directories. Something is corrupting your info so testing ram/hdd made sense.

Are you able to boot off the USB? I am not there but it could be if secure boot is still enabled, its still trying to boot off SSD. The checksum error has been known to appear on bad installs, not found it associated to the USB itself. It doesn't make sense that an installer that worked one time gives an error the next. None of the files on USB should have changed

So did you manage to wipe ssd? what did you try to use to do it?

Try unplugging both hdd, just so if we do install win 10 again, windows doesn't put its boot partition on the other drives, if they have any spare space, it will.

 

[durrgh]

did you run memtest on the ram? was that one of the tests?

the errors could all be drivers, page faults generally are.

FLTMGR is often a file associated with memory management errors. Microsoft Filesystem Filter Manager ensures all files installed on the user PC are stored in their respective directories. Something is corrupting your info so testing ram/hdd made sense.

Are you able to boot off the USB? I am not there but it could be if secure boot is still enabled, its still trying to boot off SSD. The checksum error has been known to appear on bad installs, not found it associated to the USB itself. It doesn't make sense that an installer that worked one time gives an error the next. None of the files on USB should have changed

So did you manage to wipe ssd? what did you try to use to do it?

Try unplugging both hdd, just so if we do install win 10 again, windows doesn't put its boot partition on the other drives, if they have any spare space, it will.

I ran memtest, no problems there. I wiped the SSD using the Secure Erase+ option on the BIOS menu. Trying to boot the windows iso from the USB gives me an error saying "The digital signature for this file couldn't be verified." with error code 0xc0000428. I might try using a new USB stick to try to install windows when I can get a hold of one. I did format the USB after installing windows the first time so I could use it to transfer drivers over to the new PC when it didnt have internet yet, so I'm not sure if it could have gotten corrupted along the way somehow.

 

[Colif]

i am helping someone else who has error 428, its not an error I have seen before this week and I see a lot of them (errors I mean). In his case he managed to boot up with just 1 ram stick in, so perhaps try that?

here is link to that other post, but I have yet to figure out a solution - http://www.tomshardware.com/forum/id-3760650/crash-error-code-0xc0000428-turns-seconds.html

is the ram on boards compatibility chart?

There are 2 common reasons or causes for the 0xc0000428 error. One of the main reason is the system file in the Windows kernel has been corrupted or modified by third party applications, which can possibly by virus too. To resolve the the problem of this nature, insert the Windows Vista installation DVD into DVD-ROM disc tray, and then boot up the computer from DVD drive. Select the Startup Repair option to have the Recovery Environment automatically scans and replaces corrupted or invalid system files.

Another possible cause for Windows failed to boot with 0xc0000428 error is hardware failure which corrupt, conflict or interfere with integrity of system files. The problematic and spoilt hardware can be RAM memory module, motherboard, chipset, CPU, display adapter and other components. User can use diagnostic tools to help identifying the possibly failing hardware part, such as Memory Diagnostic can be used to test the system’s memory. Once the problematic hardware component is isolated and identified, repair the error or replace the hardware component.

https://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/0xc0000428-or-0x428-cannot-verify-digital/e1d3a09a-5e62-4b87-8e56-0bc33ddbab33

 

[durrgh]

i am helping someone else who has error 428, its not an error I have seen before this week and I see a lot of them (errors I mean). In his case he managed to boot up with just 1 ram stick in, so perhaps try that?

here is link to that other post, but I have yet to figure out a solution - http://www.tomshardware.com/forum/id-3760650/crash-error-code-0xc0000428-turns-seconds.html

is the ram on boards compatibility chart?

There are 2 common reasons or causes for the 0xc0000428 error. One of the main reason is the system file in the Windows kernel has been corrupted or modified by third party applications, which can possibly by virus too. To resolve the the problem of this nature, insert the Windows Vista installation DVD into DVD-ROM disc tray, and then boot up the computer from DVD drive. Select the Startup Repair option to have the Recovery Environment automatically scans and replaces corrupted or invalid system files.

Another possible cause for Windows failed to boot with 0xc0000428 error is hardware failure which corrupt, conflict or interfere with integrity of system files. The problematic and spoilt hardware can be RAM memory module, motherboard, chipset, CPU, display adapter and other components. User can use diagnostic tools to help identifying the possibly failing hardware part, such as Memory Diagnostic can be used to test the system’s memory. Once the problematic hardware component is isolated and identified, repair the error or replace the hardware component.

https://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/0xc0000428-or-0x428-cannot-verify-digital/e1d3a09a-5e62-4b87-8e56-0bc33ddbab33

The ram should be compatible, at least according to PCpartpicker.com, so I don't think that's the issue. I'm trying to figure out what changed to make the machine run perfectly for the first few days and then suddenly begin blue screening. The only real change I can think of that happened around that time was me plugging the asus monitor's audio jack into the PC, although I'm not sure if that would normally pose any issues.

8/17/18 Update: After getting frustrated with the computer and finding no solution after messing around with it for a while, I took it to a local repair shop and had them take a look at it. They reinstalled windows and still had the same problems, but after messing around with it for a while they seem to have noticed there are no problems while the ASUS wifi network card is disconnected. It seems like that's the culprit right now, although I'm not sure if it's a result of faulty hardware or a compatibility issue.