I slapped my PC, might have broke it?

[hex4]

My computer was doing an annoying noise so i gave it a swift slap to shut it up which worked, i did it as i was loading up CSGO, and the game did not launch, it stayed on a blank screen, i then attempted to CTRL+ALT+DEL and it BSOD in a very low resolution which i found odd.

Anyway turned PC on, kept freezing at bios, ok cool.

Reset it then it said no operating system found.

Reset then it said something to do with disk read error, so i unplugged my DVD drivers.

Reset then it said Overclock failed, pres yabba dabba doo to use basic mobo settings, i ignored it and reset the PC again, this time it boots normally and i'm here typing.

 

 

WTF happened?

[Joegeddon]

I think you've killed your hard drive.

[Imaginary Friend]

Well that's wierd  

[hex4]

1 minute ago, Joegeddon said:

I think you've killed your hard drive.

It's booted fine, the OS is on the HDD and i'm here on it right now lol.

[Darel321]

gz

[don_svetlio]

RiP HDD

[Nena Trinity]

2 minutes ago, Joegeddon said:

I think you've killed your hard drive.

I vote for this to!

1 minute ago, don_svetlio said:

RiP HDD

I did that to a Laptop once! (how to kill HDD, transport in car without turning it off...)

[hex4]

No clicking noises from HDD either, maybe i caused it to skip or something?

[vorticalbox]

I had this when i hit my pc with a box by mistake. system locked up and blue screened was fine after a reboot

[Energycore]

7 minutes ago, hex4 said:

My computer was doing an annoying noise so i gave it a swift slap to shut it up which worked, i did it as i was loading up CSGO, and the game did not launch, it stayed on a blank screen, i then attempted to CTRL+ALT+DEL and it BSOD in a very low resolution which i found odd.

Anyway turned PC on, kept freezing at bios, ok cool.

Reset it then it said no operating system found.

Resest then it said something to do with disk read error, so i unplugged my DVD drivers.

Resrt then it said Overclock failed, pres yabba dabba doo to use basic mobo settings, i ignored it and reset the PC again, this time it boots normally and i'm here typing.

 

 

WTF happened?

Probably disconnected the GPU or a stick of RAM when you hit it

 

Try disassembling and reassembling if it persists

[hex4]

Well CSGO just launched fine, i think i got lucky, won't do that again.

 

Stroking PC now, poor baby i'm sorry.

[Energycore]

2 minutes ago, hex4 said:

Well CSGO just launched fine, i think i got lucky, won't do that again.

 

Stroking PC now, poor baby i'm sorry.

Please don't abuse your PC

[suchamoneypit]

Its not a good idea to physically abuse your PC. Verbal abuse usually sets it straight.

[Kaita]

Not cool man , not cool. Don't abuse your PC it has feelings

[Maslofski]

if it does funny noises play around with screws, that generally fixes it for me without needing to resort to the peoples elbow

[hex4]

Yeah i mean to me it was not a hard slap but it did give it a good shunt, need to remember i'm 6ft and 185 pounds in weight

[Rodinski]

It's fighting back and won't work until you apologize. Sometimes computers can be sensitive. Be nice! 

 

In all seriousness, sounds like your goofed the HDD. 

[hex4]

You know sometimes you just do things in teh heat of the moment? well let us all remember now and today, computers do not like abuse, they will fight back!

 

[GoodBytes]

HDDs are sensitive to vibrations.

Here is a super old video showing the issue

 

In your case, your computer noise was probably your HDD starting to fail already. The beauty of HDDs unlike an SSD, is that you usually have a warning sign of failure before it actually failed. So, instead in trying to backup your stuff before it actually failed when you heard the noise, you hit the system, and now the drive actually failed.

 

Drive failure doesn't necessarily means that the entire drive is not working, but that the head crashed on the disk plates (something that does happen, due to the closeness of the drive head to the disk platters). Basically, a section if your HDD is now non functional. The HDD has a system in place to detect faulty sections of the disk, and ignore those section, and will never be used. So, if you re-install your system, it might work again (assuming that the issue is not mechanical, like the motor broke or something), but I would no longer trust the HDD.

 

This is how close your HDD head is from the disk:

 

It looks like it is touching but it is not. It is actually closer to the disk than the thickness of a dust particle or smoke particle. That is why HDDs are nicely closed up, air tight, and the moment you open an HDD, the drive goes at the bin, because dust went in, and the moment you power it up, the head will jam on dust, or particles that might have collected inside.

[hex4]

7 minutes ago, GoodBytes said:

HDDs are sensitive to vibrations.

Here is a super old video showing the issue

 

In your case, your computer noise was probably your HDD starting to fail already. The beauty of HDDs unlike SSD, is that you usually have a warning sign of failure before it actually failed. So instead in trying to backup your stuff before it actually failed, you hit the system, and now the drive actually failed.

 

Drive failure doesn't necessarily means that the entire drive is not working, but that the head crashed on the disk plates (something that does happen, due to the closeness of the drive head to the disk platters).

 

This is how close your HDD head is from the disk:

 

 

It looks like it is touching, but it is actually closer to the disk than the thickness of a dust particle or smoke particle. That is why HDDs are nicely closed up, and the moment you open an HDD, the drive goes at the bin, because dust went in, and the moment you power ti up, the head will jam on dust.

The noise was vibration from the HDD's i have 4, just that i acted stupid and slapped it instead of just retightening some screwes etc, i have learnt my lesson and signatured it.

Edited June 12, 2016 by GoodBytes
Removed image and video from quote

[hex4]

I have checked my HDD's health, the one that caused the BSOD, it seems to be fine, do note they are not all in RAID-0 no longer.

 

 

One of my other drivers are on caution and that's reallocated sectors count which is nothing to do with this, some drives do have higher numbers for some reason.

 

 

[PlayStation 2]

52 minutes ago, Nena360 said:

I vote for this to!

I did that to a Laptop once! (how to kill HDD, transport in car without turning it off...)

My laptop went through fucking hell with me. Now its hard drive is sitting in my brother's rig so that's more than likely not the issue.

[GoodBytes]

4 minutes ago, hex4 said:

The noise was vibration from the HDD's i have 4, just that i acted stupid and slapped it instead of just retightening some screwes etc, i have learnt my lesson and signatured it.

In the future, you should get a case, with HDD vibration absorbing mounts. It helps protect the HDD against not expected vibrations, and it drastically cuts HDD noise.

They are variety of variation of the system available, but usually it consists of a rubber or silicon cylinder with a hole to pass the screw.

 

Something like this:

 

The black tray is from the case, that varies between case designs. The white rubber is the cylinder vibration absorbing mounts.

[hex4]

1 minute ago, GoodBytes said:

In the future, you should get a case, with HDD vibration absorbing mounts. It helps protect the HDD against not expected vibrations, and it drastically cuts HDD noise.

They are variety of variation of the system available, but usually it consists of a rubber or silicon cylinder with a hole to pass the screw.

 

Something like this:

 

The black tray is from the case, that varies between case designs. The white rubber is the cylinder vibration absorbing mounts.

Cool i think i will invest in some of these for sure

 

Thanks.

[Sauron]

1 hour ago, hex4 said:

WTF happened?

You forgot the basics of common sense...

11 minutes ago, hex4 said:

I have checked my HDD's health, the one that caused the BSOD, it seems to be fine, do note they are not all in RAID-0 no longer.

My theory is that the hit pulled the sata cable slightly out and unplugging a hdd in a running raid 0 setup is a recipe for disaster.