Jay's BSOD 1000007e

[jayelder]

PC Microsoft 7 BSOD issue. Started 2 weeks ago. A week ago I reloaded Windows 7 and still have issues? Here is error report and Dump files. HELP!

[FONT=&quot]Problem signature:[/FONT]
[FONT=&quot] Problem Event Name: BlueScreen[/FONT]
[FONT=&quot] OS Version: 6.1.7601.2.1.0.768.3[/FONT]
[FONT=&quot] Locale ID: 1033[/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]Additional information about the problem:[/FONT]
[FONT=&quot] BCCode: 1000007e[/FONT]
[FONT=&quot] BCP1: FFFFFFFFC0000005[/FONT]
[FONT=&quot] BCP2: FFFFF8000307E700[/FONT]
[FONT=&quot] BCP3: FFFFF880033A8478[/FONT]
[FONT=&quot] BCP4: FFFFF880033A7CD0[/FONT]
[FONT=&quot] OS Version: 6_1_7601[/FONT]
[FONT=&quot] Service Pack: 1_0[/FONT]
[FONT=&quot] Product: 768_1[/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]Files that help describe the problem:[/FONT]
[FONT=&quot] C:\Windows\Minidump\080215-30357-01.dmp[/FONT]
[FONT=&quot] C:\Users\Jay\AppData\Local\Temp\WER-13432918-0.sysdata.xml[/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]Read our privacy statement online:[/FONT]
[FONT=&quot] [/FONT][FONT=&quot]http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409[/FONT][FONT=&quot][/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]If the online privacy statement is not available, please read our privacy statement offline:[/FONT]
[FONT=&quot] [/FONT][FONT=&quot]C:\Windows\system32\en-US\erofflps.txt[/FONT][FONT=&quot][/FONT]

 

[koolkat77]

Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\KoolKat77\Downloads\JAYSDESKTOP-Sat_08_08_2015_182953_37\080815-43742-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`0301b000 PsLoadedModuleList = 0xfffff800`03262730
Debug session time: Sat Aug  8 14:33:47.534 2015 (UTC + 6:00)
System Uptime: 0 days 10:58:43.001
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80003086700, fffff88009473478, fffff88009472cd0}

Probably caused by : volmgr.sys ( volmgr!VmpCleanupVolumeExtension+3d )

Followup: MachineOwner
---------

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80003086700, The address that the exception occurred at
Arg3: fffff88009473478, Exception Record Address
Arg4: fffff88009472cd0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!memcmp+90
fffff800`03086700 488b01          mov     rax,qword ptr [rcx]

EXCEPTION_RECORD:  fffff88009473478 -- (.exr 0xfffff88009473478)
ExceptionAddress: fffff80003086700 (nt!memcmp+0x0000000000000090)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000048
Attempt to read from address 0000000000000048

CONTEXT:  fffff88009472cd0 -- (.cxr 0xfffff88009472cd0;r)
rax=0000000000000000 rbx=fffff8a0001a11a8 rcx=0000000000000048
rdx=fffff8a0001a11a8 rsi=0000000000000000 rdi=fffff80003241aa0
rip=fffff80003086700 rsp=fffff880094736b8 rbp=0000000000000048
 r8=0000000000000010  r9=0000000000000002 r10=0000000000000000
r11=fffff8000320ee80 r12=fffff8a0151e1450 r13=0000000000000000
r14=fffff8a014badd40 r15=fffffa800a5c9650
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!memcmp+0x90:
fffff800`03086700 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000048=????????????????
Last set context:
rax=0000000000000000 rbx=fffff8a0001a11a8 rcx=0000000000000048
rdx=fffff8a0001a11a8 rsi=0000000000000000 rdi=fffff80003241aa0
rip=fffff80003086700 rsp=fffff880094736b8 rbp=0000000000000048
 r8=0000000000000010  r9=0000000000000002 r10=0000000000000000
r11=fffff8000320ee80 r12=fffff8a0151e1450 r13=0000000000000000
r14=fffff8a014badd40 r15=fffffa800a5c9650
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!memcmp+0x90:
fffff800`03086700 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000048=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000048

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032cc100
GetUlongFromAddress: unable to read from fffff800032cc1c0
 0000000000000048 Nonpaged pool

FOLLOWUP_IP: 
volmgr!VmpCleanupVolumeExtension+3d
fffff880`00e66f5d 488b8be0000000  mov     rcx,qword ptr [rbx+0E0h]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff800032fcc6f to fffff80003086700

STACK_TEXT:  
fffff880`094736b8 fffff800`032fcc6f : fffffa80`0a4dc3b0 fffffa80`0a5c9650 fffff800`0320a4a8 fffff780`00000008 : nt!memcmp+0x90
fffff880`094736c0 fffff800`0346082b : 00000000`00000048 00000000`00000002 00000000`00000048 fffff880`094737d8 : nt!WmipFindGEByGuid+0x3f
fffff880`094736f0 fffff800`03460b33 : 00000000`00000048 00000000`00000002 00000000`00000048 fffff8a0`151e1428 : nt!WmipDisableCollectionForRemovedGuid+0x2b
fffff880`09473760 fffff800`03460ba3 : 00000000`00000001 fffff8a0`151e1428 00000000`00000040 fffff8a0`21a121a0 : nt!WmipGenerateRegistrationNotification+0x83
fffff880`094737c0 fffff800`03460be2 : 00000000`00000000 00000000`00000001 fffffa80`06c35650 fffffa80`0a5c9650 : nt!WmipRemoveDataSourceByDS+0x13
fffff880`094737f0 fffff800`033cbcd2 : fffffa80`06c35650 fffffa80`00000001 fffffa80`06c35650 00000000`00000000 : nt!WmipRemoveDataSource+0x22
fffff880`09473820 fffff800`034bdbb4 : 00000000`00800045 00000000`00800045 fffffa80`06c35650 fffffa80`0a5c9700 : nt! ?? ::NNGAKEGL::`string'+0x18999
fffff880`09473860 fffff800`034c388e : fffffa80`0a5c97a0 00000000`00000000 00000000`00000000 fffffa80`0a5c9650 : nt!WmipDeregisterDevice+0x64
fffff880`09473890 fffff880`00e66f5d : fffffa80`0a5c97a0 fffffa80`0a5c97a0 fffffa80`0561f340 fffffa80`0a5c9601 : nt!IoWMIRegistrationControl+0xde
fffff880`094738c0 fffff880`00e66046 : fffffa80`00000000 fffffa80`00000000 fffffa80`0a5c9600 fffffa80`0a5c9600 : volmgr!VmpCleanupVolumeExtension+0x3d
fffff880`094738f0 fffff880`013c8273 : fffffa80`078342d0 fffffa80`0a9a3210 fffffa80`078342d0 fffffa80`0a5c9650 : volmgr! ?? ::NNGAKEGL::`string'+0x66d
fffff880`09473960 fffff880`013c7fc2 : fffffa80`07834180 fffffa80`07834180 fffffa80`0a9a3360 fffffa80`0561f0c0 : fvevol!FveFilterRemoveDevice+0xcf
fffff880`09473990 fffff880`01010c4e : fffffa80`0561f0c0 00000000`00000000 00000000`00000000 fffff800`030a1521 : fvevol!FveFilterPnp+0x122
fffff880`094739c0 fffff800`032f9721 : fffffa80`0a9a3210 fffff880`09473af8 00000000`c00000bb fffffa80`0561f0c0 : volsnap!VolSnapPnp+0x7e
fffff880`09473a40 fffff800`03476a21 : fffffa80`0a5c9650 00000000`00000000 fffffa80`0a590240 00000000`00000801 : nt!IopSynchronousCall+0xe1
fffff880`09473ab0 fffff800`0318f783 : fffff8a0`21f79300 fffff8a0`21f79300 00000000`00000018 00000000`00000000 : nt!IopRemoveDevice+0x101
fffff880`09473b70 fffff800`03476574 : fffffa80`0a590240 00000000`00000000 00000000`00000002 00000000`00000000 : nt!PnpRemoveLockedDeviceNode+0x1a3
fffff880`09473bc0 fffff800`03476680 : 00000000`00000000 fffffa80`0a5e8b00 fffff8a0`1516aad0 fffff880`09473ce8 : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`09473bf0 fffff800`03476779 : fffffa80`08f9e102 fffffa80`08f9e190 00000000`00000001 fffffa80`08f9e100 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`09473c60 fffff800`030994b5 : fffff800`03476700 fffff800`032392d8 fffffa80`0a5e8b00 fffffa80`0b75b788 : nt!PnpDelayedRemoveWorker+0x79
fffff880`09473cb0 fffff800`03329456 : 00000000`00000001 fffffa80`0a5e8b50 00000000`00000080 fffffa80`053ce720 : nt!ExpWorkerThread+0x111
fffff880`09473d40 fffff800`030812c6 : fffff800`0320ee80 fffffa80`0a5e8b50 fffff800`0321ccc0 fffff880`0a389401 : nt!PspSystemThreadStartup+0x5a
fffff880`09473d80 00000000`00000000 : fffff880`09474000 fffff880`0946e000 fffff880`09473510 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  volmgr!VmpCleanupVolumeExtension+3d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: volmgr

IMAGE_NAME:  volmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce792a0

IMAGE_VERSION:  6.1.7601.17514

STACK_COMMAND:  .cxr 0xfffff88009472cd0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_volmgr!VmpCleanupVolumeExtension+3d

BUCKET_ID:  X64_0x7E_volmgr!VmpCleanupVolumeExtension+3d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_volmgr!vmpcleanupvolumeextension+3d

FAILURE_ID_HASH:  {d93afb5d-af26-cc37-92ed-1445fdd068c9}

Followup: MachineOwner
---------

 Clean boot

• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

• How to Change, Add, or Remove Startup Programs in Windows 7

Run Disk Check on your Hard Drive for file system errors and bad sectors on it.

 Hard Drive Diagnostics

• Double click and open my computer.
• Right click on desired drive and hit properties.
• Click on tools tab and Check now.

Read complete instructions on the tutorial: http://www.sevenforums.com/tutorials/433-disk-check.html

Other Tests:

 

• Upload a screenshot of your hard disk using Crystal Disk Info.
• Make a hard drive test from the hard drive manufacturers website.
• Test your Hard Drive with SeaTools.