Crashing..... BSOD 0x119

alwazir5959 · Aug 11, 2012

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 119
BCP1: 0000000000000001
BCP2: 000000000000003D
BCP3: 0000000000000006
BCP4: 0000000000000006
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\081112-18486-01.dmp
C:\Users\Richard\AppData\Local\Temp\WER-34975-0.sysdata.xml

Tekno Venus · Aug 11, 2012

Re: Crashing.

Hello and welcome to Sysnative!

Recommendations

Problem Devices
Please install the drivers for the following devices. Devices without drivers can be unstable and cause BSOD's. Also, the device causing an error 52 is a Razor mouse. They are known BSOD causers. Please uninstall all Razer software from control panel and then change to a 'normal' mouse for the duration of the troubleshooting.

Code:

Razer Nostromo    ROOT\HIDCLASS\0000    52
SBRE    ROOT\LEGACY_SBRE\0000    This device is not present, is not working properly, or does not have all its drivers installed.

BSOD Analysis

Graphics Card/DirectX
Looking at your dumps, I see know definitive cause. The dumps mainly point to hardware and possibly the graphics card. Some dumps just blamed the Windows kernel, which won't cause BSOD's. The rest showed a possible graphics card/DirectX issue. DirectX is built into Windows, so it could also mean a possible file corruption. So, to resolve this, work through the below steps.

Please run the sfc /scannow checker to check and repair important system files. To do so, follow the below steps.

Open a command prompt window as an administrator. To do so, click Start and type cmd. Don't press enter!. Then right click the top entry(cmd.exe) and then "Run as Administrator"
Type the following command - sfc /scannow and press enter. Note - there is a space between the sfc and the /scannow
Wait!

If it reports that Windows Resource Protection did not find any integrity violations, then all is well. If it attempts to repair files, attach the CBS.log file to your next post. It is located here C:\Windows\Logs\CBS\CBS.log.

Then, follow the steps for http://windows.microsoft.com/en-US/windows7/Diagnosing-basic-problems-with-DirectX. If that proves unsuccessful and doesn't solve the BSOD's, then try to reinstall your graphics card drivers by following these steps.

Read More:

Work through each of these steps and report back after you've completed each one. If you have any questions, feel free to ask
Stephen

ANALYSIS
The following is for informational purposes only, I have resolved all the issues in the above steps.

Dump files

Code:

**************************Sat Aug 11 17:59:20.254 2012 (UTC + 1:00)**************************
Loading Dump File [C:\Users\Stephen\Documents\Computer Stuff\BSOD Dumps\Sysnative\alwazir5959\Windows7_Vista_jcgriff2\081112-18486-01.dmp]
 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
 
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
 
System Uptime: 0 days 0:06:49.236
 
BugCheck 119, {1, 3d, 6, 6}
 
*** WARNING: Unable to verify timestamp for atikmpag.sys
 
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
 
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
 
VIDEO_SCHEDULER_INTERNAL_ERROR (119)
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
BUGCHECK_STR:  0x119
 
PROCESS_NAME:  svchost.exe
 
FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
 
  BIOS Version                  080015 
 
  BIOS Release Date             04/20/2010
 
  Manufacturer                  BIOSTAR Group
 
  Product Name                  TA890GXB HD
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug 11 05:38:44.168 2012 (UTC + 1:00)**************************
Loading Dump File [C:\Users\Stephen\Documents\Computer Stuff\BSOD Dumps\Sysnative\alwazir5959\Windows7_Vista_jcgriff2\081112-20358-01.dmp]
 
Loading Dump File [C:\Users\Stephen\Documents\Computer Stuff\BSOD Dumps\Sysnative\alwazir5959\Windows7_Vista_jcgriff2\081012-20779-01.dmp]
 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
 
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
 
System Uptime: 0 days 4:59:01.994
 
BugCheck 1A, {41287, 30, 0, 0}
 
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42625 )
 
MEMORY_MANAGEMENT (1a)
 
BUGCHECK_STR:  0x1a_41287
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42625
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug 11 00:18:52.500 2012 (UTC + 1:00)**************************
Loading Dump File [C:\Users\Stephen\Documents\Computer Stuff\BSOD Dumps\Sysnative\alwazir5959\Windows7_Vista_jcgriff2\081012-24570-01.dmp]
 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
 
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
 
System Uptime: 0 days 4:35:28.342
 
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
 
BugCheck 24, {1904fb, fffff88009b92b28, fffff88009b92390, fffff88001228147}
 
Probably caused by : Ntfs.sys ( Ntfs+d147 )
 
NTFS_FILE_SYSTEM (24)
 
PROCESS_NAME:  WerFault.exe
 
BUGCHECK_STR:  0x24
 
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
 
FAILURE_BUCKET_ID:  X64_0x24_Ntfs+d147
 
  BIOS Version                  080015 
 
  BIOS Release Date             04/20/2010
 
  Manufacturer                  BIOSTAR Group
 
  Product Name                  TA890GXB HD
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Aug 10 19:42:46.071 2012 (UTC + 1:00)**************************
Loading Dump File [C:\Users\Stephen\Documents\Computer Stuff\BSOD Dumps\Sysnative\alwazir5959\Windows7_Vista_jcgriff2\081012-28158-01.dmp]
 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
 
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
 
System Uptime: 0 days 0:04:49.523
 
BugCheck 119, {1, 5e4, 52c, 52c}
 
*** WARNING: Unable to verify timestamp for atikmpag.sys
 
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
 
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
 
VIDEO_SCHEDULER_INTERNAL_ERROR (119)
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
BUGCHECK_STR:  0x119
 
PROCESS_NAME:  WinSAT.exe
 
FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
 
  BIOS Version                  080015 
 
  BIOS Release Date             04/20/2010
 
  Manufacturer                  BIOSTAR Group
 
  Product Name                  TA890GXB HD
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Aug 10 19:37:18.580 2012 (UTC + 1:00)**************************
Loading Dump File [C:\Users\Stephen\Documents\Computer Stuff\BSOD Dumps\Sysnative\alwazir5959\Windows7_Vista_jcgriff2\081012-26442-01.dmp]
 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
 
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
 
System Uptime: 0 days 0:21:12.421
 
BugCheck 4E, {7, 12b99c, 1, 0}
 
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
 
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
 
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
 
*** WARNING: Unable to verify checksum for win32k.sys
 
Probably caused by : afd.sys ( afd+570d )
 
PFN_LIST_CORRUPT (4e)
 
BUGCHECK_STR:  0x4E_7
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  X64_0x4E_7_afd+570d
 
  BIOS Version                  080015 
 
  BIOS Release Date             04/20/2010
 
  Manufacturer                  BIOSTAR Group
 
  Product Name                  TA890GXB HD
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Aug 10 19:15:34.373 2012 (UTC + 1:00)**************************
Loading Dump File [C:\Users\Stephen\Documents\Computer Stuff\BSOD Dumps\Sysnative\alwazir5959\Windows7_Vista_jcgriff2\081012-25287-01.dmp]
 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
 
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
 
System Uptime: 0 days 1:41:41.199
 
BugCheck 3B, {c0000005, fffff960000fb492, fffff8800807c940, 0}
 
Probably caused by : win32k.sys ( win32k!ThreadUnlock1+12 )
 
SYSTEM_SERVICE_EXCEPTION (3b)
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
BUGCHECK_STR:  0x3B
 
PROCESS_NAME:  explorer.exe
 
FAILURE_BUCKET_ID:  X64_0x3B_win32k!ThreadUnlock1+12
 
  BIOS Version                  080015 
 
  BIOS Release Date             04/20/2010
 
  Manufacturer                  BIOSTAR Group
 
  Product Name                  TA890GXB HD
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Aug 10 17:33:21.371 2012 (UTC + 1:00)**************************
Loading Dump File [C:\Users\Stephen\Documents\Computer Stuff\BSOD Dumps\Sysnative\alwazir5959\Windows7_Vista_jcgriff2\081012-21871-01.dmp]
 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
 
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
 
System Uptime: 0 days 0:01:21.823
 
BugCheck 7F, {8, 80050031, 6f8, fffff80003095b84}
 
*** WARNING: Unable to verify checksum for win32k.sys
 
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
 
UNEXPECTED_KERNEL_MODE_TRAP (7f)
 
BUGCHECK_STR:  0x7f_8
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
 
  BIOS Version                  080015 
 
  BIOS Release Date             04/20/2010
 
  Manufacturer                  BIOSTAR Group
 
  Product Name                  TA890GXB HD
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Aug 10 06:38:58.438 2012 (UTC + 1:00)**************************
Loading Dump File [C:\Users\Stephen\Documents\Computer Stuff\BSOD Dumps\Sysnative\alwazir5959\Windows7_Vista_jcgriff2\081012-21637-01.dmp]
 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
 
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
 
System Uptime: 0 days 9:17:56.264
 
BugCheck 1A, {41284, 1b38001, 0, fffff70001080000}
 
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a13 )
 
MEMORY_MANAGEMENT (1a)
 
BUGCHECK_STR:  0x1a_41284
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
PROCESS_NAME:  WerFault.exe
 
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a13
 
  BIOS Version                  080015 
 
  BIOS Release Date             04/20/2010
 
  Manufacturer                  BIOSTAR Group
 
  Product Name                  TA890GXB HD
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Aug  9 21:20:31.228 2012 (UTC + 1:00)**************************
Loading Dump File [C:\Users\Stephen\Documents\Computer Stuff\BSOD Dumps\Sysnative\alwazir5959\Windows7_Vista_jcgriff2\080912-20716-01.dmp]
 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
 
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
 
System Uptime: 0 days 5:30:46.679
 
BugCheck 116, {fffffa8005eed4e0, fffff88003e43768, 0, 2}
 
*** WARNING: Unable to verify timestamp for atikmpag.sys
 
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
 
*** WARNING: Unable to verify checksum for win32k.sys
 
Probably caused by : atikmpag.sys ( atikmpag+8768 )
 
VIDEO_TDR_FAILURE (116)
 
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
 
BUGCHECK_STR:  0x116
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
 
  BIOS Version                  080015 
 
  BIOS Release Date             04/20/2010
 
  Manufacturer                  BIOSTAR Group
 
  Product Name                  TA890GXB HD
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Shintaro · Aug 11, 2012

Re: Crashing.

May I suggest that the OP start with installing SP1.
http://windows.microsoft.com/en-AU/windows7/install-windows-7-service-pack-1

Tekno Venus · Aug 11, 2012

Re: Crashing.

Thanks! I completly missed that, been at my computer to long I think. :grin1:

Stephen

Shintaro · Aug 11, 2012

Re: Crashing.

Not a problem. We are all here to help each other.

alwazir5959 · Aug 12, 2012

Re: Crashing.

As requested and thank you so much guys i cant take another day of it.

Patrick · Aug 12, 2012

According to the CBS log, unless I'm missing something... it looks like whatever repairs needed to be made went through without issue. If you're still BSOD'ing, can you attach the latest crash dumps?

Regards,

Patrick

Tekno Venus · Aug 12, 2012

I agree with Patrick, could you please upload the latest dumps. I feel we have some kind of graphics card/driver issue so continue with the DirectX/Driver reinstall steps. When we get more dumps, we'll see if we can find anything else.

Stephen

Search

Search

Crashing..... BSOD 0x119

alwazir5959

New member

Tekno Venus

Senior Administrator, Developer

Shintaro

Well-known member

Tekno Venus

Senior Administrator, Developer

Shintaro

Well-known member

alwazir5959

New member

Attachments

Patrick

Sysnative Staff

Tekno Venus

Senior Administrator, Developer