driver blocking device searching

[zepplin1]

Just built my pc last week. I have an asus maximus viii hero, so i installed the necessary drivers off of the install disk and then updated to their latest versions. But i noticed when i went into device manager that when i would try to remove a driver or search for a new device, it would just endlessly search or uninstall, and there was no way to exit the program. on top of this the windows restart would never restart as well. Also programs like cpu-z would come up with errors and would not be able to find hardware.With talking to Microsoft, we figured it was not a windows issue, So i figured it was a driver issue. I disabled all of my startups minus the windows startups and it worked fine with no issue.

So my question is, how can i find out what driver is causing the issue?

 

[maikutech]

Did you uninstall their old drivers first that came off of the cd or did you download the new drivers over it ?

 

[zepplin1]

Did you uninstall their old drivers first that came off of the cd or did you download the new drivers over it ?

Yea thinking about it now i probably shouldve uninstalled the old ones. But to answer your question no i did not.

this is the cpu-z error i get when this happens:

[bInitDriver] path = C:\Users\JOSHPC~1\AppData\Local\Temp\
[bInitDriver] GetCurrentDirectory = C:\Program Files\CPUID\CPU-Z
[bInitDriver] GetModuleFileName = C:\Program Files\CPUID\CPU-Z\cpuz.exe
[vGetOSVersion] m_iOSVersion = 2 (10.0)
[vGetOSVersion] m_bIsAMD64 = 0
[bInitDriver] m_hDriverMutex = 7C
[bDeleteFile 21:33:04] DeleteFile returned = 0 (error = 5)
[bDeleteFile 21:33:04] RemoveDirectory C:\Users\JOSHPC~1\AppData\Local\Temp\\cpuz139\ returned = 0 (error = 145)
[bInitDriver] m_szFilename = cpuz139_x64.sys
[bInitDriver] bInitDriver returned 258
[vCloseDriver 21:33:06] WaitForSingleObject error = 258
[vCloseDriver] CloseHandle(mutex) = 1

I was reading that it might be caused by the Intel Engine Management drivers? and ideas?

 

[maikutech]

Go ahead and uninstall all of drivers from control panel add and remove programs.
Once you've done that, start off with sound card drivers, next ethernet drivers, then you go for the chipset drivers.
The kicker here is to find out which driver might be bad and to avoid using it for time being.

* Realtek Audio Driver V6.0.1.7629 bing that or google it followed by your os version and 64bit.
As for the intel try it again, I've been hearing that driver has a problem you might have to call intel.

If all else fails, I'm going to recommend a better mobo then asus and have you get a refund for your asus board.
Let us know what happens soon.

 

[zepplin1]

Go ahead and uninstall all of drivers from control panel add and remove programs.
Once you've done that, start off with sound card drivers, next ethernet drivers, then you go for the chipset drivers.
The kicker here is to find out which driver might be bad and to avoid using it for time being.

* Realtek Audio Driver V6.0.1.7629 bing that or google it followed by your os version and 64bit.
As for the intel try it again, I've been hearing that driver has a problem you might have to call intel.

If all else fails, I'm going to recommend a better mobo then asus and have you get a refund for your asus board.
Let us know what happens soon.

So after 2 clean windows installs I finally think I have solved the problem but, will see for sure if it comes back in the next week.

On Asus's website they have a driver for the Intel Engine Management, so I downloaded that, clean installed windows and then reinstalled the drivers without using the cd from the box. Same issue occured. And on top of this I couldnt even update to the latest version of windows.

So I figured I would do another clean install but this time only install the chipset drivers and the ethernet drivers, then update to the latest windows and then continue with the rest. While looking through the updates that windows was downloading, I saw an update for Intel Engine Management. I let windows update and then did not install the driver from Asus, but instead compared versons. The windows update was a newer version of the drivers so i think i was installing the older driver from asus on top of the new microsoft one. honestly asus's support webpage sucks and has little to no information.

Lets hope it keeps working.

 

[Paul NZ]

Wait till you get any TPlink wireless adapters. Their drivers suck more than ASUS lol

Kinda of what happened with this Canon printer I have here. Before I could install the drivers from the site, but now with the latest version of Win10, they crash.

Luckily the windowsupdate drivers for it work Otherwise, I wouldnt be able to use the printer

Good thing with this is, I no longer have to connect the USB cable to install the drivers for the printer.

If I reformat again, all I have to do is go online turn the printer on, check updates install the printer drivers and it's done!

 

[maikutech]

Go ahead and uninstall all of drivers from control panel add and remove programs.
Once you've done that, start off with sound card drivers, next ethernet drivers, then you go for the chipset drivers.
The kicker here is to find out which driver might be bad and to avoid using it for time being.

* Realtek Audio Driver V6.0.1.7629 bing that or google it followed by your os version and 64bit.
As for the intel try it again, I've been hearing that driver has a problem you might have to call intel.

If all else fails, I'm going to recommend a better mobo then asus and have you get a refund for your asus board.
Let us know what happens soon.

So after 2 clean windows installs I finally think I have solved the problem but, will see for sure if it comes back in the next week.

On Asus's website they have a driver for the Intel Engine Management, so I downloaded that, clean installed windows and then reinstalled the drivers without using the cd from the box. Same issue occured. And on top of this I couldnt even update to the latest version of windows.

So I figured I would do another clean install but this time only install the chipset drivers and the ethernet drivers, then update to the latest windows and then continue with the rest. While looking through the updates that windows was downloading, I saw an update for Intel Engine Management. I let windows update and then did not install the driver from Asus, but instead compared versons. The windows update was a newer version of the drivers so i think i was installing the older driver from asus on top of the new microsoft one. honestly asus's support webpage sucks and has little to no information.

Lets hope it keeps working.

Ok then post back again next monday night, if everything remains stable don't bother it.
If it starts up again, same problem that you had, speak to intel first like I recommended.
Since its their driver, their parts on the asus board let them help, if they cannot find any resolution.
If you have enough time to repackage the board send it back to the store for a full refund.
I rather you use Gigabyte or asrock, both of those do far more better on intel platforms then asus does.

 

[zepplin1]

so problem happened again. trying to talk to asus and then will contact intel. im very sure its a driver issue, just not sure how to figure out which one

 

[Paul NZ]

And dont rely on device manager, it doesnt / wont find every driver.

It's the lazy way to do it. Go to the mobo maker's site, and see if there are any later drivers

 

[zepplin1]

And dont rely on device manager, it doesnt / wont find every driver.

It's the lazy way to do it. Go to the mobo maker's site, and see if there are any later drivers

im not using device manager to search for drivers. My drivers are updated based on ASUS and my other peripherals but device manager so far has been the only way I can tell when I am having the issue.

Just to rehash the issue. When it happens, plugging in hardware will not work. Device manager upon scanning for new hardware will go into an endless loop, I cant even close the process its just stuck. Also windows shut down and restart will not work. They will stay on the restarting or shutting down screen with the looping dots. I have done 3 clean installs with my motherboards recommended drivers downloaded from their website. I have also updated windows to the latest versions. Im out of ideas. I really just need a way to see what is triggering this issue and then figure out what to do with it.

also this is a consistent error message in the windows even log:

"The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS."

UPDATE: Im pretty sure now that this is being caused by my Saitek x52 and their shitty software. Could be wrong, but not having the issue with it uninstalled