RADAR_PRE_LEAK_64 plus Display Crashes

[KibblesAwoo | TTV]

I'm experiencing random display crashes during play. Only error I was able to locate was the below memory leak in the Windows 10 event log. Any help would be appreciated! Thank you in advance!

Fault bucket 129336032293, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: YookaLaylee64.exe
P2: 5.4.2.39900
P3: 10.0.14393.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
/?/C:/Users/User/AppData/Local/Temp/RDR755A.tmp/empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER757A.tmp.WERInternalMetadata.xml
((These files don't exist))
These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: a76bc638-1ed7-11e7-b42e-b8975a07d9ac
Report Status: 0
Hashed bucket: 6365e51a25729fb4a39bed757f9e422c

System Information

OS Name	Microsoft Windows 10 Pro
Version	10.0.14393 Build 14393
Other OS Description 	Not Available
OS Manufacturer	Microsoft Corporation
System Name	PUPTOP
System Manufacturer	BIOSTAR Group
System Model	TZ77A
System Type	x64-based PC
System SKU	None
Processor	Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz, 3401 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date	American Megatrends Inc. 4.6.5, 2/14/2012
SMBIOS Version	2.7
Embedded Controller Version	255.255
BIOS Mode	UEFI
BaseBoard Manufacturer	BIOSTAR Group
BaseBoard Model	Not Available
BaseBoard Name	Base Board
Platform Role	Desktop
Secure Boot State	Unsupported
PCR7 Configuration	Binding Not Possible
Windows Directory	C:\Windows
System Directory	C:\Windows\system32
Boot Device	\Device\HarddiskVolume2
Locale	United States
Hardware Abstraction Layer	Version = "10.0.14393.206"
User Name	PUPTOP\SDHusky
Time Zone	Pacific Daylight Time
Installed Physical Memory (RAM)	8.00 GB
Total Physical Memory	7.97 GB
Available Physical Memory	4.29 GB
Total Virtual Memory	9.22 GB
Available Virtual Memory	5.62 GB
Page File Space	1.25 GB
Page File	C:\pagefile.sys
Hyper-V - VM Monitor Mode Extensions	Yes
Hyper-V - Second Level Address Translation Extensions	Yes
Hyper-V - Virtualization Enabled in Firmware	No
Hyper-V - Data Execution Protection	Yes

Graphics Card: nVidia GeForce GTX 560 Ti
Driver Version: 381.65

[KibblesAwoo | TTV]

引用自 Spawk：

引用自 PedigreetheHusky：

Graphics Card: nVidia GeForce GTX 560 Ti
Driver Version: 381.65

You posted a log from Windows' memory resource warning service, so don't you think it would be helpful to post the amount of system RAM in your computer and the amount of VRAM on your 560 Ti? It also wouldn't hurt to post your processor information :)

Processor information (are you referring to something else?): Processor Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz, 3401 Mhz, 4 Core(s), 4


RAM: Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.97 GB
Available Physical Memory 4.29 GB
Total Virtual Memory 9.22 GB
Available Virtual Memory 5.62 GB


As for VRAM: http://i.imgur.com/88A6X5K.png


Any further graphics card questions, the best I can do is link the technical specs: http://www.geforce.com/hardware/desktop-gpus/geforce-gtx-560ti/specifications

[KibblesAwoo | TTV]

引用自 Spawk：

Sorry, I overlooked the system information part of your post. I was bouncing in between threads. Did you go to the Nvidia Control Panel > Manage 3D Settings > Global and check if your preferred graphics processor is set to 'High-performance Nvidia processor'?

I am looking through the global settings and do not see this option. Is there another way to set high performance as default?

[KibblesAwoo | TTV]

Here is a crash dump from WinDbg that I found for every display crash I had within Yooka Laylee.

It looks as if the display crashes are related to the nVidia display driver. I'm going to try to do a clean driver install and see if that fixes things. In the meantime, if you have any additional suggestions, I'd like to hear them.

Use !analyze -v to get detailed debugging information.

BugCheck 141, {ffffcc09db69c010, fffff8073f057914, 0, 7d0}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+157914 )
_________________________________________________________________________

VIDEO_ENGINE_TIMEOUT_DETECTED (141)
One of the the display engines failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: ffffcc09db69c010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8073f057914, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 00000000000007d0, Optional internal context dependent data.

Debugging Details:
_________________________________________________________________________


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.14393.953 (rs1_release_inmarket.170303-1614)

DUMP_TYPE:  2

BUGCHECK_P1: ffffcc09db69c010

BUGCHECK_P2: fffff8073f057914

BUGCHECK_P3: 0

BUGCHECK_P4: 7d0

FAULTING_IP: 
nvlddmkm+157914
fffff807`3f057914 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_ENGINE_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


CPU_COUNT: 4

CPU_MHZ: d47

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

BUGCHECK_STR:  0x141

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  PUPTOP

ANALYSIS_SESSION_TIME:  04-11-2017 21:18:12.0062

ANALYSIS_VERSION: 10.0.15063.137 amd64fre

STACK_TEXT:  
ffffb780`754d2570 fffff807`3c0bb5bc : ffffcc09`db69c010 ffffcc09`db69c010 ffffb780`754d2710 ffffcc09`dae72010 : watchdog!WdDbgReportRecreate+0x10c
ffffb780`754d25c0 fffff807`3ec14d44 : 00000000`00000000 00000000`c00000bb ffffcc09`d94cd000 ffffcc09`d94cd000 : dxgkrnl!TdrUpdateDbgReport+0xec
ffffb780`754d2610 fffff807`3ec8eef9 : ffffcc09`d94cd000 00000000`00000000 00000000`00000001 ffffcc09`d9274001 : dxgmms2!VidSchiResetEngine+0x74c
ffffb780`754d2900 fffff807`3ec73a56 : ffffcc09`d94cd000 00000000`00000002 00000000`00000000 ffffcc09`d9274000 : dxgmms2!VidSchiResetEngines+0x99
ffffb780`754d2940 fffff807`3ec52eb7 : 00000000`00000002 00000000`00018a23 00000000`0032a5da 00000000`00000001 : dxgmms2! ?? ::NNGAKEGL::`string'+0xf8d6
ffffb780`754d29b0 fffff807`3ebfa4c4 : ffffcc09`d965b300 ffffcc09`d9274000 ffffcc09`d965b308 00000000`00000002 : dxgmms2!VidSchiWaitForSchedulerEvents+0x337
ffffb780`754d2a70 fffff807`3ec5f27f : ffffcc09`daeb4900 ffffb780`754d2bd0 ffffcc09`daeb4900 ffffcc09`00000000 : dxgmms2!VidSchiScheduleCommandToRun+0x3d4
ffffb780`754d2b80 fffff807`3ec5f240 : ffffcc09`d9274500 ffffcc09`d9274000 00000000`00000080 fffff807`3ec5f1c0 : dxgmms2!VidSchiRun_PriorityTable+0x2f
ffffb780`754d2bd0 fffff800`622c72d5 : fffff800`6254d180 fffff800`62364baf 00000000`06a802b5 ffffcc09`d94cc800 : dxgmms2!VidSchiWorkerThread+0x80
ffffb780`754d2c10 fffff800`62364c86 : fffff800`6254d180 ffffcc09`d94cc800 fffff800`622c7294 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffffb780`754d2c60 00000000`00000000 : ffffb780`754d3000 ffffb780`754cd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  b0c892d0727a58d7d65954dcbff4afa4bb2d61d7

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  557e5e1a298761d7c57fe88ac395a90aa3ce25af

THREAD_SHA1_HASH_MOD:  d61bf2826c83f42798f71aa711aa4f2cb3225799

FOLLOWUP_IP: 
nvlddmkm+157914
fffff807`3f057914 ??              ???

SYMBOL_NAME:  nvlddmkm+157914

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  58cb13e2

FAILURE_BUCKET_ID:  LKD_0x141_IMAGE_nvlddmkm.sys

BUCKET_ID:  LKD_0x141_IMAGE_nvlddmkm.sys

PRIMARY_PROBLEM_CLASS:  LKD_0x141_IMAGE_nvlddmkm.sys

TARGET_TIME:  2017-04-11T23:53:45.000Z

OSBUILD:  14393

OSSERVICEPACK:  953

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-03-03 22:09:56

BUILDDATESTAMP_STR:  170303-1614

BUILDLAB_STR:  rs1_release_inmarket

BUILDOSVER_STR:  10.0.14393.953

ANALYSIS_SESSION_ELAPSED_TIME:  4ce

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:lkd_0x141_image_nvlddmkm.sys

FAILURE_ID_HASH:  {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc}

[KibblesAwoo | TTV]

If it helps, I've been able to trigger this crash consistently even on lowest display settings in high performance mode just by entering Hivory Towers as Yooka and Laylee for the first time.

[KibblesAwoo | TTV]

Clean reinstall of nVidia does not fix this issue. I feel like it definitely has to be an issue with Yooka Laylee software itself. Here's a crash dmp from the Yooka Laylee folder, I hope it will help resolve this issue. I'm getting very frustrated just trying to play this game.

Any help would be appreciated! Thanks in advance!

[KibblesAwoo | TTV]

Crash Dump from Yooka Laylee folder. https://pastebin.com/wtkF83pP

Unity Error log from Yooka Laylee folder. https://pastebin.com/w21Vki1A

Output log from Yooka Laylee folder. https://pastebin.com/KSvB0FDE

[KibblesAwoo | TTV]

引用自 Spawk：

Did you try running the DirectX and Microsoft Visual C++ installers, usually located in the _CommonRedist folder in the game's install directory?

I did, the crash still occurs.

[KibblesAwoo | TTV]

Here is all the information again, including my DxDialog. If someone is able to help, please let me know.

DxDialog: https://pastebin.com/sPnrgdvz

Crash Dump from Yooka Laylee folder. https://pastebin.com/wtkF83pP

Unity Error log from Yooka Laylee folder. https://pastebin.com/w21Vki1A

Output log from Yooka Laylee folder. https://pastebin.com/KSvB0FDE

[Team17_Assistance]

Hey PedigreetheHusky,


I'm sorry for the delay in responding to your thread and thank you for the information you have provided.
Could you please confirm whether or not you are able to play the game at this point or if you are still experiencing the issue you previously mentioned.
If you are still experiencing the issue, then I will do my best to assist you further in resolving the matter.

Apologies for any inconvenience this may have caused.


Thank you,
Team17_Assistance