PC Desktop: Very Frequently BSOD + NTRLD is Missing

M

masTKI

New Member
Hi Experts.
I believe this question has been asked several time but I'm still not able to solve the problem with my PC desktop.
It's an old self assembly PC. The last time i upgraded the hardware was in early 2015, with the following configurations:
  • Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz 3.60 GHz
  • NVIDIA GeForce GT610
  • 2 x 16 GB DDR3 1600
  • C: Kingstone SV300S37A240G - For system and app. Free space more than 20%.
  • D: DVD/CD-ROM Drive Asus DRW-24D3ST
  • E: Hitachi HDT725050VLA380 (500 GB) - free space approx. 50
  • F: ST2000DM008-2FR102 (1.8 TB) - free space approx. 60%
I'm not into the gaming. Mostly I use my PC for Adobe Lightroom, YouTube and internet browsing only.
I upgrade the OS from Windows 7 to 10 two weeks ago to enable me to install plug-in Luminar AI.
Worked well for around one week, then the problem happen and continue until today, ie. my PC frequently crash / BSOD and then after re-boot stop at black screen "NTRDL is Missing". It happen several time a day after, after 1- 4 hours using my PC; even if I don't use it.
The BSOD error messages are not always similar. Could be:
  • Critical process died
  • System service exception
  • Unexpected store exception
  • Page Fault in nonpaged area
Once the NTRDL is missing screen occur; it will not back to normal if I immediately press "Ctrl + alt Del". It always back to NTRDL is missing screen.
I have to wait sometime (could be more than 1 hours) to press "Ctrl + alt Del" and then the PC will back to normal, though the problem happen again after 1 - 4 hours.
I've done few things such as memory test (Windows 10 memory diagnostic ), Chkdsk, Test all drive with CrystalDisk , Bitdefender system scan & vulnerability scan; all are good. Check and update all drivers. Check the temperatures - all good (35 - 42 C)
The problem does not disappear; in fact getting worst (more frequently and longer waiting time to reboot).
Very frustrating.
Thanks and appreciate for any advices and suggestions.
 
Do this.

Download BlueScreenView
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
 
@johnb35
Many thanks for the advice.
Unfortunately, I face another problem. Now, the PC stop at bios booting, frozen at this screen.

IMG_20210801_175803.jpg
I can't do anything.
I will wait and try again, hopefully back to windows screen.
 
Thanks a lot for all advise. Being dumb-dumb, taking more time to get back and update.
For few days, the PC does not response at all. Stop at the bios start-up screen as above. But today, it back to the |NTRDL is missing" screen.
So, I try to perform a startup repair using a bootable USB.
I could see the Boot Menu, then I select:
Start-up Repair > Troubleshoot > Advanced Options > Start-up repair --- get the message "Start-up repair couldn't repair your PC"
Repeat several times, with two HDD's removed (SSD still connected); same result.
No idea, what should I do now
 
While SSD's rarely fail, it is possible. Those Kingstons weren't the best but it should still be ok.

At this point I would reinstall Windows. I'm guessing your valuable data is on the other drives? If so a simple wipe and reinstall should be easy enough. If you still have problems after that it's 99 percent likely to be a hardware problem.
 
Darren said:
While SSD's rarely fail, it is possible. Those Kingstons weren't the best but it should still be ok.

At this point I would reinstall Windows. I'm guessing your valuable data is on the other drives? If so a simple wipe and reinstall should be easy enough. If you still have problems after that it's 99 percent likely to be a hardware problem.
Click to expand...
Thanks Darren.
Indeed, all the data are in both HDD. Windows and other software are in the SSD. I have the back-up in an external hard drive too.
I'm not quite sure what you mean a simple wipe and reinstall.
I did the following steps:

> Windows Setup > Activate Windows > Windows 10 Home > Accept Term & Condition > Custom: Install Windows only (Advanced) >

I cant find my SSD. The available options are:
NameTotal SizeFree SpaceType
Drive 1 Partition 1128.0 MB128.0 MBMSR (Reserved)
Drive 1 Partition 2 New Volume1862.9 GB616.GBPrimary
Drive 2 Partition 1465.8 GB266.1 GBSystem

so I choose the Drive 1 Partition 2. Does not work. Stop with a message : We couldn't create a new partition or locate an existing one. For more information see the set up log.

I don't know where is the setup log.

Since I cant find the SSD - does it mean the SSD fail/broken?

I cant install to Drive 2 Partition 1. The message : Windows cannot be installed to this disk. The selected disk has an MBR partition table. On EFI system, Windows can only be installed to GPT disk

Then to install Windows, do I need to format the drive 2 Partition 1 ?

Thanks again
 
Stop what you are doing until you figure out which one is the ssd. First of all, how big is the ssd? What that list shows is 2 drives 1 with 2 tb and the other with 500gb.
 
Drive 2 Partition 1 would have been your E drive since it's 500GB (~465 GiB), Drive 1 would be your other 2TB mechanical drive, the one you had mapped to F:

I'd unhook all of the other drives but the SSD when trying to install Windows, if it never shows up in BIOS as a SATA device or on the Windows installation screen, it's probably dead. It may also be worth trying to reseat the connectors and try another SATA cable to the SSD, or a different SATA port on the motherboard.
 
Thanks again,
I detached the two HDD (E: and F Check BIOS, all SATA device are empty except Port 1 (DRW drive)
The only drive available on the windows setup menu is Drive 0 Unallocated spare with total size 0.0 MB.
Seem my SSD is dead.
 
Last edited:
Intel_man said:
Try a different sata port and sata cable.
Click to expand...
Thanks @Intel_man
I connected the SSD with one of the Sata port previously used for HDD; switch-on, my PC quickly completed the start-up routine and displayed the normal Windows 10 desktop screen including all applications.
I can access the C: (SSD) drive and the bootable USB. Unfortunately, this only happen for 5 minutes before BSOD Critical Process Died; then back again to USB windows set-up; similar with previous process. The only drive available on the windows setup menu is Drive 0 Unallocated spare with total size 0.0 MB. No repair or windows installation can be done.

Then I connected the SSD to another Sata port; exactly similar as above. After 5 minutes, I got BSOD Critical Process Died.
then back again to USB windows set-up; similar with previous process. The only drive available on the windows setup menu is Drive 0 Unallocated spare with total size 0.0 MB. No repair or windows installation can be done.

Now, all three Sata ports are not working. The SSD drive is not recognized.
 
After sometime; I connected the SSD to one of Sata Port; it work again - get the Windows 10 desktop screen; for 5 minutes before BSOD Critical Process Died - again.
 
Run that bluescreen program I posted about and post the results. You've got bad hardware somewhere.
 
johnb35 said:
Run that bluescreen program I posted about and post the results. You've got bad hardware somewhere.
Click to expand...
Thanks - I misunderstood your instruction by googling the program trying to download. My PC always stop and get another BSOD every time I connect USB wifi modem.
I just realized you attached the program - thanks again. This help a lot. This what I get:

==================================================
Dump File : 080121-8187-01.dmp
Crash Time : 01/08/2021 09:16:24
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffe78e`f32045e8
Parameter 2 : 00000000`00000002
Parameter 3 : fffff806`40227e60
Parameter 4 : 00000000`00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f6f20
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+3f6f20
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\080121-8187-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 19041
Dump File Size : 1,865,020
Dump File Time : 01/08/2021 09:17:18
==================================================

==================================================
Dump File : 071221-13734-01.dmp
Crash Time : 12/07/2021 07:49:22
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : ffff8a80`01068240
Parameter 3 : 00000000`000001ff
Parameter 4 : 00000000`00000200
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f6b90
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+3f6b90
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\071221-13734-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 19041
Dump File Size : 1,883,188
Dump File Time : 12/07/2021 07:50:10
==================================================

==================================================
Dump File : 071021-10203-01.dmp
Crash Time : 10/07/2021 18:20:17
Bug Check String :
Bug Check Code : 0x00000139
Parameter 1 : 00000000`00000003
Parameter 2 : ffff8485`1fa532b0
Parameter 3 : ffff8485`1fa53208
Parameter 4 : 00000000`00000000
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+4ce90
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+3f6b90
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\071021-10203-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 19041
Dump File Size : 2,090,228
Dump File Time : 10/07/2021 18:22:13
==================================================

==================================================
Dump File : 070721-6687-01.dmp
Crash Time : 07/07/2021 11:58:47
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff801`42335c42
Parameter 3 : fffff181`17b85818
Parameter 4 : fffff181`17b85050
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+135c42
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : Ntfs.sys+135c42
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\070721-6687-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 19041
Dump File Size : 1,935,052
Dump File Time : 07/07/2021 12:00:09
==================================================
 

Attachments

Looks like some of the issues is memory related. However, please zip up the following files and attach them to your next post. I will then try to debug them for better clarification of whats going on.

C:\WINDOWS\Minidump\070721-6687-01.dmp
C:\WINDOWS\Minidump\071021-10203-01.dmp
C:\WINDOWS\Minidump\071221-13734-01.dmp
C:\WINDOWS\Minidump\080121-8187-01.dmp
 
masTKI said:
My PC always stop and get another BSOD every time I connect USB wifi modem.
Click to expand...
Does your PC operate fine otherwise? I'd quit using that if that's the case, some failing USB devices can do weird things to the rest of the system from a power or grounding perspective. Also obscure one off devices or bottom-bin budget ones generally seem to have the worst driver support, a lot of devices suffer from issues down the line from a buggy 'one and done' firmware that nobody cares about updating.

What specific USB modem is it?
 
johnb35 said:
Looks like some of the issues is memory related. However, please zip up the following files and attach them to your next post. I will then try to debug them for better clarification of whats going on.

C:\WINDOWS\Minidump\070721-6687-01.dmp
C:\WINDOWS\Minidump\071021-10203-01.dmp
C:\WINDOWS\Minidump\071221-13734-01.dmp
C:\WINDOWS\Minidump\080121-8187-01.dmp
Click to expand...
Unfortunately until now I'm not able to bring back the computer back to work despite swapping all for SATA ports to the SSD. The SSD is not recognized.
Previously I was lucky, after waiting several hours then swap to one of the sata port, the PC worked for less than 5 minutes before BSOD critical process died.
I'll wait few days, hope my luck return. If not, I will connect to one of the HHD (500 GB one - I have the back-up files) and install the Windows there.
 
beers said:
Does your PC operate fine otherwise? I'd quit using that if that's the case, some failing USB devices can do weird things to the rest of the system from a power or grounding perspective. Also obscure one off devices or bottom-bin budget ones generally seem to have the worst driver support, a lot of devices suffer from issues down the line from a buggy 'one and done' firmware that nobody cares about updating.

What specific USB modem is it?
Click to expand...

My PC worked for less than 5 minutes without the USB modem before BSOD. But, if connect the USB modem (before BSOD), then the PC stop / hang almost immediately (no BSOD).

The USB modem is TP-Link TL-WN727N (150 Mbps). I don't have any problem with this USB modem before.
 
You must log in or register to reply here.
Back
Top