x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,192 Location %systemroot% Mar 3, 2021 #21 @zbook I wouldn't just randomly pull out third-party drivers from the raw stack. With a Stop 0x133, you need to get a full kernel memory dump and then see where the DPC which timed out is running. From there, you'll need to examine the call stack and attempt to find the driver which has held up the DPC completion. x BlueRobot said: If possible, please zip and upload the MEMORY.DMP file, it should be in the following location: Click to expand... I forgot to mention, this file will need to be uploaded to a file sharing site such as Google Drive.
@zbook I wouldn't just randomly pull out third-party drivers from the raw stack. With a Stop 0x133, you need to get a full kernel memory dump and then see where the DPC which timed out is running. From there, you'll need to examine the call stack and attempt to find the driver which has held up the DPC completion. x BlueRobot said: If possible, please zip and upload the MEMORY.DMP file, it should be in the following location: Click to expand... I forgot to mention, this file will need to be uploaded to a file sharing site such as Google Drive.
Z zbook Member Joined Oct 2, 2015 Posts 919 Mar 3, 2021 #22 x BlueRobot said: If possible, please zip and upload the MEMORY.DMP file, it should be in the following location: Rich (BB code): %systemroot%\MEMORY.DMP Click to expand... A memory.dmp was not created (see logs)
x BlueRobot said: If possible, please zip and upload the MEMORY.DMP file, it should be in the following location: Rich (BB code): %systemroot%\MEMORY.DMP Click to expand... A memory.dmp was not created (see logs)