However, I have found that lately the werfault.exe obscures the crash symptom, whereas ProcMon used to at least give us a pseudo Stack Back Trace of an exception event. ProcMon would be a better diagnostic for that. Does "fixed right away" mean that these don't happen any more? Otherwise I would say the "must be repaired" would probably suggest that you need to find a CheckSUR to run. On the windows update i got this two problems which then fixed right away: Crashes in low level modules like this are generally regardedĪs symptoms from a victim module not a problem one so a SBT or at least a list of loaded modules may give a clue about an possible interferer you could try to eliminate from your problem scenario. the same diagnostic that drwtsn32.log used to give us.
That Exception code may be useful but in general I think you may need to get a dump you can get a Stack Back Trace from. How did you manage that without getting into Control Panel?īelow is the technical details shown for the critical events of Explorer.Exe: I've also tried procexp, when i opened control panel i can see werfault.exe comes up under svchost.exe and explorer.exe under winlogon.exe. Windows Update components must be repaired.Potential Windows Update Database error detected 0x80070490.on the windows update i got this two problems which then fixed right
on the search and indexing, i clicked all four possibility of problems and the reply for it is, "Troubleshooting couldn't identify the problem". I got 4 critical events shown from reliability monitor. 16578, time stamp: 0x515fac9cįaulting application start time: 0x01ce7f297de515b4įaulting application path: C:\Windows\Explorer.EXEįaulting module path: C:\Windows\SYSTEM32\ntdll.dll 16433, time stamp: 0x50763130įaulting module name: ntdll.dll, version. I've tried reliability monitor and below is the technical details shown for the critical events of Explorer.Exe:įaulting application name: Explorer.EXE, version.
0 kommentar(er)
