Blue screen of Death

H

HugMePl0x

New member
Local time
9:06 PM
Messages
4
Hello, a few minutes ago i got a random blue screen. I made a lot of research but i can't find a solution most probably cause i am a newbie :cry: If anyone could help me out i would be so grateful, thanks in advance :)
 

My Computer My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Turbo X
OS
Windows 7 x64 Home Premium
CPU
AMD Phenom(tm) II X6 1090T Processor 3.20 GHz
Motherboard
GA-890XA-UD3
Memory
4,00GB
Graphics Card(s)
NVIDIA GeForce GT 430
Sound Card
NVIDIA High Definition Audio
Hard Drives
ST31000528AS ATA Device
Antivirus
AVG Internet Security
Browser
Firefox, Google Chrome
Here is my results.
 

My Computer My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Turbo X
OS
Windows 7 x64 Home Premium
CPU
AMD Phenom(tm) II X6 1090T Processor 3.20 GHz
Motherboard
GA-890XA-UD3
Memory
4,00GB
Graphics Card(s)
NVIDIA GeForce GT 430
Sound Card
NVIDIA High Definition Audio
Hard Drives
ST31000528AS ATA Device
Antivirus
AVG Internet Security
Browser
Firefox, Google Chrome
Hi HugMePl0x, welcome to 7F! :)

Please keep all correspondence about your BSOD in this thread, do not post in different forums as it will only create confusion.

I have added a link to your query in the Sound and Audio (S&A) Forum to point anyone looking there back to here. At some point one of the Admins or Mods may merge both of your posts to here. Link from the S&A thread.

Now....

Your .dbg points to a 0x116 bugcheck

Code: 
Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80079174e0, fffff88004babe30, 0, d}

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
Probably caused by : nvlddmkm.sys ( nvlddmkm+13be30 )

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

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

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

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


FAULTING_IP: 
nvlddmkm+13be30
fffff880`04babe30 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`021909c8 fffff880`05914000 : 00000000`00000116 fffffa80`079174e0 fffff880`04babe30 00000000`00000000 : nt!KeBugCheckEx
fffff880`021909d0 fffff880`05913d87 : fffff880`04babe30  fffffa80`079174e0 fffffa80`06abd7c0 fffffa80`068ab410 :  dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02190a10 fffff880`059baf07 : fffffa80`079174e0  00000000`00000000 fffffa80`06abd7c0 fffffa80`068ab410 :  dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`02190a40 fffff880`059e4b75 : 00000000`ffffffff  00000000`000704d8 00000000`00000000 00000000`00000002 :  dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02190b20 fffff880`059e32bb : 00000000`00000102  00000000`00000000 00000000`000704d8 00000000`00000000 :  dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02190b50 fffff880`059b62c6 : ffffffff`ff676980  fffffa80`068ab410 00000000`00000000 00000000`00000000 :  dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02190bf0 fffff880`059e2e7a : 00000000`00000000  fffffa80`06abd7c0 00000000`00000080 fffffa80`068ab410 :  dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02190d00 fffff800`03b1ffee : 00000000`fffffc32  fffffa80`06792060 fffffa80`039d69e0 fffffa80`06792060 :  dxgmms1!VidSchiWorkerThread+0xba
fffff880`02190d40 fffff800`038765e6 : fffff800`039fae80  fffffa80`06792060 fffff800`03a08cc0 00000000`00000000 :  nt!PspSystemThreadStartup+0x5a
fffff880`02190d80 00000000`00000000 : 00000000`00000000  00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+13be30
fffff880`04babe30 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+13be30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51c41788

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------
This error code is explained here:
"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling." - H2SO4

Source: BSOD Index #0x00000116
Click to expand...
I appreciate the fact that you listed your system specs that SandeepP asked for in your S&A thread, but can you supply more information as to the maker and model of your Turbo X machine.

In the meantime here are some things you can try:

  • How long have you owned this machine, is it kept in a dusty area, when was the last time you blowed it out, never?
  • Are you keeping the machine as cool as possible?
  • Have you tried to restart your machine and try the speakers and headset?
  • Have you tried to restart your machine in safe mode and select "Last Known Good Configuration"? Option One, arrow keys to "Last Known Good Configuration" touch enter or return, let the OS restart and then check the speakers and headset?
  • What do you have as far as restore points? You can try a System Restore.
 

My Computer My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Gateway DX4831-01e (Mid-Tower Desktop)
OS
Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
CPU
Intel i3 530 2.93GHz, 2933MHz 2 Cores 4 Logical Processors
Motherboard
Gateway H57M01 133 megahertz
Memory
6GB of 1,333MHz DDR3 SDRAM
Graphics Card(s)
32MB Intel Graphics Media Accelerator HD IGChip
Sound Card
Realtek High Definition Audio
Monitor(s) Displays
Gateway HX2000 20inch TFT active matrix TN
Screen Resolution
1600 x 900 x 59 hertz
Hard Drives
WDC WD10EADS-00M2B0 [HDD] (1000.20 GB) -- drive 0,
HL-DT-ST DVDRAM GH41N [CD-ROM dr]
Four card readers, and Four USB 2.0
PSU
300watts.
Case
Mid-Tower Desktop
Cooling
Stock from Gateway
Keyboard
Natural Ergonomic Keyboard 4000, see Other Info
Mouse
Orig. Gateway wore out now using Insignia USB wired optical
Internet Speed
Vz FIOS 10ms png 57.64Mbps down 65.53Mbps up Speedtest.org
Antivirus
Zamana Anti-logger with Anti-malware, MSE, Windows Firewall,
Browser
IE11.0.9600.19399-Upd ver11.0.135, Firefox 68.0.1 x64
Other Info
System Specs by Belarc.

BIOS: American Megatrends Inc. P01-A0 11/17/2009

Replaced the MS 'Natural' Standard PS/2 Enhanced 101-102 Keyboard with a new Natural Ergonomic Keyboard 4000 on August 1st 2014.

Canon Pixma MG3222 Printer.

Updated to IE11 on 12102015 | Fios Quantum Router g1100

Additional AV: SpywareBlaster, manual Mbam, SAS
You must log in or register to reply here.

Similar threads

Solved Black screen of death
Replies
2
Views
5K
Sam1951
S
Solved Not blue but BLACK screen of death!
Replies
2
Views
5K
Novice John
N
Blue screen of death - no downloads or changes to computer recently
Replies
17
Views
32K
CHRISX
C
Blue Screen of Death 1e
Replies
1
Views
836
MrPepka
M
Windows 7 Blue Screen Of Death with error: IRQL_NOT_LESS_OR_EQUAL
Replies
1
Views
769
axe0
A
Back
Top