Quote from rier

Launched and nothing happens. How to enable scanning?

Despite the fact that the question is 2 years old, but for the happy owner of the SES, it is relevant, and the BlueScreenView utility will help them.
Briefly about the main:
We say BSOD (not of name), we mean SES, STOP code, crash dump, memory dump.

Occurs when the OS is in danger of crashing, i.e., the developer protects the OS from "playful hands".
Usually, SES pops up if there are problems with hardware, 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 can throw a surprise.
If it has come critical day: OS receives STOP code, stops communication, displays for 1 sec Bill Gates Blue Square, goes to reboot, and automatically creates a memory dump.
To enjoy this wonderful picture: => RMB Computer or w+break => Additional system settings=> Tab => Parameters... field System failure- remove label Perform automatic reboot and also, uncheck Replace existing dump file(may come in handy for recurring errors). Ibid Writing debug information there is a choice: Kernel memory dump or Small memory dump indicating the appropriate ways to save the dumps.

But, if you have not become the happy owner of the SES, it does not matter, we will create it, because you need to know the enemy in person.

=> 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 named CrashOnCtrlScroll with value 1.
Restart PC.

now this happiness in your hands: holding right CTRL key double click scroll lock, you will receive , we are interested in within 1 and 2 .
What does it mean in translation:

An issue has been identified 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.
On repeat:
Check if any new device or software is installed correctly.
If a new installation, contact the device or software manufacturer and ask for Windows updates.
If problems continue, disable/remove any newly 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...
Starting a physical memory flush.
Flush physical memory to disk: 100
Reset physical memory.
For further assistance, please contact the admin/support team.

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

BlueScreenView is a program that provides detailed information about all the "Blue Screen Of Death" that have 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 gives the following data: minidump file name, date and time of the crash, basic information displayed on the blue screen at the time of the error (Bug Check Code and 4 parameters), and details regarding the driver or module that could cause a critical error in 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 starts scanning the %SystemRoot%\Minidump folder and displays the results. The scanning process may take a few seconds.

What's new in this version?

1.55 (30.01.2015)

• added support for Drag & Drop, now you can simply drag MiniDump files to the main window;
• fixed a bug where the application did not "remember" the time of the last "blue screen" if it was "highlighted" not on the main monitor.

Hello! Today we will talk about the problem of the blue screen of death - BlueScreen. Many users, in the process of working or playing at a computer, are faced with it. We will tell you what this “Issue Event Name: BlueScreen” is and what needs to be done to fix it. Also, we will describe the solution to the problem with the BlueScreen error 1049.

Almost every one of us has experienced 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, which says about a critical system error and that the computer will be rebooted with the loss of all unsaved data. Also, the message 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 report message appears after 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 a laptop or PC;
3. Voltage drop in the network;
4. Incorrectly installed Windows updates;
5. Deleted important system files or folders;
6. Incorrectly installed drivers are the most common mistake.

As a rule, in the event of a Blue Screen, many users are helped by a simple reboot. After that everything goes back to normal. But if the problem lies in 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 occurs, the screen appears literally for a second, and then a reboot follows. In order to get acquainted with the problem and identify the code, it is first necessary to remove the reboot. Sign in Control Panel\All Control Panel Items\System. Press Additional system settings. In the window that opens, uncheck Perform an automatic reboot.

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

Diagnosis with overheating and physical problems is very well done by the AIDA64 program. In case of system problems, BlueScreenView is suitable for searching and determining. It will list all 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 (near the end).

BlueScreen code 1049 what is the problem

One of the most common causes can be problems with video card drivers. In this case, the message "Problem event name: BlueScreen" (code 1049) appears, which means a violation in the operation of the video card. In this case, you need:

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

Related Utilities

• WinCrashReport - Displays a report about a 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.

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

BlueScreenViewFeatures

• 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 the 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 installtion 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"
/nosort	When 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 !

The problem with the BlueScreen event name can appear in Windows OS (for example, Windows 7) after some time. Or, say, jump out when a computer game is running. The single appearance of BlueScreen can be ignored - perhaps nothing terrible has happened yet. If the BlueScreen problem event name starts to appear intermittently, then you should think about possible problems with your computer and how to fix them.

What are the causes of 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 may be as follows:

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

Options to fix the BlueScreen problem

Solutions vary depending on what caused the problem. 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. Of the other problems with the video card, it may be necessary to update its BIOS. Also try to reduce the frequency - the RivaTuner utility helps;
3. If you overclocked the processor, video card, RAM - remove it;
4. If the error “Problem event name BlueScreen” appears after the game, try to reduce the screen resolution and graphic rendering in it to the minimum, and only then play. Find out if the problem is being created by the video card;
5. Also try resetting your BIOS to default. The documentation for the computer or motherboard can help;
6. If you don't have the latest version of DirectX, update it.
7. Perhaps there is overheating. Check the temperature of your graphics card, power supply, processor and southbridge on the motherboard. You may need additional cooling.
8. If possible, try temporarily replacing your power supply with another, more powerful one, and see if a message appears with the name of the event - BlueScreen.

Use Windows tools to test your RAM for errors. If you have more than one of its modules, then extract everything and insert, for example, one. Keep working for a couple of days. If the fatal BlueScreen problem has stopped appearing, change the memory module to another one and so find the damaged one, if any. Try also inserting memory modules into different slots - the problem happens in them.

You can return 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 recovery.

However, before the previous paragraph, it is still better to try a “clean” boot of the operating system and check if everything is working fine. To do this, proceed as follows: Start > Find programs and files > Configuration > System configuration. There, in the "General" tab, check "Normal startup", there the "Services" tab, then check the "Do not display Microsoft services" checkbox and disable everything else through the "Disable all" button. Go to the "Startup" tab and there, with the same button, turn off everything "non-standard". Click Apply and OK, restart your computer.

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

After booting the system, look: some programs will not load automatically at system startup, however, manual start will allow them to fully work.

If the BlueScreen problem is not resolved after all of the above, then contact the service center. Most likely, the video card will still be to blame - request its testing.