Random BSOD, error 0x000000d1 DRIVER_IRQL...

Well, I had a lot of these BSOD lately. It all started when I installed a new graphics card. On the first (in fact, was the second) start of the system, after driver installing and all that stuff, a wild BSOD appeared. I reinstalled the graphics card drivers but the BSOD keep appearing. So I thought, maybe is the RAM I had to remove when cleaning, but when I ran Memtest it showed no errors. These BSOD keep appearing and I've been tempted to set the computer on fire.

Windows Specs:

- Home Premium 64bit
- OEM
- Second install, because I formatted the HD thinking it was soft problem, this install it's about five months old.

Additional Info:

- The error is 0x000000d1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
- The new graphics card is a Gigabyte GeForce 520, the old one was built in. I ran a stress test on it and it was all fine.
- BlueScreenView says something about ntoskrnl.exe
- The BSOD appear randomly. Usually when playing Football Manager 2012 or starting Firefox. With other games or programs I have less problems.
- I had more BSOD's than dumps in the zip, that's because my brother hard resets the computer when dumping (one of these days I'm going to set him on fire with the computer)
- Driver Verifier was running, but I closed it sometime ago.

PD: I'm a humble spanish man, so don't be fussy with the grammar and ortography.

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\johncasel\Windows_NT6_BSOD_jcgriff2\030112-12542-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 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e5a670
Debug session time: Thu Mar  1 10:35:07.490 2012 (UTC - 7:00)
System Uptime: 0 days 9:09:43.926
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff9805b277003, 2, 0, fffffa80070b8fcf}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff9805b277003, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffffa80070b8fcf, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec4100
 fffff9805b277003 

CURRENT_IRQL:  2

FAULTING_IP: 
+3033613535653562
fffffa80`070b8fcf 0fb602          movzx   eax,byte ptr [rdx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  uTorrent.exe

TRAP_FRAME:  fffff88007173850 -- (.trap 0xfffff88007173850)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000002d rbx=0000000000000000 rcx=0000000000000019
rdx=fffff9805b277003 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa80070b8fcf rsp=fffff880071739e0 rbp=fffff9805b276fee
 r8=0000000000000004  r9=0000000000005800 r10=000000000000003a
r11=00000000000000ca r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
fffffa80`070b8fcf 0fb602          movzx   eax,byte ptr [rdx] ds:c668:fffff980`5b277003=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c911e9 to fffff80002c91c40

STACK_TEXT:  
fffff880`07173708 fffff800`02c911e9 : 00000000`0000000a fffff980`5b277003 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`07173710 fffff800`02c8fe60 : 00000000`00000006 fffff800`02cbd830 00000000`00000000 00000000`00000002 : nt!KiBugCheckDispatch+0x69
fffff880`07173850 fffffa80`070b8fcf : 00000000`00000002 fffffa80`03357f90 00000000`00000000 fffff800`031292c7 : nt!KiPageFault+0x260
fffff880`071739e0 00000000`00000002 : fffffa80`03357f90 00000000`00000000 fffff800`031292c7 00000000`01fbdf4b : 0xfffffa80`070b8fcf
fffff880`071739e8 fffffa80`03357f90 : 00000000`00000000 fffff800`031292c7 00000000`01fbdf4b fffff800`0312824c : 0x2
fffff880`071739f0 00000000`00000000 : fffff800`031292c7 00000000`01fbdf4b fffff800`0312824c fffffa80`03357f80 : 0xfffffa80`03357f90


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`02c8fe60 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xD1_VRF_nt!KiPageFault+260

BUCKET_ID:  X64_0xD1_VRF_nt!KiPageFault+260

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

When Verifier points to system files as the probable cause of the crashes, it usually means a bad driver, data corruption on the system, or hardware problems. We will start with bad drivers first. Before proceeding with these steps, ensure that Verifier is indeed disabled by doing the following steps: Start Menu -> All Programs -> Accessories -> Right click Command prompt -> Run as administrator ->

verifier /reset

-> Restart the computer.

I note that you have an old driver installed for the graphics card. Please update via GIGABYTE - Graphics Card - NVIDIA - PCI Express Solution - GeForce 500 Series - GV-N520OC-1GI going to Downloads, Download type: Driver, OS: Windows 7 64-Bit.

See if that resolves the crashes. If not, we will proceed with other steps.

Well, thanks for the response and the help, I've just finished the install of the new drivers, I'm going to play Football Manager a bit and see if I have any crash. Will post if I have another BSOD.

Sounds like a good plan; best wishes!

Well, I have not had any BSOD in two days, but I've been having a different problem. Sometimes, the monitor turns black (like turned off or in stand by) and then normal again , and a pop up window says: "Display driver stopped responding and has recovered". I've noticed it happens usually when I do things that require more ram.

Thanks again.

4 GB should be plenty. When you say you ran memtest in your first post, do you mean Memtest86+?

Also, have you run a test on your graphics card memory? |MG| Video Memory Stress Test 1.7.116 Download

For both Memtest86+ and the video memory test, let it run for at least seven passes.

Yeah, I've already run both, but only once. I'll let it run seven times more.

Thanks again.

You're welcome. Keep us updated. :)