Windows 10: Repeated crashes on shut down

Hi


I have a Windows 10 Pro X64 setup on a Asus Z-170A that has been slow to shut down for a while now.


It MAY have started after the RS 5 install but that was a while ago.


Anyway, I saw several examples of crashes in the System event log.


Here is the latest one from last night's shut down -


The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff8c8d2d8c5800, 0xfffff800731ac7d0, 0xffff8c8d3c6df9d0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 45257772-a94d-4193-916c-1104dc1c6ae5.


I have done two full rebuilds in the last week and it was ok for a day or two and then it has started again.


This is what I have found using WINDBG -


0: kd> .bugcheck
Bugcheck code 0000009F
Arguments 00000000`00000003 ffff8c8d`2d8c5800 fffff800`731ac7d0 ffff8c8d`3c6df9d0
0: kd> !poaction 2

Allocated power irps (PopIrpList - fffff800706c0f20)
IRP: ffff8c8d35553010 (wait-wake/S4), PDO: ffff8c8d3553c110
IRP: ffff8c8d355c76f0 (wait-wake/S4), PDO: ffff8c8d354de060
IRP: ffff8c8d354e3660 (wait-wake/S4), PDO: ffff8c8d354df060
IRP: ffff8c8d355ca610 (wait-wake/S4), PDO: ffff8c8d354e1540
IRP: ffff8c8d3b282270 (wait-wake/S4), PDO: ffff8c8d35520480
IRP: ffff8c8d34eda9a0 (wait-wake/S4), PDO: ffff8c8d3555b800
IRP: ffff8c8d3adb73f0 (wait-wake/S4), PDO: ffff8c8d35d41590
IRP: ffff8c8d39292010 (wait-wake/S4), PDO: ffff8c8d3555c060
IRP: ffff8c8d39acfac0 (wait-wake/S4), PDO: ffff8c8d34fe2740
IRP: ffff8c8d3c6df9d0 (set/S4), PDO: ffff8c8d2d8c5800, CURRENT: ffff8c8d2d941050, NOTIFY: ffff8c8d2d84e0a0

Irp worker threads (PopIrpThreadList - fffff800706b9600)
THREAD: ffff8c8d2d8cb080 (static)
THREAD: ffff8c8d2d85e4c0 (static)
THREAD: ffff8c8d3ae2c040 (dynamic)
THREAD: ffff8c8d3a11c080 (dynamic)
THREAD: ffff8c8d3965c080 (dynamic)
THREAD: ffff8c8d3f313080 (dynamic)
THREAD: ffff8c8d3a9112c0 (dynamic)
THREAD: ffff8c8d3a98d080 (dynamic)
THREAD: ffff8c8d3b38d440 (dynamic)
THREAD: ffff8c8d3b085080 (dynamic)
THREAD: ffff8c8d3b475080 (dynamic)
THREAD: ffff8c8d3b498080 (dynamic)
THREAD: ffff8c8d3af8e080 (dynamic)
THREAD: ffff8c8d3a97c400 (dynamic)
THREAD: ffff8c8d3a97e400 (dynamic)

0: kd> !irp ffff8c8d`3c6df9d0
Irp is active with 3 stacks 2 is current (= 0xffff8c8d3c6dfae8)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
cmd flg cl Device File Completion-Context
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffff8c8d2d941050 00000000 fffff80070791b70-ffff8c8d2dd7a050 Success Error Cancel pending
\Driver\ACPI nt!PopSystemIrpCompletion
Args: 00015600 00000000 00000005 00000003
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-ffff8c8d2dd7a050

Args: 00000000 00000000 00000000 00000000
0: kd> !drvobj \Driver\ACPI
Driver object (ffff8c8d2d93f070) is for:
\Driver\ACPI
Driver Extension List: (id , addr)

Device Object list:
ffff8c8d3b5658a0 ffff8c8d3627ae00 ffff8c8d36278e00 ffff8c8d360f2e00
ffff8c8d2f5f1880 ffff8c8d2f5f0ce0 ffff8c8d2f5f0ab0 ffff8c8d2f5f0880
ffff8c8d2f5efce0 ffff8c8d2f5efab0 ffff8c8d2f5ef880 ffff8c8d2f5ecce0
ffff8c8d2f5ecab0 ffff8c8d2f5ec880 ffff8c8d2f5eac80 ffff8c8d2f5e3c60
ffff8c8d2f5ddc60 ffff8c8d2f5dbc60 ffff8c8d2f5d1c80 ffff8c8d2f5d1a70
ffff8c8d2f5d1860 ffff8c8d2f5d0cd0 ffff8c8d2f5d0ac0 ffff8c8d2f8a7db0
ffff8c8d2f8cedb0 ffff8c8d2f8a5db0 ffff8c8d2f8a3db0 ffff8c8d2f8a1db0
ffff8c8d2f564c60 ffff8c8d2f76dbb0 ffff8c8d2f76d9a0 ffff8c8d2f76cdc0
ffff8c8d2f76cbb0 ffff8c8d2f76c9a0 ffff8c8d2f76bdc0 ffff8c8d2f76bbb0
ffff8c8d2f76b9a0 ffff8c8d2f76adc0 ffff8c8d2f76abb0 ffff8c8d2f76a9a0
ffff8c8d2f769dc0 ffff8c8d2f769bb0 ffff8c8d2f7699a0 ffff8c8d2f768bf0
ffff8c8d2f7689c0 ffff8c8d2f77ac30 ffff8c8d2f77aa00 ffff8c8d2f744e30
ffff8c8d2f4979c0 ffff8c8d2f515bf0 ffff8c8d2f5159c0 ffff8c8d2f4d6c30
ffff8c8d2f4d6a00 ffff8c8d2f502c30 ffff8c8d2f502a00 ffff8c8d2f465c30
ffff8c8d2f465a00 ffff8c8d2f4c3c30 ffff8c8d2f4c3a00 ffff8c8d2f44dc80
ffff8c8d2f41ec80 ffff8c8d2d97bc90 ffff8c8d2d94cc90 ffff8c8d2f419ca0
ffff8c8d2d86b060 ffff8c8d2d941050
0: kd> !lmi ACPI
Loaded Module Info: [acpi]
Module: ACPI
Base Address: fffff800733d0000
Image Name: ACPI.sys
Machine Type: 34404 (X64)
Time Stamp: a49a6357 (This is a reproducible build file hash, not a true timestamp)
Size: c8000
CheckSum: c679f
Characteristics: 22
Debug Data Dirs: Type Size VA Pointer
CODEVIEW 21, 71f1c, 7051c RSDS - GUID: {5C41D6FD-ABE8-0126-3127-50C3CB66F838}
Age: 1, Pdb: acpi.pdb
POGO 614, 71f40, 70540 [Data not mapped]
REPRO 0, 0, 0 [Debug data not mapped]
Image Type: MEMORY - Image read successfully from loaded memory.
Symbol Type: PDB - Symbols loaded successfully from symbol server.
C:\ProgramData\dbg\sym\acpi.pdb\5C41D6FDABE80126312750C3CB66F8381\acpi.pdb
Load Report: public symbols , not source indexed
C:\ProgramData\dbg\sym\acpi.pdb\5C41D6FDABE80126312750C3CB66F8381\acpi.pdb

Any idea how I can fix this please ?


I have a MEMORY.DMP file if that would help.


Thanks

:)

 

all games crash!

I suggest you run rthdribl > http://www.daionet.gr.jp/~masa/archives/rthdribl_1_2.zip
Increase the window size step by step and watch your vga temps permanently.
What happens?
If it crashes, run at stock speeds as suggested before and retry.

P.S.: When your system locks, does the display signal turn off after a time?
Stuttering sound or no sound at all when freezing?
What X1800XT model do you own exactly?

 

Repeated Crash-rebooting on Windows 10 - what hardware is at fault?

Brief overview
About a couple weeks ago, my custom-desktop (built 2015) started hard crashing and auto-rebooting. The computer has crashed so many times at this point that I can barely keep track (like 50 times in 2 weeks). When I start it up in the morning, it works fine for a few hours, then it will suddenly crash, reboot, and then wait 5-10 min before crashing again and starts to enter the death-spiral of repeated crashes that become increasingly more frequent. Last time this happened (yesterday), it couldn't even get past the BIOS splash screen before another crash. Seems like a short circuit? I have tried a lot of troubleshooting steps so-far, and will list that out in detail below - but for those TL;DR, I am 98% sure it is hardware related, the question is, how to isolate what piece of hardware is at fault? How to test? motherboard or power supply or something else?

Computer Specs:

PS: EVGA 750W GOLD Power Supply

MB: Asus Z170-A, running American Megatrends BIOS 3802 3/5/2018 (UEFI)

CPU: Intel i5-6600K Skylake CPU @ 3.50GHz, 3504 Mhz

GPU: EVGA NVIDIA GeForce GTX 980 Ti

Troubleshooting steps taken thus far:

1. I dis-enabled auto-reboot (per suggestions online), and then when machine crashed again, it automatically rebooted, which clearly seems to indicate that the problem is not triggered by Windows.
   
2. I checked the Windows Event Viewer, and here is what it looked like:
   Kernel-Power Event log
   There is no detail available beyond this event ID, because the machine apparently doesn't have a chance to write a dump file prior to crashing, which strongly suggests that it is a hardware problem. The crashes happened several times with no software running, so that confirms that hardware is likely suspect
   
3. I opened up machine and thoroughly cleaned it and checked pin connections between power supply and the motherboard. I re-seated these connections, and it seemed to stop the crashes for 5-6 days, but then it started happening again.
   
4. I updated BIOS to most current build available
   
5. I installed a CPU temperature reading program to see if the i5-6600K is overheating. Here is a normal read-out (cold start)
   CPU Temp cold start
   followed by a read-out I was able to capture shortly after a crash. I don't know about you, but 57°C seems awfully hot for a processor. Makes me start to think that the processor is overheating? Which gets to the next thing
   CPU Temp after crash
   
6. I have tried tweaking the BIOS to disenable overclocking but I am thus far unsuccessful - I don't know why the ASUS Z170-A motherboard is so hard to throttle down, the 'EZ menu' doesn't provide an easy option to just shut it off, and in Advanced mode, even with most settings in the 'AI Tweaker' panel disenabled, it still overclocks. Still looking for a good guide out there that can show me how to do this.
   

Can you provide any insight? I am at my wits end

 

Repeated Crashes and Boot Errors Apparently Caused by Driver Updates







Still no boot. Moving on to the next step.