Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: System Service Exeption 0x3B


12 Apr 2012   #1

Windows 7 Home Premium 64bit
 
 
System Service Exeption 0x3B

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.


My System SpecsSystem Spec
.

12 Apr 2012   #2

Windows 7 Home Premium 64bit
 
 

Bump, Please help me guys.
My System SpecsSystem Spec
13 Apr 2012   #3

Windows 7 Home Premium 64 Bit
 
 

http://www.sevenforums.com/general-d...ease-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 Check Disk (chkdsk) - Read Event Viewer Log.
    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.
My System SpecsSystem Spec
.


14 Apr 2012   #4

Windows 7 Home Premium 64bit
 
 

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>
My System SpecsSystem Spec
14 Apr 2012   #5

Windows 7 Home Premium 64bit
 
 

I'm after getting the BSOD again, this time with the error code APC_INDEX_MISMATCH. Attached is the dump file.
My System SpecsSystem Spec
14 Apr 2012   #6

Windows 7 Home Premium 64bit
 
 

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.
My System SpecsSystem Spec
14 Apr 2012   #7

Windows 7 Home Premium 64 Bit
 
 

Code:
  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 ---------
  2. 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 ---------
  3. 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 ---------
  1. 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.
  2. Same possible causes as 1. but points more toward memory problems...
  3. 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.
My System SpecsSystem Spec
15 Apr 2012   #8

Windows 7 Home Premium 64bit
 
 

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>
My System SpecsSystem Spec
15 Apr 2012   #9

Windows 7 Home Premium 64 Bit
 
 

Don't worry about the mouse drivers just yet. Disk checks came back clean. Proceed with the Memtest86+ step.
My System SpecsSystem Spec
17 Apr 2012   #10

Windows 7 Home Premium 64bit
 
 

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.
My System SpecsSystem Spec
Reply

 System Service Exeption 0x3B




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:13 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33