BSOD happening very sporadically. Possibly the sata card?

jivex5k · 02 Feb 2012

Greetings all.
First and foremost I'd like to thank the individuals who take time out to help others analyze problems. I stumbled across this board yesterday and have already learned quite a bit about analyzing BSODs.

Anyways, I've got a fairly new computer, it's about 4 months old with all new hardware:
Windows 7 64bit Embedded installed from scratch.
(I use the application compatibility template when building the image.)
I put it together myself with all unused hardware.
The OS was installed from scratch 4 months ago.

I actually looked over the dumps with winDBG, says the probable cause is dxgmms1.sys
After a quick search it seems like a faulty driver could be the issue. I did find there was a sata card that had been disabled, I re-enabled it and it had a missing driver.
I've installed the correct one now and it hasn't crashed again yet, but only time will tell if it truly fixed it since the machine could work for a week before crashing.

Anyways, any more insight on this would be greatly appreciated.
Thanks!

mgorman87 · 02 Feb 2012

All your crashes are the same STOP 0x119 and blame your video card driver

What type of motherboard do you have? Is it a Foxconn H61A?

Code:

igdkmd64.sys Fri Oct 01 17:14:28 2010 (4CA64F34)

Because you are using on board video, it's hard to find the correct download link for your video card.

Try running the Intel update utility and see if you can find a newer video card driver - http://downloadcenter.intel.com/

Your perfmon report says you don't have an AV installed?

You also have some devices that need to be addressed

Code:

SCSI Controller       This device is disabled.    
Standard PS/2 Keyboard      This device is not present, is not working properly, or does not have all its drivers installed.    
Not Available       The drivers for this device are not installed.    
Microsoft PS/2 Mouse     This device is not present, is not working properly, or does not have all its drivers installed.

The one in red belongs to "Microsoft Streaming Service Proxy". Don't know what that is or what to do to fix it. Check in device manager for unknown or problem devices and try to reinstall the drivers.

Your main concern though is to get your video drivers updated because that is what is causing the crashes. If you find a newer driver, great. If you don't, then download the latest drivers, go into device manager, uninstall your video card, reboot your computer and then install the driver package you just downloaded.

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 27 15:53:02.483 2012 (UTC - 5:00)
System Uptime: 1 days 0:02:42.373
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for watchdog.sys - 
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
BUGCHECK_STR:  0x119
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 16 08:32:00.368 2012 (UTC - 5:00)
System Uptime: 4 days 5:15:46.258
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for watchdog.sys - 
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
BUGCHECK_STR:  0x119
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 11 00:50:00.534 2012 (UTC - 5:00)
System Uptime: 1 days 15:47:18.424
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for watchdog.sys - 
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
BUGCHECK_STR:  0x119
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan  3 23:59:47.462 2012 (UTC - 5:00)
System Uptime: 6 days 12:24:34.352
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for watchdog.sys - 
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
BUGCHECK_STR:  0x119
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Dec 22 18:23:17.946 2011 (UTC - 5:00)
System Uptime: 1 days 3:22:29.836
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for watchdog.sys - 
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
BUGCHECK_STR:  0x119
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Dec 19 12:14:11.712 2011 (UTC - 5:00)
System Uptime: 3 days 0:14:24.602
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for watchdog.sys - 
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
BUGCHECK_STR:  0x119
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Dec 16 11:46:35.363 2011 (UTC - 5:00)
System Uptime: 2 days 0:19:54.253
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for watchdog.sys - 
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
BUGCHECK_STR:  0x119
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Nov 16 16:06:36.736 2011 (UTC - 5:00)
System Uptime: 7 days 12:50:24.627
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for watchdog.sys - 
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
BUGCHECK_STR:  0x119
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Oct 22 02:08:37.370 2011 (UTC - 5:00)
System Uptime: 8 days 23:51:54.261
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for watchdog.sys - 
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
BUGCHECK_STR:  0x119
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

jivex5k · 02 Feb 2012

Thanks for the detailed help =) It's a foxconn H67M actually.
I did find a newer integrated graphics driver and installed it so hopefully it will end the BSODs.
I also found an update for the LAN driver which I installed.

I'm not sure how to fix the PS/2 Mouse & Keyboard issue. Device manager shows everything installed correctly and the mouse and keyboard work fine.

I'm curious to how you were able to tell it was the graphics card. I was looking at dxgmms1.sys and thinking that was the cause but now that you mentioned the video card I noticed the igdkmd64.sys and realized that is the integrated graphics driver.
Should I always be looking at the first driver listed in crash analysis instead of the Probably caused section?

Thanks again btw, it's fun learning this stuff.

EDIT -- When I check out the dumps in my debugger it doesn't show that graphics driver. I can only guess it because I didn't install the symbol support.

mgorman87 · 02 Feb 2012

If you get a dump that says

*** ERROR: Symbol file could not be found. Defaulted to export symbols for watchdog.sys -
*** WARNING: Unable to verify timestamp for igdkmd64.sys

Then it is most likely that driver that caused the crash. If it is a windows driver that is
listed there then it is either hardware or another driver that's being masked by
the windows driver

jivex5k · 17 Feb 2012

It's strange I don't see that line in my debugger. I must have mine set up differently because this is the output I got:

Code:

Loading Dump File [C:\Users\brian\Downloads\Windows_NT6_BSOD_jcgriff2\122711-25646-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: c:\symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer EmbeddedNT SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a4a000 PsLoadedModuleList = 0xfffff800`02c8f670
Debug session time: Thu Dec 22 18:23:17.946 2011 (UTC - 5:00)
System Uptime: 1 days 3:22:29.836
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.......
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for watchdog.sys - 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 119, {1, 104923, 104925, 104925}

Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
Probably caused by : dxgmms1.sys ( dxgmms1+7eb9 )

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

Doesn't even list IGD in mine.
Oh BTW the driver update seems to have fixed the issue, thanks for all the help =)