📎 AI Summary:
The thread discusses a Windows user experiencing persistent issues despite running SFC and DISM scans and attempting a system reset. A responder identifies a likely cause related to graphics drivers, particularly atikmdag.sys, and recommends removing the current GPU driver with DDU before reinstalling a fresh version. They also highlight potential issues with other drivers like AMD Overdrive and Microsoft wireless device drivers, advising the user to update or troubleshoot these as needed.
The thread discusses a Windows user experiencing persistent issues despite running SFC and DISM scans and attempting a system reset. A responder identifies a likely cause related to graphics drivers, particularly atikmdag.sys, and recommends removing the current GPU driver with DDU before reinstalling a fresh version. They also highlight potential issues with other drivers like AMD Overdrive and Microsoft wireless device drivers, advising the user to update or troubleshoot these as needed.
Solution
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {2d8, 7, 0, fffff8076fc52aa4}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+a2aa4 )
Followup: MachineOwner
all dump files...
kemical
Essential Member
Member details
- Joined
- Aug 28, 2007
- Messages
- 36,163
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {2d8, 7, 0, fffff8076fc52aa4}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+a2aa4 )
Followup: MachineOwner
all dump files mention the gpu driver so try removing your current version using the DDU (this will remove any corruption) then installing a new driver:
Link Removed
I also noticed a number of other possible issues such as:
AODDriver2.sys Tue Feb 11 11:06:52 2014: AMD Overdrive; also in EasyTune6 for Gigabyte motherboard, Known BSOD issues in Win7. If your overclocking then please stop until after the bsod cause has been found.Please remove until after testing has finished.
dc3d.sys Wed May 18 09:07:24 2011: Filter Driver for Identification of Microsoft Hardware Wireless Mouse and Keyboard Device Models - Microsoft IntelliType Pro / IntelliPoint please update:
Link Removed
Your driver dates look a little uniform and i wonder if you used an app to find the drivers for you?
Post any new dump files.