Bsod IRQL_NOT_LESS_OR_EQUAL Bug Check Code : 0x0000000a

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [K:\BSODDmpFiles\Moteo\Windows_NT6_BSOD_jcgriff2\012512-32339-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0324e000 PsLoadedModuleList = 0xfffff800`03493670
Debug session time: Tue Jan 24 18:03:52.230 2012 (GMT-7)
System Uptime: 0 days 0:36:37.073
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa804d5e9010, 2, 0, fffff800032b3618}

Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+c8 )

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

2: 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: fffffa804d5e9010, memory referenced
Arg2: 0000000000000002, 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: fffff800032b3618, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034fd100
 fffffa804d5e9010 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiRestoreTransitionPte+c8
fffff800`032b3618 488b18          mov     rbx,qword ptr [rax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800a0b2530 -- (.trap 0xfffff8800a0b2530)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa804d5e9010 rbx=0000000000000000 rcx=fffff88003195033
rdx=0000098000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032b3618 rsp=fffff8800a0b26c0 rbp=0000000000000001
 r8=0000000000000001  r9=0000000000000001 r10=0000000000000002
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!MiRestoreTransitionPte+0xc8:
fffff800`032b3618 488b18          mov     rbx,qword ptr [rax] ds:04c0:fffffa80`4d5e9010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032ca1e9 to fffff800032cac40

STACK_TEXT:  
fffff880`0a0b23e8 fffff800`032ca1e9 : 00000000`0000000a fffffa80`4d5e9010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a0b23f0 fffff800`032c8e60 : 00000000`00000000 fffff800`03493f40 fffffa80`109e2780 fffffa80`06496860 : nt!KiBugCheckDispatch+0x69
fffff880`0a0b2530 fffff800`032b3618 : fffffa80`06496860 00000000`00000001 00000000`00000000 00000000`00000080 : nt!KiPageFault+0x260
fffff880`0a0b26c0 fffff800`033187ad : 00000000`00000002 fffff800`00000001 fffffa80`06496860 fffff8a0`0d76ecf8 : nt!MiRestoreTransitionPte+0xc8
fffff880`0a0b2750 fffff800`0328f29f : fa800ceb`9bb004c0 fa800ceb`9bb004c0 fffff880`0a0b2840 00000000`000000e2 : nt!MiRemoveLowestPriorityStandbyPage+0x1d5
fffff880`0a0b27d0 fffff800`035674ea : fffffa80`0d5fc540 fffffa80`00000001 fffffa80`0d5fc540 00000000`00000005 : nt!MiPfPutPagesInTransition+0x826
fffff880`0a0b2940 fffff800`03276d37 : fffffa80`0d5fc540 00000000`34110000 00000000`34110000 fffff800`0346b260 : nt!MmPrefetchForCacheManager+0x8e
fffff880`0a0b2990 fffff800`0331098e : fffffa80`0f0b2070 fffffa80`00000000 00000000`00000000 fffff800`034cc8b8 : nt!CcPerformReadAhead+0x2f3
fffff880`0a0b2ac0 fffff800`032d5001 : fffffa80`0ce061a0 fffff800`035c1901 fffff800`034cc8d0 00000000`00000002 : nt!CcWorkerThread+0x21e
fffff880`0a0b2b70 fffff800`03565fee : fffff880`09a40f68 fffffa80`109e2780 00000000`00000080 fffffa80`0cd02890 : nt!ExpWorkerThread+0x111
fffff880`0a0b2c00 fffff800`032bc5e6 : fffff880`03165180 fffffa80`109e2780 fffff880`031700c0 fffff880`0125b384 : nt!PspSystemThreadStartup+0x5a
fffff880`0a0b2c40 00000000`00000000 : fffff880`0a0b3000 fffff880`0a0ad000 fffff880`0a0b28a0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRestoreTransitionPte+c8
fffff800`032b3618 488b18          mov     rbx,qword ptr [rax]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiRestoreTransitionPte+c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiRestoreTransitionPte+c8

BUCKET_ID:  X64_0xA_nt!MiRestoreTransitionPte+c8

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

Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Antivirus Software...

Thanks to Dave76 for help understanding possible causes.



We will start with the most likely problems first.

• If you are overclocking anything, please stop.
  
  
  
• Remove Tune Up Utilities as it is known to cause crashes due to its "optimization" techniques. I highly recommend avoiding automated registry cleaning tools like those used by this software.
  
  Code:

  TuneUpUtilitiesDriver64	fffff880`0c8c0000	fffff880`0c8c8000	Thu Sep 17 05:54:52 2009 (4ab2238c)	000052de		TuneUpUtilitiesDriver64.sys

  If you would like to optimize Windows, the best method is to post a thread in Performance & Maintenance - Windows 7 Forums asking for optimization methods, or you may refer to the tutorials on that forum for optimization techniques, such as Optimize Windows 7
  
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  
  
• 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. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
  
  
  
• 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.

Moteo said:

Well the crashes started before i installed tuneup....even the first time i turned it on after building it the blue screen appeared! i ran furmark no problems were detected an i ran memetest last night but it only took 15 minutes an gave me a pass should i let it contiune for longer after the first one??ok i downloaded the prime test but am kinda confused on how to run it or how it works tbh! i know am a noob! oh forgot to mention i have an asus motherboard p8p67 pro rev 3.1 if thats any help! an no am not overclock anything. thanks for your help!

Memtest should be run for 7 passes.

There is also a video memory stress test in addition to Furmark that should be run.

The link for prime95 on these forums gives instructions for how to run it. Run all three tests for a few hours each. If you get errors, stop the test and post back here.