# Crash, exit or high CPU when viewing certain directories

**URL:** https://resource.dopus.com/t/crash-exit-or-high-cpu-when-viewing-certain-directories/1325
**Category:** Opus FAQs
**Created:** [December 3, 2005, 9:38pm UTC](https://resource.dopus.com/t/crash-exit-or-high-cpu-when-viewing-certain-directories/1325 "2005-12-03T21:38:04Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Leo](https://resource.dopus.com/user_avatar/resource.dopus.com/leo/32/69732_2.png) [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [December 3, 2005, 9:38pm UTC](https://resource.dopus.com/t/crash-exit-or-high-cpu-when-viewing-certain-directories/1325/1 "2005-12-03T21:38:04Z")

</div>

### See also:

- [Crash, exit or high CPU usage when right-clicking certain files](https://resource.dopus.com/t/crash-exit-or-high-cpu-when-right-clicking-certain-files/1335)
- [How to find components causing high CPU usage](https://resource.dopus.com/t/how-to-find-components-causing-high-cpu-usage/14144)
- [How to find components causing memory leaks](https://resource.dopus.com/t/how-to-find-components-causing-memory-leaks/10135)
- [Crash dumps for bug reports](https://resource.dopus.com/t/crash-dumps-for-bug-reports/8861)
- [General slowdown or instability investigation steps](https://resource.dopus.com/t/general-slowdown-or-instability-investigation-steps/4618)

## Summary:

_This FAQ helps you if Directory Opus crashes, exits or uses high CPU when you view a certain folder or folders containing certain types of files. These problems are usually caused by bugs in 3rd party components and this FAQ contains steps for finding and disabling the faulty component._\*

## Known Issues:

- See also: **[Shell extensions which are blocked by default](https://resource.dopus.com/t/shell-extensions-which-are-blocked-by-default/15350)**

- **Intel Optane / iaStorAfsServiceApi Service:**

- **Broken Icon Packagers:**

- **Boxcryptor** :

- **Windows 10 Fall Creators Update:**

- **Old versions of Icaros (part of K-Lite codec pack):**

- **Cloud Storage tools (Google Drive, OneDrive, Bitcasa, etc.):**

- **Acronis TrueImage:**

- **LibreOffice:**

- **Alcohol:**

- **Toolbars:**

- **Script Add-Ins:**

## Notes:

- **Right-click Context Menus:** If you are experiencing problems when opening right-click context menus, rather than when viewing directories, then you should read the separate [FAQ entry about that issue](https://resource.dopus.com/t/crash-exit-or-high-cpu-when-right-clicking-certain-files/1335).

- **Definition of "high CPU":** When this page says "high CPU" it means that something running inside of Opus has become stuck in a loop using as much CPU as it can get _on a single CPU thread_ and doesn't stop until you exit or terminate the program. You'll see approximately 100% CPU usage on a single-core system, 50% a dual-core, 25% on a quad-core, and so on.

## Isolating the cause:

If you experience crashes, apparently spontaneous exits, or high CPU usage when you open a Directory Opus window and point it to certain folders or folders containing certain types of files then the problem is likely caused by an Explorer shell extension, a video codec or an Opus viewer plugin that is going wrong because of the contents of one of the files in the directory.

Note that, depending on the columns you have showing, shell extensions, video codecs and viewer plugins can be called in _all_ view modes. Opus may call on them to extract information from the files even if you are not viewing them or generating thumbnails for them.

You can usually diagnose this problem in two ways:

1. **Work out which file is causing the crash:**

2. **Work out which plugin or extension is causing the crash:**

If you track down your problem to a particular file, plugin or shell extension then please report it via these forums (and to the authors of any involved 3rd party component, if applicable) to help anyone else who is using it, and in case a fix or workaround can be developed.

## Crash dump investigation:

If you cannot find the cause using the methods above, and the problem is a full crash, then there should be a [crash dump](https://resource.dopus.com/t/crash-dumps-for-bug-reports/8861) corresponding to the time of each crash.

We'll only look at crash dumps from people with linked accounts. Please start a thread if you wish to send them to us, with details of what's going wrong and what you have tried already, and we can advise further.