Computer locks up during certain games, event viewer included

It's one of the steps in Troubleshooting Steps for Windows 7 which by the time all are completed will normally reveal the problem. So why pick and choose?

Having half the task bar larded with startups is a Worst Practice.

Ok good news and bad news.
Good news for Company of heroes seems to no longer crash, bad news is that other games are now locking up the computer. Sigh, what do i do

MajorFoley said:

anyways if i were to do the clean boot setup with only AV what about my sound and video card drivers?

The functioning of drivers has nothing whatsoever to do with freeloader crapware being allowed to start up with Windows. Most of those are updaters which are little more than spyware building a consumer profile on your web browsing habits to sell to advertisers.

You don't need anything to start with Windows except your AV which should be lean Microsoft Security Essentials to avoid problems.

If you will let us know your progress working through each step of the tutorial we may have other steps to give you. But you'll only succeed if you are willing to do the work. Othewise take it to a shop.

Bump (sorry) but im stuck in trouble shooting steps
Im getting desperate guys, i can't play any games post 2012 anymore, it keeps locking up. Im not enabling auto hardware updates either for the simple reason that it nearly killed my computer last time and since i have 3 harddrives of different manufactures how am i supposed to scan them all.

Still stuck on step 4

Windows Update problems are one in a million. You will have other problems before that. We rely on Windows Update just like System Restore as vital functions which preserve and patch the OS reliably.

Scroll down the Administrative log as shown in the steps to see which errors repeat and then google their text and number to see how others resolve them. This is not as critical as the other steps, more housekeeping. However Critical errors should be resolved.

You should unplug all other HD's when troubleshooting long enough to see if one of them is causing the problem. If so, then plug them in one by one to see which.

While they are still connected please post back a screenshot of Disk Management - Post a Screen Capture Image

gregrocker said:

Windows Update problems are one in a million. You will have other problems before that. We rely on Windows Update just like System Restore as vital functions which preserve and patch the OS reliably.

Scroll down the Administrative log as shown in the steps to see which errors repeat and then google their text and number to see how others resolve them. This is not as critical as the other steps, more housekeeping. However Critical errors should be resolved.

You should unplug all other HD's when troubleshooting long enough to see if one of them is causing the problem. If so, then plug them in one by one to see which.

While they are still connected please post back a screenshot of Disk Management - Post a Screen Capture Image

Heres a screenshot on the disk management, im sure the current unallocated disk 1 is the ssd i just put in.

Ive also found the id error, its ID error 41
"
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

DISK1 is not even initialized yet, so you'll need to rightclick on its disk number to initialize as an MBR disk to use it, then righclick on the drive to create a partition(s) and format.

DISK3 is a Dynamic disk which is meant only to span a partition across Multiple HD's. If it's not doing that then you should Convert a Dynamic Disk to a Basic Disk. Be sure to either move the data off first or use the non-destructive method with Partition Wizard.

I always want my System drive to be in DISK0 position to avoid the System boot files from being derailed to a prior Primary Partition during any repair or reinstall. See if you can swap the data cable between DISK2 and DISK0 or change the port on mobo. Remember to take anti-static precautions before working in the case: never work on carpet, hold case before reaching inside, never touch electronics without grounding yourself by holding case.

The error you ask about is pro forma notification that you did a hard shut down. The cause may be revealed elsewhere. Focus on the repeat errors at every reboot.

gregrocker said:

DISK1 is not even initialized yet, so you'll need to rightclick on its disk number to initialize as an MBR disk to use it, then righclick on the drive to create a partition(s) and format.

DISK3 is a Dynamic disk which is meant only to span a partition across Multiple HD's. If it's not doing that then you should Convert a Dynamic Disk to a Basic Disk. Be sure to either move the data off first or use the non-destructive method with Partition Wizard.

I always want my System drive to be in DISK0 position to avoid the System boot files from being derailed to a prior Primary Partition during any repair or reinstall. See if you can swap the data cable between DISK2 and DISK0 or change the port on mobo. Remember to take anti-static precautions before working in the case: never work on carpet, hold case before reaching inside, never touch electronics without grounding yourself by holding case.

The error you ask about is pro forma notification that you did a hard shut down. The cause may be revealed elsewhere. Focus on the repeat errors at every reboot.

Disk 1 isn't initialized cos i just put it in yesterday, its the SSD which i was going to put a fresh copy of windows 7 on it.
I don't want to swap the cables of disk 2 and 0 because that would mean putting a 3gbps cable on my 6gbps hard-drive so i don't think i want to do that.

With disk 3 being dynamic, do i need to use partition wizard or could i use something like Easeus partition master or should i be safe and just use that?

Regarding to that event viewer ID, thats what keeps coming up everytime the lockup happens