Windows 10: Screen goes blank, then reboots after 15 secs.

Hello all,

I have this stability problem with my rig:

Every few days, the screen goes blank but I can still hear background sounds, then after maybe 15 seconds, the computer reboots but the reboot process takes a few minutes instead of a few seconds as usual when that happens.

This can happen anytime (playing WoW, browsing the web, or sitting idle).

I have noticed that before the computer crashes, I have a dozen Event ID 4101 "Display driver nvlddmkm stopped responding and has successfully recovered"

Then the really slow reboot comes from a critical Event ID 100 with extremely long BootUserProfileProcessingTime
For example:

EventData BootTsVersion 2 BootStartTime 2016-10-01T22:42:36.683475900Z BootEndTime 2016-10-01T22:47:38.211820700Z SystemBootInstance 27 UserBootInstance 27 BootTime 222190 MainPathBootTime 205090 BootKernelInitTime 22 BootDriverInitTime 200 BootDevicesInitTime 857 BootPrefetchInitTime 0 BootPrefetchBytes 0 BootAutoChkTime 0 BootSmssInitTime 7469 BootCriticalServicesInitTime 137 BootUserProfileProcessingTime 194439 BootMachineProfileProcessingTime 15 BootExplorerInitTime 1252 BootNumStartupApps 37 BootPostBootTime 17100 BootIsRebootAfterInstall false BootRootCauseStepImprovementBits 0 BootRootCauseGradualImprovementBits 0 BootRootCauseStepDegradationBits 0 BootRootCauseGradualDegradationBits 0 BootIsDegradation false BootIsStepDegradation false BootIsGradualDegradation false BootImprovementDelta 0 BootDegradationDelta 0 BootIsRootCauseIdentified false OSLoaderDuration 637 BootPNPInitStartTimeMS 22 BootPNPInitDuration 1117 OtherKernelInitDuration 515 SystemPNPInitStartTimeMS 1624 SystemPNPInitDuration 90 SessionInitStartTimeMS 1723 Session0InitDuration 5134 Session1InitDuration 321 SessionInitOtherDuration 2014 WinLogonStartTimeMS 9193 OtherLogonInitActivityDuration 189 UserLogonWaitDuration 6461

If someone could help me squash the bug, that would be great! *Smile

:)

 

Blank screen on 10 install

Have installed windows 10 on my laptop with no problems but on trying to install windows 10 on the wife's laptop, both running windows 7, the screen has gone blank (yes, it still has power) and does not move on. Have powered off and rebooted and Dell's
front screen appears for a few seconds then a blue screen with the new Windows logo comes up with the working circle running but after about 30 secs screen goes blank although still illuminated. A message came up at one point saying error occurred at startup,
restarting, but still stuck on blank screen after being left overnight. Seems to be stuck in a reboot loop

 

Nokia 2730

How do you adjust the power saver settings on the Nokia 2730 - I can't find where it is??

This phone's screen goes blank after 25 secs ... even if the screensaver is on??

 

Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial.
Code: Event[5396]: Log Name: System Source: volmgr Date: 2016-10-01T18:42:38.292 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: REDBOX Description: Crash dump initialization failed![/quote]
Please check your SSD for firmware updates.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

• Uninstall Daemon Tools
• Download the SPTD standalone installer and follow these steps:
  • Double click the executable to open it
  • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window.


Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver, you can use this tutorial for the installation part *Arrow NVIDIA Drivers - Avoid Problems - Windows 7 Help Forums
Attachment 104094

 

Minidump: configured, but I had a message that says that Windows cannot do a dump when the Virtual Memory is disabled. (Enabled Virtual Memory)

SSD Firmware: already at the latest firmware

Deamon Tools: Uninstalled
SPTD: Was already uninstalled with the above

DDU: Done, but when the system restarted, I had a slow boot like described in my first post.
Nvidia Driver: Did ask you asked (Graphics driver + PhysX only) but now my Oculus Rift doesn't work anymore!!! ( I had to reinstall the driver with everything checked except Geforce Experience to make the Oculus Rift work again)

I will report back in a week (or earlier if the system crashes again!)

 

If the system is stable again then I would focus on other problems, that's what I'm doing with my system *Smile

 

The rig crashed again last night (sitting idle) but now that I have re-enabled virtual memory, we now have a crash dump and a bugcheck 0x116 (VIDEO_TDR_ERROR).

Here are the new logs:

 

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver, you can use this tutorial for the installation part *Arrow NVIDIA Drivers - Avoid Problems - Windows 7 Help Forums
Attachment 104531
Code: 11: kd> lmvm nvlddmkm Browse full module list start end module name fffff804`24200000 fffff804`24fe3000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: nvlddmkm.sys Image name: nvlddmkm.sys Browse all global symbols functions data Timestamp: Sat Sep 17 00:21:27 2016 (57DC7067) CheckSum: 00DA19C2 ImageSize: 00DE3000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

I don't understand.... I have already done this step exactly as you instructed (see reply #3), the only difference is that I need the 3D vision drivers installed, otherwise my Oculus Rift will not work at all.

 

The 0x116 is a GPU driver reset problem crash (drivers didn't respond, reset didn't work, etc.), that and below is why I posted it again.

It is necessary that you follow the instructions exactly, without exception for anything as it is not yet known if what you want to make an exception for causes problems or not.

 

I think I nailed it down! This afternoon I had another crash while I was away with a 0x1a bug check. So I went ahead and did a memory test and it found errors. So I spent the rest of the day doing many memory tests with each ram sticks individually and 1 of them failed the test twice.

I'll run my system for another week with only 16gb of ram and post again as solved (hopefully!) if there are no more crashes.

 

Well, it looks like removing the faulty ram stick did not solve the bugcheck 0x116 problem *Sad
I'm now at your mercy Axe0! *Smile
I removed the nvidia drivers using DDU, redownloaded the nvidia drivers (nvidia has newer drivers now) and installed only Graphics Driver and PhysX modules with the clean install box checked.

 

The faulty stick may had affected things, but the 0x116 is usually not caused by faulty memory (unfortunately in this case)

If you get 0x116 crashes again, my suggestion for now would be to try different driver versions, a minimum of 3 different driver versions would be the best.

 

Using different Nvidia driver versions did not change anything. I'm still getting BSOD 0x116 from time to time, but today I experienced a new symptom! Weird video problem + crash. See screenshot.

 

Try to use the GPU in another system if possible.