Blue Screen loop when playing games? Help please!

Luke_Live

Reputable
Jan 20, 2016
37
0
4,530
I have frequently gotten BSODs and they would eventually go away. Whether it be updating a driver, or whatever small thing i did. But they never completely go away.

A few weeks ago I was getting BSODs and other crash screens that would be different shades of red and would not have error messages. Many helpful people here helped me come to the conclusion that the problem was my PSU. So I upgraded it and everything was fine until last night.

My friend asked me to try playing World of Warcraft for the first time. The game isnt very demanding compared to other games I play. And yet, During this game I get Blue Screens. (probably unrelated to the game, however)

It started off with System_Service_Exception. Then it would instantly go into System_Exception_Thread_Not_Handled. I finally got into my PC and checked to see if there was a driver update, but there was not (on the driver program that installed with the GPU). There was however, a windows update. So I started the update and went to sleep. I woke up today and the update was not done. I logged on and restarted the update and I crashed at 13%. got a few blue screens. This time I got Kmode_exception_not_handled. I checked the driver website and there was an update. So I updated and everything was fine. Got back on WoW and played for about an hour until I got the Kmode again.

If anyone knows what could be happening, I would love some help!

(I don't know how to find crash reports that I could post here like some other threads did. If someone could tell me how to do that I will post them when I get back home in a few hours)

I have not dusted my pc in a while. I will also try to dust my Pc when I get home.

My specs:

CPU - AMD FX-8350 8-Core Processor @4.00 GHz
CPU Cooler - Cooler Master Hyper 212 EVO
GPU - XFX RX 480 8GB GDDR5
RAM - Corsair Vengeance 2x4GB PC3-12800 DDR3
HDD - Western Digital Blue 1TB
SSD - SanDisk Internal SSD 120GB
PSU - EVGA 750 GQ Semi-Modular
Motherboard - Asus M5A97 LE R2.0 ATX AM3+ Motherboard
OS - Windows 10 Home 64 Bit
 


Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 4/29/2017 2:15:06 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\042917-18046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8001EB228A4, 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 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 Sat 4/29/2017 2:15:06 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xD5F4C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8001EB228A4, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 4/29/2017 2:14:20 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\042917-18531-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Fri 4/28/2017 10:42:07 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\042817-23078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCCDA2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8010DD46DA2, 0xFFFFD0017E07E268, 0xFFFFD0017E07DA80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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.



On Thu 4/27/2017 10:41:41 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\042817-29156-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
 
0xFFFFFFFFC0000005
indicates a bad memory address being provided to a driver.

you would remove any overclocking, and boot and run memtest86 to confirm your memory timings

the unknown bugcheck I generally see this from amd graphics cards when they don't have proper power from the PSU to the GPU power connector. (or they are overclocked or overheated)

anyway, put your memory dumps on a server, share them for public access and post a link