random BSOD on Overclocked system (both gpu and cpu)

[dae7]

i'm quite sure that my system is *almost* stable.

it's overclocked, both CPU and GPU and i've done a lot of adjusting over the years

it was doing so many BSOD when i was tweaking the overclock, but i left it alone when i left the home i was at, at the time (i have had it so it was much stable and was rarely BSOD'ing) and i moved to somewhere else for a while, but anyways

now i'm back and taking my computer to my actual home, so now i want to get this under control



if you could please explain to me what is causing my crashes, it would be greatly appreciated





thanks

 

[dae7]

sorry i didn't read the sticky intructions

working on it now

 

[dae7]

i was trying to figure it out and i ran Windows_NT6_BSOD_v3.03_jcgriff2_ program a few times is that ok?

 

[dae7]

here it is, sorry for my first few posts haha

 

[dae7]

is my title not acceptable or something? just wondering, no one has replied still

 

[writhziden]

Security Software:

msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	964	8	200	1380	18/03/2012 5:43 AM	3.0.8402.0	12.48 KB (12,784 bytes)	27/04/2011 5:21 PM
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	2444	8	200	1380	18/03/2012 5:44 AM	3.0.8402.0	281.52 KB (288,272 bytes)	27/04/2011 5:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	3040	8	200	1380	18/03/2012 5:44 AM	2.1.1116.0	1.37 MB (1,436,736 bytes)	15/06/2011 2:35 PM

Possible out of date drivers:

[B][COLOR="Red"]RTCore64	fffff880`07406000	fffff880`0740c000	Wed May 25 00:39:12 2005 (42941d90)	0000a4c9		RTCore64.sys[/COLOR][/B]
RimSerial_AMD64	fffff880`04485000	fffff880`0448cc00	Mon Nov 24 10:01:01 2008 (492addcd)	00016de0		RimSerial_AMD64.sys
AtiPcie	fffff880`01880000	fffff880`01888000	Tue May 05 09:00:22 2009 (4a005486)	000134c7		AtiPcie.sys
AsUpIO	fffff880`04574000	fffff880`0457a000	Sun Jul 05 20:21:38 2009 (4a515fb2)	0000edf8		AsUpIO.sys

Remove

msiafterburner.exe	c:\program files (x86)\msi afterburner\msiafterburner.exe	680	6	200	1380	18/03/2012 5:43 AM	2.0.0.0	347.30 KB (355,640 bytes)	30/08/2010 8:04 PM

It is known to have problems on Windows 7.

RimSerial_AMD64.sys
AtiPcie.sys
AsUpIO.sys

[list=1][*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\dae7\dump files\Windows_NT6_BSOD_jcgriff2\031812-23119-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0301f000 PsLoadedModuleList = 0xfffff800`03264670
Debug session time: Sun Mar 18 06:42:25.599 2012 (UTC - 6:00)
System Uptime: 0 days 2:45:28.801
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3637383335636163
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880032b0a98 -- (.exr 0xfffff880032b0a98)
ExceptionAddress: fffff800030a6f96 (nt!KiRetireDpcList+0x00000000000000a6)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff880032b0b40 -- (.trap 0xfffff880032b0b40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000022 rbx=0000000000000000 rcx=0000000000000022
rdx=0000000000000368 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030a6f96 rsp=fffff880032b0cd0 rbp=0000000003288180
 r8=0000000000000000  r9=0000000000000f44 r10=000000000000fdbd
r11=fffff88003288100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!KiRetireDpcList+0xa6:
fffff800`030a6f96 98              cwde
Resetting default scope

MISALIGNED_IP: 
nt!KiRetireDpcList+a6
fffff800`030a6f96 98              cwde

LAST_CONTROL_TRANSFER:  from fffff800030935fe to fffff8000309bc10

STACK_TEXT:  
fffff880`032afb78 fffff800`030935fe : 00000000`00000000 00001f80`002a0280 fffff880`032b02f0 fffff800`030c7830 : nt!KeBugCheck
fffff880`032afb80 fffff800`030c74fd : fffff800`032a571c fffff800`031e2c30 fffff800`0301f000 fffff880`032b0a98 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`032afbb0 fffff800`030c62d5 : fffff800`031e60fc fffff880`032afc28 fffff880`032b0a98 fffff800`0301f000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`032afbe0 fffff800`030d7361 : fffff880`032b0a98 fffff880`032b02f0 fffff880`00000000 00002356`95ff772a : nt!RtlDispatchException+0x415
fffff880`032b02c0 fffff800`0309b2c2 : fffff880`032b0a98 fffff880`03288180 fffff880`032b0b40 fffff880`03293040 : nt!KiDispatchException+0x135
fffff880`032b0960 fffff800`0309941f : fffff880`032b0b40 00000000`00000002 00000007`8bfc4400 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`032b0b40 fffff800`030a6f96 : 00000008`d5ba815c 00000008`d5ba8381 00000008`d5ba815c 00000000`00000029 : nt!KiInvalidOpcodeFault+0x11f
fffff880`032b0cd0 fffff800`0309396a : fffff880`03288180 fffff880`03293040 00000000`00000000 fffff880`132dd7a0 : nt!KiRetireDpcList+0xa6
fffff880`032b0d80 00000000`00000000 : fffff880`032b1000 fffff880`032ab000 fffff880`032b0d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`030935fe 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\dae7\dump files\Windows_NT6_BSOD_jcgriff2\022512-29343-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0300c000 PsLoadedModuleList = 0xfffff800`03251670
Debug session time: Sat Feb 25 04:10:29.365 2012 (UTC - 6:00)
System Uptime: 5 days 23:04:35.207
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {186ff3, 2, 1, fffff80003080950}

Probably caused by : hardware ( nt!KiIdleLoop+40 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000186ff3, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003080950, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bb100
 0000000000186ff3 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiIdleLoop+40
fffff800`03080950 007402f3        add     byte ptr [rdx+rax-0Dh],dh

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880032b0bf0 -- (.trap 0xfffff880032b0bf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000002e
rdx=0000000000187000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003080950 rsp=fffff880032b0d80 rbp=0000000000000000
 r8=fffffa8006a0c0c8  r9=0000000000000000 r10=ffffffffffffffdf
r11=fffffa800a06bc20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiIdleLoop+0x40:
fffff800`03080950 007402f3        add     byte ptr [rdx+rax-0Dh],dh ds:0010:00000000`00186ff3=??
Resetting default scope

MISALIGNED_IP: 
nt!KiIdleLoop+40
fffff800`03080950 007402f3        add     byte ptr [rdx+rax-0Dh],dh

LAST_CONTROL_TRANSFER:  from fffff800030881e9 to fffff80003088c40

STACK_TEXT:  
fffff880`032b0aa8 fffff800`030881e9 : 00000000`0000000a 00000000`00186ff3 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`032b0ab0 fffff800`03086e60 : 00000000`00000000 00000000`00000000 fffff880`0328b020 fffff880`03288180 : nt!KiBugCheckDispatch+0x69
fffff880`032b0bf0 fffff800`03080950 : fffff880`03288180 fffff880`03293040 00000000`00000000 fffffa80`06ad80a0 : nt!KiPageFault+0x260
fffff880`032b0d80 00000000`00000000 : fffff880`032b1000 fffff880`032ab000 fffff880`032b0d40 00000000`00000000 : nt!KiIdleLoop+0x40


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiIdleLoop+40
fffff800`03080950 007402f3        add     byte ptr [rdx+rax-0Dh],dh

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiIdleLoop+40

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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


[/list]

1. Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
   Thanks to JMH for helping with my understanding of this crash.
2. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...

Given the infrequency of your crashes and the crash codes, I suspect MSI Afterburner is the culprit. See how things go after removing that program.


I should also mention: the crashes could be due to overclocking. The first thing to check when crashes occur is turn off all overclocking and see if the system is stable. If it is, that means overclocking is reducing stability of the system.

 

[dae7]

ty i'll check it out