BSOD: A driver has overrun a stack-based buffer. Error 0x000000F7

humphrey06 · 11 Apr 2014

Hi guys,

I get this error when playing Diablo 3, and I've been getting a bunch of other BSODs when playing Diablo 3. I've updated my graphics drivers but still am not sure what's going on here. I've also gotten the error: 0x0000003b

I've attached the log below.

Arc · 12 Apr 2014

Hi humphrey06.

Install the NVIDIA DRIVERS 314.22WHQL only.

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 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

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

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.

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.
_____________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa7f8e667c41, a, 1, fffff8800491f972}

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

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

2: 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: fffffa7f8e667c41, memory referenced
Arg2: 000000000000000a, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800491f972, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034ca100
GetUlongFromAddress: unable to read from fffff800034ca1c0
 fffffa7f8e667c41 

CURRENT_IRQL:  a

FAULTING_IP: 
nvlddmkm+b7972
fffff880`0491f972 108b410c4989    adc     byte ptr [rbx-76B6F3BFh],cl

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:  FFFFF88002F92FB0

TRAP_FRAME:  fffff88002f8b650 -- (.trap 0xfffff88002f8b650)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002f8b8b0 rbx=0000000000000000 rcx=fffff88002f8b970
rdx=fffff88002f88870 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800491f972 rsp=fffff88002f8b7e0 rbp=fffff88002f8b7e0
 r8=fffff88002f8b8c8  r9=fffff88002f8b8c0 r10=0000000000000000
r11=fffff88002f8b870 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nvlddmkm+0xb7972:
fffff880`0491f972 108b410c4989    adc     byte ptr [rbx-76B6F3BFh],cl ds:ffffffff`89490c41=??
Resetting default scope

MISALIGNED_IP: 
nvlddmkm+b7972
fffff880`0491f972 108b410c4989    adc     byte ptr [rbx-76B6F3BFh],cl

LAST_CONTROL_TRANSFER:  from fffff80003292169 to fffff80003292bc0

STACK_TEXT:  
fffff880`02f8b508 fffff800`03292169 : 00000000`0000000a fffffa7f`8e667c41 00000000`0000000a 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f8b510 fffff800`03290de0 : fffffa80`072dae60 00000000`00000000 fffff880`02f8b6c0 fffffa80`051d7000 : nt!KiBugCheckDispatch+0x69
fffff880`02f8b650 fffff880`0491f972 : fffff880`02f8b8a0 fffff880`0491cc8b fffff880`048ea84c fffffa80`051d7000 : nt!KiPageFault+0x260
fffff880`02f8b7e0 fffff880`02f8b8a0 : fffff880`0491cc8b fffff880`048ea84c fffffa80`051d7000 00000000`00000000 : nvlddmkm+0xb7972
fffff880`02f8b7e8 fffff880`0491cc8b : fffff880`048ea84c fffffa80`051d7000 00000000`00000000 00000000`00000000 : 0xfffff880`02f8b8a0
fffff880`02f8b7f0 fffff880`048ea84c : fffffa80`051d7000 00000000`00000000 00000000`00000000 fffff880`02f8b8b0 : nvlddmkm+0xb4c8b
fffff880`02f8b7f8 fffffa80`051d7000 : 00000000`00000000 00000000`00000000 fffff880`02f8b8b0 00000000`00000000 : nvlddmkm+0x8284c
fffff880`02f8b800 00000000`00000000 : 00000000`00000000 fffff880`02f8b8b0 00000000`00000000 00000000`00000000 : 0xfffffa80`051d7000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+b7972
fffff880`0491f972 108b410c4989    adc     byte ptr [rbx-76B6F3BFh],cl

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+b7972

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_nvlddmkm.sys

BUCKET_ID:  X64_IP_MISALIGNED_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_ip_misaligned_nvlddmkm.sys

FAILURE_ID_HASH:  {615fd2a3-a8b5-9567-3eba-e25ae36502f0}

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

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`04868000 fffff880`0530f000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jan 18 18:52:15 2013 (50F94C87)
    CheckSum:         00A92B69
    ImageSize:        00AA7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

humphrey06 · 12 Apr 2014

Hi Arc, thanks for helping.

I uninstalled my previous video card drivers and then installed 314.22WHQL only.

I followed the "Drivers - Clean left over files after uninstalling", then installed and followed the settings in the screenshot.

I then ran Furmark video stress test. The test got 5 minutes and 16 seconds in and then my screen froze. I had to manually restart my computer (by holding down the power button), and now I am writing this post! The min/max of my video card temperature was 32C and 62C. It was at 62C when it froze. I was getting 14FPS.

I have not run Memtest yet, I will do so overnight, and Stress Test the CPU tomorrow. It's currently 7:27am here so the results of those tests might not be for awhile.

However, since my video stress test FAILED, does that mean my video card is faulty and the cause of my crashes? BSODs are rare, I would say most of the time my screen just freezes in game (Diablo3) and I have to manually restart.

Humphrey

humphrey06 · 12 Apr 2014

Could it be a PSU issue as well?

Arc · 12 Apr 2014

humphrey06 said:

However, since my video stress test FAILED, does that mean my video card is faulty and the cause of my crashes?

Humphrey

As it appears.

My next suggestion to you would be to observe the situation with either another GPU or with the onboard graphics.

You may postpone the other hardware tests for the time being, until and unless it yields the same issue with the replacement GPU (though I kinda think it will not).

humphrey06 · 12 Apr 2014

Arc,

I will do so. A friend of mine suggested seeing if the RAM was the issue (since my GPU is pretty new...), since I was getting a lot of random freezes as well.

I have 3 sticks of RAM (2gb each all the same model). Lets call them A, B, and C. Well when I tried to boot up my computer with just one stick in, RAM A, my computer wouldn't boot - it wouldn't even get to the screen where I could start up BIOS. Then when I tried to boot up my computer with only RAM B, it was fine, and only RAM C, it was fine.

Currently, I'm running a Memtest on Ram A to see if it's faulty. Interestingly, when I went to start Memtest, the RAM A had no problem booting up to the BIOS screen. I find that really perplexing. I have an inkling the RAM is probably faulty, but we shall see. If it goes through 8 passes and no errors come up, I'm going to be surprised and I'll try to observe the situation as you suggested with onboard graphics.

Arc · 12 Apr 2014

I think you may/might postpone the other hardware tests for the time being. The primary attention now should be on the GPU.

But if you want to do it, you may proceed.

humphrey06 · 12 Apr 2014

Here's an update:

"Ram A" - performed memtest 7 passes and no errors. I replaced all the RAM and tried the GPU Stress Test again, this time - it didn't crash at all. Surprisingly, it went 15 minutes without any problems. Usually I crash within 10 minutes of playing Diablo3, I just started it again and played for 20 minutes, and I went to zones where there was a lot going on visually.

I have no clue whats going on. It seems like my crashes for the time being have subsided. I will continue to monitor this progress when I play diablo 3 tonight and check it out