cancel
Showing results for 
Search instead for 
Did you mean: 

GL502VM Crash all night ...

lachemou
Level 7
All is in title !
I have an Asus GL502VML, i have a fresh install of windows 10 (Re install last week) and full update V1809 17763.316.
My config is : Intel i7 6700HQ , GTX1060, 16Go , BIOS 301
I'm using the original Windows driver expect for ACPI (Asus official V1.0.0050 ) and nvidia official 419.17 notebook.
i have desactivated extended standby.
All the night my Asus crash and shutdown :mad: .. and minidump are created, here my last crashdump :


Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\030119-7343-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff807`43a12000 PsLoadedModuleList = 0xfffff807`43e2dad0
Debug session time: Fri Mar 1 19:17:25.821 2019 (UTC + 1:00)
System Uptime: 0 days 17:01:49.328
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {1, 1e00, fffff80743f54380, 0}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+1fa44d )

Followup: MachineOwner
---------


Can you help me to solve it ?
Thanks a lot for your help
729 Views
1 REPLY 1

lachemou
Level 7
nobody to help me ? today morning new BSOD and same minidump log ...