Download the bluescreenview program to your windows 7 computer. BlueScreen problem event name - how to fix it? Features and nuances of self-recovery of the system

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 => Extra options systems=> 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.

=> 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.

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 if any new device or software is installed correctly.
If a 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 you need 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.

Hello! Today we will talk about the problem blue screen 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 BSOD problem(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 in 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.

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

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

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

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

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

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

Translating BlueScreenView to other languages

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

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 a computer game is running. 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 motherboard south bridge, video cards;
• 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 have overclocked a processor, video card, random access memory- 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 the last one DirectX version- 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.

By 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’s better to try a “clean” boot operating system and check if everything is working normally. To do this, proceed as follows: Start > Find programs and files > Configuration > System Configuration. There, in the “General” tab, check “Normal startup”, 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 of the above, then contact service center. Most likely, it will be the video card that is at fault - request testing of it.

BlueScreenView is a program that provides detailed information about all the "Blue Screen Of Death" that occurred in the system. The program scans all minidump files created during a BSOD, and provides the user with detailed information about all system crashes in one table. For each BSOD, the program produces the following data: minidump file name, date and time of the crash, basic information displayed on the blue screen during the error (Bug Check Code and 4 parameters), and details regarding the driver or module that could cause critical error on the system (driver file name, product name, file description and version).

The program is provided in two versions: portable and as a complete installation. The Russian language is installed separately by downloading the archive with the Russification file. Immediately after launch, the program begins scanning the %SystemRoot%\Minidump folder and displays the results. The scanning process may take several seconds.

What's new in this version?

1.55 (30.01.2015)