[SOLVED] Black Screen then Restart.

jcdomingo

Reputable
Aug 8, 2019
68
5
4,545
There are 2 occasions where I encountered it.
  1. While playing games particularly Shadow of War
  2. While browsing using firefox

The screen just went black then rebooted.
I didn't encounter BSOD
The PC didn't really sound like in booting process like turning on
Its the way it is, it just went black then reboot.
 
Solution
Don't panic - it gives us new information. And can help us find the cause my friend!

I have debugged the DMP file and you can see the full report here: https://pste.eu/p/UgTL.html

Summary of findings:
BugCheck 1A, {41201, ffffec3ffe715740, 6000001565ed005, ffff8b07bc0ba0a0}
Probably caused by : memory_corruption ( nt!MiGetPageProtection+19bda6 )

MEMORY_MANAGEMENT (1a)
Bugcheck subtype 41201

In the process of querying a virtual address, there was an inconsistency between the Page Frame Number(PFN) and the current Page Table Entry (PTE) pointer. Parameter 2 is the corresponding PTE. Parameter 3 is the PTE contents and parameter 4 is the virtual address descriptor.

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT...
Welcome to the forums my friend!

Please post your entire system spec including PSU make and model.

Random reboots can be indicative of many things, however tends to point towards PSU. Especially if it is poor quality.
Thanks for replying :)
Here are my system specs:
GTX 1060 6GB G1
i58600K
16GB RAM
PSU: EVGA 650GQ 80+ Gold 650W
 
The PSU is good quality, but doesn't necessarily mean it is functioning normally. You may want to consider the following:

  • Monitor GPU and CPU temps under load (CPU individual cores, not overall package).
  • Monitor PSU voltages on the 12v, 5V, 3.3V rails.
  • If you have any overclock or XMP enabled, remove it.

You can use MSI afterburner or HWInfo to monitor the criteria above. Being as you've only had the shut down twice, it might be hard to try and recreate or eliminate the root cause.
 
The PSU is good quality, but doesn't necessarily mean it is functioning normally. You may want to consider the following:

  • Monitor GPU and CPU temps under load (CPU individual cores, not overall package).
  • Monitor PSU voltages on the 12v, 5V, 3.3V rails.
  • If you have any overclock or XMP enabled, remove it.
You can use MSI afterburner or HWInfo to monitor the criteria above. Being as you've only had the shut down twice, it might be hard to try and recreate or eliminate the root cause.
Do power outages can kill PSU?
I experienced this frequent shutdowns last week 3 times in fact.
Though adding more to the problem....(Before the outages)
I'm experiencing frequent BSOD's with different error everytime almost like once a day
and it's annoying me.
like kernel_security_failure, video memory management and some other errors.

I don't know whats the problem anymore. I think i started experiencing this BSODs after i updated my OS to 1903 or 431.16 on the graphics driver?

Or is the power outages the cause?
 
Yes they can.


In which case please see this guide and get us the dump files so that we can try and assist further: https://forums.tomshardware.com/thr...nclude-in-blue-screen-of-death-posts.3468965/

You may want to try booting into safe mode and see if the issue still occurs.
A BSOD just occurred; system_thread_exception not handled nvlddmkm.sys
I followed the link you provided and this is my memory dump
https://drive.google.com/open?id=1AU1UB-iTdUDgZg10kstIHjyBVK95mWiN
 
I've ran the dump file and you can see the full report here: https://pste.eu/p/Bi8H.html

Summary of findings:
BugCheck 1000007E, {ffffffffc0000005, fffff80574a2acb8, ffffb9892e91de08, ffffb9892e91d650}
Probably caused by : nvlddmkm.sys ( nvlddmkm+75acb8 )

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ...If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening.

MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys

Some things to consider:
other items:
  • If you have any overclock or XMP - disable it.
  • You have WinRing Library running, which is a known BSOD cause. It may not be yours, but it is a culprit.
  • The Gigabyte Apple Charger is also reported as a known BSOD cause. Same as above.
  • I could not deduce your BIOS version, is this up to date?
  • Are you RAM modules from the same pack?
  • May need to look at Realtek internet drivers if nothing else improves.
  • I noticed there is no antivirus, do you use one or just use windows defender?
For problem drivers, you may want to use autoruns to disable them from startup.

Admittedly, based on your previous comments, everything is pointing to your GPU. So it may be worth testing if you still encounter an issue in safe mode.
 
I'm surprised and grateful for such detailed explanations.

I'll try rolling back and see if I'll encounter any problems.

Should i delete WinRing and AppleCharger?
https://drive.google.com/open?id=10mSsuZSE9vmuTXc5j3VnskoTHbVC8Zey
I just updated my BIOS using the GIGABYTE App Center it prompted me.
I only use Windows Defender enough right?

I don't really know much about this stuff but is there a serious problem?
Is my video card broken? Is it time to replace? I'm getting paranoid.

Specifically, what do you mean if I'll still encounter it in safe mode? Should I run a benchmark or stress test in safe mode?
 
Use autoruns to just disable them (I linked in my previous post). This doesn't remove them, just stops them from starting, and allows you to re-enable them later if needed.

I only use Windows Defender enough right?
Yes that's fine, just had to make sure you were using something!

I don't really know much about this stuff but is there a serious problem?
Is my video card broken? Is it time to replace? I'm getting paranoid.
Don't panic, we don't know the problem just yet. Most BSOD are indicative of driver problems. So it's just eradicating that first. I won't lie, various different BSOD can be more indicative (not always) of hardware, but it's a case of eliminating the possibilities.

Specifically, what do you mean if I'll still encounter it in safe mode?
Basically if you are encountering this problem all the time, then running in safe mode will allow you to see if it also happens there. You won't be able to run any stress tests within safe mode as it disables all third party software.

However if the problem completely disappears in safe mode, then the likelihood is it is third party drivers causing the issue. If the issue continues in safe mode, then it could be hardware or core OS corruption.

This is only really applicable when you are able to try and recreate the crash. So if it ONLY ever crashes under heavy loads, then you probably won't be able to simulate this in safe mode.
 
This is only really applicable when you are able to try and recreate the crash. So if it ONLY ever crashes under heavy loads, then you probably won't be able to simulate this in safe mode.
All/Most of the BSOD's are while playing games. I don't really encounter it when I'm just browsing or doing some other stuff. Only in 1 occassion that I ecountered the black screen and reboot while browsing.
 
All/Most of the BSOD's are while playing games. I don't really encounter it when I'm just browsing or doing some other stuff. Only in 1 occassion that I ecountered the black screen and reboot while browsing.
Have you monitored GPU and CPU temps as previously mentioned? See below:

  • Monitor GPU and CPU temps under load (CPU individual cores, not overall package).
  • Monitor PSU voltages on the 12v, 5V, 3.3V rails.
  • If you have any overclock or XMP enabled, remove it.
 
Have you monitored GPU and CPU temps as previously mentioned? See below:
UPDATE:

So I rolled back my NVIDIA Driver to 425.31 that was released last April 2019. As far as I can remember, it was the period of total glory with my gaming sessions(no BSOD, Black Screen). Today, I ran some stress testing using MSI Afterburner Furmark GL 1 hour for stock/defaults clocks and 1 hour for overclock.
 
UPDATE:

So I rolled back my NVIDIA Driver to 425.31 that was released last April 2019. As far as I can remember, it was the period of total glory with my gaming sessions(no BSOD, Black Screen). Today, I ran some stress testing using MSI Afterburner Furmark GL 1 hour for stock/defaults clocks and 1 hour for overclock.
So the recommendation for rolling back your NVIDIA drivers appears to have done the trick?
i know you also disabled other items so it could be a red herring...
 
So the recommendation for rolling back your NVIDIA drivers appears to have done the trick?
Likely though I'm not sure yet; up to this moment, I didn't really encounter any problems. I playing Shadow of the tomb raider, AC Unity and Witcher 3 at Ultra with rivatuner monitoring.

during the stress testing, GPU is the only overlocked.
stock temp - min: 27C max: 75C
CPU temp - min: 26C max: 60C
OC temp - min: 33C max: 80C
CPU temp - min: 28C max: 63C

I'm satisfied that there are no errors for today unlike before where there are sometimes 3 instances of error in a day which is annoying me.

I'm going to continue monitoring if I'll ever encounter some problems again.

I thought updating to the latest drivers is the best but darn nvidia, not everyone has RTX cards!

Thank you for having the time and patience helping me with my problem. The thought of having a hardware problem is really horrifying.

Keep doing the best work!
 
Last edited:
  • Like
Reactions: PC Tailor
Just be wary of the language, as moderators will remove it if they see it as children and families can visit these forums! I understand there is nothing malicious in your content, just may be worth you removing it first my friend! :)

And most importantly I'm just glad to help. NVIDIA and AMD GPU drivers have always had issues, just there is a bit of a trend with the latest updates along with latest Windows, so may just be waiting for the next update. For all we know it could actually be a combination of GPU drivers with another driver that's causing the issue, but we'll see.

Hopefully I haven't jinxed it, but let us know if the problem returns, it's just a matter of elimination :)
 
For all we know it could actually be a combination of GPU drivers with another driver that's causing the issue, but we'll see.

Hopefully I haven't jinxed it, but let us know if the problem returns, it's just a matter of elimination :)
Actually, I searched for other workarounds in fixing the nvlddmkm.sys which requires me to rename it to something like nvlddmkm.sys.old then copying the nvlddmkm.sy_ then expanding it in CMD, like creating a new nvlddmkm.sys file in case the older is corrupted.

Upon searching first for nvlddmkm.sys, There are 2 instances where 2 nvlddmkm.sys appeared.
1st is in the folder nv_dispi......
2nd is inside the folder nv_ref...........
both in System32/Drivestore/FileRepository

I noticed the folder nv_dispi... has the current driver version 431.16 (not rolling back yet (current: 425.31)).
and the folder nv_ref has the older driver which from 2017 (tried rolling back to fix with a 2017 nvidia driver).

I deleted the nv_ref folder because as far as I know, both folders has the same contents and nv_dispi... is newer.
didn't really experienced any problems deleting nv_ref folder.

Then I removed the latest nvidia update then roll back to the most stable driver I can remember (current driver 425.31)

Maybe that was the cause of the issue? conflicting nvlddmkm.sys?
Or it's just really the problem with the latest driver itself?
 
Last edited:
  • Like
Reactions: PC Tailor
Don't panic - it gives us new information. And can help us find the cause my friend!

I have debugged the DMP file and you can see the full report here: https://pste.eu/p/UgTL.html

Summary of findings:
BugCheck 1A, {41201, ffffec3ffe715740, 6000001565ed005, ffff8b07bc0ba0a0}
Probably caused by : memory_corruption ( nt!MiGetPageProtection+19bda6 )

MEMORY_MANAGEMENT (1a)
Bugcheck subtype 41201

In the process of querying a virtual address, there was an inconsistency between the Page Frame Number(PFN) and the current Page Table Entry (PTE) pointer. Parameter 2 is the corresponding PTE. Parameter 3 is the PTE contents and parameter 4 is the virtual address descriptor.

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: nvcontainer.ex
MODULE_NAME: nt

Some things to consider:
  • Do you have latest BIOS installed (I may have already asked this) - if not, the Intel Management Enginer should be ideally aligned with the BIOS.
  • I've seen the Gigabyte Tools and RGB driver cause some issues in the past.
  • Uninstall MSI Afterburner / Riva whichever you have installed as these can easily cause BSOD.
  • As with any memory management bugcheck, it's now recommended that you run memtest for at least 4 passes to verify the integrity of your memory modules.

When did the BSOD occur? Under any particular circumstances?
 
  • Like
Reactions: jcdomingo
Solution
Ok :) This could take a while so I'll update you when it's finished.
MAJOR UPDATE!
2 x HyperX Fury DDR4 8GB 2400mhz
So I ran memtest 3 times. 4/4 pass each time with no errors.
1st - Both sticks - https://pste.eu/p/18om.html
2nd - removed the other - https://pste.eu/p/iqhj.html (the counterfeit)
3rd - switched - https://pste.eu/p/po4y.html



I'd like to make it clear that I bought each stick separately online and I'm pretty sure they are the same.

1st RAM, using it for 5months then I bought the 2nd RAM.

The major surprise was, turned out that the 1st RAM I bought was counterfeit. Based on my readings about checking a hyperx ram authenticity, there is a sticker which will change color from something like light red to dark(vise versa) when tilted. Also, when the item was shipped to me, it's inside a chinese packaging which is questionable. Nonetheless it's working perfectly that time (last year July 2018) it's 8gb running at 2400mhz so why bother.
1st RAM - does not change color
2nd RAM - it does change. Came with proper hyperx packaging icluding a manual and warranty card.

Is it safe to assume now that counterfeit ram was the culprit of these problems? Though with the tests showing no errors?
 
Last edited: