Windows 10 Home clean install BSOD Critical Structure Corruption

Old Dell inspiron Was running Windows 7, never had BSOD.

Clean installed Windows 10 Home 64bit, only has avast and used portable spybot a couple of times.

Drivers seem OK on device manager.

bluescreenviewer shows caused by ntoskrnl.exe

Memtest86 passed.

Advice needed please. Thank you.

• DESKTOP-UMSBIUQ-Mon_22_08_2016_172402_17.zip (204.4 KB, 2 views)

The dumps do not contain much useful information:

Code:

CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption: 1) A driver has inadvertently or deliberately modified critical kernel code  or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 2) A developer attempted to set a normal kernel breakpoint using a kernel  debugger that was not attached when the system was booted. Normal breakpoints,  "bp", can only be set if the debugger is attached at boot time. Hardware  breakpoints, "ba", can be set at any time. 3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.

Code:

OVERLAPPED_MODULE: Address regions for 'mslldp' and 'WUDFRd.sys' overlap PG_MISMATCH:  84F5E8EA0 CUSTOMER_CRASH_COUNT:  1 DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT BUGCHECK_STR:  0x109

You are running mismatched memory which can cause problems. Did you run memtest86 or memtest86+ and for how many passes. We prefer memtest86+ for a minimum of 8 passes like this:
===================================================
RAM:

Follow this tutorial: MemTest86+ - Test RAM - Windows 10 blog

   Information

MemTest86+is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

   Warning

MemTest86+needs to run for at least 8 passesto be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+by a windowssh blog member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

   Note

MemTest86+has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+just before you go to bed and leave it overnight.

Hi Ztruker,

Thanks for your quick reply. Your suggestion led me to suspect the experiment I did.

The RAM will not be the problem, though I haven't done 8 pass, only 3 pass done and I can't wait.

I was using the kon-boot to bypassing the password, so it must use a low-level driver to bypass the login password. Without kon-boot, the system running fine. But I haven't had problem on other Windows 10 and Windows 7 machine with kon-boot.

Would you be able to share a little bit more about the result you replied? I did a "grep" on the reported logs and didn't find the keywords "overlap" or "overlapped module".

Thanks.

The !sysinfo smbios command in windbg is what shows the ram data I looked at to see that you had mismatched memory.

Why do you need kon boot? There are ways to remove a password if you've forgotten it. It makes no sense to me at all to use a program like this? See here: How to enable the hidden Administrator account in Windows 8. For Windows 8, works with 10 as well.

Sorry been busy lately.

Yes, the kon-boot doesn't make sense to home users. As a tech we often get computers in and forget to ask their passwd. There are many tools you can reset passwd, some even able to find (guess) passwd by dictionaries, or you might simply create another admin user and do what you want. But you need to load user profiles to be able do things sometimes and kon-boot seems very handy without touching their passwd.

Anyway, thank you for the smbios stuff.

Hmmm, since I do a lot of tech work too, think I'll take a closer look at kon-boot.
Thanks for the info.