BSOD while in games, error 0x0000000d1

[Alerq]

I've suddenly run into some troubles while playing intensive games, suddenly my PC turns off and shows the BSOD. I also had 0x0000...116 bsod before the D1 reinstalled the nvidia drivers, removed OC from the video, but nothing helped. Thought of new beta-drivers, but installation of previous ones didn't helped. Please, help me.

 

[Alerq]

the log

View attachment 306500

 

[Arc]

Hi Alerq.

It is apparently a display driver failure. And, it also seems that you are using a BETA display driver, which you should not use.

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {20000100c, 2, 0, fffff8800feda101}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+45d101 )

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: 000000020000100c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800feda101, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003515100
GetUlongFromAddress: unable to read from fffff800035151c0
 000000020000100c Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nvlddmkm+45d101
fffff880`0feda101 448b490c        mov     r9d,dword ptr [rcx+0Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

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

DPC_STACK_BASE:  FFFFF80000BA2FB0

TRAP_FRAME:  fffff80000b9c410 -- (.trap 0xfffff80000b9c410)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000030 rbx=0000000000000000 rcx=0000000200001000
rdx=000000000ca57000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800feda101 rsp=fffff80000b9c5a0 rbp=fffffa8010cf4010
 r8=fffff80000b9c570  r9=0000000000002101 r10=0000000000000000
r11=fffff80000b9c4a8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x45d101:
fffff880`0feda101 448b490c        mov     r9d,dword ptr [rcx+0Ch] ds:00000002`0000100c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032dd169 to fffff800032ddbc0

STACK_TEXT:  
fffff800`00b9c2c8 fffff800`032dd169 : 00000000`0000000a 00000002`0000100c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c2d0 fffff800`032dbde0 : fffffa80`0cd05c00 fffffa80`0f3ad000 fffffa80`0cd05c00 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c410 fffff880`0feda101 : fffff800`00b90080 fffffa80`00000001 fffff880`0fed9b66 fffff800`00b9c680 : nt!KiPageFault+0x260
fffff800`00b9c5a0 fffff800`00b90080 : fffffa80`00000001 fffff880`0fed9b66 fffff800`00b9c680 00000000`0ca57000 : nvlddmkm+0x45d101
fffff800`00b9c5a8 fffffa80`00000001 : fffff880`0fed9b66 fffff800`00b9c680 00000000`0ca57000 fffff880`fffffa80 : 0xfffff800`00b90080
fffff800`00b9c5b0 fffff880`0fed9b66 : fffff800`00b9c680 00000000`0ca57000 fffff880`fffffa80 fffffa80`10cb8250 : 0xfffffa80`00000001
fffff800`00b9c5b8 fffff800`00b9c680 : 00000000`0ca57000 fffff880`fffffa80 fffffa80`10cb8250 fffffa80`10b938a8 : nvlddmkm+0x45cb66
fffff800`00b9c5c0 00000000`0ca57000 : fffff880`fffffa80 fffffa80`10cb8250 fffffa80`10b938a8 fffffa80`10cf4010 : 0xfffff800`00b9c680
fffff800`00b9c5c8 fffff880`fffffa80 : fffffa80`10cb8250 fffffa80`10b938a8 fffffa80`10cf4010 00000000`00000000 : 0xca57000
fffff800`00b9c5d0 fffffa80`10cb8250 : fffffa80`10b938a8 fffffa80`10cf4010 00000000`00000000 fffffa80`0ca57000 : 0xfffff880`fffffa80
fffff800`00b9c5d8 fffffa80`10b938a8 : fffffa80`10cf4010 00000000`00000000 fffffa80`0ca57000 fffff880`0fee238b : 0xfffffa80`10cb8250
fffff800`00b9c5e0 fffffa80`10cf4010 : 00000000`00000000 fffffa80`0ca57000 fffff880`0fee238b 00000000`00000000 : 0xfffffa80`10b938a8
fffff800`00b9c5e8 00000000`00000000 : fffffa80`0ca57000 fffff880`0fee238b 00000000`00000000 fffff800`00b9c680 : 0xfffffa80`10cf4010


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+45d101
fffff880`0feda101 448b490c        mov     r9d,dword ptr [rcx+0Ch]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+45d101

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52d6ef25

FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+45d101

BUCKET_ID:  X64_0xD1_nvlddmkm+45d101

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_nvlddmkm+45d101

FAILURE_ID_HASH:  {f01431d9-7389-1727-05e7-dba211b37e5c}

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0fa7d000 fffff880`106ca000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Jan 16 01:57:17 2014 (52D6EF25)
    CheckSum:         00C15A56
    ImageSize:        00C4D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

And unfortunately I dont know any driver version that works good with GTX 780. You may try the drivers on a trial and error basis:

• 320.49 WHQL
• 327.23 WHQL
• 331.58 WHWL
• 331.65 WHQL
• 331.82 WHQL
• 332.21 WHQL

Get them from Drivers - Download NVIDIA Drivers

Do a clean install on all of them. Uninstall the previously installed driver first.
Uninstall All nvidia items in Control Panel > Programs and features

• • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download the target WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Lengthy process, but the only stable version of nvidia is 314.22 lately, which does not support 700 series GPU.

Best of luck. Let us know about the advancement.

 

[Alerq]

Unfortunately, after doing everything you had supposed, I've got 116 errors. I can see, that every time i re-install all the drivers games work fine for 15 min. Then, after bsod i start to get bsod amlost immediately i start playing.View attachment 306519



second ago i had another D1, though

 

[Arc]

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .
http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

 

[Alerq]

The first thing i did after the start of bsods was the cancel of OC. Now i have all my hardware on stock settings, especially videocards. Furmark, like all intensive programmes causes bsod immediately. The heat is not the reason. though, because i know all the temperatures of my hardware. VGA don't go over 80C even in games, CPU is about 70. No dust in the system. I get the crash even before the part can be overheated.

 

[Alerq]

http://speccy.piriform.com/results/vpKQsexDzvRItFN0epbGBwp

 

[Arc]

Furmark, like all intensive programmes causes bsod immediately.

If it is the fact, that means the GPU is not able to take any sort of stress, and it fails whenever it feels a stress.

Replace the GPU. If you are still within warranty, RMA it.

 

[Alerq]

Then how it can be, that it works fine after a full reinstallation of drivers until i want to Tab-alt from the game? A replacement is a bad variant for me since i've bought my VGA in USA that is sooooo far away from me...

 

[Arc]

Then how it can be, that it works fine after a full reinstallation of drivers until i want to Tab-alt from the game? A replacement is a bad variant for me since i've bought my VGA in USA that is sooooo far away from me...

Unfortunately there is no other possible explanation to the situation than that is below:

Furmark, like all intensive programmes causes bsod immediately.

If it is the fact, that means the GPU is not able to take any sort of stress, and it fails whenever it feels a stress.

Replace the GPU. If you are still within warranty, RMA it.

Rest is on you, how you can manage the GPU.