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


  • This topic is locked This topic is locked
15 replies to this topic

#1 Barronno

Barronno

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:08 AM

Posted 07 October 2012 - 04:43 PM

Hello to all,
I recently got a new laptop on which I installed windows 7 pro. At this point I've gotten 3 BSODs and I'm not entirely sure what is causing the problem. Below you can find the debugging report based on the procedure I took form usasma's post on "How to receive help diagnosing Blue Screens and Windows crashes". I'm using a Clevo P150EM. The bug report appears to be about the video card, which is a GTX675 working with Intel 4000 integrated via optimus. Any assistance would be greatly appreciated, and I thank you for your time.


Microsoft ® Windows Debugger Version 6.2.9200.16384 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\100712-7924-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e4a670
Debug session time: Sun Oct 7 14:47:12.931 2012 (UTC - 6:00)
System Uptime: 0 days 3:20:57.638
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007dd0010, fffff8800f1fc584, 0, 2}

*** 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+14b584 )

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

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

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

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


FAULTING_IP:
nvlddmkm+14b584
fffff880`0f1fc584 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`043af4f8 fffff880`0495b000 : 00000000`00000116 fffffa80`07dd0010 fffff880`0f1fc584 00000000`00000000 : nt!KeBugCheckEx
fffff880`043af500 fffff880`0495ad0a : fffff880`0f1fc584 fffffa80`07dd0010 fffffa80`0ab37010 fffffa80`0ab32010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`043af540 fffff880`0fda8f07 : fffffa80`07dd0010 00000000`00000000 fffffa80`0ab37010 fffffa80`0ab32010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`043af570 fffff880`0fdd6d5a : fffffa80`ffffffff 00000000`000bcaaf fffff880`043af6c0 00000000`00000006 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`043af650 fffff880`0fdbcbb1 : fffffa80`0ab62000 ffffffff`feced300 00000000`00000006 fffffa80`0ab62000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`043af690 fffff880`0fdba04c : 00000000`00000001 fffff8a0`0c40b410 fffffa80`0ab62000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`043af790 fffff880`0fdb7803 : 00000000`00000000 fffffa80`0a068000 00000000`00000014 fffff8a0`0c40b410 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xfc
fffff880`043af7d0 fffff880`0fdd165d : 00000000`00000000 fffff8a0`0f138980 fffffa80`00000000 fffffa80`075aadc0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd6f
fffff880`043af9a0 fffff880`0fdd1398 : fffff800`00b96080 fffff880`0fdd0d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`043afb90 fffff880`0fdd0e96 : 00000000`00000000 fffffa80`07b51920 00000000`00000080 fffffa80`0ab32010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`043afbc0 fffff800`02f1be6a : 00000000`012474a8 fffffa80`0ab61060 fffffa80`06984990 fffffa80`0ab61060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`043afc00 fffff800`02c75ec6 : fffff800`02df7e80 fffffa80`0ab61060 fffff800`02e05cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`043afc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+14b584
fffff880`0f1fc584 4055 push rbp

SYMBOL_NAME: nvlddmkm+14b584

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

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,583 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:02:08 AM

Posted 07 October 2012 - 05:12 PM

1) You said you installed W7 on this brand new system. What did it ship with, why did you install a new OS, and from where did you obtain the OS DVD?

2) After installing the OS, did you install all of the appropriate drivers including the chipset driver?

3) Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#3 Barronno

Barronno
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:08 AM

Posted 07 October 2012 - 07:54 PM

1) I bought the computer without an operating system since I already had the W7Pro OEM, and therefore saved about 200 on the bill. The OS was bought from a group called e-academy, who sells software to public school teachers at a steep discount. I installed the W7 on a different computer prior to the one in question, and had no issues with the installation (clean install-- not upgrade).

2) I installed all the drivers from the manufacturer (clevo). These were downloaded from the clevo website to make sure they were up to date, in addition to the nvidia driver for the gtx675, and the other 3rd party manufacturers. Drivers were installed for the chipset,audio, USB 3.0, video (intel and nvidia), LAN, wireless, and many other on board hardware devices (webcam, card reader ect.)

3) I will run the blue screen view soon, and share the results in my next post. Thank you for taking the time to help me out on this.

#4 Barronno

Barronno
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:08 AM

Posted 07 October 2012 - 10:22 PM

==================================================
Dump File : 100712-7924-01.dmp
Crash Time : 10/7/2012 2:48:01 PM
Bug Check String :
Bug Check Code : 0x00000116
Parameter 1 : fffffa80`07dd0010
Parameter 2 : fffff880`0f1fc584
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000002
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100712-7924-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 461,704
==================================================

==================================================
Dump File : 100612-8205-01.dmp
Crash Time : 10/6/2012 8:21:16 PM
Bug Check String :
Bug Check Code : 0x00000116
Parameter 1 : fffffa80`09ff44e0
Parameter 2 : fffff880`0f1cc584
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000002
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100612-8205-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 561,312
==================================================

==================================================
Dump File : 100612-13837-01.dmp
Crash Time : 10/6/2012 4:04:40 PM
Bug Check String :
Bug Check Code : 0x00000116
Parameter 1 : fffffa80`07d77310
Parameter 2 : fffff880`0f205584
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000002
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100612-13837-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 457,440
==================================================

#5 Allan

Allan

  • BC Advisor
  • 8,583 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:02:08 AM

Posted 08 October 2012 - 06:48 AM

First, I'm not sure your Windows 7 license permits installation on multiple machines. But okay, for the moment let's move on. The info you provided from BSV is not the info I wanted. Still, that particular error typically points to a problem with the video card or driver.

Open Device Manager - are there any yellow or red symbols?
Make sure you have the correct and latest driver for your video card (obtain the driver from the website of the video card manufacturer)
Download and (re)install DirectX (http://www.microsoft.com/en-us/download/details.aspx?id=35)

#6 Barronno

Barronno
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:08 AM

Posted 08 October 2012 - 07:18 PM

The windows license supports installation on two machines, which in this case would be my old and new laptops.

There are no apparent flags on the device manager.

I have installed the most recent driver from the nvidia driver page.

I apologize that I could not get you the correct info from the BSV. You'd think a school teacher could follow directions well :).

I'll try re-installing direct x and get back to you.

Anything else I should try in case that doesn't work?

One thing that crossed my mind-- I installed 3 drivers for video. One intel driver for the integrated 4000 chip, and two for nividia. One was the 675 driver from the nividia site mentioned above. The other came from Clevo (maker of the notebook) who listed a VGA Nvidia driver that was not "optional". Could these two drivers be conflicting with each other? Thanks again for all your help.

#7 Barronno

Barronno
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:08 AM

Posted 08 October 2012 - 08:15 PM

I tried to re-install direct x but it said I had a newer version than the download, and no installation was required--> exit. There was a device driver installation warning that flashed for about 5 seconds before it disappeared. I didn't get to read it before it disappeared.

#8 Allan

Allan

  • BC Advisor
  • 8,583 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:02:08 AM

Posted 09 October 2012 - 06:49 AM

Okay, then don't worry about direct-x.

Sorry, I missed the part about this being a laptop (my fault, you state it clearly in your first post). Drivers for laptops should always and ONLY be obtained from the website of the laptop manufacturer. Uninstall ALL video drivers then reinstall the one from the laptop manufacturer.

#9 Barronno

Barronno
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:08 AM

Posted 09 October 2012 - 09:28 PM

I uninstalled the video driver and replaced it with an older one downloaded from the Clevo website. Interestingly, they had 2 video driver downloads for Nvidia. One was listed as "nVIDIA VGA driver for Windows 7 64-bit" which I re-installed, and the other was listed as "nVIDIA GTX670MX/GTX675MX/GTX680M VGA card driver for Windows 7 64-bit version". The latter when installed from the Clevo download (instead of from the nvidia website) said a I did not have compatible hardware. The device manager shows no flags at this point, and even thought the re-installed driver appears to be an older version, the device manager says its up to date when prompted to look online for updates. I'll continue testing to see if any more blue screens appear now that the driver has been re-installed. Thank you again for all your help in troubleshooting this issue. I appreciate your time and patience in helping a novice tech enthusiast with a new project.

#10 Allan

Allan

  • BC Advisor
  • 8,583 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:02:08 AM

Posted 10 October 2012 - 06:41 AM

When a driver says "no compatible hardware found" during installation it means that the driver is for a different model than you have. You want the other driver.

#11 chrisd87

chrisd87

  • Members
  • 811 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NC
  • Local time:01:08 AM

Posted 10 October 2012 - 08:00 AM

When a driver says "no compatible hardware found" during installation it means that the driver is for a different model than you have. You want the other driver.


Also it could mean that it can't detect the hardware. I had a video card in my desktop the the pcie slot wasn't detecting. I tried to install the nvidia drivers thinking that it was a driver issue and it said no compatible hardware found. So I then moved the card to another slot, and the PC recognized it and the drivers installed successfully.

Glad you got it working. Let us know if you need anymore help in the future.

Edited by chrisd87, 10 October 2012 - 08:02 AM.

"Like car accidents, most hardware problems are due to driver ɹoɹɹǝ."

 


#12 Barronno

Barronno
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:08 AM

Posted 10 October 2012 - 09:53 PM

I'm pretty sure since this is a laptop, and it is not capable of SLI or Crossfire there should be only one MXM Pci slot for the 675m. Also, the nvidia control center just prompted me to update my driver to version 306.97 which was released today. I'll update and see if anything changes. Thanks to both of you for helping me out on this.

#13 chrisd87

chrisd87

  • Members
  • 811 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NC
  • Local time:01:08 AM

Posted 10 October 2012 - 10:35 PM

make sure you do a clean installation of the Nvidia drivers. go to custom installation when it asks and choose the box that says clean installation.

"Like car accidents, most hardware problems are due to driver ɹoɹɹǝ."

 


#14 hamluis

hamluis

    Moderator


  • Moderator
  • 55,550 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:08 AM

Posted 11 October 2012 - 05:53 PM

<<The windows license supports installation on two machines, which in this case would be my old and new laptops.>>

FWIW: There is no OEM, authorized version of Windows...that sanctions installation on a second, differing system. The closest thing to such would be the MS Win 7 family pack, which authorizes install on 3 different systems, using the same license...and this is restricted to the Win 7 Home Premium Upgrade version.

Louis

#15 Barronno

Barronno
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:08 AM

Posted 11 October 2012 - 10:34 PM

I didn't know that about the OEM. Granted, the disk installed and activated without issues on both machines. Chris87, I did the custom clean install, and haven't seen any issues as of yet. I'll post again if the bsod returns. Thanks to all for helping me out.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users