@wilfriedd
I need some debug information.
But you need to install Windows 10(1607) and my mod. You'll receive the error with Code 43.
Then go to Windows Logs->Application
Find last event with a source is Windows Error Reporting and a name is LiveKernelEvent
Show this.

Zitat von DeathBringer im Beitrag #226

---

@wilfriedd
I need some debug information.
But you need to install Windows 10(1607) and my mod. You'll receive the error with Code 43.
Then go to Windows Logs->Application
Find last event with a source is Windows Error Reporting and a name is LiveKernelEvent
Show this.

---

Zitat von wilfriedd im Beitrag #227

---

But i have win 10 20h2 .

---

Zitat von DeathBringer im Beitrag #228

---

Zitat von wilfriedd im Beitrag #227

---

But i have win 10 20h2 .

---

At first try to use current version.

---

Zitat

---

Errors , type 0
Name ;: LiveKernelEvent
Réponse : Non disponible
ID de CAB : b0997a89-4b3f-44e4-8c03-8ecbb52ff75b

Error signature;:
P1 : 193
P2 : 804
P3 : ffffffffc00002b9
P4 : 108
P5 : fffff80257cc7934
P6 : 10_0_19042
P7 : 0_0
P8 : 256_1
P9 :
P10 :

Joint files;:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210302-2307.dmp
\\?\C:\Windows\TEMP\WER-3748687-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER486D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER487E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER487D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER489D.tmp.txt

Files maybe available here :
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_193_b3e9d99fcaacb3a1bf862052b72fedd4a617b320_00000000_cab_6f8a38a8-2fbe-4e75-9929-a7de1fd86df9

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : 6f8a38a8-2fbe-4e75-9929-a7de1fd86df9
Statut du rapport : 4
Récipient avec hachage :
GUID CAB :0

---

When i look at "details tab" next to the first

Zitat

---

- System

- Provider

[ Name] Windows Error Reporting

- EventID 1001

[ Qualifiers] 0

Version 0

Level 4

Task 0

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2021-03-02T22:17:23.1280444Z

EventRecordID 18019

Correlation

- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel Application

Computer DESKTOP-J7L6OAU

Security


- EventData


0
LiveKernelEvent
Not available
b0997a89-4b3f-44e4-8c03-8ecbb52ff75b
193
804
ffffffffc00002b9
108
fffff80257cc7934
10_0_19042
0_0
256_1


\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210302-2307.dmp \\?\C:\Windows\TEMP\WER-3748687-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER486D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER487E.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER487D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER489D.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_193_b3e9d99fcaacb3a1bf862052b72fedd4a617b320_00000000_cab_6f8a38a8-2fbe-4e75-9929-a7de1fd86df9

0
6f8a38a8-2fbe-4e75-9929-a7de1fd86df9
4

0

---

Some terms are in French but overall , you can see the whole details

@wilfriedd
Thx!
That's very useful:
P3 ffffffffc00002b9

C00002B9 - STATUS_NOINTERFACE

Please do the same with new test mod - https://drive.google.com/file/d/1cELWSIN...4BhlRvSjZSNHIT/

I did it. This didn't work.
But unlike first Time, I'm not able to recover my graphics. So I can't see anything and I can't access my computer since all is black.

What I could do is try to reboot from a restore point. But this will erase all files logs.

@wilfriedd
Try to boot in safe mod to see logs.

Zitat von DeathBringer im Beitrag #232

---

@wilfriedd
Try to boot in safe mod to see logs.

---

Zitat

---

GENERAL INFORMATIONS :

Errors , type 0
Event Name : LiveKernelEvent
Réponse : Non disponible
ID de CAB : ae34a5b3-2d31-4a9e-bcdf-ebb12b3ffcbf

Problem :
P1 : 193
P2 : 804
P3 : ffffffffc00002b9
P4 : 108
P5 : fffff80660f47934
P6 : 10_0_19042
P7 : 0_0
P8 : 256_1
P9 :
P10 :

Joint files :
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210303-0846.dmp
\\?\C:\Windows\TEMP\WER-34356500-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER530D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER531D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER531C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER533C.tmp.txt

Ces fichiers sont peut-être disponibles ici :
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_193_e0b192f77f2797ec78d5c54924522ced0b541b7_00000000_cab_828b0809-f99e-4464-bae1-c82e2bd75da2

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : 828b0809-f99e-4464-bae1-c82e2bd75da2
Statut du rapport : 4
Récipient avec hachage :
GUID CAB :0


--------------------------------

DETAILS

- System

- Provider

[ Name] Windows Error Reporting

- EventID 1001

[ Qualifiers] 0

Version 0

Level 4

Task 0

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2021-03-03T07:47:20.5588248Z

EventRecordID 18139

Correlation

- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel Application

Computer DESKTOP-J7L6OAU

Security


- EventData


0
LiveKernelEvent
Non disponible
ae34a5b3-2d31-4a9e-bcdf-ebb12b3ffcbf
193
804
ffffffffc00002b9
108
fffff80660f47934
10_0_19042
0_0
256_1


\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210303-0846.dmp \\?\C:\Windows\TEMP\WER-34356500-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER530D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER531D.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER531C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER533C.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_193_e0b192f77f2797ec78d5c54924522ced0b541b7_00000000_cab_828b0809-f99e-4464-bae1-c82e2bd75da2

0
828b0809-f99e-4464-bae1-c82e2bd75da2
4

0

---

@wilfriedd
It's rather stange - the same error.
Are you sure that you used new igdkmd64.sys?

Try with second version of test mod - https://drive.google.com/file/d/1fDfUpgY...Qi2XJ9xXAoQMJ4/

yeah , i replaced both files with yours in google drive .

Ok now testing v2 .

Okay !

I've tested your mod . Unfortunately , I keep encountering the BSOD with igdkmd64.sys involved. So it's a different behaviour .

Booting in Safe mode doesn't help , since for this one , no log recorded . So we can't analyze any log .

Btw i think that we don't have any logs because when installing the drivers, the blue screen appeared BEFORE the end of install . It's like having a corrupt file before the end , that means the install did not complete and windows doesn't have the whole problem in hand . That's my thought

ps : You can see the Blue screen capture ( in French) , on the bottom you can clearly see the file igdkmd64.sys involved with " System Service Exception"

@wilfriedd
Bad news...
Now I haven't ideas how to fix it.
Please post full ID string for your Intel graphics with SUBSYS_ and REV_.

Do you agree to do a lot of tests in Windows 7?

@DeathBringer

My UHD GRAPHIC CARD :

VALUE : PCI\VEN_8086&DEV_9BC4&SUBSYS_22128086&REV_05\3&11583659&0&10

COMPATIBLE IDs :

PCI\VEN_8086&DEV_9BC4&REV_05
PCI\VEN_8086&DEV_9BC4
PCI\VEN_8086&CC_030000
PCI\VEN_8086&CC_0300
PCI\VEN_8086
PCI\CC_030000&DT_9
PCI\CC_030000
PCI\CC_0300&DT_9
PCI\CC_0300

I absolutely have no problem testing on WIN 7 , since i'm on dual boot and all my files are on Win 10 ..

@wilfriedd
OK. Install in Windows 7 my common mod - Win 7 x64 Coffee Like UHD 630 Video driver (8)
Get Code 43
Download and unpack my 3rd test mod - https://drive.google.com/file/d/1lYCzY9O...k1IOuRjP_-tKSF/
Copy igdkmd64.sys from subfolder with name 1 to \Windows\system32\drivers
Reboot.

If you get BSOD then stop and tell me about it.
If no BSOD and you get Code 43 again then copy igdkmd64.sys from subfolder with name 2 to \Windows\system32\drivers
Reboot.

If you get BSOD then stop and tell me about it.
If no BSOD and you get Code 43 again then copy igdkmd64.sys from subfolder with name 3 to \Windows\system32\drivers
Reboot.

BSOD or Code 43 now?

Hello!
No luck, after first test ( using. Sys file in folder 1), the computer keeps rebooting and rebooting again because of BSOD with igdkmd64.sys involved.
Just went back with a restore point.