bsod notskrnl.exe help

Solution
look at these changes below, most do not have a direct connection to your bugcheck. The minidump does not contain the proper debug info for your problem.
so, try the updates/remove drivers and see if you hit the problem again. if you do, change the memory dump type to kernel memory dump
and provide the c:\windows\memory.dmp file after the next crash. It will contain the debug info to see what happened.

https://support.symantec.com/en_US/article.howto31321.html


-----------
you have a current BIOS dated 6/29/2016, this will just not be good with your old 2011 USB drivers. Your BIOS has the various updates to support the fixes and standards updated in 2012 and in 2013 but you still have the old USB drivers installed.

pick up the...
Hello... Here is the Windows debug screen... easier to read.
You NEED to be logged on as administrator to the OS...

let's see what the OS is reporting as the error... Right click computer-manage-System Tools-Windows logs-system.... Click on the "RED" errors, for more information... and files/drivers/Apps, comments/suggestions/information associated with them B )

Posting screen images from here will help me, help you faster... But copy and posting text will work too B )
 

MrWhiskey282

Commendable
Jul 22, 2016
6
0
1,510
not sure if this is what you wanted but here's the last couple events before the crash https://drive.google.com/open?id=0Bx2hDe3_O5VqZGFXX1VKLXlJYkU



 

MrWhiskey282

Commendable
Jul 22, 2016
6
0
1,510
full specs
CPU AMD FX-630

RAM 16.0GB Single-Channel DDR3 @ 665MHz (9-9-9-24)

Motherboard ASRock 970 Pro3 R2.0

GPU AMD Radeon R9 380

Storage 2TB Seagate hard drive

nothing is overclocked
I ran a stress test on my CPU that turned up nothing, and did a 4 hour long memtest which also yielded nothing
the blue screens only happen when I play more demanding games like rust or xcom 2 and never happen on lower tier games or just gneral computer use



 
look at these changes below, most do not have a direct connection to your bugcheck. The minidump does not contain the proper debug info for your problem.
so, try the updates/remove drivers and see if you hit the problem again. if you do, change the memory dump type to kernel memory dump
and provide the c:\windows\memory.dmp file after the next crash. It will contain the debug info to see what happened.

https://support.symantec.com/en_US/article.howto31321.html


-----------
you have a current BIOS dated 6/29/2016, this will just not be good with your old 2011 USB drivers. Your BIOS has the various updates to support the fixes and standards updated in 2012 and in 2013 but you still have the old USB drivers installed.

pick up the updates from http://www.asrock.com/mb/AMD/970%20Pro3%20R2.0/?cat=Download&os=Win764
your motherboards usb system will run better.

you have the driver for Atheros network adapter driver (assume this is a wifi card, not usb based)

remove or update(used to override the max current on the USB port)
\SystemRoot\system32\DRIVERS\AsrAppCharger.sys Tue May 10 01:28:46 2011

remove cFosSpeed - The Internet Accelerator
\SystemRoot\system32\DRIVERS\cfosspeed6.sys Wed May 29 09:47:24 2013

remove:
non standard turbo USB, most likely will not work correctly with current bios versions.
\SystemRoot\System32\drivers\FNETURPX.SYS Wed May 30 20:00:47 2012

old
\SystemRoot\system32\DRIVERS\usbfilter.sys Tue Dec 13 23:44:02 2011 (this should get updated with the motherboard chipset update)

install your motherboard ethernet driver or disable the hardware in BIOS.
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
----------------
looks like you had GameOverlayUI.exe accessing some service, the service broke and caused a bugcheck.
I assume the service exit was related to a network card being installed or removed.
I think the tool does chat functions and web access.

also looks like a network driver was being installed at the same time Rt64win7.sys

lots of issues with the OS installed on this machine.

machine info:
BIOS Version P2.80
BIOS Starting Address Segment f000
BIOS Release Date 05/31/2016
Manufacturer ASRock
Product 970 Pro3 R2.0
Processor Version AMD FX(tm)-6300 Six-Core Processor
Processor Voltage 8ch - 1.2V
External Clock 200MHz
Max Speed 3500MHz
Current Speed 3500MHz







Rt64win7.sys

 
Solution


also, can u post an image of ur system rating...in detail???
 

MrWhiskey282

Commendable
Jul 22, 2016
6
0
1,510
most of those red errors are from skype for some reason. I hardly doubt skype is the reason my computer's os is killing itself.

also no red or yellow marks in my device manager



 

MrWhiskey282

Commendable
Jul 22, 2016
6
0
1,510
https://drive.google.com/open?id=0Bx2hDe3_O5VqZml6OGtxR0E1Xzg

link to latest crash while playing xcom.