ntoskrnl.exe and igdkmd64.sys

[gerenda110]

Hello!
I want to ask something.
1st, Sry my english.
2nd.
I have all Time BSOD in my Asus B250i Strix MOBO.
My first Bsod coming with Lan driver, i've tryd to update, but this ******* said, already up to date... (wtf???)
okay, my luck, have wi-fi on mobo, and i can now use net...... But i disabled in bios the intel lan.
Intel lan runned errors:
-ndis.sys (ndis+0x1CE91)code: 0x1000007E
-e1d65x64
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: IRQL_NOT_LESS_OR_EQUAL

This is the lan error.....

And now, i'll show the other....

On Thu 2017. 10. 12. 18:39:52 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101217-5921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 2017. 10. 12. 16:21:54 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101217-6140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x139 (0x3, 0xFFFFA700F7C4C8B0, 0xFFFFA700F7C4C808, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 2017. 10. 11. 20:24:05 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101117-5796-01.dmp
This was probably caused by the following module: igdkmd64.sys (igdkmd64+0x198F71)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80AC9538F71, 0xFFFFB981B2929B48, 0xFFFFB981B2929390)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_f10b0c0616a02072\igdkmd64.sys
product: Intel HD Graphics Drivers for Windows(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Wed 2017. 10. 11. 18:06:55 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101117-5843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xA (0x20000, 0x2, 0x1, 0xFFFFF801C007227B)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 2017. 10. 11. 17:26:32 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101117-6156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF802B3A65521, 0xFFFFC1015F755F40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


i'have try to update all of driver.... all is fresh... i want to broke this sh1t.... fresh windows....

And my memorys not have problem...

 

[googlyeyedchicken]

Have you updated all your drivers?

 

[Colif]

can you go to C:\windows\minidump
copy the files in this folder to desktop
Upload the copies from the desktop to a file sharing site and share links here.

 

[gerenda110]

here is the logs.
https://www.dropbox.com/s/08j1s64h3wrv0ys/101217-6140-01.dmp?dl=0
https://www.dropbox.com/s/wcqpikg0h4e076q/101117-5796-01.dmp?dl=0
https://www.dropbox.com/s/lou5auqif7qvkk9/101117-6156-01.dmp?dl=0
https://www.dropbox.com/s/vc98nrmzvawqtsy/101217-5921-01.dmp?dl=0
https://www.dropbox.com/s/9juyslfxyza3xr7/101217-5937-01.dmp?dl=0

 

[gerenda110]

Have you updated all your drivers?

yes, i have updated. with driver easy.

 

[gardenman]

Hi, I ran the dump file(s) through the debugger and got the following information: https://pste.eu/p/7Prs.html

Spoiler

File: 101217-6140-01.dmp (Oct 12 2017 - 10:21:54)
BugCheck: [KERNEL_SECURITY_CHECK_FAILURE (139)]
Probably caused by: ntkrnlmp.exe (Process: https://www.google.com/search?q=)
Uptime: 0 Day(s), 8 Hour(s), 42 Min(s), and 32 Sec(s)

File: 101217-5937-01.dmp (Oct 12 2017 - 13:48:49)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
*** WARNING: Unable to verify timestamp for ladfGSS.sys
Probably caused by: ladfGSS.sys (Process: https://www.google.com/search?q=)
Uptime: 0 Day(s), 0 Hour(s), 16 Min(s), and 44 Sec(s)

File: 101217-5921-01.dmp (Oct 12 2017 - 12:39:52)
BugCheck: [DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)]
Probably caused by: ntkrnlmp.exe (Process: https://www.google.com/search?q=)
Uptime: 0 Day(s), 2 Hour(s), 17 Min(s), and 40 Sec(s)

File: 101117-6156-01.dmp (Oct 11 2017 - 11:26:32)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: win32kbase.sys (Process: csgo.exe)
Uptime: 0 Day(s), 2 Hour(s), 07 Min(s), and 20 Sec(s)

File: 101117-5796-01.dmp (Oct 11 2017 - 14:24:05)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
*** WARNING: Unable to verify timestamp for igdkmd64.sys
Probably caused by: igdkmd64.sys (Process: https://www.google.com/search?q=)
Uptime: 0 Day(s), 2 Hour(s), 15 Min(s), and 56 Sec(s)

The BIOS information couldn't be read from the first dump file. This problem shows up sometimes when the BIOS is really outdated.

I can't help you with this. Wait for someone else to reply. Good luck.

 

[Colif]

You might want to update/remove srs_sscfilter_amd64.sys as its from 2009 - SRS Audio Sandbox driver
upgrade/remove AI Suite or PC Probe 2 or GPU Tweak as they all include AsIO.sys and its known to create BSOD... your copy is from 2012

Anything before 2015 isn't a windows 10 driver and could be causing these errors.

there are only 2 bios for your board so it might be case you have 0305, latest is 0809