New
#21
If you get any more BSOD after disabling XMP, please enable driver verifier.
OK I have created a restore point and enabled the Driver Verifier. Is there anything I need to do, other then just using this machine until something happens.
Looking at that list there is a bunch of stuff in there I don't think needs to be there anymore. Logitech, and Trend Micro mostly.
I looked at this Driver Verifier early in my BSOD battles but it was unclear at the time how to use it. This forum has great tutorials.
Arc I thought your banner looked familiar, pulled out my copy of The Bhagawad Gita and found it. I have been fascinated by Hinduism for many decades.
I am not fascinated by Hinduism or any other religion. I trust in only one religion, that is humanity. All the subsets of it make mankind different based on religion. Where there is a difference there starts an issue.
To me, Gita is not a religious book but a great philosophy; I like that philosophy. It makes me think about many a things, but not about the god. Because he/she/they does/do not exist for me.
Let us see what Driver Verifier resulted. :)
Here is the 2nd Dump file after running Driver Verifier. the BSOD happened just shortly before 0700 MDT.
Attachment 86129
It is ironic that I am using my iPad to reference the instructions on this forum to DX a Windows 10 PC.
Neither of the crash dumps are seeming to be driver verifier enabled.
They are not listing up the verifier properties.
And the DEFAULT_BUCKET_ID is not also pointing to verifier.Code:1: kd> !verifier fffff803e58f47a0: Unable to get verifier list.
When it is verifier enabled, it states VERIFIER_ENABLED_MINIDUMP.Code:DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
Please make it sure that you have enabled verifier properly. Open a command prompt and enter verifier /query.
If a verifier enabled computer yields such dumps, then it is a strong indication of a hardware related issue.
Code:BugCheck 1000007E, {ffffffffc0000005, fffff8010c8961b2, ffffd000d0fa0db8, ffffd000d0fa05d0} Probably caused by : dxgmms2.sys ( dxgmms2!VIDMM_SEGMENT::ReserveResource+462 ) Followup: MachineOwner ---------** READ FROM HERE FIRST:Code:BugCheck 3B, {c0000005, fffff801f871ab9f, ffffd001ec72e640, 0} Probably caused by : NTFS.sys ( NTFS!NtfsFsdCreate+42f ) Followup: MachineOwner ---------
EDIT: Wait a bit ....before doing anything further, please uninstall (not disable, disabling will not stop loading the modules) Trend Micro Maximum Security, at least on a test basis. Activate Windows Defender.
Code:ffffd001`ec72eee8 fffff801`f8e38c11Unable to load image tmcomm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for tmcomm.sys *** ERROR: Module load completed but symbols could not be loaded for tmcomm.sys tmcomm+0x8c11Now let the computer run and keep a sharp observation on it (with verifier disabled) for at least next 24 hours. See how it goes. Let us know.Code:ffffd001`ec72ee98 fffff801`f9843f98Unable to load image tmevtmgr.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for tmevtmgr.sys *** ERROR: Module load completed but symbols could not be loaded for tmevtmgr.sys tmevtmgr+0x3f98
Trend Micro is uninstalled. I have run their anti-viral software since the mid-1990's. I have become increasingly unhappy with it. It has become bloatware. Trend Micro's password vault is a bad joke. Windows Defender is very good.