“NVLDDMKM” is a driver component that enables your computer’s operating system to communicate effectively with the NVIDIA graphics card. Think of it as a translator that allows your computer and the graphics card to understand each other.
This software is stored in a special part of your computer’s storage called the “System32 folder.” Its function is to manage important tasks such as ensuring that images and videos look great on your screen and performing complex calculations using the graphics card.
When you’re playing a game, it might suddenly crash or even cause your computer to freeze. A common reason for this is an issue with something called “NVLDDMKM,” which is a part of the software that ensures your computer’s graphics card functions properly.
Here’s why this might happen:
- Graphics Driver Problem: The software (driver) that helps your graphics card communicate with the rest of your computer might be outdated, incomplete, or have corrupted files. This is often the primary cause of the error.
- Permission Issues: Occasionally, your computer might prevent the graphics card from performing certain operations due to existing restrictions, causing problems.
- Overclocking: If you’re pushing your graphics card to run faster than its original design intended (commonly known as “overclocking”), it might lead to instability and errors.
- Hardware Problems: Sometimes, physical issues with the graphics card or other computer components can cause these errors.
To address these problems, there are some commonly suggested solutions from people who’ve faced similar issues.
1. Take Full Ownership of the Nvlddmkm File
Before resolving the GPU driver issue, it’s recommended to ensure you don’t have any permission issues blocking the system from accessing the file properly. By taking full ownership of the Nvlddmkm file, you can reduce the likelihood of encountering the Event ID 153 error, allowing the Nvidia driver and the system to interact with nvlddmkm.sys without restrictions.
- Open Windows Explorer by pressing the Win + E keys simultaneously.
- Navigate to C:\Windows\System32.
- Locate the Nvlddmkm file, right-click on it, and select Properties.
- Follow these steps to take full control of the Nvlddmkm file.
- Note that if this does not work, do not skip the following methods. This will confirm whether or not you have any permission issues with the nvlddmkm.
2. Disable Overclocking
Overclocking accelerates the hardware component beyond its limits, which can lead to crashes and system instability, especially in highly demanding games. Resetting the overclock can stabilize the system and resolve errors by returning the hardware component to its default speed and voltage settings.
So if you have overclocked any hardware components like the GPU and RAM, it’s worth trying to reset them to determine if this is the cause of the issue.
- If you have overclocked your GPU, open MSI Afterburner and simply reset the settings to default.
- If you are using XMP to overclock your RAM, access your motherboard BIOS settings, navigate to ‘Overclock’ or ‘Advanced Settings,’ and disable the XMP profile.
- Once completed, restart your computer and verify if the “The description for Event ID 153 from source nvlddmkm cannot be found” problem persists.
3. Reinstall the GPU Driver or Roll Back to a Previous Version
Since nvlddmkm is part of the Nvidia GPU driver files, a common fix involves reinstalling the GPU driver or reverting to an older version to restore the nvlddmkm file. Newer drivers can sometimes introduce issues with certain GPUs or applications, while older drivers might be more stable.
First, we recommend a clean reinstallation of the GPU driver. If the problem persists, trying older drivers can be a beneficial step. Many users have found success with this approach, so it might be worth it for you.
- Press the Win key and type Device Manager.
- Open Device Manager, expand Display Adapters, right-click the GPU driver, and select Uninstall device.
- Click Uninstall again.
- Next, visit the Nvidia official website to install the GPU driver or use the Geforce Experience to download and install the driver.
- Make sure to check the box Perform Clean Install when installing the driver.
- Once done, restart your computer. If the issue persists, try downloading and installing an older driver version than the latest one you’ve installed on your system.
4. Check for Hardware Issues
Several user reports suggest that this issue might be due to underlying hardware problems, such as issues with the GPU. However, before arriving at any conclusions, thoroughly troubleshoot the problem by reinstalling the GPU driver or rolling back the driver. You may also reset the PC to rule out any software-related issues.
If you are sure that the issue is hardware-related, it’s advisable to take your system to a repair shop to verify if there is a hardware issue with your graphics card.
Hamza Mohammad Anwar
Hamza Mohammad Anwar is an intermediate JavaScript web developer with a focus on developing high-performance applications using MERN technologies. His skill set includes expertise in ReactJS, MongoDB, Express NodeJS, and other related technologies. Hamza is also a Google IT Certified professional, which highlights his competence in IT support. As an avid problem-solver, he recreates errors on his computer to troubleshoot and find solutions to various technical issues.
-
Home
-
News
- The Description for Event ID 153 from Source Nvlddmkm Cannot Be Found
The Description for Event ID 153 from Source Nvlddmkm Cannot Be Found
By Daisy | Follow |
Last Updated
Many users report who use Windows devices with NVIDIA GPU cards recive the description for Event ID 153 from source nvlddmkm cannot be found meesage and their games crash. This post from MiniTool introduces how to fix it.
You may see “the description for Event ID 153 from source nvlddmkm cannot be found” error message. This error is usually found in system logs after experiencing issues such as crashes, unexpected restarts, or temporary black screens.
This issue is especially common among gamers as it often causes games or other demanding applications to crash. It indicates that there is an issue related to this driver, which could be due to a variety of factors such as driver corruption, compatibility issues, or even hardware failure.
I have been plagued by countless annoying random game crashes the past months with my pc with all pointing out to this error (from event viewer) when they occur: «The description for Event ID 153 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.
…Microsoft
Related post: How to Fix NVLDDMKM Event ID 14? Here Are 12 Solutions!
Method 1: Give the Full Control Permission to the File
First, you can try an unconventional fix that seems to be working for some Windows users. Here is how to do that:
1. Find nvlddmkm.sys in C:\Windows\System32.
2. Right click it and select Properties. Then, go to Security and click Edit….
3. Enable user permissions to full control. Make sure the checkboxes in the Allow column are all checked.
Method 2: Update Nvidia Drivers
You can also try to update Nvidia drivers to fix the description for Event ID 153 from source nvlddmkm cannot be found on Windows 11.
1. Press the Windows + R keys to open the Run dialog. Then, type devmgmt.msc.
2. Expand Display adapters, right-click your GPU card, and then choose Update driver.
3. Click Search automatically for drivers.
Method 3: Roll Back Nvidia Drivers
1. Press the Windows + R keys to open the Run dialog. Then, type devmgmt.msc.
2. Next, you can expand the Display adapters category, and right-click the target Nvidia graphics card device to select Properties.
3. Then you can click the Driver tab, and click the Roll Back Driver button.
Method 4: Stop Overclocking
While you can overclock your hardware for better graphics and better gaming performance, doing so can make the description for Event ID 153 from source nvlddmkm cannot be found on Windows 11. To fix it, you can close overclocking utilities like MSI Afterburner and set the clock speed back to default.
Method 5: Update BIOS
If the above solutions are not working for the description for Event ID 153 from source nvlddmkm cannot be found issue, you can try to update BIOS.
However, updating BIOS has a risk since system crashes may happen. Thus, you had better create a system backup or back up your crucial files before starting the update. If your PC can’t boot after updating BIOS, you can restore the PC to a normal state with the backup. To do that, you can try the Windows backup software – MiniTool ShadowMaker, it can be used to create a backup for Windows operating systems, files, folders, disks, or partitions.
To update BIOS, you can refer to this post – How to Update BIOS Windows 10 | How to Check BIOS Version.
Final Words
To sum up, this post has introduced how to fix “the description for Event ID 153 from source nvlddmkm cannot be found” issue. If you come across the same issue, try these solutions.
About The Author
Position: Columnist
Having been an editor at MiniTool since graduating college as an English major, Daisy specializes in writing about data backups, disk cloning, and file syncing as well as general computer knowledge and issues. In her free time, Daisy enjoys running and going with friends to the amusement park.
Sometimes servers can display cryptic error messages that leave admins worried about hardware health and overall stability. This article addresses one such scenario and offers practical steps to diagnose and fix the problem.
TOC
Understanding Event ID 153 in Windows Server
Event ID 153 often reads: “The IO operation at logical block address [LBA] for Disk [Number] was retried.” This typically points to storage-related issues within Windows Server environments. Users may encounter noticeable performance slowdowns, intermittent freezing, or even abrupt restarts and system instability. These symptoms raise serious concerns about data integrity, hardware reliability, and the need for potential component replacements.
When Windows Server experiences a disk-related delay or a controller issue, it will attempt to reissue the IO request. If this problem persists, the repeated retries can degrade performance and eventually lead to severe disruptions. Although the message might not outright state “hardware failure,” it is a strong indicator that something is amiss in the storage subsystem, be it disk hardware, cables, drivers, or the controller interface.
Event ID 153: Common Causes
- Disk Degradation or Imminent Failure: Mechanical hard drives (HDDs) nearing end-of-life or solid-state drives (SSDs) with worn flash cells can trigger repeated IO retries.
- Faulty Storage Controller or Drivers: If the RAID controller or disk driver is outdated or malfunctions, Windows Server may struggle to process disk requests properly.
- Cabling and Connection Issues: Damaged or poorly seated cables connecting the disk to the mainboard or RAID controller can cause intermittent IO errors.
- Firmware Compatibility: Outdated disk firmware can lead to unexpected IO problems, especially in newer OS environments like Windows Server 2022.
- Resource Bottlenecks: High IO loads, insufficient memory, or resource contention can amplify disk request delays, contributing to repeated IO retries.
How Windows Server Responds to Disk Errors
When Windows encounters a potential disk-related glitch, the kernel will generally attempt to recover. It might log Event ID 153 to indicate a retry. If the underlying cause remains unresolved, this can escalate into file system corruption warnings, more frequent system hangs, or even system reboots designed to protect data integrity.
Key Indicators That Point to a Hardware Concern
When Event ID 153 appears, it’s tempting to blame software or drivers. However, there are several telltale signs that your hardware may need further attention or replacement:
Physical Indicators
- Strange Noises: In the case of HDDs, any grinding or clicking sounds usually signal mechanical issues.
- Drive Overheating: Excessive temperatures can damage internal components, leading to frequent read/write errors.
- Slow Spin-Up Times: HDDs that take longer than usual to spin up on boot can be on the verge of failure.
System Behavior
- Unresponsive OS: Sudden freezes or input lags can occur if the disk controller struggles to retrieve or write data.
- Automatic Restart or BSOD: Windows may forcibly restart the server if it detects critical disk failures to prevent further corruption.
Log File Evidence
- Frequent Event ID 153 Entries: Seeing multiple occurrences over a short period indicates consistent IO issues that aren’t transient.
- Accompanying Disk Errors (e.g., Event ID 51, 55, 57): These errors typically relate to the file system or the volume manager, suggesting deeper disk-level problems.
Diagnostic Tools and Their Significance
To distinguish between a temporary glitch and true hardware failure, reliable diagnostic methods are crucial:
| Tool Name | Purpose | Typical Outcome |
|---|---|---|
| chkdsk | Scans and repairs file system errors | Identifies and corrects logical issues; provides insight into disk health |
| Manufacturer Diagnostics (e.g., Dell, HP) | Hardware-level tests specifically designed for the manufacturer’s hardware | Confirms if disk hardware is failing |
| Smart Monitoring Tools | Reads S.M.A.R.T. attributes to gauge drive reliability | Predictive alerts of disk degradation or failure risks |
| Performance Monitor | Tracks disk performance metrics over time | Pinpoints abnormal spikes in latency or IO errors |
Detailed Step-by-Step Troubleshooting Guide
Below is a comprehensive framework to troubleshoot and resolve Event ID 153 errors.
Step 1: Review Windows Event Logs Thoroughly
Begin by examining both the System and Application logs:
- System Log: Look for consecutive errors or warnings around the same timeframe as Event ID 153. This could highlight driver, controller, or power-related issues.
- Application Log: Check for software-level conflicts, such as backup applications or security software that might overload disk operations.
How to Filter Logs for Disk-Specific Errors
- Open Event Viewer from the Start menu or via
eventvwr.msc. - Expand Windows Logs and select System.
- In the right pane, click Filter Current Log and select the “Event sources” relevant to storage (e.g., “Disk,” “Ntfs,” “Storport,” “iScsi,” or “VDS Basic Provider”).
- Compare timestamps for any correlation among the errors.
Step 2: Update Firmware, Drivers, and Windows Patches
Even if the disk isn’t failing, outdated firmware and drivers can introduce IO retry errors.
- Disk Firmware: Check the manufacturer’s site for any new firmware versions. Apply carefully, as firmware updates are critical-level operations.
- Storage Controller Drivers: If using a RAID or specialized controller, ensure you have the latest stable version. A mismatch between driver and firmware can generate repeated disk errors.
- Windows Updates: Install recommended and optional updates, especially those marked for hardware or system stability improvements.
Step 3: Assess Disk Health and Performance
Use built-in and third-party diagnostic tools to gauge if the disk is physically deteriorating:
- chkdsk /r: This parameter checks for bad sectors and attempts data recovery. Monitor the final report for any “unreadable” or “reallocated” sector counts.
- S.M.A.R.T. Analysis: Tools like smartctl or specialized vendor applications can read S.M.A.R.T. data fields (e.g., Reallocated Sector Count, Pending Sector Count).
- I/O Benchmarking: Running a read/write benchmark can expose performance anomalies that might tie back to repeated IO retries.
Diagnosing Disk Issues in Virtualized Environments
If you’re running Windows Server 2022 as a virtual machine:
- Check Hypervisor Settings: Ensure that virtual disks are allocated with sufficient performance overhead. Over-committing storage can lead to IO bottlenecks.
- Verify Hypervisor Logs: Inspect logs from VMware ESXi, Hyper-V, or other platforms for potential host-level or SAN-level storage disruptions.
Step 4: Evaluate Any Potential Hardware Replacements
If diagnostics reveal recurring problems, it’s time to consider hardware upgrades or replacements:
- Replace the Disk if Failing: Persistent bad sectors or failing S.M.A.R.T. metrics strongly indicate a drive nearing end-of-life.
- Check the Storage Controller: Controllers can fail or degrade over time, especially under heavy loads. Swapping the controller can rule out an aging or damaged board.
- Analyze Cables and Connectors: Even a minor cable fault can cause significant IO disruptions, so don’t overlook this simpler fix before more drastic replacements.
Testing Stability After Replacements
After swapping hardware, run:
- Burn-In Tests: Tools like IOmeter or manufacturer-specific burn-in utilities ensure the new component can handle sustained load.
- Stress Tests: If your environment allows it, subject the disk or array to the typical daily load plus overhead. Confirm that no new Event ID 153 or related disk errors surface.
Long-Term Strategies to Prevent Recurrence
Once Event ID 153 is under control, adopt proactive measures to keep your Windows Server running smoothly.
Regular System and Disk Audits
Establish a routine to examine hardware status:
- Monthly/Quarterly Health Checks: Use vendor tools for quick scans and a deeper “extended” test for thorough verification.
- Scheduled S.M.A.R.T. Monitoring: Automated scripts can parse S.M.A.R.T. data and alert you to signs of impending failure.
Optimize Storage Configuration
- RAID Levels and Redundancy: Implement RAID levels that offer fault tolerance, such as RAID 5 or RAID 10, particularly for critical workloads.
- Load Balancing: If the server runs I/O-intensive applications, distributing loads across multiple arrays or disks can reduce stress on a single disk.
Handling Virtualized Storage
In virtualized setups, ensure the host environment’s storage is robust. This includes redundant SANs, properly configured multipathing, and up-to-date hypervisor patching. Overcommitting virtual storage resources is a common pitfall that leads to unexpected slowdowns and can eventually trigger disk retries within guest OS logs.
Implement Real-Time Monitoring and Alerts
A robust monitoring system is key to early detection:
- Event Viewer Subscriptions: Automate forwarding of critical disk-related errors to a centralized log server.
- SNMP or Syslog Monitoring: If you have a network management platform, ensure it’s configured to receive and flag repeated disk errors.
- Automatic Email or SMS Alerts: Many hardware monitoring suites can notify administrators the moment a S.M.A.R.T. parameter crosses a threshold.
Addressing Server-Wide Performance Issues
Event ID 153 might be one symptom of a broader performance or resource problem in the server. Often, a deeper system-level approach can yield significant improvements and reduce the likelihood of IO-related issues.
Memory and CPU Considerations
- Check for Overutilization: In Resource Monitor or Performance Monitor, evaluate if the CPU or RAM usage is consistently maxed out. A saturated system may struggle to handle normal disk requests, leading to retries.
- Memory Leaks in Applications: If a service consistently consumes more memory over time without releasing it, the disk could be overworked with paging operations.
Optimizing for Virtual Memory
Sometimes, disk IO is hampered by heavy paging file usage:
- Set Proper Page File Sizes: A best practice is letting Windows manage this automatically, unless specific constraints require a fixed size.
- Separate Paging Volumes: In high-load environments, isolate the paging file to a dedicated disk or high-speed SSD to reduce interference with general storage IO.
Storage Spaces and ReFS Considerations
Windows Server 2022 supports advanced features like Storage Spaces and the Resilient File System (ReFS). While these offer benefits, misconfigurations can trigger repeated IO errors:
- Storage Spaces Resiliency: Make sure pools have enough capacity and healthy drives to maintain redundancy.
- ReFS Integration: Verify that ReFS is updated, and performance hotfixes are applied. ReFS might log events similar to ID 153 if the underlying hardware experiences latency.
When to Consider a Complete Server Replacement
In extreme cases, you may wonder if the entire server is compromised. While this step is rarely the first solution, it’s sometimes justified:
- Repeated Disk Failures: If multiple drives in the same chassis fail in short succession, the enclosure or power supply might be at fault.
- End-of-Life Hardware: If the server has reached its manufacturer-endorsed lifecycle, performance or reliability limitations might outweigh repair costs.
- Chronic Instability: Persistent system issues—memory faults, CPU errors, power anomalies—can combine with disk errors, making a new server more cost-effective than continuing patchwork fixes.
Before opting for a full replacement, conduct a thorough cost-benefit analysis. Sometimes, upgrading critical components (e.g., new disks, fresh motherboard or RAID controllers) yields a stable environment without fully decommissioning the existing server.
Maintaining Server Reliability Over Time
Once you’ve resolved Event ID 153, consider the following best practices to ensure long-term server reliability:
Frequent Data Backups and Recovery Testing
An up-to-date backup strategy is the linchpin of any robust IT infrastructure:
- Regular Schedule: Perform daily or weekly incremental backups, plus monthly full backups, depending on data criticality.
- Off-Site Storage: Protect backups from local disasters by storing them at a different location or in the cloud.
- Recovery Drills: Periodically test restoring data from backups. This ensures you can recover quickly if hardware fails.
Documentation of Hardware and Software Changes
A well-documented environment helps you react quickly if disk errors reappear. Track:
- Firmware Upgrades: Log the date, time, and version applied.
- Driver Updates: Maintain a version history for your storage controller drivers and OS patches.
- Hardware Replacements: List replaced disks, controllers, and cables, along with any relevant model or serial numbers.
Implementing Redundancy at Multiple Layers
- Power Redundancy: Use dual power supplies or UPS solutions to avoid sudden server shutdowns that can corrupt disks.
- Network Redundancy: If iSCSI or network-attached storage is involved, ensure multiple NICs and switches to reduce a single point of failure.
Conclusion
Event ID 153 in Windows Server generally signals that your system is encountering disk IO retries, likely due to hardware glitches, driver incompatibilities, or connection faults. While not every instance of Event ID 153 guarantees an impending disk catastrophe, it’s a sign that you should thoroughly investigate storage components, controller drivers, and system configurations.
By systematically checking logs, updating drivers, performing disk diagnostics, and preparing for potential hardware replacements, you can either isolate and fix the offending component or confirm that the disk subsystem is in good shape. Proactive monitoring and consistent maintenance minimize the chances of unplanned downtime and data loss, ensuring that your Windows Server environment remains reliable and efficient for the long haul.
I got a lot of Disk Errors Event ID 153 every day when using Windows Backup. Every day at the same time more or less.
Analysis :
First we need to find out which one is Disk 4 ?
Open the registry and go to : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\disk\Enum
You will see that I had 4 Disk, of which the number 4 is a USB Memory card storage…
It will match up with the Server Manager Disks
Next start the Command Line using Admin Privileges
And run this command
set DEVMGR_SHOW_NONPRESENT_DEVICES=1 devmgmt.msc
Go to Portable Devices and see check the Drive letters
In my case it is G: drive ?
On the GENERAL tab you can read that the device is NOT ENABLED
Using WMIC to get more info on the Event ID PDO name Device\00000xxx ID
Use this command to get all drivers detailed information :
wmic /output:c:\temp\drivers.txt path Win32_PnPSignedDriver
And look for the device number in the column PDO
If you don’t find it, it means it is a STALE device that can be removed.
See here on how to…
Solution :
In our case we had to disable the INTERNAL SD Card Slot using the BIOS.
Use these steps on an HP server :
UEFI System Utilities and Shell Command Mobile Help for HPE ProLiant Gen9 Servers and HPE Synergy
Going to System Utilities – by pressing F9
Enabling or disabling the Internal SD Card Slot
Procedure :
1. From the System Utilities screen, select System Configuration > BIOS/Platform Configuration (RBSU) > System Options > USB Options > Internal SD Card Slot and press Enter.
2. Select a setting and press Enter:
a. Enabled—The server can access the internal SD card slot.
b. Disabled—The server cannot access the internal SD card slot.
3. Press F10.
Enjoy!
This entry was posted on Tuesday, December 18th, 2018 at 10:47 am and is filed under Server, Windows. You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
Windows 10: Random nvlddmkm Event id 153 errors
Discus and support Random nvlddmkm Event id 153 errors in Windows 10 Software and Apps to solve the problem; Hi, I recently built a new PC and I have had all sorts of problems. I will begin from the start and get to where I am now with this new issue I am…
Discussion in ‘Windows 10 Software and Apps’ started by nikola neshev, Jan 14, 2025.
-
Random nvlddmkm Event id 153 errors
Hi, I recently built a new PC and I have had all sorts of problems. I will begin from the start and get to where I am now with this new issue I am having.SPECSMBD: ASRock Z790 Pro RS BIOS ver. 15.01CPU: Intel i5-12600k set to default clocks/speeds, never overclockedGPU: Gigabyte GTX 1080 Xtreme GamingRAM: Kingston Fury Beast 2 x 16GB DDR5 6000MHzPSU: 750w COUGAR GEX 80 Plus Gold1. The first problem I had were random bluescreens, which turned into outright freezes and restarts. The event viewer showed an Event ID 41: «The system has rebooted without cleanly shutting down first». Since my
-
The description for Event ID 153 from source nvlddmkm cannot be found
Hello,
I have been plagued by countless annoying random game crashes the past months with my pc with all pointing out to this error (from event viewer) when they occur: «The description for Event ID 153 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\00000092
Reset TDR occurred on GPUID:100
The message resource is present but the message was not found in the message table»
Have tried numerous possible solutions already from forums, but with no luck.. Fortnite and many other games crash after random intervals. Can anyone suggest a solution for this?
My specs are the following:
Processor Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz
Installed RAM G-SKILL F4 3200-C16 32,0 GB DDR4
GPU EVGA GTX 980 Superclocked ACX 2.0
Drives Patriot M.2 P300 512GB and Seagate Hybrid HDD 4TB
Motherboard GIGABYTE H510M H V2
Microsoft Windows 11 Professional (x64) Build 22631.3593 (23H2)
Have to note that i recently replaced almost all parts from the pc due to a previous motherboard burnout which killed many components, expect the PSU (which was repaired by the technician) and GPU (which the technician said was saved from the burnout) and the Hybrid HDD (have this HDD since 2016). Apart from this, i restored my windows partition through Macrium Reflect image backup (from the Hybrid HHD saved backup).
Thanks in advance for any possible solutions to this, if any!
-
Random freeze at certain interval , Event id 153
Check out the following URL which explains why you don’t see this error in Windows 7. Hopefully it can give you a better idea of the issues you are experiencing.
Interpreting Event 153 Errors — Ntdebugging Blog — Site Home — MSDN Blogs
Random nvlddmkm Event id 153 errors
-
Random nvlddmkm Event id 153 errors — Similar Threads — Random nvlddmkm Event
-
Event 153, nvlddmkm
in Windows 10 Gaming
Event 153, nvlddmkm: I have been going crazy with this error cant find any fix :The description for Event ID 153 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… -
Event 153, nvlddmkm
in Windows 10 Software and Apps
Event 153, nvlddmkm: I have been going crazy with this error cant find any fix :The description for Event ID 153 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… -
Random nvlddmkm Event id 153 errors
in Windows 10 Gaming
Random nvlddmkm Event id 153 errors: Hi, I recently built a new PC and I have had all sorts of problems. I will begin from the start and get to where I am now with this new issue I am having.SPECSMBD: ASRock Z790 Pro RS BIOS ver. 15.01CPU: Intel i5-12600k set to default clocks/speeds, never overclockedGPU:… -
Random nvlddmkm Event id 153 errors
in Windows 10 BSOD Crashes and Debugging
Random nvlddmkm Event id 153 errors: Hi, I recently built a new PC and I have had all sorts of problems. I will begin from the start and get to where I am now with this new issue I am having.SPECSMBD: ASRock Z790 Pro RS BIOS ver. 15.01CPU: Intel i5-12600k set to default clocks/speeds, never overclockedGPU:… -
nvlddmkm event id 153, 13 and a warning
in Windows 10 Gaming
nvlddmkm event id 153, 13 and a warning: So, i’ve been having quite a few issues with my games and pc. I’ve been having this error nonstop and aswell a bsod. I had a faulty_hardware_corrupted_page error due to the reason of ntkrnlmp.exe. After my game crashed i immediately checked the event viewer and saw these… -
nvlddmkm event id 153, 13 and a warning
in Windows 10 Software and Apps
nvlddmkm event id 153, 13 and a warning: So, i’ve been having quite a few issues with my games and pc. I’ve been having this error nonstop and aswell a bsod. I had a faulty_hardware_corrupted_page error due to the reason of ntkrnlmp.exe. After my game crashed i immediately checked the event viewer and saw these… -
nvlddmkm event id 153 windows 10
in Windows 10 Gaming
nvlddmkm event id 153 windows 10: CPU: i9-9900KFGPU: 2080 TiMotherboard: Z390 DesignareRAM: G.SKILL Ripjaws V Series Intel XMP DDR4 RAM 32GB 4x16GB 3200MT/s PSU: Corsair HX Series, HX1200Purchased most of these 4 years ago half the ram and psu more recentlyI was playing CS2 while on discord when my PC froze… -
nvlddmkm event id 153 windows 10
in Windows 10 Software and Apps
nvlddmkm event id 153 windows 10: CPU: i9-9900KFGPU: 2080 TiMotherboard: Z390 DesignareRAM: G.SKILL Ripjaws V Series Intel XMP DDR4 RAM 32GB 4x16GB 3200MT/s PSU: Corsair HX Series, HX1200Purchased most of these 4 years ago half the ram and psu more recentlyI was playing CS2 while on discord when my PC froze… -
nvlddmkm event id 153 windows 10
in Windows 10 BSOD Crashes and Debugging
nvlddmkm event id 153 windows 10: CPU: i9-9900KFGPU: 2080 TiMotherboard: Z390 DesignareRAM: G.SKILL Ripjaws V Series Intel XMP DDR4 RAM 32GB 4x16GB 3200MT/s PSU: Corsair HX Series, HX1200Purchased most of these 4 years ago half the ram and psu more recentlyI was playing CS2 while on discord when my PC froze…