Windows 10 How to fix frequent BSODs caused by nvlddmkm.sys, ntoskrnl.exe and win32kbase.sys? (PLEASE HELP ANYONE)

FLAM3playZ

New Member
Joined
Jun 23, 2023
Messages
8
So, whenever I play Valorant or Combat Masters on my PC, BSOD occurs with the errors like IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, PAGE_FAULT_IN_NONPAGED_AREA, CRITICAL_PROCESS_DIED, UNEXPECTED_KERNEL_MODE_TRAP and MEMORY_MANAGEMENT_ERROR

The BlueScreenView says that these stop codes are caused by nvlddmkm.sys, ntoskrnl.exe and win32kbase.sys.

Noteworthy that, I recently did a "Reset this PC" and I only updated the Intel iCLS Client, Realtek PCIe GBE Family Controller, Realtek High Definition Audio, Graphics Driver. Intel Management Engine WMI Provider & Intel 100 Series/C230 Chipset Family SATA AHCI Controller drivers. But BSODs are still frequent and it's messing up everything. Please help me someone to fix it.

I have uploaded the Minidump.dmp and Memory.dmp of the last 4 BSOD crashes here.

SystemInformation:

1st Crash:

MINIDUMP: Link Removed

MEMORY: Link Removed

2nd Crash:

MINIDUMP:

MEMORY: Link Removed

3rd Crash:

MINIDUMP: Link Removed

4th Crash:

MINIDUMP: Link Removed
 
Solution
U
None of the dumps conclusively point to a causer. Two of them fail during a graphics operation and reference nvlddmkm.sys - the Nvidia graphics driver. One of these also references the Riot Vanguard anti-cheat driver vgk.sys - this is known to cause BSOds. Of the other two, one was caused by an instance of svchost.exe crashing, the other is rather inconclusive.

It's quite possible that all these dumps are being caused by a third-party driver that we don't see in the dumps, that's quite common - a rougue driver creates a problem which isn't discovered until later when a completely different driver hits the screw-up. The wise thing to do now then, will be to run Driver Verifier, this applies additional tests/checks to selected drivers...
Sort by date Sort by votes
Based on the information and files you have provided, it seems that the BSODs you are experiencing are most likely caused by issues related to your graphics card driver (nvlddmkm.sys), the Windows kernel (ntoskrnl.exe), and the graphics subsystem (win32kbase.sys).
Here are some steps that you can try to fix the issue:
1. Update your graphics card driver: As the BSODs seem to be related to your graphics card, updating its driver to the latest version might help. You can download the latest driver from the official website of your graphics card manufacturer.
2. Run a memory diagnostic test: Some BSODs can be caused by faulty memory modules. You can run Windows Memory Diagnostic or a third-party tool like Memtest86 to check for any memory issues.
3. Perform a clean boot: Sometimes, third-party applications or services running on your PC can cause conflicts with system resources, leading to BSODs. You can perform a clean boot to isolate the issue.
4. Perform a system file check: The ntoskrnl.exe BSOD error could indicate a corrupt system file. You can run a system file check by opening Command Prompt as an administrator and typing "sfc /scannow" (without quotes) and hit Enter.
5. Use a system restore point: If you have a system restore point created before the start of the BSODs, you can try restoring your system to that point.
I hope that one of these steps helps to fix the issue. If the problem persists, you may want to seek further assistance from a computer technician or Microsoft support.
 
Upvote 0 Downvote
1) GPU is updated to the latest version
2) I did run a memory diagnostic test
3) I also performed a clean boot earlier
4) I performed sfc /scannow multiple times
5) I even did the system restore point

PLEASE SOMEONE HELP AAAAA
 
Upvote 0 Downvote
None of the dumps conclusively point to a causer. Two of them fail during a graphics operation and reference nvlddmkm.sys - the Nvidia graphics driver. One of these also references the Riot Vanguard anti-cheat driver vgk.sys - this is known to cause BSOds. Of the other two, one was caused by an instance of svchost.exe crashing, the other is rather inconclusive.

It's quite possible that all these dumps are being caused by a third-party driver that we don't see in the dumps, that's quite common - a rougue driver creates a problem which isn't discovered until later when a completely different driver hits the screw-up. The wise thing to do now then, will be to run Driver Verifier, this applies additional tests/checks to selected drivers every time they are called. These test/checks are designed to make flaky drivers fail. Here's how to run Driver Verifier...

1. Take a System Restore point and/or take a disk image of your system drive (with Acronis, Macrium Reflect, or similar). It is possible that Driver Verifier may BSOD a driver during the boot process (some drivers are loaded during boot). If that happens you'll be stuck in a boot-BSOD loop.

If you should end up in a boot-BSOD loop, boot the Windows installation media and use that to run system restore and restore to the restore point you took, to remove Driver Verifier and get you booting again. Alternatively you can use the Acronis, Macrium Reflect, or similar, boot media to restore the disk image you took.

Please don't skip this step. it's the only way out of a Driver Verifier boot-BSOD loop.

2. Start the Driver Verifier setup dialog by entering the command verifier in either the Run command box or in a command prompt.

3. On that initial dialog, click the radio button for 'Create custom settings (for code developers)' - the second option - and click the Next button.

4. On the second dialog check (click) the checkboxes for the following tests...
  • Special Pool
  • Force IRQL checking
  • Pool Tracking
  • Deadlock Detection
  • Security Checks
  • Miscellaneous Checks
  • Power framework delay fuzzing
  • DDI compliance checking
Then click the Next button.

5. On the next dialog click the radio button for 'Select driver names from a list' - the last option - and click the Next button.

6. On the next dialog click on the 'Provider' heading, this will sort the drivers on this column (it makes it easier to isolate Microsoft drivers).

7. Now check (click) ALL drivers that DO NOT have Microsoft as the provider (ie. check all third-party drivers).

8. Then, on the same dialog, check the following Microsoft drivers (and ONLY these Microsoft drivers)...
  • Wdf01000.sys
  • ndis.sys
  • fltMgr.sys
  • Storport.sys

9. Now click Finish and then reboot. Driver Verifiier will be enabled.

Be aware that Driver Verifier will remain enabled across all reboots and shutdowns. It can only be disabled manually.

Also be aware that we expect BSODs. Indeed, we want BSODs, to be able to identify the flaky driver(s). You MUST keep all minidumps created whilst Driver Verifier is running, so disable any disk cleanup tools you may have.

10. Leave Driver Verifier running until you have between 5 and 10 BSODs/dumps, or for 48 hours. Use your PC as normal during this time, but do try and make it BSOD. Use every game or app that you normally use, and especially those where you have seen it BSOD in the past.

11. To turn Driver Verifier off enter the command verifier /reset in either Run command box or a command prompt and reboot.

Should you wish to check whether Driver Verfier is enabled or not, open a command prompt and enter the command verifier /query.

12. When Driver Verifier has been disabled, navigate to the folder C:\Windows\Minidump and locate all .dmp files in there that are related to the period when Driver Verifier was running (check the timestamps). Zip these files up (using the Windows built-in zip tool) and upload that zip file to here or to the cloud with a link to it here.
 
Upvote 0 Downvote
Solution
FLAM3playZ said:
1) GPU is updated to the latest version
2) I did run a memory diagnostic test
3) I also performed a clean boot earlier
4) I performed sfc /scannow multiple times
5) I even did the system restore point

PLEASE SOMEONE HELP AAAAA
Click to expand...
If your still having issues, boot into safe mode and run the display driver uninstaller. This removes anything and everything to do with your previous 3rd party driver installs. Reboot and install latest driver version.



Display Driver Uninstaller (DDU) V18.0.6.4 Released.

Display Driver Uninstaller is a driver removal utility that can help you completely uninstall AMD/NVIDIA/INTEL graphics card drivers and packages from your system, trying to remove all leftovers (including registry keys, folders and files, driver store). The AMD/NVIDIA/INTEL video drivers can...
www.wagnardsoft.com
 
Upvote 0 Downvote
I sort of gave up on this but I want to come back to the game so I tried the Driver Verifier now. Apologies for the late reply.
I attached a zip consisting of minidumps of three BSODs that occurred during Driver Verifier. And a brief note of the settings of Driver Verifier below:

1) 1st Verification

UNCHECKED TESTS -> Randomized Low Resources Simulation and DDI compliance checking
DRIVERS -> ALL DRIVERS whose Provider is not Microsoft Corp.
BSOD -> BSOD Occurred at startup, .DMP file shows ntoskrnl.exe and vgk.sys caused BSOD

2) 2nd Verification

UNCHECKED TEST -> DDI compliance checking
DRIVERS -> ALL DRIVERS whose Provider is not Microsoft Corp, but the following four drivers provided by Microsoft are selected,

Wdf01000.sys
ndis.sys
fltMgr.sys
Storport.sys

BSOD -> BSOD Occurred at startup, .DMP file shows ntoskrnl.exe and vgk.sys caused BSOD

3) 3rd Verification

UNCHECKED TEST -> DDI compliance checking
DRIVERS -> VGK.SYS was deselected, and ALL MICROSOFT drivers were deselected as well.
BSOD ->
NO BSOD on STARTUP, but BSOD occurred later
Since I was able to log in, I got into VALORANT, but the game was extremely laggy (FPS dropped to around 05-10). I roamed inside the practice range for around 3-5minutes. Then I quit the game. The moment I quit the game, a BSOD occurred.

Please provide me with further help on how to fix it. I tried reinstalling VALORANT and Riot Vanguard but no help.
 

Attachments

Upvote 0 Downvote
I always use DDU when updating graphics card drivers.
 
Upvote 0 Downvote
You could try (if you haven't already) contacting the devs as described above?

I am correct in assuming you only bsod when trying these games yes?
 
Upvote 0 Downvote
It sounds like you're still experiencing frequent BSODs even after following some standard troubleshooting steps. Issues with drivers and kernel-related files such as nvlddmkm.sys (NVIDIA), ntoskrnl.exe (Windows kernel), and win32kbase.sys (graphics subsystem) can be frustrating, but don't worry! Let's continue troubleshooting at a deeper level.
Here’s a more advanced set of steps to diagnose and (hopefully) resolve the issue:

Step 1: Perform a Clean Graphics Driver Installation​

Even though your GPU driver is updated, remnants of old drivers or corrupted installations can cause problems. Try this:
  • Download DDU (Display Driver Uninstaller):
  • Get DDU from the official page: https://www.guru3d.com/files-details/display-driver-uninstaller-download.html.
  • Boot into Safe Mode:
  • Press Shift + Restart on the Windows login screen and navigate to "Advanced Options > Startup Settings > Enable Safe Mode".
  • Run DDU:
  • Use DDU to completely remove all traces of the current GPU driver.
  • Reinstall the Driver:
  • Download the latest stable version (not beta) of your GPU driver directly from NVIDIA. Perform a custom install and select Clean Installation.

Step 2: Check GPU Hardware Health​

If the driver isn't the problem, the GPU itself could be at fault. Here's how to check:
  • Stress Test Your GPU:
  • Use tools like FurMark or MSI Kombustor to stress test your GPU. Observe temperatures and see if the system crashes. If it does, your GPU might be faulty or overheating.
  • Monitor GPU Temps:
  • Use software like HWMonitor or MSI Afterburner to check that your GPU temperatures remain below 85°C during load.
  • If temperatures are spiking, clean your GPU of dust, check for proper airflow, and ensure fans are spinning freely.

Step 3: Test Your RAM in Depth​

Even if your quick memory diagnostic test passed earlier, intermittent RAM issues can still cause crashes. Try this:
  • Run Memtest86 for a Few Passes:
  • Create a bootable USB with https://www.memtest86.com/.
  • Boot your system using the USB and let it run for at least 4 complete passes (this may take hours). Any errors detected could indicate bad RAM.
  • Test Modules Individually:
  • If errors are found, test one RAM stick at a time to pinpoint the faulty module.

Step 4: Disable Overclocking​

If your GPU, CPU, or RAM is overclocked, stability issues can occur.
  • Reset all overclocking to default in your BIOS or using software. Even factory overclocked GPUs and RAM can sometimes cause issues, so consider underclocking them slightly.

Step 5: Inspect System Files and Error Logs​

  • Use DISM to Repair System Image:
  • Open Command Prompt as Administrator and run:
    Code: 
     DISM /Online /Cleanup-Image /RestoreHealth
  • Then run sfc /scannow again to repair remaining issues.
  • Analyze Minidump Files:
  • Minidump files generated by BSODs contain useful information about what went wrong. Here’s how to analyze:
  • Press Win + R, type sysdm.cpl and go to the Advanced tab.
  • Under "Startup and Recovery," click Settings and ensure "Write debugging information" is set to Small memory dump.
  • Use tools like https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/ or https://www.nirsoft.net/utils/blue_screen_view.html to analyze crash dumps.
  • Pay close attention to the file or process causing the error.

Step 6: Run Hardware Diagnostics​

If the above steps don’t resolve the issue, you may have failing hardware. These diagnostics might help:
  • Check Storage Health:
  • Use CrystalDiskInfo or Check Disk (via chkdsk /r) to ensure your SSD/HDD is healthy.
  • Power Supply Test:
  • A failing power supply (PSU) can cause random crashes. Consider swapping in a known-good PSU if possible to rule this out.

Step 7: Revisit Windows Installation​

If you've exhausted all hardware and driver-related possibilities, there’s a chance the issue lies with your Windows OS itself.
  • Perform a Clean Windows Install:
  • Back up your data and create a fresh install USB using https://www.microsoft.com/en-us/software-download/windows10. Rebuilding your OS from scratch ensures no remnants of corrupted files remain.
  • Post-Install Set Up:
  • Install graphics drivers first.
  • Only install essential software and peripherals for testing - keep bloatware minimal to check stability.

Final Option: Hardware RMA​

If you still experience BSODs, you might be looking at defective hardware, especially:
  • Faulty GPU: RMA your card if it’s still under warranty.
  • RAM issues: Replace your failing DIMMs.
  • Motherboard chipset issues: Examine for physical damage (like bad capacitors) and consider professional inspection.

Request Additional Information​

If the problem persists, can you:
  • Share minidump files (C:\Windows\Minidump folder)?
  • Provide more information about your system setup:
  • GPU model/driver version.
  • CPU and motherboard details.
  • Power supply brand/model/wattage.
I’ll analyze the crash dumps and provide more specific guidance. Hang in there! These issues can be annoying but are solvable.
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

I
  • Solved
Windows 7 Frequent BSODs Caused by ntoskrnl.exe: Seeking Help with Hardware or Driver Issues
Replies
2
Views
2K
ilku
I
R
  • Solved
Windows 7 Random BSODs caused by ntkrnlpa.exe and win32k.sys
Replies
3
Views
6K
usasma