Computer Crashing

[Hidan]

As the title says, my computer as of late has begun to crash repeatedly. This used to happen before and I was able to link it to the Graphics Card overheating after a while based on what was happening, and I changed Graphics cards to a lower end so it won't use as much power and dusted out my whole computer, but at this point I'm unable to tell what is actually occurring. What happens is I could be playing a game and all of a sudden, the computer shuts off. It turns itself off and then pretty much restarts. When it is restarting it doesn't say whether or not there was a problem. There are no error messages - it just simply shuts off.

A little information on my computer:

Graphics Card Drivers are Updated.

Vista 32- Bit
AMD Phenom(tm) 9600 Quad-Core Processor ~2.3 GHZ
About 4GB RAM
Radeon x1650 Series

So could guys please help me? Thanks.
Post if you need more information about the specs of my computer.

 

[The Slayer]

i had the same problem. Try to run 'memtest 86'. There might be a mem module broken. Also, what games are u trying to play? if it is something like black ops, that required 2 gig ram, then it might be because u don't have enough memory.

Also, add me on steam: ukdestroyer. I might be able to help u more.

 

[K^^]

Also, the overheating might of not been totally the GFcard's fault.
It might very well be that your system in whole has poor cooling, a.k.a. underperforming fans


-K

 

[Ric]

Hello.

Please perform the following:
1) Hit Windows Key and R at the same time, should bring up a Run window.
2) Type in "cmd.exe" without the quotes, should bring up a black prompt window.
3) Inside the prompt window, please type "eventvwr" without the quotes, should bring up a new window that may take a minute or two to update.
3) In the left hand corner, you will see a folder called "Windows Logs". To the left of that will be an arrow, click it so it displays all its sub-contents.
4) Highlight "Application" and scroll through their. What we're looking for is anything with a red ! that has the level at Error.
5) Please copy all the text from the field after highlighting the error and post it in this thread.

After you are done, please repeat the above steps, except this time click "System" and search for any red ! with the level as Error.

It shouldn't be too far down, as you seem to encounter this error a lot. If there are absolutely no errors, please let us know.

Thanks.

 

[Hidan]

Hello.

Please perform the following:
1) Hit Windows Key and R at the same time, should bring up a Run window.
2) Type in "cmd.exe" without the quotes, should bring up a black prompt window.
3) Inside the prompt window, please type "eventvwr" without the quotes, should bring up a new window that may take a minute or two to update.
3) In the left hand corner, you will see a folder called "Windows Logs". To the left of that will be an arrow, click it so it displays all its sub-contents.
4) Highlight "Application" and scroll through their. What we're looking for is anything with a red ! that has the level at Error.
5) Please copy all the text from the field after highlighting the error and post it in this thread.

After you are done, please repeat the above steps, except this time click "System" and search for any red ! with the level as Error.

It shouldn't be too far down, as you seem to encounter this error a lot. If there are absolutely no errors, please let us know.

Thanks.

Sorry for delayed response / dumb question, but should I copy + paste what is in the General tab or in the Details tab?

 

[Ric]

For now, General.

It should look something like this...

Faulting application name: hl2.exe, version: 0.0.0.0, time stamp: 0x4d094ebe
Faulting module name: client.dll, version: 0.0.0.0, time stamp: 0x4d110c8b
Exception code: 0xc0000005
Fault offset: 0x00259a62
Faulting process id: 0xdec
Faulting application start time: 0x01cbc0bd54e31055
Faulting application path: crogram files (x86)steamsteamappsNEGATIVEcounter-strike sourcehl2.exe
Faulting module path: crogram files (x86)steamsteamappsNEGATIVEcounter-strike sourcecstrikebinclient.dll
Report Id: 6d817efe-2ce5-11e0-81c8-00248cdfe30d

 

[Hidan]

APPLICATIONS

Warnings :


The description for Event ID 110 from source Ati HotKey Poller cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:


______________________________________________________________


Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

DETAIL -
2 user registry handles leaked from \Registry\User\S-1-5-21-1300062131-1313217679-2922051671-1011:
Process 1432 (\Device\HarddiskVolume1\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-1300062131-1313217679-2922051671-1011\Software\Microsoft\Windows\CurrentVersion\Internet Settings
Process 1432 (\Device\HarddiskVolume1\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-1300062131-1313217679-2922051671-1011\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings

______________________________________________________________
Errors :

The COM+ Event System could not remove the EventSystem.EventSubscription object {CEB8B221-89C5-41A8-98CE-79B413BF150B}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The HRESULT was 80070005.

______________________________________________________________

Faulting application OfficeLiveSignIn.exe, version 2.0.2313.0, time stamp 0x491c0a79, faulting module OfficeLiveSignIn.exe, version 2.0.2313.0, time stamp 0x491c0a79, exception code 0xc0000005, fault offset 0x00003ce7, process id 0x894, application start time 0x01cbc0e142d894a6.



______________________________________________________________

Faulting application hl.exe, version 1.1.1.1, time stamp 0x48feaf5a, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x697dec1f, process id 0x6dc, application start time 0x01cbc0ba4e6bf016.



______________________________________________________________


SYSTEM

Warnings :








Errors :

The Windows Media Player Network Sharing Service service depends on the UPnP Device Host service which failed to start because of the following error:
The dependency service or group failed to start.

______________________________________________________________


The UPnP Device Host service depends on the SSDP Discovery service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

______________________________________________________________

The AODDriver service failed to start due to the following error:
The system cannot find the path specified.


______________________________________________________________

The following boot-start or system-start driver(s) failed to load:
amdide
ASPI32
cdrom
i8042prt

______________________________________________________________


The SQL Server Agent (SQLEXPRESS) service depends on the SQL Server (SQLEXPRESS) service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.



______________________________________________________________


Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.


______________________________________________________________


DCOM got error "1068" attempting to start the service upnphost with arguments "" in order to run the server:
{204810B9-73B2-11D4-BF42-00B0D0118B56}

______________________________________________________________









These are the errors that occured. Some of them occured more often, but I didn't want to make the post to huge so I just simplified it to what errors I get.