Windows 10 BSOD, driver issue??


New Member
I'm getting frequent BSOD. I suspect it is a driver issue, I've gone through and tried to install all the correct drivers and that has reduced the BSOD significantly, although I still get them.

I don't think it is a RAM issue, I ran memtest86 and the windows memory diagnostic tool which both reported no errors.

I ran verifier to try and find the faulty drivers, I'll attach 3 dump files along with the MSInfo32 file and a copy and paste of my systeminfo. I hope someone can help me to identify the culprit!

Thanks so much in advance


  • BSOD Debugging
    871.3 KB · Views: 291
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck C1, {fffff90165492fb0, fffff90165492442, 5f4050, 23}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ndis.sys ( ndis!ndisDoOidRequests+118 )

Followup:     MachineOwner
a driver is writing to an invalid section of the special pool.

I see your using:
Intel® NUC Kit NUC6i7KYK

The drivers for this can be downloaded as a bundle here:
Downloads for Intel® NUC Kit NUC6i7KYK

See if updating helps and please post any new dump files.

Is there any clue to which driver it could be? I've installed all the drivers from the link you provided previously but to no avail. If I could find the problem driver I might try installing previous versions in case the latter happens to be instable. Otherwise I'm out of ideas...

Thanks for the help so far by the way, greatly appreciated!
WdFilter.sys is mentioned in the first dump file and is a system file to do with defender. Running these scans may help in this regard:

File scans
Open a 'admin command prompt' and type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.

The only driver I saw mentioned (which wasn't windows based) is this one:

Netwtw06.sys = Intel wifi driver? Do you use anything wifi related?