<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Udithasuranjith on Medium]]></title>
        <description><![CDATA[Stories by Udithasuranjith on Medium]]></description>
        <link>https://medium.com/@udithasuranjith?source=rss-0836526afcc2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Udithasuranjith on Medium</title>
            <link>https://medium.com/@udithasuranjith?source=rss-0836526afcc2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:08:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@udithasuranjith/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Computer Fundamentals: What I Learned by Actually Troubleshooting My Own Computer]]></title>
            <link>https://medium.com/@udithasuranjith/computer-fundamentals-what-i-learned-by-actually-troubleshooting-my-own-computer-7a617c5da36a?source=rss-0836526afcc2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a617c5da36a</guid>
            <category><![CDATA[computer-fundamental]]></category>
            <category><![CDATA[cpu]]></category>
            <category><![CDATA[rams]]></category>
            <category><![CDATA[troubleshooting]]></category>
            <dc:creator><![CDATA[Udithasuranjith]]></dc:creator>
            <pubDate>Wed, 09 Sep 2026 14:37:39 GMT</pubDate>
            <atom:updated>2026-09-09T14:37:39.923Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dqosuMwEfxLCGzpXj_oCJg.jpeg" /></figure><h3>My first step into IT</h3><p>I am currently working through a structured journey from beginner-level IT support toward cybersecurity.</p><p>I decided not to skip the fundamentals.</p><p>Before learning cybersecurity, networking, SOC operations, or advanced security topics, I wanted to understand what a computer actually does and, more importantly, learn how to <strong>troubleshoot problems instead of guessing</strong>.</p><p>This article documents what I learned during my first stage: <strong>Computer Fundamentals</strong>.</p><h3>1. What is a computer?</h3><p>A computer is a machine that takes information, processes it, stores information, and produces results.</p><p>The important thing I learned is that a computer is not just one component.</p><p>It is a combination of:</p><ul><li>CPU</li><li>RAM</li><li>Storage</li><li>Operating system</li><li>Applications</li><li>Other hardware and software</li></ul><p>These parts work together.</p><p>For example, when I open Microsoft Word, Word is an application. But Word doesn’t directly control the physical hardware by itself.</p><p>The operating system helps manage the communication between applications and the computer’s hardware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vn0gJdgRLGpgV8uc86eKsw.jpeg" /></figure><h3>2. CPU — the processor</h3><p>The CPU, or Central Processing Unit, is one of the main components responsible for processing instructions.</p><p>When a program needs something to be calculated or processed, the CPU performs the required operations.</p><p>A simple way I understand it is:</p><blockquote><strong>CPU = the part that does the processing work.</strong></blockquote><p>But I also learned something important during troubleshooting:</p><p><strong>A high CPU percentage doesn’t automatically mean the CPU is bad.</strong></p><p>If my computer becomes slow and CPU usage is high, I need to investigate what is using the CPU.</p><p>For example:</p><ul><li>A program may be doing heavy work.</li><li>Windows may be performing an update.</li><li>A background process may be consuming resources.</li><li>Something unusual may need further investigation.</li></ul><p>So instead of saying:</p><blockquote><em>“CPU is high, therefore I need a new CPU.”</em></blockquote><p>I should ask:</p><blockquote><strong><em>“What is using the CPU, and why?”</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SP1fQ1P7pzclcrtZoMh98w.png" /></figure><h3>3. RAM — temporary working memory</h3><p>RAM stands for Random Access Memory.</p><p>RAM is temporary working memory used by the computer while programs are running.</p><p>For example, if I open:</p><ul><li>Chrome</li><li>Microsoft Word</li><li>Spotify</li><li>Microsoft Teams</li></ul><p>these applications need RAM while they are running.</p><p>I think of RAM like a <strong>study desk</strong>.</p><p>If I have a large desk, I can keep many books and papers open at the same time.</p><p>If my desk becomes completely full, I have less space to work comfortably.</p><p>RAM works in a similar way.</p><p>The computer needs RAM to keep information available for active programs.</p><h3>4. RAM is not the same as storage</h3><p>This was one of the concepts I wanted to understand properly.</p><p>If a laptop has:</p><p><strong>8 GB RAM + 512 GB SSD</strong></p><p>that does NOT mean it has 512 GB of RAM.</p><p>The two have different purposes.</p><h3>RAM</h3><p>RAM is mainly used for <strong>temporary working data</strong> while the computer is running.</p><h3>Storage</h3><p>Storage, such as an SSD or HDD, is used to keep information for the long term.</p><p>For example:</p><ul><li>Windows</li><li>Applications</li><li>Documents</li><li>Photos</li><li>Videos</li><li>Other files</li></ul><p>remain on storage even after the computer is turned off.</p><p>My study-desk analogy helped me understand this:</p><blockquote><strong><em>RAM is like the desk where I am currently working. Storage is like the cupboard where I keep my books and files.</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OQHj45mfljsN_gFsfbcX_g.jpeg" /></figure><h3>5. Understanding computer performance</h3><p>One of the biggest lessons from this stage was that:</p><blockquote><strong><em>A slow computer does not automatically mean the hardware needs to be upgraded.</em></strong></blockquote><p>At first, it is easy to think:</p><blockquote><em>“The computer is slow → maybe I need more RAM.”</em></blockquote><p>But that is not good troubleshooting.</p><p>Instead, I learned to look at the actual evidence.</p><p>Windows Task Manager can show things such as:</p><ul><li>CPU usage</li><li>Memory usage</li><li>Disk usage</li><li>GPU usage</li></ul><p>These measurements help me investigate what is happening.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P8UMLgV5wiAFr6skKT7bqw.png" /></figure><h3>6. My first performance investigation</h3><p>I worked through several troubleshooting scenarios where the computer was slow.</p><p>For example, imagine Task Manager shows:</p><ul><li>CPU: 25%</li><li>Memory: 92%</li><li>Disk: 15%</li><li>GPU: 5%</li></ul><p>In this situation, I would not immediately blame the CPU, disk, or GPU.</p><p>The first thing that stands out is memory usage.</p><p>I would investigate which programs are using the RAM.</p><p>For example, Chrome might have many tabs open.</p><p>A browser with many tabs can consume a significant amount of memory.</p><p>But even then, I shouldn’t immediately conclude:</p><blockquote><em>“I need more RAM.”</em></blockquote><p>I should investigate first.</p><h3>7. Investigating Chrome memory usage</h3><p>One of my exercises involved Chrome using around <strong>7.2 GB of RAM</strong>, with total memory usage around <strong>94%</strong>.</p><p>Instead of immediately recommending a hardware upgrade, I would investigate:</p><ul><li>How many tabs are open?</li><li>Are all the tabs necessary?</li><li>Is one tab or process using an unusually large amount of memory?</li><li>Is another application also consuming significant RAM?</li><li>Is there a background process contributing to the high usage?</li></ul><p>I then considered closing unnecessary Chrome tabs and observing whether memory usage decreased.</p><p>This taught me an important troubleshooting habit:</p><blockquote><strong><em>Change one thing, then observe the result.</em></strong></blockquote><p>If I close unnecessary tabs and memory usage drops significantly, I have useful evidence.</p><h3>8. Don’t assume that high RAM usage means the RAM is broken</h3><p>Another scenario I worked through involved a computer with <strong>8 GB RAM</strong> and around <strong>95% memory usage</strong>.</p><p>Chrome, Teams, Word, and Spotify were running.</p><p>At first, it might look obvious that the computer needs more RAM.</p><p>But I learned to investigate before making that conclusion.</p><p>Windows itself and background processes also use memory.</p><p>So if I see several applications using RAM, I should not simply add their numbers and assume everything remaining is free.</p><p>The correct approach is to look at the overall memory situation in Task Manager and investigate what is actually causing the problem.</p><h3>9. What if closing applications doesn’t solve the problem?</h3><p>This was another important lesson.</p><p>Suppose I close unnecessary Chrome tabs.</p><p>Memory usage falls from:</p><p><strong>96% → 91%</strong></p><p>but the computer is still slow.</p><p>I should not stop troubleshooting.</p><p>I can continue investigating:</p><ul><li>Other applications</li><li>Background processes</li><li>Windows updates</li><li>Disk activity</li><li>Startup applications</li><li>Other possible causes</li></ul><p>If memory eventually falls to around 70% and the computer becomes responsive again, that gives me evidence that memory pressure contributed to the problem.</p><p>But if the computer is still slow, I continue investigating.</p><p>This is the mindset I want to develop:</p><blockquote><strong><em>Don’t stop at the first possible explanation.</em></strong></blockquote><h3>10. Disk usage and the HDD investigation</h3><p>I also worked through a scenario where:</p><ul><li>CPU: 30%</li><li>Memory: 70%</li><li>Disk: 100%</li><li>GPU: 5%</li><li>Storage: HDD</li></ul><p>The computer was taking around <strong>5–10 seconds</strong> to switch between applications.</p><p>The 100% disk usage made the HDD a reasonable suspect.</p><p>But I learned an important distinction:</p><blockquote><strong><em>100% disk usage does not automatically prove that the HDD is faulty.</em></strong></blockquote><p>I need to investigate what is causing the disk activity.</p><p>For example:</p><ul><li>Windows Update</li><li>File transfers</li><li>Background processes</li><li>Applications performing heavy disk operations</li></ul><p>could cause high disk usage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uAVjSiRrOLFwxK1VFWCvXA.jpeg" /></figure><h3>11. The Windows Update lesson</h3><p>This became one of my most useful troubleshooting examples.</p><p>I encountered a scenario where Windows Update was downloading and installing updates.</p><p>During this process:</p><p><strong>Disk usage → 100%</strong></p><p>The computer became slow.</p><p>It would have been easy to say:</p><blockquote><em>“The HDD is bad. Replace it with an SSD.”</em></blockquote><p>But instead, I investigated the activity.</p><p>After around 20 minutes, the update finished.</p><p>Then the system returned to approximately:</p><ul><li>Disk: 8%</li><li>CPU: 15%</li><li>Memory: 50%</li></ul><p>And the computer became fast and responsive again.</p><p>That changed my conclusion.</p><p>The evidence showed that Windows Update had temporarily created heavy disk activity.</p><p>I could not use that incident alone as proof that the HDD was faulty.</p><p>This taught me one of the most important lessons from this entire stage:</p><blockquote><strong><em>Don’t replace hardware until the evidence supports the conclusion.</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q1f19PFucl94WfMt-HstMw.jpeg" /></figure><h3>12. My troubleshooting method</h3><p>Through these exercises, I learned a troubleshooting process that I want to continue using throughout my IT and cybersecurity career:</p><h3>Observe → Identify → Investigate → Determine Cause → Fix → Verify</h3><h3>Observe</h3><p>Look at what is actually happening.</p><p>Example:</p><blockquote><em>The computer is slow.</em></blockquote><h3>Identify</h3><p>Find the resource or component that appears unusual.</p><p>Example:</p><blockquote><em>Disk usage is at 100%.</em></blockquote><h3>Investigate</h3><p>Find out what is causing it.</p><p>Example:</p><blockquote><em>Windows Update is downloading and installing.</em></blockquote><h3>Determine the cause</h3><p>Decide whether the evidence supports a conclusion.</p><p>Example:</p><blockquote><em>The update is temporarily causing heavy disk activity.</em></blockquote><h3>Fix</h3><p>Take the appropriate action.</p><p>Example:</p><blockquote><em>Allow the update to finish.</em></blockquote><h3>Verify</h3><p>Check whether the original problem has actually disappeared.</p><p>Example:</p><blockquote><em>Disk usage returns to normal and the computer becomes responsive.</em></blockquote><p>This is much better than simply guessing.</p><h3>13. The difference between an application and an operating system</h3><p>Another fundamental concept I learned is the difference between an <strong>operating system</strong> and an <strong>application</strong>.</p><h3>Operating system</h3><p>Examples:</p><ul><li>Windows</li><li>Linux</li><li>macOS</li></ul><p>The operating system manages important parts of the computer, including hardware, files, applications, users, and permissions.</p><h3>Application</h3><p>Examples:</p><ul><li>Microsoft Word</li><li>Google Chrome</li><li>Spotify</li></ul><p>An application is software designed to perform a particular task for the user.</p><p>For example:</p><blockquote><strong><em>Windows = operating system</em></strong></blockquote><blockquote><strong><em>Microsoft Word = application</em></strong></blockquote><p>Word runs on the operating system.</p><p>I think of the operating system as the layer that helps applications work with the computer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-P07gqkiSA-aPq2dNCq40w.jpeg" /></figure><h3>14. Why applications need the operating system</h3><p>I originally thought about this as applications needing some way to communicate with the hardware.</p><p>For example, Microsoft Word needs to:</p><ul><li>use memory</li><li>access files</li><li>display information</li><li>interact with the computer</li></ul><p>Word doesn’t simply take direct control of the physical hardware.</p><p>The operating system provides services and manages access to those resources.</p><p>So the basic relationship I understand now is:</p><p><strong>Application → Operating System → Hardware</strong></p><p>This relationship is fundamental to understanding computers.</p><h3>15. What is virtualization?</h3><p>I also learned about <strong>virtualization</strong>.</p><p>At first, I thought a virtual machine was basically a remote computer.</p><p>That wasn’t correct.</p><p>A virtual machine, or VM, is a computer environment created using software that runs on a physical computer.</p><p>For example, my physical laptop could have:</p><p><strong>16 GB RAM</strong></p><p>I could configure an Ubuntu virtual machine with:</p><ul><li>4 GB RAM</li><li>2 CPU cores</li><li>50 GB virtual disk</li></ul><p>The VM uses resources from my physical computer.</p><p>The 50 GB virtual disk is not necessarily another physical 50 GB drive. It is storage allocated from the existing physical storage.</p><p>When the VM is shut down, the RAM assigned to that VM becomes available to the host computer again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VH8bM1SqQbY8uOpJrtaMhQ.jpeg" /></figure><h3>16. Why virtualization is important for IT and cybersecurity</h3><p>Virtual machines are extremely useful for learning.</p><p>Instead of experimenting directly on my main operating system, I can create a separate environment.</p><p>For example, I can eventually use virtual machines to practice:</p><ul><li>Linux</li><li>Windows administration</li><li>Networking</li><li>Security tools</li><li>Logs</li><li>Services</li><li>Troubleshooting</li></ul><p>This will become especially useful as I move toward cybersecurity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tnWwo97hPR9lM4_ejNG5Ew.jpeg" /></figure><h3>17. Task Manager became one of my first troubleshooting tools</h3><p>Windows Task Manager became an important tool during this stage.</p><p>It lets me observe what the computer is doing.</p><p>I can look at:</p><ul><li>CPU</li><li>Memory</li><li>Disk</li><li>GPU</li><li>Processes</li><li>Startup applications</li></ul><p>This helped me move away from guessing.</p><p>Instead of:</p><blockquote><em>“The computer is slow.”</em></blockquote><p>I can start asking:</p><blockquote><em>“What resource is under pressure?”</em></blockquote><p>Then:</p><blockquote><em>“Which process is causing it?”</em></blockquote><p>Then:</p><blockquote><em>“Why is that process using the resource?”</em></blockquote><p>That’s a much more useful way to troubleshoot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VXzdgO7IjsCV00pecogXUA.png" /></figure><h3>18. What I learned about troubleshooting</h3><p>The biggest lesson from Computer Fundamentals wasn’t actually about CPU, RAM, or storage.</p><p>It was about <strong>how to think</strong>.</p><p>When something goes wrong, I should not immediately jump to a solution.</p><p>For example:</p><h3>Bad troubleshooting</h3><blockquote><em>Computer is slow → buy more RAM.</em></blockquote><h3>Better troubleshooting</h3><blockquote><em>Computer is slow → check Task Manager → identify high resource usage → investigate the process → determine the cause → fix it → verify performance.</em></blockquote><p>The second approach uses evidence.</p><p>That is the approach I want to carry into every future stage of IT and cybersecurity.</p><h3>19. What I know now</h3><p>After completing this stage, I can explain and work with the following concepts:</p><ul><li>What a computer is</li><li>CPU</li><li>RAM</li><li>Storage</li><li>RAM vs storage</li><li>Operating systems</li><li>Applications</li><li>Hardware and software relationships</li><li>Virtualization</li><li>Virtual machines</li><li>Task Manager</li><li>CPU, memory, disk and GPU usage</li><li>Basic performance troubleshooting</li><li>Evidence-based troubleshooting</li><li>Hypothesis and testing</li><li>Verification after making a change</li></ul><p>More importantly, I have actually practiced troubleshooting scenarios instead of only reading definitions.</p><h3>20. What I still need to improve</h3><p>I am still at the beginning of my IT journey.</p><p>Understanding computer fundamentals doesn’t mean I know everything about computers.</p><p>There is much more to learn, including:</p><ul><li>Windows administration</li><li>Linux</li><li>Networking</li><li>Security fundamentals</li><li>PowerShell</li><li>Bash</li><li>Python</li><li>System logs</li><li>Services</li><li>User permissions</li><li>Troubleshooting</li><li>Cybersecurity</li></ul><p>That is why I am continuing step by step rather than trying to skip directly into advanced cybersecurity.</p><h3>21. My biggest takeaway</h3><p>If I had to summarize this entire stage in one sentence, it would be:</p><blockquote><strong><em>Good IT troubleshooting is not about guessing the answer quickly; it is about collecting evidence, testing a reasonable explanation, fixing the actual cause, and verifying the result.</em></strong></blockquote><p>That is the mindset I want to build before moving deeper into IT and cybersecurity.</p><h3>What’s next?</h3><p>My next stage is <strong>Windows Fundamentals</strong>.</p><p>I will learn and practice:</p><ul><li>Windows users and accounts</li><li>Standard users vs administrators</li><li>Groups</li><li>Permissions</li><li>Services</li><li>Processes</li><li>Windows Event Logs</li><li>Basic Windows troubleshooting</li></ul><p>I won’t just read about these topics.</p><p>I will create test users, change permissions in a safe lab, test what those users can and cannot do, investigate unexpected results, and document what I learn.</p><p>The goal is simple:</p><blockquote><strong><em>Learn it. Practice it. Break it safely. Troubleshoot it. Verify it. Explain it.</em></strong></blockquote><p>That is how I want to build my IT foundation before moving into cybersecurity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a617c5da36a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>