INVESTIG8 Documentation
Complete guide to using INVESTIG8, the free Revit journal file parser. Learn how to analyze crashes, diagnose performance issues, and generate detailed reports from your Revit journal files.
What is a Revit Journal File?
A Revit journal file is a text file that records every action performed during a Revit session. Revit automatically creates a new journal file each time you start the application, logging commands, file operations, errors, and system events.
Journal files are invaluable for:
- Crash investigation - Understanding what happened before Revit crashed
- Performance analysis - Identifying slow operations and memory issues
- Add-in troubleshooting - Finding which add-ins are causing problems
- Support requests - Providing detailed information to Autodesk or add-in vendors
Journal files can grow quite large (50MB+) for long sessions. INVESTIG8 can handle files up to 100MB.
Finding Journal Files
Revit stores journal files in a specific location on your computer. The default path is:
%LOCALAPPDATA%\Autodesk\Revit\Autodesk Revit [Year]\Journals
For example:
C:\Users\YourName\AppData\Local\Autodesk\Revit\Autodesk Revit 2024\JournalsC:\Users\YourName\AppData\Local\Autodesk\Revit\Autodesk Revit 2025\Journals
Quick Access Method
Win + R on your keyboard to open the Run dialog.%LOCALAPPDATA%\Autodesk\Revit and press Enter.Revit keeps only the last 10 journal files by default. If you need to investigate an older crash, check your recycle bin or backup the journals folder regularly.
Quick Start Guide
Analyzing a journal file with INVESTIG8 takes just a few seconds. Here's how:
.txt journal file. Files up to 100MB are supported.Report Overview
After analysis, INVESTIG8 generates a comprehensive report divided into several sections. Each section provides specific insights into your Revit session.
Crash Detection
INVESTIG8 uses intelligent pattern matching to detect crashes and identify their likely cause. The parser examines the last 50 lines of the journal file (the "crash zone") where crash indicators are most likely to appear.
Detected Crash Types
| Crash Type | Description |
|---|---|
| Out of Memory (OOM) | Revit ran out of available RAM or virtual memory |
| Fatal Exception | Unhandled exception caused Revit to terminate |
| Access Violation | Memory access error, often from corrupt data or driver issues |
| Graphics Crash | GPU or graphics driver related crash |
| Add-in Crash | Crash caused by a third-party add-in |
| Network Timeout | BIM 360/ACC connection issues or network failures |
Memory Leak vs Hardware Exhaustion
INVESTIG8 performs intelligent memory diagnosis to distinguish between:
- Memory Leak - Software bug causing unbounded memory growth (RAM still available but Revit's allocation grows)
- Hardware Exhaustion - System genuinely running out of RAM (common with large models on 16GB machines)
- Network OOM - Memory issues caused by network queue buildup (PubNub, BIM360)
Session Information
The Session Information section provides key details about the Revit session:
- Revit Version - Full version and build number
- Session Duration - How long Revit was running
- Session Start Time - When the session began
- Startup Time - How long Revit took to start
- Username - The Windows user running Revit
Environment & Hardware
Understanding the hardware environment is crucial for diagnosing performance issues. INVESTIG8 extracts:
- Operating System - Windows version and build
- RAM - Total system memory
- GPU - Graphics card model
- Graphics Driver - Driver version (important for graphics crashes)
- .NET Version - Installed .NET framework version
Outdated graphics drivers are a common cause of Revit crashes. Check the driver version in the report and update if it's more than 6 months old.
Add-ins
The Add-ins section lists all third-party add-ins that loaded during the Revit session, along with their load status.
Add-in Load Status
- Success - Add-in loaded correctly
- Failed - Add-in failed to load (may cause issues)
- Disabled - Add-in was disabled by user or Revit
If you see failed add-ins and are experiencing crashes, try disabling them temporarily. Go to Revit > Options > Add-ins to manage your add-ins.
Memory Analysis
INVESTIG8 tracks memory usage throughout the session, capturing RAM and Virtual Memory snapshots at regular intervals.
Memory Metrics
- RAM Usage - Physical memory used by Revit
- Virtual Memory - Total memory allocation including page file
- Peak Usage - Maximum memory used during session
- Available RAM - Free system memory at crash time
Memory Health Indicators
The parser uses thresholds to identify potential memory issues:
- Normal - RAM usage below 80% of system memory
- Warning - RAM usage between 80-95%
- Critical - RAM usage above 95% or OOM detected
Files & Links
The Files section shows all Revit files accessed during the session:
- Central Model - The workshared central file path
- Local File - The local cached copy path
- Linked RVT Files - Other Revit files linked into the project
- Linked CAD Files - DWG, DGN, and other CAD links
Sync Performance
For workshared models, INVESTIG8 tracks synchronization operations:
- Number of Syncs - How many times the user synchronized
- Average Sync Duration - Typical sync time
- Last Sync - When the last successful sync occurred
- Sync Failures - Any failed sync attempts
Errors & Warnings
INVESTIG8 uses phase-aware error filtering to prioritize the most relevant errors:
Error Classification by Location
- Startup Errors (lines 1-500) - Often noise from assembly binding and lazy loading. Usually ignorable.
- Runtime Errors (middle) - Context errors that may or may not be significant.
- Crash Zone Errors (last 50 lines) - Primary suspects. These errors occurred immediately before the crash.
User Warnings
The parser also captures Revit warnings shown to the user during the session, such as:
- Element warnings (overlapping rooms, duplicate marks)
- Workset conflicts
- Missing links or fonts
PDF Export
Export your analysis report as a PDF document for sharing or archiving. The PDF includes all sections of the report in a professional format.
How to Export
- Complete your journal analysis
- Click the Download PDF button in the report toolbar
- The PDF will be generated and downloaded automatically
Email Report
Send the analysis report directly to an email address. This is useful for sharing with colleagues, IT support, or Autodesk support.
How to Email
- Complete your journal analysis
- Click the Email Report button
- Enter the recipient's email address
- Click Send
Frequently Asked Questions
Yes, INVESTIG8 is 100% free with no limits on usage. No account required, no trial period, no feature restrictions. We built it as a free tool for the AEC community.
INVESTIG8 can process journal files up to 100MB. Most journal files are under 50MB, so this should cover virtually all use cases.
Yes. Journal files are processed on our server and the extracted data is stored temporarily for report viewing. We do not share your data with third parties. Files are automatically deleted after 30 days. See our Privacy section for details.
INVESTIG8 supports journal files from Revit 2019 through 2026. The parser is regularly updated to support new Revit versions.
Currently, INVESTIG8 analyzes one journal file at a time. For batch analysis across multiple files, you would need to upload them individually.
Some crashes don't leave clear indicators in the journal file. This can happen with sudden system crashes, blue screens, or power failures. In these cases, the journal may be incomplete or truncated.
Privacy & Data
We take data privacy seriously. Here's how INVESTIG8 handles your journal files:
- Processing - Files are uploaded to our server for parsing. The file itself is not stored permanently.
- Storage - Extracted analysis data is stored in our database for report viewing.
- Retention - Analysis reports are automatically deleted after 30 days.
- Sharing - We never share your data with third parties.
- Encryption - All transfers use HTTPS encryption.
Journal files may contain file paths, usernames, and project names. If this is a concern for your organization, review the journal contents before uploading or use INVESTIG8 only on non-sensitive projects.