Hi all. The title of the thread says it all. I've been having BSOD errors basically everyday since I built this computer. Whether I'm playin WOW or workin on some music in Fruity Loops or just on the internet. Actually just had 2 today which is why I registered earlier for this forum, Haha.
I think the problem may be my Windows 7. It's a legit copy. I guess something got screwed up during install or something. But I just need a second opinion from you guys. I've zipped the minidump files and attached them to this post. I'm so tired of this crap. It started out every now and then, but I get at least 1 if not more of these a day now.
Thanks in advance! If anyone needs anymore info about my CPU, please let me know.
EDIT: Sorry guys. Rar should be full now.
I think the problem may be my Windows 7. It's a legit copy. I guess something got screwed up during install or something. But I just need a second opinion from you guys. I've zipped the minidump files and attached them to this post. I'm so tired of this crap. It started out every now and then, but I get at least 1 if not more of these a day now.
Thanks in advance! If anyone needs anymore info about my CPU, please let me know.
EDIT: Sorry guys. Rar should be full now.
The folder seems to be empty.
The folder was empty. Follow these instructions for uploading: Blue Screen of Death (BSOD) Posting Instructions
Edited to add: Rich, I'm glad it was just not me.
Edited to add: Rich, I'm glad it was just not me.
Same here.
Sorry, I'm retarded. 
The zip is there now.
The zip is there now. Goodness, there are a bunch of them. I looked at the four most recent. These are hardware/hardware related problems.
Error code 7E - BSOD Index
Error code 1 - BSOD Index
Error code 8E - BSOD Index
Two of the dumps indicate c0000005 which is memory corruption. Three point to Windows system core drivers as the cause - which is highly unlikely - and one points to atikmdag.sys, which is an ATI Radeon driver.
Let's begin by checking your RAM. Download a copy of Memtest86+ - Advanced Memory Diagnostic Tool and burn the ISO to a CD using http://isorecorder.alexfeinman.com/W7. Boot from the CD, and leave it running for at least 7 passes. Errors, if any, will show on your screen in red. Post back with your results.
In looking at your drivers, I may have found the cause or at least part of the cause:
ASACPI.sys Thu Aug 12 22:52:52 2004
Old versions of this driver are a known BSOD cause and this is the oldest version I have seen.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2004 or 2005).
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads. Do not reinstall; only uninstall.
Post back when you have updated ASACPI.sys and uninstalled sptd.sys.
I also find other out of date drivers. In general, Windows does not like older drivers. They can and do cause conflicts and memory corruption.
How To Find Drivers:
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
Error code 7E - BSOD Index
Error code 1 - BSOD Index
Error code 8E - BSOD Index
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\Downloads\A-Rar\Dump Files\081510-13509-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.x86fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0x82c00000 PsLoadedModuleList = 0x82d48810 Debug session time: Sun Aug 15 01:44:47.744 2010 (GMT-4) System Uptime: 2 days 0:19:55.690 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ................. Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, 922a140f, 9315e7fc, 9315e3e0} *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys Probably caused by : atikmdag.sys ( atikmdag+26440f ) Followup: MachineOwner --------- 0: 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: c0000005, The exception code that was not handled Arg2: 922a140f, The address that the exception occurred at Arg3: 9315e7fc, Exception Record Address Arg4: 9315e3e0, 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: atikmdag+26440f 922a140f ff82e4010000 inc dword ptr [edx+1E4h] EXCEPTION_RECORD: 9315e7fc -- (.exr 0xffffffff9315e7fc) ExceptionAddress: 922a140f (atikmdag+0x0026440f) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000001 Parameter[1]: 000001e4 Attempt to write to address 000001e4 CONTEXT: 9315e3e0 -- (.cxr 0xffffffff9315e3e0) eax=00000003 ebx=9315ea54 ecx=00000000 edx=00000000 esi=00000000 edi=00000001 eip=922a140f esp=9315e8c4 ebp=9315e8c4 iopl=0 nv up ei pl nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206 atikmdag+0x26440f: 922a140f ff82e4010000 inc dword ptr [edx+1E4h] ds:0023:000001e4=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 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: 00000001 EXCEPTION_PARAMETER2: 000001e4 WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d68718 Unable to read MiSystemVaType memory at 82d48160 000001e4 FOLLOWUP_IP: atikmdag+26440f 922a140f ff82e4010000 inc dword ptr [edx+1E4h] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from 922c21c1 to 922a140f STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 9315e8c4 922c21c1 00000002 02ead000 0000000f atikmdag+0x26440f 9315e8e0 9204c63e 00b2ed00 00000002 02ead000 atikmdag+0x2851c1 9315e9b4 91588e48 8792af10 ffffffff 830156ee atikmdag+0xf63e 9315e9f8 918591ac 01f18940 85c70400 87a06000 atikmpag+0x4e48 9315ea20 9183707e 9315ea54 9315ea3c 918ee171 dxgkrnl+0x231ac 9315ea2c 918ee171 86ddf000 9315ea54 9315eb74 dxgkrnl+0x107e 9315ea3c 91906436 9315ea54 8792a4b8 a25efe58 dxgmms1!DXGADAPTER::DdiBuildPagingBuffer+0x11 9315eb74 91908add 00000000 a25efe58 00000000 dxgmms1!VIDMM_GLOBAL::DiscardAllocationInternal+0xa4 9315eb88 91915bcd a25efe58 28550a16 85d34290 dxgmms1!VIDMM_GLOBAL::DiscardAllocation+0x1b 9315ec58 919087ff a25efe58 00000000 8573e3f8 dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x395 9315ecc4 91908e66 9315ece0 00000000 9315ecf8 dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x741 9315ecf0 9190a4c8 00000000 9315ed18 9191e2cd dxgmms1!VIDMM_GLOBAL::ProcessTerminationCommand+0x40 9315ecfc 9191e2cd 85eb4e40 8573e3f8 8573e3f8 dxgmms1!VidMmiProcessTerminationCommand+0x10 9315ed18 9191f27d 8606a610 85d2b640 9315ed3c dxgmms1!VidSchiSubmitDeviceCommand+0x33 9315ed28 9191f4cc 8573e3f8 82c3c3f1 86dde4b8 dxgmms1!VidSchiSubmitQueueCommand+0xaf 9315ed3c 9191f573 86dde4b8 00000000 879fdd48 dxgmms1!VidSchiRun_PriorityTable+0x24 9315ed50 82e0e6d3 86dde4b8 bdb3843b 00000000 dxgmms1!VidSchiWorkerThread+0x7f 9315ed90 82cc00f9 9191f4f4 86dde4b8 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: atikmdag+26440f FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4be0caf0 STACK_COMMAND: .cxr 0xffffffff9315e3e0 ; kb FAILURE_BUCKET_ID: 0x7E_atikmdag+26440f BUCKET_ID: 0x7E_atikmdag+26440f Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\Downloads\A-Rar\Dump Files\081510-13696-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.x86fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0x82c1e000 PsLoadedModuleList = 0x82d66810 Debug session time: Sun Aug 15 02:20:57.510 2010 (GMT-4) System Uptime: 0 days 0:35:34.180 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1, {82e7b510, 0, ffff0000, 0} Probably caused by : ntkrpamp.exe ( nt!NtDeviceIoControlFile+0 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* APC_INDEX_MISMATCH (1) This is a kernel internal error. The most common reason to see this bugcheck is when a filesystem or a driver has a mismatched number of calls to disable and re-enable APCs. The key data item is the Thread->KernelApcDisable field. A negative value indicates that a driver has disabled APC calls without re-enabling them. A positive value indicates that the reverse is true. This check is made on exit from a system call. Arguments: Arg1: 82e7b510, address of system function (system call) Arg2: 00000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex Arg3: ffff0000, Thread->KernelApcDisable Arg4: 00000000, Previous KernelApcDisable Debugging Details: ------------------ FAULTING_IP: nt!NtDeviceIoControlFile+0 82e7b510 8bff mov edi,edi CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1 PROCESS_NAME: audiodg.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 774e64f4 to 82c617d3 STACK_TEXT: 8dc1bd34 774e64f4 badb0d00 01b5fc58 00000000 nt!KiServiceExit2+0x17a WARNING: Frame IP not in any known module. Following frames may be wrong. 01b5fcb0 00000000 00000000 00000000 00000000 0x774e64f4 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nt!NtDeviceIoControlFile+0 82e7b510 8bff mov edi,edi SYMBOL_NAME: nt!NtDeviceIoControlFile+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac FAILURE_BUCKET_ID: 0x1_nt!NtDeviceIoControlFile+0 BUCKET_ID: 0x1_nt!NtDeviceIoControlFile+0 Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\Downloads\A-Rar\Dump Files\081510-14289-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.x86fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0x82c1b000 PsLoadedModuleList = 0x82d63810 Debug session time: Sun Aug 15 21:20:11.434 2010 (GMT-4) System Uptime: 0 days 0:41:30.730 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1, {82e78510, 0, ffff0000, 0} Probably caused by : ntkrpamp.exe ( nt!NtDeviceIoControlFile+0 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* APC_INDEX_MISMATCH (1) This is a kernel internal error. The most common reason to see this bugcheck is when a filesystem or a driver has a mismatched number of calls to disable and re-enable APCs. The key data item is the Thread->KernelApcDisable field. A negative value indicates that a driver has disabled APC calls without re-enabling them. A positive value indicates that the reverse is true. This check is made on exit from a system call. Arguments: Arg1: 82e78510, address of system function (system call) Arg2: 00000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex Arg3: ffff0000, Thread->KernelApcDisable Arg4: 00000000, Previous KernelApcDisable Debugging Details: ------------------ FAULTING_IP: nt!NtDeviceIoControlFile+0 82e78510 8bff mov edi,edi CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1 PROCESS_NAME: audiodg.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 774b64f4 to 82c5e7d3 STACK_TEXT: a7ca3d34 774b64f4 badb0d00 0093f9a0 00000000 nt!KiServiceExit2+0x17a WARNING: Frame IP not in any known module. Following frames may be wrong. 0093f9f8 00000000 00000000 00000000 00000000 0x774b64f4 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nt!NtDeviceIoControlFile+0 82e78510 8bff mov edi,edi SYMBOL_NAME: nt!NtDeviceIoControlFile+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac FAILURE_BUCKET_ID: 0x1_nt!NtDeviceIoControlFile+0 BUCKET_ID: 0x1_nt!NtDeviceIoControlFile+0 Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\Downloads\A-Rar\Dump Files\081510-15662-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.x86fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0x82c00000 PsLoadedModuleList = 0x82d48810 Debug session time: Sun Aug 15 20:38:00.051 2010 (GMT-4) System Uptime: 0 days 18:16:21.721 Loading Kernel Symbols ............................................................... ................................................................ .............................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 98a152b1, 9d857be0, 0} Probably caused by : win32k.sys ( win32k!xxxDoPaint+c4 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) 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: c0000005, The exception code that was not handled Arg2: 98a152b1, The address that the exception occurred at Arg3: 9d857be0, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: win32k!xxxDoPaint+c4 98a152b1 0fb7482a movzx ecx,word ptr [eax+2Ah] TRAP_FRAME: 9d857be0 -- (.trap 0xffffffff9d857be0) ErrCode = 00000000 eax=00000000 ebx=fe916608 ecx=80000800 edx=00000000 esi=fea0dec8 edi=00000000 eip=98a152b1 esp=9d857c54 ebp=9d857c60 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 win32k!xxxDoPaint+0xc4: 98a152b1 0fb7482a movzx ecx,word ptr [eax+2Ah] ds:0023:0000002a=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 98a099e0 to 98a152b1 STACK_TEXT: 9d857c60 98a099e0 00000000 9d857ce4 05301cf9 win32k!xxxDoPaint+0xc4 9d857cb4 98a01e76 9d857ce4 000025ff 00000000 win32k!xxxRealInternalGetMessage+0x39c 9d857d18 82c4344a 0013fb48 00000000 00000000 win32k!NtUserPeekMessage+0x3f 9d857d18 775064f4 0013fb48 00000000 00000000 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 0013faf8 00000000 00000000 00000000 00000000 0x775064f4 STACK_COMMAND: kb FOLLOWUP_IP: win32k!xxxDoPaint+c4 98a152b1 0fb7482a movzx ecx,word ptr [eax+2Ah] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!xxxDoPaint+c4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c425a FAILURE_BUCKET_ID: 0x8E_win32k!xxxDoPaint+c4 BUCKET_ID: 0x8E_win32k!xxxDoPaint+c4 Followup: MachineOwner ---------
Let's begin by checking your RAM. Download a copy of Memtest86+ - Advanced Memory Diagnostic Tool and burn the ISO to a CD using http://isorecorder.alexfeinman.com/W7. Boot from the CD, and leave it running for at least 7 passes. Errors, if any, will show on your screen in red. Post back with your results.
In looking at your drivers, I may have found the cause or at least part of the cause:
ASACPI.sys Thu Aug 12 22:52:52 2004
Old versions of this driver are a known BSOD cause and this is the oldest version I have seen.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2004 or 2005).
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads. Do not reinstall; only uninstall.
Post back when you have updated ASACPI.sys and uninstalled sptd.sys.
I also find other out of date drivers. In general, Windows does not like older drivers. They can and do cause conflicts and memory corruption.
Quote:
ASACPI.sys Thu Aug 12 22:52:52 2004
cledx.sys Mon May 09 14:08:41 2005
cmudax3.sys Fri May 22 03:02:59 2009
nvsmu.sys Mon Jun 29 03:36:34 2009
ymidusbw.sys Mon Aug 03 22:14:52 2009
cledx.sys Mon May 09 14:08:41 2005
cmudax3.sys Fri May 22 03:02:59 2009
nvsmu.sys Mon Jun 29 03:36:34 2009
ymidusbw.sys Mon Aug 03 22:14:52 2009
How To Find Drivers:
Quote:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
Quote:
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
Thank you so much for your help.
I have updated the Motherboard drivers and it's stamped 2009. There is no updated driver for the CMedia audio driver. (cmudax3.sys) I have also uninstalled sptd.sys
Checking the other drivers and downloading the MemTest now.
I have updated the Motherboard drivers and it's stamped 2009. There is no updated driver for the CMedia audio driver. (cmudax3.sys) I have also uninstalled sptd.sys
Checking the other drivers and downloading the MemTest now.
You are welcome and thank you for the progress report.
Did you try this site for the cmudax3.sys driver? C-Media Electronics, Inc. Is this a software program? If so, you might want to consider uninstalling it if it causes problems.
Did you try this site for the cmudax3.sys driver? C-Media Electronics, Inc. Is this a software program? If so, you might want to consider uninstalling it if it causes problems.
Ok, went to the CMedia website and downloaded the very first CMI8738-LX update.
My soundcard is a Turtle Beach Montego DDL. And I read elsewhere on this forum that the CMI8738 chip runs this card. So when I installed the update and went into System32, the cmudax3.sys file is now stamped 2/26/2007 instead of 2009! I think the Turtle Beach drivers from their site are a little more up to date. I'm gonna reinstall those.
And as far as nvsmu.sys, which is my Nvidia nForce 720a, the driver release date on the site is May 11th, 2009 so I don't think it's anything new.
I'll post back when I get the memtest done.
Oh, and FYI, ymidusbw.sys is for my USB-MIDI keyboard. A Yamaha YPT-400. I do music production on the side. I went to their site and they have no new drivers as of today.
EDIT:
Actually the cmudax3.sys is stamped 2009. But the .DLL cmudax3 is what's stamped 2007. Would this be the cause of some kind of error?
My soundcard is a Turtle Beach Montego DDL. And I read elsewhere on this forum that the CMI8738 chip runs this card. So when I installed the update and went into System32, the cmudax3.sys file is now stamped 2/26/2007 instead of 2009! I think the Turtle Beach drivers from their site are a little more up to date. I'm gonna reinstall those.
And as far as nvsmu.sys, which is my Nvidia nForce 720a, the driver release date on the site is May 11th, 2009 so I don't think it's anything new.
I'll post back when I get the memtest done.
Oh, and FYI, ymidusbw.sys is for my USB-MIDI keyboard. A Yamaha YPT-400. I do music production on the side. I went to their site and they have no new drivers as of today.
EDIT:
Actually the cmudax3.sys is stamped 2009. But the .DLL cmudax3 is what's stamped 2007. Would this be the cause of some kind of error?
Ok. I ran 2 passes last night and no errors came back. But I stopped it cause I needed to do some things before I went to bed. I booted MemTest up and ran it all night expecting the same thing and I was unpleasantly surprised. I have attached a quick table, that I typed, of what I saw. All red. Didn't know how to scroll down (or how to save the test data) so there could have been more maybe.
EDIT:
If it's any help, I'm also attaching a .html report generated by CPUID so you can get a feel for what my computer is running. It will be in a .rar since I can't attach html files.
EDIT:
If it's any help, I'm also attaching a .html report generated by CPUID so you can get a feel for what my computer is running. It will be in a .rar since I can't attach html files.
�� Quote: Originally Posted by legend86 
Ok, went to the CMedia website and downloaded the very first CMI8738-LX update.
My soundcard is a Turtle Beach Montego DDL. And I read elsewhere on this forum that the CMI8738 chip runs this card. So when I installed the update and went into System32, the cmudax3.sys file is now stamped 2/26/2007 instead of 2009! I think the Turtle Beach drivers from their site are a little more up to date. I'm gonna reinstall those.
And as far as nvsmu.sys, which is my Nvidia nForce 720a, the driver release date on the site is May 11th, 2009 so I don't think it's anything new.
My soundcard is a Turtle Beach Montego DDL. And I read elsewhere on this forum that the CMI8738 chip runs this card. So when I installed the update and went into System32, the cmudax3.sys file is now stamped 2/26/2007 instead of 2009! I think the Turtle Beach drivers from their site are a little more up to date. I'm gonna reinstall those.
And as far as nvsmu.sys, which is my Nvidia nForce 720a, the driver release date on the site is May 11th, 2009 so I don't think it's anything new.
Quote:
Oh, and FYI, ymidusbw.sys is for my USB-MIDI keyboard. A Yamaha YPT-400. I do music production on the side. I went to their site and they have no new drivers as of today.
EDIT:
Actually the cmudax3.sys is stamped 2009. But the .DLL cmudax3 is what's stamped 2007. Would this be the cause of some kind of error?
EDIT:
Actually the cmudax3.sys is stamped 2009. But the .DLL cmudax3 is what's stamped 2007. Would this be the cause of some kind of error?
�� Quote: Originally Posted by legend86 Ok. I ran 2 passes last night and no errors came back. But I stopped it cause I needed to do some things before I went to bed. I booted MemTest up and ran it all night expecting the same thing and I was unpleasantly surprised. I have attached a quick table, that I typed, of what I saw. All red. Didn't know how to scroll down (or how to save the test data) so there could have been more maybe.
EDIT:
If it's any help, I'm also attaching a .html report generated by CPUID so you can get a feel for what my computer is running. It will be in a .rar since I can't attach html files.
EDIT:
If it's any help, I'm also attaching a .html report generated by CPUID so you can get a feel for what my computer is running. It will be in a .rar since I can't attach html files.
You can make this easier by downloading Speccy.
Memtest has identified that you have a RAM problem. This could mean a bad stick of RAM, a bad motherboard slot or incompatible RAM. Here is the next step; it will be time consuming.
Power down and remove all of your RAM except one stick. Run Memtest for at least 5 -7 passes on that stick. If it passes, set aside and remember that it is a good stick. Then repeat with the next stick and so on until you have tested each stick separately. If you get a bad stick, set that aside and remember that it is bad.
If all sticks test good, take a good stick and test each slot with it until you have test all of your RAM slots.
Post back with your results.
Ok, my specs have been updated. Will post back with MemTest results when I can.
EDIT:
Forgot to mention that when we built this cpu, my friend overclocked the ram for me slightly. It wasn't running at the advertised speeds.
G.SKILL 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500)
Again, thank you.
EDIT:
Forgot to mention that when we built this cpu, my friend overclocked the ram for me slightly. It wasn't running at the advertised speeds.
G.SKILL 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500)
Again, thank you.
You are very welcome and thanks for filling in your system specs. That helps.
Return your RAM to stock settings. That may well be part of the problem.
Return your RAM to stock settings. That may well be part of the problem.
Ok, I'm gonna run the MemTest tonight. But I have a question. Like I said, my friend overclocked my RAM slightly when we built the CPU. I will admit that I know NOTHING about overclocking. I watched him do it and he explained it to me, but that was a few months ago and I don't remember how we did it, haha. Also, I've moved to a new location in the past few weeks so I can't get up with him.
I'm pretty sure once I get a guide from Google and get into the BIOS, I'll be fine. I just need to know what needs to be changed to get it back to stock settings.
Here is a link to my RAM that I bought from Newegg:
Newegg.com - G.SKILL 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500) Dual Channel Kit Desktop Memory Model F2-8500CL5D-4GBPK
And here is the info for my 2 sticks via PCWizard:
Thanks again.
I'm pretty sure once I get a guide from Google and get into the BIOS, I'll be fine. I just need to know what needs to be changed to get it back to stock settings.
Here is a link to my RAM that I bought from Newegg:
Newegg.com - G.SKILL 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500) Dual Channel Kit Desktop Memory Model F2-8500CL5D-4GBPK
And here is the info for my 2 sticks via PCWizard:
Code:
General Information : DIMM_A1 (BANK0 ) : 2048 MB - DIMM DIMM_A2 (BANK2 ) : 2048 MB - DIMM Information SPD EEPROM (DIMM_A1) : Manufacturer : G Skill Part Number : F2-8500CL5-2GBPK Serial Number : Unspecified Type : DDR2-SDRAM PC2-6400 (399 MHz) - [DDR2-800] Format : Regular UDIMM (133.35 x 3) Size : 2048 MB (2 ranks, 8 banks) Module Buffered : No Module Registered : No Module SLi Ready (EPP) : Yes Width : 64-bit Error Correction Capability (EC... No Max. Burst Length : 8 Refresh : Reduced (.5x)7.8, Self Refresh�s Voltage : SSTL 1.8v Prefetch Buffer : 4-bit Manufacture : 2000 Supported Frequencies : 266 MHz, 400 MHz CAS Latency (tCL) : 4 clocks @ 266 MHz, 5 clocks @ 400 MHz RAS to CAS (tRCD) : 4 clocks @ 266 MHz, 5 clocks @ 400 MHz RAS Precharge (tRP) : 4 clocks @ 266 MHz, 5 clocks @ 400 MHz Cycle Time (tRAS) : 10 clocks @ 266 MHz, 15 clocks @ 400 MHz Min TRC : 16 clocks @ 266 MHz, 24 clocks @ 400 MHz EPP Profile #1 : Full Performance Voltage Level : 2.1V Address Command Rate : 2T Cycle Time : 1.875ns @ 533.33 MHz CAS Latency (tCL) : 5 clocks RAS to CAS (tRCD) : 5 clocks RAS Precharge (tRP) : 5 clocks Cycle Time (tRAS) : 15 clocks tRC : 48 clocks tWR : 13 clocks Information SPD EEPROM (DIMM_A2) : Manufacturer : G Skill Part Number : F2-8500CL5-2GBPK Serial Number : Unspecified Type : DDR2-SDRAM PC2-6400 (399 MHz) - [DDR2-800] Format : Regular UDIMM (133.35 x 3) Size : 2048 MB (2 ranks, 8 banks) Module Buffered : No Module Registered : No Module SLi Ready (EPP) : Yes Width : 64-bit Error Correction Capability (EC... No Max. Burst Length : 8 Refresh : Reduced (.5x)7.8, Self Refresh�s Voltage : SSTL 1.8v Prefetch Buffer : 4-bit Manufacture : 2000 Supported Frequencies : 266 MHz, 400 MHz CAS Latency (tCL) : 4 clocks @ 266 MHz, 5 clocks @ 400 MHz RAS to CAS (tRCD) : 4 clocks @ 266 MHz, 5 clocks @ 400 MHz RAS Precharge (tRP) : 4 clocks @ 266 MHz, 5 clocks @ 400 MHz Cycle Time (tRAS) : 10 clocks @ 266 MHz, 15 clocks @ 400 MHz Min TRC : 16 clocks @ 266 MHz, 24 clocks @ 400 MHz EPP Profile #1 : Full Performance Voltage Level : 2.1V Address Command Rate : 2T Cycle Time : 1.875ns @ 533.33 MHz CAS Latency (tCL) : 5 clocks RAS to CAS (tRCD) : 5 clocks RAS Precharge (tRP) : 5 clocks Cycle Time (tRAS) : 15 clocks tRC : 48 clocks tWR : 13 clocks Memory Controller Information : Memory Controller : System Memory Location : Mainboard Error Correction Capability : No Number of connectors : 4 Max. Module Size : 16384 MB
Not sure if this has anything to do with it or not.
But my computer used to get BSOD because my Processor was overheating. This could happen if your heatsink isnt seated/attached properly, or if you accidently OC'ed your CPU when you OC'ed your ram. If your buddy upped the FSB (to get a 1:1 Ratio), and didnt lower the multiplier, this could result in unintended CPU overclocking.
But my computer used to get BSOD because my Processor was overheating. This could happen if your heatsink isnt seated/attached properly, or if you accidently OC'ed your CPU when you OC'ed your ram. If your buddy upped the FSB (to get a 1:1 Ratio), and didnt lower the multiplier, this could result in unintended CPU overclocking.
Thanks for the input! I'm pretty sure my processor isn't overheating though. We did overclock the processor from 3.0Ghz to 3.3Ghz. But even as of today, the processor is running at an average temperature of 45C
I am not an expert with RAM and overclocking. I will get someone to answer your questions. I will say that for troubleshooting you should return all setting to stock - CPU RAM, and graphics card. You need to eliminate all possible causes of crashes, of which overclocking can be a cause.
It is my understanding that restoring the BIOS to default settings should remove the overclock. You can usually do this in the BIOS settings. If not, there is a battery somewhere on the motherboard that can be removed, then put back, which will clear any changes.
When it comes to overclocking, RAM is actually the hardest part to OC. Most do not OC very well. And those that can, will require much looser timings to achieve higher frequencies.
It is also the easiest piece of hardware to ruin by overclocking.
Generally speaking, the best way to OC, is by lowering the RAM speed below what its rated at.
For example: If 1066 RAM, lower it to 800Mhz with fairly loose timings such as 5-5-5-15.
At that point, start OCing the FSB (effectivly raising CPU speed and the RAM slightly.
Once you hit the point you want for CPU speed, start tightening RAM timings.
Being an AMD system it may work slightly different, however the same principle applies.
You can not set the RAM at its rated speed and start Overclocking. You need to lower the RAM speed 1st.
It is also the easiest piece of hardware to ruin by overclocking.
Generally speaking, the best way to OC, is by lowering the RAM speed below what its rated at.
For example: If 1066 RAM, lower it to 800Mhz with fairly loose timings such as 5-5-5-15.
At that point, start OCing the FSB (effectivly raising CPU speed and the RAM slightly.
Once you hit the point you want for CPU speed, start tightening RAM timings.
Being an AMD system it may work slightly different, however the same principle applies.
You can not set the RAM at its rated speed and start Overclocking. You need to lower the RAM speed 1st.
�� Quote: Originally Posted by Wishmaster When it comes to overclocking, RAM is actually the hardest part to OC. Most do not OC very well. And those that can, will require much looser timings to achieve higher frequencies.
It is also the easiest piece of hardware to ruin by overclocking.
Generally speaking, the best way to OC, is by lowering the RAM speed below what its rated at.
For example: If 1066 RAM, lower it to 800Mhz with fairly loose timings such as 5-5-5-15.
At that point, start OCing the FSB (effectivly raising CPU speed and the RAM slightly.
Once you hit the point you want for CPU speed, start tightening RAM timings.
Being an AMD system it may work slightly different, however the same principle applies.
You can not set the RAM at its rated speed and start Overclocking. You need to lower the RAM speed 1st.
It is also the easiest piece of hardware to ruin by overclocking.
Generally speaking, the best way to OC, is by lowering the RAM speed below what its rated at.
For example: If 1066 RAM, lower it to 800Mhz with fairly loose timings such as 5-5-5-15.
At that point, start OCing the FSB (effectivly raising CPU speed and the RAM slightly.
Once you hit the point you want for CPU speed, start tightening RAM timings.
Being an AMD system it may work slightly different, however the same principle applies.
You can not set the RAM at its rated speed and start Overclocking. You need to lower the RAM speed 1st.
If unsure about all the settings, or how to adjust them, the best bet would be the
"Reset to Opitmized Defaults" option in the bios.
I would still run Memtest as well, just to be sure theres no issues.
"Reset to Opitmized Defaults" option in the bios.
I would still run Memtest as well, just to be sure theres no issues.
^^
Thank you so much. I just wanted to get the system back to default in BIOS before I ran the Memtest. I'll try this now.
EDIT:
Ok, I went back into BIOS and set the DRAM Frequencies to set Automatically instead of Manual. So instead of running at like approx. 573Mhz, it's running at approx. 430Mhz and the timings are now back to 5-5-5-15 instead of 5-7-7-20
Thank you so much. I just wanted to get the system back to default in BIOS before I ran the Memtest. I'll try this now.
EDIT:
Ok, I went back into BIOS and set the DRAM Frequencies to set Automatically instead of Manual. So instead of running at like approx. 573Mhz, it's running at approx. 430Mhz and the timings are now back to 5-5-5-15 instead of 5-7-7-20
Hello,
Are you using Memtest86+ as recommended by CarlTR6 on Post #6?
When having issues it is best to return the BIOS to default settings.
Did you have the settings at default the first time you started the computer?
After you re-set the BIOS to default, what are the RAM timings (first four) and DRAM voltage settings?
You should D/L your motherboard manual, Asus M4N78 PRO here.
Read the section on your CPU and Memory.
From the website:
From manual:
This will need to be checked.
Your RAM is on the recommended list, at 5-5-5-15 and 2.1v.
From your manual:
Confirm which slots your RAM is currently located.
Read the BIOS section in your manual, the CPU and RAM settings are in the AI Tweaker Menu section 2.4.
Let us know the:
CPU voltage
CPU/NB voltage
DRAM voltage
Can you D/L CPUZ?
Open CPUZ and take a screen shot of the CPU, Mainboard, Memory and SPD tabs, use the Snipping tool, Start button> All Programs> Accessories> Snipping Tool.
Save to a convenient place.
Then post using this method.
How to Post a Screenshot in Seven Forums.
This will give us the basic info, in one easy to read post.
Are you using Memtest86+ as recommended by CarlTR6 on Post #6?
When having issues it is best to return the BIOS to default settings.
Did you have the settings at default the first time you started the computer?
After you re-set the BIOS to default, what are the RAM timings (first four) and DRAM voltage settings?
You should D/L your motherboard manual, Asus M4N78 PRO here.
Read the section on your CPU and Memory.
From the website:
Quote:
Memory 4 x DIMM, Max. 16 GB, DDR2 1200(O.C.)/1066*/800/667 ECC,Non-ECC,Un-buffered Memory
Dual Channel memory architecture
*Due to AMD CPU limitation, DDR2 1066 is supported by AM2+/AM3 CPU for one DIMM per channel only. Refer to ASUSTeK Computer for the memory QVL (Qualified Vendors Lists).
Dual Channel memory architecture
*Due to AMD CPU limitation, DDR2 1066 is supported by AM2+/AM3 CPU for one DIMM per channel only. Refer to ASUSTeK Computer for the memory QVL (Qualified Vendors Lists).
Quote:
This motherboard does not support DIMMs made up of 256 megabit (Mb) chips or less.
Your RAM is on the recommended list, at 5-5-5-15 and 2.1v.
From your manual:
Quote:
Due to AM3/AM2+ CPU limitations, only one DDR2 1066 Dimm is supported per channel.
Quote:
Supports one pair of modules inserted into eithor the blue slots or the black slots as one pair of Dual-channel memory configuration
Read the BIOS section in your manual, the CPU and RAM settings are in the AI Tweaker Menu section 2.4.
Let us know the:
CPU voltage
CPU/NB voltage
DRAM voltage
Can you D/L CPUZ?
Open CPUZ and take a screen shot of the CPU, Mainboard, Memory and SPD tabs, use the Snipping tool, Start button> All Programs> Accessories> Snipping Tool.
Save to a convenient place.
Then post using this method.
How to Post a Screenshot in Seven Forums.
This will give us the basic info, in one easy to read post.
Posting from my iPod touch as I am running the Memtest reccomended by Carl.
The first time I booted the cpu, the BIOS was at default. We overclocked CPU and RAM afterwards. I am running 2x2GB sticks. One in the blue slot and one in the black slot. I did not default the entire BIOS before running the current memtest. Just turned the DRAM Frequencies back to Auto.
I have CPUz and will post back in the morning as the test on the first stick is currently on pass #4 and its 2:45am where Im at. Haha, Thank you!
The first time I booted the cpu, the BIOS was at default. We overclocked CPU and RAM afterwards. I am running 2x2GB sticks. One in the blue slot and one in the black slot. I did not default the entire BIOS before running the current memtest. Just turned the DRAM Frequencies back to Auto.
I have CPUz and will post back in the morning as the test on the first stick is currently on pass #4 and its 2:45am where Im at. Haha, Thank you!
Hopefully it will pass the memtest86+.
My guess is there will be a couple of settings that will need adjusted.
When you OC the CPU it will affect the FSB (Front Side Bus) which in turn affects the RAM.
Which slots are your RAM sticks in, DIMM A1 and DIMM A2, the numbering system is from your MOBO manual.
Let us know what the DRAM Frequency and NB Voltage is set at.
My guess is there will be a couple of settings that will need adjusted.
When you OC the CPU it will affect the FSB (Front Side Bus) which in turn affects the RAM.
Which slots are your RAM sticks in, DIMM A1 and DIMM A2, the numbering system is from your MOBO manual.
Let us know what the DRAM Frequency and NB Voltage is set at.
Dave, Petey and Wishmaster, thank you very much for the help. 
Ran the first Memtest on Stick 1. 15 Passes, No errors.
I also found out how to default my BIOS back to stock settings after the Memtest. But for your info, my CPU WAS at:
CPU Ratio: 15.50x
FSB Frequency: 215
PCIE Frequency: 100
CPU Voltage: 1.3875
CPU/NB Voltage: Auto
DRAM Voltage: 2.100V
Everything, as of now, is turned to Auto.
My RAM is inserted into DIMM_A1 & DIMM_A2.
I have attached the photos of CPUz. FYI, because I just finished Memtest, I have only ONE stick inserted into DIMM_A1
I also found out how to default my BIOS back to stock settings after the Memtest. But for your info, my CPU WAS at:
CPU Ratio: 15.50x
FSB Frequency: 215
PCIE Frequency: 100
CPU Voltage: 1.3875
CPU/NB Voltage: Auto
DRAM Voltage: 2.100V
Everything, as of now, is turned to Auto.
My RAM is inserted into DIMM_A1 & DIMM_A2.
I have attached the photos of CPUz. FYI, because I just finished Memtest, I have only ONE stick inserted into DIMM_A1
Good work, legend. I presume you are going to test the second stick now?
I have one question. I just want to confirm that you updated ASACPI.sys Thu Aug 12 22:52:52 2004 to a version dated 2009 or 2010?
I have one question. I just want to confirm that you updated ASACPI.sys Thu Aug 12 22:52:52 2004 to a version dated 2009 or 2010?
If memtest86+ passes on the second RAM stick, and your still getting BSoDs then update your BIOS to Version 1205.
�� Quote: Originally Posted by CarlTR6 Good work, legend. I presume you are going to test the second stick now?
I have one question. I just want to confirm that you updated ASACPI.sys Thu Aug 12 22:52:52 2004 to a version dated 2009 or 2010?
I have one question. I just want to confirm that you updated ASACPI.sys Thu Aug 12 22:52:52 2004 to a version dated 2009 or 2010?
This ASACPI.sys file is stamped 2004. Also in this same folder is atk2000.cat (stamped 2004), atk2000.inf (stamped 2004), and atk2000.PNF (stamped 2010)
What are these and would this be any cause for error??
Yes, I'm getting ready to test the second stick. Quick question though. Stick 1 was tested in DIMM_A1. (its original position) I was thinking about testing Stick 2 in DIMM_A2. (its original position) If Stick 2 comes back with no errors, can we effectively say that both sticks AND both slots are not faulty? Therefore removing the need to test Stick 1 in A2 and Stick 2 in A1. And would I need to check slots B1 and B2 even though I don't use those?
�� Quote: Originally Posted by Dave76 Hello,
Are you using Memtest86+ as recommended by CarlTR6 on Post #6?
When having issues it is best to return the BIOS to default settings.
Did you have the settings at default the first time you started the computer?
After you re-set the BIOS to default, what are the RAM timings (first four) and DRAM voltage settings?
You should D/L your motherboard manual, Asus M4N78 PRO here.
Read the section on your CPU and Memory.
From the website:
From manual:
This will need to be checked.
Your RAM is on the recommended list, at 5-5-5-15 and 2.1v.
From your manual:
Confirm which slots your RAM is currently located.
Read the BIOS section in your manual, the CPU and RAM settings are in the AI Tweaker Menu section 2.4.
Let us know the:
CPU voltage
CPU/NB voltage
DRAM voltage
Can you D/L CPUZ?
Open CPUZ and take a screen shot of the CPU, Mainboard, Memory and SPD tabs, use the Snipping tool, Start button> All Programs> Accessories> Snipping Tool.
Save to a convenient place.
Then post using this method.
How to Post a Screenshot in Seven Forums.
This will give us the basic info, in one easy to read post.
Are you using Memtest86+ as recommended by CarlTR6 on Post #6?
When having issues it is best to return the BIOS to default settings.
Did you have the settings at default the first time you started the computer?
After you re-set the BIOS to default, what are the RAM timings (first four) and DRAM voltage settings?
You should D/L your motherboard manual, Asus M4N78 PRO here.
Read the section on your CPU and Memory.
From the website:
Quote:
Memory 4 x DIMM, Max. 16 GB, DDR2 1200(O.C.)/1066*/800/667 ECC,Non-ECC,Un-buffered Memory
Dual Channel memory architecture
*Due to AMD CPU limitation, DDR2 1066 is supported by AM2+/AM3 CPU for one DIMM per channel only. Refer to ASUSTeK Computer for the memory QVL (Qualified Vendors Lists).
Dual Channel memory architecture
*Due to AMD CPU limitation, DDR2 1066 is supported by AM2+/AM3 CPU for one DIMM per channel only. Refer to ASUSTeK Computer for the memory QVL (Qualified Vendors Lists).
Quote:
This motherboard does not support DIMMs made up of 256 megabit (Mb) chips or less.
Your RAM is on the recommended list, at 5-5-5-15 and 2.1v.
From your manual:
Quote:
Due to AM3/AM2+ CPU limitations, only one DDR2 1066 Dimm is supported per channel.
Quote:
Supports one pair of modules inserted into eithor the blue slots or the black slots as one pair of Dual-channel memory configuration
Read the BIOS section in your manual, the CPU and RAM settings are in the AI Tweaker Menu section 2.4.
Let us know the:
CPU voltage
CPU/NB voltage
DRAM voltage
Can you D/L CPUZ?
Open CPUZ and take a screen shot of the CPU, Mainboard, Memory and SPD tabs, use the Snipping tool, Start button> All Programs> Accessories> Snipping Tool.
Save to a convenient place.
Then post using this method.
How to Post a Screenshot in Seven Forums.
This will give us the basic info, in one easy to read post.
�� Quote: Originally Posted by legend86 �� Quote: Originally Posted by CarlTR6 Good work, legend. I presume you are going to test the second stick now?
I have one question. I just want to confirm that you updated ASACPI.sys Thu Aug 12 22:52:52 2004 to a version dated 2009 or 2010?
I have one question. I just want to confirm that you updated ASACPI.sys Thu Aug 12 22:52:52 2004 to a version dated 2009 or 2010?
This ASACPI.sys file is stamped 2004. Also in this same folder is atk2000.cat (stamped 2004), atk2000.inf (stamped 2004), and atk2000.PNF (stamped 2010)
What are these and would this be any cause for error??
Quote:
Yes, I'm getting ready to test the second stick. Quick question though. Stick 1 was tested in DIMM_A1. (its original position) I was thinking about testing Stick 2 in DIMM_A2. (its original position) If Stick 2 comes back with no errors, can we effectively say that both sticks AND both slots are not faulty? Therefore removing the need to test Stick 1 in A2 and Stick 2 in A1. And would I need to check slots B1 and B2 even though I don't use those?
Finished Memtest on stick 2 in slot A2. 7 Passes, 0 Errors. 
Don't know why my first Memtest on both sticks came up with errors. I guess I'll stick to the defaults for everything for now and see if I get any more BSODs. The CPU was only OC'd by .3Ghz so it was more for show than actual performance.
I would like to thank everyone who helped me on this issue. I know I was probably annoying all of you to death! Haha. But with your help, hopefully now I'll be BSOD free.
Glad I found a place with good people to get some answers from as this is my first ever home build.
Don't know why my first Memtest on both sticks came up with errors. I guess I'll stick to the defaults for everything for now and see if I get any more BSODs. The CPU was only OC'd by .3Ghz so it was more for show than actual performance.
I would like to thank everyone who helped me on this issue. I know I was probably annoying all of you to death! Haha. But with your help, hopefully now I'll be BSOD free.
Glad I found a place with good people to get some answers from as this is my first ever home build.
It's best to check all the RAM slots, this will tell you if there is a MOBO or controller fault.
If both RAM sticks pass in their original slots then fails in another slot, this indicates a slot failure, or controller problem which may be corrected by adjusting the RAM settings.
If RAM stick #1 passes in slot A1 but fails in slot B1, then test RAM stick #2 in slot B1.
Since you re-set BIOS to default, have you ran memtest86+ with both RAM sticks installed?
IF you get a failure it means the RAM settings in BIOS need adjusted. Usually a voltage bump for the NB will help.
Let us know the results before you change any voltage settings, you need to be very careful with the NB voltage setting.
If both RAM sticks pass in their original slots then fails in another slot, this indicates a slot failure, or controller problem which may be corrected by adjusting the RAM settings.
If RAM stick #1 passes in slot A1 but fails in slot B1, then test RAM stick #2 in slot B1.
Since you re-set BIOS to default, have you ran memtest86+ with both RAM sticks installed?
IF you get a failure it means the RAM settings in BIOS need adjusted. Usually a voltage bump for the NB will help.
Let us know the results before you change any voltage settings, you need to be very careful with the NB voltage setting.
Follow Dave's advice; he is very knowledgeable in this area.
�� Quote: Originally Posted by Dave76 It's best to check all the RAM slots, this will tell you if there is a MOBO or controller fault.
If both RAM sticks pass in their original slots then fails in another slot, this indicates a slot failure, or controller problem which may be corrected by adjusting the RAM settings.
If RAM stick #1 passes in slot A1 but fails in slot B1, then test RAM stick #2 in slot B1.
Since you re-set BIOS to default, have you ran memtest86+ with both RAM sticks installed?
IF you get a failure it means the RAM settings in BIOS need adjusted. Usually a voltage bump for the NB will help.
Let us know the results before you change any voltage settings, you need to be very careful with the NB voltage setting.
If both RAM sticks pass in their original slots then fails in another slot, this indicates a slot failure, or controller problem which may be corrected by adjusting the RAM settings.
If RAM stick #1 passes in slot A1 but fails in slot B1, then test RAM stick #2 in slot B1.
Since you re-set BIOS to default, have you ran memtest86+ with both RAM sticks installed?
IF you get a failure it means the RAM settings in BIOS need adjusted. Usually a voltage bump for the NB will help.
Let us know the results before you change any voltage settings, you need to be very careful with the NB voltage setting.
Ok, sorry for the delay guys. I ran a memtest 2 nights ago, then went out of town for a couple hours the next day. When I came back, my computer was off. Weird to say the least. Ran one again last night. 7 Passes, 0 Errors.
Another question. My sticks are now running at 800Mhz at 5-5-5-15. Any way I can get it to it's rated 1066? Is it worth it? According to ASUS, they say my MOBO is compatible for this mode.
And this comes from the G.Skill forums:
http://www.gskill.us/forum/showthread.php?t=723
Another question. My sticks are now running at 800Mhz at 5-5-5-15. Any way I can get it to it's rated 1066? Is it worth it? According to ASUS, they say my MOBO is compatible for this mode.
And this comes from the G.Skill forums:
Quote:
Please be aware that at this point in time 1066MHz support is not guaranteed on every motherboard and CPU. Unfortunately, some boards have a better BIOS than others and as such will offer superior support for a 1066 mode. A few steps to get the best results when attempting 1066 mode.
1. Ensure your motherboard has full Phenom II/1066MHz support from the manufacturer and that you are running the latest BIOS.
2. Do not try to achieve 1066MHz via overclocking the bus or the memory via the 800MHz divider, you will NOT be able to achieve the speeds in this way as the internal memory controller (IMC) timings will still be too tight. Hence, you must first enabled 1066MHz mode specifically to relax these timings.
3. Ensure the memory timings are set loosely enough to accept these speeds. My recommendation would be: CAS 5, TRCD 6, TRP 6, TRAS 24, TRC 30 and a TRFC of 195us or 52-55 (depending on how your motherboard lists it).
4. Max voltage you should ever need for this mode is 2.0v. If you are still noticing instability, 99% of the time it will not be solved by increasing vdimm further past this point. Most of the time 1.9v should suffice for stability with most 2x2GB modules at these speeds and timings.
5. 4GB and 8GB are entirely different animals on this platform and should be treated as such. 8GB will add extra heat to your CPU via the IMC and will also put extra stress on the board. The two primary variables to keep in mind when going from 4GB to 8GB on an AM2+ system are heat and voltage. The former will increase as a side effect of the extra memory and will need to be dealt with in the form of active cooling over the memory and/or better cooling of the CPU. The latter will most likely need to be increased to maintain stability. When going to 8GB, test first, and if it is found to be unstable where previously 4GB was stable, look to gently increase CPU-NB as well as motherboard NB voltages. Increase by .025v increments on CPU-NB first. Do not increase more than .075v at stock CPU-NB speeds as it is unnecessary. If you are still seeing instabilities, look to increase the motherboard NB voltage by the same amount.
6. Always test BEFORE trying to boot into Windows. This will save you a lot of headaches, assist you in the troubleshooting of the issue, and most importantly...it will save your Windows installation! Run Memtest86 for at least 10 loops of test 5 to test initial stability and at least 60 passes to test more thoroughly.
As always, your mileage may vary, but in following these steps you should be able to increase your chances of being able to run 1066 mode.
1. Ensure your motherboard has full Phenom II/1066MHz support from the manufacturer and that you are running the latest BIOS.
2. Do not try to achieve 1066MHz via overclocking the bus or the memory via the 800MHz divider, you will NOT be able to achieve the speeds in this way as the internal memory controller (IMC) timings will still be too tight. Hence, you must first enabled 1066MHz mode specifically to relax these timings.
3. Ensure the memory timings are set loosely enough to accept these speeds. My recommendation would be: CAS 5, TRCD 6, TRP 6, TRAS 24, TRC 30 and a TRFC of 195us or 52-55 (depending on how your motherboard lists it).
4. Max voltage you should ever need for this mode is 2.0v. If you are still noticing instability, 99% of the time it will not be solved by increasing vdimm further past this point. Most of the time 1.9v should suffice for stability with most 2x2GB modules at these speeds and timings.
5. 4GB and 8GB are entirely different animals on this platform and should be treated as such. 8GB will add extra heat to your CPU via the IMC and will also put extra stress on the board. The two primary variables to keep in mind when going from 4GB to 8GB on an AM2+ system are heat and voltage. The former will increase as a side effect of the extra memory and will need to be dealt with in the form of active cooling over the memory and/or better cooling of the CPU. The latter will most likely need to be increased to maintain stability. When going to 8GB, test first, and if it is found to be unstable where previously 4GB was stable, look to gently increase CPU-NB as well as motherboard NB voltages. Increase by .025v increments on CPU-NB first. Do not increase more than .075v at stock CPU-NB speeds as it is unnecessary. If you are still seeing instabilities, look to increase the motherboard NB voltage by the same amount.
6. Always test BEFORE trying to boot into Windows. This will save you a lot of headaches, assist you in the troubleshooting of the issue, and most importantly...it will save your Windows installation! Run Memtest86 for at least 10 loops of test 5 to test initial stability and at least 60 passes to test more thoroughly.
As always, your mileage may vary, but in following these steps you should be able to increase your chances of being able to run 1066 mode.
I'm glad to hear that your RAM has passed with no errors. Dave will have to answer your questions about the RAM timing and speed.
�� Quote: Originally Posted by legend86 Ok, sorry for the delay guys. I ran a memtest 2 nights ago, then went out of town for a couple hours the next day. When I came back, my computer was off. Weird to say the least. Ran one again last night. 7 Passes, 0 Errors.
Another question. My sticks are now running at 800Mhz at 5-5-5-15. Any way I can get it to it's rated 1066? Is it worth it? According to ASUS, they say my MOBO is compatible for this mode.
And this comes from the G.Skill forums:
Note to AMD AM2+ users... - GSKILL TECH FORUM
Another question. My sticks are now running at 800Mhz at 5-5-5-15. Any way I can get it to it's rated 1066? Is it worth it? According to ASUS, they say my MOBO is compatible for this mode.
And this comes from the G.Skill forums:
Quote:
Please be aware that at this point in time 1066MHz support is not guaranteed on every motherboard and CPU. Unfortunately, some boards have a better BIOS than others and as such will offer superior support for a 1066 mode. A few steps to get the best results when attempting 1066 mode.
1. Ensure your motherboard has full Phenom II/1066MHz support from the manufacturer and that you are running the latest BIOS.
2. Do not try to achieve 1066MHz via overclocking the bus or the memory via the 800MHz divider, you will NOT be able to achieve the speeds in this way as the internal memory controller (IMC) timings will still be too tight. Hence, you must first enabled 1066MHz mode specifically to relax these timings.
3. Ensure the memory timings are set loosely enough to accept these speeds. My recommendation would be: CAS 5, TRCD 6, TRP 6, TRAS 24, TRC 30 and a TRFC of 195us or 52-55 (depending on how your motherboard lists it).
4. Max voltage you should ever need for this mode is 2.0v. If you are still noticing instability, 99% of the time it will not be solved by increasing vdimm further past this point. Most of the time 1.9v should suffice for stability with most 2x2GB modules at these speeds and timings.
5. 4GB and 8GB are entirely different animals on this platform and should be treated as such. 8GB will add extra heat to your CPU via the IMC and will also put extra stress on the board. The two primary variables to keep in mind when going from 4GB to 8GB on an AM2+ system are heat and voltage. The former will increase as a side effect of the extra memory and will need to be dealt with in the form of active cooling over the memory and/or better cooling of the CPU. The latter will most likely need to be increased to maintain stability. When going to 8GB, test first, and if it is found to be unstable where previously 4GB was stable, look to gently increase CPU-NB as well as motherboard NB voltages. Increase by .025v increments on CPU-NB first. Do not increase more than .075v at stock CPU-NB speeds as it is unnecessary. If you are still seeing instabilities, look to increase the motherboard NB voltage by the same amount.
6. Always test BEFORE trying to boot into Windows. This will save you a lot of headaches, assist you in the troubleshooting of the issue, and most importantly...it will save your Windows installation! Run Memtest86 for at least 10 loops of test 5 to test initial stability and at least 60 passes to test more thoroughly.
As always, your mileage may vary, but in following these steps you should be able to increase your chances of being able to run 1066 mode.
1. Ensure your motherboard has full Phenom II/1066MHz support from the manufacturer and that you are running the latest BIOS.
2. Do not try to achieve 1066MHz via overclocking the bus or the memory via the 800MHz divider, you will NOT be able to achieve the speeds in this way as the internal memory controller (IMC) timings will still be too tight. Hence, you must first enabled 1066MHz mode specifically to relax these timings.
3. Ensure the memory timings are set loosely enough to accept these speeds. My recommendation would be: CAS 5, TRCD 6, TRP 6, TRAS 24, TRC 30 and a TRFC of 195us or 52-55 (depending on how your motherboard lists it).
4. Max voltage you should ever need for this mode is 2.0v. If you are still noticing instability, 99% of the time it will not be solved by increasing vdimm further past this point. Most of the time 1.9v should suffice for stability with most 2x2GB modules at these speeds and timings.
5. 4GB and 8GB are entirely different animals on this platform and should be treated as such. 8GB will add extra heat to your CPU via the IMC and will also put extra stress on the board. The two primary variables to keep in mind when going from 4GB to 8GB on an AM2+ system are heat and voltage. The former will increase as a side effect of the extra memory and will need to be dealt with in the form of active cooling over the memory and/or better cooling of the CPU. The latter will most likely need to be increased to maintain stability. When going to 8GB, test first, and if it is found to be unstable where previously 4GB was stable, look to gently increase CPU-NB as well as motherboard NB voltages. Increase by .025v increments on CPU-NB first. Do not increase more than .075v at stock CPU-NB speeds as it is unnecessary. If you are still seeing instabilities, look to increase the motherboard NB voltage by the same amount.
6. Always test BEFORE trying to boot into Windows. This will save you a lot of headaches, assist you in the troubleshooting of the issue, and most importantly...it will save your Windows installation! Run Memtest86 for at least 10 loops of test 5 to test initial stability and at least 60 passes to test more thoroughly.
As always, your mileage may vary, but in following these steps you should be able to increase your chances of being able to run 1066 mode.
The specific RAM timings and voltage settings mentioned here will be different for the different MOBO and RAM model configurations.
This is a good general guideline, unless your running the exact MOBO and exact RAM, these numbers will vary.
The 1066 support will depend on your motherboard and BIOS.
Is it worth it?
Depending on what you do with your computer, you will likely not notice the difference.
Just remember, any overclocking can potentially damage your hardware, continue at your own risk.
You can try it and check for stability.
Manually set the timings as per the CPUZ SPD tab for EPP#1.
Frequency 533MHz
CAS# Latency 5
RAS# to CAS# 5
RAS# precharge 5
tRAS 15
tRC 48
Command Rate 2T
Leave all other timing settings on Auto.
Check what the DRAM voltage is set at, it should be on AUTO when you re-set the BIOS to defaults.
From the previous settings, JEDEC #2, it should be at 1.8v.
Manually set it to 2.1v.
Check for stability, run memtest86+ for at least 10 passes.
If you get errors, you will need to bump the CPU-NB voltage, slowly and be careful to do these steps exactly as described in the G.Skill post.
Quote:
Gently increase CPU-NB as well as motherboard NB voltages. Increase by .025v increments on CPU-NB first. Do not increase more than .075v at stock CPU-NB speeds as it is unnecessary. If you are still seeing instabilities, look to increase the motherboard NB voltage by the same amount.
The first thing to do is get it running stable at recommended settings.
Let us know if you have any questions and keep us updated with your progress.
^^^
Thank you. I'll save this information for later. I think after all this I'm just glad to have my computer workin' again. Been about 4 days now with no BSODs so I'm more than happy. I've done enough tweaking and memtesting for a while.
If I ever decide to tinker around with the memory though, I'll let you guys know. I appreciate all the help you all have given me.
Thank you. I'll save this information for later. I think after all this I'm just glad to have my computer workin' again. Been about 4 days now with no BSODs so I'm more than happy. I've done enough tweaking and memtesting for a while.
If I ever decide to tinker around with the memory though, I'll let you guys know. I appreciate all the help you all have given me.
Glad it's running stable for you.
Enjoy it and if you decide to adjust the RAM later just let us know if you have any questions.
Enjoy it and if you decide to adjust the RAM later just let us know if you have any questions.
That is good to hear. Thank you for reporting back - and a good job of following suggestions.
Dave knows his stuff and I thank him for his help.
Happy computing and don't be a stranger to the forum.
Dave knows his stuff and I thank him for his help.
Happy computing and don't be a stranger to the forum.
Không có nhận xét nào:
Đăng nhận xét