No VGA beep code sometimes

[Daniel256612]

Hi Guys,

This is an extremely weird case.

In 2012, I build a PC which has been fine up until the point where I recently moved houses.
I've set up the PC at my new house about 1 month ago and started playing games which then it became frozen while I was playing a game. Naturally I think, windows or something else running has crashed, I'll just restart and continue playing. I restart he PC and gave 1 short beep and 3 long beeps, which is the no VGA detected beep code on Asus's motherboards. At this point I thought my graphics card has shit itself, so I started troubleshooting.

I take the graphics card out of the PCI slot and re-sit it. I restart and it boots and I'm able to play again. After 1 hour its frozen again. I restart, get the beep code error, re-sit the GPU and then continue playing. It freezes again, I re-sit the card again, but this time, it still doesn't boot. I leave the PC off for an hour and then return and it boots.

Fast forward 1 month without touching the PC (I was extremely busy), the PC gets past the NO vga beep code SOMETIMES and other times even after its not powered on for a week it'll give the beep code.
When the PC has gotten past the beep code, I've ran stability tests on the GPU and CPU for an hour and its all fine, temps and performance are where they should be, which throws me off thinking its either the GPU or CPU.

How can I stop this computer from randomly crashing and then giving the beep code as well as getting past the beep code sometimes? Does anyone have any idea or experience with what part could be causing this issue?

I've tried:
-Other 3 PCI slots
-Re-sitting RAM
-Different power pins from PSU
-Disconnecting all power cables and reconnecting

I don't have another PC to test the GPU in, which is very unfortunate. 
 



Motherboard: Asus Rampage IV Extreme
GPU: Asus Nvidia GTX 770
CPU: Intel i7 3820
RAM: 16gb corsair vengeance DDR3
CPU Cooler: Noctua DH-14
PSU: Antec 900w

No parts have been changed, except for the GPU which was bought new in 2014 and replaced from a GTX 660.

Any help would be greatly appreciated, thanks.

[digitaldoughnut]

47 minutes ago, Daniel256612 said:

Hi Guys,

This is an extremely weird case.

In 2012, I build a PC which has been fine up until the point where I recently moved houses.
I've set up the PC at my new house about 1 month ago and started playing games which then it became frozen while I was playing a game. Naturally I think, windows or something else running has crashed, I'll just restart and continue playing. I restart he PC and gave 1 short beep and 3 long beeps, which is the no VGA detected beep code on Asus's motherboards. At this point I thought my graphics card has shit itself, so I started troubleshooting.

I take the graphics card out of the PCI slot and re-sit it. I restart and it boots and I'm able to play again. After 1 hour its frozen again. I restart, get the beep code error, re-sit the GPU and then continue playing. It freezes again, I re-sit the card again, but this time, it still doesn't boot. I leave the PC off for an hour and then return and it boots.

Fast forward 1 month without touching the PC (I was extremely busy), the PC gets past the NO vga beep code SOMETIMES and other times even after its not powered on for a week it'll give the beep code.
When the PC has gotten past the beep code, I've ran stability tests on the GPU and CPU for an hour and its all fine, temps and performance are where they should be, which throws me off thinking its either the GPU or CPU.

How can I stop this computer from randomly crashing and then giving the beep code as well as getting past the beep code sometimes? Does anyone have any idea or experience with what part could be causing this issue?

I've tried:
-Other 3 PCI slots
-Re-sitting RAM
-Different power pins from PSU
-Disconnecting all power cables and reconnecting

I don't have another PC to test the GPU in, which is very unfortunate. 
 



Motherboard: Asus Rampage IV Extreme
GPU: Asus Nvidia GTX 770
CPU: Intel i7 3820
RAM: 16gb corsair vengeance DDR3
CPU Cooler: Noctua DH-14
PSU: Antec 900w

No parts have been changed, except for the GPU which was bought new in 2014 and replaced from a GTX 660.

Any help would be greatly appreciated, thanks.

Try using a different GPU and PSU  (do you still have your GTX 660?)

If you change the gpu or psu dont change both components at once, i would probably start with the gpu as it is a bit easier. 

have you installed any new major windows/driver updates? 

hope this helps 

[Daniel256612]

2 hours ago, digitaldoughnut said:

Try using a different GPU and PSU  (do you still have your GTX 660?)

If you change the gpu or psu dont change both components at once, i would probably start with the gpu as it is a bit easier. 

have you installed any new major windows/driver updates? 

hope this helps 

Hey

 

Thanks for your response!

 

Nope, haven’t installed any major driver/windows updates prior to the error starting to occur.

Dont have my GTX 660, it was sold.

 

Would resetting cmos have any impact or could I perhaps have a corrupt bios ?

 

Thanks

[Daniel256612]

Does anyone know if this could be the result of a faulty power cable to the PSU? I think the last one was faulty, I replaced it and the error has not occurred yet. I don’t have much confidence it won’t happen again, but I guess we’ll see. 

[digitaldoughnut]

12 hours ago, Daniel256612 said:

Hey

 

Thanks for your response!

 

Nope, haven’t installed any major driver/windows updates prior to the error starting to occur.

Dont have my GTX 660, it was sold.

 

Would resetting cmos have any impact or could I perhaps have a corrupt bios ?

 

Thanks

I don't think that you have a corrupt bios, you could try to reset cmos and see what happens. It could be the power cable to the psu, see if it still happens. The thing with troubleshooting an issue is that you have to try everything . Try also booting with one stick of ram and try different ram slots and sticks if the error still occurs, ram can give very strange issues sometimes. Good Luck  

[digitaldoughnut]

Also try to run the following command in an elevated (administrator) command prompt window:

 

sfc /scannow

 

 

 

 

[Daniel256612]

6 hours ago, digitaldoughnut said:

Also try to run the following command in an elevated (administrator) command prompt window:

 

sfc /scannow

 

 

 

 

Thanks for the response.

 

The error did happen before I was in Windows, but I’ll give the command a try just to see if there is potentially any issues with the OS. I’ll start it up with the old PSU power cable and see if the error occurs again.

 

Thanks so much for your help, will let you know how it goes!

[digitaldoughnut]

On 28/05/2018 at 10:12 PM, Daniel256612 said:

Thanks for the response.

 

The error did happen before I was in Windows, but I’ll give the command a try just to see if there is potentially any issues with the OS. I’ll start it up with the old PSU power cable and see if the error occurs again.

 

Thanks so much for your help, will let you know how it goes!

Brilliant, sorry for the slow response. Any luck?