Laptop - Predator Helios Neo 16 (2023)
so currently my laptop is plagued with nvlddmkm errors for my 4060 laptop gpu with event ids 14, 153 and 0. with most of the time nvlddmkm 14 being at the forefront of the error with this description.
These happens on both idle or under load which eventually causes the system to intermittently freeze, cause bsod with TDR failure, require a hard restart, or sometimes a System_thread_exception BSOD.
I have done just about everything to get this fixed such as running a DDU to reinstall to latest drivers, underclocking the Discrete GPU, resetting pc back to factory, giving full control to nvlddmkm.sys, turning off hardware acceleration, turning off fast startup, creating a TDRdelay, running windows memory diagnostic test. but none of these seems to have worked out
The only thing that ended up working for a bit was boost locking my Discrete GPU using EVGA precision X1 which basically puts my GPU in a constant state of 2500mhz core and 8000 memory clock, this allows my system to stay alive even if my Discrete GPU is active at idle but the driver would either crash to desktop or create a TDR bsod within a few minutes to hours of the Discrete GPU going underload such as playing games or going through a benchmark. The system runs perfectly fine if the Discrete GPU is disabled from ever running.
Currently, I am going through my event viewer and have noticed a specific windows event listed in the WerKernel that happens usually around the time or on the nose of an nvlddmkm crash and the description reads
Windows error reporting Kernel Driver Event ID 1001
If anyone can help me analyze this situation it would be greatly appreciated
so currently my laptop is plagued with nvlddmkm errors for my 4060 laptop gpu with event ids 14, 153 and 0. with most of the time nvlddmkm 14 being at the forefront of the error with this description.
The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Video8
321c68f0 000142b0 00000000 202b2456 202b2338 202b1924 202cc36a 202b4838
These happens on both idle or under load which eventually causes the system to intermittently freeze, cause bsod with TDR failure, require a hard restart, or sometimes a System_thread_exception BSOD.
I have done just about everything to get this fixed such as running a DDU to reinstall to latest drivers, underclocking the Discrete GPU, resetting pc back to factory, giving full control to nvlddmkm.sys, turning off hardware acceleration, turning off fast startup, creating a TDRdelay, running windows memory diagnostic test. but none of these seems to have worked out
The only thing that ended up working for a bit was boost locking my Discrete GPU using EVGA precision X1 which basically puts my GPU in a constant state of 2500mhz core and 8000 memory clock, this allows my system to stay alive even if my Discrete GPU is active at idle but the driver would either crash to desktop or create a TDR bsod within a few minutes to hours of the Discrete GPU going underload such as playing games or going through a benchmark. The system runs perfectly fine if the Discrete GPU is disabled from ever running.
Currently, I am going through my event viewer and have noticed a specific windows event listed in the WerKernel that happens usually around the time or on the nose of an nvlddmkm crash and the description reads
Windows error reporting Kernel Driver Event ID 1001
Component WATCHDOG has requested to create a Live Kernel Dump and the request has been completed. RequestedType Kernel Dump, GrantedType Kernel Dump, Status When a block of memory is allotted for future updates, such as the memory allocated to hold discretionary access control and primary group information, successive updates may exceed the amount of memory originally allotted.
Since quota may already have been charged to several processes which have handles to the object, it is not reasonable to alter the size of the allocated memory.
Instead, a request that requires more memory than has been allotted must fail and the STATUS_ALLOTED_SPACE_EXCEEDED error returned., ThrottleCheckResult 0x21.
If anyone can help me analyze this situation it would be greatly appreciated