BSOD ntoskrnl.exe Windows 10 Issue

Joined
Nov 25, 2016
Messages
3
Reaction score
0
Recently I've been getting this error a lot and have been getting a lot of issues in regards to this BSoD, It only happens when i play certain (GPU intensive games) other than that, it rarely happens.

-I have run Memtest (but willing to give it ago again) and it all came back with no errors,
-Bios is up to date according to website and system info (unless i get BETA Bios which i don't really feel comfortable with).
chkdsk came back all normal.
- I think all drivers are up to date

I am just wondering if there could possibly be another conflict that may be causing this issue that i am not aware of.

Gigabyte GA-Z77X-D3H
16GB RAM
Nvidia GTX970
750W PSU
Samsung 250GB SSD
2TB HDD

My Dump file is attached.
 

Attachments

  • minidump.zip
    57.6 KB · Views: 380

Trouble

Noob Whisperer
Moderator
Joined
Nov 19, 2013
Messages
13,396
Reaction score
2,318
I think all drivers are up to date
There are some older drivers present that may need your attention
Code:
SiLib.sys            2/6/2007
AseUSBCC.sys            2/6/2007
WmXlCore.sys            4/27/2010
WmBEnum.sys            4/27/2010
PxHlpa64.sys            10/17/2011
mvxxmm.sys            1/19/2012
mvs91xx.sys            1/19/2012
HECIx64.sys            7/2/2012
iaStorA.sys            9/1/2012
L1C63x64.sys            7/16/2013
Armed with Google and some patience, see what you can find....
Updates / Upgrades, uninstall, etc.
Especially the Marvel drivers and the intel storage controller driver Gigabyte should have something newer on their support page for your board. Pay attention to the "Rev.#" and make sure you are getting the proper driver for your board's Revision Number.
 
Joined
Nov 25, 2016
Messages
3
Reaction score
0
Thanks for the reply,

SiLib.sys, AseUSBCC.sys and L1c63x64.sys cannot be updated as they are already the latest driver that supports my Motherboard Rev1.1
All the others have been updated to the latest that supports my motherboard.

I'll give it a go and i'll report back if the issue still persists.
 
Joined
Nov 25, 2016
Messages
3
Reaction score
0
Unfortunately a no go, it still crashes but this time it does not give me an error code of some sort, all it does is throws me
There are some older drivers present that may need your attention
Code:
SiLib.sys            2/6/2007
AseUSBCC.sys            2/6/2007
WmXlCore.sys            4/27/2010
WmBEnum.sys            4/27/2010
PxHlpa64.sys            10/17/2011
mvxxmm.sys            1/19/2012
mvs91xx.sys            1/19/2012
HECIx64.sys            7/2/2012
iaStorA.sys            9/1/2012
L1C63x64.sys            7/16/2013
Armed with Google and some patience, see what you can find....
Updates / Upgrades, uninstall, etc.
Especially the Marvel drivers and the intel storage controller driver Gigabyte should have something newer on their support page for your board. Pay attention to the "Rev.#" and make sure you are getting the proper driver for your board's Revision Number.


Unfortunately a no go, it still BSOD but without an error code now, it just shows up "something has happened" (or something along those lines) for a brief second and restarts the computer.
Is there anything i can submit to see what could be the underlining issue?

Also in regards to the old drivers only SiLib.sys and AseUSBCC.sys could not be updated as thats the driver for my CPU liquid cooling and they have no had an update on the software for a long while.
 

Trouble

Noob Whisperer
Moderator
Joined
Nov 19, 2013
Messages
13,396
Reaction score
2,318
it still BSOD but without an error code now
IS it still generating .dmp files.
it just shows up "something has happened" (or something along those lines) for a brief second and restarts the computer.
First make sure your machine is configured properly to facilitate the collection of .dmp files.
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top