Win10 mining cannot write DAG
Publish: 2021-05-17 15:03:27
1. On the basis of motherboard, 6 cards can be mined by PCI-E X1 extension adapter
up to 7 cards can be mined by expansion card.
up to 7 cards can be mined by expansion card.
2. can be said to
3. Currency exchange is a powerful blockchain platform in China. At present, the relatively large domestic exchange is OK huo'an exchange.
4. There are a few that can't be bought, such as the wave ring, to be won in the fishing competition. You see, the boatman treasure interface shows the way to get the location
5.
-
generally, high-end and high-performance graphics cards are needed for mining, and mining consumes the performance of graphics cards
-
it is recommended to replace or check the driver version of the graphics card to see if it is the same. If it is still the same, it is recommended to re install the system and use the latest version of win10
6. Encountered such a problem, is the reason for the authority. For example, the delivery place or shipping point set by the authority should not be limited to its location.
7. First of all, this paper summarizes the causes of such problems as "application failed to start e to incorrect application configuration":
after Windows XP SP2, windows introced the concept of side by side execution, which was originally proposed by. Net, but later windows integrated this concept into the operating system. We should all know the problem of DLL hell. In order to solve the problem of DLL hell, side by side proposes that different versions of DLL files can exist in the same system at the same time, and applications that depend on different versions of DLL can use the originally compiled DLL when they run. For example:
1. Suppose you write a C + + program a, which uses MFC 8.0 (this version is released with Visual Studio 2005)
2. Later, the machine upgraded the version of visual studio, and the MFC library upgraded from 2005 to 2008 was version 9.0. At this time, two versions of MFC, 8.0 and 9.0, were installed in the operating system
3. Write another C + + program B with Visual Studio 2008, which depends on MFC 9.0
4. If you run program a, the operating system will load MFC 8.0 into the process of A
5. If program B is running at the same time, the operating system will load MFC 9.0 into the process of B. This is the concept of side by side execution
the reason why the operating system can do this is that before loading programs a and B, it will view the manifest files of a and B in addition to the DLL information that a and B depend on in PE format. The manifest file stores the environment setting information of windows executable files (including exe and DLL files) to run. The file name is usually the full name of the executable file plus. Manifest. For example, the manifest file of notepad.exe should be notepad.exe.manifest. In addition, some programs embed the manifest file directly into the resources of the executable file, which is why sometimes you can't see the manifest file of the program. Generally speaking, the content of a manifest file is as follows:
& lt;? xml version=' 1.0' encoding=' UTF-8' standalone=' yes'?& gt;< br />< assembly xmlns=' urn:schemas-microsoft-com :asm.v1' manifestVersion=' 1.0'& gt;< br />< trustInfo xmlns=" urn:schemas-microsoft-com :asm.v3"& gt;< br />< security>< br />< requestedPrivileges>< br />< requestedExecutionLevel level=' asInvoker' uiAccess=' false' /& gt;< br /></ requestedPrivileges>< br /></ security>< br /></ trustInfo>< br />< dependency>< br />< dependentAssembly>< br />< assemblyIdentity type=' win32' name=' Microsoft.VC90.DebugCRT' version=' 9.0.21022.8'< br />processorArchitecture=' x86' publicKeyToken=' 1fc8b3b9a1e18e3b' /& gt;< br /></ dependentAssembly>< br /></ dependency>< br /></ assembly>
in the above example, it shows that this program depends on CRT 9.0 and is a debug version. The CPU architecture is a 32-bit CPU. For programs that embed manifest files into resource files, there is also a way to see manifest information
1. One is to use mt.exe (manifest handler of Visual Studio):
MT - input tresource:test.exe;# 1 / out:test.manifest
2. Another method is to use mpbin program to print the contents of the entire exe to a file, then open it with a text editor, and search assem string style to find the manifest information
after Windows XP SP2, windows introced the concept of side by side execution, which was originally proposed by. Net, but later windows integrated this concept into the operating system. We should all know the problem of DLL hell. In order to solve the problem of DLL hell, side by side proposes that different versions of DLL files can exist in the same system at the same time, and applications that depend on different versions of DLL can use the originally compiled DLL when they run. For example:
1. Suppose you write a C + + program a, which uses MFC 8.0 (this version is released with Visual Studio 2005)
2. Later, the machine upgraded the version of visual studio, and the MFC library upgraded from 2005 to 2008 was version 9.0. At this time, two versions of MFC, 8.0 and 9.0, were installed in the operating system
3. Write another C + + program B with Visual Studio 2008, which depends on MFC 9.0
4. If you run program a, the operating system will load MFC 8.0 into the process of A
5. If program B is running at the same time, the operating system will load MFC 9.0 into the process of B. This is the concept of side by side execution
the reason why the operating system can do this is that before loading programs a and B, it will view the manifest files of a and B in addition to the DLL information that a and B depend on in PE format. The manifest file stores the environment setting information of windows executable files (including exe and DLL files) to run. The file name is usually the full name of the executable file plus. Manifest. For example, the manifest file of notepad.exe should be notepad.exe.manifest. In addition, some programs embed the manifest file directly into the resources of the executable file, which is why sometimes you can't see the manifest file of the program. Generally speaking, the content of a manifest file is as follows:
& lt;? xml version=' 1.0' encoding=' UTF-8' standalone=' yes'?& gt;< br />< assembly xmlns=' urn:schemas-microsoft-com :asm.v1' manifestVersion=' 1.0'& gt;< br />< trustInfo xmlns=" urn:schemas-microsoft-com :asm.v3"& gt;< br />< security>< br />< requestedPrivileges>< br />< requestedExecutionLevel level=' asInvoker' uiAccess=' false' /& gt;< br /></ requestedPrivileges>< br /></ security>< br /></ trustInfo>< br />< dependency>< br />< dependentAssembly>< br />< assemblyIdentity type=' win32' name=' Microsoft.VC90.DebugCRT' version=' 9.0.21022.8'< br />processorArchitecture=' x86' publicKeyToken=' 1fc8b3b9a1e18e3b' /& gt;< br /></ dependentAssembly>< br /></ dependency>< br /></ assembly>
in the above example, it shows that this program depends on CRT 9.0 and is a debug version. The CPU architecture is a 32-bit CPU. For programs that embed manifest files into resource files, there is also a way to see manifest information
1. One is to use mt.exe (manifest handler of Visual Studio):
MT - input tresource:test.exe;# 1 / out:test.manifest
2. Another method is to use mpbin program to print the contents of the entire exe to a file, then open it with a text editor, and search assem string style to find the manifest information
8. Because win10 system makes more full use of graphics card than other systems.
Hot content