Stumped.

[DarrenP]

So a customer brought in a desktop he had built himself. 

The specs are as follows: 

Intel Core i7 990X

Gigabyte G.1Killer LGA 1366

Some amount of corsair dominator ram, can't tell because of RAM cooler

Power  Color Radeon 6990

240GB Intel 530 SSD

some amount of hard drives, doesn;t matter

 

So what the computer does is it posts, goes to check RAM, and crashes. Wont boot to disk won't do anything. The odd time it boots into windows, and when you try to do anything it crashes. I originally thought a format reinstall would fix this. Well i can't even get it to boot to disk. So motherboard perhaps? 

 

Need some feedback, ASAP. 

 

Thanks guys. 

[megadarkwood]

Sounds like a RAM issue. Take off that RAM cooler and try re-seating the sticks. If that does not work, try one at a time.

[DarrenP]

Sounds like a RAM issue. Take off that RAM cooler and try re-seating the sticks. If that does not work, try one at a time.

I thought this might be it. I'll try that. 

[mopman94]

Sooo... It goes to check RAM and crashes... and you haven't even checked the RAM because you haven't removed the cooler, you don't even know what RAM it is? I think I know why you're stumped.

[kushari]

Sounds like a RAM issue. Take off that RAM cooler and try re-seating the sticks. If that does not work, try one at a time.

Exactly this, if it's not able to check ram, and when it does load windows, the second you load something into ram, it fails means that one or more sticks of ram is faulty. Check sticks one by one, and remove any bad ones.

[DarrenP]

Sooo... It goes to check RAM and crashes... and you haven't even checked the RAM because you haven't removed the cooler, you don't even know what RAM it is? I think I know why you're stumped.

Don't be a dick. The RAM check passes. That's why i had no reason to suspect RAM. It crashes shortly after RAM check. Plus the RAM is brand new. 

[mopman94]

Don't be a dick. The RAM check passes. That's why i had no reason to suspect RAM. It crashes shortly after RAM check. Plus the RAM is brand new.

It'd still be the thing I would check even if it happened shortly after. You mention a customer so I assume you work in a computer shop which is why I am slightly astonished you hadn't even looked to see what all of the components were. But hey I suppose we all do silly things sometimes.

[kushari]

Don't be a dick. The RAM check passes. That's why i had no reason to suspect RAM. It crashes shortly after RAM check. Plus the RAM is brand new. 

Doesn't matter if the ram is brand new. I'll guarantee you it's the ram. Ever heard of something called DOA (dead on arrival)? He might be being a dick, but you're also not doing your due diligence and thats why he is being a dick. Check the ram and post back.

[DarrenP]

It'd still be the thing I would check even if it happened shortly after. You mention a customer so I assume you work in a computer shop which is why I am slightly astonished you hadn't even looked to see what all of the components were. But hey I suppose we all do silly things sometimes.

You know why i didn't check what kind of RAM it is. Why bother pulling shit out unless you know with some certainty that the component you're pulling out is faulty. I don't want to pull shit out if i don't have to. It's called efficiency. The faster i can get a computer done the better. The more money is made. 

[DarrenP]

Doesn't matter if the ram is brand new. I'll guarantee you it's the ram. Ever heard of something called DOA (dead on arrival)? He might be being a dick, but you're also not doing your due diligence and thats why he is being a dick. Check the ram and post back.

It was a Stick of RAM. Thank you guys for your help.

[ViperGTX88]

I was going to suggest taking out the ram and trying it in another PC but, i see that the problem has been solved. Plz mark it as solved. 

[mopman94]

You know why i didn't check what kind of RAM it is. Why bother pulling shit out unless you know with some certainty that the component you're pulling out is faulty. I don't want to pull shit out if i don't have to. It's called efficiency. The faster i can get a computer done the better. The more money is made.

 

 

It was a Stick of RAM. Thank you guys for your help.

And that ladies and gentlemen is why I never take stuff to 'specialists' to be fixed.

I hope you learnt a lesson on being thorough. I don't apologise for being a dick because I'm fed up of people in these shops not doing a proper job because they want to make more money or they can't be bothered. You mentioned that you didn't check the ram because you didn't want to go pulling out components and wasting time when you could be making money, well look at the time you wasted here because you didn't.

[DarrenP]

 

 

And that ladies and gentlemen is why I never take stuff to 'specialists' to be fixed.

I hope you learnt a lesson on being thorough. I don't apologise for being a dick because I'm fed up of people in these shops not doing a proper job because they want to make more money or they can't be bothered. You mentioned that you didn't check the ram because you didn't want to go pulling out components and wasting time when you could be making money, well look at the time you wasted here because you didn't.

Can i explain something to you. I'm 16 Years old. I don't have the experience that you have, but what i do have is the People skills to be head technician. Which i know for a fact you don't. I may not have the prior experience, and i bet you can't fix a lot of things i can. So with that i say. Thanks and have a nice day. 

[mopman94]

Can i explain something to you. I'm 16 Years old. I don't have the experience that you have, but what i do have is the People skills to be head technician. Which i know for a fact you don't. I may not have the prior experience, and i bet you can't fix a lot of things i can. So with that i say. Thanks and have a nice day.

In that case you need to get out of that: "You know why i didn't check what kind of RAM it is. Why bother pulling shit out unless you know with some certainty that the component you're pulling out is faulty. I don't want to pull shit out if i don't have to. It's called efficiency. The faster i can get a computer done the better. The more money is made." mind set now and don't make it a habit because it will cause you to screw up bit time.

[DarrenP]

In that case you need to get out of that: "You know why i didn't check what kind of RAM it is. Why bother pulling shit out unless you know with some certainty that the component you're pulling out is faulty. I don't want to pull shit out if i don't have to. It's called efficiency. The faster i can get a computer done the better. The more money is made." mind set now and don't make it a habit because it will cause you to screw up bit time.

I haven't screwed up yet. First time i've ever had to ask a question as to why a computer wasn't working. In my 6 months of work. So i'm thinking my mentality is going pretty well for me. Efficiency is key in the business. I could have taken an hour pulling part after part out. When all i had to do was ask you guys, and you knew right away. 

 

Pretty efficient don't you think? I think yes considering it only took me what 15 minutes? 

[kushari]

Can i explain something to you. I'm 16 Years old. I don't have the experience that you have, but what i do have is the People skills to be head technician. Which i know for a fact you don't. I may not have the prior experience, and i bet you can't fix a lot of things i can. So with that i say. Thanks and have a nice day. 

Ok, settle down, he's trying to get a point accross to you, that you need to be thurough when checking a malfunctioning computer. Like he said your mindset at 16 years old is fix it quickly and move on, which you will learn quickly in IT, you can't have at all because things get complicated quickly. Many people these days can fix things thanks to google, so sorry to let you down, but that doesn't make you able to diagnose everything. Also as head technician, you need Techincal skills, its kind of in the word lol. You also do need people skills, but the way you reacted to mopman94 would suggest you don't.

[DarrenP]

Ok, settle down, he's trying to get a point accross to you, that you need to be thurough when checking a malfunctioning computer. Like he said your mindset at 16 years old is fix it quickly and move on, which you will learn quickly in IT, you can't have at all because things get complicated quickly. Many people these days can fix things thanks to google, so sorry to let you down, but that doesn't make you able to diagnose everything. Also as head technician, you need Techincal skills, its kind of in the word lol. You also do need people skills, but the way you reacted to mopman94 would suggest you don't.

I have people skills. I am frustrated at the fact he thinks he can just get away with being rude. I have technician skills. Or i wouldn't have a job. I'm done posting in this thread. Thanks for your help guys. 

[kushari]

I haven't screwed up yet. First time i've ever had to ask a question as to why a computer wasn't working. In my 6 months of work. So i'm thinking my mentality is going pretty well for me. Efficiency is key in the business. I could have taken an hour pulling part after part out. When all i had to do was ask you guys, and you knew right away. 

 

Pretty efficient don't you think? I think yes considering it only took me what 15 minutes? 

No you're wrong again, if you did this on your own, it would have been a 2 minute job. You're lucky we replied quickly, or you could have just been waiting around forever for someone to reply. If no one replied what would you have done? Check my post before this one and read it, then calm down, and learn your lesson. At 16 that's a hard thing to do, but trust me if you apply this to your way of doing things, you'll be ahead of people your age forever since most people don't at your age.

[DarrenP]

No you're wrong again, if you did this on your own, it would have been a 2 minute job. You're lucky we replied quickly, or you could have just been waiting around forever for someone to reply. If no one replied what would you have done? Check my post before this one and read it, then calm down, and learn your lesson. At 16 that's a hard thing to do, but trust me if you apply this to your way of doing things, you'll be ahead of peopel your age forever since most people don't at your age.

Thank you for your patience. I am just frustrated. 

[kushari]

Thank you for your patience. I am just frustrated. 

That's what I'm getting at, if you get frustrated easily, you'll burn out quickly in the IT industry, learn to be thurough, patient, and understanding and you'll go far. I'm just trying to mentor you as the way I saw myself when I was 16.

[mopman94]

Out of curiosity where do you work, its sort of... odd that you're head technician, you're only 16 and had to ask the internet for help with this problem, which would be fine as your 16, but is odd as your a head technician.