Windows 7 x64 Intermittent Explorer Crashes

[sanzen07]

Hi guys,

I am trying to figure out what is wrong with Windows 7 on my computer. I am running Windows 7 x64 with all of the latest updates and I am getting intermittent explorer.exe crashes at random moments. I am not sure what the problem is and was hoping someone could point me in the right direction. I have the latest drivers for all of my hardware. This was not happening when I initially built my machine back in mid-2012 but I believe it started sometime in the past 6 months to a year ago. It's now reached the point where it's annoying as heck. See below for details. Thanks for any help in finding the solution to this issue!

What I have tried:

- clean reinstalling Windows 7
- running memtest86+ for many hours (with no errors found)

An example of an error that shows up in Windows Event Viewer after an explorer.exe crash:

Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000041d
Fault offset: 0x0000000004a90fd8
Faulting process id: 0x71c
Faulting application start time: 0x01cf83775fab89ae
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: unknown
Report Id: 347aa427-ef6e-11e3-9c28-00224d866507

Relevant system specs:

Intel Core i7-3770K Ivy Bridge
Intel DZ77GA-70K Motherboard
16GB (4x4GB) Corsair Vengeance Low Profile 1600mhz DDR3 (CML16GX3M4A1600C9)
Gigabyte GeForce GTX 670 2048MB "Windforce 3x" 256-bit PCI-E 3.0 (GV-N670OC-2GD)
ASUS Xonar Essence ST PCI Sound Card
ASUS PCE-N15 802.11n Wireless PCI-Express LAN Card
Intel 320 Series 120GB 2.5" Solid-State Drive
Western Digital Caviar SE WD7500AAKS 750GB SATA Hard Drive
Samsung SH-S203N SATA DVD Writer with Lightscribe
Seasonic X-560 SS-560KM 560 Watt ATX Power Supply

Update 1: It is not blue screening. I get a dialog saying "explorer.exe has stopped working" and then explorer relaunches automatically. No new hardware has been added since the computer was built. I have added various pieces of software since I built it. I used the same DVD to re-install as I did with the original install. When I installed I wiped the main drive (SSD).

 

[SimMike2]

So it is blue screening on you?

 

[Dave3000]

I used to get Explorer crashes when accessing stuff from the Control Panel in Windows 7 Pro SP1. I tried new memory, different CPU, different network drivers but it still happened. What fixed it for me was redownloading the official Windows 7 SP1 ISO (not a torrent) and reinstalling Windows 7 SP1 from that ISO and I haven't had that problem since. Also installing Windows 7 from my retail disc and then upgrading to SP1 still gave me the same errors. Maybe something was corrupted in the ISO the first time I downloaded it and maybe there was something corrupted in the SP1 file as well, I don't know.

 

[Ketchup]

Have you added any hardware/ software in the past year?

Did you use the same DVD to re-install Windows as you did the original install?

What all did you re-install before the explorer crashes came back?

When you re-installed Windows, are well saying this is from a wiped drive or partition, or did you just delete the old install?

If you are getting blue screens, I might suggest a program, such as whocrashed, to see if more data on this is available.

 

[sanzen07]

See original post for updates. I may try getting the official Windows 7 SP1 ISO and doing another re-install to see if that fixes the issue.

 

[Ketchup]

See original post for updates. I may try getting the official Windows 7 SP1 ISO and doing another re-install to see if that fixes the issue.

Good info thanks. When you re-installed Windows, did you disconnect the Caviar?

Have you ever checked the Caviar for malware?

When the crashes started after the re-install, had you installed anything from the Caviar onto the SSD?

 

[sanzen07]

Yes, I run virus and malware scans about every 2 weeks. I did not disconnect the Caviar when installing Windows. I keep my downloaded application installers on the Caviar, so I used that to install much of my software.

 

[Ketchup]

... I keep my downloaded application installers on the Caviar, so I used that to install much of my software.

That part alone is fine, but Windows has a bad habit of putting the MBR on a different drive when multiple drives are connected during the initial Windows installation.

Now, in your particular case, the issues don't remind me of an issue that would cause, but plenty of visitors here have had issues when doing an install with more than one drive present.

 

[JackMDS]

A an experiment take out the Wireless card and see if it keep happening.

 

[sanzen07]

Just adding another update here after taking more steps. I ended up downloading the official Windows 7 x64 SP1 ISO and reinstalling Windows with that. When I reinstalled, I disconnected my secondary drive (the Caviar) during the install. Everything seemed to be okay for a bit but now I am getting a different sort of explorer.exe crash:

Problem signature:
  Problem Event Name:    BEX64
  Application Name:    Explorer.EXE
  Application Version:    6.1.7601.17567
  Application Timestamp:    4d672ee4
  Fault Module Name:    StackHash_a417
  Fault Module Version:    0.0.0.0
  Fault Module Timestamp:    00000000
  Exception Offset:    0000000004980fd8
  Exception Code:    c0000005
  Exception Data:    0000000000000008
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1:    a417
  Additional Information 2:    a41736ed71912b9cc53a8c82f18d8b16
  Additional Information 3:    d9b8
  Additional Information 4:    d9b82c48d6f9d0138f64dafadac8e31c

Read our privacy statement online:
  [URL]http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409[/URL]

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

The dialog is different than before and shows the error information above and I have to click continue before explorer restarts. Before it just said explorer has stopped working and then restarted explorer.exe automatically. It seems to be happening slightly less often than before I reinstalled, so I guess that is good. I ran a chkdsk on all my drives just to see if there were any problems, and no errors were detected.

 

[Ketchup]

I know you said that your tested the RAM, but I would start running 2 sticks at a time to see if things change at all. What speed are you running the RAM? And what voltage?

 

[sanzen07]

I know you said that your tested the RAM, but I would start running 2 sticks at a time to see if things change at all. What speed are you running the RAM? And what voltage?

Memory is running 1600mhz @ 1.5V (9-9-9-24).

 

[John Connor]

I am having Explorer crashes too and I think it's hard drive related. I actually installed Windows 7 64 with a SSD and platter installed, luckily I don't think the MBR was stuck on the platter since I just did a low level format of the second drive, the platter.

I too tested my memory with Memtest 86 for a half day and all night with a total of 9 passes and no errors. My bro has had no errors, but he changed memory anyway and it solved what ever computer problem he was having. Probably incompatible RAM.

 

[sanzen07]

Well, I am reporting back again. I still haven't solved this annoying issue and have no idea what to try next. Is it possible there is a problem with my SSD? I have no idea what to try next. I see other errors in the Windows logs, which I am pasting in case they have anything to do with my issue (don't know if they are normal or not):

Many of these:
Source: WLAN-AutoConfig
WLAN Extensibility Module has failed to start.
Module Path: C:\Windows\system32\Rtlihvs.dll
Error Code: 126

Source: WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

 

[code65536]

Errors like that in the event logs mean very little and are not a concern.

Generally, as a rule of thumb, if explorer.exe (and only explorer.exe) is in a crashy mood, then you're likely looking at a bad COM object. I'm surprised nobody has suggested this yet. Anyway, this is because the Windows shell (explorer.exe) is highly extensible and thus can play host to a lot of third-party code. And more likely than not, if there's a crash in the shell, it's that buggy third-party code.

Especially since your crash has a StackHash signature, which means that the crashing code is not in a loaded module. In the context of explorer.exe, this often (though not always) suggests that a DLL was improperly unloaded--i.e., it was removed even though it was still in use. And this often (though not always) is the result of a reference counting bug in a COM object. Anyway, that's just an educated guess based on the very thin information in this thread. But in any case, memory and disk corruption are unlikely culprits given the nature of this crash (for starters, if it was hardware, other programs should be crashy, too). (StackHash can also mean that the crashed code was generated, which is why you see a lot of StackHash signatures when a web browser crashes, because stuff like JavaScript is generated code.)

Does this happen on a completely clean install? (i.e., nothing else installed, not even device drivers--though device drivers manually installed by their INF via the Device Manager are generally fine, but device drivers installed via an installer could drop off a COM object; e.g., GPU drivers polluting your desktop context menu with a shortcut to their configuration because polluting your system notification area with their ugly icon apparently wasn't enough)

Alternatively, you can run Process Explorer, select the explorer.exe process, press Ctrl-D to bring up the list of loaded DLLs, sort by the Company Name column, and post everything not made by Microsoft Corporation. That's the list of third-party DLLs loaded by explorer.exe. There is a chance that one of them is the culprit. But given the dynamic-load nature of COM, procexp might not catch it. As another alternative, you can also look in Autoruns for third-party extensions to Explorer.

 

[sanzen07]

@code65536:

So I did another completely clean install last night (on a brand new hard drive) and as I was installing my programs I received another crash. So I turned on capturing of crash dumps and when it happened again I opened the dump file in WinDbg and did an analyze. Below is the ouput - does it tell you anything? I also ran Process Explorer and the only DLL I see loaded that is non-Microsoft is Nvidia Display Shell Extension (nvshext.dll).

Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\LocalDumps\explorer.exe.1752.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

WARNING: Whitespace at end of path element
Error: Empty Path.
Symbol search path is: [URL]http://msdl.microsoft.com/download/symbols[/URL] 
Executable search path is: 
Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Fri Sep  5 22:41:52.000 2014 (UTC - 7:00)
System Uptime: not available
Process Uptime: 0 days 0:23:56.000
................................................................
................................................................
..............................................
Loading unloaded module list
................................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(6d8.794): Access violation - code c0000005 (first/second chance not available)
ntdll!ZwWaitForMultipleObjects+0xa:
00000000`778618ca c3              ret
0:003> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


FAULTING_IP: 
+49bcff0
00000000`02a80fd8 ??              ???

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0000000002a80fd8
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 0000000002a80fd8
Attempt to execute non-executable address 0000000002a80fd8

CONTEXT:  0000000000000000 -- (.cxr 0x0;r)
rax=00000000c0000001 rbx=0000000002fae4b0 rcx=0000000002670000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000002
rip=00000000778618ca rsp=0000000002fae378 rbp=0000000000000002
 r8=0000000002fada98  r9=0000000002fadc00 r10=0000000000000000
r11=0000000000000246 r12=0000000000000000 r13=0000000002fae420
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
ntdll!ZwWaitForMultipleObjects+0xa:
00000000`778618ca c3              ret

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 memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  0000000002a80fd8

WRITE_ADDRESS:  0000000002a80fd8 

FOLLOWUP_IP: 
explorer!CTaskBand::_SwitchToWindow+139
00000000`ff094ed7 4585e4          test    r12d,r12d

FAILED_INSTRUCTION_ADDRESS: 
+139
00000000`02a80fd8 ??              ???

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

APP:  explorer.exe

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

FAULTING_THREAD:  0000000000000794

BUGCHECK_STR:  APPLICATION_FAULT_SOFTWARE_NX_FAULT_INVALID

PRIMARY_PROBLEM_CLASS:  SOFTWARE_NX_FAULT_INVALID

DEFAULT_BUCKET_ID:  SOFTWARE_NX_FAULT_INVALID

LAST_CONTROL_TRANSFER:  from 0000000077729bd1 to 0000000002a80fd8

STACK_TEXT:  
00000000`02faf658 00000000`77729bd1 : 00000000`000e06aa 00000000`00000001 00000000`00000000 00000000`00000000 : 0x2a80fd8
00000000`02faf660 00000000`777272cb : 00000000`00000000 00000000`02a80fd8 00000000`00000000 00000000`00000000 : user32!UserCallWinProcCheckWow+0x1ad
00000000`02faf720 00000000`77726829 : 00000000`00000000 00000000`77726aa8 00000000`00000000 000007fe`00000794 : user32!DispatchClientMessage+0xc3
00000000`02faf780 00000000`77861225 : 00000000`00000001 00000000`00000000 00000000`000e06aa 00000000`77729aa6 : user32!_fnDWORD+0x2d
00000000`02faf7e0 00000000`7771cc3a : 00000000`ff094ed7 00000000`0e139810 00000000`0e139810 00000000`000e06aa : ntdll!KiUserCallbackDispatcherContinue
00000000`02faf868 00000000`ff094ed7 : 00000000`0e139810 00000000`0e139810 00000000`000e06aa 00000000`ff05acf1 : user32!NtUserCallHwndParamLock+0xa
00000000`02faf870 00000000`ff094dd2 : 00000000`000e06aa 00000000`00000000 00000000`0e139810 00000000`00000000 : explorer!CTaskBand::_SwitchToWindow+0x139
00000000`02faf8b0 00000000`ff0944d3 : 00000000`ff10d890 00000000`049a97b0 00000000`00000001 00000000`00000001 : explorer!CTaskBand::SwitchTo+0xe9
00000000`02faf8f0 00000000`ff094326 : 0000000d`00000082 00000000`029bce10 00000000`00000082 00000000`0000000d : explorer!CTaskListWnd::_HandleClick+0x369
00000000`02faf950 00000000`ff09427d : 00000000`00000000 00000000`029bce10 00000000`00000000 00000000`00000000 : explorer!CTaskListWnd::_HandleMouseButtonUp+0xdc
00000000`02faf990 00000000`ff0512b0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`7772919b : explorer!CTaskListWnd::v_WndProc+0x5e9
00000000`02fafa90 00000000`77729bd1 : 00000000`00000000 80000000`02010000 00000000`00000001 00000000`00000000 : explorer!CImpWndProc::s_WndProc+0x91
00000000`02fafad0 00000000`777298da : 00000000`02fafc40 00000000`ff05124c 00000000`0015ec61 00000000`006b8220 : user32!UserCallWinProcCheckWow+0x1ad
00000000`02fafb90 00000000`ff051177 : 00000000`ff138800 00000000`ff138800 00000000`ff05124c 00000000`00000001 : user32!DispatchMessageWorker+0x3b5
00000000`02fafc10 00000000`ff0730e9 : 00000000`ff138800 00000000`ff138800 00000000`ff138800 00000000`001b7da0 : explorer!CTray::_MessageLoop+0x446
00000000`02fafca0 000007fe`fdedc71e : 00000000`00000000 00000000`001b7da0 00000000`0000282a 00000000`0000282a : explorer!CTray::MainThreadProc+0x8a
00000000`02fafcd0 00000000`7760652d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : shlwapi!WrapperThreadProc+0x19b
00000000`02fafdd0 00000000`7783c521 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd
00000000`02fafe00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d


STACK_COMMAND:  ~3s; .ecxr ; kb

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  explorer!CTaskBand::_SwitchToWindow+139

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: explorer

IMAGE_NAME:  explorer.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a144

FAILURE_BUCKET_ID:  SOFTWARE_NX_FAULT_INVALID_c0000005_explorer.exe!CTaskBand::_SwitchToWindow

BUCKET_ID:  X64_APPLICATION_FAULT_SOFTWARE_NX_FAULT_INVALID_BAD_IP_explorer!CTaskBand::_SwitchToWindow+139

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:software_nx_fault_invalid_c0000005_explorer.exe!ctaskband::_switchtowindow

FAILURE_ID_HASH:  {24cd78ea-a9a3-9941-f35f-663f0bae82c9}

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

 

[Ketchup]

What drivers had been installed when you got the error?

 

[sanzen07]

All of them:

ASUS PCE-N15 PCI-E Wireless Card Driver 1.0.0.8
ASUS Xonar Essence ST Audio Card Driver 7.12.8.1794
Dell U2311H Monitor Driver
HP LaserJet 1020 Driver
Intel Chipset Drivers 9.4.0.1027
Intel Management Engine Driver 8.1.40.1416
Intel USB 3.0 Driver 1.0.9.254
Geforce Driver 340.52 Driver
Logitech SetPoint 6.32.20
Microsoft Intellitype Pro 8.2
Xbox 360 Controller Drivers 1.2

Also, don't know if this is important but it happened before I had done any Windows Updates. Only the base SP1 was installed since I used the official ISO w/ SP1 integrated.

 

[Ketchup]

Out of curiousity, if you uninstall the xbox driver, can you recreate the issue?

 

[sanzen07]

Out of curiousity, if you uninstall the xbox driver, can you recreate the issue?

I have uninstalled it. If the crash happens again I will report back (well, I'll report back either way )

 

[code65536]

@code65536:

So I did another completely clean install last night (on a brand new hard drive) and as I was installing my programs I received another crash. So I turned on capturing of crash dumps and when it happened again I opened the dump file in WinDbg and did an analyze. Below is the ouput - does it tell you anything? I also ran Process Explorer and the only DLL I see loaded that is non-Microsoft is Nvidia Display Shell Extension (nvshext.dll).

Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\LocalDumps\explorer.exe.1752.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

WARNING: Whitespace at end of path element
Error: Empty Path.
Symbol search path is: [URL]http://msdl.microsoft.com/download/symbols[/URL] 
Executable search path is: 
Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Fri Sep  5 22:41:52.000 2014 (UTC - 7:00)
System Uptime: not available
Process Uptime: 0 days 0:23:56.000
................................................................
................................................................
..............................................
Loading unloaded module list
................................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(6d8.794): Access violation - code c0000005 (first/second chance not available)
ntdll!ZwWaitForMultipleObjects+0xa:
00000000`778618ca c3              ret
0:003> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


FAULTING_IP: 
+49bcff0
00000000`02a80fd8 ??              ???

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0000000002a80fd8
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 0000000002a80fd8
Attempt to execute non-executable address 0000000002a80fd8

CONTEXT:  0000000000000000 -- (.cxr 0x0;r)
rax=00000000c0000001 rbx=0000000002fae4b0 rcx=0000000002670000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000002
rip=00000000778618ca rsp=0000000002fae378 rbp=0000000000000002
 r8=0000000002fada98  r9=0000000002fadc00 r10=0000000000000000
r11=0000000000000246 r12=0000000000000000 r13=0000000002fae420
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
ntdll!ZwWaitForMultipleObjects+0xa:
00000000`778618ca c3              ret

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 memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  0000000002a80fd8

WRITE_ADDRESS:  0000000002a80fd8 

FOLLOWUP_IP: 
explorer!CTaskBand::_SwitchToWindow+139
00000000`ff094ed7 4585e4          test    r12d,r12d

FAILED_INSTRUCTION_ADDRESS: 
+139
00000000`02a80fd8 ??              ???

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

APP:  explorer.exe

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

FAULTING_THREAD:  0000000000000794

BUGCHECK_STR:  APPLICATION_FAULT_SOFTWARE_NX_FAULT_INVALID

PRIMARY_PROBLEM_CLASS:  SOFTWARE_NX_FAULT_INVALID

DEFAULT_BUCKET_ID:  SOFTWARE_NX_FAULT_INVALID

LAST_CONTROL_TRANSFER:  from 0000000077729bd1 to 0000000002a80fd8

STACK_TEXT:  
00000000`02faf658 00000000`77729bd1 : 00000000`000e06aa 00000000`00000001 00000000`00000000 00000000`00000000 : 0x2a80fd8
00000000`02faf660 00000000`777272cb : 00000000`00000000 00000000`02a80fd8 00000000`00000000 00000000`00000000 : user32!UserCallWinProcCheckWow+0x1ad
00000000`02faf720 00000000`77726829 : 00000000`00000000 00000000`77726aa8 00000000`00000000 000007fe`00000794 : user32!DispatchClientMessage+0xc3
00000000`02faf780 00000000`77861225 : 00000000`00000001 00000000`00000000 00000000`000e06aa 00000000`77729aa6 : user32!_fnDWORD+0x2d
00000000`02faf7e0 00000000`7771cc3a : 00000000`ff094ed7 00000000`0e139810 00000000`0e139810 00000000`000e06aa : ntdll!KiUserCallbackDispatcherContinue
00000000`02faf868 00000000`ff094ed7 : 00000000`0e139810 00000000`0e139810 00000000`000e06aa 00000000`ff05acf1 : user32!NtUserCallHwndParamLock+0xa
00000000`02faf870 00000000`ff094dd2 : 00000000`000e06aa 00000000`00000000 00000000`0e139810 00000000`00000000 : explorer!CTaskBand::_SwitchToWindow+0x139
00000000`02faf8b0 00000000`ff0944d3 : 00000000`ff10d890 00000000`049a97b0 00000000`00000001 00000000`00000001 : explorer!CTaskBand::SwitchTo+0xe9
00000000`02faf8f0 00000000`ff094326 : 0000000d`00000082 00000000`029bce10 00000000`00000082 00000000`0000000d : explorer!CTaskListWnd::_HandleClick+0x369
00000000`02faf950 00000000`ff09427d : 00000000`00000000 00000000`029bce10 00000000`00000000 00000000`00000000 : explorer!CTaskListWnd::_HandleMouseButtonUp+0xdc
00000000`02faf990 00000000`ff0512b0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`7772919b : explorer!CTaskListWnd::v_WndProc+0x5e9
00000000`02fafa90 00000000`77729bd1 : 00000000`00000000 80000000`02010000 00000000`00000001 00000000`00000000 : explorer!CImpWndProc::s_WndProc+0x91
00000000`02fafad0 00000000`777298da : 00000000`02fafc40 00000000`ff05124c 00000000`0015ec61 00000000`006b8220 : user32!UserCallWinProcCheckWow+0x1ad
00000000`02fafb90 00000000`ff051177 : 00000000`ff138800 00000000`ff138800 00000000`ff05124c 00000000`00000001 : user32!DispatchMessageWorker+0x3b5
00000000`02fafc10 00000000`ff0730e9 : 00000000`ff138800 00000000`ff138800 00000000`ff138800 00000000`001b7da0 : explorer!CTray::_MessageLoop+0x446
00000000`02fafca0 000007fe`fdedc71e : 00000000`00000000 00000000`001b7da0 00000000`0000282a 00000000`0000282a : explorer!CTray::MainThreadProc+0x8a
00000000`02fafcd0 00000000`7760652d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : shlwapi!WrapperThreadProc+0x19b
00000000`02fafdd0 00000000`7783c521 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd
00000000`02fafe00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d


STACK_COMMAND:  ~3s; .ecxr ; kb

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  explorer!CTaskBand::_SwitchToWindow+139

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: explorer

IMAGE_NAME:  explorer.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a144

FAILURE_BUCKET_ID:  SOFTWARE_NX_FAULT_INVALID_c0000005_explorer.exe!CTaskBand::_SwitchToWindow

BUCKET_ID:  X64_APPLICATION_FAULT_SOFTWARE_NX_FAULT_INVALID_BAD_IP_explorer!CTaskBand::_SwitchToWindow+139

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:software_nx_fault_invalid_c0000005_explorer.exe!ctaskband::_switchtowindow

FAILURE_ID_HASH:  {24cd78ea-a9a3-9941-f35f-663f0bae82c9}

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

This stack is... unexpected. Did this happen when you were switching programs? Because that's what the stack is indicating. It looks almost like it could be a 64-bit porting issue--some program registering a function but truncates the address to 32 bits.

 

[sanzen07]

This stack is... unexpected. Did this happen when you were switching programs? Because that's what the stack is indicating. It looks almost like it could be a 64-bit porting issue--some program registering a function but truncates the address to 32 bits.

No, it's rather random but most of the time it happens when I am doing operations in windows explorer. Copying files, moving files, browsing files, etc.

I'm starting to wonder if my motherboard is bad and I should try another one. I have had numerous issues with it since I bought it, like my keyboard randomly not being recognized on boot or having certain USB devices plugged in causing it to not boot at all.