Windows 7 Explorer.exe not responding - Event ID 1000 (New Build)

Rogue_Shadow

Reputable
Dec 30, 2014
21
0
4,510
Windows 7 Explorer.exe not responding - Event ID 1000 (New Build)

Hi

I'm having stability issues with Windows 7 Explorer.exe on my newly built PC.

Explorer.exe and web browsers will crash on startup or display the " stopped responding" message upon opening.
The Explorer.exe "not responding" issue has become less frequent, however I believe it maybe linked to instability with web browsers.
I cannot find any certain trigger that causes the crash, the PC is perfectly stable when left idle or even running scans.

It may not be relevant, but for a short period I found that typing caused the crashes. Opening IE11 and clicking the links on the homepage worked fine,

however the second I typed in the address or search bar IE11 would "stop responding".
During this time I could also trigger explorer.exe to crash by searching/typing into the start menu. Yet manually clicking icons and programs didn't cause a crash. This still occurred when using the virtual keyboard.
However this is no longer happening, yet web browser instability continues. Either a crash on startup (Firefox more so than IE11) or "not responding" after various lengths of time.

Tested completed


  • SFC /scannow reveals no issues
    No graphics card or additional PCI devices are connected (motherboard/ram/cpu only)
    RAM has been tested on this PC & another known working PC & vice vera
    Driver verification manager displays no unlicensed drivers
    2009 fix for this issue is not relevant as "machine throttle" entry is not in the registry
    All installed drivers are WHQL

I would really appreciate any help with this issue & it's driving me insane right now. I can't believe I'm the only person having issues on a clean install.


Logs from event viewer:


Faulting application name: IEXPLORE.EXE, version: 11.0.9600.17496, time stamp: 0x546fddcc
Faulting module name: MSHTML.dll, version: 11.0.9600.17496, time stamp: 0x546ff2f9
Exception code: 0xc0000005
Fault offset: 0x00210001
Faulting process id: 0x41c
Faulting application start time: 0x01d03c97dc6d13e4
Faulting application path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
Faulting module path: C:\Windows\system32\MSHTML.dll
Report Id: 1c8934a5-a88b-11e4-9e13-7824af8cf5c9

--------------------------------------------------------------

Faulting application name: iexplore.exe, version: 11.0.9600.17496, time stamp: 0x546fdf97
Faulting module name: IEFRAME.dll, version: 11.0.9600.17496, time stamp: 0x546fe9dd
Exception code: 0xc0000005
Fault offset: 0x000000000047fdd1
Faulting process id: 0x10ac
Faulting application start time: 0x01d03c1ea7fb573d
Faulting application path: C:\Program Files\Internet Explorer\iexplore.exe
Faulting module path: C:\Windows\system32\IEFRAME.dll
Report Id: 4428965d-a813-11e4-8742-7824af8cf5c9

-----------------------------------------------------------------

Faulting application name: explorer.exe, version: 6.1.7601.17567, time stamp: 0x4d672ee4
Faulting module name: msvcrt.dll, version: 7.0.7601.17744, time stamp: 0x4eeb033f
Exception code: 0xc0000005
Fault offset: 0x00000000000011fd
Faulting process id: 0x87c
Faulting application start time: 0x01d03c10ed1f8569
Faulting application path: C:\Windows\explorer.exe
Faulting module path: C:\Windows\system32\msvcrt.dll
Report Id: 2bc4db76-a804-11e4-a7f1-7824af8cf5c9

--------------------------------------------------------------

Thank You!
 

Rogue_Shadow

Reputable
Dec 30, 2014
21
0
4,510
I've now turned on Driver verifier manager to force PC to BSOD when it encounters a driver conflict.

I'm getting this repeatedly



crash dump file: C:\Windows\Minidump\013115-5179-01.dmp
This was probably caused by the following module: iomap64.sys (IOMap64+0x1708)
Bugcheck code: 0xC9 (0x226, 0xFFFFF8800740F708, 0xFFFFF9802FB0EEE0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\iomap64.sys
product: ASUS Kernel Mode Driver for Windows
company: ASUSTeK Computer Inc.
description: ASUS Kernel Mode Driver for NT
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iomap64.sys (ASUS Kernel Mode Driver for NT , ASUSTeK Computer Inc.).
Google query: ASUSTeK Computer Inc. DRIVER_VERIFIER_IOMANAGER_VIOLATION