BSOD playing DOTA 2, BBCode: d1, error 0x00000116

GabrielK · 17 Jul 2015

Hello

When i started a game of DOTA2 today, i got a BSOD and after that my PC would not start anymore. I am not 100% sure if i caught the correct error from the BSOD as after it happened, i couldn't get my PC to work. I managed to take a picture with my phone of the BSOD but i didn't manage to catch all the info, but someone here might be able to make sense of it. Currently, the PC only works in safeboot mode, when i try to start it normally, it never reaches the login screen for W7. I'll try to include what i know so far:

EDIT: i forgot to mention, i have not installed any new software or hardware, and this is the first BSOD i've got in about 2-3 years.

Trying to repair the system gave me the following errors

BCCode: d1
BCP1: D3AAFA50
BCP2: 00000002
BCP3: 00000008
BCP4: D3AAFA50
OS Version: 6_1_7601

My PC specs are

OS: Windows 7 Professional N 64bit
CPU: AMD Phenom II X4 965 3.4GHz
RAM: 4GB
GPU: Nvidia GTX460

In my Device Manager, under Other Devices, i have Universal Serial Bus (USB) Controller with a yellow triangle with an exclemenation mark infront of it. When trying to view its properties, it shows me nothing. Trying to update the driver gives me nothing either.

Appreciate any help or information i can get!
Gabi~

Boozad · 17 Jul 2015

Let's clear a few things up, you have experienced a 0x116 (always a GPU problem) and a 0xD1 (usually a driver) yes? Neither are showing in your logs. What is showing in your logs is a 0x101 which isn't giving away too much info. So, at a guess going on the STOP codes, update your nVidia driver to the latest version by downloading the latest version from here and follow NVIDIA Drivers - Avoid Problems for the cleanest possible install.

Please monitor your CPU and GPU temperatures and report them back.

Warning

Please do not use CCleaner while you're experiencing BSODs. It will wipe the dump files from your machine.

Code:

BugCheck 101, {31, 0, fffff88002f63180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f63180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
fffff880`009a9768 fffff800`02f1da4a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f63180 : nt!KeBugCheckEx
fffff880`009a9770 fffff800`02ed06f7 : 00000000`00000000 fffff800`00000002 00000000`00002710 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`009a9800 fffff800`02e12895 : fffff800`02e38460 fffff880`009a99b0 fffff800`02e38460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`009a9900 fffff800`02ec3113 : 00000000`5deede18 fffff800`03041e80 00000000`00000000 fffff800`00040004 : hal!HalpHpetClockInterrupt+0x8d
fffff880`009a9930 fffff800`02efc483 : fffff800`03041e80 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`009a9ac0 fffff800`02ecba1c : 00000000`00000000 fffff880`009a9bf8 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x93
fffff880`009a9b00 fffff800`02e896e9 : 00000000`000000e6 00000000`00000000 fffffa80`01eaadc0 00000000`00000100 : nt!KeFlushMultipleRangeTb+0x28c
fffff880`009a9bd0 fffff800`02e89f37 : ffffffff`ffffffff 00000000`000000ff 00000000`00000000 00000000`00000000 : nt!MiZeroPageChain+0x14e
fffff880`009a9c10 fffff800`031632ea : fffffa80`039d3ab0 00000000`00000080 fffffa80`039d3040 fffff800`02eb78d9 : nt!MmZeroPageThread+0x83a
fffff880`009a9d40 fffff800`02eb78e6 : fffff800`03041e80 fffffa80`039d3ab0 fffff800`0304fcc0 60428d44`c88b48d2 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_clock_watchdog_timeout_4_proc_analysis_inconclusive

FAILURE_ID_HASH:  {d61e255a-5a6a-8ac9-10f0-973c0c42bda6}

Followup: MachineOwner

GabrielK · 18 Jul 2015

Hello, sorry for the late reply.

Trying to follow the Nvidia uninstall guide, it won't let me uninstall most of the drivers in safe mode. I believe my temperatures are around 30-35C, looking at BIOS, other than that im not sure how i can monitor them because barely any program will start in safe mode.

Should i still try to do a clean install of the new driver?

EDIT: looking at the minidump files i received, they all seem to date back to 2013 for some reason, i'm not sure if that has anything to do with this though.

Boozad · 18 Jul 2015

Here are a couple of things to try to boot into Normal Mode. Firstly, follow Troubleshooting Windows 7 Failure to Boot to see if that helps. If not, could you uninstall the GPU through Device Manager, physically remove it from the PC and boot using onboard graphics.

GabrielK · 18 Jul 2015

Hey Boozad, just here with a quick update.

I tried some stuff in the W7 trouble shoot guide, it did not help me, however it did give me another bluescreen, where i can definitly confirm 0x116, took a picture aswell. I'm not sure how the log collector works, but i made a new one just in case and will add it to this post.

I will uninstall the GPU through device manager and attempt to physically remove it from the PC now.

Also would like to quickly mention that the yellow triangle infront of the Universal Serial Bus seems to have a code 28 issue on PCI-bus 2, although no further information about it, and im not sure if that affects the GPU in anyway.

Boozad · 18 Jul 2015

For the USB you'd need to download and install either the USB drivers or the chipset drivers for your motherboard from the manufacturer's support page, that should clear that problem up.

There are still no new dump files in your logs, only one form 2013.

Open Advanced System Settings
Click on Settings in Startup & Recovery
Make sure both boxes indicated below are checked
In the dropdown box ensure you're set to record Small Memory Dumps

GabrielK · 18 Jul 2015

I followed the instructions, however the crash dump won't be saved in the minidump folder (for some reason, there's only one 2013 dump there). instead it is saved in another folder called LiveKernelReports/WATCHDOG, i'm not sure if i can do anything with these crash dumps but these are the only ones i get from today.

Boozad · 18 Jul 2015

Can you manually move them to the Minidump folder then re-run the DM Log Collector, see if that ctaches them.

I may not be around for a while so please bear with me and I'll get back to you as soon as I can.

GabrielK · 18 Jul 2015

Alright thanks!

I moved the files from 2015 to the mindump folder and ran the log collector again, it seemed to work i think.

Boozad · 18 Jul 2015

All of your dumps are 0x117 (VIDEO_TDR_ERROR) and are blaming the nVidia driver.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa80052f9010, fffff880131df4ac, 0, 0}

*** 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+1584ac )

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

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`13087000 fffff880`13d67000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Nov 12 20:51:31 2014 (5463C853)
    CheckSum:         00CA4D59
    ImageSize:        00CE0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Download the latest driver for your card from here and follow NVIDIA Drivers - Avoid Problems for the cleanest possible install. Give that a try and see how the machine performs.

Did you manage to boot into Normal Mode yet?