Computer Randomly Shuts off

[pr1zzle]

I am having trouble playing Black Ops without my computer shutting off. I recently added another video card, 4gb of ram, and a new heatsink to my rig. I have not had this problem before, but I will be playing for 2 minutes and my computer will completely shut off. It doesn't crash, or restart, it just completely shuts off. It turns on just fine and just says windows was not shut down successfully. I'm not sure if I need a stronger power supply, if windows needs to be repaired, or if its just the game bugging out on me.


my rig:

Windows 7 64-bit
Asus M4A89GTD Pro
AMD Phenom II X6 Six-Core @ 3.0ghz
Corsair H50 Liquid cooling HeatSink
8GB DDR3 G.Skill RipJaw 1333mhz
Silverstone 850 Watt PSU
1TB HDD
Crossfired Sapphire 6870
40' Samsung TV connected via DVI

 

[Captain Pooka]

Well, if it were really a 40' TV, I would say your video card is over heating, but it's probably a 40". Slap in the other video card and play for 10 minutes, see if it happens. Tell us what your old card was. Download a temperature program, I used HWMonitor. See what the temps are for the old card after two minutes of play, then the new video card after two minutes of play.

From what I see people run xfired 6870s with 850Ws just fine. Just test the temps. If it were them, though, the game would simply shut down. andgive an overheating error message. You can also check the error logs either in the bios or in management. If you're on Windows 7 it will have "why" it shut down if you click that little flag in the tray. Now that I read, you are running windows 7. Great.

I build my computer about two years ago and I have xfired 4870s. Originally it had XP, but I put seven on it a year ago. My computer also would randomly shut down after I put 7 on there. Come to find Windows 7 automatically installed the wrong driver. I went to get the right one and it now works.

 

[pr1zzle]

I checked the dump folder and all i have is





Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\120610-372748-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image Unknown_Module_fffff800`02a04000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_fffff800`02a04000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffff800`02a04000
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a04000 PsLoadedModuleList = 0xfffff800`02c41e50
Debug session time: Mon Dec 6 14:27:59.708 2010 (UTC - 8:00)
System Uptime: 0 days 10:44:02.113
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image Unknown_Module_fffff800`02a04000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_fffff800`02a04000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffff800`02a04000
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.........
Unable to load image Unknown_Module_fffff800`02fe1000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_fffff800`02fe1000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffff800`02fe1000
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 5C, {2001, 5, 6, 0}

Unknown module 'Unknown_Module_fffff800_02fe1000' found on stack, using vad to reload module.
!vad_reload -1 0xfffff80002fe1000
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_EPROCESS ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_EPROCESS ***
*** ***
*************************************************************************
Failed to get old VAD root
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : Unknown_Module_fffff800_02fe1000 ( Unknown_Module_fffff800_02fe1000+33f92 )

Followup: MachineOwner
---------


can you tell me what exactly that is?

 

[cboucher]

You said you added a new heat sink in your original post. Was this a CPU heat sink? Also, was the problem happening before you replaced the heat sink? You may have the heat sink installed incorrectly, too much thermal compound, not enough thermal compound. I would remove, clean and reinstall the heat sink with the correct amount of thermal compound and see what happens.