-
The error that occurs when prompting "Try to run C: Windows System32 ,NVSastartup" is because after the NVIDIA driver is installed, there are several startup items, and the startup item calls this file, but the file is gone, and it cannot be found. That's why I prompted this.
1: Delete the relevant nvidia startup items (steps: enter msconfig in the run--select start--check the box in front of the prompted file name--click OK to restart.) Note: There is a hint to tick the box after restarting).
2: If it still doesn't work, reinstall the driver.
This is the official website address, and my graphics card is nvidia like yours.
-
Uninstall the graphics card driver and install it again.
Or you can look for this file on another machine. Paste the two files in the C: Windows System32 directory and NVStaper over them.
-
Graphics card driver, it's best to find the original official driver of the graphics card, press setup to install it, give it a try, if it doesn't work, it may be a hardware problem with the graphics card.
-
Run ---msconfig--- start, and remove the relevant startup items from it.
-
Turn off the graphics card in the boot item, and you can turn it off in 360.
-
I've been in this situation too, and it's very unpleasant to watch! 、
-
It may be that you deleted something and deleted the system files, and you reinstalled it all over the system to see.
-
At a glance, you know that the boot device was not found.
There are several reasons for this:
1. The hard disk is not in good contact, including the data cable and power cable, or the motherboard hard disk interface is problematic.
2. The power supply of the hard disk is insufficient, and the hard disk does not start.
3. If the system is being installed and started from the optical drive, the optical drive does not have a system disk.
4. The system has been damaged, and it is very serious.
Please check the moderators one by one, I hope it can help the moderators.
-
Registry modification method: Enter "regedit" at "Start" "Run", in.
hkey current user software\Microsoft\Windows CurrentVersion\Run", the right window finds the residual program name to be deleted. Or open the registry, in Search, enter the wrong file name, delete the search, press the F3 key, search for the next one, until all of them are deleted.
Start Menu - Run - Enter msconfig Enter.
Put ** in the boot bar insideJust remove the tick in front of the dll.
1. Start - run - msconfig - start - remove the tick of the add-on ***dll. Restart the computer, usually this is the case, if it still pops up, then proceed to the second step.
2. Start-Run-regedit Delete the corresponding key in the following location: hkey current user software microsoft windows currentversion run hkey local machine software microsoft windows currentversion run
According to your description, it should be a virus or spyware that has been removed. But it's also possible that you didn't uninstall a piece of software incorrectly.
The dll is lost for some reason (most likely because it is a virus or rogue software dll file, which was deleted by the killer software), but its related registration information is still there, resulting in the system still loading it when booting up, but its file cannot be found, so the error is reported.
If you click "OK" and the system is not abnormal and can operate normally, you can use this software to clean up the boot add-on, and this message will not appear when you boot up in the future.
autoruns: startup item management.
Enter safe mode and open the hkey in the registry
Local Machine Software\Microsoft\Windows\CurrentVersion\Run\Restart after deleting the HBKRNL entries in it. >>>More
If you can't enter the system all the time, press the F8 key when trying to boot the computer and select the last correct configuration or safe mode. >>>More
The causes of such failures are generally complex, and may be a conflict between the system and the software, or a conflict between the software and the software, resulting in errors when the system runs some service programs, and it is difficult to find the source of the fault by detecting the root cause. So the easiest, most fundamental, quickest and most effective way is to reinstall the system. >>>More
When trying to open Device Manager in "System Properties" always prompts "MMC cannot open file C: Windows System32. This could be due to the file not existing, not an MMC console, or being created with a later version of MMC. >>>More
Did you move the registry?,360 recently has a registry** function,Be careful not to be blind.,Don't get it if you don't understand.,If you have to get it.,That's up to you.,Fortunately, this registry** app has the function of automatically backing up the registry before**,Please wait when you start,You just wait for a while,After entering the system,Enter 360 to find the registry**,Restore the last backup OK,I hope it can help you, My little brother's machine was like this some time ago.