Problem with computer

Associate
Joined
20 Sep 2011
Posts
144
Location
Wales
Well the screen starting flashing black for a few seconds the other day and I just thought it was my dodgy HDMI cable, but then a few days later playing a game the screen just went black and "No Signal" came up on to the screen. So I turned the computer off and tried to turn it back on but it still said "No Signal" and there was a normal POST beep followed by two short beeps after each other.

So I took the jumper off and put it on the other pins and back to reset it and this will work sometimes but then I have to reset the time and date every time and it gets annoying and it only works sometimes.

Also the PSU makes a whiney noise when on and off but it is more noticeable when off. (don't know whether this is normal or not?)
 
Obvious question, what is the spec of the PC, in particular the brand and spec of the power supply, whiney noises make me suspicious of rubbish PSUs.
 
Corsair make reasonably PSU's, but it may be worth, if you've got another PSU, doing a swap a out and see what happens, as DazQ87 said I would be suspicious of the PSU in that situation too
 
Last edited:
Nope I don't have another PSU to test and I've had this setup for just under a year now and it hasn't had any problems and nothing is overclocked.
 
It could be your graphics card try taking the card out of the system and use the onboard graphics to see if it posts. Obviously you wont be able to play games with onboard but you can see if it posts.
 
Yeah it works with no graphics card, but it does work sometimes with the graphics card so it could be the psu or the graphics card.
 
Looking up the beep codes for your motherboard I have found the following:

On the AMI bios (which im pretty sure your board has) 2 beeps indicates:

"2 beeps - Parity error - bad memory"

(taken from http://forum-en.msi.com/faq/article/bios-beep-codes)

If this is the case dont panic, you can check RAM faults easily just by running Memtest86, this will be a good inicator if there are any errors.
 
I ran memtest for 2 hours and this is what I had.

vfxox5.jpg


I don't know what it means but I can see there is an error.
 
pretty much, just run memtest on each stick individually (take one stick out and run with just one) to work out which one it is.
 
Back
Top Bottom