A program to determine the cause of a blue screen. BlueScreenView: how to use to determine the cause of BSOD. Loading MemTest from a flash drive

Attention! The article describes methods that require some preparedness and experience of the user.

In this article there will be no “smart” words; we will try to explain unclear words right away. The article will provide general recommendations for eliminating the “blue screen of death” specifically for beginners. For all programs used, there will (if possible) be links to download files or pages from which you can download them.

Blue screen of death, also known as BSOD, also known as bluescreen. What to do?

A lot has already been written about the so-called blue screens of death. Advanced users personal computers with operating system Windows family, have long learned to study them, and quite successfully determine the cause of their appearance.

The problem for novice users is that they are terrified of blue screens. Of course, such a screen can cause a lot of trouble. But seven troubles - one answer: a “programmer” comes in who got a bad mark in English at school, and the Unified State Exam is just around the corner and reinstalls the system. And 20 minutes after he leaves, you are very disappointed - the unfortunate error pops up again.

But what to do then, because on most forums and websites, everything is written in technical language. Once you ask a clarifying question, you are sent to the “sandbox” - a section of a website or forum for beginners. Good advice. Such sections usually contain information that will allow you to study basic concepts and terms. But all this takes time, and you obviously won’t do this if you, for example, have a small child. What can you advise in this case?

  • Take your computer (laptop) to a service center. This is the most preferred option.
  • Try to fix the BSOD without outside help. This is also a good option, but it requires you to have basic concepts and skills, at least such as entering the website address directly in the address bar without Google help or Yandex.

If you understand what is meant in the second paragraph, we can get started.

Standard testing methods.

Let's assume that your operating system still boots normally and the BSOD error appears some time after startup. Let's try to use standard methods of checking a computer before it appears.

1. Checking the temperature of computer components

It happens that novice users do not even know about the need to clean their computer. If they do, it comes down to regular vacuuming.

Cleaning your computer involves a whole range of activities. This includes cleaning the computer from dust inside the case, cleaning radiators (dust is compressed in its fins), also cleaning and lubricating fans, replacing thermal paste between radiators and microcircuits. So vacuuming is quite ineffective.

Let's check the temperature of your computer components. To do this, it is advisable to use some specialized program. We will use one of the most popular programs - AIDA64. It's paid. But effective. Immediately a warning: ways to free receipt and so on. you won't find it.

So let's launch the program. On the left side of the window select "Computer" then "Sensors" and look.

We warn you right away. Meaning "PCH Diode" very often shows high temperature. Somewhere on the forum, developers AIDA64 confirmed that this is exactly the case on many boards. This screenshot was no exception. The actual temperature of all components of our PC does not exceed 34 degrees.

In general, opinions about what temperature is considered normal vary. But nevertheless, we will proceed from the fact that the normal operating temperature CPU- 30-50 degrees. Anything higher will be considered overheating. For video card ( GPU), normal temperature Let's consider 60-65 degrees. I would like to clarify that these figures are taken from personal experience and the norm varies from processor to processor, from video card to video card. For a motherboard, the “tolerable” norm is 40-45, but for some motherboards the norm may be 50.

If the numbers are an order of magnitude higher than those given, the “patient’s” temperature needs to be “brought down.” It is possible that overheating is the cause of the blue screen. If this is left to chance, the computer may begin to turn off spontaneously - the protection will be triggered. If for some reason it does not work, or your motherboard poor quality, then the consequences can be disastrous.

Also pay attention to the fan speed CPU. If its speed is above 3500 rpm. This also indirectly indicates overheating.

Many bloggers on YouTube tell you how to clean your computer at home.

//www.youtube.com/watch?v=KW5onHAIhjc

2. Checking RAM

Sometimes the culprits of stop errors are “broken” modules random access memory. To check them, use the utility MemTest86+. This program is available for Windows, as well as a version with its own bootloader (allows you to load MemTest instead of Windows). The latter is preferable, since when scanning from Windows, the computer may freeze, and you never know what else. So we will use the second option.

We will need:

  1. Flash drive.
  2. Internet connection.

2.1 Downloading and recording MemTest to a flash card.

Download the automatic program installer MemTest and unpack it to any convenient place, for example on Desktop.

Insert a clean USB flash drive into your computer and run the extracted file.


MemTest Installer. Step 1.

The red rectangle marks the required parameters that will be used when recording MemTest to a USB flash drive. Select the letter of the flash drive and check the box that will allow the program to format it.


Advertising

MemTest Installer. Step 2.

Click the button , and on the next screen .

All. Program MemTest recorded, and the flash drive is now bootable.

2.2 Load MemTest from a flash drive.

We turn on the computer and see this picture:

The boot menu in our case opens by pressing . In your case, it may be another key - you will have to figure it out yourself.


Boot menu

Select our flash drive, click and after a couple of seconds the RAM check begins.


Our memory test completed successfully.

The bad thing is when red lines appear during the check.

If a similar picture appears on your screen, most likely the bluescreen appeared precisely because of a malfunction of one or more RAM modules. What to do in this case:

1. try to identify the faulty module by inserting them one by one into the motherboard and checking each one MemTest-ohm.

2. do not use a faulty module, or replace it with a working one.

Remember: any modern computer or a laptop is a high-tech device that requires thoughtful handling of all its components.

If you are not confident in your abilities, ask more experienced users for help. You perform all actions at your own peril and risk. Only you and no one else is responsible for your actions.

3. Checking the video card.

The video card is a fairly common cause of a stop error. If your computer has a discrete video card and motherboard there is a connector SVGA, try removing the video adapter board and working with the built-in one.

How to remove the video card is shown in the video above.

4. Checking the power supply.

Unfortunately, it is almost impossible to check the power supply at home. Someone may disagree, but nevertheless it is so. It is not enough to measure the voltage at the connectors with a multimeter. Checking the power supply is a painstaking process.

The only thing you can try to do is try to put similar in parameters power supply from a working machine. Again, some skills are required.

5. Checking the hard drive.

IN Lately, a common cause of death screens has become hard disks. 10-15 years ago, and there was no thought of sinning HDD. They were the most reliable element of the computer.

Now that they have begun to save heavily on their production, i.e. They moved production to countries with cheaper labor, began to use copper or brass alloys instead of gilding, the quality and price of the discs leave much to be desired.

Of course, there are high-quality ones, but not everyone can afford to have them on their home computer. So it's still worth checking the disk.

5.1 Checking the S.M.A.R.T of the hard drive.

In modern hard drives There is such a wonderful technology - S.M.A.R.T. This is such a microprogram in the controller hard drive, which collects information about its errors - read-write errors, head movement errors, etc.

So, it will not be possible to describe every parameter collected by this technology, since this is a broad topic, clearly not for ordinary users. We will just check the overall health of our disk.

For this we need a program HHDScan from Data Recovery Lab R.LAB.

The archive needs to be unpacked to any place convenient for you.

Let's move directly to the program itself. On the main screen of the program you need to select the hard drive to be tested and click on the button .


A window will open with many parameters, and they will be marked in green or red. If everyone is green, everything is fine. If there are red ones, look for their meanings in Yandex or Google.

Information about S.M.A.R.T. - HDD Scan program

5.2 Checking the file system for errors.

All that remains is to check file system for mistakes. This can be done from the command line using the utility CHKDSK.

Run the cmd program as Administrator (habit).

In the window that opens, enter:

chkdsk c: /r /f

where “c” is the letter of your system drive.

Be patient. The process is not fast. The program will check and correct any errors found automatically.

Something else. If errors are detected, try changing the interface cable SATA or IDE or simply “trail”.

6. Checking the operating system, updating it and updating drivers.

Before this, we were checking equipment. Now let's check the integrity of system files and update operating system and drivers, virus checking. Let's start with viruses, since their presence can prevent us from performing other actions.

6.1 Checking for viruses and malware

The Internet was once relatively clean. There was a minimum of advertising, and there were only rumors about viruses. Now everything has changed - advertising is at every step, and there is no need to talk about the number of viruses and any other “evil spirits”. Especially recently, the so-called Malware- malware from which it is very difficult to escape. It easily bypasses antiviruses and firewalls.

So, update your antivirus, and turn off its screens for a while (so as not to interfere). Download utilities Cure IT And AntiMalwareBytes. Scan your computer with them. Why these programs? They are very simple for any user, even a beginner. Each of these utilities finds viruses and malware even on seemingly clean computers.

After the reboot, you can proceed to further actions.

6.2 Checking the integrity of system files.

Run again command line on behalf of the Administrator. In the program window, enter:

sfc /scannow

and press .

The scanning process will begin, during which you will definitely have time to drink tea. As a result, Windows will restore all files that it considers damaged.

Restart your computer.

6.3 Windows update.

Update Windows. Whatever one may say, it needs to be updated. The update helps eliminate system flaws and vulnerabilities. It also improves its overall stability and security.

It is quite possible that the update has already resolved some problems due to which bluescreen may appear on your equipment. You can update the system by opening Control Panel, and then Center Windows updates .

6.4 Update drivers

Update your hardware drivers. The considerations are the same as with Windows updates - the more recent the better. This can be done in several ways. It all depends on your desire and experience. You can download each driver individually by visiting the websites of your hardware manufacturers.

You can use the utilities that are located on the driver disk from your motherboard, for example MSI Live Update And ASUS.

You can download offline and online driver packs containing all kinds of hardware drivers, For example DriverPack Solution or DevID Agent. All listed programs are in Russian and are as automated as possible.


DriverPack Solution program

Conclusion

These are not all the ways to resolve the BSOD error. There is a lot that was not included in this article.

For example:

  • How to disable automatic system reboot upon failure.
  • how to identify an error by its code.
  • how to read a memory dump.
  • and much more...

But that was not the purpose of the post.

The purpose of the post is to show an inexperienced user how to deal with an error in ways available to him. Explain that it is not necessary to waste time and energy on reinstalling the system, being unsure of the result.

Related Utilities

  • WinCrashReport - Displays a report about crashed Windows application.
  • WhatIsHang - Get information about Windows software that stopped responding (hang)
  • AppCrashView - View application crash information on Windows 7/Vista.

See Also

  • NK2Edit- Edit, merge and fix the AutoComplete files (.NK2) of Microsoft Outlook.

Description

BlueScreenView scans all your minidump files created during "blue screen of death" crashes, and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of the driver or module that possibly caused the crash ( filename, product name, file description, and file version).
For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash.

Versions History

  • Version 1.55:
    • Added Drag & Drop support: You can now drag a single MiniDump file from Explorer into the main window of BlueScreenView.
    • Fixed bug: BlueScreenView failed to remember the last size/position of the main window if it was not located in the primary monitor.
  • Version 1.52:
    • Added "Google Search - Bug Check" and "Google Search - Bug Check + Parameter 1" options.
  • Version 1.51:
    • Added automatic secondary sorting ("Crash Time" column).
    • Added 64-bit build.
  • Version 1.50:
    • The "Crash Time" now displays more accurate date/time of the crash. In previous versions, the value of "Crash Time" column was taken from the date/time of dump file, which actually represents that time that Windows loaded again, after the crash. The actual crash time is stored inside the dump file , and now the "Crash Time" displays this value.
    • Added "Dump File Time" column, which displays the modified time of the dump file.
  • Version 1.47:
    • Added "Auto Size Columns+Headers" option, which allows you to automatically resize the columns according to the row values ​​and column headers.
  • Version 1.46:
    • Fixed issue: The properties and the "Advanced Options" windows opened in the wrong monitor, on multi-monitors system.
  • Version 1.45:
    • You can now choose to open only a specific dump file - from the user interface or from command-line.
    • You can now also specify the MiniDump folder or MiniDump file as a single parameter, and BlueScreenView will be opened with the right dump file/folder, for example: BlueScreenView.exe C:\windows\minidump\Mini011209-01.dmp
  • Version 1.40:
    • Added "Raw Data" mode on the lower pane, which displays the processor registers and memory hex dump.
  • Version 1.35:
    • Added "Crash Address" column.
    • Added 3 columns that display that last 3 calls found in the stack (Only for 32-bit crashes)
  • Version 1.32:
    • Added "Mark Odd/Even Rows" option, under the View menu. When it"s turned on, the odd and even rows are displayed in different color, to make it easier to read a single line.
  • Version 1.31:
    • Added "Google Search - Bug Check+Driver" for searching in Google the driver name and bug check code of the selected blue screen.
  • Version 1.30:
    • Added "Dump File Size" column.
  • Version 1.29:
    • You can now send the list of blue screen crashes to stdout by specifying an empty filename ("") in the command-line of all save parameters.
      For example: bluescreenview.exe /stab "" > c:\temp\blue_screens.txt
  • Version 1.28:
    • Added "Add Header Line To CSV/Tab-Delimited File" option. When this option is turned on, the column names are added as the first line when you export to csv or tab-delimited file.
  • Version 1.27:
    • Fixed issue: removed the wrong encoding from the xml string, which caused problems to some xml viewers.
  • Version 1.26:
    • Fixed "DumpChk" mode to work properly when DumpChk processing takes more than a few seconds.
  • Version 1.25:
    • Added "DumpChk" mode, which displays the output of Microsoft DumpChk utility (DumpChk.exe). You can set the right path and parameters of DumpChk in "Advanced Options" window. By default, BlueScreenView tries to run DumpChk from "%programfiles%\Debugging Tools for Windows"
    • The default MiniDump folder is now taken from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
  • Version 1.20:
    • Added 3 new columns in the upper pane: Processors Count, Major Version, Minor Version.
    • Added "Explorer Copy" option, which allows you to copy dump files to the clipboard and then paste them into Explorer window.
  • Version 1.15:
    • Added option to view the blue screen list of multiple computers on your network. The computer names are specified in a simple text file. (See below).
    • Added Combo-Box to easily choose the MiniDump folders available in the hard-disks currently attached to your computer.
    • Added "Computer Name" and "Full Path" columns.
  • Version 1.11:
    • Added /sort command-line option.
  • Version 1.10:
    • Added accelerator keys for allowing you to toggle between modes more easily.
    • Added command-line options for saving the crash dumps list to text/csv/html/xml file.
    • Added command-line option for opening BlueScreenView with the desired MiniDump folder.
    • Fixed focus problems when opening the "Advanced Options" window.
    • Added "default" button to the "Advanced Options" window.
    • Added "processor" column - 32-bit or x64.
  • Version 1.05 - Added support for x64 MiniDump files.
  • Version 1.00 - First release.

BlueScreenView Features

  • Automatically scans your current minidump folder and displays the list of all crash dumps, including crash dump date/time and crash details.
  • Allows you to view a blue screen which is very similar to the one that Windows displayed during the crash.
  • BlueScreenView enumerates the memory addresses inside the stack of the crash, and find all drivers/modules that might be involved in the crash.
  • BlueScreenView also allows you to work with another instance of Windows, simply by choosing the right minidump folder (In Advanced Options).
  • BlueScreenView automatically locate the drivers appeared in the crash dump, and extract their version resource information, including product name, file version, company, and file description.

System Requirements

  • BlueScreenView works with Windows XP, Windows Server 2003, Windows Server 2008, Windows Vista, Windows 7, Windows 8, Windows 10, as long as Windows is configured to save minidump files during BSOD crashes. If your system doesn't create MiniDump files on a blue screen crash, try to configure it according to the following article:
  • BlueScreenView can read the MiniDump files of both 32-bit and x64 systems.
  • Be aware that on Windows 10, some of the created MiniDump files might be empty and BlueScreenView will not display them.

Using BlueScreenView

BlueScreenView doesn't require any installation process or additional dll files. In order to start using it, simply run the executable file - BlueScreenView.exe
After running BlueScreenView, it automatically scans your MiniDump folder and display all crash details in the upper pane.

Crashes Information Columns (Upper Pane)

  • Dump File: The MiniDump filename that stores the crash data.
  • Crash Time: The created time of the MiniDump filename, which also matches to the date/time that the crash occurred.
  • Bug Check String: The crash error string. This error string is determined according to the Bug Check Code, and it"s also displayed in the blue screen window of Windows.
  • Bug Check Code: The bug check code, as displayed in the blue screen window.
  • Parameter 1/2/3/4: The 4 crash parameters that are also displayed in the blue screen of death.
  • Caused By Driver: The driver that probably caused this crash. BlueScreenView tries to locate the right driver or module that caused the blue screen by looking inside the crash stack. However, be aware that the driver detection mechanism is not 100% accurate, and you should also look in the lower pane, that display all drivers/modules found in the stack. These drivers/modules are marked in pink color.
  • Caused By Address: Similar to "Caused By Driver" column, but also display the relative address of the crash.
  • File Description: The file description of the driver that probably caused this crash. This information is loaded from the version resource of the driver.
  • Product Name: The product name of the driver that probably caused this crash. This information is loaded from the version resource of the driver.
  • Company: The company name of the driver that probably caused this crash. This information is loaded from the version resource of the driver.
  • File Version: The file version of the driver that probably caused this crash. This information is loaded from the version resource of the driver.
  • Crash Address: The memory address that the crash occurred. (The address in the EIP/RIP processor register) In some crashes, this value might be identical to "Caused By Address" value, while in others, the crash address is different from the driver that caused the crash.
  • Stack Address 1 - 3: The last 3 addresses found in the call stack. Be aware that in some crashes, these values ​​will be empty. Also, the stack addresses list is currently not supported for 64-bit crashes.

Drivers Information Columns (Lower Pane)

  • Filename: The driver/module filename
  • Address In Stack: The memory address of this driver that was found in the stack.
  • From Address: First memory address of this driver.
  • To Address: Last memory address of this driver.
  • Size: Driver size in memory.
  • Time Stamp: Time stamp of this driver.
  • Time String: Time stamp of this driver, displayed in date/time format.
  • Product Name: Product name of this driver, loaded from the version resource of the driver.
  • File Description: File description of this driver, loaded from the version resource of the driver.
  • File Version: File version of this driver, loaded from the version resource of the driver.
  • Company: Company name of this driver, loaded from the version resource of the driver.
  • Full Path: Full path of the driver filename.

Lower Pane Modes

Currently, the lower pane has 4 different display modes. You can change the display mode of the lower pane from Options->Lower Pane Mode menu.
  1. All Drivers: Displays all the drivers that were loaded during the crash that you selected in the upper pane. The drivers/module that their memory addresses found in the stack, are marked in pink color.
  2. Only Drivers Found In Stack: Displays only the modules/drivers that their memory addresses found in the stack of the crash. There is a very high chance that one of the drivers in this list is the one that caused the crash.
  3. Blue Screen in XP Style: Displays a blue screen that looks very similar to the one that Windows displayed during the crash.
  4. DumpChk Output: Displays the output of Microsoft DumpChk utility. This mode only works when Microsoft DumpChk is installed on your computer and BlueScreenView is configured to run it from the right folder (In the Advanced Options window).
    You can get DumpChk from the installation CD/DVD of Windows or with the installationtion of Debugging Tools for Windows.

Crashes of Remote Network Computer

If you have multiple computers on your network and you have full administrator access to them (e.g: you have access to \\ComputerName\c$), you can also view the crashes of the other computers on your network remotely. In order to do that, simply go to "Advanced Options" (Ctrl+O) and type the MiniDump folder of the remote computer, for example: \\MyComp\c$\Windows\MiniDump.

Notice: If you fail to get full administrator access to the remote computer, you should read the instructions in the following Blog post: .

Watching the crashes of multiple computers on your network

If you have a network with multiple computers, and you have full admin access to these computers, you can view the blue screens list of all these computers in one table, and easily detect computers with recurring BSOD problems.

In order to use this feature, prepare a list of all computer names/IP addresses that you want to inspect, and save it to a simple text file. The computer names in the list can be delimited by comma, semicolon, tab character, or Enter (CRLF).
Example for computer names list:

Comp01 comp02 192.168.0.1 192.168.0.2 192.168.0.4 After you have a text file contains the computers list, you can go to Advanced Options window (Ctrl+O), choose the second option and type the computers list filename.

Command-Line Options

/LoadFrom Specifies the source to load from.
1 -> Load from a single MiniDump folder (/MiniDumpFolder parameter)
2 -> Load from all computers specified in the computer list file. (/ComputersFile parameter)
3 -> Load from a single MiniDump file (/SingleDumpFile parameter)
/MiniDumpFolder Start BlueScreenView with the specified MiniDump folder.
/SingleDumpFile Start BlueScreenView with the specified MiniDump file. (For using with /LoadFrom 3)
/ComputersFile Specifies the computers list filename. (When LoadFrom = 2)
/LowerPaneMode<1 - 3> Start BlueScreenView with the specified mode. 1 = All Drivers, 2 = Only Drivers Found In Stack, 3 = Blue Screen in XP Style.
/stext Save the list of blue screen crashes into a regular text file.
/stab Save the list of blue screen crashes into a tab-delimited text file.
/scomma Save the list of blue screen crashes into a comma-delimited text file (csv).
/stabular Save the list of blue screen crashes into a tabular text file.
/shtml Save the list of blue screen crashes into HTML file (Horizontal).
/sverhtml Save the list of blue screen crashes into HTML file (Vertical).
/sxml Save the list of blue screen crashes into XML file.
/sort This command-line option can be used with other save options for sorting by the desired column. If you don"t specify this option, the list is sorted according to the last sort that you made from the user interface. The parameter can specify the column index (0 for the first column, 1 for the second column, and so on) or the name of the column, like "Bug Check Code" and "Crash Time". You can specify the "~" prefix character (e.g: "~Crash Time") if you want to sort in descending order. You can put multiple /sort in the command-line if you want to sort by multiple columns.

Examples:
BlueScreenView.exe /shtml "f:\temp\crashes.html" /sort 2 /sort ~1
BlueScreenView.exe /shtml "f:\temp\crashes.html" /sort "Bug Check String" /sort "~Crash Time"
/nosortWhen you specify this command-line option, the list will be saved without any sorting.

Translating BlueScreenView to other languages

In order to translate BlueScreenView to other language, follow the instructions below:
  1. Run BlueScreenView with /savelangfile parameter:
    BlueScreenView.exe /savelangfile
    A file named BlueScreenView_lng.ini will be created in the folder of BlueScreenView utility.
  2. Open the created language file in Notepad or in any other text editor.
  3. Translate all string entries to the desired language. Optionally, you can also add your name and/or a link to your Web site. (TranslatorName and TranslatorURL values) If you add this information, it"ll be used in the "About" window.
  4. After you finish the translation, Run BlueScreenView, and all translated strings will be loaded from the language file.
    If you want to run BlueScreenView without the translation, simply rename the language file, or move it to another folder.

License

This utility is released as freeware. You are allowed to freely distribute this utility via floppy disk, CD-ROM, Internet, or in any other way, as long as you don"t charge anything for this. If you distribute this utility, you must include all files in the distribution package, without any modification!

Problem with the name BlueScreen events may appear in Windows OS (for example, Windows 7) after some time of operation. Or, say, jump out when it’s running computer game. A one-time appearance of BlueScreen can be ignored - perhaps nothing terrible has happened yet. If the BlueScreen problem event name begins to appear periodically, then you should think about possible problems with the computer and eliminating them.

What are the reasons for the BlueScreen error?

STOP error 0X116- “the driver did not respond to the system request in a timely manner” - appears quite often, and its reasons can be as follows:

  • Overheating on the south bridge motherboard, video card;
  • Driver malfunction;
  • Overclocking a video card;
  • Problems with RAM;
  • Low power supply;
  • There is a malfunction in the equipment itself.

Options for fixing the BlueScreen problem

Depending on what caused the problem, the solutions vary. I'll tell you about all the possibilities.

  1. If you recently updated the video driver, try rolling it back and/or restoring the system to an earlier state;
  2. Other problems with the video card may require updating its BIOS. Also try to reduce the frequency - the RivaTuner utility helps;
  3. If you overclocked the processor, video card, or RAM, remove it;
  4. If the error “BlueScreen problem event name” appears after playing a game, try lowering the screen resolution and graphics settings to the minimum settings, and only then play. Find out if the problem is caused by the video card;
  5. Try also resetting your BIOS to default. The documentation for your computer or motherboard can help;
  6. If you don't have latest version DirectX - update it.
  7. There may be overheating. Check the temperature of your video card, power supply, processor and southbridge on the motherboard. Additional cooling may be needed.
  8. If possible, try temporarily replacing your power supply with another, more powerful one, and see if a message appears with the event name - BlueScreen.

Using Windows tools, test your RAM for errors. If you have more than one module, then remove them all and insert, for example, one. Continue working for a couple of days. If the fatal BlueScreen problem stops appearing, replace the memory module with another one and find the damaged one, if any. Also try inserting memory modules into different slots - the problem may be in them.

You can return it to the factory state or reinstall Windows (if you find it difficult yourself, contact the technical support of your computer manufacturer). If it is important to save some data, first create an image of the system for its subsequent restoration.

However, before the previous point, it is better to try a “clean” boot of the operating system and check whether everything is working normally. To do this, proceed as follows: Start > Find programs and files > Configuration > System Configuration. There, in the “General” tab, mark “ Normal launch", there is the "Services" tab, then check the "Do not display Microsoft services" checkbox and disable everything else using the "Disable all" button. Go to the “Startup” tab and use the same button to disable everything “non-standard”. Click Apply and OK and restart the computer.

Note: the above is for Windows 7. In other OSes, similar settings can also be accessed by entering “msconfig” after clicking Start -> Run.

After loading the system, look: some programs will not load automatically when the system starts, but manual start will allow them to work fully.

If the BlueScreen problem is not resolved after all the above, then contact service center. Most likely, it will be the video card that is at fault - request testing of it.

Quote: rier

I launched it and nothing happens. How to enable scanning?

Despite the fact that the question is 2 years old, it is still relevant for lucky SES owners, and the BlueScreenView utility can help them.
Briefly about the main:
We say BSOD (not the official name), we mean SES, STOP code, crash dump, memory dump.

Occurs when there is a threat of OS crash, i.e., the developer protects the OS from “playful hands”.
Usually, SES pops up if there are problems with hardware or hardware drivers. Programs are often not capable of SES, because fail without affecting the operation of the OS, and those that work at the kernel (driver) level may present a surprise.
If it's time critical day: OS receives STOP code, stops communication, displays for 1 second Bill Gates Blue Square, goes to reboot, and automatically creates a memory dump.
To enjoy this wonderful picture: => RMB Computer or W+Break => Advanced System Settings=> Tab => Options... field System failure- remove the label Perform automatic reboot, and also, remove the label Replace existing dump file(may be useful for recurring errors). Ibid. Writing Debug Information there is a choice: Kernel memory dump or Small memory dump indicating the appropriate ways to save dumps.


But if you haven’t become the happy owner of an SES, it doesn’t matter, we will create it, because you need to know the enemy by sight.

=> W+R => regedit => Enter =>
For PS/2 keyboard: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters
For USB keyboard: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\kbdhid\Parameters
Create a new 32bit DWORD value called CrashOnCtrlScroll, with a value of 1.
Restart your PC.


now this happiness in your hands: holding right CTRL key press twice Scroll Lock, you will receive , we are interested within 1 And 2 .
What does it mean in translation:

An issue has been detected and the OS has been disabled to prevent damage to the PC.
User manually created a crash dump.
If you see a stop screen for the first time, restart your PC.
When repeating:
Check to see if any new hardware or software is installed correctly.
If new installation, contact the device or software manufacturer for Windows updates.
If problems continue, disable/uninstall everything again installed devices or software.
Disable BIOS memory options - caching/shadowing.
If needed safe mode to remove/disable components, restart your PC => F8 => Advanced startup options => Safe Mode.
Technical information:
*** STOP: 0x000000E2 (0x00000000, 0x00000000, 0x00000000, 0x00000000)
Data collection for emergency reset...
Initializing disk for emergency reset...
Start of physical memory reset.
Flushing physical memory to disk: 100
Reset physical memory.
For additional assistance, contact the admin/tech support team.


Error 0x000000E2 indicates that the user deliberately initiated a crash dump using the kernel debugger or using the keyboard.
Launch BlueScreenView, look..., if it doesn’t see it, help through Settings = Additional options...

Hello! Today we will talk about the problem of the blue screen of death - BlueScreen. Many users encounter it while working or playing on a computer. We will tell you what “Problem Event Name: BlueScreen” is and what you need to do to fix it. We will also describe a solution to the problem with BlueScreen error 1049.

Almost all of us have encountered the Blue Screen of Death. Let's try to give a simple definition of this problem, so:

BlueScreen is a “message” addressed to the user indicating a critical system error and that the computer will restart with the loss of all unsaved data. The message also indicates the general causes of the problem and the error code. Experts call this problem BSOD (Blue Screen of Death).

For Windows 7, if a blue screen occurs, an error message appears after a reboot.

The causes of BSOD can be different, from physical to systemic:

  1. Problems with computer hardware - incorrectly installed devices;
  2. Overheating of the video card, processor or other components of the laptop or PC;
  3. Voltage drop in the network;
  4. Wrong installed updates Windows;
  5. Important items removed system files or folders;
  6. Wrong installed drivers- the most common mistake.

As a rule, in case of a Blue Screen, a simple reboot helps many users. After it everything returns to normal. But if the problem is with the drivers, then in certain cases, the problem will recur. This is possible when the user launches a game or program. Let's figure out what needs to be done in this case and how to determine what exactly the system does not like.

Very often, when a BSOD error appears, the screen appears literally for a second and then a reboot follows. To get acquainted with the problem and identify the code, you first need to remove the reboot. Sign in Control Panel\All Control Panel Items\System. Press Additional system parameters. In the window that opens, uncheck the Perform an automatic reboot.

After this, you can write down the error code. There can be a huge number of sources of problems and codes. Therefore, next, you should enter this code into a search query and find a solution on the Internet. There is no single solution to such situations; each problem must be solved separately.

Diagnosis of overheating and physical problems is carried out very well by the AIDA64 program. In case of system problems, BlueScreenView is suitable for searching and identifying. It will list all the dumps (.dmp - error report) and analyze all the data, even indicating the driver that led to the problem. You can learn more about the BlueScreenView utility in this video (closer to the end).

BlueScreen code 1049 what is this problem

One of the most common reasons may be problems with video card drivers. In this case, the message “Problem event name: BlueScreen” (code 1049) appears, which means a problem with the video card. In this case, it is necessary:

  1. Disable the built-in video card (if any) in the settings;
  2. Completely update video drivers;
  3. Check the physical parameters - for overheating and whether it fits tightly in the slot;
  4. Use the BlueScreenView utility to determine.