BSOD randomly browsing internet; ntoskrnl.exe

Please check inside the case for any dust, durt or anything that doesn't belong there and remove it.
Please make sure everything is seated properly, make sure to ground yourself before opening the case, if you haven't cleaned the system of dust recently.

I'll check the files when I wake up within a couple of hours, almost half past 12PM here.

Nvidia drivers again

Code:

fffff803`48d77680  fffff800`793b734dUnable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xe734d

But I would like to focus on old drivers for now.
These are the drivers not in 2015.

Code:

GPCIDrv64		Thu Jul 10 14:58:31 2008 (48760777)		GPCIDrv64.sys // Gigabyte driver
WPRO_41_2001		Mon Nov 07 22:04:48 2011 (4eb847f0)			WPRO_41_2001.sys
ew_jubusenum		Thu Nov 24 12:30:19 2011 (4ece2acb)			ew_jubusenum.sys
ISCTD64		Tue Nov 27 20:52:34 2012 (50b51a02)			ISCTD64.sys
HECIx64		Mon Dec 17 20:32:21 2012 (50cf7345)		HECIx64.sys
imsevent		Tue Jan 08 20:33:33 2013 (50ec748d)			imsevent.sys
ikbevent		Tue Jan 08 20:34:06 2013 (50ec74ae)			ikbevent.sys
mbam		Wed Sep 03 19:50:25 2014 (540754e1)			mbam.sys
SC808HDB64		Thu Dec 18 07:35:56 2014 (549275cc)		SC808HDB64.sys // audio driver

Please remove Gigabyte software

Driver Reference Table - WPRO_41_2001.sys
Driver Reference Table - ew_jubusenum.sys
Driver Reference Table - ISCTD64.sys
Driver Reference Table - HECIx64.sys
Driver Reference Table - imsevent.sys
Driver Reference Table - ikbevent.sys

Please reinstall Malwarebytes: https://support.malwarebytes.org/cus...5311?b_id=6438 & Malwarebytes | Free Anti-Malware & Internet Security Software
When removing Malwarebytes, license data will be removed as well, note any license data before removal.

I can't find driver updates for the audio driver, please check in device manager for driver updates.

Code:

Name	HD Audio PCI-e Audio Device
Manufacturer	C-Media Electronics Inc.
Status	OK
PNP Device ID	HDAUDIO\FUNC_01&VEN_13F6&DEV_8888&SUBSYS_13F60002&REV_1004\5&311B8301&0&0101
Driver	c:\windows\system32\drivers\sc808hdb64.sys (8.0.14.1218, 62,50 KB (64*000 bytes), 2015-11-24 20:55)

Looks like a networking crash, I would suggest to start with updating the network drivers via the site of the manufacturer of the network adapters.

I'll check the files tomorrow

Kaiketsu said:

I ran memtest86+ for 8 hours. No errors at all.

Going back to this, because the last crash was a read error.
Can you recall how many passes were completed?
If not 8 passes, I suggest to run MemTest86+ again.

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Code:

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8012d2a2b18, address which referenced memory

With all those USB drivers in the dumps it certainly looks like it yes.

Got a bsod, but it was netio again, so I'm guessing it's another "memory referenced" error.

Here it is. I'll run memtest today again.

Attachment 52677

EDIT: another NETIO.SYS crash, shortfly after the first one. Sigh.

Here's the 2nd netio crash:

Attachment 52692


EDIT2: and another, but NOT netio this time.
I think I had enough... if memtest shows nothing all i can do at this point is reinstall W10 from scratch.

Attachment 52696


USB referenced again when I only had mouse/keyboard/HDD....

GUESS IT MIGHT BE THE HDD Those things happened when it was in use.

I disconnected it for a while to see if it helps.