The stop code is
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bug check, the debugger doesn't give a lot of information on the cause.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+6333373330386364
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002f8b328 -- (.exr 0xfffff88002f8b328)
ExceptionAddress: fffff80002c947a5 (nt!KiTimerWaitTest+0x00000000000002a5)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: ffffffffffffffff
Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000
TRAP_FRAME: fffff88002f8b3d0 -- (.trap 0xfffff88002f8b3d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000009 rbx=0000000000000000 rcx=0000000000000000
rdx=effffa8003fb80d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c947a5 rsp=fffff88002f8b560 rbp=effffa8003fb80d0
r8=fffff88002f65301 r9=0000000000000002 r10=0000000000000002
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe cy
nt!KiTimerWaitTest+0x2a5:
fffff800`02c947a5 488b6d00 mov rbp,qword ptr [rbp] ss:0018:effffa80`03fb80d0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c836be to fffff80002c8bcd0
STACK_TEXT:
fffff880`02f8a408 fffff800`02c836be : 00000000`00000002 fffff800`031f7e08 fffff880`02f8ab80 fffff800`02cb7890 : nt!KeBugCheck
fffff880`02f8a410 fffff800`02cb755d : fffff800`02e92968 fffff800`02dcfcbc fffff800`02c0c000 fffff880`02f8b328 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8a440 fffff800`02cb6335 : fffff800`02dd30fc fffff880`02f8a4b8 fffff880`02f8b328 fffff800`02c0c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8a470 fffff800`02cc73b1 : fffff880`02f8b328 fffff880`02f8ab80 fffff880`00000000 fffffa80`03d7bcc0 : nt!RtlDispatchException+0x415
fffff880`02f8ab50 fffff800`02c8b382 : fffff880`02f8b328 fffffa80`03d7bcc8 fffff880`02f8b3d0 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`02f8b1f0 fffff800`02c89b52 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02f8b3d0 fffff800`02c947a5 : fffff800`02dfee80 fffffa80`05ac4b60 00000000`00000000 fffffa80`03d7bcc0 : nt!KiStackFault+0x112
fffff880`02f8b560 fffff800`02c9749d : fffffa80`03d7bcc0 fffffa80`040cc298 fffffa80`040cc298 00000000`00000000 : nt!KiTimerWaitTest+0x2a5
fffff880`02f8b5e0 fffff800`02c973de : 000000ab`50432319 fffff880`02f8bc58 00000000`0047f802 fffff880`02f655c8 : nt!KiProcessExpiredTimerList+0x6d
fffff880`02f8bc30 fffff800`02c971c7 : 00000032`5c823bc1 00000032`0047f802 00000032`5c823b95 00000000`00000002 : nt!KiTimerExpiration+0x1be
fffff880`02f8bcd0 fffff800`02c83a2a : fffff880`02f63180 fffff880`02f6dfc0 00000000`00000000 fffff880`04855480 : nt!KiRetireDpcList+0x277
fffff880`02f8bd80 00000000`00000000 : fffff880`02f8c000 fffff880`02f86000 fffff880`02f8bd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`02c836be 90 nop
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b
FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Followup: MachineOwner
---------
Check for newer drivers, 2009+, or uninstall the programs for testing purposes.
Code:
AsIO AsIO.sys Mon Dec 17 17:11:49 2007 - Asus PCProbe Utility - [URL]http://support.asus.com/download/download.aspx[/URL]
Uninstall all the Asus utility programs, they are known to cause crashes.
You can re-install later, one by one, if you want to keep them.
You have a lot of these errors, as well as app hangs.
Since sfc scannow didn't repair it, rebuild the index.
How to Rebuild the Windows 7 Index
Code:
Event[190]:
Log Name: Application
Source: Microsoft-Windows-Search
Date: 2011-05-27T16:58:48.000
Event ID: 3028
Task: Gatherer
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Ryan-PC
Description:
The gatherer object cannot be initialized.
Context: Windows Application, SystemIndex Catalog
Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)
Event[193]:
Log Name: Application
Source: Microsoft-Windows-Search
Date: 2011-05-27T16:58:47.000
Event ID: 9002
Task: Search service
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Ryan-PC
Description:
The Windows Search Service cannot load the property store information.
Context: Windows Application, SystemIndex Catalog
Details:
The content index server cannot find a description of the content index in its database. Search will automatically attempt to recreate the content index description. If this problem persists, stop and restart the search service and, if necessary, delete and recreate the content index. (HRESULT : 0x80041181) (0x80041181)
Update MSE, this is indicating that the
latest definitions have not been updated.
Code:
Event[3618]:
Log Name: System
Source: Microsoft Antimalware
Date: 2011-05-28T18:43:28.000
Event ID: 3002
Task: N/A
Level: Error
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Ryan-PC
Description:
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed.
Feature: Behavior Monitoring
Error Code: 0x80004005
Error description: Unspecified error
[COLOR=red]Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection[/COLOR].
Update, reinstall the mouse driver.
Code:
Event[5331]:
Log Name: System
Source: XMouseButton Launcher
Date: 2011-05-28T07:59:31.000
Event ID: 0
Task: N/A
Level: Error
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Ryan-PC
Description: N/A
Which Graphics Card driver do you have installed?
AODDriver.sys - this is reported as >AMD Overdrive; also in EasyTune6 for Gigabyte motherboard
I am assuming you have an Asus mobo, add to your system specs.
Post the current perfmon report in your next post.
Code:
Event[6025]:
Log Name: System
Source: Service Control Manager
Date: 2011-05-27T18:33:06.155
Event ID: 7000
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Ryan-PC
Description:
The AODDriver4.0 service failed to start due to the following error:
The system cannot find the path specified.
There are many errors per day, let's do a malware check.
Download and run Malwarebytes, be sure to update it before running.
If this doesen't fix the problem, then you need to look at hardware.
You have the latest BIOS version for your motherboard.
You have done a lot of testing, your next step may be to do a Repair Install or Clean Install.
Let's eliminate all the hardware possible causes first.
Replace your keyboard and mouse for testing purposes, if you have a spare or borrow them, I have seen these cause this type of crash.
At this stage it is best to try and eliminate all variables as possible.
Disconnect all peripherals not required to run your system, all external drives, any USB hubs or connected devices, CD ROM if not needed, sound card and speakers, etc., everything.
If the crashes stop, then re-install them one at a time and test for stability.
If they don't stop then you need to look at the main internal components.
