Windows 10: bsod playing rust(has been a few differant error codes)

have been experiancing bsod's for the last few days on rust (game either spits the dummy or it bsod's)

have a funny feeling it may be linked to my gpu or something else could be the cause, not entirely sure but if i was i wouldnt be here posting this now would i haha

thanks in advance to who ever comes to my rescue on this.

Attachment 94617

:)

 

BSOD troubleshooting help

Hello and thanks in advance you your help and knowledge. I have been getting hard BSOD crashes constantly while playing Rust the last couple of days. I don't know if this is related, but a new patch just game out for the game and it started after that.
I get the BSOD with a message 90% of the time that says IRQL NOT LESS OR EQUAL and a couple of times it has given me KERNAL SECURITY CHECK FAILURE. 95% of the crashes have been while playing rust, sometimes after only 5 minutes, other times after a couple
of hours. I have crashed as well from the desktop with BSOD while not in rust at all a couple times; those times have been usually right after the computer restarts after the first crash.

Things I've done so far:

-verified Rust local game files on Steam

-Rolled back Nvidia driver to older version

-uninstalled and reinstalled realtek sound driver

-unplugged all peripherals including controllers and usb headset (except mouse and keyboard)

-Reset BIOS to default settings (i didn't have anything overclocked anyway but just in case)

-lots of swearing

I have put a link to my 16 dump files and my MSinfo32 file on OneDrive here:

DMP files

MSinfo32

Thanks so much in advance!

 

Windows 10 BSOD (driver irql, clock watchdog)

Both Drivers have now been updated. BSOD crashes are far more infrequent but the freezing/lockups/hangs, remain, and they don't provide a dump file as far as I know.

The game I was playing at the time (Rust) recovered from one of them and created a few files, including a .dmp, I will upload all of the files in a zip and maybe that will help you diagnose it. (This is the first time it has recovered from the freeze, and
actually generated anything,it normally results in a reboot)

Here is a link to the dumpfiles generated by the game: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

 

8/6 11:11 dump indicates a problem with nvlddmkm.sys:
Code: BugCheck A, {202a, 2, 0, fffff801df0e4d3a} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiProcessPresentHistoryToken+fc )[/quote] dxgmms2.sys is considered the probable cause but very unlikely. This is a Microsoft module which is part of DirectX support.

You have the latest available Nvidia driver so not much you can do there other than try some of the older ones.

The dump also indicated qa problems with athuw8x.sys:
Code: fffff801`e0ce7fc8 fffff800`ef78c201Unable to load image \SystemRoot\System32\drivers\athuw8x.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for athuw8x.sys *** ERROR: Module load completed but symbols could not be loaded for athuw8x.sys athuw8x+0x2ac201[/quote] This belongs to your Qualcomm Atheros wireless device, which is pretty old and needs to be updated:
Code: 5/14/2013 2:06:43 PM C:\Windows\system32\drivers\athuw8x.sys[/quote] See this web page: Windows 10 Compatibility for TP-LINK Products
see if there is a newer driver for the device.

 

dxgmms2.sys is considered the probable cause but very unlikely. This is a Microsoft module which is part of DirectX support.

You have the latest available Nvidia driver so not much you can do there other than try some of the older ones.

The dump also indicated qa problems with athuw8x.sys:
Code: fffff801`e0ce7fc8 fffff800`ef78c201Unable to load image \SystemRoot\System32\drivers\athuw8x.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for athuw8x.sys *** ERROR: Module load completed but symbols could not be loaded for athuw8x.sys athuw8x+0x2ac201[/quote] This belongs to your Qualcomm Atheros wireless device, which is pretty old and needs to be updated:
Code: 5/14/2013 2:06:43 PM C:\Windows\system32\drivers\athuw8x.sys[/quote] See this web page: Windows 10 Compatibility for TP-LINK Products
see if there is a newer driver for the device.[/quote]

iv recently pulled a memory stick and issue has been fixed, my wifi adaptor is on my to do list as it pops up as an issue alot and il be buying something newer to replace it as the driver they list on the site doesnt supourt my adaptor for some reason