Windows 10: Computer Only Reboots When I'm Not Around. Logs & Detail In Post

Hello All,

When I'm at work during the day and sometimes at night when I'm sleeping, on average once a day, my PC will reboot on its own. This has been going on the past few days. It never seems to do it when I'm using it, which I find odd. I'm sure it's a software problem. Detailed computer specs below, and required files attached. I can't seem to figure it out and don't want to do further damage. I've been down that road unfortunately. Never again.

If someone can tell me what the guilty party is I'd appreciate it. Thank you.

Sincerely,

Frank

PS - Also, how does one delete previously uploaded files in their account? I can't figure this out for the life of me.


Name Intel Core i7 3770 Codename Ivy Bridge
Specification Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz cores 37x

Memory Size 8192 MBytes

Samsung SSD 850 EVO mSATA 1TB Capacity 931.5 GB

NVIDIA GeForce GTX 660

Microsoft Windows 10 (10.0) Home 64-bit

:)

 

windows media player rich preview handler displays in wrong Place (And in Task bar) after April update

I discovered a temporary work-around.

If I double-click the file to open it in Windows Media Player, and then close it, the next time I use Windows Explorer, the previews not only display in the proper locations, but they are playable too.

Unfortunately this is only temporary. I'm not exactly sure when it gets reset to the unwanted behavior, but I think it's when the PC reboots or you log out of Windows.

 

No seriously, how to I prevent Windows 10 from automatically updating?

This has been posted here dozens of times, always asking how to deactivate automatic updates. However, the only answers I can find are for how to change the conditions around when it automatically updates. I don't mind the notifications, but the option
to reboot the computer should remain entirely in the user's control. How can I do this? I'm sick of losing work to this.

 

That I can help you with. Uploaded files that you don't use in a post get deleted automatically after a while. For the others, click the 'Settings' link, at the top near the far right. Scroll down and you'll find 'Attachements' near the bottom of the list on the left. Or this link will take you straight there. Windows 10 Help Forums

 

Hello frankma,

Yes, the crash dump files all point to a network driver causing these problems. The sequence of events leading to the crash is shown below (in reverse order):

Code: STACK_TEXT: ffffe381`d90f7868 fffff802`71300f87 : 00000000`000000c2 00000000`00000007 00000000`206c644d 00000000`040d0005 : nt!KeBugCheckEx ffffe381`d90f7870 fffff806`405b4d3d : ffffa609`895fdde0 ffffa609`7de00000 00000000`00000001 00000000`00000000 : nt!ExFreePoolWithTag+0xf67 ffffe381`d90f7970 ffffa609`895fdde0 : ffffa609`7de00000 00000000`00000001 00000000`00000000 00000000`00000004 : rtwlanu+0x44d3d ffffe381`d90f7978 ffffa609`7de00000 : 00000000`00000001 00000000`00000000 00000000`00000004 fffff806`40b165e5 : 0xffffa609`895fdde0 ffffe381`d90f7980 00000000`00000001 : 00000000`00000000 00000000`00000004 fffff806`40b165e5 ffffe381`d90f7ba0 : 0xffffa609`7de00000 ffffe381`d90f7988 00000000`00000000 : 00000000`00000004 fffff806`40b165e5 ffffe381`d90f7ba0 00000000`00000000 : 0x1 *** WARNING: Unable to verify timestamp for rtwlanu.sys *** ERROR: Module load completed but symbols could not be loaded for rtwlanu.sys[/quote] I would advise you to rollback the driver for your Realtek Wireless Network or if you can't do this just install the latest one from the DELL website which is an older driver than the one you have. You may also need to stop Windows from automatically updating your drivers to prevent it becoming updated by Microsoft and starting the BSOD events again.

 

Hmm, ok thanks, I never thought this to be the issue. It just happened out of the blue. I'll change it out and post whether or not it solves the problem. Obviously I'll need some time to confirm. Thank you for the tip, I really appreciate it.

 

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 /f /r
This may take many hours so plan to run overnight.

Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

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


Run chkdsk and hd tune on each drive and post the images and results into the thread.

 

Just wanted to say thank you. I wanted to know for sure my problem is solved and it is. Replacing the network driver indeed did the trick. Thank you so much for saving my sanity.

 

That's great that the network driver solved your problem.

During the workup of this problem other problems were discovered.

The event logs displayed problems with the drive:

The IO operation at logical block address 0x127a8d8f for Disk 9 (PDO name: \Device\000002b3) was retried.
The device, \Device\Harddisk9\DR9, has a bad block.
The IO operation at logical block address 0x0 for Disk 8 (PDO name: \Device\0000009c) was retried.
The IO operation at logical block address 0xb203c for Disk 5 (PDO name: \Device\0000009a) was retried.
The IO operation at logical block address 0x8e690db for Disk 4 (PDO name: \Device\00000098) was retried.

See post #5 for troubleshooting the drives.


Code: Event[2313]: Log Name: System Source: Disk Date: 2017-09-27T20:20:43.717 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The IO operation at logical block address 0x1717734 for Disk 9 (PDO name: \Device\0000028d) was retried.Event[2314]: Log Name: System Source: Disk Date: 2017-09-27T20:22:28.966 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The IO operation at logical block address 0x1717734 for Disk 9 (PDO name: \Device\0000028d) was retried.Event[2315]: Log Name: System Source: Disk Date: 2017-09-27T20:24:14.165 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The IO operation at logical block address 0x1717734 for Disk 9 (PDO name: \Device\0000028d) was retried.Event[2316]: Log Name: System Source: Disk Date: 2017-09-27T20:25:59.492 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The IO operation at logical block address 0x171773b for Disk 9 (PDO name: \Device\0000028d) was retried.Event[2317]: Log Name: System Source: Disk Date: 2017-09-27T20:26:24.747 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The device, \Device\Harddisk9\DR9, has a bad block.Event[2318]: Log Name: System Source: Disk Date: 2017-09-27T20:27:31.180 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The device, \Device\Harddisk9\DR9, has a bad block.Event[2319]: Log Name: System Source: Disk Date: 2017-09-27T20:47:42.200 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The IO operation at logical block address 0x1717734 for Disk 9 (PDO name: \Device\0000028d) was retried.Event[2320]: Log Name: System Source: Disk Date: 2017-09-27T20:49:27.205 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The IO operation at logical block address 0x1717734 for Disk 9 (PDO name: \Device\0000028d) was retried.Event[2321]: Log Name: System Source: Disk Date: 2017-09-27T20:51:13.438 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The IO operation at logical block address 0x1717734 for Disk 9 (PDO name: \Device\0000028d) was retried.Event[2322]: Log Name: System Source: Disk Date: 2017-09-27T20:53:00.632 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The IO operation at logical block address 0x1717739 for Disk 9 (PDO name: \Device\0000028d) was retried.Event[2323]: Log Name: System Source: Disk Date: 2017-09-27T20:54:30.408 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The device, \Device\Harddisk9\DR9, has a bad block.Event[2324]: Log Name: System Source: Disk Date: 2017-09-27T20:54:34.385 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The device, \Device\Harddisk9\DR9, has a bad block.Event[2325]: Log Name: System Source: Disk Date: 2017-09-27T21:13:00.717 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The IO operation at logical block address 0x1717734 for Disk 9 (PDO name: \Device\0000028d) was retried.Event[2326]: Log Name: System Source: Disk Date: 2017-09-27T21:14:47.753 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The IO operation at logical block address 0x1717734 for Disk 9 (PDO name: \Device\0000028d) was retried.Event[2327]: Log Name: System Source: Disk Date: 2017-09-27T21:16:34.977 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The IO operation at logical block address 0x1717734 for Disk 9 (PDO name: \Device\0000028d) was retried.Event[2328]: Log Name: System Source: Disk Date: 2017-09-27T21:18:22.407 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The IO operation at logical block address 0x1717739 for Disk 9 (PDO name: \Device\0000028d) was retried.Event[2329]: Log Name: System Source: Disk Date: 2017-09-27T21:19:09.502 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The device, \Device\Harddisk9\DR9, has a bad block.Event[2330]: Log Name: System Source: Disk Date: 2017-09-27T21:19:55.546 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stud-PC Description: The device, \Device\Harddisk9\DR9, has a bad block.[/quote]

 

You are welcome! *Smile