BSOD error Stop 0xa - IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe

Problem Devices:

Code:

Not Available	ACPI\ATK0110\1010110	The drivers for this device are not installed.

Older versions of ASACPI.SYS are a known BSOD problem on Windows 7. Install a newer driver by:

1. Going to the Asus motherboard support site
   When you reach the website:
2. Scroll down the page and click Utilities
3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
4. Search for "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" (without quotes)
5. Download and install the driver.
6. After installation is complete, verify that it installed correctly.
   
   • Click Start Menu
   • Click My Computer
   • Go to C:\WIndows\System32\drivers\
   • Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)

Security Software: ??? Recommend either of these two:

• Microsoft Security Essentials - Free Antivirus for Windows
  
  
• Good and Free system security combination.

Update the Security Software and run a full scan for viruses/malware.


Download and install all Windows Updates.

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\Outc4sted\Windows_NT6_BSOD_jcgriff2\041412-18345-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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c53000 PsLoadedModuleList = 0xfffff800`02e90e50
Debug session time: Sat Apr 14 17:47:01.140 2012 (UTC - 6:00)
System Uptime: 0 days 0:01:49.264
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff80402ec3b5c, 2, 0, fffff80002d7d83d}

Probably caused by : ntkrnlmp.exe ( nt!PpmPerfChooseCoresToUnpark+36d )

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

4: 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: fffff80402ec3b5c, 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: fffff80002d7d83d, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efb0e0
 fffff80402ec3b5c 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!PpmPerfChooseCoresToUnpark+36d
fffff800`02d7d83d 418b8c90600b2700 mov     ecx,dword ptr [r8+rdx*4+270B60h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880009fd910 -- (.trap 0xfffff880009fd910)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000008 rbx=0000000000000000 rcx=fffff80002c53000
rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d7d83d rsp=fffff880009fdaa0 rbp=0000000000000003
 r8=fffff80002c53000  r9=0000000000100000 r10=0000000000000000
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!PpmPerfChooseCoresToUnpark+0x36d:
fffff800`02d7d83d 418b8c90600b2700 mov     ecx,dword ptr [r8+rdx*4+270B60h] ds:2000:fffff804`02ec3b5c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cc4469 to fffff80002cc4f00

STACK_TEXT:  
fffff880`009fd7c8 fffff800`02cc4469 : 00000000`0000000a fffff804`02ec3b5c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009fd7d0 fffff800`02cc30e0 : 00000000`00000000 00000000`00000000 00000000`ffffffff fffff880`009fdc50 : nt!KiBugCheckDispatch+0x69
fffff880`009fd910 fffff800`02d7d83d : fffffa80`06c89600 fffff880`009fdb00 00000000`00001b5c 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009fdaa0 fffff800`02d7e132 : 00000000`00000000 fffff880`009b0004 00000000`00000000 fffff800`02da90dc : nt!PpmPerfChooseCoresToUnpark+0x36d
fffff880`009fdb70 fffff800`02d7c25c : fffff880`009b2180 00000000`00000000 fffff800`02e65310 00000000`0df8fd77 : nt!PpmPerfCalculateCoreParkingMask+0x6c2
fffff880`009fdca0 fffff800`02cd05dc : fffff880`009b2180 00000000`00001b5c 00000000`110c5d58 00000000`0000005c : nt!PpmCheckRun+0x8c
fffff880`009fdcd0 fffff800`02ccd6fa : fffff880`009b2180 fffff880`009bd0c0 00000000`00000000 fffff800`02d7c1d0 : nt!KiRetireDpcList+0x1bc
fffff880`009fdd80 00000000`00000000 : fffff880`009fe000 fffff880`009f8000 fffff880`009fdd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PpmPerfChooseCoresToUnpark+36d
fffff800`02d7d83d 418b8c90600b2700 mov     ecx,dword ptr [r8+rdx*4+270B60h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!PpmPerfChooseCoresToUnpark+36d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0xA_nt!PpmPerfChooseCoresToUnpark+36d

BUCKET_ID:  X64_0xA_nt!PpmPerfChooseCoresToUnpark+36d

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

The crashes themselves seem to indicate hardware. Your information provided would further substantiate that the problem is hardware related. When two operating systems crash, the cause is very indicative of hardware failure. You appear to have already done many of the steps I would suggest to check the hardware. Did you run at least seven passes of Memtest86+?

Here is my usual hardware checklist:

• 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). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. 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
  
  
• 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).
  
  If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.