Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
20632 Discussions

Intel HD 530 causing "Windows Explorer" error in "System"

RRees1
Beginner
3,379 Views

I just built a new computer. I am a novice. I learn enough to build a computer and then forget it all once it's up and running until I want/need a new card or box or something like that. Well, I fired this one up just fine and was pleased. But, as I began installing drivers, I saw one odd quirk. When I install the Intel HD Graphics 530 driver, it causes an error, but only when I attempt to go into the "System" page under "Control Panel." The error is, "Windows Explorer Has Stopped Working," and it says it's restarting then takes me back to the desktop. If I uninstall Intel's HD 530 driver, the error goes away. I had to uninstall the HD 530 driver just to authenticate windows. I've tried every driver (including the beta version) that Intel has on its support page.

Now, my first approach was to attack this by trying to determine what was wrong with Windows Explorer (explorer.exe) and I tried looking at the registry and all that, but nothing worked. Then, I uninstalled all my drivers and through trial and error determined that it was this video driver that was causing the problem. It could be some conflict between the two, but why would it only occur in "System"?? It's a strange error and I cannot figure out how to make it go away. I haven't seen it anywhere else and it may have no real practical effect, but I hate ghosts in the machine like this and would prefer to get this resolved before I start loading additional software, etc.

Here's my build:

Windows 7 x64

Motherboard: Gigabyte GA-B150M-D3H-GSM DDR4 with onboard graphics (no separate video card)

CPU: Intel Core Skylake i5-6500 with Intel HD Graphics 530

RAM: Corsair Vengeance LPX DDR4 2133MHZ 16gb (2x8gb sticks)

SSD: Samsung 850 EVO 500gb

ODD: SilverStone slim slot; SST-SOD02

PSU: EVOGA 650 GQ modular

Case: Raijintek Styx

0 Kudos
5 Replies
Anonymous
Not applicable
993 Views

Hi BilleyPilgrim,

This is a new integration with Windows® 7. I suggest you to reinstall the operating system, install the latest Chipset and Management Engine drivers from Gigabyte website.

Then, run Windows® 7 update and finally try again with the latest graphics driver for HD graphics 530, file name:

win61_154010.4300.exe

https://downloadcenter.intel.com/download/25484/Intel-Graphics-Driver-for-Windows-7-8-1-10-15-40 https://downloadcenter.intel.com/download/25484/Intel-Graphics-Driver-for-Windows-7-8-1-10-15-40-

Regards,

 

Mike C
0 Kudos
RRees1
Beginner
993 Views

Thank you, Mike C. I tried that. I've re-installed Windows about 4 times now. I've had to install a graphics card, which works, but my goal was to just use the onboard video.

0 Kudos
Anonymous
Not applicable
993 Views

Hi BilleyPilgrim,

Could you please confirm if you used the graphics file win64_154010.4300.exe?

https://downloadcenter.intel.com/download/25484/Intel-Graphics-Driver-for-Windows-7-8-1-10-15-40- Download Intel® Graphics Driver for Windows® 7/8.1/10* [15.40]

If yes, I suggest you to install an older driver, let's try to narrow down the issue.

https://downloadcenter.intel.com/product/88184/Intel-Core-i5-6500-Processor-6M-Cache-up-to-3-60-GHz https://downloadcenter.intel.com/product/88184/Intel-Core-i5-6500-Processor-6M-Cache-up-to-3-60-GHz-

Please, reply with a picture of the issue.

Regards,

 

Mike C
0 Kudos
RRees1
Beginner
993 Views

I think it was bad RAM, but it appears to be fixed. Basically, I disabled onboard graphics and uninstalled the HD 530 software, installed a fairly cheap graphics card I had in an old setup, and just used that for a while. That got my system up and runnning. I installed Windows updates (there were so many...), etc. Then, I ordered new RAM and installed it. Disabled my graphics card, re-installed the HD Driver and bam, it seems to be working fine now.

I probably should have tried it one last time before installing the new RAM to see if it was somehow linked to a Windows update that did or did not install. Then, I'd feel more confident about my shoddy RAM diagnosis. Nevertheless, I think we're good to go. Thanks, Mike C.

0 Kudos
Anonymous
Not applicable
993 Views

Hi BilleyPilgrim,

Thank you for your feedback.

Regards,

 

Miguel C
0 Kudos
Reply