These STOPCODES started only once with VIDEO TDR FAILURE nvlddmkm.sys; then came MEMORY MANAGEMENT, CRITICAL PROCESS FAILED, and mostly vmbkmclr.sys IRQL

Question

In following up STOPCODE which survived an in-place reinstallation of Windows, I find out the one bugcheck to be 'd1' and the other 'ef' ('d1' will occur about the log-in screen, 'ef' will occur on trying to start randomly services that are stopped for Selective Mode -this mode survived too the reinstallation of Windows).

These bugcheck 'd1' are described in WINdbg Preview as 'improper addresses for paths to memory';

Surely there is nothing else to do than resetting the device from WinRE?

In the event of involving display drivers, there has been already a removal and reinstallation of drivers by way of e.g. DDU Utility

Answer 1

Hello Claus Debanker,

Thank you for posting in Q&A forum.

The bugcheck 'd1' error, often referred to as DRIVER_IRQL_NOT_LESS_OR_EQUAL, typically indicates that a driver has attempted to access an improper address while the system was at a high IRQL (Interrupt Request Level). This can lead to system crashes and is usually related to driver issues or memory corruption.

You can follow these steps:

1. Update Drivers: Ensure all your drivers are up to date, especially those related to network and storage devices.
2. Check for Hardware Issues: Run hardware diagnostics to check for any issues with your RAM or other hardware components.
3. Analyze Memory Dumps: Use WINdbg to analyze memory dump files. You can use commands like !analyze -v to get detailed information about the crash.
4. Check for Software Conflicts: Perform a clean boot to rule out software conflicts.

I hope the information above is helpful.

If you have any questions or concerns, please feel free to let us know.

Best Regards,

Daisy Zhou

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.