Blue Screen Everytime

Hi, I'm getting sick of the BSOD's that I'm getting. Everytime that my PC is in medium/full charge (i.e. playing a game), I get these damn Blue Screens. I get Driver_IRQL_NOT_LESS_OR_EQUAL, and IRQL_NOT_LESS_OR_EQUAL. I have tried formatting my PC, changing video cards, Ram sticks, PSU's, EVERYTHING, and I can't seem to find the cause.

Specs:
Windows 7 x64 Home Premium
AMD Athlon II X4 640
AsRock N68-S UCC
AMD HD 6850
2X2 Corsair XMS2 DDR2 800mhz
Antec Neo Eco 520C 520W

Pleeease, any help would be much appreciated!!!

I only see one BSOD in your report. I am at work so I am unable to analyze it. Looking through your system events, I see there were three crashes. One on the 26th, one on the 25th and one on the 24th. Are you running any type of system cleaners? They will remove the minidumps from the harddrive.

One of your BSOD

Code:

STOP 0x00000074: BAD_SYSTEM_CONFIG_INFO    (go to top of page)
Usual causes:  System hive corruption, Missing registry keys/values
 
Resolving the Problem
 
Try restarting the computer by selecting "last known good configuration" 
in the boot options.If the restart does not fix the problem, 
the registry damage is too extensive. You must reinstall the OS or
use the Emergency Repair Disk (ERD) that you previously created
by using the Windows Backup tool.

The other two BSOD were STOP 0xD1 and STOP 0x0A.
BSOD Index - STOP 0x0A
BSOD Index - STOP 0xD1

Enable driver verifier and see if it catches any drivers - Driver Verifier - Enable and Disable

I was looking at this, but the callstack from a minidump just isn't enough to capture this. You're going to need to configure your system for a kernel dump, and then get another crash to be definitivie.

1. Open sysdm.cpl
2. Click the "Advanced" tab
3. Click the "Settings" button in the "Startup and Recovery" section
4. Change the "Write debugging information" drop down box to "Kernel memory dump"
5. Click "OK"
6. Reboot for changes to take effect

Once the next crash occurs, you should have a file called "memory.dmp" in the \Windows directory. This file will likely be quite large, and as such will need to be compressed and then uploaded to a file hosting site before we can make further analysis.

It looks like your system is crashing when the Windows kernel enters a function called "KeAccumulateTicks", which is supposed to call back into the driver that called into the cpu to acquire a spinlock at DPC level (the driver is not responding, which causes a paging fault, which can't happen at DPC dispatch level or higher, thus the bugchecks). Without being able to see the driver on the stack, we don't know what is causing it, and this information is not available in a minidump.

Well this is interesting - the memory referenced in the bugcheck (param 3) that causes the crash is also the instruction location that is responsible for calling this address (param 1):

Code:

1: kd> .bugcheck
Bugcheck code 00000050
Arguments fffff800`039e869f 00000000`00000008 fffff800`039e869f 00000000`00000002

The base pointer has been completely corrupted (it's NULL), and the stack pointer contains an invalid address as well:

Code:

1: kd> r
Last set context:
rax=000000000002bb21 rbx=0000000000000000 rcx=fffffa8004b2b550
rdx=fffffa80047d5198 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800039e869f rsp=fffff88002f1bca0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000a5e23b85d r10=00000000000051ed
r11=000000000002be7f r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=5b6b  es=000d  fs=0000  gs=0000             efl=00010246
fffff800`039e869f ??              ???

1: kd> u @rsp
fffff880`02f1bca0 99              cdq
fffff880`02f1bca1 9e              sahf
fffff880`02f1bca2 360000          add     byte ptr ss:[rax],al
fffff880`02f1bca5 0000            add     byte ptr [rax],al
fffff880`02f1bca7 00d8            add     al,bl
fffff880`02f1bca9 fd              std
fffff880`02f1bcaa c10480fa        rol     dword ptr [rax+rax*4],0FAh
fffff880`02f1bcae ff              ???

Ultimately, 2 seconds before the crash, the task scheduler appears to have started a new thread to do something (via taskhost.exe):

Code:

1: kd> !thread fffffa80059eeb60
THREAD fffffa80059eeb60  Cid 114c.01ac  Teb: 000007fffffac000 Win32Thread: 0000000000000000 WAIT: (UserRequest) UserMode Non-Alertable
    fffffa80040ddab0  NotificationEvent
Not impersonating
DeviceMap                 fffff8a00114db80
Owning Process            fffffa80039a1060       Image:         taskhost.exe
Attached Process          N/A            Image:         N/A
Wait Start TickCount      874042         Ticks: 1330 (0:00:00:20.781)
Context Switch Count      10             
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x000007fee9a882c8
Stack Init fffff88008a32db0 Current fffff88008a32900
Base fffff88008a33000 Limit fffff88008a2d000 Call 0
Priority 7 BasePriority 6 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`08a32940 fffff800`02adf992 : 00000000`00000100 fffffa80`059eeb60 fffffa80`00000000 ffffffff`ffffffff : nt!KiSwapContext+0x7a
fffff880`08a32a80 fffff800`02ae1cff : 00000000`00000100 00000000`02eaeb01 00000000`00000000 fffff880`08a32b50 : nt!KiCommitThreadWait+0x1d2
fffff880`08a32b10 fffff800`02dd0ed2 : 00000000`00000c00 fffff880`00000006 00000000`00000001 0000007f`ffffff00 : nt!KeWaitForSingleObject+0x19f
fffff880`08a32bb0 fffff800`02ad7993 : fffffa80`059eeb60 00000000`ffffffff 00000000`00000000 fffffa80`040ddab0 : nt!NtWaitForSingleObject+0xb2
fffff880`08a32c20 00000000`76dbf6fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`08a32c20)
00000000`02eaf6a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76dbf6fa

Unfortunately, this is a kernel dump, which means no user-mode stack, so I'm not really sure what exactly ran at the time:

Code:

1: kd> .time
Debug session time: Sun May  1 16:04:50.148 2011 (UTC - 4:00)
System Uptime: 0 days 3:47:57.695

Might want to look at your task scheduler or your event viewer to see if anything was scheduled to run at about that time?