Windows 10: BSOD when stream

Hello guy and i say thank you for reading my message !
I start to stream recently and my pc start to have BSOD

I check reinstall all window and Bios, i make a memtest + Oc test intelburn occt realbench. And nothing, everything is fine. SO what can i do?
I get other bsod like this : IRQL NO LESS OR EQUAL/KMODE_EXCEPTION_NOT_HANDLED /kernel mod heap corruption.
I hope i make all you need
I am french sorry for my english T-T

AGAIN THX FOR YOUR TIME <3

Minidump file :https://1drv.ms/u/s!Al4MpciF7T5_iXMi5ncCggS6-ub6?e=ju5nZL

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Wed 11/11/2020 00:24:02 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111120-10843-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0x1E 0xFFFFFFFFC0000005, 0xFFFFF803379FD147, 0x0, 0xFFFFFFFFFFFFFFFF
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating thermal issue or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 11/11/2020 00:24:02 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: rt64.sys rt640x64+0x26A28
Bugcheck code: 0x1E 0xFFFFFFFFC0000005, 0xFFFFF803379FD147, 0x0, 0xFFFFFFFFFFFFFFFF
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating thermal issue or because of a buggy driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rt64.sys .
Google query: rt64.sys KMODE_EXCEPTION_NOT_HANDLED



On Tue 10/11/2020 23:36:13 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111020-7953-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0x1E 0xFFFFFFFFC0000005, 0xFFFFF804527FD147, 0x0, 0xFFFFFFFFFFFFFFFF
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating thermal issue or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 10/11/2020 18:34:13 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111020-8265-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0x1E 0xFFFFFFFFC0000005, 0xFFFFF80666FFD147, 0xFFFFFB074B2ABE98, 0xFFFF808076FF9920
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating thermal issue or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 08/11/2020 23:40:43 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110820-8468-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0x1E 0xFFFFFFFFC0000005, 0xFFFFF8035F1FD147, 0xFFFF828798288E98, 0xFFFFA10074C46920
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating thermal issue or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 08/11/2020 22:38:40 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110820-9375-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0x1E 0xFFFFFFFFC0000005, 0xFFFFF80680DFD147, 0xFFFF920377A74D18, 0xFFFFC280A4DAD920
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating thermal issue or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

:)

 

Adobe flash will not play Xfinity stream on Win10pro

Hi,

Thank you for writing to Microsoft Community Forums.

I understand that you are facing an issue with Xfinity stream due to Adobe Flash player. We will look into this for you. However, in order to get clarity and to assist you with appropriate steps, please reply with the answers to
the questions below.

1. Which browser are you facing this issue with, apart from Firefox?
   
2. Have you checked if the Flash player is enabled on your browser?
   
3. Was there any major change or an update on your system, prior to which you weren’t facing this issue?
   

Meanwhile, I would suggest you to follow the steps below and check if it is helpful to you.

Steps to unblock Adobe Flash Player:

1. Login to Xfinity streaming on your browser.
   
2. If there is a lock sign on the left or right end of the URL/address bar, click on it.
   
3. Scroll down to find Adobe Flash Player and click on Unblock.
   
4. You should be able to stream once the Flash Player is Unblocked.
   

I would also suggest you to refer the article on
Flash Player Help by Adobe and check if it is helpful to you.

Kindly follow the suggestions and get back to us with the results.

We await your response.

Aaron Summith

Microsoft Community – Moderator

 

Xbox One Streaming

Hi Dylan,

Incorrect configuration setting is one of the possible reasons why you are unable to stream on your Xbox One S. For us to properly assist you, we need to gather more details. Kindly answer the questions below:

• When was the last time you were able to stream from your Xbox One S?
• Have you tried using a different computer and check if the issue persists?
• What are the troubleshooting steps you have done so far?

Meanwhile, we suggest that you run the troubleshooter for Windows apps using the link below. This can help remove conflicts with an app from Microsoft Store.

Click here

You may also check the link below for troubleshooting steps.

Troubleshooting Xbox app game streaming on Windows 10

 

BSOD while playing WOW or watching streaming video


With help from @axe0 it appear you Daemon Tools installed

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.

Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below
   
   
   
   
   
   
   
   
   If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window.