BSOD i have tried everything i can think of.

[Rhion145]

I get BSOD when I try to stream from my pc to twitch. I have reset the whole computer including windows 10 and all my drivers. I have scanned for viruses and checked all my hardware to the best of my ability with no luck. (amd FX-8350 , radeon rx 460 videocard,16 gb ddr3 ram ipjaws, mb asrock 970A-G/3.1) dump files below https://1drv.ms/f/s!AiYI86xq2w4fhxdUNvBUxh6pt7jZ

 

[Rhion145]

the app charger should be disabled. ill double check that and uninstall Malwarebytes. it only does bsod when I use open broadcaster software or xsplit I have tried both. I get bsod when I capture a window( example if I was playing any type of game or video and capture it using those 2 apps I get bsod)

 

[Paul NZ]

App charger should be uninstalled / removed completely not disabled.

It does nothing but crash windows

 

[Rhion145]

ok the app charger and Malwarebytes are uninstalled completely

 

[Paul NZ]

Ok see if it crashes now. Hopefully it doesnt !

 

[Rhion145]

Crashed while doing the same thing as before. I ll get you the dump files after it restarts. The bsod is showing page fault in nonpaged area

 

[Rhion145]

here is the dump file https://1drv.ms/u/s!AiYI86xq2w4fhxyyhJ_rF-bdolS2

 

[Rhion145]

On Tue 12/20/2016 5:05:53 PM your computer crashed
crash dump file: C:\Windows\Minidump\122016-232437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD1, 0x2, 0xFFFFF80056F00E93, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Paul NZ]

So does it crash if you dont use twitch?? If it doesnt then it maybe a twitch prob

 

[Rhion145]

It crashes without using twitch. Just a game capture or a screen capture of video is enough to do it. When you add twitch into the factor it crashes faster. It crashes without streaming.

 

[Paul NZ]

Could be the video drivers, try uninstalling them then use ddu uninstaller in safe mode then reboot.

Then install the latest video drivers

 

[Rhion145]

I had the newest driver installed on the video card when this issue started then I went to a previous version. I'll try using ddu and downloading the newest driver again.

 

[Paul NZ]

Or if it's a brand GPU like ASUS / GB, get the driver off their site.

Sometimes installing the latest version isnt a good idea

I found that out when I installed this cheap Nvidia card. The only drivers that work properly are the ASUS drivers (it's an ASUS card) off their site.

If I install the latest / previous version drivers for it, on the Nvidia site, the browser crashes, the program/drivers stop responding and I get artifacts

 

[Rhion145]

Ok I delete and uninstalled my gpu driver loaded up safe mode and used the display driver uninstaller rebooted and downloaded the driver off of gigabytes website. my new dump is https://1drv.ms/u/s!AiYI86xq2w4fhx3eYzi_XzFVOcY1.

 

[Rhion145]

update I deleted my os and started new on a different hard drive. still getting the same blue screen. On Mon 1/2/2017 8:04:49 PM your computer crashed
crash dump file: C:\Windows\Minidump\010217-26250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0xD1 (0xFFFFD98000000001, 0xFF, 0x0, 0xFFFFD98000000001)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 1/2/2017 8:04:49 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0xFFFFD98000000001, 0xFF, 0x0, 0xFFFFD98000000001)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.