Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. You may receive a "Stop" error message on a computer that is running Windows Server 2003, Windows 2000, Windows Small Business Server 2003, Small Business Server 2000, or Windows XP

You may receive a "Stop" error message on a computer that is running Windows Server 2003, Windows 2000, Windows Small Business Server 2003, Small Business Server 2000, or Windows XP

Symptoms

You may receive an error message on your computer that is running Microsoft Windows Server 2003, Microsoft Windows 2000 Server, Microsoft Windows Small Business Server 2003, Microsoft Small Business Server 2000, or Microsoft Windows XP. When this issue occurs, you may experience one of the following symptoms:
  • Your computer may stop responding, and you may receive either of the following error messages:
    STOP 0x0000007b (p1, 0xc0000102, p3, p4) ERROR_UNHANDLED_ERROR
    Note The second parameter value (0xc0000102) may be 0xc000009c. The p1, p3, and p4 values may vary.

    STOP 0x0000000a (0xbb693f7c, 0x00000002, 0x00000001, 0x8006543a) IRQL_NOT_LESS_OR_EQUAL STOP 0x0000000a (0x00000016, 0x0000001c, 0x00000000, 0x80432ed0) IRQL_NOT_LESS_OR_EQUAL
  • Your computer may stop responding, and you may receive the following error message when Windows tries to mount a volume that is in a cluster on your Windows 2000 Advanced Server-based computer:

    STOP 0x0000001e (0xc0000005, 0xbf89e3f1, 0x00000000 0x0000002e)
  • Your computer may stop responding, and you may receive the following error message when you try to run the Windows Small Business Server 2003 Setup program to upgrade your Small Business Server 2000 computer:

    STOP 0x000000ED (0x89AE1B28, 0xC000009C, 0x00000000, 0x00000000) UNMOUNTABLE_BOOT_VOLUME

↑ Back to the top

Cause

This issue occurs with some versions of the Pqv2i.sys driver. The Pqv2i.sys driver is included with the V2i Protector 2.0 program from Symantec.

↑ Back to the top

Resolution

To resolve this issue, contact Symantec for an update to the V2i Protector 2.0 program. To obtain the update, visit the following Symantec Web site:
http://service1.symantec.com/SUPPORT/powerquest.nsf/35f1485389b899f088256e97004a3bb4/626010eae181acc988256e75007cd1f9?OpenDocument&prod=V2i%20Protector&ver=Server%20Edition%202.0&pcode=v2ipro&src=ent&miniver=v2ipro_server_2&tpre=&prev=&dtype=corp
Note The Symantec document ID number for this issue is 2004076514991962.Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

↑ Back to the top

Workaround

To work around this issue, use the Recovery Console to disable the V2i Protector 2.0 program, or rename the Pqv2i.sys driver.

Note The Pqv2i.sys driver is located in the %windir%\System32\Drivers folder.For additional information about how to use the Recovery Console to disable a service that is preventing Windows from starting, click the following article numbers to view the articles in the Microsoft Knowledge Base:

310602 How to disable a service or device that prevents Windows from starting

244905 How to disable a service or device that prevents Windows from booting

326215 How to use the Recovery Console on a Windows Server 2003-based computer that does not start

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

↑ Back to the top

Keywords: kbentirenet, kbtshoot, kbprb, kb

↑ Back to the top

Article Info
Article ID : 892000
Revision : 5
Created on : 4/21/2018
Published on : 4/21/2018
Exists online : False
Views : 130