BSOD on boot 9/10 times, IQRL and KMODE on ntoskrnl.exe

Minidumps I have:
minidumps - Google Drive

Win Version 20H2 Build 19042.746.

It's a 2018 Matebook X Pro, thought the BSODs were caused by liteon ssd so I've replaced it but still happening, also did a fresh install but it's still happening, so it might be huawei drivers or some other driver I've reinstalled. Last is the ram which is soldered on so I can't replace it.

I can still get into windows after it boot loops a couple times, it's a pattern between the IQRL error and then KMODE exception and then 0xc100000e. I've tried the fix mbr commands and tried startup repair from Windows Media USB but it always says startup repair fails. The SRT trail log file for the startup repair is attached, says it can't find the hard disk. But it's a brand new Samsung nvme ssd and windows boots 1 out of 5-10 tries.

Please help I've tried everything! The reason I don't think it's the ram is because when its running it will run everything fine for hours/days with no trouble, but the only BSOD's I get are on wake up from sleep/hibernate and on startup/restart.

Seems like it could be a RAM issue which is a challenge when RAM is soldered onto the motherboard.
Perhaps load up a copy of Ubuntu onto a usb stick and try booting from that. That way you will know if its a hardware issue or a Windows issue.

I ran the Tune Up Bat file and results are pasted below:

I don't think its ram if I don't have any problems once its booted, and if it is RAM that means I just have to get a new machine.


###########################################################
# The following commands will be run in sequence. #
# The first 5 will take quite a while to run, be patient. #
###########################################################

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow

chkdsk /scan

wmic recoveros get autoreboot
wmic recoveros set autoreboot = false
wmic recoveros get autoreboot
wmic recoveros get DebugInfoType
wmic recoveros set DebugInfoType = 7
wmic recoveros get DebugInfoType

wmic pagefile list /format:list
wmic Computersystem where name="MATEBOOK-X-PRO" get AutomaticManagedPagefile
wmic Computersystem where name="MATEBOOK-X-PRO" set AutomaticManagedPagefile=True
wmic Computersystem where name="MATEBOOK-X-PRO" get AutomaticManagedPagefile

bcdedit /enum {badmemory}


C:\windows\system32>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:\windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.746

Image Version: 10.0.19042.746

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

C:\windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.746

Image Version: 10.0.19042.746

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

C:\windows\system32>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:\windows\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
603904 file records processed.
File verification completed.
Phase duration (File record verification): 7.56 seconds.
10731 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.53 milliseconds.

Stage 2: Examining file name linkage ...
3584 reparse records processed.
778790 index entries processed.
Index verification completed.
Phase duration (Index verification): 21.57 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 685.79 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 1.22 milliseconds.
3584 reparse records processed.
Phase duration (Reparse point and Object ID verification): 11.74 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 51.46 milliseconds.
87444 data files processed.
Phase duration (Data attribute verification): 1.40 milliseconds.
CHKDSK is verifying Usn Journal...
40752736 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 348.70 milliseconds.

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

487458775 KB total disk space.
159445372 KB in 301976 files.
219420 KB in 87445 indexes.
0 KB in bad sectors.
730863 KB in use by the system.
65536 KB occupied by the log file.
327063120 KB available on disk.

4096 bytes in each allocation unit.
121864693 total allocation units on disk.
81765780 allocation units available on disk.
Total duration: 30.24 seconds (30249 ms).

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


C:\windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\MATEBOOK-X-PRO\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

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


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


C:\windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\MATEBOOK-X-PRO\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

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


C:\windows\system32>wmic pagefile list /format:list


AllocatedBaseSize=1728
CurrentUsage=100
Description=C:\pagefile.sys
InstallDate=20190622160456.921285-360
Name=C:\pagefile.sys
PeakUsage=102
Status=
TempPageFile=FALSE




C:\windows\system32>wmic Computersystem where name="MATEBOOK-X-PRO" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\windows\system32>wmic Computersystem where name="MATEBOOK-X-PRO" set AutomaticManagedPagefile=True
Updating property(s) of '\\MATEBOOK-X-PRO\ROOT\CIMV2:Win32_ComputerSystem.Name="MATEBOOK-X-PRO"'
Property(s) update successful.

C:\windows\system32>wmic Computersystem where name="MATEBOOK-X-PRO" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


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

RAM Defects
-----------
identifier {badmemory}
Press any key to continue . . .

- - - Updated - - -

I tried Ubuntu usb it boots up fine

- - - Updated - - -

Just finished memtest86 with no errors and Ubuntu usb works fine. I have a feeling it's a driver but can't figure out which one. I've checked huawei's pc manager and it says all drivers are up to date. Updated nvidia driver manually as well.

Please see posting instructions:
BSOD - Posting Instructions

zbook said:

Please see posting instructions:
BSOD - Posting Instructions

Attachment 316505Attachment 316505

1) Uninstall Avast using the applicable uninstall tool:
Avast Uninstall Utility | Download aswClear for Avast Removal

2) Make a new restore point

2) Modify the Windows Driver Verifier (DV) customized tests from 3 to 11 customized tests

Code:

  Standard Flags:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [X] 0x00000010 I/O verification.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [X] 0x00000200 Force pending I/O requests.
    [X] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

Add

Code:

    
    [ X] 0x00000001 Special pool.
    [X ] 0x00000002 Force IRQL checking.
    [X ] 0x00000008 Pool tracking.
    [ X] 0x00000020 Deadlock detection.
    [ X] 0x00000080 DMA checking.
    [ X] 0x00000100 Security checks.
    [X ] 0x00000800 Miscellaneous checks.
    [ X] 0x00020000 DDI compliance checking.

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


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

Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are ran in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) after each BSOD use the reset command to turn off the tool
e) if the reset command does not work then use the bootmode command
f) only if both reset and bootmode command fail to turn off the tool then use restore
g) start with the 3 customized test settings in the Ten Forums link
h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
i) report any performance problems or very slow boot so that the customized settings can be modified


For any BSOD:

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

Thanks will do first thing tomorrow, had a feeling it was avast so I used their tool to clear it, it crashed upon restart AFTER the uninstall but so far no bsods for 3-restarts.

There were no comments on Windows DV in the opening post.

1) Uninstall Malwarebytes using the applicable uninstall tool:
https://downloads.malwarebytes.com/file/mb_clean


2) Uninstall Kaspersky AV using the applicable uninstall tool:
https://support.kaspersky.com/common/uninstall/12783


3) Uninstall and reinstall:
logi_joy_bus_enum.sys
Logitech G HUB Virtual Bus Enumerator

Code:

logi_joy_bus_enum	Logitech G HUB Virtual Bus Enumerator Driver	c:\windows\system32\drivers\logi_joy_bus_enum.sys	Kernel Driver	Yes	Manual	Running	OK	Normal	No	Yes

Logitech Support + Download
Logitech: Wireless Mouse, Keyboards, Headsets & Video Conferencing
Topics – Logitech Support + Download


4) For Windows DV frozen at 100% > power off > run V2


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


5) Restart DV
Customize by selecting all tests except:
[ ] (0x00000004) Randomized low resources simulation

Code:

logi_joy_bus_enum.sys Tue Nov 20 09:28:21 2018 (5BF42815)