Windows 10: Unexplained reboot nothing in event log

Wondering if this is a hardware problem or something else (see specs). Machine is on 24/7 and since updating the graphics driver to the latest version from Nvidia as it contains Spectre mitigations I have experienced 1 black screen which lasted for 2 seconds.

The other night I left my machine at the login screen and came back to it the next morning and it was at the login screen still but must have rebooted as it took a few seconds to login and startup programs had to run again as if I was logging in after a reboot.

Nothing in the even log apart from an event log uptime of 5 hours at midday. Any ideas as to what could have caused the reboot as usually when there is a power blip I get a kernel power event in the event log?

:)

 

Nokia re-format freeze

unexplainably, the hard reset now worked. Thanks Nokia for nothing

 

Is it safe to delete the empty folder <C:\ProgramData\regid.1991-06.com.microsoft> ?

I'm using now for the past several hours. Nothing extra showing in event logs and probably been rebooted a time or two times. TastManager shows 4:48 minutes up time right now.

 

Hello,

Black screens or random flashes are completely fine when updating or reinstalling your graphics driver.

Are you sure there was a reboot? I mean, your machine might activate power saving mode and shut all the programs down.

Also, unless it happens very often and it bugs you, I don't see any big deal happening here EVEN if there actually was a reboot so yeah you shouldn't be worried.

 

Check the Reliability History ("Control Panel" > "Security and Maintenance" > "Maintenance" > "View reliability history") or
("Start" > "Run" and type "perfmon /rel" then click "OK" or press {Enter}). You will see a number of "Critical" errors. Click on the "View technical details" of one of these errors and it should show the error details. For some reason, crashes may not be showing on the Event Logs anymore, but do show on the Reliability History.

JohnD

 

After (re)installing most drivers it's normal to reboot the system so driver can take effect. I always reboot even when it doesn't explicitly says so.

 

You can use this command to see the time when your computer booted/rebooted.

Code: systeminfo | find "Boot Time"[/quote]

 

[/quote] Thanks for that it shows 23/01/18 07:00:50 so I was right it reboot going to check reliability history now.

Edit from RH: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8010a60a370, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\012318-17062-01.dmp. Report Id: 041d5c32-2867-4ec0-98da-9ef5c9aedf65.

 

This is the definition of that error:

"Bug Check 0x113: VIDEO_DXGKRNL_FATAL_ERROR"

The VIDEO_DXGKRNL_FATAL_ERROR bug check has a value of 0x00000113. This indicates that the Microsoft DirectX graphics kernel subsystem has detected a violation.

So it appears that it may be a graphics driver related issue. You said you updated your graphics driver recently. You might want to back off to the previous version. There have been a number of issues with the updates being put out to fix the Meltdown/Spectre problems. HP and Dell have pulled BIOS updates due to the problems they have caused. It might be best to wait until the smoke clears before doing these updates.

JohnD

 

Thanks John will roll the graphics driver back.

 

No more reboots so can say this is solved. Interesting when in Device Manager and clicking roll back on properties I was presented with a survey which I clicked "More reliable" then rolled back. Haven't seen this survey before.

 

I know but I am pretty sure the Nvidia driver is at fault and I have rolled back to a working driver as far as I know.

So far so good with prim95 and furmark although had to stop furmark at 80 degrees as it only has a passive cooler.

 

This happening again so trying latest Nvidia drivers.

 

Run the beta log collector and post a zip into this thread:
https://www.tenforums.com/attachmen...ting-instructions-log-collector-v2-beta10.zip
(extract > open)
Use the text and images in this link in case there are any problems running the beta log collector: (post #5)
DM Log tool problem Solved - Windows 10 Forums

 

Log collector appeared to run ok. Here is the zip. Many thanks.