Code:
-
Loading Dump File [D:\Kingston\BSODDmpFiles\Brunan\041512-36956-01\041512-36956-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*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.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`0425e000 PsLoadedModuleList = 0xfffff800`044a2650
Debug session time: Sat Apr 14 17:27:12.151 2012 (UTC - 6:00)
System Uptime: 0 days 0:02:58.368
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff960001474e0, fffff880085f9fc0, 0}
Probably caused by : win32k.sys ( win32k!HMAssignmentUnlock+10 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960001474e0, Address of the instruction which caused the bugcheck
Arg3: fffff880085f9fc0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
win32k!HMAssignmentUnlock+10
fffff960`001474e0 834208ff add dword ptr [rdx+8],0FFFFFFFFh
CONTEXT: fffff880085f9fc0 -- (.cxr 0xfffff880085f9fc0)
rax=0000000000000001 rbx=fffff900c21b40b0 rcx=fffff900c21b40c8
rdx=fffef900c082e880 rsi=0000000000000001 rdi=0000000000000000
rip=fffff960001474e0 rsp=fffff880085fa9a0 rbp=fffff880085faca0
r8=0000000000000012 r9=0000000000000071 r10=0000000000002407
r11=fffff900c2097010 r12=0000000000000001 r13=fffff880085fab68
r14=0000000000000400 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
win32k!HMAssignmentUnlock+0x10:
fffff960`001474e0 834208ff add dword ptr [rdx+8],0FFFFFFFFh ds:002b:fffef900`c082e888=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: ipoint.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff960001474e0
STACK_TEXT:
fffff880`085fa9a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!HMAssignmentUnlock+0x10
FOLLOWUP_IP:
win32k!HMAssignmentUnlock+10
fffff960`001474e0 834208ff add dword ptr [rdx+8],0FFFFFFFFh
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!HMAssignmentUnlock+10
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f2b63bd
STACK_COMMAND: .cxr 0xfffff880085f9fc0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!HMAssignmentUnlock+10
BUCKET_ID: X64_0x3B_win32k!HMAssignmentUnlock+10
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\Brunan\041512-28095-01\041512-28095-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*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.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`0425e000 PsLoadedModuleList = 0xfffff800`044a2650
Debug session time: Sat Apr 14 17:22:52.140 2012 (UTC - 6:00)
System Uptime: 0 days 0:26:07.732
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff800042fa261, fffff880009a9968, fffff880009a91c0}
Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+181 )
Followup: MachineOwner
---------
2: 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: fffff800042fa261, The address that the exception occurred at
Arg3: fffff880009a9968, Exception Record Address
Arg4: fffff880009a91c0, 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!MiUnlinkFreeOrZeroedPage+181
fffff800`042fa261 48893cc2 mov qword ptr [rdx+rax*8],rdi
EXCEPTION_RECORD: fffff880009a9968 -- (.exr 0xfffff880009a9968)
ExceptionAddress: fffff800042fa261 (nt!MiUnlinkFreeOrZeroedPage+0x0000000000000181)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880009a91c0 -- (.cxr 0xfffff880009a91c0)
rax=00060000000cc858 rbx=fffffa8001d592c0 rcx=0000000000000008
rdx=fffffa8000000008 rsi=fffffa80069037a0 rdi=ffffffffffffffff
rip=fffff800042fa261 rsp=fffff880009a9ba0 rbp=0000000000000064
r8=0000000000000000 r9=0000000000000000 r10=fffffa80069037c0
r11=fffff880009a9be0 r12=0000000000000064 r13=0000000000000001
r14=00000000ffffffff r15=0000000000000001
iopl=0 nv up ei pl nz ac pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010212
nt!MiUnlinkFreeOrZeroedPage+0x181:
fffff800`042fa261 48893cc2 mov qword ptr [rdx+rax*8],rdi ds:002b:002ffa80`006642c8=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
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: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000450c100
ffffffffffffffff
FOLLOWUP_IP:
nt!MiUnlinkFreeOrZeroedPage+181
fffff800`042fa261 48893cc2 mov qword ptr [rdx+rax*8],rdi
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff800042a1d6e to fffff800042fa261
STACK_TEXT:
fffff880`009a9ba0 fffff800`042a1d6e : 00000000`000000ff 00000000`00000064 00000000`00000064 00000000`00000000 : nt!MiUnlinkFreeOrZeroedPage+0x181
fffff880`009a9c10 fffff800`04574fda : fffffa80`06a25b60 00000000`00000080 fffffa80`06a25040 fffff800`042cb9b9 : nt!MmZeroPageThread+0x541
fffff880`009a9d40 fffff800`042cb9c6 : fffff800`0444fe80 fffffa80`06a25b60 fffff800`0445dcc0 3a413b04`8a411474 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a98b0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiUnlinkFreeOrZeroedPage+181
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4f558b55
STACK_COMMAND: .cxr 0xfffff880009a91c0 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x7E_nt!MiUnlinkFreeOrZeroedPage+181
BUCKET_ID: X64_0x7E_nt!MiUnlinkFreeOrZeroedPage+181
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\Brunan\041412-28563-01\041412-28563-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*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.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`0425b000 PsLoadedModuleList = 0xfffff800`0449f650
Debug session time: Sat Apr 14 16:55:17.713 2012 (UTC - 6:00)
System Uptime: 0 days 1:06:21.915
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1, {74d02e09, 0, ffff0000, fffff880061acca0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them. A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 0000000074d02e09, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 00000000ffff0000, Thread->KernelApcDisable
Arg4: fffff880061acca0, Previous KernelApcDisable
Debugging Details:
------------------
FAULTING_IP:
+3837356334626561
00000000`74d02e09 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1
PROCESS_NAME: AvastSvc.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800042d7229 to fffff800042d7c80
STACK_TEXT:
fffff880`061aca68 fffff800`042d7229 : 00000000`00000001 00000000`74d02e09 00000000`00000000 00000000`ffff0000 : nt!KeBugCheckEx
fffff880`061aca70 fffff800`042d7160 : 00000000`00001d78 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`061acbb0 00000000`74d02e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`07b8ec48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74d02e09
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemServiceExit+245
fffff800`042d7160 4883ec50 sub rsp,50h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiSystemServiceExit+245
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4f558b55
FAILURE_BUCKET_ID: X64_0x1_SysCallNum_3_nt!KiSystemServiceExit+245
BUCKET_ID: X64_0x1_SysCallNum_3_nt!KiSystemServiceExit+245
Followup: MachineOwner
---------
- Appears to be related to your mouse... Other possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
Thanks to JMH for helping with my understanding of this crash.
- Same possible causes as 1. but points more toward memory problems...
- Appears to be related to avast! which could mean avast! is corrupt, your network adapter drivers are corrupt, or your audio drivers are corrupt. Could also mean any of these are old/out of date. Other possible cases are drivers... hard disk file system corruption...
First thing's first: your hard disk checks did not come back clean and should be run again and the logs posted again. You do not have bad sectors, so no need to run with both boxes this time. You can just run with Automatically fix file system errors checked, which is a lot faster.
Check your memory:- Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
If you swap any memory components, follow these steps for ESD safety:
- Shut down and turn off your computer.
- Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
- Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
- Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
Quote