none
Windows 7 Blue Screen Video Scheduler

    Question

  • Hi, 

     

    I am currently running Windows 7 Enterprise 32-bit edition.  My computer has randomly been hanging and then giving me a blue screen of death.  At the bottom of this message, I have posted the error that pops up when my computer finishes rebooting.  I have run sfc /scannow and no violations are found.  I also have the latest driver for my video card.  I have also uploaded the dumps into my SkyDrive and here is the link:  http://cid-460e2205e74c9830.office.live.com/self.aspx/.Public/112810-21013-01.zip

    Please help me as I have finals coming up soon! 

     

    Problem signature:

      Problem Event Name: BlueScreen

      OS Version: 6.1.7600.2.0.0.256.4

      Locale ID: 1033

     

    Additional information about the problem:

      BCCode: 119

      BCP1: 00000001

      BCP2: 0003934F

      BCP3: 00039352

      BCP4: 00039351

      OS Version: 6_1_7600

      Service Pack: 0_0

      Product: 256_1

     

    Tuesday, November 30, 2010 6:44 AM

Answers

  • Bug Check 0x119: VIDEO_SCHEDULER_INTERNAL_ERROR

    This indicates that the video scheduler has detected a fatal violation.

    http://msdn.microsoft.com/en-us/library/ff557275%28VS.85%29.aspx


    Update your extremely old ATI driver, please:

        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Mon Dec 01 22:01:46 2008

    STACK_TEXT: 
    80786878 8ef81276 00000119 00000001 0003934f nt!KeBugCheckEx+0x1e
    807868a0 944f7b2c 06000000 86a9d518 88938000 watchdog!WdLogEvent5+0xc6
    807868bc 944fd90f 000011ac 0003934f 00000000 dxgmms1!VidSchiVerifyDriverReportedFenceId+0x8c
    807868f0 944fdf6d 88938000 80786950 00000001 dxgmms1!VidSchDdiNotifyInterruptWorker+0x16f
    8078690c 9443bbdb 85147920 80786950 80786934 dxgmms1!VidSchDdiNotifyInterrupt+0x7b
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8078691c 9443bc5e 8679b768 85147920 80786950 dxgkrnl+0x1bdb
    80786934 8f828469 85147920 80786950 86a49000 dxgkrnl+0x1c5e
    807869f0 8f82838d 80786a08 8f832c71 883521c0 atikmdag+0x18469
    807869f8 8f832c71 883521c0 80786a7c 80786a58 atikmdag+0x1838d
    80786a08 8f94f2fa 86b02000 80786a18 00000040 atikmdag+0x22c71
    80786a58 8f9539cf 86a49000 8f828364 883521c0 atikmdag+0x13f2fa
    80786aa4 8f953ad3 86a49000 86a4c000 885b2a38 atikmdag+0x1439cf
    80786af0 8f953b64 85dc0022 82f36654 82f34d05 atikmdag+0x143ad3
    80786b10 83220ba9 82f34d20 00000005 80786b50 atikmdag+0x143b64

    80786b20 00000000 80786b7c 00000000 00000000 hal!KfLowerIrql+0x61

    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 000000f6, Referencing user handle as KernelMode.

    STACK_TEXT: 
    967d220c 8316bf1f 000000c4 000000f6 000001e0 nt!KeBugCheckEx+0x1e
    967d222c 83170782 000001e0 8f422958 8f42c7a0 nt!VerifierBugCheckIfAppropriate+0x30
    967d22c0 8305b2f3 967d24a4 967d240c 967d2414 nt!VfCheckUserHandle+0x14f
    967d22f4 8305b1ad 000001e0 00000001 8073ede8 nt!ObReferenceObjectByHandleWithTag+0x13b
    967d2318 830b8e84 000001e0 00000001 8073ede8 nt!ObReferenceObjectByHandle+0x21
    967d2374 82e7a44a 000001e0 967d2414 967d24a4 nt!NtQuerySymbolicLinkObject+0xee
    967d2374 82e78ded 000001e0 967d2414 967d24a4 nt!KiFastCallEntry+0x12a
    967d23f8 8d1cc9e3 000001e0 967d2414 967d24a4 nt!ZwQuerySymbolicLinkObject+0x11
    WARNING: Stack unwind information not available. Following frames may be wrong.
    967d24c0 8d1ccc1a 81f34800 8ade0800 c0000001 AMonTDLH+0xf9e3

        Image path: \??\C:\Windows\system32\Drivers\AMonTDLH.sys
        Image name: AMonTDLH.sys
        Timestamp:        Mon May 24 03:44:18 2010

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

    STACK_TEXT: 
    8b30fc8c 98568015 82f415bc c000000e 8a365ab8 nt!IofCallDriver+0x5f
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8b30fcc0 98569502 8a374000 8a365ab8 9fc33650 ATSwpDrv+0x10015
    8b30fcd4 98569582 8a365ab8 00000001 873041b8 ATSwpDrv+0x11502
    8b30fcec 83027815 8a365a00 9fc33650 850b7020 ATSwpDrv+0x11582

    8b30fd00 82e74f3b 873041b8 00000000 850b7020 nt!IopProcessWorkItem+0x23
    8b30fd50 830156d3 00000001 a9303d54 00000000 nt!ExpWorkerThread+0x10d
    8b30fd90 82ec70f9 82e74e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

        Image path: \SystemRoot\system32\DRIVERS\ATSwpDrv.sys
        Image name: ATSwpDrv.sys
        Timestamp:        Tue Aug 28 21:47:32 2007



    Update those drivers, to fix the crashes.

    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, November 30, 2010 3:00 PM

All replies

  • Bug Check 0x119: VIDEO_SCHEDULER_INTERNAL_ERROR

    This indicates that the video scheduler has detected a fatal violation.

    http://msdn.microsoft.com/en-us/library/ff557275%28VS.85%29.aspx


    Update your extremely old ATI driver, please:

        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Mon Dec 01 22:01:46 2008

    STACK_TEXT: 
    80786878 8ef81276 00000119 00000001 0003934f nt!KeBugCheckEx+0x1e
    807868a0 944f7b2c 06000000 86a9d518 88938000 watchdog!WdLogEvent5+0xc6
    807868bc 944fd90f 000011ac 0003934f 00000000 dxgmms1!VidSchiVerifyDriverReportedFenceId+0x8c
    807868f0 944fdf6d 88938000 80786950 00000001 dxgmms1!VidSchDdiNotifyInterruptWorker+0x16f
    8078690c 9443bbdb 85147920 80786950 80786934 dxgmms1!VidSchDdiNotifyInterrupt+0x7b
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8078691c 9443bc5e 8679b768 85147920 80786950 dxgkrnl+0x1bdb
    80786934 8f828469 85147920 80786950 86a49000 dxgkrnl+0x1c5e
    807869f0 8f82838d 80786a08 8f832c71 883521c0 atikmdag+0x18469
    807869f8 8f832c71 883521c0 80786a7c 80786a58 atikmdag+0x1838d
    80786a08 8f94f2fa 86b02000 80786a18 00000040 atikmdag+0x22c71
    80786a58 8f9539cf 86a49000 8f828364 883521c0 atikmdag+0x13f2fa
    80786aa4 8f953ad3 86a49000 86a4c000 885b2a38 atikmdag+0x1439cf
    80786af0 8f953b64 85dc0022 82f36654 82f34d05 atikmdag+0x143ad3
    80786b10 83220ba9 82f34d20 00000005 80786b50 atikmdag+0x143b64

    80786b20 00000000 80786b7c 00000000 00000000 hal!KfLowerIrql+0x61

    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 000000f6, Referencing user handle as KernelMode.

    STACK_TEXT: 
    967d220c 8316bf1f 000000c4 000000f6 000001e0 nt!KeBugCheckEx+0x1e
    967d222c 83170782 000001e0 8f422958 8f42c7a0 nt!VerifierBugCheckIfAppropriate+0x30
    967d22c0 8305b2f3 967d24a4 967d240c 967d2414 nt!VfCheckUserHandle+0x14f
    967d22f4 8305b1ad 000001e0 00000001 8073ede8 nt!ObReferenceObjectByHandleWithTag+0x13b
    967d2318 830b8e84 000001e0 00000001 8073ede8 nt!ObReferenceObjectByHandle+0x21
    967d2374 82e7a44a 000001e0 967d2414 967d24a4 nt!NtQuerySymbolicLinkObject+0xee
    967d2374 82e78ded 000001e0 967d2414 967d24a4 nt!KiFastCallEntry+0x12a
    967d23f8 8d1cc9e3 000001e0 967d2414 967d24a4 nt!ZwQuerySymbolicLinkObject+0x11
    WARNING: Stack unwind information not available. Following frames may be wrong.
    967d24c0 8d1ccc1a 81f34800 8ade0800 c0000001 AMonTDLH+0xf9e3

        Image path: \??\C:\Windows\system32\Drivers\AMonTDLH.sys
        Image name: AMonTDLH.sys
        Timestamp:        Mon May 24 03:44:18 2010

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

    STACK_TEXT: 
    8b30fc8c 98568015 82f415bc c000000e 8a365ab8 nt!IofCallDriver+0x5f
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8b30fcc0 98569502 8a374000 8a365ab8 9fc33650 ATSwpDrv+0x10015
    8b30fcd4 98569582 8a365ab8 00000001 873041b8 ATSwpDrv+0x11502
    8b30fcec 83027815 8a365a00 9fc33650 850b7020 ATSwpDrv+0x11582

    8b30fd00 82e74f3b 873041b8 00000000 850b7020 nt!IopProcessWorkItem+0x23
    8b30fd50 830156d3 00000001 a9303d54 00000000 nt!ExpWorkerThread+0x10d
    8b30fd90 82ec70f9 82e74e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

        Image path: \SystemRoot\system32\DRIVERS\ATSwpDrv.sys
        Image name: ATSwpDrv.sys
        Timestamp:        Tue Aug 28 21:47:32 2007



    Update those drivers, to fix the crashes.

    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, November 30, 2010 3:00 PM
  • Before replying with advice that doesn't help, please read my query in detail.  You'll notice that I mentioned that all the drivers are already up to date.  10 driver versions have been released for the ATI Mobility Radeon X2300.  The latest driver was released on 12/1/2008.  This matches the timestamp in the dump file.  It is not a driver issue.  Do not reply if you do not have an answer that will help me. 
    Tuesday, November 30, 2010 5:23 PM
  • instead of trolling around update the 2 other drivers.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, November 30, 2010 10:32 PM
  • why don't you actually be of some help and tell me which drivers to update?  i understand that those file names in bold are the drivers to be replaced.  how, as a novice computer user, am i supposed to identify which devices those drivers apply to and how i should update them? please stop "trolling" around and be of some real assistance. 
    Wednesday, December 01, 2010 5:45 PM
  • sorry, this is my last reply. I told you everything. Click on the file properties to see that name of the manufacture and get the latest driver from the homepage.
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Wednesday, December 01, 2010 6:56 PM