Community
cancel
Showing results for 
Search instead for 
Did you mean: 
CVans
Beginner
1,577 Views

DH87RL motherboard, Intel Desktop Utilities keep spinning

DH87RL motherboard

Intel Desktop Utilities worked fine before.

After upgrade to W8.1 the IDU program works, but i cant receive info : in the window it stays spinning : see attached file

OS is W8 pro 64 bit

I did search - download and install latest drivers and bios update regards my system, but no result : IDU window stays spinning without receiving information.

What can be the solution to this ? Or where do i need to find - correct the problem ?

If more information is needed, i gladly hear it !

Thanks in advance for any help - information.

Best Regards,

Christof Vanstaen

Tags (1)
0 Kudos
18 Replies
Allan_J_Intel1
Employee
43 Views

I am sorry to hear that have had issues with Intel Desktop Utilities.

The Intel engineering department is aware of this problem and they are currently working to get this issue resolved. I still do not have an estimate time of resolution on this matter. For additional details please check Readme file of the Intel Desktop Utilities here:

ISSUE-6

http://downloadmirror.intel.com/20488/eng/IDU_3.2.8_Readme.txt http://downloadmirror.intel.com/20488/eng/IDU_3.2.8_Readme.txt

Allan.

CVans
Beginner
43 Views

Thx Allan !

I did have hope with the new Bios update and the recent Desktop Utilities file from january 2014 this would have been covered,

so therefore my question after trying these;

i tought i did overlook something.

Is it worth to try still some differend settings ?

Or better to await a new updated program file and or Bios ?

I dont want to waste my time If there is no solution at this moment; Overal system is running Strong so no doubts there

Best Regards,

Christof Vanstaen

NSCOTT_P_Intel
Employee
43 Views

Christof,

I need to see the contents of file "C:\Program Files (x86)\Intel\FSC\FSCAppServ.log". You can post its contents here or send it to me via private message...

...Scott

CVans
Beginner
43 Views

Hi Scott,

here it is :

06/29/13 13:41:29 INFO Service Loading; Version = 1.2.3.42

06/29/13 13:41:31 INFO Service Running

06/29/13 13:45:54 INFO Service Terminated

06/29/13 13:46:16 INFO Service Loading; Version = 1.2.3.42

06/29/13 13:46:18 INFO Service Running

06/29/13 13:47:47 INFO Service Terminated

06/29/13 13:48:09 INFO Service Loading; Version = 1.2.3.42

06/29/13 13:48:10 INFO Service Running

06/29/13 14:11:47 INFO Service Terminated

06/29/13 14:12:13 INFO Service Loading; Version = 1.2.3.42

06/29/13 14:12:15 INFO Service Running

06/29/13 14:37:09 INFO Service Terminated

06/29/13 14:37:40 INFO Service Loading; Version = 1.2.3.42

06/29/13 14:37:43 INFO Service Running

06/29/13 14:37:50 INFO Service Terminated

06/29/13 14:38:15 INFO Service Loading; Version = 1.2.3.42

06/29/13 14:38:17 INFO Service Running

06/29/13 14:45:15 INFO Service Suspended

06/29/13 14:49:32 INFO Service Loading; Version = 1.2.3.42

06/29/13 14:49:35 INFO Service Running

06/29/13 14:50:47 INFO Service Suspended

06/29/13 14:52:29 INFO Service Loading; Version = 1.2.3.42

06/29/13 14:52:31 INFO Service Running

06/29/13 14:56:04 INFO Service Suspended

06/29/13 14:57:05 INFO Service Running

06/29/13 14:58:57 INFO Service Suspended

06/29/13 15:00:14 INFO Service Loading; Version = 1.2.3.42

06/29/13 15:00:17 INFO Service Running

06/29/13 15:00:53 INFO Service Loading; Version = 1.2.3.42

06/29/13 15:00:56 INFO Service Running

06/29/13 15:03:53 INFO Service Suspended

06/29/13 15:05:11 INFO Service Loading; Version = 1.2.3.42

06/29/13 15:05:14 INFO Service Running

06/29/13 15:06:17 INFO Service Suspended

06/29/13 15:56:46 INFO Service Loading; Version = 1.2.3.42

06/29/13 15:56:48 INFO Service Running

06/29/13 15:57:06 INFO Service Suspended

06/29/13 15:57:59 INFO Service Running

06/29/13 15:58:47 INFO Service Suspended

06/29/13 16:00:09 INFO Service Loading; Version = 1.2.3.42

06/29/13 16:00:11 INFO Service Running

06/29/13 16:01:45 INFO Service Suspended

06/29/13 16:48:06 INFO Service Loading; Version = 1.2.3.42

06/29/13 16:48:08 INFO Service Running

06/29/13 16:48:41 INFO Service Suspended

06/29/13 16:50:46 INFO Service Running

06/29/13 16:51:23 INFO Service Suspended

06/29/13 16:58:10 INFO Service Loading; Version = 1.2.3.42

06/29/13 16:58:12 INFO Service Running

06/29/13 16:58:44 INFO Service Suspended

06/29/13 17:00:16 INFO Service Running

06/29/13 17:01:06 INFO Service Suspended

06/29/13 17:03:22 INFO Service Loading; Version = 1.2.3.42

06/29/13 17:03:24 INFO Service Running

06/29/13 17:03:47 INFO Service Suspended

06/29/13 17:06:06 INFO Service Running

06/29/13 17:08:23 INFO Service Suspended

06/29/13 17:22:43 INFO Service Loading; Version = 1.2.3.42

06/29/13 17:22:45 INFO Service Running

06/29/13 17:24:29 INFO Service Suspended

06/29/13 17:29:09 INFO Service Loading; Version = 1.2.3.42

06/29/13 17:29:11 INFO Service Running

06/29/13 17:31:02 INFO Service Suspended

06/29/13 17:56:36 INFO Service Loading; Version = 1.2.3.42

06/29/13 17:56:38 INFO Service Running

06/29/13 17:57:06 INFO Service Suspended

06/29/13 17:59:13 INFO Service Running

06/29/13 17:59:46 INFO Service Suspended

06/29/13 18:01:57 INFO Service Running

06/29/13 18:03:30 INFO Service Suspended

06/29/13 18:08:30 INFO Service Running

06/29/13 18:11:04 INFO Service Suspended

06/29/13 18:13:40 INFO Service Running

06/29/13 18:14:36 INFO Service Suspended

07/02/13 10:01:25 INFO Service Loading; Version = 1.2.3.42

07/02/13 10:01:27 INFO Service Running

07/02/13 10:03:10 INFO Service Suspended

07/02/13 11:08:36 INFO Service Loading; Version = 1.2.3.42

07/02/13 11:08:38 INFO Service Running

07/02/13 11:12:10 INFO Service Suspended

07/02/13 11:14:34 INFO Service Running

07/02/13 11:14:45 INFO Service Suspended

07/02/13 11:15:48 INFO Service Running

07/02/13 11:18:24 INFO Service Suspended

07/02/13 14:44:56 INFO Service Loading; Version = 1.2.3.42

07/02/13 14:45:00 INFO Service Running

07/02/13 14:55:01 INFO Service Suspended

07/02/13 16:51:29 INFO Service Running

07/02/13 16:51:39 INFO Service Suspended

07/02/13 19:30:14 INFO Service Loading; Version = 1.2.3.42

07/02/13 19:30:18 INFO Service Running

07/02/13 19:32:18 INFO Service Suspended

07/02/13 20:33:46 INFO Service Running

07/02/13 20:34:58 INFO Service Suspended

07/03/13 09:31:26 INFO Service Loading; Version = 1.2.3.42

07/03/13 09:31:29 INFO Service Running

07/03/13 09:35:51 INFO Service Suspended

07/03/13 09:46:07 INFO Service Loading; Version = 1.2.3.42

07/03/13 09:46:10 INFO Service Running

07/03/13 09:46:31 INFO Service Suspended

07/03/13 19:04:46 INFO Service Loading; Version = 1.2.3.42

07/03/13 19:04:49 INFO Service Running

07/03/13 20:00:09 INFO Service Suspended

07/03/13 21:00:46 INFO Service Running

07/03/13 21:31:45 INFO Service Suspended

07/03/13 23:24:29 INFO Service Running

07/03/13 23:49:55 INFO Service Suspended

07/04/13 07:28:28 INFO Service Running

07/04/13 07:38:44 INFO Service Suspended

07/26/13 21:43:05 INFO Service Loading; Version = 1.2.3.42

07/26/13 21:43:08 INFO Service Running

07/26/13 21:54:08 INFO Service Terminated

07/26/13 21:54:35 INFO Service Loading; Version = 1.2.3.42

07/26/13 21:54:41 INFO Service Running

07/26/13 21:59:43 INFO Service Terminated

07/26/13 22:00:10 INFO Service Loading; Version = 1.2.3.42

07/26/13 22:00:12 INFO Service Running

07/26/13 22:12:38 INFO Service Terminated

07/26/13 22:13:04 INFO Service Loading; Version = 1.2.3.42

07/26/13 22:13:08 INFO Service Running

07/26/13 22:48:53 INFO Service Loading; Version = 1.2.3.42

07/26/13 22:48:55 INFO Service Running

07/26/13 23:38:00 INFO Service Suspended

07/27/13 10:17:34 INFO Service Running

07/27/13 15:02:37 INFO Service Suspended

07/27/13 18:26:28 INFO Service Loading; Version = 1.2.3.42

07/27/13 18:26:30 INFO Service Running

07/27/13 18:42:17 INFO Service Suspended

07/27/13 19:04:13 INFO Service Loading; Version = 1.2.3.42

07/27/13 19:04:15 INFO Service Running

07/27/13 21:45:39 INFO Service Suspended

07/27/13 21:47:51 INFO Service Running

07/27/13 21:50:48 INFO Service Suspended

08/17/13 13:25:33 INFO Service Loading; Version = 1.2.3.42

08/17/13 13:25:35 INFO Service Running

08/17/13 15:41:46 INFO Service Suspended

08/18/13 14:52:12 INFO Service Loading; Version = 1.2.3.42

08/18/13 14:52:15 INFO Service Running

08/18/13 15:58:10 INFO Service Suspended

08/19/13 21:18:03 INFO Service Running

08/19/13 22:51:47 INFO Service Suspended

08/20/13 12:34:23 INFO Service Running

08/20/13 23:54:35 INFO Service Suspended

08/21/13 09:21:48 INFO Service Running

<p...
NSCOTT_P_Intel
Employee
43 Views

Christof,

The log file is telling me that our background monitoring service is suffering a GP fault. It started happening on October 20th (presumably the point where you upgraded to Windows 8). This was with IDU version 3.2.6/3.2.7 (which used the same version of the background monitoring service), but continued to happen after you installed IDU version 3.2.8 on February 4th.

We set up a RL board, installed Windows 8.1 and all standard drivers and then installed IDU version 3.2.8. We are seeing no failures. This means that there is something in a bad state as a result of the Windows 7 to Windows 8 upgrade (my personal rule: as painful as it is reinstalling everything, do so; *never* upgrade), or there is something else that needs to be included in the picture in order for us to see the problem occur...

To look into the latter case, I need some more information regarding your configuration and what (else) you have installed. What additional hardware to you have installed? How do you have the BIOS configured? For example, did you use legacy boot or did you use UEFI? Did you secure Windows 8.1? Do you use RAID or SSD caching? If not, did you install the RST driver anyway? If so, what version of RST did you use? What other major software packages and drivers do you have installed?

Thanks in advance,

...Scott

CVans
Beginner
43 Views

Hi Scott,

this system what is brand new from somewhere june 2013 is original installed with Windows 8 pro, so no upgrade there

Around that 20 october i did install the Windows 8.1 pro Upgrade, sadly i did not directly notice that IDU was not working anymore

These just for clarification.

Further i did not install any new hardware between now and then, system did stay the same

Also no real major software packages i did change or install between now and then, or drivers,

only the last days the updated files from Intel, and all windows updates to date.

UEFI Boot is used ( never changed settings there )

Further i guess you can have alot with this System Report file from the RST software :

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

System Report

System Information

OS name: Microsoft Windows 8.1 Pro

OS version: 6.3.9600 9200

System name: HUISKAMER-PC

System manufacturer: INTEL_

System model: DH87RL__

Processor: GenuineIntel Intel64 Family 6 Model 60 Stepping 3 3.401 GHz

BIOS: Intel Corp., RLH8710H.86A.0323.2013.1204.1726

Intel® Rapid Storage Technology enterprise Information

User interface version: 12.0.0.1083

Language: English (United States)

Driver version: 12.0.0.1082

ISDI version: 12.0.0.1083

Storage System Information

Controller name: Intel(R) 8 Series/C220 Chipset Family SATA AHCI Controller

Type: SATA

Mode: AHCI

Number of SATA ports: 4

Number of volumes: 0

Number of spares: 0

Number of available disks: 3

Rebuild on Hot Plug: Disabled

Manufacturer: 32902

Model number: 35842

Product revision: 4

Direct attached disk: 130740406595

Direct attached disk: WD-WCC1U0652178

Direct attached disk: WD-WCC1U1333114

Disk on Controller 0, Port 0

Status: Normal

Type: SATA SSD

Location type: Internal

Size: 119 GB

System disk: Yes

Disk data cache: Enabled

Command queuing: NCQ

SATA transfer rate: 3 Gb/s

Model: SanDisk SDSSDH2128G

Serial number: 130740406595

SCSI device ID: 0

Firmware: X211200

Physical sector size: 512 Bytes

Logical sector size: 512 Bytes

Disk on Controller 0, Port 1

Status: Normal

Type: SATA disk

Location type: Internal

Size: 932 GB

System disk: No

Disk data cache: Enabled

Command queuing: NCQ

SATA transfer rate: 6 Gb/s

Model: WDC WD10EFRX-68JCSN0

Serial number: WD-WCC1U0652178

SCSI device ID: 1

Firmware: 01.01A01

Physical sector size: 4096 Bytes

Logical sector size: 512 Bytes

Disk on Controller 0, Port 2

Status: Normal

Type: SATA disk

Location type: Internal

Size: 932 GB

System disk: No

Disk data cache: Enabled

Command queuing: NCQ

SATA transfer rate: 6 Gb/s

Model: WDC WD10EZRX-00A8LB0

Serial number: WD-WCC1U1333114

SCSI device ID: 2

Firmware: 01.01A01

Physical sector size: 4096 Bytes

Logical sector size: 512 Bytes

ATAPI device on Controller 0, Port 4

Location type: Internal

SATA transfer rate: 1.5 Gb/s

Model: TSSTcorp CDDVDW SH-224BB

Serial number: R8WS68ECC047VY

Firmware: SB00

Besides this, i also did take a print screen from the installed Intel Software :

The option Secure boot in the Bios i did select off today ( was On ), to see if IDU would work regards that, but no luck

If anything else is needed, i gladly hear it.

Thx again !

Best Regards,

Christof

NSCOTT_P_Intel
Employee
43 Views

Christof,

The latest version of RST posted is 12.8.0.1016. You have only 12.0.0.1083 installed. Try installing the newer release and see if this helps (it is the only thing that I see different)...

...Scott

CVans
Beginner
43 Views

Hi Scott,

thx for pointing this out to me !

I did upgrade RST to the latest version and did a reboot a couple of times,

but No luck, IDU stays spinning in his window

Not sure what changed from Windows 8 pro to 8.1 to make this occur,

time will tell i guess what solution will pop up.

It still confuses me

Best Regards,

Christof

NSCOTT_P_Intel
Employee
43 Views

Christov,

Do the following:

  1. Run Regedit.
  2. Navigate to "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Intel\Desktop Board\Aux Sensors" (Note for others: equivalent for 32-bit Windows installs is "HKEY_LOCAL_MACHINE\SOFTWARE\Intel\Desktop Board\Aux Sensors").
  3. Double-click on item "Monitor S.M.A.R.T." and change value from "TRUE" to "FALSE".
  4. Close Regedit.
  5. Reboot.

If the issue is related to RST access, this will stop it from occurring. IDU will work, but (unfortunately) it will not monitor the temperatures of any HDDs or SSDs.

...Scott

CVans
Beginner
43 Views

Hello Scott,

I did all steps above and did change the value to FALSE,

did reboot : no Luck regards IDU sadly

Now running the PC a day or 2 like this, and did check regular when fresh start occurs, stays spinning

Do i put the value again on TRUE ?

Best Regards,

Christof

NSCOTT_P_Intel
Employee
43 Views

Christof,

Ok, this means that the issue is not with the RST support. You can put the value of "Monitor S.M.A.R.T." back to TRUE if you wish. There are two other things you can try. First, symbol "Monitor TSOD" controls whether any attempts are made to extract temperatures from the Memory DIMMs (via Thermal-Sensor-On-DIMM device). Second, symbol "Monitor DTS" controls whether any attempts are made to extract Processor Core temperatures. See if setting either of these to FALSE fixes the issue for you...

...Scott

CVans
Beginner
43 Views

Scott,

Thank you !

I did put the value for "Monitor S.M.A.R.T." back to TRUE and Changed the "Monitor TSOD" value to FALSE,

did a reboot and IDU works Perfect now, and if i am not mistaken : complete !

Can i ask why these changes make it work now ?

Or better : what is the exact problem why IDU did keep spinning in W8.1 Upgrade, and with this setting to FALSE have a 100% operation ?

And side question : if a future update will roll out from INTEL or Microsoft that normaly would take care of these, do i better change value then back to TRUE ? Or do i not need to follow this up and can leave it on FALSE ?

Thanks again for the support in this !

Best Regards,

Christof

NSCOTT_P_Intel
Employee
43 Views

Christof,

The "Monitor TSOD" flag enables support for the enumeration and monitoring of DIMM (and SODIMM) temperatures (via Thermal Sensor On DIMM (TSOD) devices). These are very common on ECC DIMMs for Workstation- and Server-class machines but not so much in Mobile- and Desktop-class machines. In mainstream, folks just aren't willing to pay the premium for the feature. I am - and I do - and that's why I included support for this feature in IDU. For you, unless you plan to pay the premium for TSOD-enabled DIMMs so you have these extra sensors, you can just leave this flag set to FALSE (which disables the feature completely).

As for why this feature is causing this problem, I am unsure. I haven't been able to reproduce the problem and can't debug it until I do. If I was to hazard a guess, I would say that our SMBus driver has been mucked up by the Windows Upgrade process (you communicate with the TSOD device on each DIMM over SMBus). For most users with 6-, 7- and 8-Series Intel® Desktop Boards, the TSOD feature is the only one that requires SMBus access, so this is not so big an issue for them. For those folks with X79-based Intel® Desktop Boards (DX79SI, DX79TO or DX79SR), however, they need the SMBus support working to allow monitoring of the temperature and voltage sensors in the enhanced Voltage Regulation circuitry, so I will need to sort this out...

...Scott

CVans
Beginner
43 Views

When i need to upgrade my memory in the Future, I will think about you

Thanks again for the support and detailed answers, Intel Rocks !

Best Regards,

Christof

NSCOTT_P_Intel
Employee
43 Views

Christof,

When we attempted to reproduce your issue, our results differed from yours. Instead of the FSCAppServ Service suffering the GP Fault, we saw an error message indicating a problem during DIMM monitoring initialization. The Service recovered from this error and continued to run, allowing IDU to run properly as well. On a lark (ok, call it an educated guess on my part), we then tried manually running the SMBus driver installer. After the reboot, no errors occurred and there were no issues with IDU operation.

This tells us that the Win8 to Win8.1 upgrade definitely screwed up the SMBus driver installation. If you have some time, we would like you to try an experiment for us:

  1. Unzip the IDU 3.2.8 installation package again.
  2. Double-click on the Setup.exe file in the SMBus subfolder (this will run the SMBus driver installer manually).
  3. Click through and complete the driver install. When it asks you to reboot at the end, do not do so.
  4. Go into REGEDIT and reset the "Monitor TSOD" parameter to "TRUE".
  5. Reboot.

If IDU runs properly after the reboot, we will know that the manual install of the SMBus driver fixed whatever was screwed up. If it doesn't, you can reset the parameter to "FALSE" again and be where you were...

Thanks in advance,

...Scott

CVans
Beginner
43 Views

Hi Scott,

did try out what you asked : and I can confirm :

IDU works Perfect After manually SMBus driver install, and setting of Monitor TSOD back to "TRUE" ,and of course reboot

So, a positive test !

I think i keep it this way :-)

Best Regards,

Christof

CVans
Beginner
43 Views

I can confirm Now I did Upgrade to Windows 10 : same Procedure needed like After the Upgrade to 8.1

Intel Desktop Utilities was again out of order After the Update to Windows 10 ( keeps spinning ) > did the procudure like above in reply 15. > All Perfect again !

Hopefully others read this, so they can bring a solution to There system :-)

Best Regards,

Christof

n_scott_pearson
Super User Retired Employee
43 Views

Yes, alas, Microsoft's Windows upgrade tool is chucking this driver because it is not on the compatibility list. After doing an upgrade, you will need to reinstall the SMBus driver...

...Scott

(This is the same Scott responding. I am on an external account now that I have retired)