Windows 10: Dell Vostro 3559 won't boot to Windows 10 or USB PE Solved

Page 3 of 4 FirstFirst 1234 LastLast
  1.    26 Mar 2018 #21

    I don't think its a physical memory problem as the user reported its been swapped with a working PC.

    Did a swap of Hard Disk and Memory with friends laptop - and with the HDD and memory from wife's laptop the friend's laptop booted into windows without errors.

    The swap also revealed that with the HDD and memory from friend's laptop in the wife's Dell, same error messages as originally!
      My ComputersSystem Spec


  2. Posts : 5
    Windos 10 PRO 64bit
       26 Mar 2018 #22

    To me it sounds like the BIOS update reset some BIOS settings.

    Make sure that Boot option is set to UEFI, legacy boot option to disabled, secure boot to enabled

    Settings for W8 and 10. You could also try to load default in Bios
      My ComputersSystem Spec


  3. Posts : 18,508
    windows 10 professional version 1607 build 14393.969 64 bit
       26 Mar 2018 #23

    Very often when a drive is moved from one computer to another the computer cannot boot as the operating system is married to the motherboard.

    Please clarify the swaps that were done:
    Was the SSD able to be the boot drive an launch Windows in the other computer?
    Was a SSD from another computer able to be the boot drive and launch Windows in the problematic computer?

    Also in the thread you commented that you have an image.

    Consider installing Windows on the SSD and test the computer as a clean install. Then if the hardware and operating system after clean install passes you can recover the image.
      My ComputerSystem Spec

  4.    26 Mar 2018 #24

    rydhan said: View Post
    To me it sounds like the BIOS update reset some BIOS settings.
    Make sure that Boot option is set to UEFI, legacy boot option to disabled, secure boot to enabled

    I thought of that, but the BIOS, although showing the SSD no boot options are available.
    I have made a UEFI WinPE USB boot disk, and can boot into it OK now.

    So there does seem to be a problem with the BIOS and booting.

    If I change to UEFI mode I keep getting the message 'No File System Found'.
    Could that mean the SSD will only boot in legacy mode?
      My ComputerSystem Spec

  5.    26 Mar 2018 #25

    zbook said: View Post
    Very often when a drive is moved from one computer to another the computer cannot boot as the operating system is married to the motherboard.

    Please clarify the swaps that were done:
    Was the SSD able to be the boot drive an launch Windows in the other computer?
    Was a SSD from another computer able to be the boot drive and launch Windows in the problematic computer?

    Also in the thread you commented that you have an image.

    Consider installing Windows on the SSD and test the computer as a clean install. Then if the hardware and operating system after clean install passes you can recover the image.
    The swops worked fine. It was a different make (Lenovo) but it booted into Windows 10 after it updated some drivers. So the disk is fine!
      My ComputerSystem Spec

  6.    26 Mar 2018 #26

    I think (certain) the SSD was setup using Legacy/BIOS mode, I cannot see anywhere it has a UEFI mode.

    Unfortunately the disk will not boot using the BIOS legacy mode! It returns the errors in my first post.

    So even if I could start afresh with Windows 10, and then reinstalled the image would I be back to square one?
    Last edited by lafargeotte; 26 Mar 2018 at 15:41.
      My ComputerSystem Spec


  7. Posts : 18,508
    windows 10 professional version 1607 build 14393.969 64 bit
       26 Mar 2018 #27

    In the post you had indicated that you can boot the SSD in other computers. When in other computers you can view disk management. In addition you can download and install Minitool partition wizard. If you can post both of these in the thread we can confirm what is on the drive.
    Also on the working computer with the drive you can run the beta log collector and post a zip into the thread for troubleshooting.

    Disk Management - How to Post a Screenshot of Windows 10 Tutorials
    MiniTool Partition Wizard Free Edition - Free download and software reviews - CNET Download.com

    And if you run administrative command prompt on the drive in the working computer run these commands:
    1) sfc /scannow
    2) dism /online /cleanup-image /scanealth
    3) dism /online /cleanup-image /restorehealth
    4) chkdsk /scan
    5) diskpart
    7) list disk
    8) list volume
    9) select disk 0
    10) list partition
    11) exit
    12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
      My ComputerSystem Spec

  8.    27 Mar 2018 #28

    The Dell was upgraded from Windows 7 to 10, so pretty certain it is legacy.

    The SSD is in a different laptop, Lenovo, also legacy. Working fine. This is a friend's spare, and I can keep it for a while, so will leave the SSD in there for now until I can find a solution!

    Click image for larger version. 

Name:	DiskMngt.JPG 
Views:	3 
Size:	123.0 KB 
ID:	182458Click image for larger version. 

Name:	PartWiz.JPG 
Views:	2 
Size:	131.9 KB 
ID:	182459

    Here is the read out from the instructions you requested. Note that it wanted to repair but for some reason, probably because Cortana is disabled, but after pointing to the wim file in 2 separate places it did not work!

    Microsoft Windows [Version 10.0.16299.334]
    (c) 2017 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.

    C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15

    Image Version: 10.0.16299.334

    [==========================100.0%==========================] The component store is repairable.
    The operation completed successfully.

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15

    Image Version: 10.0.16299.334

    [==========================100.0%==========================]
    Error: 0x800f081f

    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source | Microsoft Docs.

    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.
    Volume label is MainDisk.

    Stage 1: Examining basic file system structure ...
    473344 file records processed.
    File verification completed.
    17430 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    28788 reparse records processed.
    545132 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    28788 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    35895 data files processed.
    CHKDSK is verifying Usn Journal...
    37487600 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    106986817 KB total disk space.
    33700632 KB in 124762 files.
    103704 KB in 35896 indexes.
    0 KB in bad sectors.
    585837 KB in use by the system.
    65536 KB occupied by the log file.
    72596644 KB available on disk.

    4096 bytes in each allocation unit.
    26746704 total allocation units on disk.
    18149161 allocation units available on disk.

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth /Source:wim:G:\sources\install.wim

    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15

    Image Version: 10.0.16299.334


    Error: 87

    An error occurred while processing wim:G:\sources\install.wim. The specified path was not found.
    Ensure that the argument is valid and that the path exists.

    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth /Source:wim:G:\sources\install.wim:1 /limitaccess

    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15

    Image Version: 10.0.16299.334

    [===========================85.0%================= ]
    Error: 0x800f081f

    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source | Microsoft Docs.

    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth /Source:wim:C:\W10\sources\install.wim:1 /limitaccess

    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15

    Image Version: 10.0.16299.334

    [===========================84.9%================= ]
    Error: 0x800f081f

    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source | Microsoft Docs.

    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth /Source:wim:C:\W10\sources\install.wim

    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15

    Image Version: 10.0.16299.334

    C:\WINDOWS\system32>diskpart

    Microsoft DiskPart version 10.0.16299.15

    Copyright (C) Microsoft Corporation.
    On computer: JILLLAPTOP

    DISKPART> list disk

    Disk ### Status Size Free Dyn Gpt
    -------- ------------- ------- ------- --- ---
    Disk 0 Online 447 GB 0 B

    DISKPART> list volume

    Volume ### Ltr Label Fs Type Size Status Info
    ---------- --- ----------- ----- ---------- ------- --------- --------
    Volume 0 F DVD-ROM 0 B No Media
    Volume 1 C MainDisk NTFS Partition 102 GB Healthy System
    Volume 2 NTFS Partition 489 MB Healthy
    Volume 3 D Programs NTFS Partition 112 GB Healthy
    Volume 4 E Software Ba NTFS Partition 231 GB Healthy

    DISKPART> select disk 0

    Disk 0 is now the selected disk.

    DISKPART> list partition

    Partition ### Type Size Offset
    ------------- ---------------- ------- -------
    Partition 1 Primary 102 GB 1024 KB
    Partition 2 Primary 489 MB 102 GB
    Partition 3 Primary 112 GB 102 GB
    Partition 4 Primary 231 GB 215 GB

    DISKPART> exit

    Leaving DiskPart...

    C:\WINDOWS\system32>

    Why will the BIOS now not read the legacy SSD? If I change the BIOS to UEFI mode and insert a UEFI USB key, I can boot to it. However, if the BIOS is in legacy mode and it will not boot to a legacy USB, error 'Page Fault Error in non-paged area'.

    Just out of curiosity I put the Lenovo's SSD (128GB) with Windows 10 Pro into the Dell, and again got exactly the same error message as the Dell was giving to my SSD (well the wife's!!!), 'Memory Management'.
    Last edited by lafargeotte; 27 Mar 2018 at 11:08.
      My ComputerSystem Spec

  9.    27 Mar 2018 #29

    Well, managed to solve it with the aid of Google (5 days of it!!!).

    Basically when the BIOS updated it turned PTT ON. To boot with legacy PTT must be OFF. So thanks Dell for not even helping when I contacted you!!!

    Thanks to you guys for trying to help, it was a weird one, but got there in the end.

    So, for anyone else who finds themselves in this situation, if you cannot boot using legacy you will probably need to turn off PTT. It is in the BIOS under the 'Security' section. Here are a couple of links to help others, note the BIOS is of a different model, but it seems all recent Dells are very similar:
    http://www.dell.com/support/article/fr/fr/frbsdt1/sln302676/how-to-configure-the-trusted-platform-module-tpm-when-its-greyed-out-in-bios-on-a-latitude-7350?lang=en

    Windows 10 firmware bootloaders unable to boot from the Unified Extensible Firmware Interface (UEFI) on my Dell laptop



      My ComputerSystem Spec

  10.    27 Mar 2018 #30

    The TPM is on Dell "business" systems and the Vostro's are/were Dell's entry level business machines.
    I was aware of that but never thought that would cause the problem.

    But, glad to hear its sorted out.
      My ComputersSystem Spec


 
Page 3 of 4 FirstFirst 1234 LastLast

Related Threads
ok before i take this laptop to a repair shop i needed to ask for help. This is my huge problem, i installed rollbax rx trail to test it, when it rebooted i saw the BSOD. I created a iso backup using macrium so i thought i was safe but i guess not....
Dell 3847 Inspiron with Windows 10 Home OS. I can change the BIOS to boot from ODD as the primary but system still boots to Windows. Dell support had me update chipset drivers but no luck. After an hour of trial and error they then wanted to...
How can I boot my Dell Studio 1749 Laptop from either a USB or External HP CD/DVD drive in order to bypass a disabled internal CD/DVD (with stuck disk)? And how do I create the USB Boot Drive? The F12 boot options freeze up trying to boot my...
Solved problem upgrading dell vostro 1000 laptop in Windows Updates and Activation
Tried upgrading my vostro 1000 to Windows 10, but got an message window saying that Dell has an issue with ati Radeon xpress 1150 not sure if it's a driver issue or hardware.. is is there anything I can do ? thanks
I have two older Dell Vostro laptops: Vostro 1720 Windows 7 Home Premium x64 Vostro 3550 Windows 7 Home Premium x64 For each one, when I go to the Dell product support site and enter the service tag, I get the following warning. I suspect that...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 14:43.
Find Us