Solved Keep having bluescreens regularly, cannot grasp why

E Revo · Feb 9, 2015

Well, I keep having bluescreens and crashes. All. The. Time. Usually only while playing. The screen will suddenly freeze, all sound cease, I hear something switch off inside the computer, for it then to shut down completely. Usually without even giving me the bluescreen. It just dies. Then it proceeds to start up by itself, for then to usually turn on and shut down multiple times before being able to even give me a picture on the screen.
I'll put by a file with debug files as according to this thread: http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

Arc · Feb 9, 2015

First of all update the display driver. Drivers - Download NVIDIA Drivers

See how it goes. Let us know for any further BSODs. We may need to take further actions depending the resulting situation.
_____________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80087834e0, fffff8800f9b77a0, ffffffffc000009a, 4}

*** 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+9a57a0 )

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: fffffa80087834e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f9b77a0, 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+9a57a0
fffff880`0f9b77a0 48ff25f94eedff  jmp     qword ptr [nvlddmkm+0x87a6a0 (fffff880`0f88c6a0)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`04416a48 fffff880`0fd33134 : 00000000`00000116 fffffa80`087834e0 fffff880`0f9b77a0 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`04416a50 fffff880`0fd06867 : fffff880`0f9b77a0 fffffa80`09787000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`04416a90 fffff880`0fd32f43 : fffff800`ffffd846 ffffffff`fffe7960 fffffa80`087834e0 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`04416b40 fffff880`02c8603d : fffffa80`0a081010 00000000`00000080 00000000`00000000 fffffa80`096c5410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`04416bc0 fffff800`039130ca : 00000000`0318d97e fffffa80`09365a00 fffffa80`06996b30 fffffa80`09365a00 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`04416c00 fffff800`03667be6 : fffff800`037f0e80 fffffa80`09365a00 fffff800`037fecc0 fffff880`03369150 : nt!PspSystemThreadStartup+0x5a
fffff880`04416c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+9a57a0
fffff880`0f9b77a0 48ff25f94eedff  jmp     qword ptr [nvlddmkm+0x87a6a0 (fffff880`0f88c6a0)]

SYMBOL_NAME:  nvlddmkm+9a57a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f012000 fffff880`0fca0000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 23:12:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

E Revo · Feb 10, 2015

Alright, thanks :3 I'll try that

E Revo · Feb 24, 2015

Arc said:

First of all update the display driver. Drivers - Download NVIDIA Drivers

See how it goes. Let us know for any further BSODs. We may need to take further actions depending the resulting situation.
_____________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80087834e0, fffff8800f9b77a0, ffffffffc000009a, 4}

*** 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+9a57a0 )

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: fffffa80087834e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f9b77a0, 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+9a57a0
fffff880`0f9b77a0 48ff25f94eedff  jmp     qword ptr [nvlddmkm+0x87a6a0 (fffff880`0f88c6a0)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`04416a48 fffff880`0fd33134 : 00000000`00000116 fffffa80`087834e0 fffff880`0f9b77a0 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`04416a50 fffff880`0fd06867 : fffff880`0f9b77a0 fffffa80`09787000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`04416a90 fffff880`0fd32f43 : fffff800`ffffd846 ffffffff`fffe7960 fffffa80`087834e0 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`04416b40 fffff880`02c8603d : fffffa80`0a081010 00000000`00000080 00000000`00000000 fffffa80`096c5410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`04416bc0 fffff800`039130ca : 00000000`0318d97e fffffa80`09365a00 fffffa80`06996b30 fffffa80`09365a00 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`04416c00 fffff800`03667be6 : fffff800`037f0e80 fffffa80`09365a00 fffff800`037fecc0 fffff880`03369150 : nt!PspSystemThreadStartup+0x5a
fffff880`04416c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+9a57a0
fffff880`0f9b77a0 48ff25f94eedff  jmp     qword ptr [nvlddmkm+0x87a6a0 (fffff880`0f88c6a0)]

SYMBOL_NAME:  nvlddmkm+9a57a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f012000 fffff880`0fca0000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 23:12:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Welp, it didn't work, that's for darn sure.
I have no idea what to do. When the bluescreen pops up, it says something in way of "Dumping physical memory" or something, followed by "Dumping complete" then it proceeds to restart up to 16 times by itself, before giving me a picture.
Please, if you can help, help me :c I'll supply you with any information from my computer you need
Thank you

Arc · Feb 24, 2015

Follow the Blue Screen of Death (BSOD) Posting Instructions once again.

E Revo · Feb 27, 2015

Sorry.
Here.

Arc · Feb 28, 2015

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also inform us if you experienced any artifacts or crashes during the test.

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 .
______________________________________________

Code:

.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800cf7e350, fffff8800607af38, ffffffffc000009a, 4}

*** 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+7a3f38 )

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: fffffa800cf7e350, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800607af38, 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+7a3f38
fffff880`0607af38 48ff25f192edff  jmp     qword ptr [nvlddmkm+0x67d230 (fffff880`05f54230)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`03e42a48 fffff880`04b22134 : 00000000`00000116 fffffa80`0cf7e350 fffff880`0607af38 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`03e42a50 fffff880`04af5867 : fffff880`0607af38 fffffa80`0b67d000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03e42a90 fffff880`04b21f43 : 00000000`ffffd846 fffff800`03801080 fffffa80`0cf7e350 fffff880`04bf1f3c : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`03e42b40 fffff880`04bf203d : fffffa80`070477e0 00000000`00000080 00000000`00000000 fffffa80`0b664010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`03e42bc0 fffff800`03172b8a : 00000000`04fbdb91 fffffa80`0b6a4060 fffffa80`069959e0 fffffa80`0b6a4060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`03e42c00 fffff800`02ec58e6 : fffff800`03050e80 fffffa80`0b6a4060 fffff800`0305ecc0 fffffa80`0b663810 : nt!PspSystemThreadStartup+0x5a
fffff880`03e42c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+7a3f38
fffff880`0607af38 48ff25f192edff  jmp     qword ptr [nvlddmkm+0x67d230 (fffff880`05f54230)]

SYMBOL_NAME:  nvlddmkm+7a3f38

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  54d3b001

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`058d7000 fffff880`062e9000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Feb 05 23:31:37 2015 (54D3B001)
    CheckSum:         009D4DDE
    ImageSize:        00A12000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

E Revo · Mar 11, 2015

I ran Furmark, and had no issues while running the benchmark.(Screenshot uploaded) However, I cannot give you a screenshot of Speccy after a couple of hours of normal usage, as my computer usually crashes within fifteen minutes of my normal usage.
I'm either way fairly certain that overheating is not the problem. The fans spins nowhere near max pace during normal usage. They did when I ran Furmark though, ran at a high pace.
I did some research, and found that I should fix the "nvlddmkm.sys" file in the Nvidia drivers. This didn't work either.

Arc · Mar 11, 2015

We need to check the temps .... otherwise a big possibility will remain untouched.

nvlddmkm.sys is the nvidia display driver. But stop 0x116 does include teh entire graphics environment within its scope. And we have already noticed that the issue continues irrespective of the display driver version involved. So it is anything else within the graphics environment that is causing the BSODs.

I dont want to know the fan speeds, what I need to know is the system temperature. Fan speed may not have a proper bearing on it. It depends on some more other things as well.

About furmark, you ran the benchmark whereas you were supposed to run the stress test for some more time. Still, the benchmark yielded 90ºC which is hot enough to cause a display crash.

E Revo · Mar 11, 2015

Well, last week I ran Furmark for over an hour. Sure enough, the GPU temperature went above 90 degrees celsius. It reached its peaking point at 98 degrees. And stayed about there for the rest of the stress test. The computer didn't crash, even when running the GPU at 98%, and keeping a temperature of nearly a 100 degrees for quite some time.
Usually, when playing my games earlier on, before these problems, my GPU stayed at about 83 degrees, give or take.

Arc · Mar 11, 2015

83º is high for a GPU.

But if can take the stress test for that long (over an hour), we cannot say that it is the GPU that is causing the issue.

We have already seen that the driver version does not have anything to do here.

So the system temps becomes very critical information here. Cannot you provide a speccy screenshot?

E Revo · Mar 12, 2015

Of course, I can provide a Speccy screenshot. But as mentioned, not after a couple hours of my usually heavy usage. As the computer crashes long before two hours have gone by.

Arc · Mar 12, 2015

Did not you notice? It is indicating.

View attachment 352430

Dismantle the computer. Clean the inside very carefully. Clean all the air vents and fan grills so that it can blow the hot air out efficiently. While re-seating, apply new thermal paste to the CPU heatsneak.

If you cannot do it yourself, get it done by somebody who can; but dont leave it pending. Do it at once.

Report us for any further BSOD only after it is done. Because no troubleshooting will be feasible in this state.

E Revo · Mar 12, 2015

The CPU is simply too hot? I hope you're right, I'll give it a go. Would make sense, as I've never properly cleaned it all-through, over the three years I've had it..
Thanks alot :3

Arc · Mar 12, 2015

Post another CPU screenshot when the job is done.

E Revo · Mar 12, 2015

Doesn't appear to have made THAT much of a difference in degrees on the CPU. Jumping around between 51 and 58 on "idle" usage. Instead of about 57-65. But what do I know. I'll try running the computer as I usually do, and see if it still has problems.
How hot is the CPU supposed to be?

E Revo · Mar 12, 2015

While playing my game, it stays right about at these temepratures. Haven't crashed in fifteen minutes, that's an improvement

Arc · Mar 13, 2015

What CPU cooler do you use?

E Revo · Mar 20, 2015

No matter any longer, It's all running properly now! I applied new thermal paste and cleaned out the case, turns out it was in fact the CPU overheating. Thanks a lot mate :3

Arc · Mar 21, 2015

Its OK, good news.

Solved Keep having bluescreens regularly, cannot grasp why

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Similar threads