Horizontal flickering and black screen flickering after POST, sometimes BSOD?

[nuggim]

Hardware:
GPU: Radeon R390
CPU: Ryzen 1600
Motherboard: Asus b350 prime plus
RAM: Corsair V LPX 8GB DDR4 Black 2x288, 3000MHz
Power Supply: Corsair VS650, 650W PSU
OS: Windows 10

Problem:
Computer is running fine for a few days days, but suddenly while gaming the screen starts going black and then crashes with a SYSTEM_SERVICE_EXCEPTION BSOD
After the crash the computer turns on again, but as soon as i get past POST and to the login screen, the screen starts flickering like crazy in the lower part of the screen horizontal and keeps going black (Seems the Display driver is crashing multiple times)
Sometimes it BSOD's sometimes it just keeps flickering and goes black. When it BSOD i also got a IRQL_NOT_LESS_OR_EQUAL

Important information:
Problem started after i replaced my CPU, RAM And Motherboard to the things above. It started 3 days after to be precise
Safe mode is the only thing that doesn't crash the PC right after POST
The problem only seems to start after gaming for 6-8 hours or leaving the PC on for this long and then gaming after
The problem stops automatically, let's say the problem started in the evening, next day i've had luck just turning on the PC again and then it worked
I've also had luck running in safe mode for 2 hours and then just restarting to see what happens, then it works fine again
BlueScreenViewer always rotates between these drivers being the problem: atikmpag.sys - dxgkrnl.sys - dxgmms2.sys - ntoskrnl.exe

Things i've tried:

Reinstalling Windows
Changing the PSU
Changing the GPU to a Geforce (This fixes the problem until i install the drivers, then the problem starts right again)
Smart check on HDD (No errors)
Memtest86 for 8 hours (No errors)
Only having 1 Ram stick in
Trying all RAM slots
Removing ALL overclocks
Updating BIOS / Downgrading BIOS


I have attached the last 5 crash dumps i've had on this installation of my Windows. You can find them here:
https://drive.google.com/open?id=0B1mxLeG6zY_QaEduUDh6UEdBaW8

 

[N3rdR4ge]

Sounds like ram problems.

clear your cmos first and make sure your ram is set to 2133 @ 1.2v afterwards.

Buy another kit to test if that doesn't work. get something with 2400mhz or less with 1.2v.

ive had bad ram pass testing numerous times. caused lines and blue screens like you describe. make sure you purchase a kit of 2 (2x4gb), not separate or single sticks.

 

[nuggim]

Already tried, forgot to mention it.

Same problem sadly. The second the installer is halfway through the driver installation, the flickering starts

 

[N3rdR4ge]

i changed my last post completely. not sure if you saw it. the first one was irrelevant since i overlooked that you did a clean windows install.

 

[nuggim]

Also tried to clear the CMOS and letting the RAM stay at it's standard setup. Doesn't matter if the RAM is running at 2166 or 2966, the error still occurs. Also if the RAM was the problem, shouldn't the Memtest atleast report a single error, and shouldn't the crashes/flickering happen more often than after 8 hours of gaming?

I'm running with 2x4gb and i would be a little sad if had to use more money than i've already had just to try new RAM, i've just spent 100$ changing the PSU in hope of that fixing the problem

 

[nuggim]

Edit: Just tried booting into normal mode again after running in safe mode for an hour. Now its changing between flickering and just going to black and restarting the computer, doesn't even BSOD anymore, after starting up again i got this message http://i.imgur.com/z389WYT.jpg

But i also got 2 new minidumps:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

PAGE_FAULT_IN_NONPAGED_AREA

See attached for these 2 .dmp

https://drive.google.com/open?id=0B1mxLeG6zY_QWGw1X2swZ19XMjA

 

[N3rdR4ge]

i don't believe this is a psu issue. i still think it is ram. like i said before, iv'e had ram pass every test and still give the same issue you are describing. do you have another machine in your house you can steal the ram from or maybe borrow a stick from a friend? I think your best bet is replacing the ram before you go nuts trying to troubleshoot.

 

[nuggim]

I've managed to create the same topic twice without realizing, can a moderator delete this one?

I'll countinue here http://www.tomshardware.co.uk/forum/id-3469015/horizontal-flickering-black-screen-flickering-post-bsod.html

 

[N3rdR4ge]

make sure you try the ram!

if you've tried a clean install and two separate graphics cards, i doubt this is a gpu issue like the other thread is mentioning.

 

[nuggim]

MERGED QUESTION
Question from nuggim : "Horizontal flickering and black screen flickering after POST, sometimes BSOD?"

Hardware:
GPU: Radeon R390
CPU: Ryzen 1600
Motherboard: Asus b350 prime plus
RAM: Corsair V LPX 8GB DDR4 Black 2x288, 3000MHz
Power Supply: Corsair VS650, 650W PSU
OS: Windows 10

Problem:
Computer is running fine for a few days days, but suddenly while gaming the screen starts going black and then crashes with a SYSTEM_SERVICE_EXCEPTION BSOD
After the crash the computer turns on again, but as soon as i get past POST and to the login screen, the screen starts flickering like crazy in the lower part of the screen horizontal and keeps going black (Seems the Display driver is crashing multiple times)
Sometimes it BSOD's sometimes it just keeps flickering and goes black. When it BSOD i also got a IRQL_NOT_LESS_OR_EQUAL

Important information:
Problem started after i replaced my CPU, RAM And Motherboard to the things above
Safe mode is the only thing that doesn't crash the PC right after POST
The problem only seems to start after gaming for 6-8 hours or leaving the PC on for this long and then gaming after
The problem stops automatically, let's say the problem started in the evening, next day i've had luck just turning on the PC again and then it worked
I've also had luck running in safe mode for 2 hours and then just restarting to see what happens, then it works fine again
BlueScreenViewer always rotates between these drivers being the problem: atikmpag.sys - dxgkrnl.sys - dxgmms2.sys - ntoskrnl.exe

Things i've tried:

Reinstalling Windows
Changing the PSU
Changing the GPU to a Geforce (This fixes the problem until i install the drivers, then the problem starts right again)
Smart check on HDD (No errors)
Memtest86 for 8 hours (No errors)
Only having 1 Ram stick in
Trying all RAM slots
Removing ALL overclocks
Updating BIOS / Downgrading BIOS


I have attached the last 5 crash dumps i've had on this installation of my Windows. You can find them here:
https://drive.google.com/open?id=0B1mxLeG6zY_QaEduUDh6UEdBaW8

I can't read dump files but this can, can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them, while we wait for someone who can read dumps for you

Copy/paste summary in here and I see what I can do

--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.54
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-T33JGIU
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., PRIME B350-PLUS
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor AMD586, level: 23
12 logical processors, active mask: 4095
RAM: 8523141120 bytes total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 15-07-2017 16:38:03 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071517-8921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x1A (0x61941, 0xFFFFFE3FFD069000, 0x9, 0xFFFF98020035AF40)
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. This problem might also be caused because of overheating (thermal issue).
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 15-07-2017 16:38:03 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: 0x1A (0x61941, 0xFFFFFE3FFD069000, 0x9, 0xFFFF98020035AF40)
Error: MEMORY_MANAGEMENT
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. This problem might also be caused because of overheating (thermal issue).
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 15-07-2017 16:36:33 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071517-13171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x1A (0x41792, 0xFFFFCBBFFCB6CEE0, 0x10000000, 0x0)
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. This problem might also be caused because of overheating (thermal issue).
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 15-07-2017 16:32:38 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071517-21890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x1A (0x41201, 0xFFFFFA3FFAF24018, 0x88F98764321, 0xFFFFCE8F5E57E900)
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. This problem might also be caused because of overheating (thermal issue).
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 15-07-2017 12:29:12 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071517-12656-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF803AA5F04C0)
Bugcheck code: 0x50 (0xFFFFC081D1810000, 0x2, 0xFFFFC081D09FD511, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
A third party driver was identified as the probable root cause of this system error.
Google query: PAGE_FAULT_IN_NONPAGED_AREA





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

11 crash dumps have been found and analyzed. Only 5 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmpag.sys
atikmdag.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.




Notice: Safemode works without any problems, if i uninstall my AMD drivers i can also run in normal mode, as soon as i update the drivers to my Radeon R390 the crashing starts again and then sometime randomly fixes itself and runs for another week until the fault comes again.

Tried a Geforce GPU and also got the same BSOD' errors, just referring to the Geforce drivers

odd getting same error pattern on Nvidia and AMD cards, I assume you have the latest motherboard drivers.

it has to be drivers of some sort as otherwise safe mode would crash as well. Someone who can read dumps may see what I am missing here,

Do you have any overclocking software on PC as it can cause this. Are you running AI Suite? same with Asus GPU Tweak 2. I would remove them as well until we figure this out

Overclocking has been done via BIOS. Overclock or not, the problem still happens

Just tried to uninstall all the drivers for my R390, now i only experience Memory_Management BSOD and no flickering anymore/Black screen

Without display drivers i can boot into windows but i keep getting Memory_Management BSOD and CRITICAL_PROCESS_DIED BSOD at random times now - See .dmp files: https://drive.google.com/open?id=0B1mxLeG6zY_QcjBGUmZBbnFmcDQ



I've now experienced ALL of these BSOD messages:

MEMORY_MANAGEMENT

CRITICAL_PROCESS_DIED

PAGE_FAULT_IN_NONPAGED_AREA

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

IRQL_NOT_LESS_OR_EQUAL

SYSTEM_SERVICE_EXCEPTION

And 2 BSOD's wihout a bug check string that points to "caused by dxgkrnl.sys"

Windows later decided to install the drivers for R390 automatically while i was in normal mode and crashed right after with VIDEO_TDR_FAILURE and flickering

if you've tried a clean install and two separate graphics cards, i highly doubt this is a gpu issue like the this thread is mentioning. i don't believe this is a psu issue especially since you've replaced that too. i still think it is ram. all of these errors can be caused by ram. like i said before, iv'e had ram pass every test and still give the same issue you are describing. do you have another machine in your house you can steal the ram from or maybe borrow a stick from a friend? I think your best bet is replacing the ram before you go nuts trying to troubleshoot. you cant be sure unless you replace it and it is the best suspect after the troubleshooting you've done.

if you've tried a clean install and two separate graphics cards, i highly doubt this is a gpu issue like the this thread is mentioning. i don't believe this is a psu issue especially since you've replaced that too. i still think it is ram. all of these errors can be caused by ram. like i said before, iv'e had ram pass every test and still give the same issue you are describing. do you have another machine in your house you can steal the ram from or maybe borrow a stick from a friend? I think your best bet is replacing the ram before you go nuts trying to troubleshoot. you cant be sure unless you replace it and it is the best suspect after the troubleshooting you've done.

Im thinking this is where i am headed too. But i just can't wrap my head around why the error occurs then the computer is "broken" for 1-2 days and then randomly works again for up to 7 days without a single error, only to start again from the beginning

 

[N3rdR4ge]

ram will do that! sorry to be a nag.