I would need to go back to the day I first started seeing this to find out what changes were made on my workstation and isolate the responsible culprit. Several days had passed since I first encountered the problem. With two false-positives, I would need to dig deeper to find the cause. To confirm I didn’t have a bad image of Process Monitor running on my workstation, I ran it live from the SysInternals site and the system still crashed. Stack-wise, it was pretty much the same as the previous dump, but with offender listed this time as Process Monitor: After starting Process Monitor, the system crashed again and I opened the dump created in C:\Windows\Minidump. To be sure, though, I replaced the RAM sticks and tested the issue again. Although memory can go bad at any time for any reason, this was not likely the cause. When analyzing, be wary of false-positives. Further down, the debugger points to the faulty module as memory corruption: All the other modules being called here were Microsoft so it didn’t seem to be an issue with any 3rd party device drivers or application components. You can see that PROCMON20 (the process monitor sys file) is called right before passing off to nt to bug check. This can be caused by any number of things, from bad RAM to buggy drivers and applications. Going down further, we have the exception code:Ĭ0000005 tells us this is an access violation, which occurs when a process attempts to access a portion of memory assigned to another application, or an unused memory area, without having permission to do so. In this case, the bug check “indicates that a kernel-mode program generated an exception which the error handler did not catch.” I suppose this means that WinDbg’s heuristics cannot definitively isolate what caused the system to bug check. Use WinDbg help to gather some details about the bug check. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M in the excerpt above. When reading a dump, gather some basic information. I waited for a few seconds for the symbols to load: Crashing Config Manager Client
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |