Windows 10: BSOD playing OldSchool Runescape while watching YouTube/Twitch

Hey guys,

I've been having BSOD's once to twice a week since I upgraded to Windows 10 around 10 months ago. I also installed a new CPU cooler (Kraken x61) at the same time so it's hard to isolate it to windows 10. My PC also freezes sometimes too and I have to restart, it's not heat related though as my processor never really goes above 40 degrees Celsius.

The BSOD's and screen freezes have started happening way more frequently recently and WhoCrashed ​always tells me it's likely to do with a driver. I've tested all my drivers on many occasions and windows device manager tells me everything is up to date. The drivers AMD say are for Windows 10 for my motherboard (Sabertooth 990FX) are the same as the windows 7 drivers, so maybe my motherboard is the issue.

The common BSOD's I get:

• MEMORY_MANAGEMENT
• PAGE_NOT_FOUND (or something to that effect)
• KMODE_EXCETPTION_NOT_HANDLED

A common example of my most frequent BSOD:

On Mon 26-Sep-16 3:53:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\092616-9968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0B0)
Bugcheck code: 0x1A (0x41793, 0xFFFFCC800003AFF8, 0x200, 0x1FF)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


I ran memtest86+ around 6 months ago and it didn't find anything concerning (I think). Also my PC has 16GB's of RAM but I often see from PC spec detecting software that the physical memory is 16GB but that only around 10GB-12GB are actually usable or something. I've attached the TF folder, thanks for reading *Smile

:)

 

Windows 10 stuttering.

And today, for no reason at all, while watching a twitch stream i had a bsod. On a 4 day old installation that was made fresh btw.

 

Blue screen ( sad face ) "hardware problem" on Youtube or twitch or Netflix

hi there . while i was watching youtube or twitch or Netflix or playing video game i run into blue screen with sad face and its telling me about factually hardware problem . any help ? thx

Moved from Virus & Malware

Original title: blue screen ( sad face )

 

Hi njeksey,

Do you still need help?

 

Hey, so I found out in the BIOS that my PC was only seeing 12GB of RAM when I had 16GB installed, also on the "System" page on Windows 10 it was saying "16GB RAM (11.9GB Usable)". After swapping them round a bit and testing each RAM individually i managed to get my PC to now detect all 16GB of RAM. Since then it's been fine, but who knows if that was the reason? I've purposefully had loads of tabs open and multiple YouTube videos to test if my PC is now fully stable and I've had no crashes thus far *Smile

Could one of the RAM sticks not being pushed in properly be the cause of my BSOD's?

Thanks for the reply axe0

 

Basically, yes because data cannot be saved properly in such a case and possibly corrupt the data because it can't be saved properly.

 

Hi, I can't believe it but I just got another BSOD *Sad

It happened as I was taking a printscreen, I also had multiple tabs open including twitch streams and a game open. Guess the issue isn't solved and it is some underlying driver issue. This is what WhoCrashed says for this crash:

On Thu 20-Oct-16 12:05:22 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102016-10250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF801B3B6DD90, 0x0, 0xFFFF9A0D47594DD8)
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 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.


Any help would be much appreciated *Smile

 

Please read How to upload files

 

Hey Axe, there are minidumps attached on my initial post. By the way I found out that the BSOD's were caused by only PrintScreening, when i pressed PrintScreen it would 100% BSOD. I did some research and this was because I still had a debug setting turned on in the boot advanced settings found in system configuration. Now that I disabled debug in the advanced boot settings it no longer BSOD's. But yeah it would be great if you could have a look at the minidumps I attached in my initial post *Smile

 

The issue with those dumps is that they are from 16th this month, the zip doesn't have the dump of today. If I provide analysis from those dumps I cannot provide suggestions for possible solutions for the crash of today.

 

It would be cool if you could just analyse those because the crash i had recently i've been able to resolve myself *Smile I have to turn off my anti-virus in order for the TenForums tool to work so i'm not keen on doing it again if I dont have to.

 

That's a false positive from your AV, all the tool does is run some commands from a .bat file (through command prompt in other words) to collect information that is present on your system.

Looking at the zip it appears to be incomplete, a few important files are missing.

 

Ok I've done it *Smile can I attach it in this thread or do I need to make a new post?

 

They all look quite similar, some may have a few differences.

I have seen the following software/drivers re-occuring:

• Razer drivers,
• Nvidia display drivers,
• Your protection software,
• Chipset drivers

Assuming the somewhat older crashes were also occuring when you had the debugging configuration enabled I personally do not see a direct reason to provide suggestions.

 

Thank you so much! I only enabled the debugging configuration 2 days ago, but I believe the other crashes could've been the result of the RAM stick not being fully pushed in, I hope so at least *Biggrin