Windows explorer dr watson crashing

The disassembly portion includes the function being executed when the error occurred, the memory address, raw machine instruction, and decoded machine instruction for each adjacent instruction and an analysis of the faulty instruction. The default value is 10 0xA in Hexadecimal. The "Number of Errors to Save" parameter specified how many errors should be maintained in its application error viewer and in the Event Viewer application log.

By default, this value is 10 0xA in Hexadecimal. The possible values range from 0 to 4,,,! In reality though, you would not want to set the value this high.

When the number of recorded errors reaches the value of this entry, Dr. Watson will continue to add errors to the log file and the dump - but will not add errors to its own log viewer or the Application Event log until it is reset using the "Clear" button or the value is increased. The "Dump Symbol Table" dumps the symbol table for each module.

Selecting this option can cause log files to become very large! The "Dump all Thread Contexts" specifies whether Dr. Watson will log a state dump for each thread in the program that failed or only the faulting thread. The other options are self-explanatory. The Log File and Dump File path are not present by default - if you change the location of these files, you will see the Registry values for these options.

So that wraps up Dr. Watson - but what if you're running Windows Vista or Windows Server , or you prefer to use something other than Dr. For pre-Vista Operating Systems, you can also use Userdump. Let's look at ADPlus first. ADPlus has two different modes - Hang and Crash. Ran SeaTools advanced scan on hard disk - no problem found. Turned off Data Execution Prevention on explorer. Re-installed Windows XP. I have Hardware Sensors Monitor installed which shows no overheating issues.

I have also attached the Dr. Watson log which caught the last crash but I don't understand it. Any help would be appreciated, thanks. Frank4d Retired Trusted Advisor. Joined Sep 10, Messages 9, Maybe they will show something DrWatson doesn't. Thanks for the reply Frank.

Unfortunately this is the first crash since the re-install so it's the only one to go on. Watson directory. I think I will just have to wait till it crashes again a couple of more times before I can provide more information. I cannot replicate the crash and as it is totally random it will probably occur anywhere between a couple of days and a couple of weeks.

Joined Sep 5, Messages 5. Thanks Macaholic for having a look at the log. Well, explorer. Faulting application explorer. Event ID: , Time: Explorer.

Unfortunately Dr. Watson crashed when I clicked the Debug button so the errors were not logged and no dump files were created. I have taken your advice and replaced the shell I thought I'd give you an update on the problem. Since I replaced the shell As I have said before, sometimes it can occur after a couple of weeks, so if it doesn't crash within another week I will mark the problem as solved.

Thanks for checking back. Well it happened again this morning when I opened "My Computer" with no applications running. It said "Windows explorer has encountered a problem and needs to close". Event ID Faulting application explorer. The desktop, taskbar and system tray disappear briefly but then come back again. For this purpose, you can switch to the "turn off" option available for the working antivirus programs on your system. It can be done for fixing the issue of crashing windows.

In your Windows Explorer, you get a feature of a Quick access menu that can help you access some files or folders from your system quickly. Being the utility part, quick access issues may result in causing the issue of Explorer keeps crashing. Follow the instructions for this purpose:. The unexpected closure of some utilities may occur as a result of corrupt drives or files in your system.

It is not going to be an ideal option if you start searching for the corrupt drives manually and fixing them. In the windows, there exist some in-built methods which can help resolve the issue of corrupt drives.

In the command prompt, use some of the commands to resolve the issue on your system. Check them below:. If you're downloading any programs with third-party on your system, it may result in making integration additions to the explorer.

And if there is damage in any integrations irrespective of any reason, it can result in the issue of Explorer keeps crashing. You can use a free app to turn off extensions with the following steps:.

If you look at any windows crashing issue when you access any file or folder, then you should keep an eye on the folder permission. Use the following guide:. Step 1: Access "File Explorer" from the search bar and right-click on the folder for changes.

Click on "Properties. Step 4: Go to the "Enter the object name to select" menu and put "Administrator. Step 5: Select the "Check names" option to verify and hit the "OK" button. Hanging application explorer. Faulting application drwtsn These are the Event Viewer excerpts of the crashes that I got. For the Explorer, hangs, unknown module, ntdll. Does anyone have any ideas how to fix this! Please help! Also the event viewer logs are somewhat similar to Simdudes. Data: 41 70 70 6c 69 63 61 74 Applicat 69 6f 6e 20 46 61 69 6c ion Fail 75 72 65 20 20 64 72 77 ure drw 74 73 6e 33 32 2e 65 78 tsn Data: 41 70 70 6c 69 63 61 74 Applicat 69 6f 6e 20 46 61 69 6c ion Fail 75 72 65 20 20 65 78 70 ure exp 6c 6f 72 65 72 2e 65 78 lorer.

What is causing this? It worked for about 10 minutes and then it started happening again. I have Spybot and Ccleaner on both and they all seem to be finding nothing. No mention of it doing this kind of damage though. I am also backing up my main PC with Drive Image so that I can restore an older image to see what effect that has. My PC isn't connected to the internet, so it can't be from a bad update or malware since I only updated it through the 3 Service Packs when each one came out.

And I installed SP3 quite a long time ago while these crashes started about 10 days ago. It must be something else, that corrupts those files as soon as they are replaced with new ones. The only things that I updated recently on my PC are the DirectX august version and my graphic card drivers ati catalyst 8.

I've been suggested to perform a repair install of my WinXP Pro, but I'm afraid that once replaced, the bad files that'll get replaced will be corrupted back straight away. Shockwolf , there must be something that both your PC's have in common, a recent update or something.

As I said, the only things that I've changed on my computer around the date when this started are the DX 9 aug update and the Catalyst 8. Have you got any of these two on your PC's? Indeed it could be that DX9 update then. Normally I have my automatic updates set to notify me before downloading and installing however I noticed that somehow they have been set back to automatic.

It could also be that the bug in the DX9 patch is greater with the Catalyst drivers than it is with the Nvidia drivers which is why you're having a worse time than I am with this. Ok I've restored an older image on both of my PC's and so far they seem to be behaving properly. I have even received updates on my main PC with no introduction to any more errors. However I have not noticed any DX9 updates included yet. I shall be keeping an eye out for them though and probably ignoring them from now on.

Reinstalling Windows or restoring a backup may be the only answer to this I'm afraid. I'll post back here if the issue returns. I can't even repair install the windows. The windows setup manager detects two blank drives on my computer and asks me on wich one to install? It should have detected my windows on drive C and I could have been able to repair-install it and keep all my other stuff too. What the heck is wrong? I can't backup or save my files, there's no windows detected on my computer, I've done all the virus, addware, spyware, malware, etc.

I've ran the system file recovery and nothing was found, nothing has changed What the heck happened?? Does anyone have any idea? What could be wrong?? I've found this problem reported on various internet forums since , so it can't be the august DX9 update, or any new graphic driver, or anything from the SP3.

Also, people are reporting a wide array of different. Almost always taking DrWatson with it, however dbghelp. I'm going nuts!