人気ブログランキング | 話題のタグを見る

Blue Screen Stop 0x0000008E -Unable to backup files or perform" Verifier.exe " [Solved]

Blue Screen Stop 0x0000008E -Unable to backup files or perform" Verifier.exe "

original title: BSOD Stop 0x0000008E ( 0xc000005, 0x82d6b04d,0x9053987c, 0x00000000) I've been unable to backup files or perform" Verifier.exe " without a blue screen shutting down the computer.
__
Dump File         : 021311-20982-01.dmp
Crash Time        : 2/13/2011 4:22:33 PM
Bug Check String  : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x1000008e
Parameter 1       : 0xc0000005
Parameter 2       : 0x82d6b04d
Parameter 3       : 0x9d53987c
Parameter 4       : 0x00000000
Caused By Driver  : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+12004d
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor         : 32-bit
Computer Name     :
Full Path         : C:\Windows\Minidump\021311-20982-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 158,232
==================================================

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation.
All rights reserved.

Loading Dump File [C:\Windows\MEMORY - Copy.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x82c1a000 PsLoadedModuleList = 0x82d62810
Debug session time: Sun Feb 13 14:29:39.442 2011 (UTC - 6:00)
System Uptime: 0 days 1:51:35.011
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C5, 54dcbd4, 2, 1, 82d3a943
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+2e3 )
Followup: Pool_corruption
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 054dcbd4, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 82d3a943, address which referenced memory
Debugging Details:
------------------

BUGCHECK_STR:  0xC5_2
CURRENT_IRQL:  2
FAULTING_IP:
nt!ExDeferredFreePool+2e3
82d3a943 894604          mov     dword ptr [esi+4],eax
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
TRAP_FRAME:  8cd6fb44 -- (.trap 0xffffffff8cd6fb44)
ErrCode = 00000002
eax=85a0d0b8 ebx=000001ff ecx=000001ff edx=82d4fa28 esi=054dcbd0 edi=82d4f8c0
eip=82d3a943 esp=8cd6fbb8 ebp=8cd6fbf0 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!ExDeferredFreePool+0x2e3:
82d3a943 894604          mov     dword ptr [esi+4],eax ds:0023:054dcbd4=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from 82d3a943 to 82c6081b
STACK_TEXT: 
8cd6fb44 82d3a943 badb0d00 82d4fa28 0000ab9d nt!KiTrap0E+0x2cf
8cd6fbf0 82d398aa 82d4f8c0 00000000 8583a6d0 nt!ExDeferredFreePool+0x2e3
8cd6fc58 82c55101 8583a6d0 00000000 00000000 nt!ExFreePoolWithTag+0x8a4
8cd6fc78 82cb2fa3 00000001 00000000 8601a128 nt!CcDeleteSharedCacheMap+0x19f
8cd6fca8 82cbafd6 8cd6fcc4 a308fa2f 853ef448 nt!CcWriteBehind+0x715
8cd6fd00 82c8803b 853ef448 00000000 85447d48 nt!CcWorkerThread+0x164
8cd6fd50 82e289df 00000000 a308fabf 00000000 nt!ExpWorkerThread+0x10d
8cd6fd90 82cda1d9 82c87f2e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

STACK_COMMAND:  kb
FOLLOWUP_IP:
nt!ExDeferredFreePool+2e3
82d3a943 894604          mov     dword ptr [esi+4],eax
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!ExDeferredFreePool+2e3
FOLLOWUP_NAME:  Pool_corruption
IMAGE_NAME:  Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID:  0xC5_2_nt!ExDeferredFreePool+2e3
BUCKET_ID:  0xC5_2_nt!ExDeferredFreePool+2e3
Followup: Pool_corruption
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 054dcbd4, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 82d3a943, address which referenced memory
Debugging Details:
------------------
 OS Name Microsoft Windows 7 Professional
Version 6.1.7600 Build 7600
Other OS Description  Not Available
OS Manufacturer Microsoft Corporation
System Name System Manufacturer Dell Inc.
System Model Dell XPS720
System Type X86-based PC
Processor Intel(R) Core(TM)2 Extreme CPU Q6850  @ 3.00GHz, 3000 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date Dell Inc.
A06, 4/1/2008
SMBIOS Version 2.3
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.1.7600.16385"
Time Zone Central Standard Time
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 2.75 GB
Available Physical Memory 1.83 GB
Total Virtual Memory 10.7 GB
Available Virtual Memory 9.70 GB
Page File Space 8.00 GB
Page File C:\pagefile.sys

Solutions to the Problem Blue Screen Stop 0x0000008E -Unable to backup files or perform" Verifier.exe "

Download SmartPCFixer to Fix It (Free)

Hi,

Most likely causes are MEMORY and DRIVERS.

-----------------------------------------------------
Check this thread for information using BlueScreenView, MyEventViewer and other methods
to troubleshoot BlueScreens - top 3 replies (+1 other).
http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/c675b7b8-795f-474d-a1c4-6b77b3fcd990
We can analyze the minidumps if you make them available from the SkyDrive or other file
sharing sites.

Zip or upload the contents of C:\Windows\minidump
Use SkyDrive to upload collected files and post screen shot/picture.
http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
===============================================================
BCCode: 8E  0x0000008E is same as 0x1000008E

Two primary causes of these blue screen are video drivers and BIOS - Check with System Maker's
Site for Display Adapter (Video) and BIOS and then Device Maker's site for latest Video.
It can be
other drivers so check while there.
Turn OFF auto-driver installation as those are older and if
Windows Updates suggests a driver just HIDE it.
Antivirus is another possibility.
See Generic Driver Update Methods and check running Driver Verifier in the next
message.
BCCode: 8E  0x0000008E is same as 0x1000008E

Cause
The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check is a very common bug check.
To interpret it, you must identify which exception was generated.
Common exception codes include the following:

0x80000002: STATUS_DATATYPE_MISALIGNMENT indicates that an unaligned data reference was encountered.
0x80000003: STATUS_BREAKPOINT indicates that a breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.
0xC0000005: STATUS_ACCESS_VIOLATION indicates that a memory access violation occurred.
Resolving the Problem
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques:
Make sure you have enough disk space.
If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.Try changing video adapters.
Check with your hardware vendor for any BIOS updates.
Disable BIOS memory options such as caching or shadowing.

If you plan to debug this problem, you might find it difficult to obtain a stack trace.
Parameter 2 (the exception address) should identify the driver or function that caused this problem.
If you do not know the specific cause of the exception, consider the following items:
Hardware incompatibility.
Make sure that any new hardware installed is listed in the Microsoft Windows Marketplace Tested Products List.Faulty device driver or system service.
A faulty device driver or system service might be responsible for this error.
Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.
If the bug check message lists a driver by name , disable or remove that driver.
Also, disable or remove any drivers or services that were recently added.
If the error occurs during the startup sequence and the system partition is formatted with NTFS file
system, you might be able to use Safe Mode to rename or delete the faulty driver.
If the driver is used as part of the system startup process in Safe Mode, you have to start the computer by using the Recovery Console to access the file.
If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program.
If such software is installed, you can remove the service by starting the system by using the Recovery Console and then deleting
the offending system service file.
Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x1E.
You can disable memory caching of the BIOS to try to resolve the error.
You should also run
hardware diagnostics, especially the memory scanner, that the system manufacturer supplies.
For more information about these procedures, see the owner's manual for your computer.
The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished.
A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities.
For problems during Windows
installation that are associated with lack of disk space, reduce the number of files on the target hard disk drive.
Check for and delete any temporary files that you do not have to have, Internet cache files, application backup files, and.chkfiles
that contain saved file fragments from disk scans.
You can also use another hard disk drive with more free space for the installation.
You can resolve BIOS problems by upgrading the system BIOS version
BCCode: 8E  0x0000008E is same as 0x1000008E  <-- read this link
http://www.faultwire.com/solutions-fatal_error/KERNEL-MODE-EXCEPTION-NOT-HANDLED-0x0000008E-*1151.html?order=date

=============================================
BCCode: C5    0x000000C5

This error is most often a driver, think Video and others, and BIOS.
Antivirus/antispyware/security
programs are also suspects.
BCCode: C5    0x000000C5
Bug Check 0xC5: DRIVER_CORRUPTED_EXPOOL
The DRIVER_CORRUPTED_EXPOOL bug check has a value of 0x000000C5.
This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
Important Information If You Have Received a STOP Code
If you have received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss.
A hardware device, its driver, or related software might have caused this error.
If your copy of Windows came with your computer,
call the manufacturer of your computer.
If you purchased Windows separately from your computer, Microsoft provides support.
To find contact information for Microsoft or your computer manufacturerContact
Support.
If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft articleResolving STOP (Blue Screen) Errors in Windows.
The following actions might prevent an error like this from happening again:
Download and install updates and device drivers for your computer from Windows Update.Scan your computer for computer viruses.
Check your hard disk for errors.

DRIVER_CORRUPTED_EXPOOL Parameters
The following parameters are displayed on the blue screen.

Parameter
Description

1

Memory referenced


2

IRQL at time of reference


3

0: Read
1: Write


4

Address that referenced memory


Cause
The kernel attempted to access pageable memory (or perhaps completely invalid memory) when the IRQL was too high.
The ultimate cause of this problem is almost certainly a driver that has corrupted the system pool.
In most cases, this bug check results if a driver corrupts a small allocation (less than PAGE_SIZE).
Larger allocations result inbug check 0xD0
(DRIVER_CORRUPTED_MMPOOL).
Resolution
If you have recently installed any new software, check to see if it is properly installed.
Check for updated drivers on the manufacturer's website.
To debug this error, use the special pool option of Driver Verifier.
If this fails to reveal the driver that caused the error, use the Global Flags utility to enable the special pool by pool tag.
BCCode: C5    0x000000C5  <-- read this link
http://www.faultwire.com/solutions-fatal_error/A-device-driver-has-pool-0x000000C5-*1198.html

==============================================================

Driver Verifier can help find some BSOD issues :
Using Driver Verifier to identify issues with Windows drivers for advanced users
http://support.microsoft.com/kb/244617
How To Troubleshoot Driver Problems in Windows Vista or 7.
http://www.winvistaclub.com/t79.html
Using Driver Verifier
http://msdn.microsoft.com/en-us/library/ff554113(v=VS.85).aspx
How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issueshttp://www.youtube.com/watch?v=_VwIDD9xngM

Driver Verifier
http://www.techsupportforum.com/2110308-post3.html

Using Driver Verifier
http://www.faultwire.com/solutions/using_driver_verifier.php
How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issueshttp://www.youtube.com/watch?v=_VwIDD9xngM
You can disable Driver Verifier
http://support.microsoft.com/kb/244617
Start - type in Search box -> verifier /reset      hit enter to disable
Hope this helps

Rob Brown -
Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.

Run CHKDSK
  • Go to the Start button.
  • In the Search box, type "cmd" (without quotes) and press Enter.
  • At the command prompt, type "chkdsk /r /f" (without quotes) and press Enter.
  • Restart your computer.

Another Safe way to Repair the Problem: Blue Screen Stop 0x0000008E -Unable to backup files or perform" Verifier.exe ":

How to Fix Blue Screen Stop 0x0000008E -Unable to backup files or perform" Verifier.exe " with SmartPCFixer?

1. Download SmartPCFixer. Install it on your computer.

2. After the scan is done, you can see the errors and problems which need to be fixed.

3. The Repair part is finished, the speed of your computer will be much higher than before and the errors have been removed. You can also use other functions in SmartPCFixer. Like dll downloading, junk file cleaning and print spooler error repair.


Related: Black Menu Bars And Other Bars On Internet Explorer 8,Battery Life Monitor Seems To Vary Quite A Bit,Beeping Sound And Unresponsive Mouse,Best Way To Install Volume Control Panel To Bring Volume Icon Back To Taskbar,Bitlocker For Windows 7 Home Premium
Read More: Troubleshooter of Error: Battery Consumption Issue,Fast Solution to Problem: BitLocker Locks a drive when never used on that computer?,How to Fix Error - Barnes and Noble Nook Study connection to internet?!?!?,How to Fix Problem - Bios Crash windows 8?,Before I can open Outlook Express I get a dialog box, \"Run As\". How can I delete this and just use my shortcut?,bit lock drtive corrupt,Black Screen as Windows 7 boots.,Bizarre routing problems with Windows 7 64-bit affecting IE8 32bit and Outlook,Battery Life for Dell InspironT4300,Be Graphic Add-in
by externalcddrive | 2016-08-10 17:34