📎 AI Summary:
The WindowsForum thread discusses a user experiencing BSOD errors related to igdkmd64.sys on their Acer Predator laptop running Windows 10. The original poster updates their Intel graphics driver via Device Manager, after previous difficulties uninstalling it, in hopes of resolving the issue. The thread's responses advise confirming the driver source and suggest monitoring for further issues, with a generally positive and helpful tone.
The WindowsForum thread discusses a user experiencing BSOD errors related to igdkmd64.sys on their Acer Predator laptop running Windows 10. The original poster updates their Intel graphics driver via Device Manager, after previous difficulties uninstalling it, in hopes of resolving the issue. The thread's responses advise confirming the driver source and suggest monitoring for further issues, with a generally positive and helpful tone.
Solution
kemical
Essential Member
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000094, fffff803e9cc9bab, 0, 0}
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+2c9bab )
Followup: MachineOwnerLink Removed
So may I ask where did you get the driver currently installed? If it's from anywhere but the places mentioned above then you'll need to remove it and then run windows update. Just make sure you have a Link Removed so if anything goes wrong you can quickly get the system sorted out.
I'll be back shortly so will check if you have replied. Good luck.
Last edited by a moderator:
Thank you for your reply. I have just updated my Intel graphics driver through the Device Manager. I tried uninstalling it first, but everytime I did so it was still there when I restarted it. So I just went ahead and updated it instead. Hopefully this fixes the issue but I'll just have to wait and see.
kemical
Essential Member
Where did the update come from please?
