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. Error message during Windows Vista startup if the Nero InCD program is installed and if the "Special pool" feature is enabled in the Driver Verifier utility: "Stop 00000050"

Error message during Windows Vista startup if the Nero InCD program is installed and if the "Special pool" feature is enabled in the Driver Verifier utility: "Stop 00000050"

View products that this article applies to.

Support for Windows Vista without any service packs installed ended on April 13, 2010. To continue receiving security updates for Windows, make sure you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft web page: Support is ending for some versions of Windows

↑ Back to the top

Symptoms

Consider the following scenario:
  • You install the Nero InCD program on a Windows Vista-based computer.
  • You enable the "Special pool" feature in the Driver Verifier utility (Verifier.exe) for a device on the computer.
  • There is no media in the CD drive or in the DVD drive.
In this scenario, Windows Vista stops unexpectedly during startup, and then you receive an error message that resembles the following:
Stop 00000050 (83cb3054, 00000000, 8143cc97, 00000001)

↑ Back to the top

Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack

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 this specific problem. 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 Web site:
http://support.microsoft.com/contactus/?ws=support
Note 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

No prerequisites are required.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information


This hotfix does not replace any other previously released hotfixes.

Registry information


To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Vista, x86-based versions
File nameFile versionFile sizeDateTimePlatform
X86_fbe1e3bb54a3989096255682701ca47c_31bf3856ad364e35_6.0.6000.20605_none_4b39d3afecd0188a.manifestNot Applicable69724-May-200716:53Not Applicable
X86_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6000.20605_none_6ad8bf51d015a2cd.manifestNot Applicable18,77824-May-200716:55Not Applicable
Ntkrnlpa.exe6.0.6000.206053,504,31224-May-200702:24Not Applicable
Ntoskrnl.exe6.0.6000.206053,470,52024-May-200702:24Not Applicable
Windows Vista, 64-bit versions
File nameFile versionFile sizeDateTimePlatform
Amd64_9cd84196dcd4dc76036690b897e8da3d_31bf3856ad364e35_6.0.6000.20605_none_4397bb06734fe680.manifestNot Applicable70124-May-200716:53Not Applicable
Amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6000.20605_none_c6f75ad588731403.manifestNot Applicable17,33024-May-200716:58Not Applicable
Ntoskrnl.exe6.0.6000.206054,431,03224-May-200703:51x64

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Vista Service Pack 1.

↑ Back to the top

More Information

For more information, 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

Call stack information

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: 83cb3054, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8143cc97, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

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


READ_ADDRESS: 83cb3054 Nonpaged pool

FAULTING_IP:
nt!IopfCompleteRequest+97 
8143cc97 8b402c mov eax,dword ptr [eax+2Ch]

MM_INTERNAL_CODE: 1

DEFAULT_BUCKET_ID: VISTA_RC

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: 867fbc2c -- (.trap 0xffffffff867fbc2c)
ErrCode = 00000000
eax=83cb3028 ebx=00000000 ecx=816ef923 edx=9a7d2fb8 esi=9a7d2e70 edi=9a7d2f97
eip=8143cc97 esp=867fbca0 ebp=867fbcc0 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!IopfCompleteRequest+0x97:
8143cc97 8b402c mov eax,dword ptr [eax+2Ch] ds:0023:83cb3054=00008600
Resetting default scope

LAST_CONTROL_TRANSFER: from 814c583b to 8143d7f0

STACK_TEXT:
867fb774 814c583b 00000003 867f0c84 00000000 nt!RtlpBreakWithStatusInstruction 
867fb7c4 814c62a8 00000003 0000001f 8344b020 nt!KiBugCheckDebugBreak+0x1c 
867fbb70 8145f8cb 00000050 83cb3054 00000000 nt!KeBugCheck2+0x5f4 
867fbc14 814517a0 00000000 83cb3054 00000000 nt!MmAccessFault+0x151 
867fbc14 8143cc97 00000000 83cb3054 00000000 nt!_KiTrap0E+0xdc 
867fbcc0 816e5b53 9a7d2f4c 89b5da00 00000000 nt!IopfCompleteRequest+0x97 
867fbd30 816ef9c7 8344b020 815145bc 89b5da1c nt!IovCompleteRequest+0x11c 
867fbd44 81477b32 89b5da00 00000000 8344b020 nt!IovpInternalCompleteAfterWait+0x64 
867fbd7c 815cf937 89b5da00 867f0680 00000000 nt!ExpWorkerThread+0xfd 
867fbdc0 814b0a7e 81477a35 00000001 00000000 nt!PspSystemThreadStartup+0x9d 
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

↑ Back to the top

Keywords: kb, kbautohotfix, kbvistasp1fix, kbexpertisebeginner, kbfix, kbhotfixserver, kbqfe, kbpubtypekc

↑ Back to the top

Article Info
Article ID : 929637
Revision : 1
Created on : 1/7/2017
Published on : 9/23/2011
Exists online : False
Views : 225