New
#11
Here's the latest mini dump as I was literally preparing to use DDU:
072718-15531-01.dmp - Google Drive
Here's the latest mini dump as I was literally preparing to use DDU:
072718-15531-01.dmp - Google Drive
Your latest dump shows a bugcheck code of 0x5 -
This is a rare code and generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).Code:INVALID_PROCESS_ATTACH_ATTEMPT (5) Arguments: Arg1: ffffa885fb8c9090 Arg2: ffffa885fb8c9080 Arg3: 0000000000000000 Arg4: ffffa885f3a9b700
I don't see any signs of the KeAttachProcess command in any of the processor threads so I'm a bit stuck. Processor #16 was involved:
Code:# 16 TID:0011 kb kbn kbnL kn knL kpn kPn # Child-SP RetAddr Call Site 00 ffffba83`a98df968 fffff801`3989697e nt!KeBugCheckEx 01 ffffba83`a98df970 fffff801`39791e06 nt!PspExitThread+0x1c01f2 02 ffffba83`a98dfa70 fffff801`397919ae nt!PspTerminateThreadByPointer+0x96 03 ffffba83`a98dfab0 fffff801`393c3a43 nt!NtTerminateThread+0x4a 04 ffffba83`a98dfb00 00007ff9`78aea914 nt!KiSystemServiceCopyEnd+0x13 05 00000000`3352fe58 00000000`00000000 0x00007ff9`78aea914
The attached process was AfterFX.exe from Adobe.
Code:Owning Process ffffa885fb8c9090 Image: <Invalid process> Attached Process ffffa885fb8c9080 Image: AfterFX.exe
This might have been a one-off, it is quite different to all the others you have been getting.
Understood Phil, thank you. DDU'ing now.
There are two log collectors: DM and BETA
The BETA log collector is at the bottom of this web page:
BSOD - Posting Instructions - Windows 10 Forums
BSOD - Posting Instructions - Windows 10 Forums
Please run the BETA log collector and post a zip into the thread.
(extract > open)
Use the txt and images in this thread in case there are problems running the BETA log collector: (post #5)
DM Log tool problem Solved - Windows 10 Forums
DM Log tool problem Solved - Windows 10 Forums
Open file explorer > this PC > C: > in the right upper corner search for: C:\windows\memory.dmp > zip > post a one drive or drop box share link into the thread
Damn. Just got another one. This is happened just after I started a GPU rendering session however it occured after the render completed and I went to move my mouse. I'm starting to get the feeling it has something to do with how I'm using my GPUs which is for GPU rendering. I have 3x1080s and 1x1080ti. Three of the cards are liquid cooled (via AIO) and the other is air cooled. Maybe the air cooled card is getting too hot? I was really hoping that DDU was going to fix this
Here's the zip you asked for as well zbook.
Crashes have also occurred at idle as well... I also successfully ran DDU and installed latest drivers 2 days ago.
The misbehaving driver identified in the debugging was part of Acronis.
Uninstall and reinstall Acronis software.
file_protector.sys
Code:file_protect Acronis File Protector Acronis File Protector File System Auto Running OK TRUE FALSE 0 471,040 0 12/12/2017 5:08:30 AM C:\WINDOWS\system32\DRIVERS\file_protector.sys 8,192Run this link and post a zip into the thread:Code:file_protector Acronis File Protector Driver c:\windows\system32\drivers\file_protector.sys File System Driver Yes Auto Running OK Normal No Yes
(extract > open)
https://www.tenforums.com/attachment...-v2-beta10.zip
Use the txt and images in this thread in case there are problems running the BETA log collector: (post #5)
DM Log tool problem Solved - Windows 10 Forums
DM Log tool problem Solved - Windows 10 Forums