SYSTEM THREAD EXCEPTION NOT HANDLED Windows 10 CI.dll

[David_A]

Hello,

Well
Well I comment, I have almost three months ago a pc with these components.

CPU: i5-6600
Motherboard: MSI B150M PRO-VH
Ram: x2 HYPERX 4GB 2133MHZ DDR4 CL13 DIMM
VGA: MSI RX 480 8GB
SSD: 275GB SSD MX300 SATA 2 5 Kingston
HDD: Western Digital Blue 1TB Sata3 3.5' 7200rpm
PSU: EVGA 600W 80 Plus Certificada
Cabinet: Versa N21
WINDOWS 10

The first month did not present any problem, until one morning when I turned it on I threw myself a BSOD.

KMODE EXCEPTION NOT HANDLED (CI.dll) and then SYSTEM THREAD EXCEPTION NOT HANDLED (CI.dll)


Try everything until I did a clean install of Windows 10, always having the same error.

Disassemble and reassemble everything, always having the same result.
Send the parts under warranty, except hard drives and PSU. As a result they told me that they had no problems, I reassembled the pieces and I was able to work with my computer as before, play and everything, until I returned to present the same problem. That if every time I started and presented the BSOD this happened 3 or 4 times and then continued normal.

Do until one day, memtest, without errors. CHKDSK without errors. Processor without errors (intel software).

I bought another board (MSI h110m) and another Ram (Crucial 8GB 2133). Always the same result, can install windows 10, but when doing the reboot to finish installing the BSOD appears and fall in a infinite loop.

Please help me, and sorry for my english.

 

[Colif]

Getting conflicting info on what ci.dll is
Its either part of alcohol 120 - The process known as Alcohol (version 120%) belongs to software Alcohol (version 120%) by Alcohol Soft Development Team (www.alcohol-soft.com).

Or

Its part of windows vista -

Code Integrity (CI) protects Windows Vista by verifying that system binaries haven’t been tampered with by malicious code and by ensuring that there are no unsigned drivers running in kernel mode on the system. CI starts as Windows starts up. The boot loader checks the integrity of the kernel, the Hardware Abstraction Layer (HAL), and the boot-start drivers. After these binaries have been verified, the system starts and the memory manager calls CI to verify any binaries that are loaded into the kernel’s memory space. The binaries are verified by looking up their signatures in the system catalogs. Aside from the kernel memory space, CI verifies binaries loaded into a protected process and system installed dynamic libraries that implement core cryptographic functions.

https://www.windowsbbs.com/threads/bsod-at-startup-ci-dll-missing-or-corrupt.65990/

I have seen ci.dll isn't a win 10 file so I am not sure which of those it actually is.

Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
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
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

dump files might help more than me trying to figure out for you.

 

[Paul NZ]

Where did windows come from?

 

[smorizio]

with just oinboard video do you get the same error?? if the power supply 12v is noisy it can cause issues. have you run hardware info 64 biit checked 12v rail output.

 

[David_A]

Where did windows come from?

Direct from microsoft

 

[David_A]

with just oinboard video do you get the same error?? if the power supply 12v is noisy it can cause issues. have you run hardware info 64 biit checked 12v rail output.

The same error, Even with the new motherboard and RAM. 🙁

 

[Paul NZ]

It looks like this file can also get corrupted, by a rootkit.

I would either try and get into safe mode or connect the hdd to another desktop

Then run tdsskiller. See if it picks up any rootkits

The site is slow as

 

[David_A]

It looks like this file can also get corrupted, by a rootkit.

I would either try and get into safe mode or connect the hdd to another desktop

Then run tdsskiller. See if it picks up any rootkits

The site is slow as

BSOD shows up, every clean install.

 

[Paul NZ]

It maybe a rootkit on the bootblock of the hdd then. Thats where rootkits can hide

Thats what tdsskiller does remove it

Got a spare hdd you could try and install windows on? See if that works

Whats on the WD hdd?? If it's empty unplug the ssd. And try to install on that

 

[David_A]

It maybe a rootkit on the bootblock of the hdd then. Thats where rootkits can hide

Thats what tdsskiller does remove it

Got a spare hdd you could try and install windows on? See if that works

Whats on the WD hdd?? If it's empty unplug the ssd. And try to install on that

-i run the tdsskiller and no virus on both disks.
-i try the wd hdd and no difference. 🙁

 

[David_A]

Getting conflicting info on what ci.dll is
Its either part of alcohol 120 - The process known as Alcohol (version 120%) belongs to software Alcohol (version 120%) by Alcohol Soft Development Team (www.alcohol-soft.com).

Or

Its part of windows vista -

Code Integrity (CI) protects Windows Vista by verifying that system binaries haven’t been tampered with by malicious code and by ensuring that there are no unsigned drivers running in kernel mode on the system. CI starts as Windows starts up. The boot loader checks the integrity of the kernel, the Hardware Abstraction Layer (HAL), and the boot-start drivers. After these binaries have been verified, the system starts and the memory manager calls CI to verify any binaries that are loaded into the kernel’s memory space. The binaries are verified by looking up their signatures in the system catalogs. Aside from the kernel memory space, CI verifies binaries loaded into a protected process and system installed dynamic libraries that implement core cryptographic functions.

https://www.windowsbbs.com/threads/bsod-at-startup-ci-dll-missing-or-corrupt.65990/

I have seen ci.dll isn't a win 10 file so I am not sure which of those it actually is.

Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
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
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

dump files might help more than me trying to figure out for you.

thanks my friend.

I'll try and tell you how it goes.

 

[David_A]

Hello,

I run the repair system tool from the windows 10 installation CD. and show me this.

C:\WINDOWS\System32\Logfiles\Srt\SrtTail.txt

I save the file in the USB.

Diagnóstico de Reparación de inicio y registro de reparación
---------------------------
Número de intentos de reparación: 1

Detalles de la sesión
---------------------------
Disco del sistema = \Device\Harddisk1
Directorio de Windows = C:\Windows
Comprobación automática = 0
Número de causas principales = 1

Prueba realizada:
---------------------------
Nombre: Buscar actualizaciones
Resultado: Se completó correctamente. Código de error = 0x0
Tiempo invertido = 0 ms

Prueba realizada:
---------------------------
Nombre: Prueba de disco del sistema
Resultado: Se completó correctamente. Código de error = 0x0
Tiempo invertido = 0 ms

Prueba realizada:
---------------------------
Nombre: Diagnóstico de errores de disco
Resultado: Se completó correctamente. Código de error = 0x0
Tiempo invertido = 16 ms

Prueba realizada:
---------------------------
Nombre: Prueba de metadatos de disco
Resultado: Se completó correctamente. Código de error = 0x0
Tiempo invertido = 0 ms

Prueba realizada:
---------------------------
Nombre: Prueba de sistema operativo de destino
Resultado: Se completó correctamente. Código de error = 0x0
Tiempo invertido = 203 ms

Prueba realizada:
---------------------------
Nombre: Comprobación de contenido de volumen
Resultado: Se completó correctamente. Código de error = 0x0
Tiempo invertido = 15 ms

Prueba realizada:
---------------------------
Nombre: Diagnóstico del administrador de arranque
Resultado: Se completó correctamente. Código de error = 0x0
Tiempo invertido = 16 ms

Prueba realizada:
---------------------------
Nombre: Diagnóstico de registro de arranque del sistema
Resultado: Se completó correctamente. Código de error = 0x0
Tiempo invertido = 0 ms

Prueba realizada:
---------------------------
Nombre: Diagnóstico de registro de eventos
Resultado: Se completó correctamente. Código de error = 0x0
Tiempo invertido = 0 ms

Prueba realizada:
---------------------------
Nombre: Comprobación de estado interno
Resultado: Se completó correctamente. Código de error = 0x0
Tiempo invertido = 0 ms

Prueba realizada:
---------------------------
Nombre: Prueba de estado de arranque
Resultado: Se completó correctamente. Código de error = 0x0
Tiempo invertido = 0 ms

Prueba realizada:
---------------------------
Nombre: Comprobación de estado de la instalación
Resultado: Se completó correctamente. Código de error = 0x0
Tiempo invertido = 47 ms

Found root cause:
---------------------------
Error during installation was in progress.

(i have spanish windows 10 iso, directly from microsoft page)

 

[James Mason]

Found root cause:
---------------------------
Error during installation was in progress.

 

[Colif]

Can you boot off the installer, and on second screen after language choices, choose repair this PC, not install.
Choose Troubleshoot > Advanced Options > Command Prompt.
When Command Prompt opens, enter the following:
C:
cd Windows\System32\LogFiles\Srt
SrtTrail.txt

After the file opens, you should see something like this: Boot critical file c:\windows\system32\drivers\vsock.sys is corrupt. We have to mention that this is just an example as you will mostly likely get a different result. Tell us what you find.

or is that what is shows above? I can't see any file names there?

thank you for translation, James

 

[David_A]

Can you boot off the installer, and on second screen after language choices, choose repair this PC, not install.
Choose Troubleshoot > Advanced Options > Command Prompt.
When Command Prompt opens, enter the following:
C:
cd Windows\System32\LogFiles\Srt
SrtTrail.txt

After the file opens, you should see something like this: Boot critical file c:\windows\system32\drivers\vsock.sys is corrupt. We have to mention that this is just an example as you will mostly likely get a different result. Tell us what you find.

or is that what is shows above? I can't see any file names there?

thank you for translation, James

I already did that, I wrote it earlier. The srttrail.txt file just tells me this.

Found root cause:
---------------------------
Error during installation was in progress.

 

[Colif]

so helpful. thanks microsoft...

one common fix I found for this was to fix the mbr but that seems strange as you done multiple fresh installs. Wonder if its the ssd
have you tried to install onto hdd at all? if we can get windows onto PC or if you can put ssd into another PC as 2nd drive, could run https://www.kingston.com/en/support/technical/kingston-ssd-toolbox on it and check its health, software includes tests.

 

[David_A]

so helpful. thanks microsoft...

one common fix I found for this was to fix the mbr but that seems strange as you done multiple fresh installs. Wonder if its the ssd
have you tried to install onto hdd at all? if we can get windows onto PC or if you can put ssd into another PC as 2nd drive, could run https://www.kingston.com/en/support/technical/kingston-ssd-toolbox on it and check its health, software includes tests.

I tried installing windows on both disks. Always with the same result. 🙁


Can I create a dump file by cmd? And so review it for ubuntu live.

 

[James Mason]

What if it's your installation media that's wrong?
Try making a new Windows installed dvd/usb.

 

[okcnaline]

Can you go to C:\Windows\minidump and upload the files there?

 

[David_A]

What if it's your installation media that's wrong?
Try making a new Windows installed dvd/usb.

i'll try.

 

[David_A]

Can you go to C:\Windows\minidump and upload the files there?

When I login for ubuntu, I can not find that folder. Maybe he is not. Because the installation has not finished.

 

[okcnaline]

Oh, you reinstalled? Never mind.

 

[David_A]

How can I tell if my processor has problems?

As I have tried: disks, ram, motherboard. 🙁

I can install windows 7 but no game works, everything is unstable.

 

[okcnaline]

Are you still getting BSODs or applications crashing?

 

[David_A]

Are you still getting BSODs or applications crashing?

With windows 7 I do not have BSOD, but I can not run games, show up error. I also do not recognize the video card. How do I know if my VGA is damaged? I have image but device manager says standard VGA graphics card.