Hi wjang.
It is some driver related issue, but the crash dump recording mechanism failed to point out the failing driver.
We may take two sets of action here, one is precautionary, and the other is detective.
First, the precautionary action. You have a lot of startup entries. Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
- Click on the Start button
- Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
- Select the “Startup” tab.
- Deselect all items other than the antivirus and the touchpad driver, SynTPEnh.
- Apply > OK
- Accept then restart.
Then go for the detective action... enable Driver Verifier to monitor the drivers.Put the computer to hibernate for a few times with DV enabled. Hopefully we will get a crash dump that will serve our purpose.
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using
CCleaner looking at Tools > System Restore.
If there is no points,
make a System Restore Point manually before enabling DV.
Let us know the results, with the subsequent crash dumps, if any.
Also, upload the list of all the third party drivers Using
NirSoft DriverView :
- Download and execute Driverview
- View > Hide Microsoft Drivers
- Edit > Select all
- File > Save Selected Items
- In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
- Zip the .txt file and upload it.
______________________________________
Code:
BugCheck D1, {abcdd8a8, 2, 0, fffff88000e561d9}
Probably caused by : Wdf01000.sys ( Wdf01000!FxIoQueue::ProcessPowerEvents+169 )
Followup: MachineOwner
---------