New
#21
Well finally hit another BSOD while playing ark, Windows Stop code: Bad_Pool_callerAttachment 205479Attachment 205480
Well finally hit another BSOD while playing ark, Windows Stop code: Bad_Pool_callerAttachment 205479Attachment 205480
Attachment 205485Attachment 205486
Crash 2.
Open file explorer > this PC > C: > in the right upper corner search for C:\Windows\Memory.dmp > zip > post a share link into the thread using either:
one drive
drop box
google drive
Crash dump found at C:\WINDOWS\MEMORY.DMP
Creation date: 09/24/2018 20:27:31
Size on disk: 1060 MB
Well I was trying, but it has literally vanished, I tried google drive, one drive and they seemed to do nothing and now the file is missing I did manage to get a program to read the mini dumps but it keeps coming up with these, sorry man I promise i was uploading the file it isnt there and I didnt run a cleaner
1) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
2) re-install the Nvidia GPU driver from the Nvidia website
3) make sure that you check the clean install box and if available install the physx driver.
Display Driver Uninstaller Download version 17.0.8.2 (or use a new version if available)
https://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html
http://www.nvidia.com/Download/index.aspx
http://www.majorgeeks.com/files/details/display_driver_uninstaller.html
Code:Event[3079]: Log Name: System Source: Display Date: 2018-09-24T20:23:43.983 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-SM6S54N Description: Display driver nvlddmkm stopped responding and has successfully recovered.
Code:9/25/2018 12:23 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 95685c41-b466-425d-815b-72c0269375b3 Problem signature: P1: 141 P2: ffffd80e68e0e4a0 P3: fffff80b8504b664 P4: 0 P5: 360 P6: 10_0_17134 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180924-2023.dmp \\?\C:\WINDOWS\TEMP\WER-1288937-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB317.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB327.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB336.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB347.tmp.txt \\?\C:\Windows\Temp\WERDE2F.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_89fc2a5bcc87a1d8eb9092e1f2d844d9d859cec8_00000000_cab_1a17dfa5 Analysis symbol: Rechecking for solution: 0 Report Id: 3758abad-d836-4f09-807e-2d659d9d04de Report Status: 268435456 Hashed bucket: Cab Guid: 0 9/25/2018 12:02 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: ebc9903d-ca79-4d75-8f3d-40e13595a82b Problem signature: P1: 141 P2: ffffbe0a7f472010 P3: fffff8007b3eb664 P4: 0 P5: 5188 P6: 10_0_17134 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180924-1959.dmp \\?\C:\WINDOWS\TEMP\WER-16109-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B12.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B23.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B32.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B42.tmp.txt \\?\C:\Windows\Temp\WER9B95.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_3abd394ae9f8736c9458c5a17adf42d12cbadf_00000000_cab_21ac9cfb Analysis symbol: Rechecking for solution: 0 Report Id: c39beacf-ad4a-4cce-87af-1244cea69b7b Report Status: 268435456 Hashed bucket: Cab Guid: 0 8/11/2018 2:30 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 116efd21-11cb-4417-b612-93cd33c53fe1 Problem signature: P1: 141 P2: ffff9e8d2f06f4a0 P3: fffff80c9acb07f8 P4: 0 P5: 2b68 P6: 10_0_17134 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180810-2229.dmp \\?\C:\WINDOWS\TEMP\WER-29603593-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC244.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC255.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC254.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC265.tmp.txt \\?\C:\Windows\Temp\WERE5CB.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_f18ac9bf327051e47459ad62a6ebc770faac66df_00000000_cab_2d6fe8f7 Analysis symbol: Rechecking for solution: 0 Report Id: 80c2bb2e-fe4f-4116-a2a0-dac4f7881fff Report Status: 268435456 Hashed bucket: Cab Guid: 0
Alright I will do this, I did manage to get this I dont know if it is helpful but I will post it for you to see.Attachment 205493Attachment 205494Attachment 205495
Download and install: Everything
voidtools
This software will index everything on all drives.
It can be set to launch on boot or when you need it.
It is night and day compared to windows search as the results are instantaneous.
Search using:
c:\windows\memory.dmp
memory.dmp
*.dmp
See if you can find any memory dumps that are < one week old.
It's very likely that the GPU driver either caused or was involved in the crashes.
This could be confirmed if there were a memory.dmp displaying the misbehaving driver(s).
The bsod software tools bluescreenview and whocrashed can perform low level debugging.
The tools that we used provide a higher level of debugging and often find the misbehaving drivers.
The more the crashes the easier the debugging as there are more crashes that are available for debugging and for confirmation.
I will do this too, I am going to install 399 driver as 411 is all over the forums for BSOD and it didnt do this until I updated the Video card driver
https://forums.geforce.com/default/t...ther-problems/
This was the driver version in use during the crash:
Code:Name NVIDIA GeForce GTX 1080 Ti PNP Device ID PCI\VEN_10DE&DEV_1B06&SUBSYS_66963842&REV_A1\4&4390B99&0&0008 Adapter Type GeForce GTX 1080 Ti, NVIDIA compatible Adapter Description NVIDIA GeForce GTX 1080 Ti Adapter RAM (1,048,576) bytes Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_cad5fc8f5ca41c15\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_cad5fc8f5ca41c15\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_cad5fc8f5ca41c15\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_cad5fc8f5ca41c15\nvldumdx.dll Driver Version 24.21.14.1163 INF File oem11.inf (Section132 section) Color Planes Not Available Color Table Entries 4294967296 Resolution 1920 x 1080 x 144 hertz Bits/Pixel 32 Memory Address 0xDE000000-0xDF0FFFFF Memory Address 0xC0000000-0xD1FFFFFF Memory Address 0xD0000000-0xD1FFFFFF I/O Port 0x0000E000-0x0000EFFF IRQ Channel IRQ 16 Driver c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_cad5fc8f5ca41c15\nvlddmkm.sys (24.21.14.1163, 19.24 MB (20,177,280 bytes), 9/19/2018 7:32 PM)
Code:nvlddmkm nvlddmkm nvlddmkm Kernel Manual Stopped OK FALSE FALSE 9,785,344 7,737,344 0 9/18/2018 9:27:05 AM C:\WINDOWS\system32\DriverStore\FileRepository\n 36,864Code:nvlddmkm nvlddmkm c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_cad5fc8f5ca41c15\nvlddmkm.sys Kernel Driver No Manual Stopped OK Ignore No NoCode:nvlddmkm.sys Tue Sep 18 06:27:05 2018 (5BA0FD29)
After reverting to 399.xx I haven't had a single issue, no hiccups, bsod or crash otherwise. I can't say it for sure but based on what else I found and what you've shown me here I firmly believe that it was the 411.xx Nvidia driver for the 10 Series.
As always Zbook, thank you again for time and time over helping me when I needed it.
Been running since 0600 this morning non stop.