Windows 10: Win10 BSOD w/ bucheck 0x00000109 CRITICAL STRUCTURE CORRUPTION

A few moments prior, I experienced an out of the blue BSOD. I've done a quick scan on Google to get more information on the supposed cause for this particular BSOD, but I'm not able to locate a definitive reason. My best guess (currently) is a driver conflict of some sort or a hardware issue.

After checking Event Viewer, I found the following:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109 (0xa3a0205ac0c8b69c, 0x0000000000000000, 0x48539c66cfc9785e, 0x0000000000000101). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: b47e87be-4570-497d-8bea-03feee4b7df6.

An event of Windows rebooting unexpectedly preceded this (as one would imagine).

I ran WhoCrashed and received this output:




I will proceed to check updates for everything on my system, but I will require time to give more extensive feedback.

In the mean time, I would like some insight as to why this occurred or at least some assistance in pinpointing the cause.

I will also include a archive from running dm_log_collector.:
BRYAN-AMD-Fri_01_19_2018_172926_77.zip

TIA

:)

 

blue screen, stop code

My laptop keeps restarting with a blue screen. Stop code: critical structure corruption (which is BSOD error code 0x00000109), and it says what failed: tcpip.sys. The lifewire site said it means a kernel code or data corruption. Anyone know how to fix
this? I have not added any hardware or downloaded anything recently that I can think of, and everything's up to date.

 

critical structure corruption windows 10

i got a critical structure corruption bsod does anyone know how to fix this?

 

There was 1 BSOD mini dump file collected.
It displayed bugcheck 109.
There was no definitive misbehaving driver.
The older events displayed bugcheck was EF.
The logs displayed recovery of the video card.


For all tests /steps please post images into the thread.
If there are any problems posting images please use one drive or drop box share links.
Share OneDrive files and folders - Office Support
Upload photos and files to OneDrive - OneDrive


1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
6) Make sure that there is no over clocking while troubleshooting.
7) Sometimes there are problems in the bios that produce bsod.
The BIOS: Version/Date American Megatrends Inc. F3, 5/28/2015 SMBIOS Version 2.7
8) Please check to see if this is the most up to date version.
9) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.
10) To ensure that there are no improper bios settings please reset the bios.
11) Sometimes there can be failure to boot after resetting the bios.
12) Backup the computer files to another drive or to the cloud.
13) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free
14) And please create a brand new restore point.

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

15) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread
16) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread
17) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
> on the advanced tab under startup and recovery click settings > post an image of the startup and recovery into the thread.
> on the advanced tab under performance > click on settings > click on advanced tab > under virtual memory click on change > post an image of the virtual memory tab into the thread

18) Run this version of the log collector and post a zip into the thread:
log collector v2-beta08.zip

19) Run memtest86+ version 5.01 for at least 8 passes. Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 16 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM BSOD Tutorials

20) Read these links on Windows driver verifier.
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

21) Do not use Windows driver verifier until it is communicated in the thread.


Code: Event[9689]: Log Name: System Source: Display Date: 2018-01-08T17:11:37.360 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: Bryan-AMD Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote] Code: Event[9689]: Log Name: System Source: Display Date: 2018-01-08T17:11:37.360 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: Bryan-AMD Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote] Code: 1/19/2018 9:43 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 109 P2: a3a0205ac0c8b69c P3: 0 P4: 48539c66cfc9785e P5: 101 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\011918-7921-01.dmp \\?\C:\WINDOWS\TEMP\WER-15515-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5DDF.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5DFE.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E1E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_109_45a4ae8465d8a56da17af533d725817b767bed76_00000000_cab_23a06716 Analysis symbol: Rechecking for solution: 0 Report Id: b47e87be-4570-497d-8bea-03feee4b7df6 Report Status: 2049 Hashed bucket:1/19/2018 9:43 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 109 P2: a3a0205ac0c8b69c P3: 0 P4: 48539c66cfc9785e P5: 101 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\011918-7921-01.dmp \\?\C:\WINDOWS\TEMP\WER-15515-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5DDF.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5DFE.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E1E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_109_45a4ae8465d8a56da17af533d725817b767bed76_00000000_03305e2d Analysis symbol: Rechecking for solution: 0 Report Id: b47e87be-4570-497d-8bea-03feee4b7df6 Report Status: 4 Hashed bucket: 11/12/2017 8:38 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: deaddead P2: 1 P3: 2 P4: 19a9291a P5: 3c2a58ed P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\111217-6828-01.dmp \\?\C:\WINDOWS\TEMP\WER-31312-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER91C0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER91FF.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER922E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_deaddead_cef96ad2698425ecc9aaf0effec676ee0e7ac20_00000000_cab_108892d9 Analysis symbol: Rechecking for solution: 0 Report Id: def56c74-ec44-4c2f-b44d-3ce911b90898 Report Status: 2049 Hashed bucket: 11/12/2017 8:38 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: deaddead P2: 1 P3: 2 P4: 19a9291a P5: 3c2a58ed P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\111217-6828-01.dmp \\?\C:\WINDOWS\TEMP\WER-31312-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER91C0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER91FF.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER922E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_deaddead_cef96ad2698425ecc9aaf0effec676ee0e7ac20_00000000_033c922d Analysis symbol: Rechecking for solution: 0 Report Id: def56c74-ec44-4c2f-b44d-3ce911b90898 Report Status: 4 Hashed bucket: 12/15/2017 2:50 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ef P2: ffff84846a680080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\121417-8203-01.dmp \\?\C:\WINDOWS\TEMP\WER-21093-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6ADF.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B1D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B3E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_8e2841ead0cf8a6d7d13778aae566074e13619_00000000_cab_15686c08 Analysis symbol: Rechecking for solution: 0 Report Id: 72f3b9d8-66fd-42c9-8f57-4bad9f38c83f Report Status: 2049 Hashed bucket: 12/15/2017 2:50 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ef P2: ffff84846a680080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\121417-8203-01.dmp \\?\C:\WINDOWS\TEMP\WER-21093-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6ADF.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B1D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B3E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ef_8e2841ead0cf8a6d7d13778aae566074e13619_00000000_03306b3d Analysis symbol: Rechecking for solution: 0 Report Id: 72f3b9d8-66fd-42c9-8f57-4bad9f38c83f Report Status: 4 Hashed bucket: 1/5/2018 11:09 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ef P2: ffffd10a580255c0 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010518-8093-01.dmp \\?\C:\WINDOWS\TEMP\WER-15859-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER53DC.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER540B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER542B.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_809037f3581172c245bf369d58a076e0711e7552_00000000_cab_0d285505 Analysis symbol: Rechecking for solution: 0 Report Id: 75c9190b-3a5a-4f3a-8d17-6493070c61e9 Report Status: 2049 Hashed bucket: 1/5/2018 11:09 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ef P2: ffffd10a580255c0 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010518-8093-01.dmp \\?\C:\WINDOWS\TEMP\WER-15859-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER53DC.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER540B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER542B.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ef_809037f3581172c245bf369d58a076e0711e7552_00000000_0324542a Analysis symbol: Rechecking for solution: 0 Report Id: 75c9190b-3a5a-4f3a-8d17-6493070c61e9 Report Status: 4 Hashed bucket: 12/16/2017 2:17 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ef P2: ffffe20b1f68f340 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\121517-5843-01.dmp \\?\C:\WINDOWS\TEMP\WER-14609-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4BDD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4BFD.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C1D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_8d4e6ab4801e8de0fe6b76bd58fd3782b2aa6757_00000000_cab_17484cd7 Analysis symbol: Rechecking for solution: 0 Report Id: 676d5c9d-b855-44be-a53b-df218cd19e5d Report Status: 2049 Hashed bucket: 12/16/2017 2:17 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ef P2: ffffe20b1f68f340 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\121517-5843-01.dmp \\?\C:\WINDOWS\TEMP\WER-14609-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4BDD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4BFD.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C1D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ef_8d4e6ab4801e8de0fe6b76bd58fd3782b2aa6757_00000000_03284c1c Analysis symbol: Rechecking for solution: 0 Report Id: 676d5c9d-b855-44be-a53b-df218cd19e5d Report Status: 4 Hashed bucket:[/quote] Code: +++ WER6 +++:Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 141 P2: ffffc805335064a0 P3: fffff804e74c76c4 P4: 0 P5: 1dc8 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: +++ WER7 +++: Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 141 P2: ffffc805335064a0 P3: fffff804e74c76c4 P4: 0 P5: 1dc8 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: +++ WER8 +++: Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 141 P2: ffffc30bcb0d6010 P3: fffff801655b76c4 P4: 0 P5: 200c P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: +++ WER9 +++: Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 141 P2: ffffc30bcb0d6010 P3: fffff801655b76c4 P4: 0 P5: 200c P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10:[/quote]

 

@zbook

Going from your initial points, I decided to check if my video drivers were updated.

Turns out I wasn't using the latest drivers. After the update, I haven't experienced that BSOD anymore.

I freaked out over what occurred because I hadn't experienced a BSOD in nearly two-three years now.

Thank you for your assistance. I will mark the thread as solved but will post back if the issue resurfaces.