New
#21
Your last verifier enabled .dmp file you uploaded indicates hardware as a likely cause:Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\corp25\040212-18049-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16917.amd64fre.win7_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02e5f000 PsLoadedModuleList = 0xfffff800`0309be70 Debug session time: Mon Apr 2 22:43:31.414 2012 (UTC - 6:00) System Uptime: 0 days 6:27:24.320 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffff8000316e726, 0, 0, fffff80002efc032} Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 ) Followup: MachineOwner --------- 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffff8000316e726, memory referenced Arg2: 0000000000000000, IRQL Arg3: 0000000000000000, 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: fffff80002efc032, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031060e0 fffff8000316e726 CURRENT_IRQL: 0 FAULTING_IP: nt!RtlDispatchException+122 fffff800`02efc032 410fb60c24 movzx ecx,byte ptr [r12] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880033d17f0 -- (.trap 0xfffff880033d17f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff800030edd00 rbx=0000000000000000 rcx=fffff8000316e770 rdx=fffff8000316e6cc rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002efc032 rsp=fffff880033d1980 rbp=fffff880033d2828 r8=0000000000001fc0 r9=0000000000001fbf r10=fffff880033d2d00 r11=fffff880033d19c8 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!RtlDispatchException+0x122: fffff800`02efc032 410fb60c24 movzx ecx,byte ptr [r12] ds:c151:00000000`00000000=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002eceaa9 to fffff80002ecf540 STACK_TEXT: fffff880`033d16a8 fffff800`02eceaa9 : 00000000`0000000a fffff800`0316e726 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx fffff880`033d16b0 fffff800`02ecd720 : 00000000`00000000 00000000`0000005a 0002408e`00034900 0003f043`0002a00e : nt!KiBugCheckDispatch+0x69 fffff880`033d17f0 fffff800`02efc032 : fffff800`0316e726 fffff880`033d19c8 fffff880`033d2828 fffff800`02e5f000 : nt!KiPageFault+0x260 fffff880`033d1980 fffff800`02f093af : fffff880`033d2828 fffff880`033d2090 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x122 fffff880`033d2060 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16f STACK_COMMAND: kb FOLLOWUP_IP: nt!RtlDispatchException+122 fffff800`02efc032 410fb60c24 movzx ecx,byte ptr [r12] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!RtlDispatchException+122 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ec7a284 FAILURE_BUCKET_ID: X64_0xA_VRF_nt!RtlDispatchException+122 BUCKET_ID: X64_0xA_VRF_nt!RtlDispatchException+122 Followup: MachineOwner ---------
- If you are overclocking any hardware, please stop.
- Monitor temperatures during the following tests.
Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
- Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
- Follow the steps for doing a CPU stress test using IntelBurnTest
How many passes did you let Memtest86+ run? Also, since Memtest86+ is not foolproof, can you give us an idea of your RAM settings?
- Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.
Quote