Symptoms

Consider the following scenario:

  • You attach an LCD monitor to a computer that is running Windows 7 or Windows Server 2008 R2.

  • You install the related monitor driver on the computer.

  • You perform a WDF fault injection logo test for the monitor.

In this scenario, the computer crashes during the WDF Fault Injection Logo Test. Additionally, you receive a Stop error message that resembles the following:

Stop 0x000000C4 (Parameter1, Parameter2, Parameter3, Parameter4)


Notes

  • This Stop error describes a DRIVER_VERIFIER_DETECTED_VIOLATION issue.

  • The parameters in this Stop error message vary, depending on the configuration of the computer.

  • Not all "Stop 0x000000C4" errors are caused by this issue.

  • This issue does not occur when you use Generic PnP monitors.

Cause

This issue occurs because the monitor driver is unloaded and the Windows Management Instrumentation (WMI) registration flags leaks when the WdfDriverCreate() method fails in the DriverEntry routine.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.1.760
    1.18xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    GDR

    6.1.760
    1.22xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    LDR

  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 7

File name

File version

File size

Date

Time

Platform

Monitor.sys

6.1.7601.18049

23,552

11-Jan-2013

10:41

x86

Monitor.sys

6.1.7601.22215

23,552

11-Jan-2013

10:39

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Monitor.sys

6.1.7601.18049

30,208

11-Jan-2013

11:20

x64

Monitor.sys

6.1.7601.22215

30,208

11-Jan-2013

11:07

x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Monitor.sys

6.1.7601.18049

74,240

11-Jan-2013

10:36

IA-64

Monitor.sys

6.1.7601.22215

74,240

11-Jan-2013

10:42

IA-64


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

File name

X86_monitor.inf_31bf3856ad364e35_6.1.7601.18049_none_44ef1cccde9a41c0.manifest

File version

Not applicable

File size

2,087

Date (UTC)

11-Jan-2013

Time (UTC)

13:09

Platform

Not applicable

File name

X86_monitor.inf_31bf3856ad364e35_6.1.7601.22215_none_45952a19f7a32582.manifest

File version

Not applicable

File size

2,087

Date (UTC)

11-Jan-2013

Time (UTC)

13:03

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

Amd64_monitor.inf_31bf3856ad364e35_6.1.7601.18049_none_a10db85096f7b2f6.manifest

File version

Not applicable

File size

2,091

Date (UTC)

11-Jan-2013

Time (UTC)

15:41

Platform

Not applicable

File name

Amd64_monitor.inf_31bf3856ad364e35_6.1.7601.22215_none_a1b3c59db00096b8.manifest

File version

Not applicable

File size

2,091

Date (UTC)

11-Jan-2013

Time (UTC)

14:00

Platform

Not applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_monitor.inf_31bf3856ad364e35_6.1.7601.18049_none_44f0c0c2de984abc.manifest

File version

Not applicable

File size

2,089

Date (UTC)

11-Jan-2013

Time (UTC)

13:59

Platform

Not applicable

File name

Ia64_monitor.inf_31bf3856ad364e35_6.1.7601.22215_none_4596ce0ff7a12e7e.manifest

File version

Not applicable

File size

2,089

Date (UTC)

11-Jan-2013

Time (UTC)

13:55

Platform

Not applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×