Computer Issues

  • Guest, it's time once again for the massively important and exciting FoH Asshat Tournament!



    Go here and give us your nominations!
    Who's been the biggest Asshat in the last year? Give us your worst ones!

Noodleface

A Mod Real Quick
38,275
15,106
Do you have a wireless nic? Could always check if that solves it, that would confirm the cable before ripping it out.
 

Palum

what Suineg set it to
26,543
41,334
When looking around with people having similar issues, someone also mentioned the ethernet cable and replaced it to fix it. Which is unfortunate because i'll have to run a long one through those pain in the ass spots again. But I wouldn't be surprised if it was the problem. the cable is probably close to 10 years old. With two people suggesting that, im gonna start there before changing NICS etc. Because this was also happening on my old system. This build is only just a year old now.
Before you re-run if you have extra RJ-45s and some crimpers recrimp the ends.

Also to Noodle's suggestion, if you have a cheapo USB wifi that would at least eliminate the cable modem if it works fine.
 

Frenzied Wombat

Potato del Grande
14,730
31,803
When looking around with people having similar issues, someone also mentioned the ethernet cable and replaced it to fix it. Which is unfortunate because i'll have to run a long one through those pain in the ass spots again. But I wouldn't be surprised if it was the problem. the cable is probably close to 10 years old. With two people suggesting that, im gonna start there before changing NICS etc. Because this was also happening on my old system. This build is only just a year old now.
The hiccups while playing games in tandem with a ping -t that never drops is a hallmark sign that your router sucks when put under load. It's very unlikely that it's your cable unless you can spot a specific crimp or other damage to the cable. Without physical damage to the cable itself, I've maybe seen two cat5 "bad cables" in my 20 years of IT. My suggestion is to try a better router, or even bypass it entirely and connect right to your cable modem for testing.
 

Tarisk

Pathetic Reaction Bot
1,568
370
The hiccups while playing games in tandem with a ping -t that never drops is a hallmark sign that your router sucks when put under load. It's very unlikely that it's your cable unless you can spot a specific crimp or other damage to the cable. Without physical damage to the cable itself, I've maybe seen two cat5 "bad cables" in my 20 years of IT. My suggestion is to try a better router, or even bypass it entirely and connect right to your cable modem for testing.
I guess it was overlooked but I will repeat that I was going directly to the modern and it still occurs.

But a good point was made that if it was the cable the whole connection would shit out and not just two programs.

Also doesn't happen on other pc's in the house. I've started running mumble off my laptop and it won't drop when wow does on the main rig. That's why I'm wondering if it's software or nic/nic configuration
 

Noodleface

A Mod Real Quick
38,275
15,106
what is your nic configuration? YOu said multiple so I assume you're doing something different than the standard user
 

Tarisk

Pathetic Reaction Bot
1,568
370
what is your nic configuration? YOu said multiple so I assume you're doing something different than the standard user
Nothing special, just standard realtek onboard gigabit. Only one nic in it too.

I'm honestly starting to think it's related more to something out of my control than anything. Comcast or line quality elsewhere. I've been on the last few hours and not a single drop. Assuming I don't jinx it anyway.

And thanks for the link to the cable tester, etc. Lanx. I wanted to get a set anyway.

Edit/update:

Yeah, more signs pointing to it being Comcast. Seems to get worse when peak hours start approaching. Plus there's been a lot of fiber installations in the neighborhood going on, which im going to be glad when i can get it and away from comcast.
 

Armadon

<Bronze Donator>
3,699
6,712
Ok have a major issue. My computer locked up last night and I had to do a hard reset. when I turned it back on is when all the issues started. At first it would start to boot for about 3 seconds and then shut itself off and boot again for another 3 seconds doing this over and over. Hit the reset button on my mother board and tried again. This time it would do the same thing but every 10 seconds. Hit the reset button again. This time it didn't reset but I didn't get any video so I have no idea what happened. Switched the bios on my mother board to see if that was wrong but the same scenario played itself out again. I have a rampage black 4 mother board, 4790k processor, 32gigs of ram, and titan x. I have no idea what to do and I'm hoping I don't have to replace anything. Please help. Thank you guys.
 

Noodleface

A Mod Real Quick
38,275
15,106
Pop the CMOS battery for about 90s (I don't know the recommended time) then put it back in - same issue?

Remove all but 1 RAM stick, remove video cards if onboard is available, unplug unnecesary drives/cards/etc. Same issue?

Power supply could also be to blame, is it blinking or anything?
 

Armadon

<Bronze Donator>
3,699
6,712
I will have to check when i get home but power supply doesnt blink and i dont have integrated graphics. Ill try the cmos battery and ram though when i get a chance. Thanks noodle.
 

Armadon

<Bronze Donator>
3,699
6,712
Ok tried unplugging all items and testing each one, one by one, and it all does the same things. Was wondering if it was the psu but all the fans are functioning even the ones on the video card. I havent been this stumped before trying to fix my computer.
 

Palum

what Suineg set it to
26,543
41,334
Ok tried unplugging all items and testing each one, one by one, and it all does the same things. Was wondering if it was the psu but all the fans are functioning even the ones on the video card. I havent been this stumped before trying to fix my computer.
If you have a multimeter test the PSU, otherwise it just has all the hallmarks of a mobo failure.

If you don't have a multimeter, go buy a PSU at bestbuy or whatever, swap it out and if it still doesn't work just return it.
 

Lanx

<Prior Amod>
65,316
147,291
Fuck i was thinking mobo but i was in denial. Going to try new psu but fucking a
Don't forget touch tests, touch your psu when it's on, is it hot enough to cook an egg? your psu fan might be busted, check to see it's physically turning, put hand over fan etc. Same w/ cpu, maybe your heatsink paste just dried the fuck up or something, make sure you still have good connection w/ heatsink/cpu, also make sure all fans spin.

Had this happen to a friend we could figure out whats wrong so i just looked at it, as it turned on. Then it just felt too hot near the psu, then noticed fan didn't spin. (looked like ball bearing was jacked), just opened it up and solder'd on a 120m fan (it was solder'd to the board).
 

Armadon

<Bronze Donator>
3,699
6,712
Psu fan runs and its running at normal temp. I have the rog connect and the temp on the cpu is 23 to 25 degrees celsius. It just doesnt boot it seems like. The mobo has codes on it that just cycle. When i looked up the codes its all about initializing the boot up process and it just keeps cycling them over and over.
 

Armadon

<Bronze Donator>
3,699
6,712
Ok here we go with code numbers 14 pre memory CPU initialization is started 17 pre memory system agent initialization is started 19 pre memory PCH initialization is started. Now it will restart most of the time after these three unless I do a reset and then it will sometimes boot to these next codes. 60 DXE core is started 61 NVram initialization. It will restart after these after another reset It will get to these last 2 codes. 67 CPU DXE initialization is started 69 system agent DXE initialization is started. If I get to those the computer wont restart but it cycles every code over and over until I do a reset.
 

Noodleface

A Mod Real Quick
38,275
15,106
That's for sure gotta be cpu or motherboard I'd imagine. If it's dying on the pch init that is no good at all. The fact that is sometimes makes it to the DXE phase is puzzling, but I guess that doesn't matter. Dying in the PEI phase like that is way before any other devices come up, I'd say cpu or mobo. I almost want to lean towards cpu but it's tough to tell
 

Jysin

Ahn'Qiraj Raider
6,457
4,345
CPUs are nearly bulletproof these days. I would lean far towards MB first. They are probably 100x more commonly faulty vs a CPU.