[SOLVED] BSOD - Stop Code:Critical_structure_corruption CI.dll failed

[gempor]

Hi guys, I've been experiencing frequent BSOD since 19th august 2022 and up until I wrote this it's already happened 5 times.

This BSOD happened so randomly and most of the times were while idling and as for today it happened when my pc was on sleep mode (it wakes just for the bsod)

PC specs:
AsRock b450 Pro4
ryzen 3500x
ram 16gb ddr4 2667mhz clock speed
rx 5700 xt 8gb
Seagate firecuda SSHD 2TB + 1TB
adata su650 240GB m2 sata
Crucial MX250 1tb connected with enclosure through USB C port

troubleshooting i already did:
sfc check (no error)
disk check (no error)
mem diagnostic check (no error)
reverting vga driver from 22.8.1 to 22.5.1 (stable ver)
try to idle my pc while downloading for 2 days, no BSOD.

what happened before BSOD:
I update my windows 10 on 14th august and I didn't open my pc frequently until 19th august so this could be the triggerer.

dmp file by bluescreen viewer:
==================================================
Dump File : 090522-7687-01.dmp
Crash Time : 5/9/2022 6:09:44 pm
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : a39ffdd90386088f Parameter 2 : b3b70a5f5607b417
Parameter 3 : fffff80753256390 Parameter 4 : 0000000000000001
Caused By Driver : CI.dll
Caused By Address : CI.dll+56390
File Description : Code Integrity Module
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.19041.1706 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3f88c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\090522-7687-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 19041
Dump File Size : 1,019,388
Dump File Time : 5/9/2022 10:22:31 pm
==================================================

any help would be great. Thanks in advance

 

[Fix_that_Glitch]

If you updated windows it may have loaded crappy AMD drivers. Try using ddu uninstall for amd drivers. Display Driver Uninstaller Download version 18.0.5.4 (guru3d.com) Then install non beta, recommended AMD drivers and see if it stops. I would also try setting your windows power setting to high performance if it isn't already.

 

[gempor]

If you updated windows it may have loaded crappy AMD drivers. Try using ddu uninstall for amd drivers. Display Driver Uninstaller Download version 18.0.5.4 (guru3d.com) Then install non beta, recommended AMD drivers and see if it stops. I would also try setting your windows power setting to high performance if it isn't already.

windows power setting always on energy savings since I built this pc from 2020 and I've never experienced any BSOD before 19th august.
I'll try DDU 1st, thank you for your suggestions, i'll try to keep this post updated.

 

[Colif]

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
   
2. Navigate to C:\Windows\Minidump
   
3. Copy the mini-dump files out onto your Desktop
   
4. Do not use Winzip, use the built in facility in Windows
   
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
   
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
   
7. Then post a link here to the zip file, so we can take a look for you . . .
   

 

[gempor]

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

https://drive.google.com/file/d/179rlwq8w07uKSZYnD9UThY3zuK-41Pjs/view?usp=sharing

 

[Colif]

conversion of dump file
results - click run fiddle to see results

File: 090522-7687-01.dmp (Sep 5 2022 - 21:09:44)
BugCheck: [CRITICAL_STRUCTURE_CORRUPTION (109)]
Probably caused by: CI.dll (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 47 Min(s), and 12 Sec(s)

Comment: 2 or more types of RAM are installed.

how long you used 2 different sticks of ram?
8gb Hynix
8gb V gen

That could be cause if you only just started using those 2 together recently.

Possible causes:
not sure what this is, its age tells me it might not be win 10

Aug 29 2012

dfx12x64.sys

Explore Systems Virtual Audio Device (Power Technology)

This doesn't know what Ryzen was last time I checked

Dec 30 2012

speedfan.sys

SpeedFan http://www.almico.com/sfdownload.php

This can cause crashes - used for Play station & Xbox controllers

May 06 2013

ScpVBus.sys

Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus driver http://forums.pcsx2.net/

You probably don't need this

Dec 20 2018

idmwfp.sys

Internet Download Manager WFP driver (Tonec Inc.)

Could update Bios, you 5 versions behind - https://www.asrock.com/mb/Amd/B450 Pro4/#BIOS

 

[gempor]

2 different sticks of ram since may 2022, I'll try remove all the drivers you listed. as for bios, I'll wait until the next BSOD happened (hope it wont happen again though)

 

[gempor]

conversion of dump file

new BSOD appeared, this time got different error code for the 1st time since 19th august https://drive.google.com/file/d/1DxkWY43d2ePmda9LJ2fgAt4l7EodfwUG/view?usp=sharing

 

[Colif]

Holds off celebrating a new BSOD until he gets conversion
oh good, it wasn't one I didn't want to see.

results - click run this fiddle to see them

File: 090622-9859-01.dmp (Sep 6 2022 - 22:01:31)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 18 Hour(s), 57 Min(s), and 16 Sec(s)


Error stack text appears to be all cpu operations, no storage actions or ram mentioned. it was all on CPU.
Mainly file actions from what I can tell. No driver names, but that is normal.
I have worked all this out as I go along and sometimes I get results that make me wonder what its doing.

Which stick of ram is the newer one?
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

I just want to be sure its not the ram causing it.

 

[gempor]

Holds off celebrating a new BSOD until he gets conversion
oh good, it wasn't one I didn't want to see.


Which stick of ram is the newer one?
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

I just want to be sure its not the ram causing it.

hynix is the newer one, about memtest86, do I need a bootable drive / flashdisk? i've run windows mem diagnostic and everything came out clean but i'll still do the memtest as you say. Thanks again

 

[Colif]

Yes, it needs to run off flash as windows locks some memory up and won't give access, so running it without windows running means its all free.

 

[gempor]

6 days since the last BSOD appeared.

This is what i've done so far:
uninstall gpu driver using DDU and then reinstall it -> different BSOD appeared (fltmgr with system thread exception not handled error)
replace ram and use the same ram stick for dual channel -> fltmgr no longer happened

Seems the BSOD completely disappeared by now. I'll keep this post updated if something else happened