BSOD when starting up computer or random times, IRQL not less or equal

Hi Vibrance.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If there is no error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {dc, 2, 1, fffff80002eff045}

Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )

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: 00000000000000dc, 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: fffff80002eff045, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003100100
GetUlongFromAddress: unable to read from fffff800031001c0
 00000000000000dc Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeStackAttachProcess+115
fffff800`02eff045 f00fc186dc000000 lock xadd dword ptr [rsi+0DCh],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff88003716770 -- (.trap 0xfffff88003716770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000008 rbx=0000000000000000 rcx=fffffa80066e86e0
rdx=fffff88003716a58 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002eff045 rsp=fffff88003716900 rbp=fffff88003716a58
 r8=fffffa80066e86d0  r9=0000000000000130 r10=fffff880033660c0
r11=fffffa80066e8680 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeStackAttachProcess+0x115:
fffff800`02eff045 f00fc186dc000000 lock xadd dword ptr [rsi+0DCh],eax ds:00000000`000000dc=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ece2e9 to fffff80002eced40

STACK_TEXT:  
fffff880`03716628 fffff800`02ece2e9 : 00000000`0000000a 00000000`000000dc 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03716630 fffff800`02eccf60 : fffff880`037167b0 fffff8a0`0f6cd290 00000000`000000b7 fffffa80`066e8680 : nt!KiBugCheckDispatch+0x69
fffff880`03716770 fffff800`02eff045 : 00000000`00000000 fffffa80`066e8680 fffffa80`066e8680 fffff800`031a0aa3 : nt!KiPageFault+0x260
fffff880`03716900 fffffa80`0a3319c8 : fffff880`03716a80 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeStackAttachProcess+0x115
fffff880`03716980 fffff880`03716a80 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0a3319c8
fffff880`03716988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`03716a80


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeStackAttachProcess+115
fffff800`02eff045 f00fc186dc000000 lock xadd dword ptr [rsi+0DCh],eax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KeStackAttachProcess+115

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

IMAGE_VERSION:  6.1.7601.17727

FAILURE_BUCKET_ID:  X64_0xA_nt!KeStackAttachProcess+115

BUCKET_ID:  X64_0xA_nt!KeStackAttachProcess+115

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_nt!kestackattachprocess+115

FAILURE_ID_HASH:  {805e53f0-f356-736f-cb0b-e08201d4746e}

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