System Service Exeption 0x3B

Brunan · Apr 12, 2012

Hi all,
I keep getting these random BSOD for the past monthor so now, They tend to vary in error code's.
Attached is my Minidumps and everything needed as said by the BSOD Posting Instructions thread.
Can someone please help me I am really worried about the health of my PC.
It is a custom build, I build it in November 2011, But about 2 weeks ago I wiped my entire HD and did a fresh install on Windows 7 in an attempt to stop these BSOD's.
Thanks, and please help me.

Brunan · Apr 12, 2012

Bump, Please help me guys.

writhziden · Apr 13, 2012

http://www.sevenforums.com/general-discussion/8-forum-rules-info-please-read.html

Security Software (to check that it is installed and working properly; no steps need to be taken at this time):

Code:

avastsvc.exe	c:\program files\avast software\avast\avastsvc.exe	1272	8	200	1380	12/04/2012 14:42	7.0.1426.0	43.72 KB (44,768 bytes)	27/03/2012 22:29
avastui.exe	c:\program files\avast software\avast\avastui.exe	3236	8	200	1380	12/04/2012 14:42	7.0.1426.0	4.05 MB (4,241,512 bytes)	27/03/2012 22:29

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\Brunan\Windows_NT6_BSOD_jcgriff2\041112-30794-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.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0404f000 PsLoadedModuleList = 0xfffff800`04293650
Debug session time: Wed Apr 11 09:36:49.606 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:32.198
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {774a143a, 0, fffe, fffff88004ff8ca0}

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: 00000000774a143a, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 000000000000fffe, Thread->KernelApcDisable
Arg4: fffff88004ff8ca0, Previous KernelApcDisable

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


FAULTING_IP: 
+3837356334626561
00000000`774a143a ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x1

PROCESS_NAME:  services.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800040cb2e9 to fffff800040cbd40

STACK_TEXT:  
fffff880`04ff8ad8 fffff800`040cb2e9 : 00000000`00000001 00000000`774a143a 00000000`00000000 00000000`0000fffe : nt!KeBugCheckEx
fffff880`04ff8ae0 fffff800`040cb220 : fffffa80`09a4a060 fffff880`04ff8ca0 00000000`00ccfe78 00030019`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`04ff8c20 00000000`774a143a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`00ccf858 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774a143a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceExit+245
fffff800`040cb220 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:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0x1_VRF_SysCallNum_f_nt!KiSystemServiceExit+245

BUCKET_ID:  X64_0x1_VRF_SysCallNum_f_nt!KiSystemServiceExit+245

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

Probably caused by either a driver or hard disk file system errors.

Out of date driver:

Code:

mv61xx	fffff880`00c00000	fffff880`00c46000	Thu Mar 19 21:48:21 2009 (49c31205)	000320f6		mv61xx.sys

ASUS - Motherboards- ASUS M4A79XTD EVO -> Download -> OS: Windows 7 64bit -> SATA -> Marvell 61xx ESATA Controller Driver 1.2.0.69 for Windows 32/64bit XP & 32/64bit Vista& 32/64bit 7

If you are overclocking any hardware, please stop.
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.

Brunan · Apr 14, 2012

Here's the logs from the Check Disc and I updated the SATA driver. No BSOD's so far so let's hope for the best. Thanks for the reply aswell writhziden.

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 13/04/2012 20:35:13
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Brian-PC
Description:

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
135680 file records processed.

File verification completed.
206 large file records processed.

0 bad file records processed.

0 EA records processed.

76 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
178730 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
135680 file SDs/SIDs processed.

Cleaning up 397 unused index entries from index $SII of file 0x9.
Cleaning up 397 unused index entries from index $SDH of file 0x9.
Cleaning up 397 unused security descriptors.
Security descriptor verification completed.
21526 data files processed.

CHKDSK is verifying Usn Journal...
33625680 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
135664 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
129730787 free clusters processed.

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

732469247 KB total disk space.
213224660 KB in 109831 files.
63752 KB in 21527 indexes.
0 KB in bad sectors.
257683 KB in use by the system.
65536 KB occupied by the log file.
518923152 KB available on disk.

4096 bytes in each allocation unit.
183117311 total allocation units on disk.
129730788 allocation units available on disk.

Internal Info:
00 12 02 00 2a 01 02 00 e2 c6 03 00 00 00 00 00 ....*...........
46 02 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 F...L...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-04-13T19:35:13.000000000Z" />
<EventRecordID>2913</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Brian-PC</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
135680 file records processed.

File verification completed.
206 large file records processed.

0 bad file records processed.

0 EA records processed.

76 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
178730 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
135680 file SDs/SIDs processed.

Cleaning up 397 unused index entries from index $SII of file 0x9.
Cleaning up 397 unused index entries from index $SDH of file 0x9.
Cleaning up 397 unused security descriptors.
Security descriptor verification completed.
21526 data files processed.

CHKDSK is verifying Usn Journal...
33625680 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
135664 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
129730787 free clusters processed.

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

732469247 KB total disk space.
213224660 KB in 109831 files.
63752 KB in 21527 indexes.
0 KB in bad sectors.
257683 KB in use by the system.
65536 KB occupied by the log file.
518923152 KB available on disk.

4096 bytes in each allocation unit.
183117311 total allocation units on disk.
129730788 allocation units available on disk.

Internal Info:
00 12 02 00 2a 01 02 00 e2 c6 03 00 00 00 00 00 ....*...........
46 02 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 F...L...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>

Brunan · Apr 14, 2012

I'm after getting the BSOD again, this time with the error code APC_INDEX_MISMATCH. Attached is the dump file.

Brunan · Apr 14, 2012

Okay this is getting beyond a joke, I am after getting 3 BSOD's in the past hour, Can someone please help me, I am in desperate need. Attached are the 2 dump files from the last two BSOD's.

writhziden · Apr 14, 2012

Code:

[list=1][*]
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
---------


[/list]

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:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. 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.

Brunan · Apr 15, 2012

Here's the logs from the Check Disk you asked for. Also, like you said about my Mouse, I installed Driver's from the mouse as recommended when I bought it. This was Intellipoint 8.2. Could this driver be corrupt, or should I leave it alone for the time being? And thanks again for all your help. I am very grateful.

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 15/04/2012 14:35:12
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Brian-PC
Description:

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
135680 file records processed.

File verification completed.
214 large file records processed.

0 bad file records processed.

0 EA records processed.

76 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
178664 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
135680 file SDs/SIDs processed.

Cleaning up 53 unused index entries from index $SII of file 0x9.
Cleaning up 53 unused index entries from index $SDH of file 0x9.
Cleaning up 53 unused security descriptors.
Security descriptor verification completed.
21493 data files processed.

CHKDSK is verifying Usn Journal...
36989728 USN bytes processed.

Usn Journal verification completed.
Windows has checked the file system and found no problems.

732469247 KB total disk space.
207171448 KB in 109901 files.
63808 KB in 21494 indexes.
0 KB in bad sectors.
261159 KB in use by the system.
65536 KB occupied by the log file.
524972832 KB available on disk.

4096 bytes in each allocation unit.
183117311 total allocation units on disk.
131243208 allocation units available on disk.

Internal Info:
00 12 02 00 4f 01 02 00 e8 c7 03 00 00 00 00 00 ....O...........
40 02 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 @...L...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-04-15T13:35:12.000000000Z" />
<EventRecordID>3237</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Brian-PC</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
135680 file records processed.

File verification completed.
214 large file records processed.

0 bad file records processed.

0 EA records processed.

76 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
178664 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
135680 file SDs/SIDs processed.

Cleaning up 53 unused index entries from index $SII of file 0x9.
Cleaning up 53 unused index entries from index $SDH of file 0x9.
Cleaning up 53 unused security descriptors.
Security descriptor verification completed.
21493 data files processed.

CHKDSK is verifying Usn Journal...
36989728 USN bytes processed.

Usn Journal verification completed.
Windows has checked the file system and found no problems.

732469247 KB total disk space.
207171448 KB in 109901 files.
63808 KB in 21494 indexes.
0 KB in bad sectors.
261159 KB in use by the system.
65536 KB occupied by the log file.
524972832 KB available on disk.

4096 bytes in each allocation unit.
183117311 total allocation units on disk.
131243208 allocation units available on disk.

Internal Info:
00 12 02 00 4f 01 02 00 e8 c7 03 00 00 00 00 00 ....O...........
40 02 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 @...L...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>

writhziden · Apr 15, 2012

Don't worry about the mouse drivers just yet. Disk checks came back clean. Proceed with the Memtest86+ step.

Brunan · Apr 17, 2012

Tested both RAM sticks in one slot so far. No errors at all so far, So I can safely say that both sticks and one slot are fine. I will be testing the 2nd slot tomorrow, Ill tell you the news then.

Brunan · Apr 18, 2012

Okay, The last MemTest finished about 2 hours ago, Only got on the computer now. It showed up One error. I didn't know how to copy what it said so here is what I took down straight from the screen.

==========
Tst: 3
Pass: 0
Failing Address: 00000100014 - 1.0mb
Good: ffffffff
Bad: fff8ffff
Err-Bits: 00070000
Count: 1
CPU: 0
==========

Writhziden, Are you able to translate this for me please?

writhziden · Apr 18, 2012

It means either the module you tested or the slot you tested is bad. I would recommend testing with the same module that produced the error in the other slot(s). If you do not want to run Memtest86+, just run Windows as you normally would with that module in the other slot. See if Windows is stable or not. Run that way for as long as it normally takes to get a crash. If it crashes, the module is likely bad. Test the other module in each slot by running Windows as long as it normally takes to get a crash. See if the system is then stable with that module. Remember to avoid static damage to your modules and PC.

Brunan · Apr 18, 2012

I tested Stick 1 and Stick 2 in Slot 1 and got no errors. Other for today, where I tested Stick 1 in Slot 2, So I take it that Slot 2 is bad?
Also, To get the use of both my sticks again, Can I just use the other 2 slots available on my Motherboard?

writhziden · Apr 18, 2012

If it is a bad slot, then yes, you can use the other two slots. There are no guarantees that it is not a bad module, though. Keep track of which module may be bad. Memtest86+ can throw errors sometimes and not other times for a bad module. It is not an exact science because electronics can be rather finicky. Sometimes, it takes multiple tests to determine a bad module, and sometimes Windows makes a better memory testing tool than any diagnostic because it stresses RAM in more ways than the diagnostics do. That is why I was recommending testing by doing your normal routine in Windows and seeing if the system was stable with different modules in different slots.

You can try the two modules in the other two slots and see if Windows is stable. If it is not, try removing the suspected bad module and running Windows again to see how it responds.

Brunan · Apr 20, 2012

Okay, I have moved the 2 Modules to the 2 other slots. Going okay so far, I'm using my computer as I normally would and no crash's.
If I get no crash's by Monday I will mark this as Solved.
Thanks for all the work you've done Writhziden, You have been a massive help to me, I'm extremely grateful

writhziden · Apr 20, 2012

You're welcome.

Glad it has been more stable. Best wishes it remains so!

Brunan · Apr 21, 2012

Emm, I think I spoke to soon. I got a Blue Screen today after about 10 minutes of my computer being on. I have attached the Dump File. For some reason, I didn't physically see the Blue Screen, The computer just froze for a second and then restarted all on its own, Is this strange?

writhziden · Apr 21, 2012

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\Brunan\042112-24429-01\042112-24429-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`0424e000 PsLoadedModuleList = 0xfffff800`04492650
Debug session time: Sat Apr 21 06:50:40.304 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:15.896
Loading Kernel Symbols
..................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80081b8748, 0, 0}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80081b8748, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031bd6f0 fffff800`0450fca9 : fffffa80`081b8720 fffffa80`06a56b60 00000000`0000000b 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031bdc10 fffff800`043f0577 : fffffa80`081b8720 fffff800`0446a2b8 fffffa80`06a56b60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031bdc40 fffff800`04357935 : fffff800`044cbac0 00000000`00000001 fffffa80`0797a820 fffffa80`06a56b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031bdc80 fffff800`042d4361 : fffff880`0111be00 fffff800`04357910 fffffa80`06a56b00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031bdcb0 fffff800`04564fda : 00000000`00000000 fffffa80`06a56b60 00000000`00000080 fffffa80`06a25040 : nt!ExpWorkerThread+0x111
fffff880`031bdd40 fffff800`042bb9c6 : fffff880`02f64180 fffffa80`06a56b60 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bd5e0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

Proceed by reading about your crash in http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Also, you may want to try running with just the memory module that did not show any errors. See if it was the module that was causing the errors in Memtest86+ and not the slot.

Brunan · Apr 24, 2012

I got yet another BSOD, But it didn't give a Dump. I'm not sure why, But here is everything I took down off the screen

Stop Error: 7E
***dxymmsl.sys - Address FFFFF880045BA1BC base at FFFFF880457C000, Datestamp 4ce799C1

writhziden · Apr 24, 2012

Was this with the one suspected good RAM module?

The crash points to your graphics card drivers or the hardware itself. Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Dev Center - Hardware > Learn > Debugging > Windows Debugging > Bug Checks (Blue Screens) > Bug Check Code Reference > Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED said:
Resolution
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 exception code 0x80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure that a kernel debugger is connected and the system is started with the /DEBUG switch.
~~If exception code 0x80000002 occurs, the trap frame supplies additional information.~~
If you do not know the specific cause of the exception, consider the following issues:

Hardware incompatibility. Make sure that any new hardware that is installed is compatible with the installed version of Windows. For example, you can get information about compatibility with Windows 7 at the Windows 7 Compatibility Center.

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 a driver is listed by name within the bug check message, disable or remove that driver. 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 must 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 computer 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 0x7E.
You can also disable memory caching of the BIOS might 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 .chk files 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.

Try re-installing DirectX using the Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details and see how the system responds.

Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

Download the latest drivers for your display card(s)
Click Start Menu
Click Control Panel
Click Uninstall a program
For NVIDIA:
- Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
- Restart your computer
- Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
- If any remain of the above, uninstall one at a time
- If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
For AMD:
- Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
- If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
  1. Click Start Menu
  2. Right Click My Computer/Computer
  3. Click Manage
  4. Click Device Manager from the list on the left
  5. Expand Display adapters
  6. Do the following for each adapter (in case you have multiple display cards)
    - Right click the adapter
    - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  7. Restart your computer after uninstalling drivers for all display cards
  8. Install the latest driver for the display cards once Windows starts
  Alternatively:
  1. Login as an adminstrative user
  2. Click Start Menu
  3. Click Control Panel
  4. Click Hardware and Sound
  5. Click Device Manager (the last link under Devices and Printers)
  6. Expand Display adapters
  7. Do the following for each adapter (in case you have multiple display cards)
    - Right click the adapter
    - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer after uninstalling drivers for all display cards
Install the latest driver for the display cards once Windows starts

System Service Exeption 0x3B

New member

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer