This tutorial is about How to Fix ‘Store Data Structure Corruption’ Issue on Windows 10 PC. Recently I updated this tutorial and will try my best so that you understand this guide. I hope you guys like this blog, How to Fix ‘Store Data Structure Corruption’ Issue on Windows 10 PC. If your answer is yes after reading the article, please share this article with your friends and family to support us.
Check How to Fix ‘Store Data Structure Corruption’ Issue on Windows 10 PC
Many people have started complaining of receiving a blue screen of death that says “store data structure corruption”. They tend to do well after they are done playing the game, they have turned everything off, and are going to disconnect from their computers or do something else.
It’s annoying and it can happen once and it’s done, or it can happen over and over again. It is usually accompanied by a BSOD, but not always. What causes this problem and how can you prevent it from happening again? We have some potential solutions.
Uninstall any known problematic apps
There are some known applications that have been reported to cause the “CRITICAL_STRUCTURE_CORRUPTION” error in Windows 10. Uninstalling these applications may correct the error so that it does not occur again. At the moment, some of the known applications that cause this error are Daemon Tools, Blue Stacks, Alcohol 120%, Virtual Box, Intel Hardware Accelerated Execution Manager, and Mac Driver.
These are just a few, so we recommend using the Windows Event Viewer (go to Method 5) to identify any other possible applications. If you have any of these apps installed on your device, follow the simple guide below to remove them. Doing so can potentially eliminate the possibility of this blue screen error happening again.
- Click the Start menu on the taskbar, then select “Settings.” Alternatively, you can press Windows + I keys on your
- keyboard to open the application.
- Click on the “Applications” tile.
- Use the search function to find the problematic application that you have installed.
- Click on the application and choose the “Uninstall” option.
- Follow the instructions on the screen to successfully remove the application.
- When the uninstallation is complete, restart your computer.
Update your graphics driver
Keeping your drivers up to date is important. An outdated graphics driver can cause frustrating errors on your device and can ultimately lead to blue screens. Fortunately, updating these drivers is fairly easy and requires no experience; just follow our steps to make sure you have the latest version of your driver.
First, you need to check which graphics card you are using. If you still don’t know the exact model, follow these steps:
- Press Windows + R keys on your keyboard to open the Run utility. Here, just type “dxdiag” and hit the OK button.
- The DirectX Diagnostic Tool should open on your screen. Use the header menu to switch to the “Display” tab.
- In the “Device” section, check “Name”. You should be able to see the manufacturer and model of the graphics card. Keep this in mind for the next steps.
Once you’ve identified your graphics card, head over to the manufacturer’s website and find a dedicated download page for drivers. We have compiled a list of some popular graphics card brands with links to their download page:
- Intel Drivers and Software Page
- NVIDIA Driver Download Page
- AMD Drivers and Support Page
- Find your graphics card using the built-in search function, then download your latest driver compatible with your system.
- Install the latest driver by double-clicking the downloaded file and then following the on-screen instructions.
Run the Windows Memory Diagnostic Tool
Windows 10 comes with many troubleshooting tools to ensure that you can easily diagnose and fix problems without having to go to customer service. One of these tools is Windows Memory Diagnostic, which is capable of identifying problems with your memory.
Here’s how you can run it.
- Press Windows + R keys on your keyboard to open the Run utility. Here, just type “mdsched.exe” and hit the OK button.
- Choose “Restart Now and Check for Problems (Recommended)” to be instantly a memory scan. Make sure to save your files and close all open applications before clicking this option. Otherwise, choose “Check for problems next time I start my computer” and restart the device at a more convenient time.
- During the next boot, you will see that the Windows Memory Diagnostic Tool checks for problems. Make sure you read all the information displayed on the screen and wait for it to complete.
- After the memory test is complete, you can see if any problems were identified. If there were none, luckily your memory works fine.
Run the System File Checker
The System File Checker is a tool available in Windows 10 by default. Also called “SFC scan”, it is the fastest way to automatically repair corrupted system files and other problems.
- Press Windows + R keys on your keyboard. This will open the Run utility.
- Type “cmd” and press the Ctrl + Shift + Enter keys on your keyboard. By doing this, you are starting the command prompt with administrative permissions.
- If prompted, click Yes to allow the command prompt to make changes to your device.
- Once at the command prompt, type the following command and hit Enter to run it: sfc / scannow Wait for the SFC scan to finish scanning your computer and repairing corrupted files. This can take a long time; make sure that
- it does not close the command prompt or shut down the computer.
- Restart your device after the scan is complete.
Check the event viewer
Not sure which application, service, or other error caused the “Blue Screen of Death” to appear on your screen? Don’t worry, we know the perfect built-in tool to identify what exactly happened on your device. It is the event viewer.
With the Event Viewer, you can easily see the last thing that happened on your computer before it crashed. This will allow you to identify exactly what is causing your problem and resolve it more effectively by removing the application or disabling the service.
- Press Windows + X keys on your keyboard at the same time, then choose “Event Viewer” from the context menu.
- Click on “Windows Logs” within the left side panel, then choose “System”. This should change the middle section to show all events with timestamps.
- Locate the last event logged before the “CRITICAL_STRUCTURE_CORRUPTION” error occurred on your system. If you see a certain application or service, it is most likely the culprit.
Final remarks: How to Fix ‘Store Data Structure Corruption’ Issue on Windows 10 PC
I hope you understand this article, How to Fix ‘Store Data Structure Corruption’ Issue on Windows 10 PC. If your answer is no, you can ask anything via the contact forum section related to this article. And if your answer is yes, please share this article with your friends and family to give us your support.
Dian Erwin
Dian Erwin is a writer for Bollyinside, covering topics related to computing, such as laptops, tablets, Windows, and iOS. Tony spends much too much of his free time on Twitter, reading speculative fiction novels, playing video games, and reading comic books. He also enjoys reading video game manuals.
Если вы получаете ошибку CRITICAL_STRUCTURE_CORRUPTION в Windows 10/8/7, то вы можете решить ее с помощью данного руководства. Это сообщение на синем экране смерти может появиться из-за не поддерживаемого оборудования, драйвера и даже программного обеспечения. Наряду с сообщением вы можете даже увидеть коды ошибок, такие как 0x00000109, 0x8A287C67, 0x0B76E031, 0x3590B8E7 и 0x559F80CD.
Как исправить ошибку CRITICAL_STRUCTURE_CORRUPTION в Windows 10/8.1/7
1. Использование просмотра событий для получения дополнительных сообщений
Системный журнал просмотра событий может показать много вещей о любом сообщении об ошибке, произошедшем на вашем компьютере.
- Наберите в поиске windows (около кнопки пуск), «просмотр событий» и запустите это приложение.
- В просмотре событий перейдите слева по пути «Журналы Windows» > «Система» и справа найдите ошибку. Нажмите на нее два раза и в окне вы увидите подробности ошибки. Если средство просмотра событий не показала толком ничего, чтобы исправить данную проблему, то ниже мы разберем способы.
2. Использовать диагностику памяти Windows
Поскольку ошибка CRITICAL_STRUCTURE_CORRUPTION может произойти из-за поврежденного ОЗУ, вы можете использовать инструмент диагностики памяти Windows.
- Наберите в поиске mdsched.exe и запустите инструмент диагностики. Далее следуйте указанным инструкциям. Более подробно, как диагностировать оперативную помять на ошибки в Windows.
3. Установить обновления драйверов
Согласно официальному заявлению Microsoft, эта проблема может быть вызвана устаревшими драйверами. Если аппаратное обеспечение не может нормально работать с системой из-за очень старого драйвера, пользователи могут получить это сообщение об ошибке BSOD. По этому вы должны перейти на официальные сайты производителей оборудования и проверит более новые версии драйвера. Кроме того, вы должны проверить, совместимо ли ваше существующее или новое оборудование с вашей версией Windows.
4. Использовать CHKDSK
Chkdsk — это инструмент командной строки, доступный для ОС Windows. С помощью его вы можете исправить различные ошибки, связанные с жестким диском.
- Откройте командную строку от имени администратора и введите команду chkdsk /f /r. Для завершения сканирования потребуется некоторое время.
5. Воспользоваться инструментом Driver Verifier
Driver Verifier Manager — инструмент Windows, который помогает пользователям исправлять проблемы, связанные с драйверами.
- Наберите в поиске Verifier и откройте приложение.
- Выберите создать нестандартные параметры.
- В следующем окне убедитесь, что вы пометили все, кроме «Проверка соответствия требованиям DDI» и «Эмуляция случайной нехватки ресурсов».
- Далее «Выбрать имя драйвера из списка«.
- Далее выберите галочкой все драйвера, которые не предоставляются Microsoft и нажмите Готово.
Теперь откройте командную с правами администратора и выполните следующую команду для отображения настройки драйвера.
verifier /querysettings
Если флажки включены, то вам нужно будет загрузиться в безопасном режиме и ввести следующую команду для сброса драйверов.
verifier /reset
Смотрите еще:
- Что такое ACPI INT33A0 0 в Windows 10 и как исправить
- Скачать xinput1_3.dll или d3dx9_43.dll для Windows 10/8/7
- Ошибка DistributedCOM Код события 10016 Windows 10
- Как исправить CDPUserSvc прекратил работу в Windows 10
- Как исправить ошибку 0xc004f074 при активации Windows 10
[ Telegram | Поддержать ]
| title | description | keywords | ms.date | topic_type | api_name | api_type | ||
|---|---|---|---|---|---|---|---|---|
|
Bug Check 0x1C7 STORE_DATA_STRUCTURE_CORRUPTION |
The STORE_DATA_STRUCTURE_CORRUPTION bug check has a value of 0x000001C7. It indicates that the store component detected a corruption in its data structures. |
|
01/28/2019 |
apiref |
STORE_DATA_STRUCTURE_CORRUPTION |
NA |
Bug Check 0x1C7: STORE_DATA_STRUCTURE_CORRUPTION
The STORE_DATA_STRUCTURE_CORRUPTION bug check has a value of 0x000001C7. It indicates that the store component detected a corruption in its data structures.
[!IMPORTANT]
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
STORE_DATA_STRUCTURE_CORRUPTION Parameters
| Parameter | Description |
|---|---|
| 1 | Corruption ID. See values below. |
| 2 | See values below. |
| 3 | See values below. |
| 4 | See values below. |
Corruption ID
0x0 : A chunk heap buffer's hash doesn't match.
2 - Chunk heap buffer whose hash didn't match.
3 - Expected buffer hash.
4 - Page frame number of the corrupted page.
0x1 : An unhandled exception occurred on the store thread and a chunk heap buffer's hash doesn't match, which is likely the source of the exception.
2 - Chunk heap buffer whose hash didn't match.
3 - Expected buffer hash.
4 - Page frame number of the corrupted page.
0x2 : Page data appears corrupt during a read and the corresponding page record's heap buffer hash doesn't match.
2 - Chunk heap buffer whose hash didn't match containing the page record of the data being read.
3 - Expected buffer hash.
4 - Page frame number of the corrupted page.
0x3 : Page data appears corrupt during a read and the corresponding page record has changed since the start of the read operation.
2 - Pointer to the page location information snapped from the page record that was found when the read was initiated.
3 - Pointer to the page record currently in the page tree for the same page key.
4 - Reserved.
Cause
The store component detected a corruption in its data structures.
This bugcheck can occur by memory corruption due to physical memory access. The causes for physical memory corruption include:
- Defective RAM hardware
- A driver or device incorrectly modifying physical pages via an incorrect DMA operation or associated MDL.
- Corruption caused by a hardware device or firmware corrupting memory, such as firmware illegally modifying physical pages across a power transition.
For more information on Windows memory manager, see Windows Internals 7th Edition Part 1 by Pavel Yosifovich, Mark E. Russinovich, David A. Solomon and Alex Ionescu.
Resolution
Windows Memory Diagnostics Tool
To investigate if this bug check is caused by defective RAM hardware, run the Windows Memory Diagnostics tool. In the control panel search box, type Memory, and then select Diagnose your computer’s memory problems. After the test is run, use Event viewer to view the results under the System log. Look for the MemoryDiagnostics-Results entry to view the results.
See Also
Bug Check Code Reference
Windows Kernel-Mode Memory Manager
| title | description | keywords | ms.date | topic_type | api_name | api_type | ||
|---|---|---|---|---|---|---|---|---|
|
Bug Check 0x1C7 STORE_DATA_STRUCTURE_CORRUPTION |
The STORE_DATA_STRUCTURE_CORRUPTION bug check has a value of 0x000001C7. It indicates that the store component detected a corruption in its data structures. |
|
01/28/2019 |
apiref |
STORE_DATA_STRUCTURE_CORRUPTION |
NA |
Bug Check 0x1C7: STORE_DATA_STRUCTURE_CORRUPTION
The STORE_DATA_STRUCTURE_CORRUPTION bug check has a value of 0x000001C7. It indicates that the store component detected a corruption in its data structures.
[!IMPORTANT]
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
STORE_DATA_STRUCTURE_CORRUPTION Parameters
| Parameter | Description |
|---|---|
| 1 | Corruption ID. See values below. |
| 2 | See values below. |
| 3 | See values below. |
| 4 | See values below. |
Corruption ID
0x0 : A chunk heap buffer's hash doesn't match.
2 - Chunk heap buffer whose hash didn't match.
3 - Expected buffer hash.
4 - Page frame number of the corrupted page.
0x1 : An unhandled exception occurred on the store thread and a chunk heap buffer's hash doesn't match, which is likely the source of the exception.
2 - Chunk heap buffer whose hash didn't match.
3 - Expected buffer hash.
4 - Page frame number of the corrupted page.
0x2 : Page data appears corrupt during a read and the corresponding page record's heap buffer hash doesn't match.
2 - Chunk heap buffer whose hash didn't match containing the page record of the data being read.
3 - Expected buffer hash.
4 - Page frame number of the corrupted page.
0x3 : Page data appears corrupt during a read and the corresponding page record has changed since the start of the read operation.
2 - Pointer to the page location information snapped from the page record that was found when the read was initiated.
3 - Pointer to the page record currently in the page tree for the same page key.
4 - Reserved.
Cause
The store component detected a corruption in its data structures.
This bugcheck can occur by memory corruption due to physical memory access. The causes for physical memory corruption include:
- Defective RAM hardware
- A driver or device incorrectly modifying physical pages via an incorrect DMA operation or associated MDL.
- Corruption caused by a hardware device or firmware corrupting memory, such as firmware illegally modifying physical pages across a power transition.
For more information on Windows memory manager, see Windows Internals 7th Edition Part 1 by Pavel Yosifovich, Mark E. Russinovich, David A. Solomon and Alex Ionescu.
Resolution
Windows Memory Diagnostics Tool
To investigate if this bug check is caused by defective RAM hardware, run the Windows Memory Diagnostics tool. In the control panel search box, type Memory, and then select Diagnose your computer’s memory problems. After the test is run, use Event viewer to view the results under the System log. Look for the MemoryDiagnostics-Results entry to view the results.
See Also
Bug Check Code Reference
Windows Kernel-Mode Memory Manager