virge Posted April 8, 2017 Share Posted April 8, 2017 Has anyone seen this Windows 10 Redstone 2 boot up error message after doing a clean install and all the updates, it doesn't occur right away, usually a few days later PC was able to reboot many times before this message. Checked the drive for errors, was none and no hardware issues or changes. ,,,,,,,,,,,,,, then the "Your pc ran into a problem and needs to restart BSOD" bootup crash message. Windows repair won't fix it, nor did any of the 3rd party tools. Looked online and there doesn't seem to be a fix. Just as a side note, this pc ran LTSB for many months without ever seeing this message, only occurred on RS2 Anyone have any suggestions? Link to comment Share on other sites More sharing options...
sam3971 Posted April 8, 2017 Share Posted April 8, 2017 Can you get into windows via safemode or BSOD there as well? Usually when you see such errors it is usually caused by a program that does pre-boot operations like a disk defragment tool or some security vendors. Sometimes when they are removed, windows still retains the registry setting to look for the module, says it cannot be found and proceeds to boot. Now because it is a BSOD, did you notate the error code and file involved if applicable? This small tidbit of information can be really helpful at diag if you have another internet equipped device available. Best of luck, may have to just reinstall Win though. Link to comment Share on other sites More sharing options...
virge Posted April 8, 2017 Author Share Posted April 8, 2017 1 minute ago, sam3971 said: Can you get into windows via safemode or BSOD there as well? Usually when you see such errors it is usually caused by a program that does pre-boot operations like a disk defragment tool or some security vendors. Sometimes when they are removed, windows still retains the registry setting to look for the module, says it cannot be found and proceeds to boot. Now because it is a BSOD, did you notate the error code and file involved if applicable? This small tidbit of information can be really helpful at diag if you have another internet equipped device available. Best of luck, may have to just reinstall Win though. Tried all 9 of the Windows 10 safe mode startup settings/option, the same message. BSOD message was: Stop code 0xc000021a. Link to comment Share on other sites More sharing options...
sam3971 Posted April 8, 2017 Share Posted April 8, 2017 1 hour ago, virge said: Tried all 9 of the Windows 10 safe mode startup settings/option, the same message. BSOD message was: Stop code 0xc000021a. Hi Virge, Did the BSOD mention anything about "IRQ_NOT_LESS_EQUAL"? If it did, it could be a hardware issue or a windows derp. For all your hardware to work property, they have to be on their own IRQ channel. Sometimes 2 devices will try to use the same channel and windows throws a fit. On a side note, see if the trouble shooter that is built into recovery can do anything, could just be a bad update or something similar. https://www.techjunkie.com/0xc000021a-windows-8-10/ Link to comment Share on other sites More sharing options...
funkyy Posted April 8, 2017 Share Posted April 8, 2017 @virge...I have been using Win XP for a few years and about a year ago I started getting a similar message when booting. I don't get a BSOD though..it just shows the message and continues to boot normally. I tried to find out via Google about this but I could never get an explanation. Anyway, until now everything boots and runs smoothly on my computer. Link to comment Share on other sites More sharing options...
virge Posted April 9, 2017 Author Share Posted April 9, 2017 12 hours ago, sam3971 said: Hi Virge, Did the BSOD mention anything about "IRQ_NOT_LESS_EQUAL"? If it did, it could be a hardware issue or a windows derp. For all your hardware to work property, they have to be on their own IRQ channel. Sometimes 2 devices will try to use the same channel and windows throws a fit. On a side note, see if the trouble shooter that is built into recovery can do anything, could just be a bad update or something similar. https://www.techjunkie.com/0xc000021a-windows-8-10/ Nope, here is the exact message: Autochk program not found - skipping AUTOCHECK Your pc ran into a problem and needs to restart Stop code 0xc000021a. No message about IRQ. Microsoft emailed me back saying the hard drive was damaged and to replace it, lol... oh well, hopefully, it won't occur again, did another clean install. Link to comment Share on other sites More sharing options...
sam3971 Posted April 9, 2017 Share Posted April 9, 2017 10 minutes ago, virge said: Nope, here is the exact message: Autochk program not found - skipping AUTOCHECK Your pc ran into a problem and needs to restart Stop code 0xc000021a. No message about IRQ. Microsoft emailed me back saying the hard drive was damaged and to replace it, lol... oh well, hopefully, it won't occur again, did another clean install. How old is the HDD? It could be a physical issue like M$ is claiming but could just need a good wiping. I have never seen an OS fail to install due to a failing drive other then what seems like a forever install. Usually it will boot but be slow. Again, this is determined by the physical status of the drive and how far gone it really is. Link to comment Share on other sites More sharing options...
virge Posted April 9, 2017 Author Share Posted April 9, 2017 4 minutes ago, sam3971 said: How old is the HDD? It could be a physical issue like M$ is claiming but could just need a good wiping. I have never seen an OS fail to install due to a failing drive other then what seems like a forever install. Usually it will boot but be slow. Again, this is determined by the physical status of the drive and how far gone it really is. System specs if that helps: Case: COOLER MASTER Elite 110 MB: ASRock Z97E-ITX/ac CPU: Intel Pentium G3258 PS: SILVERSTONE ST45SF-G 450W SFX12V Ram: G.SKILL Ripjaws X Series 8GB HD1: Samsung SSD 840 EVO 250GB -3 years old HD2: TOSHIBA HDWD130 - 3 mos old Did a full format on it today. The OS installed just fine, the issue occurred 2-3 days later. It was Win 10 15063 OS, rolled back to 1607 So far, all is good. The system is 3-years old, was planning to replace it this summer. Link to comment Share on other sites More sharing options...
sam3971 Posted April 9, 2017 Share Posted April 9, 2017 8 hours ago, virge said: System specs if that helps: Case: COOLER MASTER Elite 110 MB: ASRock Z97E-ITX/ac CPU: Intel Pentium G3258 PS: SILVERSTONE ST45SF-G 450W SFX12V Ram: G.SKILL Ripjaws X Series 8GB HD1: Samsung SSD 840 EVO 250GB -3 years old HD2: TOSHIBA HDWD130 - 3 mos old Did a full format on it today. The OS installed just fine, the issue occurred 2-3 days later. It was Win 10 15063 OS, rolled back to 1607 So far, all is good. The system is 3-years old, was planning to replace it this summer. The drives do not seem that old. Have you tried reinstalling 15063 fresh? Link to comment Share on other sites More sharing options...
virge Posted April 9, 2017 Author Share Posted April 9, 2017 12 minutes ago, sam3971 said: The drives do not seem that old. Have you tried reinstalling 15063 fresh? I did, prefer LTSB so will wait till 2018/2019 or whenever next Redstone builds comes out. Here is the official answer from Microsoft after going back and forth with them for a week. Used Macronit Disk Scanner to scan every sector for errors, took a long time, but it didn't find one bad sector.BTW--Thanks for your help on this. Quote https://answers.microsoft.com/en-us...ot-found/46a244b4-970b-4753-9bbd-002916471f87You may try to run a check disk for the drives and let it repair them.1. Click Start, type cmd in the Start Search box, right-click cmd.exe in the Programs list, and then click Run as administrator.If you are prompted for an administrator password or for confirmation, type your password, or click Continue. 2. At a command prompt, type the following command, and then press ENTER:Chkdsk /R X:Note: In this command, X: is a placeholder that represents the drive letter of the volume that you want to check. 3. Press Y when you are prompted to check the disk the next time that the system restarts. 4. Close all applications, and then restart the computer.Note: During the restart process, Windows checks the disk for errors, and then Windows starts. 5. After the computer restarts, repeat steps 1 through 4 for the other volume, and then rerun the backup operation. For more additional information follow the link given below.Check a drive for errorshttp://windows.microsoft.com/en-us/windows7/Check-a-drive-for-errorsIf that does not help you may check the link given below which talks about the rebuilding of the Boot files run the rebuildBCD command and check if that helps.How to use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windowshttp://support.microsoft.com/kb/927392Hope this information is helpful.Amrita MMicrosoft Answers Support EngineerVisit our Microsoft Answers Feedback Forum and let us know what you think. Link to comment Share on other sites More sharing options...
virge Posted April 11, 2017 Author Share Posted April 11, 2017 So after further diagnostics, the problem turned out to be the motherboard. After testing each component one by one in another system... ram, hard drive, power supply, what was left over was obvious. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.