System shutting down at random intervals?

danboss88

danboss88

danboss88

Associate
Joined
30 May 2010
Posts
27
Hey guys, I purchased some parts from OcUK last week.
Code: 
AMD Athlon II X4 Quad Core 635 2.90GHz (Socket AM3) - Retail  	1  	
Patriot Viper 4GB (2x2GB) PC3-10666 1333MHz Dual Channel (PVS34G1333ELK) 	1 	
Asus M4A78LT-M LE AMD 760G (Socket AM3) DDR3 Motherboard 	1 	
Corsair CX 400W ATX Power Supply (CMPSU-400CXUK) 	1 	
Seagate Barracuda 7200.12 500GB SATA-II 16MB Cache - OEM (ST3500418AS) 	1 	
Xigmatek Asgard Midi Tower Case - Black 	1 
Samsung SH-S223C/BEBE 22x DVDąRW SATA ReWriter (Black) - OEM 	1
Had the system running for a few days and I'm pleased with the build. However, the system appears to shut down at random intervals without any warning or error message. Is there any way I can determine whether it is an issue with the PSU without buying another unit? I'm hoping that it is a software issue rather than a component issue. :(

Using XP if that is any help.

Thank you for your time.
 
ACEEventlog:
Code: 
0000000003: 2010-07-28 13:47:58:407    Exception <atixcode.dll>: Retrieving the COM class factory for component with CLSID {981145A7-E08E-48F3-A1C4-52C28BCAAAF9} failed due to the following error: 80040154.
 Exception  Called by: ATI.ACE.CLI.Aspect.TransCode.Graphics.Shared.TC_Component::CheckTrancodeComObject                processID:01728 threadID:(CCCThreadNew:Wizard) domainName:(ccc.exe                    ) assemblyName:(CLI.Aspect.TransCode.Graphics.Shared, Version=2.0.3496.37303, Culture=neutral, PublicKeyToken=90ba9c70f846762e)
************************************************************************************************************************


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Code: 
0000000002: 2010-07-28 13:47:57:946    Name of null object is [SAspect:MMVideo]
 Error      Called by: ATI.ACE.CLI.Aspect.MMVideo.Graphics.Runtime.RT_MMVideo::Check                                    processID:01728 threadID:(CCCThreadNew:Runtime) domainName:(ccc.exe                    ) assemblyName:(CLI.Aspect.MMVideo.Graphics.Runtime, Version=2.0.3497.43049, Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Code: 
0000000001: 2010-07-28 13:47:57:145    RT_GC_2
 Error      Called by: ATI.ACE.CLI.Caste.Graphics.Runtime.RT_GraphicsCaste_2::.ctor                                     processID:01728 threadID:(CCCThreadNew:Runtime) domainName:(ccc.exe                    ) assemblyName:(CLI.Caste.Graphics.Runtime, Version=2.0.3497.43002, Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Code: 
0000000004: 2010-07-28 13:47:11:743    Exception <WndProc - Source handler>: Object reference not set to an instance of an object.
 Exception  Called by: ATI.ACE.AEM.Plugin.Source.Kit.Server.Common.WindowBasedFeeler+CapturingWindow::WndProc           processID:01724 threadID:(HotKeyForm      ) domainName:(ccc.exe                    ) assemblyName:(AEM.Plugin.Source.Kit.Server, Version=2.0.3497.43102, Culture=neutral, PublicKeyToken=90ba9c70f846762e)
************************************************************************************************************************


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Code: 
0000000003: 2010-07-28 13:41:37:266    Exception <atixcode.dll>: Retrieving the COM class factory for component with CLSID {981145A7-E08E-48F3-A1C4-52C28BCAAAF9} failed due to the following error: 80040154.
 Exception  Called by: ATI.ACE.CLI.Aspect.TransCode.Graphics.Shared.TC_Component::CheckTrancodeComObject                processID:01724 threadID:(CCCThreadNew:Wizard) domainName:(ccc.exe                    ) assemblyName:(CLI.Aspect.TransCode.Graphics.Shared, Version=2.0.3496.37303, Culture=neutral, PublicKeyToken=90ba9c70f846762e)
************************************************************************************************************************


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Code: 
0000000002: 2010-07-28 13:41:36:375    Name of null object is [SAspect:MMVideo]
 Error      Called by: ATI.ACE.CLI.Aspect.MMVideo.Graphics.Runtime.RT_MMVideo::Check                                    processID:01724 threadID:(CCCThreadNew:Runtime) domainName:(ccc.exe                    ) assemblyName:(CLI.Aspect.MMVideo.Graphics.Runtime, Version=2.0.3497.43049, Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Code: 
0000000001: 2010-07-28 13:41:35:584    RT_GC_2
 Error      Called by: ATI.ACE.CLI.Caste.Graphics.Runtime.RT_GraphicsCaste_2::.ctor                                     processID:01724 threadID:(CCCThreadNew:Runtime) domainName:(ccc.exe                    ) assemblyName:(CLI.Caste.Graphics.Runtime, Version=2.0.3497.43002, Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Application log:
Code: 
wuauclt (2916) The database engine stopped.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Code: 
wuaueng.dll (2916) SUS20ClientDataStore: The database engine stopped the instance (0).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Code: 
Performance counters for the WmiApRpl (WmiApRpl) service were loaded successfully. The Record Data contains the new index values assigned to this service.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Code: 
Performance counters for the WmiApRpl (WmiApRpl) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
System log:
Code: 
The IMAPI CD-Burning COM Service service entered the stopped state.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Code: 
The Computer Browser service entered the stopped state.

For more information, see Help and Support Center at [url]http://go.microsoft.com/fwlink/events.asp[/url].
Code: 
The Application Layer Gateway Service service entered the running state.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Code: 
The SSDP Discovery Service service entered the running state.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

There are a lot more. :(

All here: http://www.mediafire.com/?47skzj9pqp6xexx
 
Last edited:
rickh said:
Please run WhoCrashed.
It will analyse the minidump log and will show what caused the BSOD.

http://www.resplendence.com/whocrashed

DL: http://www.resplendence.com/download/whocrashedSetup.exe
Click to expand...
I guess this is not a good thing:
--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------

Crash dump directory: E:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


No valid crash dumps have been found on your computer


--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

Crash dumps are enabled and no valid crash dumps have been found on your computer. In case your computer does experience sudden reboots it is likely these are caused by malfunctioning hardware, power failure or a thermal issue. To troubleshoot a thermal issue, check the temperature using your BIOS setup program, check for dust in CPU and motherboard fans and if your computer is portable make sure it's located on a hard surface. Otherwise it's suggested you contact the support department of the manufacturer of your system or test your system with a memory test utility for further investigation.
Click to expand...

In BIOS settings:

CPU: 41 °C
MB: 33 °C
 
Last edited:
danboss88 said:
I guess this is not a good thing
Click to expand...

Why is windows running off E:?

I'd usually expect windows to be running on C?

If a windows PC BSOD's and crash dumps are enabled, there should be crash dumps!!

Click start
Click run
type: %windir%\minidump
press enter
is the folder empty?


__

To check for memory issues, run memtest (google).
To check for cpu issues, run orthos (google again).
 
Last edited:
Have you reused a HDD from an old system in the build? Check the bios is booting from the correct HDD windows being on E: does seem strange.

The 0x0000001A error is memory related. Remove the ram and try each stick individually. It could also be worth checking the memory timing in the bios some mobos can be funny with memory that way.

Hope this helps
 
XP is installed on E. Windows 7 is installed on C. Hard drive was brand new from OcUK. All parts are brand new. I am in the process of reinstalling Windows and will check the BIOS memory settings.

Thank you. :p
 
Oh right you are dual booting that makes more sense!

I have a feeling it's memory related. Windows vista when you boot from the DVD would let you run a memory test, my win 7 disk is buried at the mo so I can't check if it's a feature on the DVD but have a look on yours.

Good luck let us know what you find
 
rickh said:
Why is windows running off E:?

I'd usually expect windows to be running on C?

If a windows PC BSOD's and crash dumps are enabled, there should be crash dumps!!

Click start
Click run
type: %windir%\minidump
press enter
is the folder empty?


__

To check for memory issues, run memtest (google).
To check for cpu issues, run orthos (google again).
Click to expand...
Had four more BSOD shut downs.

Windows 7 alone.

Here are 2 of the dump files (will try to upload third before another crash):

http://www.mediafire.com/?gq1x7a5lvxiuhr5

Here is the report:
On Thu 29/07/2010 13:08:26 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x19 (0x21, 0xFFFFF900C1E09000, 0x8340, 0x48340)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\072910-22620-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 29/07/2010 12:58:40 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF70001182BF0, 0x0, 0x0, 0xFFFFF80001CD8117)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\072910-26691-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 29/07/2010 12:55:06 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8001CD1B70, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\072910-25381-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 29/07/2010 12:51:23 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x3452, 0x7FEF5C77000, 0xFFFFF70001086238, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\072910-28532-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
Click to expand...
Ran memtest + orthos with no errors reported.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom