Table of Contents
Artificial Intelligence Translates the Language of Animals
Kim Kyung-jin, Attorney at Law
The Story of AI Learning to Listen to Whales, Dolphins, Birds, and Bees
Twelve chapters on how AI listens to dolphins, sperm whales, humpback whales, birds, and bees to find rules in their sounds, and what this technology means for its risks and for animal rights. Written in simple sentences a child can read, with verified sources in every section.
Table of Contents
AI Deciphers Ancient Scripts
Kim Kyung-jin, Attorney at Law
Ancient Records Revived by AI
In twelve chapters, this book explains how AI revives records once unreadable, from burned scrolls and wooden slips buried in mud to broken clay tablets. It covers virtual unrolling at Herculaneum, virtual collation of oracle-bone texts, reading Silla wooden tablets, computational analysis of undeciphered scripts, and multispectral archives, with verified references for each chapter.
Table of Contents
Artificial Intelligence for New Materials Design and Rocket Propulsion Engineering
Kim Kyung-jin, Attorney at Law
AI Potentials, Self-Driving Laboratories, and Physics-Informed Machine Learning (PIML)
Ten chapters on how artificial intelligence is changing new materials and rocket propulsion: atomic simulation, generative models, self-driving labs, high-temperature alloys, metal 3D printing, combustion, cooling design, and engine diagnosis and control. Written without equations, with verified sources in every chapter.
AI Library
The Age of Autonomous Scientific Discovery
Kim Kyung-jin, Attorney at Law
AI Scientists and Self-Driving Labs
This book follows how AI scientists and self-driving labs are changing the way science generates and verifies claims. It covers literature-based discovery, natural-language protocols translated into robot commands, multi-agent research systems, closed-loop laboratories, materials search, the verification gap, chains of evidence, research harnesses, journal ethics, and legal responsibility.
AI Library
A New Era of Life Sciences Opened by Artificial Intelligence
Structural Proteomics, Genomic Foundation Models, Autonomous Laboratories, and Global Governance
Kim Kyung-jin, Attorney at Law
This book is a research volume compiled with artificial intelligence. A human selected the materials and structured the work, while AI models drafted the sentences and cross-checked the facts.
AI Library
The Double Structure of Digital Sovereignty
Europe’s Departure from Palantir and the Chains of American Big Tech
Kim Kyung-jin, Attorney at Law
This is a record of 2026, when European intelligence agencies and defense ministries began removing analytics tools from America’s Palantir. It covers the replacement decisions made by France’s General Directorate for Internal Security (DGSI), Germany’s Federal Office for the Protection of the Constitution (BfV), and the Netherlands Ministry of Defense; the incident in which US export controls severed an ally’s ac…
New English Edition
Artificial Intelligence in Horticulture
Kim Kyung-jin, Attorney at Law
Across five chapters and ten sections, this book examines computer vision for crop diagnosis, harvesting robots and autonomous field systems, smart greenhouses and digital twins, precision irrigation and supply-chain quality control, high-throughput phenotyping, and predictive breeding.
New English Edition
Artificial Intelligence in Food Crop Agriculture
Kim Kyung-jin, Attorney at Law
Across six chapters and eighteen sections, the book examines digital agricultural infrastructure, remote sensing, crop diagnosis, yield forecasting, precision irrigation, genomics, molecular breeding, agricultural robotics, climate-smart agriculture, and global food security.
New English Edition
The Future of Forestry and Agroforestry
Kim Kyung-jin, Attorney at Law
Driven by Artificial Intelligence and Digital Innovation
Across five chapters and fifteen sections, the book follows satellites, drones, LiDAR, digital twins, forest-specific language models, wildfire and pest forecasting, forestry robotics, agroforestry, timber traceability, and forest carbon markets.
New English Edition
Smart Livestock Farming: AI Enters the Barn
Kim Kyung-jin, Attorney at Law
Sensors listen, cameras watch, and artificial intelligence helps farmers decide.
Across five chapters and fifteen sections, the book follows precision livestock farming from animal health and reproduction to robotic milking, virtual fencing, digital twins, methane reduction, welfare, and data ownership.
Table of Contents
Han Dong-hoon, Busan Buk-gu Gap: A Record of the 100 Days Before and After the Election (Mar. 26-Jul. 3, 2026)
Kim Kyung-jin
Table of Contents and 13 sections
From March 26 to July 3, 2026, this record follows the spring after expulsion, the Busan Buk-gu Gap by-election, victory as an independent, and the first bill submitted in the National Assembly.
Table of Contents
Artificial Intelligence and Medicine
Kim Kyung-jin, Attorney at Law
AI in clinical care, hospitals, education, and research
AI in medical imaging, risk prediction, treatment planning, hospital operations, education, and research, with patient safety, privacy, and accountability.
[AI Library] Chapter 20 Scary Error Messages: Ask AI to Read Them for You
Get 1,000% More from Your Computer with AI Agents
Chapter 20 Scary Error Messages: Ask AI to Read Them for You
Kim Kyung-jin
Introduction: One Day, the Computer Suddenly Spoke Up
On a Sunday afternoon, you were helping your child with homework. Suddenly the screen turned blue, filled with a message crammed with English letters and numbers. You saw words like KERNEL_DATA_INPAGE_ERROR. The computer restarted on its own, and the document your child had been working on vanished.
Consider another scenario: for several days, your computer has been restarting abruptly over and over without showing any warning on the screen. What on earth is going on?
Anyone experiencing this feels bewildered. But in truth, the computer had been speaking to us all along. It was simply difficult to understand because its words were composed of English, numbers, and technical code.
In this chapter, we learn how to ask an AI to read and interpret the logs left by our computers. It is not difficult: all you need to do is copy the error message and paste it to the AI.
20.1 Why Do Error Messages Look So Intimidating?
Error messages were originally created for software developers to read. Because developers are familiar with English and code, messages naturally took that shape. From a general user's standpoint, it feels like receiving a medical diagnosis written entirely in technical jargon.
However, the essence of an error message is simple: it is a report telling you where, what problem occurred, and why. It is just like an engine warning light illuminating on a car's dashboard. The warning light itself is not the problem; it is merely a signal saying, Please check here.
Therefore, the most crucial habit when encountering an error message is to stay calm and record or copy the message. Taking a photo of the screen works great too. As long as you have this message, the AI can act as your interpreter.
20.2 Event Logs: The Hidden Black Box Inside Your Computer
Airplanes have black boxes. When an accident happens, investigators open the black box to discover the cause. Computers have something very similar: the event log.
An event log is a diary the computer writes about itself. It records everything without omission: At what time which program started, At what time an error occurred, and At what time the computer shut down abnormally.
While we use our computer and even while it sleeps, event logs are continuously recorded without pause. So even in situations like my computer abruptly shut down yesterday at 3 PM and I don't know why, opening the event log reveals what happened at that exact moment.
The only hurdle is that this diary is full of English terminology and numeric codes. This is where the AI agent steps in. When you show the event log to the AI, it translates the contents into plain, accessible language.
Opening the event log differs across operating systems.
- Windows: Press Win + X simultaneously on your keyboard and select Event Viewer from the menu.
- Mac: Launch the Console app. You can type Console in Spotlight search.
- Linux: Enter the journalctl command in the terminal.
[Figure: Windows Event Viewer opening screen showing 'Windows Logs' > 'System' selected on the left and red exclamation mark (Error) entries in the center list]
20.3 Finding Why the Computer Shut Down in the Event Log
Abrupt computer shutdowns are quite common, stemming from various causes: power issues, overheating, or conflicts involving software called drivers. A driver is an interpreter program that helps computer hardware components communicate with the operating system.
The tricky part is that you see nothing on screen when power cuts out. But once the computer turns back on, the event log retains a record stating The previous system shutdown was unexpected. You simply need to give the Event ID number from this record to your AI.
Here are several representative Event IDs.
- Event ID 41 (Kernel-Power): Indicates the computer did not shut down cleanly and lost power abruptly. Causes include power supply issues, overheating, or hardware faults.
- Event ID 1001 (BugCheck): Recorded when a Blue Screen occurs, indicating the exact code number that triggered the crash.
- Event ID 6008: Notes that the previous system shutdown was unexpected.
You do not need to memorize these numbers at all; just ask your AI.
Hands-on: Asking AI to Analyze Event Logs
Caution: Reading event logs is completely safe. However, because AI recommendations might include removing drivers or changing system settings, always create a system restore point before applying modifications.
Step 1: Open Event Viewer (Win+X → Event Viewer). Step 2: In the left tree, select Windows Logs → System. Step 3: In the center list, look for red exclamation marks (Error) or yellow triangles (Warning). Step 4: Double-click an item to open its details. Step 5: Select all text in the details window (Ctrl+A) and copy it (Ctrl+C). Step 6: Paste it to the AI along with the prompt below.
Yesterday around 3:00 PM, my computer suddenly shut down. Below is the error entry copied from the Windows Event Viewer System log at that time. Please explain this content in terms a beginner can understand. Tell me which component or software caused it, and guide me through solutions ordered from lowest to highest risk.
[Paste event log content here]
→ When you enter this prompt, the AI explains what the Event ID means, lists candidate root causes, and outlines safe troubleshooting steps in order.
My computer has suddenly shut down 3 times in the past 2 weeks. Event Viewer repeatedly logs Event ID 41 (Kernel-Power). Below are the details for all 3 occurrences. Please analyze what they have in common and determine whether the issue is power supply, overheating, or drivers. Explain the reasoning behind your assessment.
[Paste 3 event log entries here]
→ The AI isolates the common thread from the recurring pattern and provides a prioritized inspection order starting from the most likely cause.
[Figure: Event Viewer details window after double-clicking Event ID 41, showing BugcheckCode, PowerButtonTimestamp, and other fields on the General tab]
Troubleshooting when things don't work: If there are too many records in Event Viewer making it hard to search, use the Filter Current Log option on the right panel. Checking only Critical and Error under Event Level filters out everything except serious problems.
20.4 Distinguishing Hardware Faults from Software Issues
When a computer develops a problem, the first question is usually: Do I need to visit a repair shop, or can I fix it myself? The heart of this question is distinguishing hardware failures from software issues.
Hardware refers to physical parts you can touch with your hands: RAM sticks, hard drives, power supply units, graphics cards, and so on. Software refers to intangible programs: operating systems, device drivers, and applications.
To use a simple analogy: if a car's engine breaks down, it is a hardware problem; if the GPS navigation app freezes, it is a software problem. An engine breakdown requires going to a mechanic, whereas a frozen app is resolved by restarting.
Computers work the exact same way. Hardware problems require swapping physical parts, while software problems are fixed by changing settings or reinstalling programs. However, judging from symptoms alone, distinguishing the two can be difficult.
For example, a sudden shutdown can stem from hardware faults (overheating, failing power supply) or software faults (driver conflicts). This is where the AI agent proves invaluable.
Clues for distinguishing the two
The table below outlines representative clues to tell hardware and software problems apart.
Suspect Hardware Problem | Suspect Software Problem
Occurrence timing: Random and without warning vs. Occurs when launching specific programs
Strange noise/smell: Present (fan noise, burning smell) vs. None
In Safe Mode: Same symptom repeats vs. Symptom disappears
Recent changes: Hardware added/replaced vs. Programs installed/updated
Event logs: WHEA, Disk errors vs. Application Error
Hands-on: Asking AI to Diagnose Hardware vs. Software
My computer repeatedly exhibits the following symptoms:
- While gaming, the screen suddenly freezes and displays a tearing visual glitch (corrupted graphics).
- 5 seconds later, the screen turns black before returning to normal.
- Display driver stopped responding is logged in Event Viewer.
Please provide a step-by-step diagnostic procedure to determine whether this is a graphics card hardware failure or a driver software issue. Format each step with branching outcomes: If result is A, suspect hardware; if result is B, suspect software.
→ The AI provides a systematic troubleshooting procedure to narrow down the cause through temperature monitoring, clean driver reinstallation, and stress testing.
Every time I turn on my computer, a S.M.A.R.T. Status Bad warning appears. Explain what this warning means.
Tell me the criteria to judge whether this is an urgent situation requiring immediate disk replacement or if I still have time. Also guide me through safely backing up data starting with the most critical files first.
→ When you enter this prompt, the AI explains the purpose of S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology) disk self-diagnostics, urgency criteria, and backup priorities.
Troubleshooting when things don't work: If you cannot copy the event log, take a photo of the error screen with your smartphone and show it to the AI. AI tools like Claude and ChatGPT can read text directly from images.
20.5 Blue Screens Are No Longer Terrifying
The Blue Screen of Death (BSOD) is the most dreaded error screen in Windows. It displays a sad-face emoticon on a light-blue background alongside messages filled with English text.
Yet the Blue Screen holds extraordinarily valuable information: the stop code. Phrases like IRQL_NOT_LESS_OR_EQUAL or KERNEL_DATA_INPAGE_ERROR serve as core clues revealing exactly why the system halted.
When a Blue Screen occurs, follow these steps:
1. Do not panic; take a photo of the stop code displayed on the screen. 2. Once the computer restarts, show the photo to the AI. 3. The AI explains what the stop code means and how to resolve it.
On Windows 10 and newer, a QR code is also displayed on the Blue Screen. Scanning this QR code with a smartphone opens a Microsoft support page. However, because explanations on that page are also highly technical, asking the AI directly is much more convenient.
When a Blue Screen happens, Windows also creates a record called a dump file. This file captures the exact state of the computer at the moment of the crash—just like black box audio from a flight recorder.
I got a Blue Screen yesterday. The stop code was KERNEL_DATA_INPAGE_ERROR, and the failed item listed ntfs.sys. Explain what this code means in plain terms a beginner can understand. Rank the likely causes (disk issue, memory issue, or something else) in order of probability, and provide inspection methods for each.
→ When you enter this prompt, the AI explains the stop code meaning (failure while reading data from disk), disk health checking methods, and memory diagnostic steps in order.
I experienced 5 Blue Screens over the past 3 months. Searching for Event ID 1001 (BugCheck) in Event Viewer returns 5 records. I will paste the 5 logs below. Analyze whether there is a common cause, and check if there is a pattern where crashes happen only while using certain programs.
[Paste 5 event logs here]
→ The AI performs a comparative analysis across all 5 crash records, identifies shared faulty drivers or modules, and points toward a clear resolution path.
[Figure: Windows Blue Screen showing a stop code at the bottom, with a smartphone taking a photo of the screen]
20.6 The Same Applies to Linux and Mac
Windows is not the only operating system that records error messages. Linux and Mac maintain their own logging systems as well. While the interfaces differ, the principle of delegating interpretation to an AI remains identical.
Checking error logs on Mac: Macs use the Console app. Search for Console in Spotlight (Command+Space). Opening Console displays system logs in chronological order. Copy entries marked Error or Fault and show them to the AI.
Checking error logs on Linux: Linux uses the journalctl command in the terminal. In particular, typing `journalctl -p err -b` filters and displays only errors that occurred since the current boot.
I am running Linux Mint. Last night my computer suddenly froze and rebooted. Below is the error log from the previous boot, obtained via the terminal command `journalctl -p err -b -1`. Interpret this content so a beginner can understand it. In particular, check whether any entries point to hardware faults.
[Paste journalctl output here]
→ The AI translates each line of the Linux system log, locating and explaining key terms such as I/O error (disk issues), GPU hang (graphics issues), or OOM (out of memory).
A message suddenly appeared on my MacBook saying Your computer restarted because of a problem. Below are the search results for the keyword panic in the Console app. Please interpret this kernel panic log, and explain whether the evidence points to an external device, internal hardware, or software.
[Paste Console app logs here]
→ The AI analyzes the Mac's kernel panic log (the Mac equivalent of a Blue Screen) and pinpoints the responsible kernel extension (kext) or hardware component.
20.7 Three Mindsets for Approaching Error Messages
To summarize what we learned in this chapter, keep these three mindsets in mind when dealing with error messages.
First: Record it. Whenever an error message appears, take a photo or copy the text. That message is the master key to solving the problem.
Second: Delegate translation. Paste the copied message to your AI and ask, Please explain what this means in simple terms. The AI translates complex English and technical codes into easily understandable language.
Third: Fix safely. Follow the solutions proposed by the AI, starting from the lowest-risk steps. Always record your current configuration before changing settings, and confirm how to revert changes beforehand.
Conclusion
Key summary
- Error messages are calls for help sent by your computer. Though intimidating in appearance, they are the most important clues for solving issues.
- Event logs are your computer's black box. Check them via Event Viewer on Windows, the Console app on Mac, and journalctl on Linux.
- Simply copying error messages or event logs and pasting them to an AI allows it to explain the problem in plain language and guide you through solutions.
- Hardware faults and software issues can be distinguished through event log keywords, occurrence patterns, and Safe Mode testing.
Copy error messages and hand them over to AI.
The AI acts as your interpreter and reveals the exact solution.