New
#11
seem to have made things worse. Downloading something from the internet and had 3 BSOD.
All the causes seem to be due to ntoskrnl.exe or ntkrnlmp.exe. Maybe I should RMA the RAM and Mobo to be sure
seem to have made things worse. Downloading something from the internet and had 3 BSOD.
All the causes seem to be due to ntoskrnl.exe or ntkrnlmp.exe. Maybe I should RMA the RAM and Mobo to be sure
What kind(s) of RAM do you have? Can you list each module and its manufacturer?
Nevermind, are those the ones listed in the system specs? If so, did you buy them at the same time?
See http://download.gigabyte.us/FileList...a-870a-ud3.pdf for compatible ram for your motherboard.
I also just read Post #44 of your previous thread, and I noted that you were told the RAM may not be compatible with the AMD motherboard. Do you still have the problem in Memtest86+ with slots 2 and 4?
Last edited by writhziden; 08 Jan 2012 at 18:20. Reason: reread the previous thread
I also note that you have a new BIOS update available that is supposed to fix RAM voltage issues. May be worth looking into with Dave76 when he responds. GIGABYTE - Motherboard - Socket AM3 - GA-870A-UD3 (rev. 2.0)
I installed the latest BIOS (F5) this morning, didn't notice any change. I'm still using the same RAM, I'm pretty sure I reran MemTest after the CPU RMA and still had errors but that was a while ago so not completely sure anymore
Sorry to see you are still having the same issues.
The BIOS update is a good idea.
This comes down to RAM compatibility, it's a known issue, AMD has had so many issues with this that they are now selling their own AMD Memory.
AMD Memory for Systems
Run memtest86+ again to be sure the RAM is not faulty.
Minimum 7 full passes, best to run over night.
Down load the crash dump files and I'll take a look at them.
We can see if there might be anything else causing issues.
Blue Screen of Death (BSOD) Posting Instructions
When posting a new crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes.
Be sure to add all the files requested.
To ensure minidumps are enabled:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.
Last edited by Dave76; 09 Jan 2012 at 08:05.
attached the dump files and reports.
I'm about to go to work so I'll run memtest now and post an update later.
I've been using AMD processors and Corsair RAM for the past 8 years now and this is the first time I've ran into problems. I just don't know if it's faulty or compatibility issues
The recent changes in CPU architecture has made it more difficult to get RAM to run on both AMD and Intel CPUs.
Let us know how the memtest86+ run goes.
Your last crash is STOP 0x00000024: NTFS_FILE_SYSTEM
Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
Cause:
One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.
Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.
This is due to a memory referenced error.
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUALCode:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 00000000001904fb Arg2: fffff88005bc77d8 Arg3: fffff88005bc7040 Arg4: fffff80002ff0000 Debugging Details: ------------------ EXCEPTION_RECORD: fffff88005bc77d8 -- (.exr 0xfffff88005bc77d8) ExceptionAddress: fffff80002ff0000 (nt!ExDeferredFreePool+0x0000000000000174) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff88005bc7040 -- (.cxr 0xfffff88005bc7040) rax=004d0053005f004c rbx=0000000000000002 rcx=fffffa800395c760 rdx=fffff8a022502bc0 rsi=0000000000000000 rdi=fffff8a0198e5010 rip=fffff80002ff0000 rsp=fffff88005bc7a10 rbp=0000000000000000 r8=fffff8a01983a4c0 r9=fffff8a022502af0 r10=fffff8a022502b00 r11=0000000000000001 r12=fffffa800395c280 r13=0000000000000000 r14=0000000000000009 r15=0000000000000001 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 nt!ExDeferredFreePool+0x174: fffff800`02ff0000 4c395008 cmp qword ptr [rax+8],r10 ds:002b:004d0053`005f0054=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: TrustedInstall CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_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: ffffffffffffffff FOLLOWUP_IP: nt!ExDeferredFreePool+174 fffff800`02ff0000 4c395008 cmp qword ptr [rax+8],r10 FAULTING_IP: nt!ExDeferredFreePool+174 fffff800`02ff0000 4c395008 cmp qword ptr [rax+8],r10 BUGCHECK_STR: 0x24 LAST_CONTROL_TRANSFER: from fffff80002ff14c1 to fffff80002ff0000 STACK_TEXT: fffff880`05bc7a10 fffff800`02ff14c1 : fffffa80`04a2b180 fffff8a0`19604450 fffffa80`06b92310 fffff880`012b754f : nt!ExDeferredFreePool+0x174 fffff880`05bc7aa0 fffff880`012bf290 : fffff8a0`19604460 fffff880`0737f4b0 fffff880`4146744e fffffa80`0a997010 : nt!ExFreePoolWithTag+0x411 fffff880`05bc7b50 fffff880`0122998d : fffffa80`0a997010 fffffa80`06b92310 fffff880`0737f4b0 fffffa80`03b25000 : Ntfs!NtfsCommonCreate+0x22f9 fffff880`05bc7d30 fffff800`02eb4447 : fffff880`0737f420 2c36866a`4eb3b04c 0662309c`7b968e9c 37820104`01062b0a : Ntfs!NtfsCommonCreateCallout+0x1d fffff880`05bc7d60 fffff800`02eb4401 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27 fffff880`0737f2f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!ExDeferredFreePool+174 FOLLOWUP_NAME: Pool_corruption IMAGE_NAME: Pool_Corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: Pool_Corruption STACK_COMMAND: .cxr 0xfffff88005bc7040 ; kb FAILURE_BUCKET_ID: X64_0x24_nt!ExDeferredFreePool+174 BUCKET_ID: X64_0x24_nt!ExDeferredFreePool+174 Followup: Pool_corruption ---------
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The MSE driver MsMpEng.exe was indicated, this is a result of the cause of the crash, the RAM.
STOP 0x0000001A: MEMORY_MANAGEMENTCode:******************************************************************************* * * * 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: 0000000000000010, 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: fffff80002ea8a4f, address which referenced memory
Usual causes: Device driver, memory, kernel
This indicates that a severe memory management error occurred.
STOP 0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_MCode:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000008884, The subtype of the bugcheck. Arg2: fffffa800046b9c0 Arg3: fffffa800046b7b0 Arg4: 0000000000000605 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x1a_8884_nt!MiRelinkStandbyPage+c6 BUCKET_ID: X64_0x1a_8884_nt!MiRelinkStandbyPage+c6
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.
This bug check indicates that a system thread generated an exception that the error handler did not catch.
Also indicating the RAM issue.
STOP 0x00000019: BAD_POOL_HEADERCode:******************************************************************************* * * * 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: fffff80002df6000, The address that the exception occurred at Arg3: fffff88002c7a4b8, Exception Record Address Arg4: fffff88002c79d20, 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!ExDeferredFreePool+174 fffff800`02df6000 4c395008 cmp qword ptr [rax+8],r10 EXCEPTION_RECORD: fffff88002c7a4b8 -- (.exr 0xfffff88002c7a4b8) ExceptionAddress: fffff80002df6000 (nt!ExDeferredFreePool+0x0000000000000174) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff88002c79d20 -- (.cxr 0xfffff88002c79d20) rax=0072006500730055 rbx=0000000000000004 rcx=fffffa800395d670 rdx=fffff8a0093eea40 rsi=0000000000000000 rdi=fffff8a007d302a0 rip=fffff80002df6000 rsp=fffff88002c7a6f0 rbp=0000000000000000 r8=fffff8a0025c6830 r9=fffff8a0093ee950 r10=fffff8a0093ee960 r11=0000000000000001 r12=fffffa800395d500 r13=0000000000000000 r14=000000000000000d r15=0000000000000001 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 nt!ExDeferredFreePool+0x174: fffff800`02df6000 4c395008 cmp qword ptr [rax+8],r10 ds:002b:00720065`0073005d=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_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 fffff80002efa0e0 ffffffffffffffff FOLLOWUP_IP: nt!ExDeferredFreePool+174 fffff800`02df6000 4c395008 cmp qword ptr [rax+8],r10 BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff80002df74c1 to fffff80002df6000 STACK_TEXT: fffff880`02c7a6f0 fffff800`02df74c1 : fffffa80`05787000 fffff8a0`08ea0140 00000000`00000008 fffffa80`03e30400 : nt!ExDeferredFreePool+0x174 fffff880`02c7a780 fffff880`14b681db : fffff8a0`08bdb9a0 fffff8a0`08bdb9a0 fffffa80`6d4d6956 fffff8a0`00000174 : nt!ExFreePoolWithTag+0x411 fffff880`02c7a830 fffff880`14b67d9c : fffffa80`05790d90 fffff8a0`08bdb9a0 fffff8a0`08bdb9a0 00000000`00000000 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnlockAllocationRange+0x10f fffff880`02c7a890 fffff880`14b5b76c : fffffa80`05787000 fffffa80`05787000 fffff8a0`08ddcc78 fffffa80`05787000 : dxgmms1!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0xdc fffff880`02c7a8d0 fffff880`14b58133 : 00000000`00000000 00000000`00000000 00000000`00000044 fffffa80`05787000 : dxgmms1!VIDMM_GLOBAL::EvictTemporaryAllocations+0xbc fffff880`02c7a910 fffff880`14b7265d : 00000000`00000000 fffff8a0`0255f2d0 fffffa80`00000000 fffffa80`04c6c400 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x69f fffff880`02c7aae0 fffff880`14b72398 : fffff880`02f67f00 fffff880`14b71d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241 fffff880`02c7acd0 fffff880`14b71e96 : 00000000`00000000 fffffa80`046fd450 00000000`00000080 fffffa80`0575c370 : dxgmms1!VidSchiSubmitQueueCommand+0x50 fffff880`02c7ad00 fffff800`02f626fa : 00000000`033b666e fffffa80`05778060 fffffa80`039ea040 fffffa80`05778060 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`02c7ad40 fffff800`02ca0b46 : fffff880`02f63180 fffffa80`05778060 fffff880`02f6df80 fffff880`012662b4 : nt!PspSystemThreadStartup+0x5a fffff880`02c7ad80 00000000`00000000 : fffff880`02c7b000 fffff880`02c75000 fffff880`02c79ea0 00000000`00000000 : nt!KiStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!ExDeferredFreePool+174 FOLLOWUP_NAME: Pool_corruption IMAGE_NAME: Pool_Corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: Pool_Corruption STACK_COMMAND: .cxr 0xfffff88002c79d20 ; kb FAILURE_BUCKET_ID: X64_0x7E_nt!ExDeferredFreePool+174 BUCKET_ID: X64_0x7E_nt!ExDeferredFreePool+174 Followup: Pool_corruption
Usual causes: Device driver.
STOP 0x0000001A: MEMORY_MANAGEMENTCode:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 0000000000000020, a pool block header size is corrupt. Arg2: fffff8a00ad658b0, The pool entry we were looking for within the page. Arg3: fffff8a00ad659c0, The next pool entry. Arg4: 000000000511040a, (reserved)
This indicates that a severe memory management error occurred.
All the crashes above are consistent with a memory issue.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000008884, The subtype of the bugcheck. Arg2: fffffa800357f9c0 Arg3: fffffa800357fcf0 Arg4: 0000000000000506 IMAGE_NAME: memory_corruption
What anti-virus are you using?
This is a driver for a tablet, Wacom(tablet) Mouse Filter
Find this and disable or un-install.Code:wacommousefilter.sys Sat Feb 17 02:12:17 2007
Have you installed all of the Windows updates?
System event logs:
Update the MSE definitions.Code:Event[257]: Log Name: System Source: Microsoft Antimalware Date: 2012-01-08T23:42:06.000 Event ID: 3002 Task: N/A Level: Error Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: SAMCRO Description: Microsoft Antimalware Real-Time Protection feature has encountered an error and failed. Feature: Behavior Monitoring Error Code: 0x80004005 Error description: Unspecified error Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection. Event[393]: Log Name: System Source: Microsoft Antimalware Date: 2012-01-08T23:27:18.000 Event ID: 3002 Task: N/A Level: Error Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: SAMCRO Description: Microsoft Antimalware Real-Time Protection feature has encountered an error and failed. Feature: Behavior Monitoring Error Code: 0x80004005 Error description: Unspecified error Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.
Code:Event[417]: Log Name: System Source: Application Popup Date: 2012-01-08T23:27:05.000 Event ID: 26 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: SAMCRO Description: Application popup: msnmsgr.exe - System Error : The program can't start because wlidcli.dll is missing from your computer. Try reinstalling the program to fix this problem.
Application event logs:
Install an updated version, if you have the latest then un-install and re-install.Code:Event[112]: Log Name: Application Source: Windows Error Reporting Date: 2012-01-08T23:48:57.000 Event ID: 1001 Task: N/A Level: Information Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: SAMCRO Description: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: AUDIODG.EXE P2: 6.1.7600.16385 P3: 4a5bced5 P4: MMDevAPI.DLL P5: 6.1.7600.16385 P6: 4a5bdf68 P7: c0000005 P8: 000000000001b4ee P9: P10:
Last edited by Dave76; 09 Jan 2012 at 09:41.
Put my comments below in red
Your last crash is STOP 0x00000024: NTFS_FILE_SYSTEM
Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
I have one HDD that's not the boot drive (might be the drive used for virtual memory now that you mention it) that SpeedFan SMART reports tells me is beginning to fail.
All the crashes above are consistent with a memory issue.Code:/Snip
What anti-virus are you using? I'm using MSE. There is something installed from McAfee but it only tells me whether or not my computer is safe, not actually an anti-Virus software, I will uninstall that when I get home
This is a driver for a tablet, Wacom(tablet) Mouse Filter
Find this and disable or un-install. It's the driver for my graphics tablet I received at Christmas. I assume I can reinstall it once we locate this problemCode:wacommousefilter.sys Sat Feb 17 02:12:17 2007
Have you installed all of the Windows updates? Not all, some install then I get a bluescreen. I can keep at it until all are installed if necessary
System event logs:
Update the MSE definitions. Will doCode:/snip
Will uninstall for the time beingCode:Application popup: msnmsgr.exe - System Error : The program can't start because wlidcli.dll is missing from your computer. Try reinstalling the program to fix this problem.
Application event logs:
Install an updated version, if you have the latest then un-install and re-install Install an updated version of what exactly? Don't quite understand the logsCode:Problem signature: P1: AUDIODG.EXE P2: 6.1.7600.16385 P3: 4a5bced5 P4: MMDevAPI.DLL P5: 6.1.7600.16385 P6: 4a5bdf68 P7: c0000005 P8: 000000000001b4ee P9: P10:
Also, before I left the front door this morning, I saw a red line in MemTest, which I guess is an error during the first pass. Both RAM sticks are in slots 1 & 2, and MemTest says it's clocked at 666MHz. Does this mean faulty RAM or compatibility issue?
just back from work. Just started pass 10 and there were 363 errors.