![]() With the above in mind here are some diagnostic procedures that I have just worked out Of course the same information is also available via windbg with its LM command. They contain the list of modules which the crashing thread was seen to have loaded and that extra information is suppressed by both msinfo32.exeĪnd RM. In any case, you can supplement what Reliability Monitor is showing by finding related Report.WER files. I still haven't found a command line query that gives us that information. I wonder how that gets derived? winver is what I would use to find out if you are still at v29. Windows Key S > type problem reports then click on "View all problem reports Control panel"Ĭan you right-click on a few of the "Internet Explorer" "stopped working" errors > View technical detailsįaulting Application Path: C:\Program Files (x86)\Internet Explorer\iexplore.exeĪdditional Information 2: bdcb33e65a9843796b7ec31cc25bda3bĪdditional Information 4: 7ae5ff970d16e403baf57c3408d06e56īucket ID: d1267b0ea6672e6c58a9ee0f9aaacd47 (107721204135) ![]() ![]() I have a friend using windows 10 and anytime he opens IE, he gets an error that says IE has stopped working and it just loops, loops, and loops.
0 Comments
Leave a Reply. |