For future ref I'll copy some of the dump analysis here:
HTML Code:
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: 00000000018569a0, 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: fffff80002aea809, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 00000000018569a0
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeGetCurrentProcessorNumberEx+19
fffff800`02aea809 668911 mov word ptr [rcx],dx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: uTorrent.exe
--------------------------------------------------------------------
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: tcpip!IppPacketizeDatagrams+b3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tcpip
IMAGE_NAME: tcpip.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4db4de6a
FAILURE_BUCKET_ID: X64_0xA_tcpip!IppPacketizeDatagrams+b3
BUCKET_ID: X64_0xA_tcpip!IppPacketizeDatagrams+b3
Followup: MachineOwner
In this dump it is again another type of code and driver. It is starting to look like there is something wrong at a deeper level. Also, in this dump, it had a problem again with basic W7 drivers, this time part of the security system...
Om the other hand, the dump before that from 7th of August, again points to graphics drivers:
HTML Code:
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A0000001, {5, 0, 0, 0}
Probably caused by : atikmdag.sys ( atikmdag+4d761 )
Followup: MachineOwner
---------
Assuming all went well in your previous steps and you did really delete old drivers and install correct new ones.. That you even checked the exact versions of these drivers that are loaded in your system. Also that all other points advised above have been done/fixed.
Again ONLY if all the above has been tried and tested... then I'd start looking at HW.. This kind of diversity of problems can, in your case of a new build, be caused by something as simple (but difficult to research) as PSU / powersetting problem.
We recently had a thread here where there were all sorts of crash codes, memtest worked fine for 7 passes etc all sort of tests... fine... but still crashes. UNtil someone thought to push up the voltage of a ram module a bit. That fixed it.
Anyway, not saying that specific example it the case here but.. IF you build your own, as you have apparently done, you need to have researched and tried out all the detail of voltages / amps on a rail etc for your specific system....
Quote