I have been getting bsods since this computer was built I fix them for awhile and they keep coming back. they seem to be related to ntoskrnl this time I have run memtest several times with no errors. here are my latest minidumps
Your zip files contains only the crash file, the other information will help us to find the problem.
Go to this link and post all of the files requested:
Blue Screen of Death (BSOD) Posting Instructions
Your last two crashes are labeled STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED.
This is a very common bug check, the other requested files/info will help to find the cause.
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This can be caused by just about anything, as mentioned, we need more information.
Code:******************************************************************************* * * * 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: +3762306232393830 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: fffff880031ae158 -- (.exr 0xfffff880031ae158) ExceptionAddress: fffff8800178dfcf (tcpip+0x00000000000b8fcf) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff880031ae200 -- (.trap 0xfffff880031ae200) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0002000000000000 rbx=0000000000000000 rcx=fffffa800650ae40 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800178dfcf rsp=fffff880031ae390 rbp=0000000000000007 r8=0000000000000000 r9=000000000166be5b r10=fffffa800650ae40 r11=fffff880031ae468 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc tcpip+0xb8fcf: fffff880`0178dfcf 488b48d0 mov rcx,qword ptr [rax-30h] ds:0004:0001ffff`ffffffd0=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ec55fe to fffff80002ecdc10 STACK_TEXT: fffff880`031ad238 fffff800`02ec55fe : fffffa80`06e0f501 fffffa80`06df5850 fffff880`031ad9b0 fffff800`02ef9830 : nt!KeBugCheck fffff880`031ad240 fffff800`02ef94fd : fffff800`030d771c fffff800`03014c30 fffff800`02e51000 fffff880`031ae158 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`031ad270 fffff800`02ef82d5 : fffff800`030180fc fffff880`031ad2e8 fffff880`031ae158 fffff800`02e51000 : nt!RtlpExecuteHandlerForException+0xd fffff880`031ad2a0 fffff800`02f09361 : fffff880`031ae158 fffff880`031ad9b0 fffff880`00000000 fffffa80`0650a000 : nt!RtlDispatchException+0x415 fffff880`031ad980 fffff800`02ecd2c2 : fffff880`031ae158 00000000`00000000 fffff880`031ae200 00000000`00000e00 : nt!KiDispatchException+0x135 fffff880`031ae020 fffff800`02ecbbca : 00000000`00000000 fffff880`031ae280 fffffa80`0650a000 00000000`00000007 : nt!KiExceptionDispatch+0xc2 fffff880`031ae200 fffff880`0178dfcf : fffffa80`063b9e98 fffff880`01751368 fffffa80`05c35890 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a fffff880`031ae390 fffff880`01751d39 : 00000000`00000000 00000000`00039662 fffffa80`063c8d40 fffffa80`0166be5b : tcpip+0xb8fcf fffff880`031ae470 fffff800`02ed95fc : fffff880`03186180 00000000`00000007 fffff880`031ae600 00000000`00000000 : tcpip+0x7cd39 fffff880`031ae570 fffff800`02ed9496 : fffffa80`0650fab8 00000000`00e59a1f 00000000`00000000 00000000`00000007 : nt!KiProcessTimerDpcTable+0x6c fffff880`031ae5e0 fffff800`02ed937e : 00000223`69f65931 fffff880`031aec58 00000000`00e59a1f fffff880`03188968 : nt!KiProcessExpiredTimerList+0xc6 fffff880`031aec30 fffff800`02ed9167 : 000000a4`58b0bec1 000000a4`00e59a1f 000000a4`58b0be91 00000000`0000001f : nt!KiTimerExpiration+0x1be fffff880`031aecd0 fffff800`02ec596a : fffff880`03186180 fffff880`031910c0 00000000`00000000 fffff880`044acdb0 : nt!KiRetireDpcList+0x277 fffff880`031aed80 00000000`00000000 : fffff880`031af000 fffff880`031a9000 fffff880`031aed40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: tcpip+b8fcf fffff880`0178dfcf 488b48d0 mov rcx,qword ptr [rax-30h] SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: tcpip+b8fcf FOLLOWUP_NAME: MachineOwner MODULE_NAME: tcpip IMAGE_NAME: tcpip.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e83e948 FAILURE_BUCKET_ID: X64_0x1E_0_tcpip+b8fcf BUCKET_ID: X64_0x1E_0_tcpip+b8fcf Followup: MachineOwner ---------
STOP 0x00000034: CACHE_MANAGER
Usual causes: Insufficient physical memory, Indexing, Device driver
Cause: One possible cause of this bug check 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.
Run memtest86+ for a minimum of 7 full passes.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CACHE_MANAGER (34) See the comment for FAT_FILE_SYSTEM (0x23) Arguments: Arg1: 0000000000050853 Arg2: fffff88003346298 Arg3: fffff88003345af0 Arg4: fffff80002f1723c Debugging Details: ------------------ EXCEPTION_RECORD: fffff88003346298 -- (.exr 0xfffff88003346298) ExceptionAddress: fffff80002f1723c (nt!MiUpdateWsleHash+0x000000000000013c) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff88003345af0 -- (.cxr 0xfffff88003345af0) rax=0000058000000000 rbx=fffbf98057e53c01 rcx=0000000000000080 rdx=000fffffffffffff rsi=fffff780c0000000 rdi=003ff6818015f94c rip=fffff80002f1723c rsp=fffff880033464d0 rbp=0000007ffffffff8 r8=fffffa8001829640 r9=ffffffff00000000 r10=fffff6fb40c00af8 r11=fffff880033464a0 r12=0000000000000000 r13=fffff80003119ac0 r14=fffff80003119ac0 r15=0000000000005773 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 nt!MiUpdateWsleHash+0x13c: fffff800`02f1723c 44893f mov dword ptr [rdi],r15d ds:002b:003ff681`8015f94c=???????? 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_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 fffff80003116100 ffffffffffffffff FOLLOWUP_IP: nt!MiUpdateWsleHash+13c fffff800`02f1723c 44893f mov dword ptr [rdi],r15d FAULTING_IP: nt!MiUpdateWsleHash+13c fffff800`02f1723c 44893f mov dword ptr [rdi],r15d BUGCHECK_STR: 0x34 LAST_CONTROL_TRANSFER: from fffff80002f48269 to fffff80002f1723c STACK_TEXT: fffff880`033464d0 fffff800`02f48269 : fffff780`c002c020 ffffffff`ffffffff ffffffff`ffffffff fffff800`00000000 : nt!MiUpdateWsleHash+0x13c fffff880`03346540 fffff800`02ef795b : 00000000`00000001 00000000`0014a998 fffff780`c0000000 fffff780`c0000488 : nt! ?? ::FNODOBFM::`string'+0x21cb9 fffff880`033465c0 fffff800`02f07eee : 00000000`00000000 fffffa80`05d07cf0 00000000`00000000 fffff880`009b2180 : nt!MiChargeWsles+0x3ab fffff880`03346600 fffff800`02f07d54 : fffffa80`05d07cf0 fffffa80`00483c90 00000000`00000000 00000000`00000000 : nt!MiReleaseSystemCacheView+0x36 fffff880`03346740 fffff800`031f4c39 : fffff980`41180000 fffff8a0`0d98d1d0 00000000`00000000 00000000`00000000 : nt!MmUnmapViewInSystemCache+0x674 fffff880`03346a20 fffff800`02f0742b : 00000000`10100000 fffffa80`08b6ccf0 00000000`00000000 00000000`40100000 : nt!CcUnmapVacb+0x5d fffff880`03346a60 fffff800`02f28a08 : 00000000`00000001 fffffa80`078e1dd0 fffffa80`094c9600 fffffa80`094c9700 : nt!CcUnmapVacbArray+0x1bb fffff880`03346af0 fffff800`02f292fe : fffffa80`094c9600 fffffa80`094c9600 fffff880`009b2180 fffffa80`094c9700 : nt!CcDeleteSharedCacheMap+0x154 fffff880`03346b50 fffff800`02f29938 : fffff880`00000000 fffff880`03346c58 fffffa80`06da05a0 fffff800`030e58b8 : nt!CcWriteBehind+0x54e fffff880`03346c00 fffff800`02eee001 : fffffa80`05560190 fffff800`031da901 fffff800`030e58c0 00000000`00000000 : nt!CcWorkerThread+0x1c8 fffff880`03346cb0 fffff800`0317efee : c2aded5d`92184a09 fffffa80`05552b60 00000000`00000080 fffffa80`0548db30 : nt!ExpWorkerThread+0x111 fffff880`03346d40 fffff800`02ed55e6 : fffff880`03186180 fffffa80`05552b60 fffff880`031910c0 188765ca`5da8dd8c : nt!PspSystemThreadStartup+0x5a fffff880`03346d80 00000000`00000000 : fffff880`03347000 fffff880`03341000 fffff880`03346510 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MiUpdateWsleHash+13c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 STACK_COMMAND: .cxr 0xfffff88003345af0 ; kb IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x34_nt!MiUpdateWsleHash+13c BUCKET_ID: X64_0x34_nt!MiUpdateWsleHash+13c Followup: MachineOwner ---------
When you run memtest86+ you are looking for bad RAM cards, bad motherboard slots, so you need to follow the testing procedure in the tutorial.
Sometimes errors from these tests can be corrected by adjusting the settings.
RAM - Test with Memtest86+
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Have you been checking your temperatures?
Use Real Temp, to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
This is important in order to continue.
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.
I ran memtest again for 8 passes this time I removed a stick and still had no errors. all voltages are on auto so I cant get them. I do monitor my temps and never get over 71 under load and my cpu tj max is 100c. I have also been having problems with my display drivers failing then restarting. I have the latest drivers installed tried to roll them back but it still happens. When I went to get cpu voltage this morning computer would not shut down and had to shut down manually and it took it for ever to boot back up. I have had boot issues every since this build. Computer is not even a yr old yet been think I might have had memory problems all along but I never fail memtest. I have attached my system report and my cpuz.http://valid.canardpc.com/show_oc.php?id=2176304
Last edited by JDMorrison; 01 Jan 2012 at 14:13.
Your 'System Zip Report' is still not complete, the other files requested will have the information needed to analyze your system.
Run the full set of data files: Blue Screen of Death (BSOD) Posting Instructions
Set your voltages to 'Manual' then you can see them, get the voltage and set it back to 'Auto' for now.
Intel® Core™ i7-950 Processor
Your max CPU case temp is 67.9°C, add 5°C for max core temps of 72.9°C.
Many OC'ers go past this but, I like to stay under that limit. The OC'ers are taking a chance that the CPU will fail, their choice if they want to risk buying a new one.
You are very close to the max Intel recommended temp, check that your CPU cooler is firmly attached. Best to remove it and re-apply the thermal paste.
This should bring the temps down.
You can get a good after market CPU cooler for $20-50, good investment.
Quote