Asus G752VSK hard crashing when playing games

I know that a few people have had issues similar to mine on the same model (and other computers, even desktops, that have 1070s).

But the guys from the local Asus branch keep insisting that there's nothing wrong with it, so I'm also trying to track down the source myself.

I already contacted the global branch through the foruns, as they seemed to be able to help some customers out by contacting the local branches. If that doesn't work, I guess I'll have to contact my local consumer defense association and/or the court .

Here are the Prime95 results.
Max temperature: 80 ºC (in the beginning, from then on it was always between 69 ºC and 74 ºC)
Test duration: 3 hour 2 minutes.

Sorry, I realized I forgot to post the link to the drivers page: ROG G752VS (7th Gen Intel Core) Driver & Tools | Laptops | ASUS Global

I believe all your crashes during the games have been associated with the LiveKernel 141 Events. In the most recent set of logfiles there were seven of these reports.

The report shows:

ReportDescription=O problema com o hardware fez com que o Windows deixasse de funcionar corretamente.

This translates: The problem with the hardware caused Windows to stop working correctly.


This would seem to confirm that the graphics hardware is at fault.

Full report here:

Code:

Version=1
EventType=LiveKernelEvent
EventTime=131619125481686366
ReportType=4
Consent=1
UploadTime=131619126220534911
ReportStatus=268435456
ReportIdentifier=27c570ce-37c6-4e17-ad54-9b2c01acf7ee
Wow64Host=34404
NsAppName=LiveKernelEvent
AppSessionGuid=00000000-0000-0000-0000-000000000000
BootId=54
Response.BucketId=LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D
Response.type=4
Response.CabId=3cf1b7e0-2a7c-4119-89b3-019f27e4d704
Sig[0].Name=Código
Sig[0].Value=141
Sig[1].Name=Parâmetro 1
Sig[1].Value=ffffe305eae14240
Sig[2].Name=Parâmetro 2
Sig[2].Value=fffff8040b9eb8e4
Sig[3].Name=Parâmetro 3
Sig[3].Value=0
Sig[4].Name=Parâmetro 4
Sig[4].Value=1f38
Sig[5].Name=Versão do SO
Sig[5].Value=10_0_16299
Sig[6].Name=Service pack
Sig[6].Value=0_0
Sig[7].Name=Produto
Sig[7].Value=768_1
DynamicSig[1].Name=Versão do SO
DynamicSig[1].Value=10.0.16299.2.0.0.768.101
DynamicSig[2].Name=ID de Região
DynamicSig[2].Value=2070
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=BLOB
State[1].Value=CHKSUM=512E5D2941A5F04318A4F9CF31801479;BID=OCATAG;ID=3cf1b7e0-2a7c-4119-89b3-019f27e4d704;SUB=1//31//2018 2:50:23 PM;SECDATA=1//31//2018 2:50:35 PM;BUID=LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D;FLHASH=d2c52edf-6456-593f-8a6b-f00801e08331;AutoFLID=d18ed123-0f53-01ab-d93a-30c0f41b1523;DREQBY=AutoKernelModeCollection
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=16299
OsInfo[3].Key=ubr
OsInfo[3].Value=192
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=2070
OsInfo[7].Key=geoid
OsInfo[7].Value=193
OsInfo[8].Key=sku
OsInfo[8].Value=101
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=768
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=20487
OsInfo[15].Key=osinsty
OsInfo[15].Value=1
OsInfo[16].Key=iever
OsInfo[16].Value=11.192.16299.0-11.0.50
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=32720
OsInfo[19].Key=svolsz
OsInfo[19].Value=475
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=170928
OsInfo[22].Key=bldtm
OsInfo[22].Value=1534
OsInfo[23].Key=bldbrch
OsInfo[23].Value=rs3_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.16299.192.amd64fre.rs3_release.170928-1534
OsInfo[30].Key=buildflightid
OsInfo[31].Key=edition
OsInfo[31].Value=Core
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=containerid
OsInfo[34].Key=containertype
OsInfo[35].Key=edu
OsInfo[35].Value=0
File[0].CabName=WATCHDOG-20180124-2154.dmp
File[0].Path=WATCHDOG-20180124-2154.dmp
File[0].Flags=34406402
File[0].Type=2
File[0].Original.Path=\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20180124-2154.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-17921-0.sysdata.xml
File[1].Flags=34406402
File[1].Type=5
File[1].Original.Path=\\?\C:\Windows\TEMP\WER-17921-0.sysdata.xml
File[2].CabName=WERInternalMetadata.xml
File[2].Path=WER5A3A.tmp.WERInternalMetadata.xml
File[2].Flags=34406402
File[2].Type=5
File[2].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A3A.tmp.WERInternalMetadata.xml
File[3].CabName=memory.csv
File[3].Path=WER5A3F.tmp.csv
File[3].Flags=34406402
File[3].Type=5
File[3].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A3F.tmp.csv
File[4].CabName=sysinfo.txt
File[4].Path=WER5A50.tmp.txt
File[4].Flags=34406402
File[4].Type=5
File[4].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A50.tmp.txt
File[5].CabName=WERDataCollectionStatus.txt
File[5].Path=WERB86E.tmp.WERDataCollectionStatus.txt
File[5].Flags=851971
File[5].Type=5
File[5].Original.Path=\\?\C:\Windows\Temp\WERB86E.tmp.WERDataCollectionStatus.txt
File[6].CabName=Report.zip
File[6].Path=Report.zip
File[6].Flags=65536
File[6].Type=11
File[6].Original.Path=\\?\C:\Windows\system32\Report.zip
Ns[0].Name=stopcode
Ns[0].Value=00000141
Ns[1].Name=p1
Ns[1].Value=FFFFE305EAE14240
Ns[2].Name=p2
Ns[2].Value=FFFFF8040B9EB8E4
Ns[3].Name=p3
Ns[3].Value=0000000000000000
Ns[4].Name=p4
Ns[4].Value=0000000000001F38
FriendlyEventName=Erro de Hardware
ConsentKey=LiveKernelEvent
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe
ReportDescription=O problema com o hardware fez com que o Windows deixasse de funcionar corretamente.
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=00000000000000000000000000000000
MetadataHash=-1183751083

Thank you, philc43.

I hope can now get Asus to do something about it, hopefully a refund. I've been a customer for a long time, but my experience with their Customer Service as been driving both me and the retailer I bought the computer from crazy.

Please run this version of the log collector and post a zip into this thread:
log collector v2-beta08.zip

Here you go, zbook. I actually had a new crash yesterday night, with a different game than the one I've been using for the tests. Same behaviour: hard crash with no BSOD, no dumps produced except for the Live Kernel one.

I tried to "push the game hard" to see if it would crash, and it performed great. Then I left it idling while I went to the kitchen, and it crashed.
I noticed that a new Nvidia driver has been released meanwhile, so I'm going to install it just to test it out.

nulmas said:

Thank you, philc43.

I hope can now get Asus to do something about it, hopefully a refund. I've been a customer for a long time, but my experience with their Customer Service as been driving both me and the retailer I bought the computer from crazy.

You are welcome, I can not guarantee that the GPU hardware is faulty but it is an indication. I would try and see if you can get more verification, there are some Graphics memory testing programs which you can find by searching the internet, they may help to determine if it is the graphics card memory that is faulty, in your first post you hinted that this might be the case.

philc43 said:

You are welcome, I can not guarantee that the GPU hardware is faulty but it is an indication. I would try and see if you can get more verification, there are some Graphics memory testing programs which you can find by searching the internet, they may help to determine if it is the graphics card memory that is faulty, in your first post you hinted that this might be the case.

I already managed to find some and ran them, just to be sure.

But the issue I suspect the card has isn't properly due to faulty VRAM in the usual sense. I don't have the know-how to explain the issue properly, but it has something to do with the way it reacts to changes in voltage, and it only happens on GTX 1070s, and only on the ones with Micron memory.

One of the problems with this particular issue is that it's a bit hard to detect and to reproduce: it only seems to show itself during "real use", and even then only at random. At first, I thought it was some bug on a game called Nioh: sometimes I would play for a couple of hours with no issues, others it would crash after a few minutes. Then, when I had some free time, I started playing other games and had the same problem. So I started testing it and realized it happened on most of them.

Then I found out that for some weird reason, WWE2k18 would crash quite more consistently than all the others, so it become my go-to tool to check if the repairs by Asus had been successful or not, using other games afterwards to verify if 2k18 wasn't to blame.

There's quite a large thread on the Asus forums on the issue: G752VS CRASHING ISSUES (SHUTS OFF AND RESTARTS AUTOMATICALLY)

The latest BSOD mini dump file debugging displayed a recurrent Nvidia GPU driver:
nvlddmkm.sys Wed Jan 03 17:40:06 2018 (5A4D69D6)
23.21.13.9065


The VIDEO_ENGINE_TIMEOUT_DETECTED bug check has a value of 0x00000141. This indicates that one of the display engines failed to respond in timely fashion.

Code:

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: ffffbc80b3a6d4a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).Arg2: fffff80aff7ab8e4, The pointer into responsible device driver module (e.g owner tag).Arg3: 0000000000000000, The secondary driver specific bucketing key.Arg4: 0000000000000204, Optional internal context dependent data.

These are some troubleshooting steps:

1) Try later and/or earlier drivers
2) Measure the GPU's temperatures at idle and under load
3) Ensure the GPU is free from dust build up and that the fan is working correctly
4) Reseat the GPU and check all connections are securely made
5) Check PSU voltages in BIOS
6) Try a different card in the system


7) What are the BIOS 3.3, 5 and 12 voltage values?
8) What are the CPU voltage and frequency?

9) In the left lower corner type: system > open system control panel > on the left pane click advanced system settings >
a) under performance click settings > on performance options click the advanced tab > under virtual memory click change > post an image of the virtual memory windows into the thread
b) under startup and recovery click settings > post an image of the startup and recovery settings into the thread.

Re-modification of the dump settings may prevent the formation of mini and memory dump files with the event viewer displaying:
Dump file creation failed due to error during dump creation.

The mini dump file displayed: C:\Windows\Minidump does not exist.
The memory dump file displayed: C:\Windows\MEMORY.DMP was not found

Code:

Name    NVIDIA GeForce GTX 1070PNP Device ID    PCI\VEN_10DE&DEV_1BE1&SUBSYS_17D01043&REV_A1\4&337D48F7&0&0008Adapter Type    GeForce GTX 1070, NVIDIA compatibleAdapter Description    NVIDIA GeForce GTX 1070Adapter RAM    (1,048,576) bytesInstalled Drivers    C:\Windows\System32\DriverStore\FileRepository\nvami.inf_amd64_0aea393ee4d64d3d\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvami.inf_amd64_0aea393ee4d64d3d\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvami.inf_amd64_0aea393ee4d64d3d\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvami.inf_amd64_0aea393ee4d64d3d\nvldumdx.dllDriver Version    23.21.13.9065INF File    oem10.inf (Section248 section)Color Planes    Not AvailableColor Table Entries    4294967296Resolution    1920 x 1080 x 120 hertzBits/Pixel    32Memory Address    0xEB000000-0xEBFFFFFFMemory Address    0xC0000000-0xCFFFFFFFMemory Address    0xD0000000-0xD1FFFFFFI/O Port    0x0000E000-0x0000E07FIRQ Channel    IRQ 4294967284Driver    c:\windows\system32\driverstore\filerepository\nvami.inf_amd64_0aea393ee4d64d3d\nvlddmkm.sys (23.21.13.9065, 16.68 MB (17,486,096 bytes), 1/25/2018 04:49 PM)

Code:

1/31/2018 10:50 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, type 0
Event Name: LiveKernelEvent
Response: Não disponível
Cab Id: 1f6b4762-436c-4c8e-8e09-a7bd65bd5591

Problem signature:
P1: 141
P2: ffff978b663b6010
P3: fffff809644fb8e4
P4: 0
P5: 25c0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20180125-0435.dmp
\\?\C:\Windows\TEMP\WER-17921-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A0A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A1E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A2F.tmp.txt
\\?\C:\Windows\Temp\WER76DE.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_ca3f2be7fd9cf9a62112feca6d1424b5cf3924f_00000000_cab_26bd7ab9

Analysis symbol: 
Rechecking for solution: 0
Report Id: 11a77a73-1d4a-474a-a871-b2ee74e345af
Report Status: 268435456
Hashed bucket:1/31/2018 10:50 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, type 0
Event Name: LiveKernelEvent
Response: Não disponível
Cab Id: 3cf1b7e0-2a7c-4119-89b3-019f27e4d704

Problem signature:
P1: 141
P2: ffffe305eae14240
P3: fffff8040b9eb8e4
P4: 0
P5: 1f38
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20180124-2154.dmp
\\?\C:\Windows\TEMP\WER-17921-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A3A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A3F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A50.tmp.txt
\\?\C:\Windows\Temp\WERB86E.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_2b96667a54f943a62640326283d6ced43df5_00000000_cab_26bdbc65

Analysis symbol: 
Rechecking for solution: 0
Report Id: 27c570ce-37c6-4e17-ad54-9b2c01acf7ee
Report Status: 268435456
Hashed bucket:1/31/2018 10:50 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, type 0
Event Name: LiveKernelEvent
Response: Não disponível
Cab Id: 4f21d850-def0-4708-9d0d-ccae9e5f05f2

Problem signature:
P1: 141
P2: ffffdb87f6d494a0
P3: fffff808586bb8e4
P4: 0
P5: 3164
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20180125-0445.dmp
\\?\C:\Windows\TEMP\WER-17921-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59EA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59ED.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59FE.tmp.txt
\\?\C:\Windows\Temp\WER29E4.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_bb4bece76ee45bbec2e47142291c3636d9d1a62d_00000000_cab_26bd2dc2

Analysis symbol: 
Rechecking for solution: 0
Report Id: b0d74a62-1e86-48d7-a1ae-56473411132f
Report Status: 268435456
Hashed bucket:1/31/2018 10:49 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, type 0
Event Name: LiveKernelEvent
Response: Não disponível
Cab Id: 4f8a8326-8271-4659-a5b7-607a3d1acc84

Problem signature:
P1: 141
P2: ffffaa0bcd3c74a0
P3: fffff80257bfb8e4
P4: 0
P5: 2058
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20180125-1736.dmp
\\?\C:\Windows\TEMP\WER-17921-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER598A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER599B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59AC.tmp.txt
\\?\C:\Windows\Temp\WERCA87.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_92787671a9cde691b3eab2661b9882df59db3d5_00000000_cab_26bcce6b

Analysis symbol: 
Rechecking for solution: 0
Report Id: dadadf9e-df3a-4009-b84f-2315a6d65206
Report Status: 268435456
Hashed bucket:1/31/2018 10:49 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, type 0
Event Name: LiveKernelEvent
Response: Não disponível
Cab Id: c87e82fd-3a14-4a44-b5f4-429ceeada613

Problem signature:
P1: 141
P2: ffffb3001a25a4a0
P3: fffff8079674b8e4
P4: 0
P5: 1504
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20180130-1638.dmp
\\?\C:\Windows\TEMP\WER-17921-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER595B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER596A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER597B.tmp.txt
\\?\C:\Windows\Temp\WER9338.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_77f2b32e281fabd4b1a99858f996f7ea432b2a0_00000000_cab_26bc98b5

Analysis symbol: 
Rechecking for solution: 0
Report Id: 91185f21-f098-4f23-b82f-27eb3200b168
Report Status: 268435456
Hashed bucket:1/31/2018 10:49 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, type 0
Event Name: LiveKernelEvent
Response: Não disponível
Cab Id: d7455f54-4b3a-446f-9060-1e10e8f42be5

Problem signature:
P1: 141
P2: ffffb6859a7434a0
P3: fffff8062bccb8e4
P4: 0
P5: 2f78
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20180125-0512.dmp
\\?\C:\Windows\TEMP\WER-17921-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59BA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59BC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59CD.tmp.txt
\\?\C:\Windows\Temp\WER2.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_5719f23b36d8da7442e96337a49601fb899a76_00000000_cab_26bd0412

Analysis symbol: 
Rechecking for solution: 0
Report Id: ce850896-e8cc-4cd5-ae64-9121742304c3
Report Status: 268435456
Hashed bucket:

Code:

Event[9379]:  Log Name: System
  Source: volmgr
  Date: 2018-02-05T00:23:19.578
  Event ID: 161
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JSFDMC95
  Description: 
Dump file creation failed due to error during dump creation.