Windows 10: Random reboots

Hello,

I've been having an issue with my PC randomly rebooting. I never really notice a BSOD as the computer just reboots with no apparent error but a 'memory.dmp' file is generated every time. I've done chkdsk's and also ran memtest86 numerous times with no errors. Booting up and shutting down goes smoothly and the machine works smoothly with no problems when in use. I have never had it crash while in use it always happens when idle. Hopefully the zip file holds some information that can be helpful to figure out the issue. I've included images from CPU-Z in case they help. Please let me know if any other information is needed. Thanks for any help you can provide.

:)

 

random reboots

You mean Return it to the shop? Will they take it back?

 

reboot at random

I just upgraded W 10 and I find that as I'm working, my computer does a reboot on it's own. When the reboot completes and I go back onto my browser it asks me would I like to continue where I left off. This happens randomly sometimes it doesn't happen
and sometimes it happens 2 or 3 times in a session. Any ideas?

 

One of the crash dumps pointed to nvlddmkm.sys, your NVIDIA display driver. It also listed netwtw04.sys, your Intel wifi card.

The other crash dump didn't specifically point to a driver, but the running thread at the time of the crash belonged to dwm.exe, the desktop window manager. Since dwm.exe uses hardware acceleration to render the desktop UI, a graphics issue is definitely possible.

I'd suggest installing the latest driver for your GTX 1080, and your Intel Wireless-AC 3165.

Code: Start memory scan : 0xfffff8020161a0f8 ($csp) End memory scan : 0xfffff8020161bfb0 (DPC Stack Base) rsp : 0xfffff8020161a0f8 : 0xfffff801fefd8a6e : nt!KiFatalExceptionHandler+0x22 0xfffff8020161a0f8 : 0xfffff801fefd8a6e : nt!KiFatalExceptionHandler+0x22 0xfffff8020161a110 : 0xfffff801ff05305d : nt!ExAllocatePoolWithTag+0x61d 0xfffff8020161a138 : 0xfffff801fef60cad : nt!RtlpExecuteHandlerForException+0xd 0xfffff8020161a140 : 0xfffff801ff159000 : "nt!BcpDisplayParameters <PERF> (nt+0x34e000)" 0xfffff8020161a148 : 0xfffff801fee0b000 : "nt!WerLiveKernelInitSystem <PERF> (nt+0x0)" 0xfffff8020161a158 : 0xfffff801ff625bb0 : hal!IoFreeAdapterChannelV2+0x60 0xfffff8020161a160 : 0xfffff8020161a220 : 0xfffff801fef5f965 : nt!KxRetireDpcList+0x5 0xfffff8020161a168 : 0xfffff801feeb4301 : nt!RtlDispatchException+0x421 0xfffff8020161a198 : 0xfffff801ff6259b2 : hal!HalAllocateAdapterChannelV2+0x11e 0xfffff8020161a1b0 : 0xfffff8020161a300 : 0xfffff801ff146180 : nt!KiInitialPCR+0x180 0xfffff8020161a1c0 : 0xfffff801fee0b000 : "nt!WerLiveKernelInitSystem <PERF> (nt+0x0)" 0xfffff8020161a1f8 : 0xfffff801ff16c788 : "nt!BcpDisplayParameters <PERF> (nt+0x361788)" Unable to load image \SystemRoot\System32\drivers\Netwtw04.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Netwtw04.sys *** ERROR: Module load completed but symbols could not be loaded for Netwtw04.sys 0xfffff8020161a220 : 0xfffff801fef5f965 : nt!KxRetireDpcList+0x5 0xfffff8020161a228 : 0xfffff801fee0b000 : "nt!WerLiveKernelInitSystem <PERF> (nt+0x0)" 0xfffff8020161a230 : 0xfffff801ff16c788 : "nt!BcpDisplayParameters <PERF> (nt+0x361788)" 0xfffff8020161a250 : 0xfffff801fefd8a4c : nt!KiFatalExceptionHandler 0xfffff8020161a300 : 0xfffff801ff146180 : nt!KiInitialPCR+0x180 0xfffff8020161a368 : 0xfffff801fef5f770 : nt!KiDispatchInterruptContinue 0xfffff8020161a398 : 0xfffff8002f298939 : tcpip!FlpSendPacketsHelper+0x299 0xfffff8020161a698 : 0xfffff80034231c6c : wdiwifi!CTxMgr::ServiceQueues+0x4e4 0xfffff8020161a718 : 0xfffff801fee2934a : nt!EtwpReserveTraceBuffer+0xca 0xfffff8020161a738 : 0xfffff801feee9180 : nt!KiOpFetchBytes+0x30 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys 0xfffff8020161a750 : 0xfffff801ff053791 : nt!ExAllocatePoolWithTag+0xd51 0xfffff8020161a758 : 0xfffff801fee0b000 : "nt!WerLiveKernelInitSystem <PERF> (nt+0x0)" 0xfffff8020161a760 : 0xfffff801ff17bd7c : "nt!BcpDisplayParameters <PERF> (nt+0x370d7c)" 0xfffff8020161a768 : 0xfffff800350e0000 : nvlddmkm 0xfffff8020161a778 : 0xfffff800350e0000 : nvlddmkm 0xfffff8020161a788 : 0xfffff800350e0000 : nvlddmkm 0xfffff8020161a798 : 0xfffff800350e0000 : nvlddmkm 0xfffff8020161a7a8 : 0xfffff800350e0000 : nvlddmkm 0xfffff8020161a7b8 : 0xfffff800350e0000 : nvlddmkm 0xfffff8020161a7c8 : 0xfffff800350e0000 : nvlddmkm 0xfffff8020161a7d8 : 0xfffff800350e0000 : nvlddmkm 0xfffff8020161a7e8 : 0xfffff800350e0000 : nvlddmkm 0xfffff8020161a7f8 : 0xfffff800350e0000 : nvlddmkm 0xfffff8020161a808 : 0xfffff800350e0000 : nvlddmkm 0xfffff8020161a868 : 0xfffff801feeb3077 : nt!KiDispatchException+0x1d7 0xfffff8020161a920 : 0xfffff801ff146a60 : nt!KiInitialPCR+0xa60 0xfffff8020161a930 : 0xfffff801ff13d290 : nt!NonPagedPoolDescriptor+0x150 0xfffff8020161a998 : 0xfffff801ff05305d : nt!ExAllocatePoolWithTag+0x61d 0xfffff8020161a9c8 : 0xfffff8002f298939 : tcpip!FlpSendPacketsHelper+0x299 0xfffff8020161ad28 : 0xfffff801feeb3a6c : nt!RtlGetExtendedContextLength+0x34 0xfffff8020161ad98 : 0xfffff801fef0b4f4 : nt!EtwpDequeueFreeBuffer+0x114 0xfffff8020161ade8 : 0xfffff801fef0b349 : nt!EtwpSwitchBuffer+0x189 0xfffff8020161ae20 : 0xfffff8020161b030 : 0xfffff801ff13d290 : nt!NonPagedPoolDescriptor+0x150 0xfffff8020161ae38 : 0xfffff801fee2934a : nt!EtwpReserveTraceBuffer+0xca 0xfffff8020161ae80 : 0xfffff8020161b030 : 0xfffff801ff13d290 : nt!NonPagedPoolDescriptor+0x150 0xfffff8020161aea0 : 0xfffff801ff07eb00 : nt!KFileEvt_NameCreate 0xfffff8020161aeb8 : 0xfffff801feeae088 : nt!EtwpEventWriteFull+0x608 0xfffff8020161af28 : 0xfffff801fef65b0e : nt!KiExceptionDispatch+0xce 0xfffff8020161af50 : 0xfffff801ff07eb01 : nt!KFileEvt_NameCreate+0x1 0xfffff8020161b030 : 0xfffff801ff13d290 : nt!NonPagedPoolDescriptor+0x150 0xfffff8020161b078 : 0xfffff801ff05305d : nt!ExAllocatePoolWithTag+0x61d 0xfffff8020161b108 : 0xfffff801fef63dbd : nt!KiGeneralProtectionFault+0xfd 0xfffff8020161b118 : 0xfffff801fef4b62a : nt!qsort+0x2fa 0xfffff8020161b148 : 0xfffff801ff146a60 : nt!KiInitialPCR+0xa60 0xfffff8020161b200 : 0xfffff801ff146180 : nt!KiInitialPCR+0x180 0xfffff8020161b228 : 0xfffff801ff623c25 : hal!HalSendSoftwareInterrupt+0xa5 0xfffff8020161b258 : 0xfffff801fee1b9ef : nt!MiInsertNonPagedPoolOnSlist+0x3df 0xfffff8020161b278 : 0xfffff801ff05305d : nt!ExAllocatePoolWithTag+0x61d 0xfffff8020161b2d8 : 0xfffff801fee7f5b9 : nt!KeInsertPriQueue+0x259 0xfffff8020161b2e0 : 0xfffff801ff13d140 : nt!NonPagedPoolDescriptor 0xfffff8020161b2e8 : 0xfffff801ff13d148 : nt!NonPagedPoolDescriptor+0x8 0xfffff8020161b310 : 0xfffff801ff13d290 : nt!NonPagedPoolDescriptor+0x150 0xfffff8020161b328 : 0xfffff801ff13d148 : nt!NonPagedPoolDescriptor+0x8 0xfffff8020161bbd8 : 0xfffff801fee41fb5 : nt!KiExecuteAllDpcs+0x335 0xfffff8020161bc10 : 0xfffff801ff146180 : nt!KiInitialPCR+0x180 0xfffff8020161bcf8 : 0xfffff801ff146180 : nt!KiInitialPCR+0x180 0xfffff8020161bd28 : 0xfffff801fee4153f : nt!KiRetireDpcList+0x8df 0xfffff8020161bd70 : 0xfffff801ff146180 : nt!KiInitialPCR+0x180 0xfffff8020161bdc0 : 0xfffff8002f8625d0 : afd!AfdTimeoutPoll 0xfffff8020161be80 : 0xfffff8002f8625d0 : afd!AfdTimeoutPoll 0xfffff8020161be90 : 0xfffff8002f8625d0 : afd!AfdTimeoutPoll 0xfffff8020161bea0 : 0xfffff8002f8625d0 : afd!AfdTimeoutPoll 0xfffff8020161beb0 : 0xfffff801fee29c20 : nt!PpmCheckPeriodicStart 0xfffff8020161bec0 : 0xfffff8002f8625d0 : afd!AfdTimeoutPoll 0xfffff8020161bed0 : 0xfffff8002f744da0 : CLASSPNP!TransferPacketRetryTimerDpc 0xfffff8020161bee0 : 0xfffff8002f744da0 : CLASSPNP!TransferPacketRetryTimerDpc 0xfffff8020161bef0 : 0xfffff8003240c680 : dxgkrnl!DpiFdoDpcForIsr 0xfffff8020161bf60 : 0xfffff8020161bdc0 : 0xfffff8002f8625d0 : afd!AfdTimeoutPoll 0xfffff8020161bfa8 : 0xfffff801fef5f965 : nt!KxRetireDpcList+0x5[/quote]

 

That is interesting. I loaded the driver for the wireless card directly from Dell and those are the latest video drivers as of last week. It looks like Nvidia released a new driver on 10/9/17. I'll load up the new video driver and replace the wifi driver with the one you posted instead of directly from Dell's website. I'll report back soon thanks!

 

Open administrative command prompt and type or copy and paste:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

4) chkdsk /x /r
This may take many hours so plan to run overnight.
5) Please locate the memory dump file: %SystemRoot%\MEMORY.DMP or C:\Windows\MEMORY.DMP

Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

Post a one drive or drop box share link into the thread.


5) Run HDTune: http://www.hdtune.com/to check the health,
scan for errors, no quick scan but full scan
run a benchmark.


It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
the health,
the error scan,
the benchmark incl. following
transfer rate,
access time,
burst rate,
cpu usage.
Take Screenshot in Windows 10 General Tips Tutorials

Code: Event[486]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2017-09-28T10:03:13.517 Event ID: 5 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-U0RLGRU Description: {Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.[/quote] Code: Event[453]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-09-28T10:03:10.807 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-U0RLGRU Description: Windows failed fast startup with error status 0xC000000F.[/quote]

 

Ok I've completed the steps in the above suggestions:

I've updated the NVidia and Intel wireless card drivers.

Here is the output from sfc and dism:
Code: C:\Windows\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\Windows\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.14393.0Image Version: 10.0.14393.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\Windows\system32>[/quote] I ran chkdsk.
Here is the link to drop box of the memory.dmp file (zipped):
https://www.dropbox.com/s/fhb40cpvwf...EMORY.zip?dl=0

And I have attached a zip file of the HDTune results.
hdtune_benchmark.zip

Please let me know if any more information is needed.

 

Use this link to find and post the chkdsk /x /r/ report into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

In the memory dump debugging there was 1 misbehaving driver:

igdkmd64.sys Intel Graphics driver Drivers & Software
This misbehaving driver you indicated in the earlier post that you have already fixed.

 

Here is the output from chkdsk:
chkdsk.txt

As far as the intel video driver I had not updated that one yet (again just loaded directly from Dells website - not sure how often they update those.) I had updated the WiFi card driver. I have just loaded the newest driver from Intels website so it is now up to date.

 

Have you had any crashes since you updated your graphics and wifi driver?

 

Not yet. It happens at least once a day almost always while in idle. Sometimes twice in an hour. I will keep it running and see how it goes. I will report back here if it crashes again. Thank you for your time and help.