Advanced Diagnostics Driver

21-04-2021 by



HP PC Hardware Diagnostics Windows is a Windows-based utility that allows you to run diagnostic tests to determine if the computer hardware is functioning properly. The tool runs within the Windows operating system in order to diagnose hardware failures.

-->

Note

  • What if Diagnostic Troubleshooting Tool Does Not Work on Windows 10, 8.1, and 7. The Troubleshooting Assistant has been part of the Windows operating system for years. With Windows 10 Diagnostic tool, you can quickly verify that certain components of your operating system are working properly.
  • Diagnostic output is accessible on systems that are running supported Linux or Solaris operating systems. If you are having specific problems with your system, use the Pc-Check Diagnostics software to diagnose and resolve these issues. The following sections are included in this chapter: Pc-Check Diagnostics Overview; Advanced Diagnostics Tests.
  • Advanced Diagnostics manufacture high quality car key programming & marine engine diagnostic equipment specifically developed for locksmiths, auto technicians and marine watercraft engineers worldwide. We develop all key programming and marine diagnostic software in-house for our products.

This article is intended for use by support agents and IT professionals. If you're looking for more general information about recovery options, see Recovery options in Windows 10.

Summary

There are several reasons why a Windows-based computer may have problems during startup. To troubleshoot boot problems, first determine in which of the following phases the computer gets stuck:

PhaseBoot ProcessBIOSUEFI
1PreBootMBR/PBR (Bootstrap Code)UEFI Firmware
2Windows Boot Manager%SystemDrive%bootmgrEFIMicrosoftBootbootmgfw.efi
3Windows OS Loader%SystemRoot%system32winload.exe%SystemRoot%system32winload.efi
4Windows NT OS Kernel%SystemRoot%system32ntoskrnl.exe

1. PreBoot

The PC’s firmware initiates a Power-On Self Test (POST) and loads firmware settings. This pre-boot process ends when a valid system disk is detected. Firmware reads the master boot record (MBR), and then starts Windows BootManager.

2. Windows Boot Manager

Windows Boot Manager finds and starts the Windows loader (Winload.exe) on the Windows boot partition.

3. Windows operating system loader

Essential drivers required to start the Windows kernel are loaded and the kernel starts to run.

4. Windows NT OS Kernel

The kernel loads into memory the system registry hive and additional drivers that are marked as BOOT_START.

The kernel passes control to the session manager process (Smss.exe) which initializes the system session, and loads and starts the devices and drivers that are not marked BOOT_START.

Here is a summary of the boot sequence, what will be seen on the display, and typical boot problems at that point in the sequence. Before starting troubleshooting, you have to understand the outline of the boot process and display status to ensure that the issue is properly identified at the beginning of the engagement.


Click to enlarge

Each phase has a different approach to troubleshooting. This article provides troubleshooting techniques for problems that occur during the first three phases.

Advanced Diagnostic Group

Note

If the computer repeatedly boots to the recovery options, run the following command at a command prompt to break the cycle:

Bcdedit /set {default} recoveryenabled no

If the F8 options don't work, run the following command:

Bcdedit /set {default} bootmenupolicy legacy

BIOS phase

To determine whether the system has passed the BIOS phase, follow these steps:

  1. If there are any external peripherals connected to the computer, disconnect them.
  2. Check whether the hard disk drive light on the physical computer is working. If it is not working, this indicates that the startup process is stuck at the BIOS phase.
  3. Press the NumLock key to see whether the indicator light toggles on and off. If it does not, this indicates that the startup process is stuck at BIOS.

If the system is stuck at the BIOS phase, there may be a hardware problem.

Boot loader phase

If the screen is completely black except for a blinking cursor, or if you receive one of the following error codes, this indicates that the boot process is stuck in the Boot Loader phase:

  • Boot Configuration Data (BCD) missing or corrupted
  • Boot file or MBR corrupted
  • Operating system Missing
  • Boot sector missing or corrupted
  • Bootmgr missing or corrupted
  • Unable to boot due to system hive missing or corrupted

To troubleshoot this problem, use Windows installation media to start the computer, press Shift+F10 for a command prompt, and then use any of the following methods.

Method 1: Startup Repair tool

The Startup Repair tool automatically fixes many common problems. The tool also lets you quickly diagnose and repair more complex startup problems. When the computer detects a startup problem, the computer starts the Startup Repair tool. When the tool starts, it performs diagnostics. These diagnostics include analyzing startup log files to determine the cause of the problem. When the Startup Repair tool determines the cause, the tool tries to fix the problem automatically.

To do this, follow these steps.

Note

For additional methods to start WinRE, see Windows Recovery Environment (Windows RE).

  1. Start the system to the installation media for the installed version of Windows. For more information, see Create installation media for Windows.

  2. On the Install Windows screen, select Next > Repair your computer.

  3. On the System Recovery Options screen, select Next > Command Prompt.

  4. After Startup Repair, select Shutdown, then turn on your PC to see if Windows can boot properly.

The Startup Repair tool generates a log file to help you understand the startup problems and the repairs that were made. You can find the log file in the following location:

%windir%System32LogFilesSrtSrttrail.txt

For more information see, A Stop error occurs, or the computer stops responding when you try to start Windows Vista or Windows 7

Method 2: Repair Boot Codes

To repair boot codes, run the following command:

To repair the boot sector, run the following command:

Note

Running BOOTREC together with Fixmbr overwrites only the master boot code. If the corruption in the MBR affects the partition table, running Fixmbr may not fix the problem.

Method 3: Fix BCD errors

If you receive BCD-related errors, follow these steps:

  1. Scan for all the systems that are installed. To do this, run the following command:

  2. Restart the computer to check whether the problem is fixed.

  3. If the problem is not fixed, run the following command:

  4. You might receive one of the following outputs:

If the output shows windows installation: 0, run the following commands:

After you run the command, you receive the following output:

  1. Try restarting the system.

Method 4: Replace Bootmgr

If methods 1, 2 and 3 do not fix the problem, replace the Bootmgr file from drive C to the System Reserved partition. To do this, follow these steps:

  1. At a command prompt, change the directory to the System Reserved partition.

  2. Run the attrib command to unhide the file:

  3. Run the same attrib command on the Windows (system drive):

  4. Rename the Bootmgr file as Bootmgr.old:

  5. Navigate to the system drive.

  6. Copy the Bootmgr file, and then paste it to the System Reserved partition.

  7. Restart the computer.

Method 5: Restore System Hive

If Windows cannot load the system registry hive into memory, you must restore the system hive. To do this, use the Windows Recovery Environment or use Emergency Repair Disk (ERD) to copy the files from the C:WindowsSystem32configRegBack to C:WindowsSystem32config.

Diagnostics

If the problem persists, you may want to restore the system state backup to an alternative location, and then retrieve the registry hives to be replaced.

Note

Starting in Windows 10, version 1803, Windows no longer automatically backs up the system registry to the RegBack folder.This change is by design, and is intended to help reduce the overall disk footprint size of Windows. To recover a system with a corrupt registry hive, Microsoft recommends that you use a system restore point. For more details, check this article.

Kernel Phase

If the system gets stuck during the kernel phase, you experience multiple symptoms or receive multiple error messages. These include, but are not limited to, the following:

Advanced Diagnostics Driver

  • A Stop error appears after the splash screen (Windows Logo screen).

  • Specific error code is displayed.For example, '0x00000C2' , '0x0000007B' , 'inaccessible boot device' and so on.

  • The screen is stuck at the 'spinning wheel' (rolling dots) 'system busy' icon.

  • A black screen appears after the splash screen.

To troubleshoot these problems, try the following recovery boot options one at a time.

Scenario 1: Try to start the computer in Safe mode or Last Known Good Configuration

On the Advanced Boot Options screen, try to start the computer in Safe Mode or Safe Mode with Networking. If either of these options works, use Event Viewer to help identify and diagnose the cause of the boot problem. To view events that are recorded in the event logs, follow these steps:

  1. Use one of the following methods to open Event Viewer:

    • Click Start, point to Administrative Tools, and then clickEvent Viewer.

    • Start the Event Viewer snap-in in Microsoft Management Console (MMC).

  2. In the console tree, expand Event Viewer, and then click the log that youwant to view. For example, click System log or Application log.

  3. In the details pane, double-click the event that you want to view.

  4. On the Edit menu, click Copy, open a new document in the program inwhich you want to paste the event (for example, Microsoft Word), and thenclick Paste.

  5. Use the Up Arrow or Down Arrow key to view the description of the previousor next event.

Clean boot

To troubleshoot problems that affect services, do a clean boot by using System Configuration (msconfig).Select Selective startup to test the services one at a time to determine which one is causing the problem. If you cannot find the cause, try including system services. However, in most cases, the problematic service is third-party.

Disable any service that you find to be faulty, and try to start the computer again by selecting Normal startup.

For detailed instructions, see How to perform a clean boot in Windows.

If the computer starts in Disable Driver Signature mode, start the computer in Disable Driver Signature Enforcement mode, and then follow the steps that are documented in the following article to determine which drivers or files require driver signature enforcement:Troubleshooting boot problem caused by missing driver signature (x64)

Note

If the computer is a domain controller, try Directory Services Restore mode (DSRM).

This method is an important step if you encounter Stop error '0xC00002E1' or '0xC00002E2'

Examples

Warning

Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that theseproblems can be solved. Modify the registry at your own risk.

Error code INACCESSIBLE_BOOT_DEVICE (STOP 0x7B)

To troubleshoot this Stop error, follow these steps to filter the drivers:

  1. Go to Window Recovery Environment (WinRE) by putting an ISO disk of the system in the disk drive. The ISO should be of same version of Windows or a later version.

  2. Open the registry.

  3. Load the system hive, and name it as 'test.'

  4. Under the following registry subkey, check for lower filter and upper filter items for Non-Microsoft Drivers:

    HKEY_LOCAL_MACHINESYSTEMControlSet001ControlClass

  5. For each third-party driver that you locate, click the upper or lower filter, and then delete the value data.

  6. Search through the whole registry for similar items. Process as an appropriate, and then unload the registry hive.

  7. Restart the server in Normal mode.

For additional troubleshooting steps, see the following articles:

Advanced Diagnostics Healthcare

To fix problems that occur after you install Windows updates, check for pending updates by using these steps:

  1. Open a Command Prompt window in WinRE.

  2. Run the command:

  3. If there are any pending updates, uninstall them by running the following commands:

Try to start the computer.

If the computer does not start, follow these steps:

  1. Open A Command Prompt window in WinRE, and start a text editor, such as Notepad.

  2. Navigate to the system drive, and search for windowswinsxspending.xml.

  3. If the Pending.xml file is found, rename the file as Pending.xml.old.

  4. Open the registry, and then load the component hive in HKEY_LOCAL_MACHINE as a test.

  5. Highlight the loaded test hive, and then search for the pendingxmlidentifier value.

  6. If the pendingxmlidentifier value exists, delete the value.

  7. Unload the test hive.

  8. Load the system hive, name it as 'test'.

  9. Navigate to the following subkey:

    HKEY_LOCAL_MACHINESYSTEMControlSet001ServicesTrustedInstaller

  10. Change the Start value from 1 to 4

  11. Unload the hive.

  12. Try to start the computer.

If the Stop error occurs late in the startup process, or if the Stop error is still being generated, you can capture a memory dump. A good memory dump can help determine the root cause of the Stop error. For details, see the following articles:

For more information about page file problems in Windows 10 or Windows Server 2016, see the following:

For more information about Stop errors, see the following Knowledge Base article:

Advanced Diagnostics Mri

If the dump file shows an error that is related to a driver (for example, windowssystem32driversstcvsm.sys is missing or corrupted), follow these guidelines:

  • Check the functionality that is provided by the driver. If the driver is a third-party boot driver, make sure that you understand what it does.

  • If the driver is not important and has no dependencies, load the system hive, and then disable the driver.

  • If the stop error indicates system file corruption, run the system file checker in offline mode.

    • To do this, open WinRE, open a command prompt, and then run the following command:

      For more information, see Using System File Checker (SFC) To Fix Issues

    • If there is disk corruption, run the check disk command:

    • If the Stop error indicates general registry corruption, or if you believe that new drivers or services were installed, follow these steps:

      1. Start WinRE, and open a Command Prompt window.
      2. Start a text editor, such as Notepad.
      3. Navigate to C:WindowsSystem32Config.
      4. Rename the all five hives by appending '.old' to the name.
      5. Copy all the hives from the Regback folder, paste them in the Config folder, and then try to start the computer in Normal mode.

Note

Starting in Windows 10, version 1803, Windows no longer automatically backs up the system registry to the RegBack folder.This change is by design, and is intended to help reduce the overall disk footprint size of Windows. To recover a system with a corrupt registry hive, Microsoft recommends that you use a system restore point. For more details, check this article.

Do you want to run diagnostics on Windows 10 operating system? Let’s read the give below solution to know how to perform diagnostics on Windows 10 step by step with sceenshots.

How to Run Diagnostics on Windows 10 Step by Step

  1. Type “Control Panel” on Windows search bar. Click on “Control panel”.
  2. Search and Hit on “System and Security”.
  3. Hit on “Administrative Tools”.
  4. Click on “Windows Memory Diagnostic”.

    5. Short Trick: Press Windows Key + R and type mdsched.exe

  5. Select “Restart now and check problems” option.

Once your machine restarts, it will open in Windows Memory Diagnostics environment. In this mode, the application will run all the scans available in the Basic mode.

What if Diagnostic Troubleshooting Tool Does Not Work on Windows 10, 8.1, and 7

The Troubleshooting Assistant has been part of the Windows operating system for years. With Windows 10 Diagnostic tool, you can quickly verify that certain components of your operating system are working properly. Unfortunately, some users have reported that the Diagnostic Troubleshooter no longer works error message on their Windows 10 PC. Since this can be a big problem, today we’ll show you how to fix it.

The Diagnostic Troubleshooting Wizard no longer works on Windows 10

Solutions

Solution 1 – Repair Microsoft.NET Framework installation

.NET Framework is used for all types of applications on Windows platforms, from system applications to video games. Almost every Windows operating system has .NET Framework installed, but sometimes this framework can cause all sorts of problems. According to the user, this Framework for Diagnostic Troubleshooting Wizard may have been responsible for working error message. To resolve this issue, you must repair the .NET Framework installation. This is a simple process, and to do this you must follow these steps:

  1. Press Windows key + S and enter programs. Select programs and functions from the result list.
  2. When Windows opens programs and functions, search for and select Microsoft.NET Framework.
  3. From the menu above, choose Change or Repair.
  4. Follow the instructions to repair your .NET Framework installation.
  5. After completing the repair process, verify that the problem is resolved.

If the problem persists, we recommend that you download this tool (100% safe and tested by us) to fix various PC issues such as corrupted files, malware and hardware errors.

Solution 2 – Reinstall Microsoft.NET Framework

As mentioned earlier, the .NET Framework installation may be the cause of this problem, and if repairing the .NET Framework installation does not resolve the issue, you will need to reinstall it. To do this, follow these steps:

  1. Open the application settings by Windows key + I press.
  2. When Settings app opens, go to System >> Apps & Features.
  3. The list of installed applications will now be displayed.
  4. Locate Microsoft.NET Framework , select it and choose Uninstall from the menu.
  5. Follow the uninstallation process to remove the .NET Framework.
  6. After the .NET Framework has been removed, download and install the following version of the Microsoft Web site.

If you do not want to use settings to remove the .NET Framework, you can also use the Programs and Features section . Just open it as in the previous solution, select the .NET Framework and choose Uninstall. After removing and reinstalling the .NET Framework, verify that the problem is resolved.

Solution 3 – Scan your PC for malware

Sometimes malicious applications interfere with the core components of Windows 10, and they can also cause the Diagnostics Troubleshooter to stop working . If you see this message, perform a detailed scan of your system with your antivirus program. In addition to your antivirus, you can use BitDefender or a similar tool to search for malware. After removing the malware, verify that the problem persists.

You can try BitDefender here.

Solution 4 – Check if the required services are running

Like any other Windows component, the Diagnostic Troubleshooting Wizard relies on certain services to run properly. However, if these services are not started or configured incorrectly, you may experience problems with the Diagnostic Troubleshooter. To check the status of your services, you must do the following:

Advanced Diagnostics Imaging

  1. Press Windows key + R and enter services.msc . Press Enter or click OK
  2. When Windows Services opens, locate the Diagnostic Policy Service and double-click it.
  3. Make sure that Service Status is set to Automatic on Running and Startup. If not, make the necessary changes. Click Apply and OK to save the changes.
  4. Now look for Diagnostic Service Host and Diagnostic System Host Services. Open their properties and make sure they are both running and that their startup type is set to Manual.
  5. After making the necessary changes, close the Windows Services and see if the problem is resolved.

By default, all these services should be running, but sometimes the status and startup type may change because of installed applications or because of some other computer problem, so check that all these services are running properly.

Solution 5 – Use registry editor

Before we begin, we must mention that using Registry Editor can potentially be dangerous and cause problems with your Windows 10 installation. It is recommended that you be careful when using Registry Editor. It is also a good practice to export your registry and use it as a backup in case something goes wrong. To edit your registration, you must do the following:

  1. Press Windows key + R and type regedit.
  2. When Registry Editor opens, in the left pane , navigate to HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsScriptedDiagnostics.
  3. Right-click the ScriptedDiagnostics button and select Delete from the menu.
  4. Then find the key ScriptedDiagnosticsProvider and delete it as well. This button should be located just below the ScriptedDiagnostics button.
  5. When finished, close the registry editor and see if the problem is resolved.

If you can not find these keys in your registry, it’s probably best to simply skip this solution.

Solution 6 – Temporarily disable the .NET Framework

As we have already mentioned, so Metimes.NET Framework may cause the Diagnostic Troubleshooting Assistant to stop working error message will appear on your Windows 10 PC. To resolve this issue, you must disable the .NET Framework. To do this, follow these steps:

  1. Open the Programs and Features section.
  2. When the Programs and Features section opens, click Turn Windows features on or off.
  3. The Windows Windows features will now be displayed. Locate the .NET Framework in the list and disable it. If you have multiple instances of the .NET Framework, make sure you disable them all.
  4. Click OK to save the changes.
  5. Restart your PC.
  6. When Windows 10 restarts, repeat these steps, enable the .NET Framework, and save the changes.
  7. Restart your PC and see if the problem is resolved.

Solution 7 – Create and run a batch file

Batch files can be very useful as they allow you to execute multiple commands almost immediately. Before you can run a batch file, you must create it, and you can do so by following these steps:

1. Open Notepad.

2. When Notepad opens, add the following lines:

  • @echo off
  • net stop wuauerv
  • cd% system root%
  • SoftwareSales SoftwareSales.old
  • net start wuauserv
  • Net stop bits
  • Net start bits
  • net stop cryptsvc
  • cd% systemroot% system32
  • ren catroot2.old
  • net start cryptsvc
  • regsvr32 Softpub.dll
  • regsvr32 Wintrust.dll
  • regsvr32 Mssip32.dll
  • regsvr32 Initpki.dll / s
  • echo reboot the computer
  • Shutdown.exe -r -t 00

3. Click File >> Save As.

4. Now set Save as type to All Files and set the file name to update.bat . Click Save to save the file.

5. Find the update.bat file that you just created, right-click it and select Run as administrator . After all commands have been executed, your PC restarts.

After restarting your PC, check if the problem is resolved.

Solution 8 – Start the sfc scan

If your Windows 10 installation is damaged, you may experience such problems on your PC. One way to fix these problems is to run sfc scan and have your PC scanned. This scan will fix any damaged Windows 10 components and hopefully fix the Diagnostics Troubleshooter that no longer works . To run sfc scan, do the following:

  1. Open Command Prompt as administrator. To do this, press Windows key + X to open the Win + X menu and select Command Prompt (Admin).
  2. When the prompt opens, type sfc/ scannow and press Enter.
  3. Wait while your computer is being scanned. If there are problems with your Windows 10 installation, they should be fixed automatically.

The Troubleshooting Wizard is an important part of Windows 10, and if you ‘ve got the Troubleshooting Assistant that stops working , be sure to try repairing the .NET Framework installation. If that does not work, you can try any other solution from this article.

Related Article: Learn how to resolve Blue Screen Of Death Error in Windows 10 quickly.





Axicon Auto Id Driver Download
Corechip USB Devices Driver Download For Windows 10

Comments are closed.