Hi everyone,

**First of all, I want to express my deepest gratitude to everyone who has been following this case study, sharing their thoughts, and supporting this investigation.** Your engagement and encouragement have been invaluable in bringing this issue to light.

Following up on my previous posts where we identified the exact code-level anomaly causing the freeze issue on the Otter / PYD Life system:

To ensure this is completely objective, I want to rule out any remaining "environment variables" across different user setups. I want to verify if other units—whether handled by end-users or distributors/sellers—are encountering the exact same execution freeze and raw log signatures across all Otter and PYD Life product lines.

For this purpose, I am preparing a lightweight, diagnostic-only tool: **Port Locker (Light Edition)**.

# What Port Locker Light does:

1. **Automated Dual-Log Bundle:** Captures both Windows raw system event logs AND internal Otter/PYD Life program logs, bundling them into a clean `.zip` file.
2. **Quick Diagnosis Snippet:** Automatically extracts the last 500 lines of system logs into a simple text file within the `.zip`.
3. **Built-in Resource Dashboard:** Features an integrated real-time monitor so you can easily check hardware usage during printing at a glance—such as actual CPU load, whether 64GB RAM is truly necessary or being maxed out, GPU activity (Memory/Copy/3D), and network traffic.
4. **100% Portable & Safe:** No installer required, no registry modifications, and no system settings changed. It strictly bundles existing system diagnostic logs without modifying your environment.

# Why We Are Requesting Your Log Data (The Core Technical Reason):

In my previous Parts 1–5 analysis, the exact root cause of the freeze was successfully identified without guesswork by cross-analyzing Windows system event logs with internal program logs.

**Windows OS automatically and permanently records every application hang, crash timestamp, and memory exception.** By extracting and cross-analyzing your PC's system log alongside the Otter program log, **we can instantly pinpoint the exact failure code without exception.** If your logs match the exact same error signatures, it irrefutably proves that the freeze is caused by the exact same underlying software defect—completely debunking any manufacturer claims of "local PC environment" or "user error."

# Simple 3-Step Process:

1. Unzip the file and place the folder directly in your system drive (e.g., `C:\PortLocker`).
2. Right-click the app and select **"Run as Administrator"** *(required to access raw Windows system event logs)*.
3. Run the log extraction and send over the generated `.zip` file via DM for analysis.

# Looking for Volunteers (Users & Dealers Across All Otter / PYD Life Models):

If you are currently experiencing unexplained freezes with your unit and want to verify if your machine is affected by the same underlying code defect, I am happy to provide this tool for free and analyze your log files.

To help establish a clear technical baseline, **when sending your log via DM, it would be great if you could just let me know:**

* **Your Country / Region** *(e.g., USA, UK, Germany, etc. — to verify global environmental independence)*

*(Note: Whether your unit is branded as* ***Otter, PYD Life****, or other local distributor brandings sharing the same hardware design, you are very welcome to participate!)*

Whether you are an end-user or an international dealer/distributor handling any of these machines, your data will be extremely valuable in proving this issue objectively.

If you'd like to participate, please **leave a comment below or send me a Direct Message (DM)**.

*(Note: To avoid automatic spam filters and respect link restrictions, I will not post direct download links here. Please comment or DM me to receive the tool link.)*

>**Privacy & Data Protection Assurance:** **You DO NOT need to disclose your real name, identity, or any personal details.** You can contact me completely anonymously via DM.  
>  
>  
>  
>**ONLY the hardware model/version signatures, country region, and specific technical error signatures (error codes, failure timestamps, and execution freeze logs) will be extracted and utilized for this investigation.** Your privacy is 100% protected.

**By analyzing both the system log and the internal software log together, we can instantly uncover the exact evidence already sitting inside your PC. If we verify that this exact same execution error signature exists across multiple users worldwide, it will serve as undeniable proof of a systemic, code-level defect.**

**Whether you are an individual owner or an international dealer/distributor handling these units, I humbly ask for your cooperation from around the world. Gathering raw log data from multiple independent users—even just 1, 2, or 3 testaments—will give us the undeniable evidence needed to confront the manufacturer, hold them fully accountable, and demand a clear, responsible stance on this issue.**

**Thank you once again to this amazing community for your continued support and for helping us reach the truth.**

Case Study: How an Asian DTF Manufacturer Lied About Hardware and Abandoned Support — Part 6: Call for Log Verification Across All Otter / PYD Life Models (Users & Dealers), Free Diagnostic Extraction Tool