NBRT starts but never finishes

Norton Security | Norton Internet Security
1

Downloaded NBRT.ISO and Rufus. Created a bootable USB with NBRT. Setup system to boot the NBRT USB. NBRT starts to run for a few minutes, then stops and puts out 13 lines of info.
1st. line: Kernal panic - not syncing: Attempted to kill init!
2nd. line: Pid: 1, comm: init Tainted: G W – ------------ 2.6.32-754.35.1.e16.i686 #1
3rd. line: Call Trace:
4th. line: [] ? panic+0x6e/0x13b
5th. line: [] ? do_exit+0x737/0x740
6th. line: [] ? sysenter_past_esp+0x6e/0xc2
7th. line: [] ? sysenter_past_esp+0x7a/0xc2
8th. line: [] ? sysenter_past_esp+0x6e/0xc2
9th. line: [] ? sysenter_past_esp+0x6e/0xc2
10th. line: [] ? sysenter_past_esp+0x6e/0xc2
11th. line: [] ? do_group_exit+0x3c/0xa0
12th. line: [] ? sys_exit_group+0x11/0x20
13th. line: [] ? sysenter_do_call+0x29/0x43

Why does it stop and what to do to fix it so it completes.

2

Glad you have a solution and thanks for posting back.

SA

3

Sorry for the long delay. Didn’t have the time.
Spent yesterday trying to get it to run with no luck.
So; today I decided to try another track. I have a software package that will burn the image to disk. Tried that and it ran fully to completion with nothing found.
So; I guess we can close the ticket. Thanks a bunch.

4

@BootCamp49 Just following up to see if the last suggestions provided any different results and if we can assist further.

SA

5

Just an FYI!! Opening a pdf file has its risks, most people here won't open them for that reason. The procedure to embed screenshots is a fairly straight forward practice. The IMCE icon just above the comments box is where to get started. 

Your screenshots: Note = The partition scheme should be MBR vice GPT as the article I linked shows for a legacy boot. You can also retry with NTFS under File System and see if the USB will boot under Legacy in BIOS. 

If the changes to Rufus do not allow the USB boot the below is the most logical issue to everything:

If you installed Windows on this HD while it was installed in another computer that is the issue. The laptop it belongs to has specific registry entries, the laptop/device it was in when Windows was installed will have different hardware and thus different settings. Windows won't recognize the original hardware and will not boot or be mounted

As a last resort. Reinstall Windows again with the HD in question installed in the device it belongs to. Re-run Rufus with the changes I suggested. Please post results follow-up.

SA

6

I have attached a screen print of running Rufus.

7

Windows won't recognize the original hardware and will not boot or be mounted. This line "1st. line: Kernal panic - not syncing: Attempted to kill init!" shows that to be the case. Kernal panic doesn't normally happen on Windows unless that OS has a VM involved. Its usually associated with "Grub" on Linux and MACOS.   It boots up everytime with NO problem.  There is NO VM involved, nor Linux, nor MACOS.  It has been running fine since I did this.

The other possible cause is the way you created the USB bootable drive. Did you follow these steps exactly? I usually use FAT32 which will allow the ISO to create its own file tables.  I created the NBRT USB drive exactly the way it says.  Used FAT32 and set UEFI to Legacy.

I cut and pasted two screen shots into WORD and saved it.  Will try and attach it.

8

Post your screenshot using this guide. The "Add a new file" area below the comment section won't accept jpg files as noted:

https://community.norton.com/en/forums/how-post-image-forums-0

You said: As I had said; I removed the drive, wiped it; ran a full complete Norton Scan; installed windows; and placed it back into the laptop.

If you installed Windows on this HD while it was installed in another computer that is the issue. The laptop it belongs to has specific registry entries, the laptop/device it was in when Windows was installed will have different hardware and thus different settings. Windows won't recognize the original hardware and will not boot or be mounted. This line "1st. line: Kernal panic - not syncing: Attempted to kill init!" shows that to be the case. Kernal panic doesn't normally happen on Windows unless that OS has a VM involved. Its usually associated with "Grub" on Linux and MACOS. 

The other possible cause is the way you created the USB bootable drive. Did you follow these steps exactly? I usually use FAT32 which will allow the ISO to create its own file tables.

You said: I also flashed the BIOS/EUFI to the latest one. Then I made changes to the EUFI settings to reflect the laptop settings.

Is the boot setting set to LEGACY in BIOS? 

https://hollandsweb.medium.com/create-a-windows-10-usb-via-rufus-uefi-or-legacy-8efa9eea6b2e

  • Choose the partition scheme and target system type:
  • For UEFI: Under “Partition scheme,” select “GPT” and under “Target system,” select “UEFI (non-CSM).”
  • For Legacy/BIOS: Under “Partition scheme,” select “MBR” and under “Target system,” select “BIOS or UEFI”.
  • If “BIOS or UEFI” doesn’t show in the list Just press Alt + E and then will show this option.

SA

 

 

9

Thanks for your reply.

As I had said; I removed the drive, wiped it; ran a full complete Norton Scan; installed windows; and placed it back into the laptop.

I also flashed the BIOS/EUFI to the latest one. Then I made changes to the EUFI settings to reflect the laptop settings.

So, I would think I covered anything they could have left on the laptop.

But; going back to the original question; why doesn't NBRT run  to completion? I keep getting the following 13 lines.

1st. line: Kernal panic - not syncing: Attempted to kill init!

2nd. line: Pid: 1, comm: init Tainted: G W -- ------------ 2.6.32-754.35.1.e16.i686 #1

3rd. line: Call Trace:

4th. line: [<c088d8d5>] ? panic+0x6e/0x13b

5th. line: [<c046d307>] ? do_exit+0x737/0x740

6th. line: [<c0898a4a>] ? sysenter_past_esp+0x6e/0xc2

7th. line: [<c0898a56>] ? sysenter_past_esp+0x7a/0xc2

8th. line: [<c0898a4a>] ? sysenter_past_esp+0x6e/0xc2

9th. line: [<c0898a4a>] ? sysenter_past_esp+0x6e/0xc2

10th. line: [<c0898a4a>] ? sysenter_past_esp+0x6e/0xc2

11th. line: [<c046d34c>] ? do_group_exit+0x3c/0xa0

12th. line: [<c046d3c1>] ? sys_exit_group+0x11/0x20

13th. line: [<c0898ac7>] ? sysenter_do_call+0x29/0x43

There was no way to save this info on the laptop, so I took a photo. It is in the form of a jpg file and that is not one of the accepted file types that can be attached.

Thanks for your help!!

10

If this were my machine I'd just replace with a NEW HD and reinstall Windows. Zero possibility of anything residual being on it with brand new hardware. As long as the previous Windows install was being used by someone with a MS account when it was activated reactivation should be automatic at no cost. 

Edited: If you have already flashed the BIOS it should be clean unless you cannot change settings. That would indicate there is an issue present. 

SA

11

Thanks for your reply.

I am running it on a Dell Latitude running Windows 10.

As I had said; I downloaded NBRT.ISO and Rufus and created a bootable USB.

I used this on the Dell laptop.  The NBRT starts and runs.  The symbol that shows it running starts at 12 O'Clock and runs down to about 5 O'Clock then stops.  It then puts out those 13 lines of info.

I saw that Dell had a new BIOS/EUFI. My laptop had version A21 and there was a new one, version A24.

So I downloaded this and installed it.

Then I reran NBRT and got the same results.

How do I get this to run to completion?

I even went into the BIOS/EUFI and set it to only boot from a USB automatically.  This way you \don't have to hit F12 and select the USB.  Got the same result.

Reason for running NBRT; wife gave "Microsoft", scammers, access to the system.  They deleted all of the files and did a system reset. I took the drive from the system to another system; wiped it; did a complete brand new install of windows from the top; then ran Norton on the full drive. Came out clean. But I don't trust that there isn't something lurking in the BIOS/EUFI.

12

Hello. Are you on MAC? Just wanting to clarify. Have you viewed this article for some suggestions about any missteps in the run process?

https://support.norton.com/sp/en/us/home/current/solutions/v72380755

Depending on your requirement, do one of the following:

Run a scan using Norton Bootable Recovery Tool

›

  1. Insert the recovery media (Norton Bootable Recovery Tool DVD or USB device) and then turn on or restart your computer.

  2. Enter the BIOS mode by pressing the key that appears on the screen immediately after your computer restarts.

  3. Select the DVD or the USB drive on which you created Norton Bootable Recovery Tool, and then press Enter.

    <p><u><strong>If you use a UEFI-enabled computer, select the recovery media under the Legacy Boot option instead of the UEFI Boot option.</strong></u> The recovery media is the Norton Bootable Recovery Tool DVD or USB drive.</p>
</li>
<li>
<p>The Norton Bootable Recovery Tool starts automatically after the countdown.</p>

<p>If the boot menu appears, in the&nbsp;<strong>Welcome to NBRT</strong>&nbsp;page, select&nbsp;<strong>Boot</strong>.</p>

<p>If the boot fails, select&nbsp;<strong>Boot (Basic Video)</strong>.</p>
</li>
<li>
<p>In the&nbsp;<strong>Select Language</strong>&nbsp;drop-down list, select your preferred language, and click&nbsp;<strong>OK</strong>.</p>
</li>
<li>
<p>Read the license agreement, and then click&nbsp;<strong>Agree</strong>.</p>
</li>
<li>
<p>Click&nbsp;<strong>Start Scan</strong>.</p>
</li>
<li>
<p>In the&nbsp;<strong>Scan Completed</strong>&nbsp;window, review the scan results.</p>

<p>By default, all detected threats have a selected remediation action. You can also select the appropriate action for each of the threats.</p>

<p>Review the scan results carefully before resolving the threats, because the files that are removed cannot be restored.</p>
</li>
<li>
<p>Click&nbsp;<strong>Fix</strong>.</p>
</li>
<li>
<p>In the&nbsp;<strong>Confirmation</strong>&nbsp;window, click&nbsp;<strong>OK</strong>.</p>
</li>
<li>
<p>In the&nbsp;<strong>Remediation</strong>&nbsp;window, click&nbsp;<strong>Continue</strong>.</p>
</li>
<li>
<p>Click&nbsp;<strong>Reboot</strong>.</p>
</li>

SA