Solved Probably video (???) related BSOD error 0x00000119

[Diazruanova]

Hi everybody, glad to be here

I started having BSOD´s from a week ago, at least once a day while doing almost anything: Browsing the internet, editing photos with Photoshop elements or using my music recording program (Cubase 6) and after doing some research, I downloaded BlueScreenView 1.52 and it says something about the problem being related to Watchdog Driver, DirectX Graphics MMS and ATI radeon kernel mode driver (in that order)

Please take a look at the attached JPG besides the requested Zip file, also attached.

I am totally computer illiterate and these are my first BSOD and it looks scary to say the least, so please any advice(s) to help me solve this problem will be very appreciated!!!

Thanks a lot in advance!

 

[HarriePateman]

Hello can you add English zip file please!

 

[Arc]

Hi Diazruanova.

A stop 0x119 is usually a display/graphics related issue. And, overclocking is an enough reason to cause it.

CPUID:        "Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz"
MaxSpeed:     2800
[COLOR=Red]CurrentSpeed: 2940[/COLOR]

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Uninstall your installed latest version of the display driver.

• How-To Uninstall AMD Catalyst Drivers From A Windows Based System

Then clean up any possible leftover.

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

Then install version 13.9 WHQL only.

• Previous AMD Catalyst? Display Drivers

You may try to apply the F11 BIOS, too. It is available in GIGABYTE - Motherboard - Socket 1156 - GA-H55M-USB3 (rev. 2.0)

Also you should update the JMicron JMB36X Controller from ftp://driver.jmicron.com.tw/SATA_Controller/Windows/ , suggesting it because everytime I have noticed an invalid fence ID, itere is something inappropriate with the SCSI setup.

Let us know the results.
________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 119, {1, 5360b, 53a04, 53a03}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+45b36 )

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

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

[COLOR=Red]VIDEO_SCHEDULER_INTERNAL_ERROR (119)[/COLOR]
[COLOR=Red]The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress.[/COLOR] Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, [COLOR=Red]The driver has reported an invalid fence ID.[/COLOR]
Arg2: 000000000005360b
Arg3: 0000000000053a04
Arg4: 0000000000053a03

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  5

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE:  FFFFF880025DFFB0

LAST_CONTROL_TRANSFER:  from fffff880015ec22f to fffff800026ccbc0

STACK_TEXT:  
fffff880`025d8428 fffff880`015ec22f : 00000000`00000119 00000000`00000001 00000000`0005360b 00000000`00053a04 : nt!KeBugCheckEx
fffff880`025d8430 fffff880`04968ec5 : fffff880`03c87e17 00000000`0005360b 00000000`00000000 00000000`00053a04 : watchdog!WdLogEvent5+0x11b
fffff880`025d8480 fffff880`04969131 : fffffa80`07e99000 fffff880`025d85c0 00000000`000011ac fffff880`04969480 : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff880`025d84b0 fffff880`04968f82 : fffff880`0005360b fffff880`049690c8 fffffa80`07ea4000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x19d
fffff880`025d8500 fffff880`0487013f : fffffa80`07a1e290 00000000`00000000 00000000`0791e001 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`025d8530 fffff880`03969b36 : 00000000`00000000 00000000`00000001 fffff880`025d85e9 00000000`00000000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`025d8560 00000000`00000000 : 00000000`00000001 fffff880`025d85e9 00000000`00000000 fffff880`025d8620 : atikmpag+0x45b36


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmpag+45b36
fffff880`03969b36 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  atikmpag+45b36

FOLLOWUP_NAME:  MachineOwner

[COLOR=Red]MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  52a231d9

FAILURE_BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+45b36

BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+45b36

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x119_1_driver_reported_invalid_fence_id_atikmpag+45b36

FAILURE_ID_HASH:  {1d656d04-b896-4c50-1a4b-ca7fd5789058}

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

5: kd> lmvm atikmpag
start             end                 module name
fffff880`03924000 fffff880`039c4000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
[COLOR=Red]    Image name: atikmpag.sys
    Timestamp:        Sat Dec 07 01:51:45 2013[/COLOR] (52A231D9)
    CheckSum:         0009FEFF
    ImageSize:        000A0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Diazruanova]

Thanks for your reply Arc and sorry for the delay,

I will follow your indications, but I was wondering, since I have had this configuration (overclock, GPU driver version, hardware untouched included the PSU, for almost six months) if it is possible for this BSOD to appear because of a sudden GPU malfunction?

Also, the problem appears almost immediately after turning on the PC in the morning, so I guess we could rule out the heat and besides the room temp is cool enough and generally, after the BSOD appears, I re start the PC and it keeps working the rest of the labor day without problems.

Meanwhile, I am attaching SOME of the requested info:

1.- Furmark´s stress test JPG (I ran the test for almost 40 Min without any artifacts or dangerous high temperature, so the Min Temp was 51°C - 123.8F and a Max temp of 72°C - 161.6F with a max fan speed of 82%)

2.- eXtreme Power Supply Calculator PDF. Please note that the installed PSU is a Corsair GS500 - 500W

3.- Speccy Summary tab screenshot JPG

4.- JMicron MB36X Controller latest version: It seems from the attached JPG screenshot that I am using the very latest version, should I install it again?

Thanks again and I´ll do the rest of your suggestions later on.

 

[Diazruanova]

Sorry, It seems that the Speccy Summary JPG was not attached, so here it goes again.

 

[Arc]

Everything else seems good to me, other than the furmark screenshot. But you ran it for 40 minutes without any crashes, which also should be counted.

Now get rid of the overclocks and see if there is any change or not.

Overclocking is subject to cause hardware/graphics related BSODs. Despite of the fact that how long it ran stable. It can cause trouble anytime.

 

[Diazruanova]

Well, Yesterday I got rid of the overclock and today the PC has ran smooth without any BSOD, so before changing my video driver for the old one, I am giving it a couple of days and see if it was the overclocking. I´ll be in touch later.

 

[Diazruanova]

Everything else seems good to me, other than the furmark screenshot. But you ran it for 40 minutes without any crashes, which also should be counted.

Now get rid of the overclocks and see if there is any change or not.

Overclocking is subject to cause hardware/graphics related BSODs. Despite of the fact that how long it ran stable. It can cause trouble anytime.

Hi again Arc,

It seems that overclocking was NOT the culprit, because today in the morning I had another BSOD, so I proceeded to un-install (and cleaned the installation with DDU.exe latest ver) the most recent Catalyst driver and reverted it back to the suggested 13.9 but I am not sure if it was correct to install the whole package, Control Center included !! ...do I have to repeat the process without the control center?

Thanks for your kind attention.

 

[Arc]

CCC is problematic. But not always. Let us see how it goes. Upload the subsequent crash dumps to let us see the situations.

 

[Diazruanova]

Hi again,

Just a follow up to inform that since the installation of the Catalyst driver version 13.9 WHQL about 6 days ago,there
has not been any BSOD, but I think I´ll wait a week or so to close as solved this thread, anyway it seems that the video driver was the culprit, so far so good

 

[Arc]

Ok, take your time.

 

[Diazruanova]

Thank you very much Arc for your kind attention and help, I think this is already solved, since I have had no more BSOD!!! , so I am marking it as solved.

Have a nice week end!

 

[Arc]

Good news.

Let us know for any further issue.