So my windows explorer keeps crashing radomly every 3-5min. not sure whats causing it. I have windows 7 64bit.
Either a corrupt OS install, or bad RAM. Not much else could constantly kill explorer like that. Lets check the easy one first: Download/run memtest86+ for a few hours to check the RAM for errors.
An unstable CPU overclock can do this as well. OP, remove any overclocks (on CPU, motherboard, ram, GPU, VRam, any voltage increases) and see if it still happens. Work from there if it is now stable.
or maybe some context program hookup. Try ShellExView http://www.nirsoft.net/utils/shexview.html For corrupt OS, open CMD and type in sfc /scannow And maybe try Windows7manager and run repair center >> windows components repair and rebuild WMI.. http://forums.guru3d.com/showpost.php?p=4434566&postcount=16
firefox did that for me randomly, took me days to track it. uninstalled it and it was gone. specifically when i had clear history on exit ticked on i think!
Do you mean Windows Explorer as in the interface part, or Windows Explorer as in the file manager part? Plugins can cause crashes like that, especially in the file manager part. For instance, thumbnail view of video files, a third party video decoder (ffdshow for example) might be used to decode the image for the thumbnail.
ok, so i used hitman pro and malwarebyte to get rid of all harmful stuff. Still is happening. My cpu is oc but its been stable for a year. here is the error log. Log Name: Application Source: Application Error Date: 11/6/2012 5:58:43 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Knuk-PC Description: Faulting application name: explorer.exe, version: 6.1.7601.17567, time stamp: 0x4d672ee4 Faulting module name: atiumd64.dll, version: 9.14.10.926, time stamp: 0x5064fc85 Exception code: 0xc0000005 Fault offset: 0x000000000019088b Faulting process id: 0x1b40 Faulting application start time: 0x01cdbc82fcbca189 Faulting application path: C:\Windows\explorer.exe Faulting module path: C:\Windows\system32\atiumd64.dll Report Id: 4629110d-2876-11e2-ae8c-002683337853 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-11-07T00:58:43.000000000Z" /> <EventRecordID>28547</EventRecordID> <Channel>Application</Channel> <Computer>Knuk-PC</Computer> <Security /> </System> <EventData> <Data>explorer.exe</Data> <Data>6.1.7601.17567</Data> <Data>4d672ee4</Data> <Data>atiumd64.dll</Data> <Data>9.14.10.926</Data> <Data>5064fc85</Data> <Data>c0000005</Data> <Data>000000000019088b</Data> <Data>1b40</Data> <Data>01cdbc82fcbca189</Data> <Data>C:\Windows\explorer.exe</Data> <Data>C:\Windows\system32\atiumd64.dll</Data> <Data>4629110d-2876-11e2-ae8c-002683337853</Data> </EventData> </Event>
Seems like a driver issue, which version are you using? If using the newer ones like beta try rolling back to previous stable drivers Or you can try this http://forums.guru3d.com/showpost.php?p=4430619&postcount=189
I hafe the same problem is there a solution yet ? FAULTING_IP: atiumd64+19088b 000007fe`e89c088b 8988443f0000 mov dword ptr [rax+3F44h],ecx EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 000007fee89c088b (atiumd64+0x000000000019088b) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000001 Parameter[1]: 0000000000003f44 Attempt to write to address 0000000000003f44 DEFAULT_BUCKET_ID: INVALID_CLASS_PTR_WRITE PROCESS_NAME: explorer.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced me mory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000001 EXCEPTION_PARAMETER2: 0000000000003f44 WRITE_ADDRESS: 0000000000003f44 FOLLOWUP_IP: atiumd64+19088b 000007fe`e89c088b 8988443f0000 mov dword ptr [rax+3F44h],ecx NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 APP: explorer.exe FAULTING_THREAD: 0000000000000f38 PRIMARY_PROBLEM_CLASS: INVALID_CLASS_PTR_WRITE BUGCHECK_STR: APPLICATION_FAULT_INVALID_CLASS_PTR_WRITE_INVALID_ POINTER_WRITE LAST_CONTROL_TRANSFER: from 0000000000000000 to 000007fee89c088b STACK_TEXT: 00000000`02f9dc00 00000000`00000000 : 00000000`00000000 00000000`00170016 000007 fe`ed5d4cf0 00000000`02f9de40 : atiumd64+0x19088b STACK_COMMAND: ~5s; .ecxr ; kb SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: atiumd64+19088b FOLLOWUP_NAME: MachineOwner MODULE_NAME: atiumd64 IMAGE_NAME: atiumd64.dll DEBUG_FLR_IMAGE_TIMESTAMP: 5064fc85 FAILURE_BUCKET_ID: INVALID_CLASS_PTR_WRITE_c0000005_atiumd64.dll!Unkn own BUCKET_ID: X64_APPLICATION_FAULT_INVALID_CLASS_PTR_WRITE_INVA LID_POINTER_WRITE_ atiumd64+19088b WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne...r_exe/6_1_7601 _17567/4d672ee4/atiumd64_dll/9_14_10_926/5064fc85/c0000005/0019088b.htm?Retriage =1 rax=0000000000000000 rbx=000000000487f7d0 rcx=0000000000000000 rdx=0000000002f9dc50 rsi=000007fee89c0870 rdi=0000000002f9dea0 rip=000007fee89c088b rsp=0000000002f9dc00 rbp=0000000002f9dc20 r8=0000000000000000 r9=0000000000000000 r10=00000000047cfb40 r11=0000000000000000 r12=0000000000000100 r13=0000000000000001 r14=0000000002981780 r15=0000000002981880 iopl=0 nv up ei pl zr na po nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246 atiumd64+0x19088b: 000007fe`e89c088b 8988443f0000 mov dword ptr [rax+3F44h],ecx ds:00000000` 00003f44=????????
Can you get into safe mode? I found that when reverting back to older amd drivers (faulty and causing bsod's), it still stored the newer ones, if you can boot into safe mode then open the device manager, open the cards properties and manually select an older working driver.
c000005 usually means memory issue. I OC'ed my ram to 1110mhz and any intense game would always crash with this exception code. Ram passes IBT or Linx or Windows memory diagnostic, only games.. Lower your system ram OC or lose its latency a bit.