Weird BSOD's new computer build transferred from an old one

andy11235 · 26 Nov 2012

Hi,

when i first transferred the computer over there where some problems with getting the data off a dying hard drive i finally got it off and transferred it over.
I had initiated OOBE and got it up and running then took another back up with clonezilla some how it fractured the operating system.
so i re-installed everything from clean and transferred over the user.
It was stable for most of a week and then it started having allot of blue screens near the end of last week.
I re-installed the drivers i have not done a stationary repair/install ("upgrade" on the windows cd) of the operating system to push all of the windows components again.
I am going to try that but most of them keep saying driver errors and it is coming from different program steams but coming back to similar bucket ids WIN7_DRIVER_FAULT and it is at IRQL0.

Would this be a bad CPU or is it still posible it is a windows install, or graphics problem.

Is the operating system the only one that can generate the IRQ0 interrupt?

Any help would be appreciated i Am attaching the dumps.

The computer configuration is:
Motherboard asus sabertooth
RAM 16GB corsair ddr3 1600
CPU Zambezi 8150
GPU AMD FirePro v7900

andy11235 · 26 Nov 2012

Code:

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


Loading Dump File [J:\tools\SystemTools\FileViewers\bsod\112612-12308-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`03052670
Debug session time: Mon Nov 26 14:40:37.494 2012 (UTC - 5:00)
System Uptime: 0 days 1:42:57.754
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8000310cb13, fffff88003376ca8, fffff88003376500}

Probably caused by : discache.sys ( discache!DisCreateObjectAttributeStore+ec )

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8000310cb13, The address that the exception occurred at
Arg3: fffff88003376ca8, Exception Record Address
Arg4: fffff88003376500, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!HvFreeHive+af
fffff800`0310cb13 448b5304        mov     r10d,dword ptr [rbx+4]

EXCEPTION_RECORD:  fffff88003376ca8 -- (.exr 0xfffff88003376ca8)
ExceptionAddress: fffff8000310cb13 (nt!HvFreeHive+0x00000000000000af)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003376500 -- (.cxr 0xfffff88003376500)
rax=fffff8a005c79640 rbx=ffff00a00ae27000 rcx=fffff8a005d23010
rdx=0000000000000001 rsi=fffff8a005d230c0 rdi=fffff8a005d23010
rip=fffff8000310cb13 rsp=fffff88003376ee0 rbp=0000000000232000
 r8=fffff8a005d23010  r9=000000000000ae00 r10=0000000000000000
r11=0000000001ffffff r12=fffff8a005c78d20 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!HvFreeHive+0xaf:
fffff800`0310cb13 448b5304        mov     r10d,dword ptr [rbx+4] ds:002b:ffff00a0`0ae27004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bc100
GetUlongFromAddress: unable to read from fffff800030bc1c0
 ffffffffffffffff 

FOLLOWUP_IP: 
discache!DisCreateObjectAttributeStore+ec
fffff880`03d67e98 3bc6            cmp     eax,esi

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff800031ee833 to fffff8000310cb13

STACK_TEXT:  
fffff880`03376ee0 fffff800`031ee833 : 00000000`00000000 00000000`00000001 fffff8a0`00000001 00000000`003bd000 : nt!HvFreeHive+0xaf
fffff880`03376f60 fffff800`030ffeca : fffff880`033770f0 fffff880`03377200 ffffffff`80000bc8 fffff880`03377638 : nt! ?? ::NNGAKEGL::`string'+0x5be5b
fffff880`03377050 fffff800`030ff7c6 : 00000000`00000010 20204d43`00000000 fffff880`033773e8 fffff880`033773e1 : nt!CmpInitHiveFromFile+0x246
fffff880`033771a0 fffff800`0310498f : 00000000`00000010 00000000`00000000 00000000`00000000 fffff800`03184fd7 : nt!CmpCmdHiveOpen+0x8a
fffff880`03377390 fffff800`031046c7 : fffff880`03370064 00000000`00000000 00000000`00000000 fffff880`03377a00 : nt!CmLoadKey+0x1a7
fffff880`03377580 fffff800`02e8c253 : 00000000`00000001 fffff880`03377a70 fffff880`00000010 00000000`00000000 : nt!NtLoadKeyEx+0x4c5
fffff880`033777e0 fffff800`02e88810 : fffff880`03d67e98 fffff880`03d6f3d0 00000000`00000000 00000000`00000001 : nt!KiSystemServiceCopyEnd+0x13
fffff880`033779e8 fffff880`03d67e98 : fffff880`03d6f3d0 00000000`00000000 00000000`00000001 00000000`00000001 : nt!KiServiceLinkage
fffff880`033779f0 fffff880`03d662b2 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff8a0`04ee09c0 : discache!DisCreateObjectAttributeStore+0xec
fffff880`03377ab0 fffff880`03d6644b : fffff800`00000043 00000000`00000000 fffff800`0302a2d8 00000000`00000000 : discache!ScpInitializeCache+0x19a
fffff880`03377af0 fffff800`02e96641 : fffff880`03d66370 ffffffff`80000aa0 fffffa80`0cd72710 fffffa80`0ce50b50 : discache!ScpInitializationWorker+0xdb
fffff880`03377b70 fffff800`03123e5a : 010d0101`0d01010d fffffa80`0ce50b50 00000000`00000080 fffffa80`0ccee990 : nt!ExpWorkerThread+0x111
fffff880`03377c00 fffff800`02e7dd26 : fffff880`03189180 fffffa80`0ce50b50 fffff880`031940c0 01000201`00020100 : nt!PspSystemThreadStartup+0x5a
fffff880`03377c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  discache!DisCreateObjectAttributeStore+ec

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: discache

IMAGE_NAME:  discache.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc52e

STACK_COMMAND:  .cxr 0xfffff88003376500 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_discache!DisCreateObjectAttributeStore+ec

BUCKET_ID:  X64_0x7E_discache!DisCreateObjectAttributeStore+ec

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

4: kd> lmvm discache
start             end                 module name
fffff880`03d65000 fffff880`03d74000   discache   (pdb symbols)          c:\symcache\discache.pdb\D25ADE8D75E74290B3E5B421A4268DC31\discache.pdb
    Loaded symbol image file: discache.sys
    Mapped memory image file: c:\symcache\discache.sys\4A5BC52Ef000\discache.sys
    Image path: \SystemRoot\System32\drivers\discache.sys
    Image name: discache.sys
    Timestamp:        Mon Jul 13 19:37:18 2009 (4A5BC52E)
    CheckSum:         00015F3F
    ImageSize:        0000F000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     syscache.sys
    OriginalFilename: syscache.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  System Indexer/Cache Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

andy11235 · 26 Nov 2012

Code:

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


Loading Dump File [J:\tools\SystemTools\FileViewers\bsod\112512-25069-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02e55000 PsLoadedModuleList = 0xfffff800`03099670
Debug session time: Sun Nov 25 16:08:00.475 2012 (UTC - 5:00)
System Uptime: 0 days 0:03:56.347
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800cfc24e0, fffff88007b6e40c, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+740c )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800cfc24e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007b6e40c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
atikmpag+740c
fffff880`07b6e40c 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`07cc8888 fffff880`06119000 : 00000000`00000116 fffffa80`0cfc24e0 fffff880`07b6e40c 00000000`00000000 : nt!KeBugCheckEx
fffff880`07cc8890 fffff880`06118d0a : fffff880`07b6e40c fffffa80`0cfc24e0 fffffa80`0d2ab5f0 fffffa80`0d1692b0 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07cc88d0 fffff880`061bff07 : fffffa80`0cfc24e0 00000000`00000000 fffffa80`0d2ab5f0 fffffa80`0d1692b0 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`07cc8900 fffff880`061e9b75 : 00000000`ffffffff 00000000`000037d9 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`07cc89e0 fffff880`061e82bb : 00000000`00000102 00000000`00000000 00000000`000037d9 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`07cc8a10 fffff880`061bb2c6 : ffffffff`ff676980 fffffa80`0d1692b0 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`07cc8ab0 fffff880`061e7e7a : 00000000`00000000 fffffa80`0d2ab5f0 00000000`00000080 fffffa80`0d1692b0 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`07cc8bc0 fffff800`0316ae5a : fffff8a0`0023d140 fffffa80`0d469b50 fffffa80`0cce9890 fffff8a0`0023d010 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`07cc8c00 fffff800`02ec4d26 : fffff800`03046e80 fffffa80`0d469b50 fffff800`03054cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`07cc8c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+740c
fffff880`07b6e40c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+740c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dd6bc99

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

0: kd> lmvm atikmpag
start             end                 module name
fffff880`07b67000 fffff880`07bb6000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri May 20 15:10:17 2011 (4DD6BC99)
    CheckSum:         00054B0B
    ImageSize:        0004F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

andy11235 · 26 Nov 2012

Code:

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


Loading Dump File [J:\tools\SystemTools\FileViewers\bsod\112612-12558-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02e68000 PsLoadedModuleList = 0xfffff800`030ac670
Debug session time: Mon Nov 26 11:49:02.646 2012 (UTC - 5:00)
System Uptime: 0 days 1:44:13.701
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5003, fffff70001080000, 25f, 77dd6005}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29031 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 000000000000025f
Arg4: 0000000077dd6005

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_5003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f4e369 to fffff80002ee6fc0

STACK_TEXT:  
fffff880`0a73c6b8 fffff800`02f4e369 : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`0000025f : nt!KeBugCheckEx
fffff880`0a73c6c0 fffff800`02f175bf : 80000003`64d168a0 80000003`64d16321 fffffa80`0a2e7420 fffffa80`10075ec8 : nt! ?? ::FNODOBFM::`string'+0x29031
fffff880`0a73c750 fffff800`02f04ed5 : 00000000`00000000 80000003`64d168a0 00000000`00000000 fffffa80`10075ec8 : nt!MiResolveTransitionFault+0x32f
fffff880`0a73c7e0 fffff800`02f03893 : 00000000`0036c71b 00000000`75983180 fffff680`003acc18 fffffa80`10075ec8 : nt!MiResolveProtoPteFault+0x325
fffff880`0a73c870 fffff800`02ef3549 : 00000000`00000000 00000000`75983180 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`0a73c980 fffff800`02ee50ee : 00000000`00000000 00000000`75983180 00000000`0035d301 00000000`75983180 : nt!MmAccessFault+0x359
fffff880`0a73cae0 00000000`77eadce5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`002bf348 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77eadce5


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+29031
fffff800`02f4e369 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+29031

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29031

BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29031

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

2: kd> lmvm nt
start             end                 module name
fffff800`02e68000 fffff800`03450000   nt         (pdb symbols)          c:\symcache\ntkrnlmp.pdb\B2DA40502FA744C18B9022FD187ADB592\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: c:\symcache\ntoskrnl.exe\503F82BE5e8000\ntoskrnl.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Thu Aug 30 11:11:58 2012 (503F82BE)
    CheckSum:         00554126
    ImageSize:        005E8000
    File version:     6.1.7601.17944
    Product version:  6.1.7601.17944
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   6.1.7601.17944
    FileVersion:      6.1.7601.17944 (win7sp1_gdr.120830-0333)
    FileDescription:  NT Kernel & System
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

andy11235 · 26 Nov 2012

Hmm Does not like xml so i added a .txt extension

x BlueRobot · 26 Nov 2012

Code:

BugCheck 116, {fffffa800cfc24e0, fffff88007b6e40c, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+740c )

Update:

Code:

Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri May 20 20:10:17 2011 (4DD6BC99)

Follow these steps:

STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Overclocking -
I recommend if you are overclocking any hardware, that you reset these values within the BIOS to their default values in order to increase the stability of your system.

Please run the following tests for your graphics card and RAM:

RAM - Test with Memtest86+

Run Memtest86+ for least 7-8 passes, and preferrly overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Graphics Card:

Video Card - Stress Test with Furmark

Read all the steps within the hardware test tutorials very carefully, as stress tests is designed run components to their maximum capacity, in order to point out failing or faulty hardware components.

Use the following program to monitor your hardware temperatures during the stress test:

CPUID HWMonitor

Hard Drive:

Scan for corrupted or missing Windows files with:

SFC /SCANNOW : Run in Command Prompt at Boot

Please check for the latest driver updates for your graphics card on the manufacturer's website, and check for any driver compatibility issues with:

Windows 7 Upgrade Advisor - Download - Microsoft Windows

If you are using DirectX, then try uninstalling and then reinstalling the DirectX Runtime:

How to download and install DirectX

Please post back your results :)

Upload a .NFO file:

Start

> Type: msinfo32 > File, Save

andy11235 · 26 Nov 2012

I think the bios might be configured for performance i will switch it to default.
I have not done memtest 86 yet but i did do windows mem test with all 16Gb in and it passed but i will run again.
The GPU driver i reinstalled yesterday removed everything all catalyst drivers and reinstalled the SolidWorks driver for it.
I will do a the stress test on it tomorrow night i will not be able to do it tonight but i can change the bios tuning.

x BlueRobot · 26 Nov 2012

Upload your .NFO (System Information File) then I will be able to help you more, by seeing what other drivers are outdated and what graphics card you are using:

Start

> Type: msinfo32 > File, Save

andy11235 · 26 Nov 2012

just check bios settings it was set to default and the ram was specifically set to 1600Mh

andy11235 · 26 Nov 2012

Here Is the nfo