Computer Freezes and Display Disconnecting

Hello!

I went to the malware remover forum and the responder told me to come here next. I have connected two screenshots because the computer I am dealing with isn't responding enough to copy and paste the spec information.

About two weeks ago the computer had failed to boot up so I ran a start up repair and ended up having to do a restore point on it. I didn't think much of it because my laptop, which also runs Windows 7, had the same issue, so I thought it was a glitch with the newest update.

However, my desktop continued to have boot up errors for a couple more days and then ran fine. I was away from the house for about a week and came back to find it in an infinite repair loop. During these failed repairs, the display on my monitor would randomly disconnect. The monitor would say to check the cable and then would go black, my desktop would still be running. I checked the wires and the slots and they all look fine. When this happened, I would hear three beeps from the desktop if I let it keep running.

I got the boot up repaired and thought that was the end of it until my computer began to freeze. My mouse would still be responsive but nothing on the screen would do anything. Sometimes it would stay the cursor shape and other times the loading wheel, if this matters at all.

This seemed to happen quicker when connected to the internet, but I discovered it was still doing it when I completely removed the network cable. I cannot find the trigger for these issues as it froze during the malware scans, the Belarc Advisor scans, and when I was on a browser. Being on a browser seems to make it freeze faster, though? Especially since I was messing around in Adobe Photoshop to save the screenshots and it was acting like everything was okay. However, when I went to play a simple in browser game to test it froze within five minutes.

The display hasn't been disconnecting nearly as much as before when doing the boot repairs, but it still happens.

Please note that this computer was built by amateurs and upheld by amateurs, me included haha, and it is probably put together with the computer equivalent of gum and tape. Thank you for any help or suggestions!

 

Sorry, looks like I didn't do the attachment right the first time. Here are the screenshots.

 

When you say "I got the boot up repaired" what exactly are you talking about?
What sort of problem presented itself that needed fixing?
How did you fix it?

You have barely enough RAM to run Windows 7 64-bit. I'm surprised that you can even load PhotoShop. If one of your RAM sticks has gone bad, that would definitely give you screen lockups.

If you have one, place your Windows 7 Repair Disk in your CD/DVD drive and reboot. Run the Windows Memory Diagnostics tool to test your installed RAM.

If you haven't yet created a Repair Disk you can do so as follows:
Open Control Panel and click on Backup and Restore
Click on Create a system repair disk from the menu on the left
Choose your CD/DVD drive
Place a blank CD in the drive
Click Create disk button

 

Hello! Sorry I was unclear. When I was having boot-up issues, the computer would freeze on the Windows logo. When I reset the computer, it would offer to a do a boot-up repair. During the repair the display would fail and I would have to try again. When the repair did complete, it said the repair failed. I followed these instructions to fix it:

http://www.sevenforums.com/tutorials/139576-startup-repair-infinite-loop-recovery.html

My computer now boots up just fine and normally.

I have been using Windows 7 Home Premium 64 Bit for about a year now without changing the RAM, give or take a few months. During that time Photoshop, browsing, games, etc. have been running without issues. I've never had issues with it before. The new installation displayed on the screenshot is from a hard drive failure. The replacement hard drive was a replacement from the company and is the same exact type I have been using.

The Windows Memory Diagnostics ran cleanly and when I logged back on it gave me the notification no memory issues were found.