BSOD Critical Structure Corruption

Hi,

I am not a techie person but am hoping someone can help. I have an older Lenovo desktop computer that keeps giving Critical Structure Corruption in clean boot, hardware clean boot and normal state. It works fine in Safe Mode. I recently upgraded from Win 7 with the Media Creation tool. Never had any problems with computer with Win 7. The minute I upgraded I started getting this message. In anything but Safe Mode I get BSOD about once an hour. No common thread of when it happens. This is what I have tried:

(Windows 10 version 1909)
Memory Diagnostic Tool--everything fine
System File Checker--all fine
DISM Image Restore Health--all fine
Lenovo Hardware diagnostics--all fine
Intel Diagnostic Tool-passed
All drivers updated

Graphics look fine. One thing that is strange is that in Device Manager under Monitor it says in events that
"Device DISPLAY\ACR02D7\1&8713bca&0&UID0 was not migrated due to partial or ambiguous match.
Last Device Instance Id: DISPLAY\ACR02D7\4&1F2A392B&0&UID16843008
Class Guid: {4d36e96e-e325-11ce-bfc1-08002be10318}
Location Path:
Migration Rank: 0xF00000000000F100
Present: true
Status: 0xC0000451"

Could that be the source of my problem? However all looks great on monitor, programs run fine, machine seems quieter and more efficient on Win 10 except for this hourly Critical Structure Corruption error. I have not tried reinstalling Windows as it hasn't seemed to help others with this problem. I am not a gamer, we just use this for internet and basic stuff. I know it is older but it has been perfect up to this point!

Power supply checked. Inside of computer checked, dust bunnies removed. I used your program and zip file is attached.

Any help is really appreciated!

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) 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

13) Uninstall Driver Easy and any drivers installed by this software

14) Open Ccleaner > click windows tab or custom clean > scroll down to system and advanced > post an image into the thread

15) Read these links on Windows driver verifier: (learn how to use the windows recovery environment (RE) commands reset and bootmode to turn off the tool) (do not use the tool until it is communicated in the thread)


Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

16) Post a share link for any memory.dmp that is < 1.5 GB

Code:

LastWriteTime       Size (MB) FullName             
-------------       --------- --------             
2/7/2020 5:54:31 PM    534.49 C:\WINDOWS\MEMORY.DMP

17) open device manager > click view > click show hidden devices > manually expand all rows > look for any row displaying a yellow triangle with black exclamation mark or unknown device > post images into the thread

Hi-thx so much for your input. I have done steps through 1-14. I uninstalled Driver Easy but didn't uninstall drivers that it put in yet. I double checked with the Intel Driver diagnostic and it didn't find anything wrong a few days ago. In Device Manager I looked at some and I don't have the option of rolling it back to the previous. Also the Critical Structure Corruption error was happening before I installed Driver Easy just in case it matters.
______________________________________________________________________
Microsoft Windows [Version 10.0.18363.592]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\Karen>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Users\Karen>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.592

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Users\Karen>
C:\Users\Karen>
C:\Users\Karen>
C:\Users\Karen>
C:\Users\Karen>
C:\Users\Karen>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.592

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Users\Karen>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Users\Karen>chkdsk /scan
The type of the file system is NTFS.
This service cannot be started in Safe Mode

A snapshot error occured while scanning this drive. Run an offline scan and fix.

C:\Users\Karen>
Microsoft Windows [Version 10.0.18363.592]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
614144 file records processed.
File verification completed.
11141 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
17903 reparse records processed.
753836 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
17903 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
69847 data files processed.
CHKDSK is verifying Usn Journal...
37231400 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

1926432837 KB total disk space.
396943836 KB in 400110 files.
229280 KB in 69848 indexes.
0 KB in bad sectors.
789721 KB in use by the system.
65536 KB occupied by the log file.
1528470000 KB available on disk.

4096 bytes in each allocation unit.
481608209 total allocation units on disk.
382117500 allocation units available on disk.

C:\WINDOWS\system32>
C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\KAREN-DESKTOPPC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\KAREN-DESKTOPPC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


:\WINDOWS\system32>
C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\WINDOWS\system32>

CC Cleaner: I am having trouble putting up screenshot, but the only things checked under System and Advanced are temp files, Clipboard, and Chkdsk File Fragments"

I am afraid of Driver Verifier and need to create a USB just in case so i will do that and update later.

For any driver that had been installed by any third party softwre please install a new driver directly from the Lenovo website:
desktops and all in ones :: ideacentre k series desktops :: ideacentre k410contentdetail - US

When available please post a share link for C:\windows\memory.dmp


Take Screenshot in Windows 10

How to Upload and Post Screenshots and Files at Ten Forums


Make a new restore point:
Create System Restore Point in Windows 10

Make a free backup image using Macrium and save the image to another disk drive or the cloud:
Macrium Software | Your Image is Everything
Backup and Restore with Macrium Reflect


For a bootable windows 10 iso:
Find a flash drive that you can format (> or = 8 GB)
https://www.microsoft.com/en-us/soft...load/windows10
Download Windows 10 ISO File
Create Bootable USB Flash Drive to Install Windows 10

Send full memory dump (MEMORY.DMP in C:\Windows)

Ok, I have done most of what was recommended. Sorry for the delay...we had a power outage here today.

What I did do since last update was to enable Driver Verifier. It promptly crashed the system and said:
"Attempted Write to Read Only Memory:
What failed: iaStorA.sys"

I had to restart with Ctrl/F8 and go into Safe Mode so I could upload resulting zipped Memory Dump file:
MEMORY (2).zip - Google Drive

I did go to Lenovo site and was ready to download drivers, but wasn't sure where they should go. It kept offering a default of a D: driver and other subfolder which didn't make sense so I didn't do that. Should I just download them into the Windows/system32/drivers folder?

I am in over my head here so please bear with me. Hopefully you can learn something from the Memory Dump file and other error messages?

Many, many thanks!

Please update post #2 step #17.

And update the steps in post #4.



https://answers.microsoft.com/en-us/...0-8d22254aa1c1


Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of


For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive


Boot into Safe Mode on Windows 10

Attachment 266417

And there were no yellow or exclamation points in Device Manager....just a long list of items repeated which I don't understand why.
Attachment 266418
Attachment 266419
Attachment 266420
Attachment 266421

I did zip the last full Memory Dump and uploaded it to Google Drive. Link was in previous post. Did it not work? Although I can reboot into normal state to really use computer without BSOD Crit Struc Corrup I need to stay in safe mode.

Please update the status:

a) new restore point
b) Macrium backup image
c) bootable Windows 10 iso 1909


For windows driver verifier:

learn how to use the windows recovery environment to run the reset and bootmode commands

The tool is designed to stress drivers.
Misbehaving drivers typically cause BSOD.

If there are BSOD with dump files they can be debugged.

Plan to use the tool for 48 hours and then for an additional 36 hours after the last BSOD.

After each BSOD you will need to turn off the tool.
When back on the desktop run V2 and upload results into the thread.
If memory.dmp is < 1.5 GB post a separate share link into the thread.

The customized settings must be entered at the start or each use of the tool.
Start with the 3 customized simultaneous customized tests in the Ten Forums link.
If there are no BSOD then increase the number of simultaneous customized tests by 3 - 5 / hour up to the 19 in the Microsoft link.


Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Sometimes while using the tool there can be performance problems and slow boots.
If this happens the number of simultaneous customized tests can be modified.

The tool can be started when:
a) a new restore point has been made
b) a free Macrium backup image has been made
c) the Macrium image has been saved to another disk drive or the cloud
d) you understand how to use Windows Recovery Environment (RE) commands (reset and bootmode) to turn off the tool

Hi. I did load a link to a full Memory.dmp file two posts ago. Driver Verifier does not run in the background....I set it up as described as in your first link to Enable and Disabling Driver Verifier. It just crashes the computer. The computer is worse now than when we started so I appreciate your input and time but I think I need to just live with it in safe mode for now. I have given a lot of info and you haven't been able to diagnose anything yet--just don't want to get in over my head and have this unusable. If you are able to give me any clues as to what this might be that would be helpful, but after the last crash it was hard to going again. The full memory dump file I posted was the one after the BSOD the first time with driver verifier. Thanks again for looking into this, sorry I am not really versed in this stuff.