I take it that by "it" you mean Verifier, not "the system"? I guess I'll keep the computer running without actively using it for another day or so then (then Verifier should still crash it at one point, shouldn't it?), because the many crashes that have occurred while running applications have not yielded usefuls minidumps so far.
All verifier does is wait and watch, when a driver misbehaves it should catch it and crash. If the driver isnt used for X hours verifier wont crash the system.
Hm, OK, but all crashes that have occurred with driver verifier running have, thus far, resulted in a 3b, 19 or 50 error, usually flagging ntoskrnl or a Microsoft driver (according to BlueScreenView). I can crash the system "at will" by leaving Firefox opened for a couple of minutes or visiting certain sites (especially with Flash videos or animations, it seems, but IE, Word and some other programs accessing the internet also crash; Chrome, on the other hand, seems very stable), but I have never seen an error with a "DRIVER_VERIFIER" description or with a non-Microsoft-driver identified as causing the crash. Does that mean that Verifier doesn't catch the faulty driver? Is there anything else I could try?
(Thanks again for your patience and advice!)
And here is the latest minidump file, created when Verifier was running. I opened IE and the system immediately crashed. Still, a Page_Fault_In_Nonpages_Area message, srvnet.sys was flagged in the crash stack... this is of no use, I guess?
What else could I try? Verifier just doesn't catch the errors.Can I be sure that the problem is a driver? MemTest86+ didn't show errors after 9 passes, but can it be something else, like a disk error or something wrong with Windows drivers or....?
Hi!
I still have not solved this error (see above) - the situation remains unchanged and my computer keeps crashing. Would anyone have a suggestion as to what to try next?
Thank so much in advance!
Quote