Windows 10: BSOD playing overwatch or while not having all fans on max settings

Hello,
I have been experiencing BSOD while playing overwatch and on any game when I do not have all my fans on maximum velocity settings.
I thought it was the CPU cooler doing a poor job so I bought a new noctua cooler in hopes of fixing the problem but it did not work.

I have updated the zip file to the new english file.

Thank you for your help,
.

:)

 

BSOD While Playing Overwatch & While Streaming (Ntoskrnl.exe & "KMODE_Exception_Not_Handled")

Hi,

Thank you for providing a detailed and complete description of the issue. The Kmode_exception_not_handled error can sometimes be caused by missing drivers. For us to fix this issue, we recommend to install the missing drivers by following these steps:

1. Press Windows Key + X then choose Device Manager from the menu.

2. When Device Manager opens, find any unknown devices, right click them and choose Update Driver Software.

3. Choose "Search automatically for updated driver software." If that doesn’t work, you may want to try the "Browse my computer for driver software" option instead.

4. After you’ve installed all the missing drivers, check if the issue is resolved.

Get back to us if you need further assistance.

 

BSOD While Playing Overwatch & While Streaming (Ntoskrnl.exe & "KMODE_Exception_Not_Handled")

Alright, so I have a home built Desktop, runs fine about... 90% of the time... but when I play a handful of games, or Stream online, I get a BSOD that points to "Ntoskrnl.exe" as the cause after using WhoCrashed. Occasionally
I'll get "Kernel_Security_Check_Failure" or "KMODE_Exception_Not_Handled" as well.

The crashes aren't immediate: when playing Overwatch, I tend to get a good 20-30 minutes of play in before the BSOD occurs.

I've uploaded the most recent dump, if anyone could take a look and see what they can find... I'm at a loss... it's getting pretty frustrating.

Specs:

Motherboard: ASRock Z97 Pro4 LGA 1150 Intel Z97 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard

Processor: Intel Core i7-4790k

RAM: 16 GB

Video Card: Radeon R9 390 (8GB)

DUMP: 110317-4937-01.dmp

 

Hi Ronark,
2 of the 3 bsod memory dumps indicate possible memory problems.
Run memtest86+ version 5.01 for at least 8 runs. This may take many hours so plan to run it overnight.
Memtest86+ - Advanced Memory Diagnostic Tool
The number of runs is important. It sometimes takes runs in the teens to find faulty RAM.

The logs are in a foreign language and I cannot read them. If you can create English logs we can read then and troubleshoot problems.

 

Hello, thank you so much for your fast reply.
I'm sorry I did not notice that it was in portuguese.
I have changed my windows 10 language to english and re-created the logs. I hope this fixed the language problem.
I will leave memtest running all night and get back to you with results tomorrow.

Thank you,
.

 

Code: BugCheck 124, {0, ffffa10a3f140028, be000000, 40110a} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : GenuineIntel[/quote] Code: BugCheck 50, {fffff80355acd0a0, 10, fffff80355acd0a0, 2} Could not read faulting driver name Probably caused by : memory_corruption[/quote] Code: BugCheck 3B, {c000001d, fffff80f6851229c, ffffb70187e1fad0, 0} Probably caused by : memory_corruption[/quote] Ronoark,
The language change is better but incomplete: Repair option: A reinicializar o adaptador de rede sem fios
Isto irá desativar e, em seguida, ativar o adaptador de rede "Wi-Fi" neste computador.
Whatever you can post in English will be helpful to interpret the information.

In device manager view network, wifi, Bluetooth, etc. Look in properties then driver to find any Intel drivers. Uninstall the intel drivers and replace the drivers with up to date drivers from the computer manufacturer's web site or from Intel.

 

Hello,
Memtest is still running currently at 6 and no errors so far.
The translation of that phrase is:
"Rebooting the wireless network adapter which will deactivate it and then activate the wifi adapter in this computer"
If you could tell me where to look I can translate it all if needed *Smile
I will uninstall all my intel drivers and reinstall them from intel's website as soon as memtest is done.
Do you think there is a chance that it might be faulty hardware or high temps making the blue screens happen?

Thank you so much for all your help,

 

When Memtest86+ version 5.01 completes at least 8 runs please post an image into the forum.
When you uninstall the Intel drivers they will likely default to Microsoft drivers.
Then you will find the most up to date compatible drivers for your computers configuration and operating system.
Sometimes the new drivers have not been completely tested for each hardware component and in those cases going to an older version may be needed.

Today there was another minidump:
Code: BugCheck 124, {0, ffffa10a3f140028, be000000, 40110a} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : GenuineIntel[/quote] When memtest86+ is complete open administrative command prompt and type or copy and paste these commands:

1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) chkdsk /scan

Please post the results into the thread.

4) Turn Windows fast startup off:
Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

We may need to stress test the hardware.

 

Memtest86+ version 5.0.1 ran a total of 8 times (it showed pass:8), it ran for 14 hours and showed 0 errors. I did not take an image of it before pressing esc to exit the program because I did not see your message in time.

Here is the result of the scans you asked me to run:

1) sfc /scannow
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.

2) dism /online /cleanup-image /restorehealth
Image Version: 10.0.14393.0
[==========================100.0%==========================]
Error: 0x800f081f
The source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature.
For more information on specifying a source location, see MSN.com - Hotmail, Outlook, Skype, Bing, Latest News, Photos Videos DISM log file can be found at C:\Windows\Logs\DISM\dism.log

3)
C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
496128 file records processed.

File verification completed. 15959 large file records processed. 0 bad file records processed.

Stage 2: Examining file name linkage ...
608724 index entries processed.
Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...
Security ID 0x979 is non-existent and unused ... queued for offline repair.
Security descriptor verification completed. 56299 data files processed.CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Windows has found problems that must be fixed offline.
Please run chkdsk /spotfix to fix the issues. 243618815 KB total disk space. 235262384 KB in 392992 files. 247964 KB in 56300 indexes. 0 KB in bad sectors. 573371 KB in use by the system. 65536 KB occupied by the log file. 7535096 KB available on disk. 4096 bytes in each allocation unit. 60904703 total allocation units on disk. 1883774 allocation units available on disk.

4) I ran the command it said to run to fix the issues:
C:\Windows\system32>chkdsk /spotfix
The type of the file system is NTFS.
Cannot lock current drive.Chkdsk cannot run because the volume is in use by anotherprocess.
Would you like to schedule this volume to bechecked the next time the system restarts? (Y/N) Y
This volume will be checked the next time the system restarts.


I have rebooted the computer and it said scanning and reparing drive C: 100% complete.

I have also turned off the windows fast startup (it was already off).

I'm having some trouble with the drivers. I could not find any intel drivers under network, wifi or bluetooth.
The only things that show intel as the device controller's manufactor are under system devices:
- The chipset (around 7 different things referencing chipset)
- Intel(R) management engine interface
- Intel host controllers (around 4)
- Intel(R) Xeon(R) Guassian Mixture Controller and PCIe Controller

I think that's all, should I uninstall those?

Thank you so much for all your help and time *Smile

 

open administrative command prompt and type or copy and paste this command:
chkdsk /x /f /r
The chkdsk command may take many hours to run so plan to run it overnight.

In the morning post the chkdsk report into the thread:

Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
CHKDSK: What is it and how do I run it? - Ask Leo!
Manually Reset or Clear Dirty Bit in Windows without using CHKDSK • Raymond.CC - Page 2
How do I see the results of a CHKDSK that ran on boot? - Ask Leo!
How to find chkdsk results in Windows 10 - Winaero uses 26226 find


Whatever you find in device manager or control panel you should be able to uninstall. For replacement drivers it is best to use the computer manufactures approved downloads or from Intel® Driver Update Utility
Download Intel® Driver Update Utility
Windows® 10 Support Information

 

I ran the chkdsk command, it didn't take much time.
Here are the results:

Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.Windows will now check the disk.

Stage 1: Examining basic file system structure ...
496128 file records processed. File verification completed.
15954 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
608916 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...
Cleaning up 27 unused index entries from index $SII of file 0x9.
Cleaning up 27 unused index entries from index $SDH of file 0x9.
Cleaning up 27 unused security descriptors.
Security descriptor verification completed. 56395 data files processed.

CHKDSK is verifying Usn Journal...
12599064 USN bytes processed. Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
496112 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
1897766 free clusters processed.
Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

243618815 KB total disk space.
235193388 KB in 393587 files.
248200 KB in 56396 indexes.
0 KB in bad sectors.
586163 KB in use by the system.
65536 KB occupied by the log file.
7591064 KB available on disk.
4096 bytes in each allocation unit.
60904703 total allocation units on disk.
1897766 allocation units available on disk.

Internal Info:
00 92 07 00 64 dd 06 00 1a d1 0c 00 00 00 00 00 ....d...........
07 01 00 00 54 00 00 00 00 00 00 00 00 00 00 00 ....T...........

Windows has finished checking your disk.
Please wait while your computer restarts.

Thank you.

 

Run HD sentinel on your drive and post images into the thread.
Run Sea Tools for windows using SMART, short and long generic and post the results into the thread.
Hard Disk Sentinel - HDD health and temperature monitoring
http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows

 

Hello, I ran HD sentinel and the images are below.
Sea Tools can't find my SSD even after uninstalling and re installing it, it still couldn't find it.
After looking for information I found out that Sea Tools isn't detecting my SDD because in the BIOS it is set to AHCI. I went into the BIOS to change it to IDE or SATA but I couldn't, the only two options that it lets me select are AHCI or RAID. IDE or SATA don't even show up as options.

Thank you.

 

Windows driver verifier stimulates drivers to find misbehaving drivers and produces bsod's.
The minidump files are then debugged to identify the driver or application.
All files must be backed up.
A restore point should be created.
To turn on windows driver verifier you will type verifier in the left lower corner search. A pop up will appear and you will make customized settings.
To turn off windows driver verifier you will need to be able to navigate to the windows recovery or advanced troubleshooting menu.
When in the windows advanced troubleshooting menu you will select startup options (not startup repair) and then make choice #6 safe mode with command prompt. Then you will enter the command verifier /reset
After entering verifier /reset you will then be able to boot to the desk top.
When back on the desk top you will then identify the misbehaving driver using software.
Download and install each Bluescreenview and Whocrashed.
They often provide a similar analysis but at times one of the software programs may provide information that was not available in the other. In addition you will update or repost a new zip file so we can debug the minidumps.

There are two important steps to make first:
1) Make sure that automatic restart is unchecked so that you have time to view the bsod. When you see the bsod you will see a stop code. The typical stop code is driver verifier detected violation. Sometimes you will see the misbehaving driver identified as *.sys. If you see this information please record the name of the driver.

https://answers.microsoft.com/en-us/...83f-4830-a4dd-


2) You must practice navigating through the Windows recovery or advanced troubleshooting menu. To do this open administrative command prompt and type or copy and paste this command: shutdown /r /o /f /t 00
It will reboot to the Windows recovery or advanced troubleshooting menu. You will then navigate to startup options. Then it will restart and you will choose #6 safe mode with command prompt. When using windows driver verifier you will need to turn it off by entering the command verifier /reset

When you have backed up your files, created a restore point, and are comfortable navigating within the windows advanced troubleshooting menu to get to safe mode with command prompt you then can start using windows driver verifier.

For each identified driver or application you will uninstall it via device manager or control panel. In most cases there will be Microsoft default drivers on reboot. You can rerun windows driver verifier to find the next misbehaving driver or you can install an up to date replacement driver from the computer manufacturer's web site for the driver that was just uninstalled. It is personal preference whether to keep running windows driver verifier to find all of the misbehaving drivers and uninstall them or to uninstall then reinstall and test the first driver replacement.

Once you run Windows driver verifier and no longer have any bsod you will continue to run windows driver verifier for 36 hours while the computer is in typical use. If there are no more bsod you will then turn off windows driver verifier. The troubleshooting and preventative maintenance will be completed.

In this link are text and images for the customized settings for running Windows driver verifier:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
e95ee5d8669d

Blue screen of death (STOP error) information in dump files.
Resplendence Software - WhoCrashed, automatic crash dump analyzer