No, sorry, memory dumps don't "speak" in that manner. As a suggestion, check in the registry whether HKLM\System\CCS\Services\Co_mon exists. If so, some of the subkeys and values may offer clues as to where it's from.
If you're having trouble finding any legit-looking references to that driver name, that's sometimes suggestive of malware.
Found it and all is working fine you are a life saver thank you so much for your guidence.
No problem. Glad to hear it's all working!
===============================
(I just noticed that I confused the name of the driver that was giving you grief [oodivd] with the one causing another poster's crashes [co_mon]. Sorry. When you look at a lot of minidumps the distinctions between them tend to go all blurry.)
No problem. Glad to hear it's all working!
===============================
(I just noticed that I confused the name of the driver that was giving you grief [oodivd] with the one causing another poster's crashes [co_mon]. Sorry. When you look at a lot of minidumps the distinctions between them tend to go all blurry.)
But is it oodivd that was my issues?
Hehe, are you purposefully aiming to confuse me now?No problem. Glad to hear it's all working!
===============================
(I just noticed that I confused the name of the driver that was giving you grief [oodivd] with the one causing another poster's crashes [co_mon]. Sorry. When you look at a lot of minidumps the distinctions between them tend to go all blurry.)
But is it oodivd that was my issues?
Yes, according to a random sampling of your 16 minidumps, all of the crashes were almost certainly caused by a driver called oodivd.sys, which is apparently something to do with "O&O DiskImage".
Quote