CN104699554A - Software repairing method, device and system - Google Patents
Software repairing method, device and system Download PDFInfo
- Publication number
- CN104699554A CN104699554A CN201510142490.3A CN201510142490A CN104699554A CN 104699554 A CN104699554 A CN 104699554A CN 201510142490 A CN201510142490 A CN 201510142490A CN 104699554 A CN104699554 A CN 104699554A
- Authority
- CN
- China
- Prior art keywords
- software
- blue screen
- unstable
- repair
- unit
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 57
- 230000008439 repair process Effects 0.000 claims description 88
- 238000009434 installation Methods 0.000 claims description 10
- 230000008569 process Effects 0.000 description 13
- 230000006870 function Effects 0.000 description 4
- 230000015654 memory Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000002155 anti-virotic effect Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000009825 accumulation Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 230000008030 elimination Effects 0.000 description 1
- 238000003379 elimination reaction Methods 0.000 description 1
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a software repairing method, device and system. The method includes: acquiring a blue screen file; acquiring the analyzing result of the blue screen file; executing corresponding repairing when the analyzing result shows that blue screen is caused by software instability, wherein the repairing includes updating or uninstalling of the unstable software. By the method, blue screen repairing efficiency can be increased.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a software repair method, device and system.
Background
In the process of using a computer, a phenomenon that an operating system is subjected to kernel-level errors and then crashes is frequently encountered. For example, in the Windows operating system, this phenomenon is called Blue screen crash (BSOD), which refers to the Blue screen displayed when the Windows operating system crashes or stops executing (due to catastrophic errors or internal conditions preventing the system from continuing to run), essentially, Blue screen crash is a mechanism for the Windows operating system to process errors, and when the Windows kernel encounters an uncorrectable error, it is presented in the form of Blue screen crash, and gives possible reasons and suggestions of the error on the Blue screen user interface, which may stay on the display screen for a long time, or may restart the computer after a brief display, and the occurrence of Blue screen, which is generally a very serious error encountered by the Windows operating system, is also very serious, and is mostly caused by an error on third-party software or hardware, for example, in the aspect of third-party software, if two or more antivirus software are installed at the same time, the antivirus software can conflict with each other, and the control right of the bottom layer is seized, so that the system is halted by a blue screen; in terms of hardware, if two different memories are mixed and inserted, when a system reads data, due to different clock cycles, the data reading is in error, so that a blue screen crash occurs, and the like. When the blue screen crash occurs, the reason for the blue screen crash needs to be located and solved, so as to avoid the phenomenon that the blue screen crash is caused again due to the same reason.
The blue screen user interface information is typically in the form of a summary giving the cause of the problem, e.g., "error cause: a process accesses a memory that is not authorized to access at too high an interrupt request level, i.e., a program uses an incorrect memory address, but does not give which program uses the incorrect memory address. Therefore, although the blue screen user interface information can help to locate the reason causing the blue screen crash, the reason for the problem cannot be accurately found through the blue screen user interface information in most cases because the blue screen user interface information is too little. Therefore, for most people, even some professionals, the problem must eventually be found by the elimination method: the sequential uninstallation of each piece of software or reinstallation of the Windows system to determine whether the software is the result of the uninstallation is obviously time-consuming and labor-consuming, and the success rate is not high.
Disclosure of Invention
In view of the above, the present invention has been made to provide a software repair method and a corresponding blue screen repair apparatus and system that overcome or at least partially solve the above-mentioned problems.
According to an aspect of the present invention, there is provided a software repair method, including:
acquiring a blue screen file;
obtaining an analysis result for analyzing the blue screen file;
and when the analysis result shows that the reason of the blue screen is that the software is unstable, executing corresponding repair processing, wherein the repair processing comprises updating or uninstalling the unstable software.
Optionally, the updating unstable software includes:
downloading and installing a stable version of the software;
or,
alternate software is downloaded and installed.
Optionally, before installing the stable version of the software, the method further includes:
comparing the version number of the stable version to be installed with the version number of the current version of the unstable software;
if the version number of the stable version to be installed is lower than that of the current version, the unstable software is uninstalled.
Optionally, before installing the replacement software, the method further comprises:
judging whether the alternative software to be installed conflicts with unstable software;
if so, the unstable software is unloaded.
Optionally, the method further comprises:
if a blue screen file exists, but no uninstalled item of the unstable software exists, the user is prompted to temporarily fail to provide a fix solution.
Optionally, before executing the corresponding repair process, the method further includes:
displaying prompt information to a user so as to detect whether the client needs to execute corresponding repair processing;
and if an indication that the repair processing needs to be executed is received, triggering the execution of the corresponding repair processing.
Optionally, the method further comprises:
after the corresponding repair processing is completed, the user is prompted to perform an operation to restart the computer.
Optionally, the method further comprises:
after the corresponding repair process is completed, a return visit time option is displayed, and an operation entry for selecting the return visit time is provided.
Optionally, the method further comprises:
and prompting the user to upload the contact information under the condition that the problem cannot be solved.
Optionally, the obtaining an analysis result of analyzing the blue screen file includes:
uploading the blue screen file to a server so that the server can analyze the blue screen file according to the corresponding relation between the blue screen characteristic information and the blue screen reason stored in a database;
and obtaining an analysis result returned by the server.
According to another aspect of the present invention, there is provided a blue screen repairing apparatus including:
the blue screen file acquisition unit is used for acquiring a blue screen file;
the analysis result acquisition unit is used for acquiring an analysis result for analyzing the blue screen file;
and the repair execution unit is used for executing corresponding repair processing when the analysis result shows that the blue screen reason is that the software is unstable, wherein the repair processing comprises updating or uninstalling the unstable software.
Optionally, the repair execution unit includes:
a stable version installation subunit, configured to download and install a stable version of the software;
or,
and the alternative software installation subunit is used for downloading and installing alternative software.
Optionally, the method further comprises:
the version comparison unit is used for comparing the version number of the stable version to be installed with the version number of the current version of the unstable software before the stable version of the software is installed;
and the first uninstalling unit is used for uninstalling the unstable software if the version number of the stable version to be installed is lower than that of the current version.
Optionally, the method further comprises:
a conflict judging unit for judging whether the alternative software to be installed conflicts with unstable software before installing the alternative software;
and the second unloading unit is used for unloading the unstable software if the conflict exists.
Optionally, the method further comprises:
and the first prompting unit is used for prompting the user that the repair scheme cannot be provided temporarily if the blue screen file exists but the uninstalled item of the unstable software does not exist.
Optionally, the method further comprises:
the second prompting unit is used for displaying prompting information to a user before the corresponding repairing processing is executed so as to detect whether the client needs to execute the corresponding repairing processing;
and the trigger unit is used for triggering the execution of the corresponding repair processing if the indication that the repair processing needs to be executed is received.
Optionally, the method further comprises:
and the third prompting unit is used for prompting the user to execute the operation of restarting the computer after the corresponding repairing processing is finished.
Optionally, the method further comprises:
and the fourth prompting unit is used for displaying the return visit time option after the corresponding repairing treatment is finished and providing an operation entry for selecting the return visit time.
Optionally, the method further comprises:
and the fifth prompting unit is used for prompting the user to upload the contact information under the condition that the problem cannot be solved. .
Optionally, the analysis result obtaining unit includes:
the uploading subunit is used for uploading the blue screen file to a server so that the server can analyze the blue screen file according to the corresponding relation between the blue screen characteristic information and the blue screen reason stored in the database;
and the acquisition subunit is used for acquiring the analysis result returned by the server.
According to another aspect of the present invention, a software repair system is provided, which includes a client and a server, wherein the client includes:
a blue screen file obtaining unit for obtaining the blue screen file
The uploading unit is used for uploading the blue screen file to the server side;
the server side includes:
the analysis unit is used for analyzing the blue screen file according to the corresponding relation between the blue screen characteristic information and the blue screen reason stored in a preset database;
the return unit is used for returning an analysis result of analyzing the blue screen file to the client;
the client further comprises:
and the repair execution unit is used for executing corresponding repair processing when the analysis result shows that the blue screen reason is that the software is unstable, wherein the repair processing comprises updating or uninstalling the unstable software.
According to the software repairing method, device and system, after the analysis result is obtained according to the blue screen file, if the reason that the blue screen is unstable is found, unstable software can be updated or the unstable software can be directly uninstalled, so that the blue screen phenomenon caused by unstable software can be conveniently and effectively repaired, the problem of low blue screen repairing efficiency is solved, and the beneficial effect of improving the blue screen repairing efficiency is achieved.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 shows a flow diagram of a software repair method according to one embodiment of the invention;
FIG. 2 shows a schematic diagram of a software repair apparatus according to one embodiment of the invention; and
FIG. 3 shows a schematic diagram of a software repair system according to one embodiment of the invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Referring to fig. 1, a software repair method provided by an embodiment of the present invention may include the following steps:
s101: acquiring a blue screen file;
in order to facilitate the determination of the reason for the blue screen crash, the Windows operating system provides options of the DUMP mechanism, and through some settings in the Windows system, when the blue screen crash occurs in the system, the information when an error occurs is automatically stored in a disk file (i.e., a blue screen file, or referred to as a DUMP file). This facilitates locating the cause of the error later by analyzing the DUMP file. Furthermore, Microsoft also provides a debugging tool that can be used to analyze DUMP files: and (5) Windbg. Windbg provides a large number of commands by which information contained in the DUMP file, such as blue screen code, processes, threads, load modules, stacks, etc., may be explored, and by analyzing this information, it is possible to find the module that caused the blue screen. Also the widbg provides a simple command: | A analyze-v, by which some important information of the blue screen can be directly obtained.
In the embodiment of the present invention, the operating system needs to be configured to automatically generate a log file, for example, the aforementioned DUMP file or the like, in which system state information at the prompting time is recorded when the operating system generates a kernel-level error prompt. In a specific implementation, the function of generating the log file is generally carried out by the operating system, so that the log file can be implemented by only performing necessary settings. For example, it may be checked whether the system is set to automatically generate a log file when a kernel-level error prompt is issued, and if not, the setting may be performed by modifying a registry or the like. Therefore, when the system sends out kernel-level error prompt, the log file recorded with the system state information at the prompt moment can be automatically generated, and the premise is provided for subsequent error source positioning.
Specifically, when uploading a blue screen file, the following rules may be followed: firstly, uploading the latest 5 Dump (if less than 5, uploading the number) files within 3 months; secondly, the uploaded Dump file is: files smaller than a specified size, e.g., 300KB, and with an extension of. dmp; thirdly, if the execution of the whole repair process is finished (a blue screen problem is repaired by using a repair scheme), recording the Dump file in a% appdata% directory, and not uploading the Dump file again in the next analysis; fourth, if there is a Dump file to be uploaded in the background, the user interface finishes the uploading process, but actually does not upload the Dump file any more. If the uploading fails, prompting an uploading failure page, and providing a retry entrance so that the user can retry and upload again; if the dump file is not locally available, prompting that the blue screen information storage file is not detected, and simultaneously opening a dump file saving switch.
Where "% appdata" is an environment variable, which is an object with a specific name that contains information to be used by one or more applications. For example, a path, when the system is required to run a program without telling it the complete path the program is in, the system will find the program under the current directory and find the path specified in the path. The user can better run the process by setting the environment variables. For example, using a location defined by an environment variable, an application can query the environment variable list according to the name in "%", and then find the predefined location, and further find the needed file therefrom.
After the blue screen file is uploaded to the server, the blue screen file can be analyzed on the server side. Specifically, in the log file, a type code is generally provided for the current error type, and such error code is automatically generated by the system, for example, 0x7f, and so on. The error corresponding to each code can be analyzed from the information, and the information can be obtained through experience accumulation. That is, for a person with sufficient experience, after knowing the error type code, it can know which information should be extracted from the log file, and further analyze on which module the error occurred. Therefore, in the embodiment of the present invention, in order to automatically complete the analysis of the log file through the program, the error types represented by each type of code may be analyzed in advance, the error location related information that needs to be extracted under each type is analyzed, and the relationship between each type of code and the error location related information that needs to be obtained is recorded. For example, for the error type of code 0x7f, it is found through a large number of empirical analysis summaries that the error is mostly caused by stack overflow due to too many stacks occupied by a certain driver. Therefore, if the occupation situation of the stack by each driver at the moment of blue screen can be extracted from the log file, the module which causes the blue screen at this time may be the module which occupies the most stack. Therefore, for the error type corresponding to the code, the error positioning related information that needs to be obtained may be the occupation situation of each driver on the stack. And performing similar processing on other codes respectively, so that a list of the corresponding relation between the type code with the error and the error positioning related information needing to be extracted can be obtained for subsequent query.
Meanwhile, the corresponding relation between the modules and the software or hardware can be obtained in advance according to empirical analysis, the corresponding relation between each module and the corresponding software or hardware is stored, and a database is formed.
Certainly, in practical application, the related operations of analyzing the blue screen file can also be directly performed at the client, and therefore, a required database can be stored at the client and updated in real time, so that the blue screen file does not need to be uploaded to a server, and network transmission and other expenses are saved.
S102: obtaining an analysis result for analyzing the blue screen file;
if the blue screen file is uploaded to the server, the analysis result can be returned to the client after the server analyzes the uploaded blue screen file, so that the client can obtain the analysis result of the server. If the blue screen file is analyzed locally at the client, the analysis result can be obtained after the analysis is finished.
S103: and when the analysis result shows that the reason of the blue screen is that the software is unstable, executing corresponding repair processing, wherein the repair processing comprises updating or uninstalling the unstable software.
In the analysis result given by the server, not only can the reason of the blue screen be displayed because the software is unstable, but also which software is or is unstable can be displayed. At this time, the corresponding repair processing scheme may be to update or directly uninstall unstable software, and both the purpose of repair may be achieved. When updating the software, a stable version can be selected from other versions of the same software for updating, or other software with similar functions can be selected for replacing. The software manager is a platform for downloading and installing software and managing software in a one-stop mode, generally has the latest and most complete software database, and information such as functions, stability and the like of various types of software and various versions of the software can be collected and stored in the database, so that when the stable version or the alternative software needs to be selected, the information such as the name, the version and the like of the existing software can be sent to the software manager, and the software manager can search the stable version or the alternative software from the database and return the stable version or the alternative software to a computer clinic. Of course, the computer clinic can also pre-establish its own software database and directly query in the database. In summary, there are three specific repair methods: a stable version of the software is downloaded and installed, or a replacement software is downloaded and installed, or unstable software is directly uninstalled.
In specific implementation, any one of the three modes can be automatically selected to perform blue screen repair for the user, or the user's opinion can be solicited first, and after the user accepts a certain mode, specific repair operation is performed. For example, the user interface may first be prompted with the following text "maybe due to certain problems with the XXX software itself, running in some specific circumstances causing a blue screen crash, suggesting that the software be updated or uninstalled, clicking 'next' to start repairing the blue screen problem", and after the user clicks 'next', the user is provided with the three options. The three options are in a radio mode, the repair content of the option is expanded after clicking, the previous step can be clicked at the moment, the analysis result page is returned after clicking, the content area of the option cannot be clicked, and only a radio button can be clicked. The text prompt on the user interface may include the following "you can try to fix the blue screen problem due to XXX" after the first radio box, "install stable version" is displayed, and an explanation for this option "install stable version of the software by computer clinic" is also displayed below. Generally, the method can solve the problem of blue screen caused by software; after the second radio box, "choose to replace software" is displayed, and similarly, explanation for this option "blue screen can be avoided by replacing software, and the computer clinic prepares a software of the same kind as the software for you and can try to install and use" can be displayed; the third radio box may then show "uninstall the software", explained below as "if this software is not the software that you often use, or that you install, suggest you uninstall to solve the blue screen problem".
When the button of 'install stable version' is clicked, the option is expanded to provide the software to be installed, and the icon, the software name, the software version, the software size and the 'download and install' button of the software to be installed can be displayed in the user interface. After clicking the 'download and install' button, executing the download and install operation, firstly establishing a connection, wherein the progress bar is 0, and at the moment, if the point 'ends', returning to the initial state. And displaying the download percentage and the download speed in the download process. And after downloading, calling out the installation program by default, displaying that the installation program is installed by the user interface, if the user closes the installation program but the software is not installed completely, displaying a button 'installation' by the user interface, and executing downloading and installation operation after clicking (if the software is downloaded, directly executing the installation operation and calling out the installation program). After installation, the user interface displays "install complete", at which point "next step" may be clicked.
It should be noted that, for different versions of the same software, if the low version is already installed on the computer, the overlay installation can be directly performed when the high version is newly installed, that is, the uninstalling operation does not need to be performed on the low version; however, if the high version is already installed on the computer, the manner of overriding the installation may be ineffective when the low version is newly installed. Therefore, before installing the stable version, it may also be detected by the software manager first, and if the local version is detected to be higher than the version to be installed when installing the stable version, the local version is unloaded by pop-up prompting on the user interface, and the flow is as follows: firstly, a popup prompts that the version to be installed is detected to be lower than the existing version, the coverage installation is possibly invalid, the existing version is requested to be uninstalled firstly and then installed, meanwhile, an 'immediate uninstall' button is displayed, and the uninstall process of the software is executed if the 'immediate uninstall' is clicked, wherein the process comprises the following steps: firstly, unloading information is analyzed, an unloading program is popped up, unloading XXX is displayed on a user interface, if the user closes the unloading program, the user returns to the user interface of 'immediate unloading', powerful unloading is not provided in the unloading process, standard unloading is only needed, after the unloading is finished, the user clicks to continue repairing the blue screen problem, then the user interface of installing the stable version is returned, and the stable version starts to be downloaded.
When the button for selecting the alternative software is clicked, the option is expanded to provide the alternative software, and the user interface displays a software icon, a software name, a software version, a software size, a software profile, and a "download and install" button. And at the moment, the other two single options can be clicked, corresponding repair contents are displayed after clicking, and after clicking 'downloading and installing', downloading and installing operation is executed.
It should be noted here that in this case of installing the alternative software, which is two different pieces of software from the existing software, if the two pieces of software exist at the same time, a conflict may occur. Therefore, before downloading or installing the alternative software, it can be determined whether there is a conflict between the two pieces of software (or by means of a software database of a "software manager" or the like tool), and if so, the existing software is first uninstalled and then the alternative software is installed. Or, according to the background configuration, if the software to be replaced conflicts with the software causing the blue screen, the software causing the blue screen may be unloaded in a popup prompt manner, specifically, the prompt information may be "detect that XXX is not unloaded, in order to achieve a better repairing effect, it is recommended to install the replacement software after uninstalling XXX", and "uninstall immediately" button, and the uninstalling process is consistent with that of the uninstalling high version, which is not described herein again.
When the button of 'uninstalling the software' is clicked, the option is expanded, the software to be uninstalled is displayed, the user interface displays a software icon and a software name, the other two single options can also be clicked at the moment, the corresponding repair content is displayed after clicking, and 'uninstalling immediately' is clicked, a software uninstalling program is called, the operation of uninstalling the software is executed, and if the software is green software and the uninstalling item is not available, the drive is forbidden. The flow of clicking "unload immediately" is as follows: firstly, an unloading item of the software is searched, a user interface displays a progress bar and unloading information under analysis, if residual items exist, powerful cleaning is provided, and after the unloading is finished, the user interface displays that the unloading is finished.
And after the repair is finished, the user needs to restart the computer to check the repair effect, so that the restart can be prompted after the repair is finished, a plan task can be created during the restart, the return visit is performed after 3 days as a default, the user can select one week or one month later, the calculation is performed according to 30 days in one month, meanwhile, if the user enters the page, the fact that the dump file is analyzed is recorded, and of course, if the user selects that the return visit is not required, the creation of the plan task is not performed. In specific implementation, the following text contents can be displayed on the user interface: "blue Screen repair is completed! The repairing effect needs to be checked by restarting your computer; please save the document opened on your computer, close other running programs, and then click the button below to restart your computer. Whether the problem that observation is needed for a period of time is solved or not is judged after the blue screen is repaired, so that a user can visit the user after the user restarts the blue screen for a period of time, the visiting time can be selected according to the requirement, and meanwhile, the following options are given in a radio box mode: three days, one week, one month and no need for revisit.
If the analysis is the result of software instability, but no uninstalled item for the software is found, and a blue screen file exists, the user may be prompted to temporarily fail to provide a fix solution. If the analysis is caused by unstable software but the blue screen file does not exist, the user is prompted to ' detect no file causing the blue screen and do not need to repair ', ' the analyzed blue screen of the computer is caused by XXX, but the software is possibly updated or uninstalled and the blue screen file does not exist, so that the computer does not need to repair the blue screen any more. You can try to repair the next blue screen by computer outpatient service.
In addition, if the blue screen problem is not solved after the repair is carried out in the prompting mode, the user can submit the contact information and the engineer can contact the contact information to upload the contact information. Displaying on a user interface: "regret! The computer outpatient service fails to help you solve the blue screen problem, you can leave your contact information, the computer outpatient service submits your contact information and the blue screen repair record to an engineer, the engineer contacts you to further analyze the reason of the blue screen, and the user contact information comprises: and a button of ' submit blue screen repair information ', and when the button is clicked, the user interface displays ' your blue screen repair information is being submitted ', and if the submission fails, the user interface displays ' submit failure! Please check your network connection, "failure to submit is usually caused by network failure or server busy, and click 'retry' to try to re-submit after checking your network connection. If the submission was successful, the user interface displays "your blue screen repair information was successfully submitted! The engineer contacts you for analysis of the blue screen reason as soon as possible ".
Corresponding to the software repair method provided by the embodiment of the present invention, the embodiment of the present invention further provides a software repair apparatus, referring to fig. 2, the apparatus including:
a blue screen file obtaining unit 201, configured to obtain a blue screen file;
an analysis result acquisition unit 202 configured to acquire an analysis result of analyzing the blue screen file;
and the repair execution unit 203 is configured to execute corresponding repair processing when the analysis result shows that the blue screen reason is that the software is unstable, where the repair processing includes updating or uninstalling the unstable software.
The repair execution unit 203 includes:
a stable version installation subunit, configured to download and install a stable version of the software;
or,
and the alternative software installation subunit is used for downloading and installing alternative software.
In a specific implementation, the apparatus may further include:
the version comparison unit is used for comparing the version number of the stable version to be installed with the version number of the current version of the unstable software before the stable version of the software is installed;
and the first uninstalling unit is used for uninstalling the unstable software if the version number of the stable version to be installed is lower than that of the current version.
A conflict judging unit for judging whether the alternative software to be installed conflicts with unstable software before installing the alternative software;
and the second unloading unit is used for unloading the unstable software if the conflict exists.
And the first prompting unit is used for prompting the user that the repair scheme cannot be provided temporarily if the blue screen file exists but the uninstalled item of the unstable software does not exist.
The second prompting unit is used for displaying prompting information before the corresponding repairing processing is executed so as to detect whether the client needs to execute the corresponding repairing processing;
and the trigger unit is used for triggering the execution of the corresponding repair processing if the indication that the repair processing needs to be executed is received.
And the third prompting unit is used for prompting the execution of the operation of restarting the computer after the corresponding repairing processing is finished.
And the fourth prompting unit is used for displaying the return visit time option after the corresponding repairing treatment is finished and providing an operation entry for selecting the return visit time.
And the fifth prompting unit is used for prompting that the contact information is uploaded under the condition that the problem cannot be solved.
In a specific implementation, the analysis result obtaining unit 202 may specifically include:
the uploading subunit is used for uploading the blue screen file to a server so that the server can analyze the blue screen file according to the corresponding relation between the blue screen characteristic information and the blue screen reason stored in the database;
and the acquisition subunit is used for acquiring the analysis result returned by the server.
Corresponding to the foregoing software repair apparatus, an embodiment of the present invention further provides a software repair system, and referring to fig. 3, the system may include a client 301 and a server 302, where the client 301 may include:
a blue screen file obtaining unit 3011, configured to obtain a blue screen file
An uploading unit 3012, configured to upload the blue screen file to the server;
the server 302 includes:
an analysis unit 3021, configured to analyze the blue screen file according to a correspondence between blue screen feature information and a blue screen reason stored in a preset database;
a returning unit 3022, configured to return an analysis result obtained by analyzing the blue screen file to the client;
the client 301 further includes:
and the repair execution unit 3013 is configured to, when the analysis result shows that the blue screen reason is that the software is unstable, execute corresponding repair processing, where the repair processing includes updating or uninstalling the unstable software.
In summary, according to the software repair device and system provided by the embodiment of the invention, after the analysis result is obtained according to the blue screen file, if the reason that the blue screen is unstable is found, unstable software can be updated, or unstable software can be directly uninstalled, so that the blue screen phenomenon caused by unstable software can be conveniently and effectively repaired.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It will be appreciated by those skilled in the art that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components in a blue screen repair device according to embodiments of the present invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
Claims (21)
1. A software repair method, comprising:
acquiring a blue screen file;
obtaining an analysis result for analyzing the blue screen file;
and when the analysis result shows that the reason of the blue screen is that the software is unstable, executing corresponding repair processing, wherein the repair processing comprises updating or uninstalling the unstable software.
2. The method of claim 1, the updating unstable software comprising:
downloading and installing a stable version of the software;
or,
alternate software is downloaded and installed.
3. The method of claim 2, further comprising, prior to installing the stable version of the software:
comparing the version number of the stable version to be installed with the version number of the current version of the unstable software;
if the version number of the stable version to be installed is lower than that of the current version, the unstable software is uninstalled.
4. The method of claim 2, further comprising, prior to installing the replacement software:
judging whether the alternative software to be installed conflicts with unstable software;
if so, the unstable software is unloaded.
5. The method of claim 1, further comprising:
if a blue screen file exists, but no uninstalled item of the unstable software exists, the user is prompted to temporarily fail to provide a fix solution.
6. The method of any of claims 1 to 5, further comprising, prior to performing the corresponding repair process:
displaying prompt information to a user so as to detect whether the client needs to execute corresponding repair processing;
and if an indication that the repair processing needs to be executed is received, triggering the execution of the corresponding repair processing.
7. The method of any of claims 1 to 5, further comprising:
after the corresponding repair processing is completed, the user is prompted to perform an operation to restart the computer.
8. The method of any of claims 1 to 5, further comprising:
after the corresponding repair process is completed, a return visit time option is displayed, and an operation entry for selecting the return visit time is provided.
9. The method of any of claims 1 to 5, further comprising:
and prompting the user to upload the contact information under the condition that the problem cannot be solved.
10. The method of any one of claims 1 to 5, wherein the obtaining of the analysis result of the analysis of the blue screen file comprises:
uploading the blue screen file to a server so that the server can analyze the blue screen file according to the corresponding relation between the blue screen characteristic information and the blue screen reason stored in a database;
and obtaining an analysis result returned by the server.
11. A software repair apparatus comprising:
the blue screen file acquisition unit is used for acquiring a blue screen file;
the analysis result acquisition unit is used for acquiring an analysis result for analyzing the blue screen file;
and the repair execution unit is used for executing corresponding repair processing when the analysis result shows that the blue screen reason is that the software is unstable, wherein the repair processing comprises updating or uninstalling the unstable software.
12. The apparatus of claim 11, the repair execution unit comprising:
a stable version installation subunit, configured to download and install a stable version of the software;
or,
and the alternative software installation subunit is used for downloading and installing alternative software.
13. The apparatus of claim 12, further comprising:
the version comparison unit is used for comparing the version number of the stable version to be installed with the version number of the current version of the unstable software before the stable version of the software is installed;
and the first uninstalling unit is used for uninstalling the unstable software if the version number of the stable version to be installed is lower than that of the current version.
14. The apparatus of claim 12, further comprising:
a conflict judging unit for judging whether the alternative software to be installed conflicts with unstable software before installing the alternative software;
and the second unloading unit is used for unloading the unstable software if the conflict exists.
15. The apparatus of claim 11, further comprising:
and the first prompting unit is used for prompting the user that the repair scheme cannot be provided temporarily if the blue screen file exists but the uninstalled item of the unstable software does not exist.
16. The apparatus of any of claims 11 to 15, further comprising:
the second prompting unit is used for displaying prompting information to a user before the corresponding repairing processing is executed so as to detect whether the client needs to execute the corresponding repairing processing;
and the trigger unit is used for triggering the execution of the corresponding repair processing if the indication that the repair processing needs to be executed is received.
17. The apparatus of any of claims 11 to 15, further comprising:
and the third prompting unit is used for prompting the user to execute the operation of restarting the computer after the corresponding repairing processing is finished.
18. The apparatus of any one of claims 11 to 15, further comprising:
and the fourth prompting unit is used for displaying the return visit time option after the corresponding repairing treatment is finished and providing an operation entry for selecting the return visit time.
19. The apparatus of any of claims 11 to 15, further comprising:
and the fifth prompting unit is used for prompting the user to upload the contact information under the condition that the problem cannot be solved.
20. The apparatus according to any one of claims 11 to 15, the analysis result acquisition unit comprising:
the uploading subunit is used for uploading the blue screen file to a server so that the server can analyze the blue screen file according to the corresponding relation between the blue screen characteristic information and the blue screen reason stored in the database;
and the acquisition subunit is used for acquiring the analysis result returned by the server.
21. A software repair system comprises a client and a server, wherein the client comprises:
a blue screen file obtaining unit for obtaining the blue screen file
The uploading unit is used for uploading the blue screen file to the server side;
the server side includes:
the analysis unit is used for analyzing the blue screen file according to the corresponding relation between the blue screen characteristic information and the blue screen reason stored in a preset database;
the return unit is used for returning an analysis result of analyzing the blue screen file to the client;
the client further comprises:
and the repair execution unit is used for executing corresponding repair processing when the analysis result shows that the blue screen reason is that the software is unstable, wherein the repair processing comprises updating or uninstalling the unstable software.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510142490.3A CN104699554B (en) | 2012-08-22 | 2012-08-22 | Software repair, apparatus and system |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510142490.3A CN104699554B (en) | 2012-08-22 | 2012-08-22 | Software repair, apparatus and system |
| CN201210300884.3A CN102855160B (en) | 2012-08-22 | 2012-08-22 | Method, device and system for software repair |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210300884.3A Division CN102855160B (en) | 2012-08-22 | 2012-08-22 | Method, device and system for software repair |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104699554A true CN104699554A (en) | 2015-06-10 |
| CN104699554B CN104699554B (en) | 2018-07-03 |
Family
ID=53346715
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510142490.3A Active CN104699554B (en) | 2012-08-22 | 2012-08-22 | Software repair, apparatus and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104699554B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106790895A (en) * | 2015-11-25 | 2017-05-31 | 北京搜狗科技发展有限公司 | A kind of fault handling method and device |
| CN107656854A (en) * | 2016-07-26 | 2018-02-02 | 佛山市顺德区顺达电脑厂有限公司 | The method for exporting the hardware check exceptional information of computer system |
| WO2018082176A1 (en) * | 2016-11-03 | 2018-05-11 | 华为技术有限公司 | Method for processing fault of terminal device, and terminal device |
| CN109697145A (en) * | 2018-12-19 | 2019-04-30 | 国云科技股份有限公司 | A method of automatically analyzing cloud desktop blue screen |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101286874A (en) * | 2008-03-05 | 2008-10-15 | 中科院嘉兴中心微系统所分中心 | Version updating method for program of nodes in sensor network |
| CN101533365A (en) * | 2009-04-16 | 2009-09-16 | 唐郡 | Computer system, maintenance method and device thereof |
| CN101944059A (en) * | 2010-08-20 | 2011-01-12 | 北京神州泰岳软件股份有限公司 | Automatic analysis method and device of crash information of computer software |
| US20120137180A1 (en) * | 2010-11-29 | 2012-05-31 | Hon Hai Precision Industry Co., Ltd. | Computing device and system error detection method |
| CN102637144A (en) * | 2012-03-31 | 2012-08-15 | 奇智软件（北京）有限公司 | System fault processing method and device |
-
2012
- 2012-08-22 CN CN201510142490.3A patent/CN104699554B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101286874A (en) * | 2008-03-05 | 2008-10-15 | 中科院嘉兴中心微系统所分中心 | Version updating method for program of nodes in sensor network |
| CN101533365A (en) * | 2009-04-16 | 2009-09-16 | 唐郡 | Computer system, maintenance method and device thereof |
| CN101944059A (en) * | 2010-08-20 | 2011-01-12 | 北京神州泰岳软件股份有限公司 | Automatic analysis method and device of crash information of computer software |
| US20120137180A1 (en) * | 2010-11-29 | 2012-05-31 | Hon Hai Precision Industry Co., Ltd. | Computing device and system error detection method |
| CN102637144A (en) * | 2012-03-31 | 2012-08-15 | 奇智软件（北京）有限公司 | System fault processing method and device |
Non-Patent Citations (1)
| Title |
|---|
| 王伟: "计算机蓝屏故障分析与处理研究", 《电脑知识与技术》 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106790895A (en) * | 2015-11-25 | 2017-05-31 | 北京搜狗科技发展有限公司 | A kind of fault handling method and device |
| CN106790895B (en) * | 2015-11-25 | 2020-07-24 | 北京搜狗科技发展有限公司 | Fault processing method and device |
| CN107656854A (en) * | 2016-07-26 | 2018-02-02 | 佛山市顺德区顺达电脑厂有限公司 | The method for exporting the hardware check exceptional information of computer system |
| WO2018082176A1 (en) * | 2016-11-03 | 2018-05-11 | 华为技术有限公司 | Method for processing fault of terminal device, and terminal device |
| CN108604200A (en) * | 2016-11-03 | 2018-09-28 | 华为技术有限公司 | The method and terminal device of the failure of processing terminal equipment |
| CN109697145A (en) * | 2018-12-19 | 2019-04-30 | 国云科技股份有限公司 | A method of automatically analyzing cloud desktop blue screen |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104699554B (en) | 2018-07-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102855160B (en) | Method, device and system for software repair | |
| CN102866930B (en) | Blue screen restorative procedure, Apparatus and system | |
| US7962788B2 (en) | Automated treatment of system and application validation failures | |
| CN104156244B (en) | A kind of method and apparatus of software upgrading | |
| US6543047B1 (en) | Method and apparatus for testing custom-configured software/hardware integration in a computer build-to-order manufacturing process | |
| US7237238B2 (en) | Method and apparatus for automated operating systems upgrade | |
| US8954930B2 (en) | System and method for reducing test effort by object risk analysis | |
| US8489922B2 (en) | Networked recovery system | |
| US20110296398A1 (en) | Systems and methods for determining when to update a package manager software | |
| US7519630B2 (en) | Method and system for automated testing of versioned information handling system applications | |
| CN102768639B (en) | Operating system kernel-level error positioning method and device | |
| CN106802814B (en) | Method and device for upgrading software version | |
| US20070074168A1 (en) | Automated step type determination | |
| US20140068325A1 (en) | Test case result processing | |
| CN104699554B (en) | Software repair, apparatus and system | |
| US20070169114A1 (en) | Application suite installer with automatic detection of content and configurable options | |
| CN108121650B (en) | Method and device for testing page user interface | |
| US9405664B2 (en) | Automating software testing | |
| CN103064767B (en) | Drive backup, the method recovered and device | |
| US9122687B2 (en) | Crash recovery for attended operating system installations | |
| CN113411225B (en) | QGA service management method, device, equipment and medium based on cloud host | |
| CN113377586B (en) | Automatic detection method and device for server and storage medium | |
| US9477447B1 (en) | Semantic representations of software extensions | |
| US20240320082A1 (en) | Systems and methods for pause-correct-replay workflow customization | |
| US20230088318A1 (en) | Remotely healing crashed processes |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220714 Address after: Room 801, 8th floor, No. 104, floors 1-19, building 2, yard 6, Jiuxianqiao Road, Chaoyang District, Beijing 100015 Patentee after: BEIJING QIHOO TECHNOLOGY Co.,Ltd. Address before: 100088 room 112, block D, 28 new street, new street, Xicheng District, Beijing (Desheng Park) Patentee before: BEIJING QIHOO TECHNOLOGY Co.,Ltd. Patentee before: Qizhi software (Beijing) Co.,Ltd. |