#NVLDDMKM Error 153

1 messages · Page 1 of 1 (latest)

fleet snow
#

Has anyone found a fix for this issue st all? I have literally tried everything I can imagine but no fix yet. I refuse to believe its a hardware issue otherwise not this many ppl would be experiencing it.

lapis sorrel
fleet snow
lapis sorrel
#

Versions of driver ?

fleet snow
#

Crashes started happening slowly on febuary 6 and are whenever i launch the game now

#

Reverting back go 536,66 didnt fix it

#

To*

lapis sorrel
#

I had the similar problem that caused my entire PC to crash at the launch of a game, the problem was the driver. Did you use DDU?

#

As for the version I'm going from 572.xx to 566.xx and it seems to have fixed the problem so try version 566.xx without forgetting to use DDU correctly before installing the 566.xx

spare foxBOT
#

If you encounter Code 14 or Code 153 within the Device Status of your GPU in your Device Manager or if you are having crashes when your PC is on idle or on heavy load, it means that your GPU is having issues with power management especially from PCIe connections. Please try the following remedial methods:

  • Removing existing Nvidia drivers with DDU and reinstalling Nvidia drivers manually.
  • Ensure all other drivers such as Chipset/IO/ME drivers are installed through the manufacturer’s website.
  • Disabling Active-state power management (ASPM) through the BIOS. Please consult the motherboard manual for details.
  • Disabling Fast Startup. You can disable Fast Startup by going to Control Panel > Power Options (Make sure View By is set to Small Icons) > Choose what closing the lid does > Change settings that are currently not available, and untick Turn On Fast Startup. Please restart your computer after that.
  • Disabling Link State Power Management. You can disable Link State Power Management by going to going to Control Panel > Power Options (Make sure View By is set to Small Icons) > Select Change Plan Setting (The selected power plan) > Change advanced power settings > PCI Express > Link State Power Management > Set both to Off.
  • Disable Nvidia Power Management. You can go to the Nvidia Control Panel > Manage 3D settings > Power Management Mode is set to “Prefer Maximum Performance”. Please note that your GPU will use more power and your clock speeds will remain high even on idle.
  • Rollback the driver to the previous version.

If all these methods still fail to fix your GPU, you may require to RMA your GPU for a replacement.

fleet snow
#

@final escarp already did all those steps

lapis sorrel
#

Make userdiag normal mode and occt gpu test and see if your computer crash of freeze

hollow nebula
#

566.36 works for my Laptop 4070 Super

#

its currently the only one that works for mine

civic kelp
#

can u try to ddu again and install manual (uncheck physx and check clean install)

hollow nebula
#

So new info I found under application logs for event viewer every 153 crash i have has this driver also fail under application:

Faulting module name: nvoglv64.dll, version: 32.0.15.6636

Faulting application name: rs2client.exe, version: 941.2.0.0, time stamp: 0x67ebcee9
Faulting module name: nvoglv64.dll, version: 32.0.15.6636, time stamp: 0x674f5e6b
Exception code: 0xc0000409
Fault offset: 0x0000000000fdc525
Faulting process id: 0x6BA8
Faulting application start time: 0x1DBA62CB1840222
Faulting application path: C:\ProgramData\Jagex\launcher\rs2client.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_085de2d4b49d7707\nvoglv64.dll
Report Id: c1f89c74-8524-4690-a7f2-9b7026ccb5f9
Faulting package full name:
Faulting package-relative application ID:

#

just preformed a DDU and gave User Full control over the 64 and 32 bit drivers for nvoglv64

#

running 566.36

final escarp
#

your GPU is Broken

#

send it for RMA/replacement warranty

hollow nebula
#

I have a laptop GPU, the GPU is fine as it only crashes randomly in games from a Driver issue, not the GPU itself i can leave heaven benchmark on for hours no issues.

#

after DDU and reinstall of 566.36 and giving user permissions i havent crashed in 2 hours