BSOD playing various games, including CS:GO / Civ 5

avengerdcs · 19 Sep 2012

As the title states, I've been getting many BSOD's in the last few days while playing games, including CS:GO and Civ5. The only thing I have done recently was play with MSI Afterburner to try and tweak my video card some. Specifically the voltage which I increased to 1.013 volts then I believe 1.025. During this time I also played with the fan speed settings. This was all trying to resolve an issue I had while trying to play BF3 (supposedly a display driver issue). Anyways I have noticed a couple times when I have to turn the computer back on is a screen I had never seen before while booting up. Something about "overclocking failed". Well when I first saw this I thought maybe MSI Afterburner had saved settings. But when I open it back up it shows everything to be at default. I even looked up what I believe are the default settings on the card and set them to it but to no avail, I still get BSOD's. So I don't know if the problem is related at all but just wanted to give some extra information. I'm semi-competent with computers so I hope to be able to help you help me.

Skylais · 19 Sep 2012

Ok well 1st, i would suggest just resetting the BIOS to defaults. Next all of the dumps (A LOT) looked like this :

Code:

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


Loading Dump File [C:\Users\Skyler\AppData\Local\Temp\Rar$DIa0.181\090412-16052-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02e57000 PsLoadedModuleList = 0xfffff800`0309b670
Debug session time: Tue Sep  4 10:57:47.493 2012 (UTC - 5:00)
System Uptime: 0 days 1:58:43.555
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8006d9f4e0, fffff8800fd561a4, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+d431a4 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006d9f4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fd561a4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+d431a4
fffff880`0fd561a4 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`035ffb88 fffff880`03c85000 : 00000000`00000116 fffffa80`06d9f4e0 fffff880`0fd561a4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`035ffb90 fffff880`03c58867 : fffff880`0fd561a4 fffffa80`07d8d000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`035ffbd0 fffff880`03c84e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`06d9f4e0 fffff880`03d53dc0 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`035ffc80 fffff880`03d53ec1 : fffffa80`066e4b00 00000000`00000080 00000000`00000000 fffffa80`07d4e410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`035ffd00 fffff800`0316ce6a : 00000000`0259d3e0 fffffa80`07a5fa00 fffffa80`0548d890 fffffa80`07a5fa00 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`035ffd40 fffff800`02ec6ec6 : fffff800`03048e80 fffffa80`07a5fa00 fffff800`03056cc0 0000001f`474fc000 : nt!PspSystemThreadStartup+0x5a
fffff880`035ffd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+d431a4
fffff880`0fd561a4 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+d431a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4fb20748

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

Which is blaming this : nvlddmkm.sys = Nvidia.
1stly check the website of the make and model, or motherboard. And update the graphics drivers. AS well, If this does not work then use this Nvidia: NVIDIA Driver Downloads - Automatically Detect NVIDIA Products
*Will need java to run*

avengerdcs · 20 Sep 2012

I went into BIOS and reset to default settings. I've noticed errors related to the display driver prior to experiencing these BSOD's. Specifically the nvlddmkm.sys file you mentioned. I had updated the driver before and to no avail. But today I found there actually is a new updated driver so I did download it. The motherboard driver appears up to date. Thank you for your assistance and I will be back to let you know if I experience anymore BSOD's in the next couple days.

avengerdcs · 20 Sep 2012

Still crashes. The following was the problem details:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA80094394E0
BCP2: FFFFF8800FBA1004
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\092012-16738-01.dmp
C:\Users\Brandon\AppData\Local\Temp\WER-84287-0.sysdata.xml

Attachment 232752

Skylais · 20 Sep 2012

Code:

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


Loading Dump File [C:\Users\Skyler\AppData\Local\Temp\Rar$DIa0.362\092012-16738-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02e59000 PsLoadedModuleList = 0xfffff800`0309d670
Debug session time: Thu Sep 20 15:37:42.317 2012 (UTC - 5:00)
System Uptime: 0 days 2:29:36.472
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80094394e0, fffff8800fba1004, ffffffffc000009a, 4}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** 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+ad6004 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80094394e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fba1004, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+ad6004
fffff880`0fba1004 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`060d0b88 fffff880`040af000 : 00000000`00000116 fffffa80`094394e0 fffff880`0fba1004 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`060d0b90 fffff880`04082867 : fffff880`0fba1004 fffffa80`07ea7000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`060d0bd0 fffff880`040aee0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`094394e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`060d0c80 fffff880`0fdefec1 : fffffa80`06b46220 00000000`00000080 00000000`00000000 fffffa80`07e95410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`060d0d00 fffff800`0316ee6a : 00000000`fffffc32 fffffa80`07b56b50 fffffa80`0548d890 fffffa80`07b56b50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`060d0d40 fffff800`02ec8ec6 : fffff800`0304ae80 fffffa80`07b56b50 fffff800`03058cc0 0000001b`15056000 : nt!PspSystemThreadStartup+0x5a
fffff880`060d0d80 00000000`00000000 : fffff880`060d1000 fffff880`060cb000 fffff880`060d0610 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+ad6004
fffff880`0fba1004 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+ad6004

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  503f8bb8

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

Again the nvidia driver.
Lets try this

Graphics: Video Card - Stress Test with Furmark (Do the above Graphics test only with the latest drivers, and then Run it until the temperatures stop increasing; should be less then 10 minutes. If you don't see any crazy glitches or distortion on the screen, The test most likely passed. Take note if the Temperature gets too high, or you see Visual artifact - Wikipedia, the free encyclopedia to stop the test.)

avengerdcs · 20 Sep 2012

Ok, I've done this test before, not long ago, maybe a few months. I followed the instructions to the guide, but when I go to the run the test my computer shuts down right away. Specifically after clicking GO! on the warning message popup.

I also noticed on my MSINFO32 that under Problem Devices it lists Marvell 91xx Config ATA Device, which I think is my motherboard. And says it isn't installed. I'm pretty sure I just installed it yesterday but it was late so I will install it again.

Skylais · 20 Sep 2012

Have you thought about temporarily switching the graphic card, to see if that is the problem?

avengerdcs · 20 Sep 2012

If you mean switching the card out for another, I do not have another.

I found my motherboard cd and updated the chipset. The update was the same as me going to the manufacturers website and downloading it.

Skylais · 21 Sep 2012

Lower the voltages a bit on the card and see how it runs. If you still get them i would suggest getting the g card checked, and or replaced.

avengerdcs · 14 Oct 2012

I purchased a new video card and I'm still crashing. I haven't seen a BSOD error, but I have shut down and restarted twice unexpectedly since installing the new card. Once I was joining a BF3 game and while the level was loading it shut down and restarted. The other time while I was in a BF3 game. After the computer shuts down I can sometimes smell something getting hot in the computer. But my CoreTemp and PrecisionX say its not the CPU or GPU. I have also been able to resolve my Marvell Controller driver problem since last posting. Is there something else I should check for overheating like my motherboard? If so please advise best way to determine. Any and all help will be greatly appreciated.

I have also updated the .zip file for recent dump information.