Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD Nightmare


  • Please log in to reply
46 replies to this topic

#1 Lordvaine

Lordvaine

  • Members
  • 21 posts
  • OFFLINE
  •  

Posted 24 December 2016 - 01:17 AM

Hey there. I recently upgraded to a MSI Geforce 1060 3GB model gpu. since then I been getting all kinds of Blue screens such as 0x00000133 During running of games. So I reformatted my pc with a clean install of win 10 x64 pro from microsoft and no difference. I have the latest drivers, cleanly installed manytimes, even backdated many times and no results. Now im getting bluescreens during bootup 0x00000116 and it reboots itself. I called Nvidia support and all they had me do is go into safemode and reinstall the drivers with the Geforce experience and change a bunch of settings. I dont know whats going on with this. When it crashed during use, I have 2 monitors and I run 2 games, Usually Firestorm with Diablo3 or WoW. Never had this issue on my 760 card. I could run both with little to no lag. Here is a recent memory dmp file (bootup failure) and my system specs. There are no viruses at all and this is driving me nuts. I just want to game without it crashing. There are no viruses, this is a clean install of windows. No I do not overclock, and yes windows is updated fully. Let me know what you think

 

1: kd> !analyze -v

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff9887b9910010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80cd35c84e0, 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:
------------------
 
 
DUMP_CLASS: 1
 
DUMP_QUALIFIER: 401
 
BUILD_VERSION_STRING:  14393.576.amd64fre.rs1_release_inmarket.161208-2252
 
SYSTEM_MANUFACTURER:  MSI
 
SYSTEM_PRODUCT_NAME:  MS-7681
 
SYSTEM_SKU:  To be filled by O.E.M.
 
SYSTEM_VERSION:  2.0
 
BIOS_VENDOR:  American Megatrends Inc.
 
BIOS_VERSION:  V4.3
 
BIOS_DATE:  01/09/2013
 
BASEBOARD_MANUFACTURER:  MSI
 
BASEBOARD_PRODUCT:  P67A-GD65 (MS-7681)
 
BASEBOARD_VERSION:  2.0
 
DUMP_TYPE:  1
 
BUGCHECK_P1: ffff9887b9910010
 
BUGCHECK_P2: fffff80cd35c84e0
 
BUGCHECK_P3: ffffffffc000009a
 
BUGCHECK_P4: 4
 
FAULTING_IP: 
nvlddmkm+9684e0
fffff80c`d35c84e0 48ff25b945e7ff  jmp     qword ptr [nvlddmkm+0x7dcaa0 (fffff80c`d343caa0)]
 
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
 
CPU_COUNT: 8
 
CPU_MHZ: d48
 
CPU_VENDOR:  GenuineIntel
 
CPU_FAMILY: 6
 
CPU_MODEL: 2a
 
CPU_STEPPING: 7
 
CPU_MICROCODE: 6,2a,7,0 (F,M,S,R)  SIG: 29'00000000 (cache) 29'00000000 (init)
 
BUGCHECK_STR:  0x116
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
ANALYSIS_SESSION_HOST:  GAMINGRIG
 
ANALYSIS_SESSION_TIME:  12-24-2016 01:13:15.0578
 
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
 
STACK_TEXT:  
ffffd980`3d7c8a58 fffff80c`d054ba88 : 00000000`00000116 ffff9887`b9910010 fffff80c`d35c84e0 ffffffff`c000009a : nt!KeBugCheckEx
ffffd980`3d7c8a60 fffff80c`d052e92f : fffff80c`d35c84e0 ffff9887`b39b1b70 ffff9887`b399f010 ffff9887`b39b1bf8 : dxgkrnl!TdrBugcheckOnTimeout+0xec
ffffd980`3d7c8aa0 fffff80c`d052badf : ffff9887`b399f010 00000000`ffffffff ffff9887`b9910010 ffff9887`b9910010 : dxgkrnl!ADAPTER_RENDER::Reset+0x153
ffffd980`3d7c8ad0 fffff80c`d054b275 : fffff802`80dc0100 00000000`00000000 00000000`00000000 00000000`00000100 : dxgkrnl!DXGADAPTER::Reset+0x307
ffffd980`3d7c8b20 fffff80c`d054b3b7 : 00000000`00000100 fffff802`80dcf280 ffff9887`b3122948 fffff80c`cfd41600 : dxgkrnl!TdrResetFromTimeout+0x15
ffffd980`3d7c8b50 fffff802`80aa91b9 : ffff9887`b4b7c040 fffff80c`d054b390 ffff9887`b30b8bd0 ffff9887`b3122948 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffd980`3d7c8b80 fffff802`80a14729 : 00000000`00000000 00000000`00000080 ffff9887`acc866c0 ffff9887`b4b7c040 : nt!ExpWorkerThread+0xe9
ffffd980`3d7c8c10 fffff802`80b61bb6 : fffff802`80d54180 ffff9887`b4b7c040 fffff802`80a146e8 00000000`00000246 : nt!PspSystemThreadStartup+0x41
ffffd980`3d7c8c60 00000000`00000000 : ffffd980`3d7c9000 ffffd980`3d7c3000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
 
 
STACK_COMMAND:  kb
 
THREAD_SHA1_HASH_MOD_FUNC:  56a150c818aff348d17e35fc9e822916b6c0190b
 
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  67a343b69e1b47e21a413d823591b03382d04893
 
THREAD_SHA1_HASH_MOD:  3225689ea8bf23dca00cdfd517975e0703e07271
 
FOLLOWUP_IP: 
nvlddmkm+9684e0
fffff80c`d35c84e0 48ff25b945e7ff  jmp     qword ptr [nvlddmkm+0x7dcaa0 (fffff80c`d343caa0)]
 
FAULT_INSTR_CODE:  b925ff48
 
SYMBOL_NAME:  nvlddmkm+9684e0
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nvlddmkm
 
IMAGE_NAME:  nvlddmkm.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  584d9744
 
FAILURE_BUCKET_ID:  0x116_VRF_IMAGE_nvlddmkm.sys
 
BUCKET_ID:  0x116_VRF_IMAGE_nvlddmkm.sys
 
PRIMARY_PROBLEM_CLASS:  0x116_VRF_IMAGE_nvlddmkm.sys
 
TARGET_TIME:  2016-12-23T05:23:31.000Z
 
OSBUILD:  14393
 
OSSERVICEPACK:  0
 
SERVICEPACK_NUMBER: 0
 
OS_REVISION: 0
 
SUITE_MASK:  272
 
PRODUCT_TYPE:  1
 
OSPLATFORM_TYPE:  x64
 
OSNAME:  Windows 10
 
OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
 
OS_LOCALE:  
 
USER_LCID:  0
 
OSBUILD_TIMESTAMP:  2016-12-09 04:23:02
 
BUILDDATESTAMP_STR:  161208-2252
 
BUILDLAB_STR:  rs1_release_inmarket
 
BUILDOSVER_STR:  10.0.14393.576.amd64fre.rs1_release_inmarket.161208-2252
 
ANALYSIS_SESSION_ELAPSED_TIME: 868
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x116_vrf_image_nvlddmkm.sys
 
FAILURE_ID_HASH:  {cffc4cef-9d06-fdb4-97d0-1f30b550aaa2}
 
Followup:     MachineOwner
 
 
 
System specs (basic)
 
Summary
Operating System
Windows 10 Pro 64-bit
CPU
Intel Core i7 2600K @ 3.40GHz 49 °C
Sandy Bridge 32nm Technology
RAM
16.0GB Dual-Channel DDR3 @ 799MHz (9-9-9-24)
Motherboard
MSI P67A-GD65 (MS-7681) (SOCKET 0) 28 °C
Graphics
LG IPS FULLHD (1920x1080@60Hz)
P235H (1920x1080@59Hz)
3072MB NVIDIA GeForce GTX 1060 3GB (MSI) 60 °C
Storage
1863GB Western Digital WDC WD20EARX-00PASB0 ATA Device (SATA) 34 °C
Optical Drives
HL-DT-ST BD-RE WH10LS30 SCSI CdRom Device
Audio
Logitech G933 Gaming Headset

Edited by Lordvaine, 24 December 2016 - 01:20 AM.


BC AdBot (Login to Remove)

 


#2 mobijones

mobijones

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:10:50 PM

Posted 24 December 2016 - 01:22 AM

which psu u use ? i mean ur power alimentation, maybe not enough power will cauz a bsod to prevent system, and i see that 3072MB NVIDIA GeForce GTX 1060 3GB (MSI) 60 °C is it current warm ? 60 seems to be certainly higher than it should.


Edited by mobijones, 24 December 2016 - 01:23 AM.


#3 Lordvaine

Lordvaine
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  

Posted 24 December 2016 - 01:26 AM

Thermaltake black widow 850 watts. Nvidia already ruled out the PSU. Im also running a game as we speak. This case is well ventilated has a lot of fans, Azza hurricane 2000 is my case CPU is liquid cooled. 



#4 mobijones

mobijones

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:10:50 PM

Posted 24 December 2016 - 01:27 AM

wow, it's more than needed so the problem is not here. 



#5 Lordvaine

Lordvaine
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  

Posted 24 December 2016 - 01:31 AM

Is it possible its a faulty card?



#6 mobijones

mobijones

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:10:50 PM

Posted 24 December 2016 - 01:31 AM

Are you sure that all nvidia hotkeys from your older graphic card are removed maybe it launches at the same time and get conflict...  did u try to boot without ur graphic card connected, i mean maybe if u run on ur graphic socket u could redownload drivers from nvdia i swear geforce sometimes does terrible bleepty things, try to get the driver a different way .



#7 Lordvaine

Lordvaine
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  

Posted 24 December 2016 - 01:32 AM

Its a clean install of windows with the new card there are no hotkeys. pc wont boot without a GPU, has no video card onboard. Re downloaded drivers many times, no results. 



#8 mobijones

mobijones

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:10:50 PM

Posted 24 December 2016 - 01:34 AM

welp i'm not enough expert to  tell you that but i already saw a corrupted grapic cards but that's so unsual ... I never saw that since 10 last years. But here clearly there is a driver default i mean : FAILURE_ID_HASH_STRING:  km:0x116_vrf_image_nvlddmkm.sys here is a nvidia component and seems to be the responsible one but i'm clearly not sure.



#9 mobijones

mobijones

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:10:50 PM

Posted 24 December 2016 - 01:36 AM

so u totally reinstalled windows for using ur new gpu right  ? 



#10 Lordvaine

Lordvaine
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  

Posted 24 December 2016 - 01:37 AM

Thats what I been telling Nvidia and I even tried many drivers that were old too and they corrupt instantly where the Nvidia control panel is missing and wont load. I do have an open ticket with them right now, waiting on a reply back they may just end up warranting the card and I am praying a new driver version releases soon. Yes. new install with new card I replaced the old card due to bad bearing in fan, sounded like a Jet engine


Edited by Lordvaine, 24 December 2016 - 01:37 AM.


#11 mobijones

mobijones

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:10:50 PM

Posted 24 December 2016 - 01:38 AM

u mean pc won't boot without gpu, but this cpu should have a graphic interface isn't it ?



#12 Lordvaine

Lordvaine
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  

Posted 24 December 2016 - 01:39 AM

It does not. The board itself has no display ports. I built this machine myself. had no issues with anything until this card was put in. 



#13 mobijones

mobijones

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:10:50 PM

Posted 24 December 2016 - 01:40 AM

do you have another version of windows may be seven or eight ? may be it's a windows 10 difficult i mean i installed  last week 2 1050 gtx on seven and worked fine at first try, that's really weird buddy.


Edited by mobijones, 24 December 2016 - 01:41 AM.


#14 Lordvaine

Lordvaine
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  

Posted 24 December 2016 - 01:42 AM

I do not. My win7 OS was nuked when windows 10 decided to upgrade on my machine without my knowing it, I lost everything. I had everything backed up, but that external hard drive seemed to have failed :/



#15 mobijones

mobijones

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:10:50 PM

Posted 24 December 2016 - 01:42 AM

ah ok my bad didn't check that.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users