Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: Scary moment  (Read 2141 times)

0 Members and 1 Guest are viewing this topic.

Cafeterialoca

    Topic Starter


    Starter

    • Experience: Beginner
    • OS: Unknown
    Scary moment
    « on: July 10, 2011, 10:23:36 PM »
    Hello there.  I just had a scary moment just now.

    I'm usually a Mac guy, but lately, I have been using this PC at my parents house when I am away from the office.
    I was browsing two websites, two which I am very used to and are not pornographic, when the computer hit a blue screen of death, and the actual computer starting to make a louder and louder noise, as if it would explode or catch on fire.
    I unplugged it, and then plugged it in after a few moments, and it seems to be working fine, but I'm scared that it's damaged or worse.  Everything seems fine, but I don't know what happened.

    The sites if you must know are Comicbookresources.com and /co/.

    Please tell me that I haven't done something wrong.  :-[

    DaveLembke



      Sage
    • Thanked: 662
    • Certifications: List
    • Computer: Specs
    • Experience: Expert
    • OS: Windows 10
    Re: Scary moment
    « Reply #1 on: July 11, 2011, 01:15:34 AM »
    What did the noise sound like? Did the noise come from speakers or internal to computer case? The most common locations for scary noise are bad fans or capacitors that are leaking. Fans generally groan and can make a buzzing sound as they chatter when failing. Capacitors that are leaking that dont explode but vent gas generally make a hissing sound and you have an odor that can be smelt if the case is opened, but also generally stand out like a sore thumb on a motherboard where they have split tops or are swelled topped vs flat.

    Cafeterialoca

      Topic Starter


      Starter

      • Experience: Beginner
      • OS: Unknown
      Re: Scary moment
      « Reply #2 on: July 11, 2011, 08:54:12 AM »
      It was coming from the computer case, and was a building whirling noise, getting to very frightening loud levels.  After unplugging the computer, it stopped.

      patio

      • Moderator


      • Genius
      • Maud' Dib
      • Thanked: 1769
        • Yes
      • Experience: Beginner
      • OS: Windows 7
      Re: Scary moment
      « Reply #3 on: July 11, 2011, 08:56:31 AM »
      I would check all fans...you can stop each temporarily with a QTip....to find the culprit.
      " Anyone who goes to a psychiatrist should have his head examined. "

      Cafeterialoca

        Topic Starter


        Starter

        • Experience: Beginner
        • OS: Unknown
        Re: Scary moment
        « Reply #4 on: July 11, 2011, 12:50:16 PM »
        Thanks, I'm going to investigate now.

        BC_Programmer


          Mastermind
        • Typing is no substitute for thinking.
        • Thanked: 1140
          • Yes
          • Yes
          • BC-Programming.com
        • Certifications: List
        • Computer: Specs
        • Experience: Beginner
        • OS: Windows 11
        Re: Scary moment
        « Reply #5 on: July 11, 2011, 02:26:46 PM »
        by the way, computers don't explode. Except in movies. But everything explodes in movies.

        You mentioned a BSOD; the actual details of that BSOD might be helpful. You can get those using BlueScreenView.

        Also, when a BlueScreen occurs, naturally all software running on the machine stops. This includes the types of programs and drivers that are often preinstalled on some computers, which often includes tools for controlling fan speeds. This can result in fans throttling to 100% after a STOP error (BSOD). When a bunch throttle to 100% when you are used to hearing the fans being controlled directly by temperature (which means you normally only get a louder PC when you have it working hard) it can be unnerving. So the sound may very well be normal.

        However, Blue Screens are not- despite what you may have heard- something that is part of "everyday life" with windows. It could be indicative of a issue that it might be best to determine.

        I was trying to dereference Null Pointers before it was cool.