Welcome Guest ( Log In | Register )

Outline · [ Standard ] · Linear+

 [FAQ] PC auto restart/Blue Screen (BSOD), All questions go here please.

views
     
f4st
post Jul 6 2007, 01:41 AM

New Member
*
Newbie
2 posts

Joined: Apr 2005


Hi guys,

I'm having some bsod problems here as well,mostly while plying wow n once awhile out in the windows,btw i already created my mini dump file by using WInDBG to analyse it. This is my results.Can anybdy help me out here?

QUOTE

Microsoft ® Windows Debugger  Version 6.7.0005.1
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\7\Desktop\Mini070507-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Thu Jul  5 16:17:21.625 2007 (GMT+8)
System Uptime: 0 days 2:35:52.411
Loading Kernel Symbols
.............................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8051b80c, f7c82a84, f7c82780}

Probably caused by : hardware ( kmixer!PerfUnregisterProvider+1f )

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: c0000005, The exception code that was not handled
Arg2: 8051b80c, The address that the exception occurred at
Arg3: f7c82a84, Exception Record Address
Arg4: f7c82780, 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!WmipDoFindRegEntryByDevice+11
8051b80c 8b5008          mov    edx,dword ptr [eax+8]

EXCEPTION_RECORD:  f7c82a84 -- (.exr 0xfffffffff7c82a84)
ExceptionAddress: 8051b80c (nt!WmipDoFindRegEntryByDevice+0x00000011)
  ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
  Parameter[0]: 00000000
  Parameter[1]: 0000000a
Attempt to read from address 0000000a

CONTEXT:  f7c82780 -- (.cxr 0xfffffffff7c82780)
eax=00000002 ebx=00000000 ecx=8055913c edx=86607a70 esi=8602df10 edi=00000000
eip=8051b80c esp=f7c82b4c ebp=f7c82b4c iopl=0        nv up ei pl nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000            efl=00010217
nt!WmipDoFindRegEntryByDevice+0x11:
8051b80c 8b5008          mov    edx,dword ptr [eax+8] ds:0023:0000000a=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  3

PROCESS_NAME:  System

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

READ_ADDRESS:  0000000a

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

MISALIGNED_IP:
nt!WmipDoFindRegEntryByDevice+11
8051b80c 8b5008          mov    edx,dword ptr [eax+8]

LOCK_ADDRESS:  805624e0 -- (!locks 805624e0)

Resource @ nt!PiEngineLock (0x805624e0)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address  : 0x805624e0
Thread Count  : 0
Thread address: 0x00000000
Thread wait  : 0x0

LAST_CONTROL_TRANSFER:  from 805e7d2b to 8051b80c

STACK_TEXT: 
f7c82b4c 805e7d2b 8602df10 00000080 8602df10 nt!WmipDoFindRegEntryByDevice+0x11
f7c82b60 805aae1a 8602df10 00000000 8602df10 nt!WmipFindRegEntryByDevice+0x1a
f7c82b74 805aadc7 8602df10 85e9b4b0 8602df10 nt!WmipDeregisterDevice+0x17
f7c82b90 b95d418f 8602df10 00000002 f7c82bb4 nt!IoWMIRegistrationControl+0xa9
f7c82ba0 b95bd4c8 8602df10 85e9b568 85942370 kmixer!PerfUnregisterProvider+0x1f
f7c82bb4 804e19ee 8602df10 85e9b4b0 f7c82c40 kmixer!DispatchPnp+0x58
f7c82bc4 8059df4d 8598ed68 8598ed68 00000017 nt!IopfCallDriver+0x31
f7c82bf0 805ab09d 8602df10 f7c82c1c 00000000 nt!IopSynchronousCall+0xb7
f7c82c44 805ab115 8598ed68 00000017 e2abb848 nt!IopRemoveDevice+0x93
f7c82c60 805ab347 00000308 e2abb848 00000000 nt!IopSurpriseRemoveLockedDeviceNode+0x90
f7c82c74 805ab372 8598d368 00000003 e2abb848 nt!IopDeleteLockedDeviceNode+0x50
f7c82ca8 805ab5fc 8598ed68 02abb848 00000003 nt!IopDeleteLockedDeviceNodes+0x3f
f7c82d3c 805ab6d0 f7c82d78 80703974 e53d3af0 nt!PiProcessQueryRemoveAndEject+0x4d2
f7c82d58 8059f480 f7c82d78 85f6e7e0 8056b4fc nt!PiProcessTargetDeviceEvent+0x2a
f7c82d7c 804e29d6 85f6e7e0 00000000 867c2640 nt!PiWalkDeviceList+0x122
f7c82dac 80576b24 85f6e7e0 00000000 00000000 nt!ExpWorkerThread+0xef
f7c82ddc 804eed86 804e2912 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
kmixer!PerfUnregisterProvider+1f
b95d418f 5d              pop    ebp

SYMBOL_STACK_INDEX:  4

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

SYMBOL_NAME:  kmixer!PerfUnregisterProvider+1f

STACK_COMMAND:  .cxr 0xfffffffff7c82780 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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

 

Change to:
| Lo-Fi Version
0.0167sec    0.33    7 queries    GZIP Disabled
Time is now: 1st December 2025 - 12:00 PM