After last week' update I started seeing a lot of "The start type of the Windows Modules Installer service was changed from auto start to demand start." Even ID 7040 in my system event log.
It triggers when laptop is idle (win 8 pro 64 bit), the CPU usage goes to 30% and higher and the event log gets pounded with the above messages.
Type DDR3 Size 8192 MBytes DRAM Frequency 532.3 MHz
Graphics Card(s)
ATI AMD Radeon HD 7310 Graphics
Sound Card
AMD High Definition Audio Device Realtek High Definition Audio USB Audio Device
Monitor(s) Displays
Name 1950W on AMD Radeon HD 7310 Graphics Current Resolution 1366x768 pixels Work Resolution 1366x76
Screen Resolution
Current Resolution 1366x768 pixels Work Resolution 1366x768 pixels
Hard Drives
AMD K140
Cores 2
Threads 2
Name AMD K140
Package Socket FT1 BGA
Technology 40nm
Specification AMD E1-1200 APU with Radeon HD Graphics
Family F
Extended Family 14
Model 2
Extended Model 2
Stepping 0
Revision ON-C0
Instruction
Thanks for reply. Now I'm noticing different stages of 7040
The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.
The start type of the Windows Modules Installer service was changed from demand start to auto start.
The start type of the Windows Modules Installer service was changed from auto start to demand start.
The start type of the Windows Modules Installer service was changed from demand start to auto start.
The start type of the Windows Modules Installer service was changed from auto start to demand start.
Type DDR3 Size 8192 MBytes DRAM Frequency 532.3 MHz
Graphics Card(s)
ATI AMD Radeon HD 7310 Graphics
Sound Card
AMD High Definition Audio Device Realtek High Definition Audio USB Audio Device
Monitor(s) Displays
Name 1950W on AMD Radeon HD 7310 Graphics Current Resolution 1366x768 pixels Work Resolution 1366x76
Screen Resolution
Current Resolution 1366x768 pixels Work Resolution 1366x768 pixels
Hard Drives
AMD K140
Cores 2
Threads 2
Name AMD K140
Package Socket FT1 BGA
Technology 40nm
Specification AMD E1-1200 APU with Radeon HD Graphics
Family F
Extended Family 14
Model 2
Extended Model 2
Stepping 0
Revision ON-C0
Instruction
Asus M2N-MX SE Plus § DualCore AMD Athlon 64 X2, 2300 MHz (11.5 x 200) 4400+ § Corsair Value Select
CPU
AMD 4400+/4200+
Motherboard
Asus M2N-MX SE Plus/Asus A8M2N-LA (NodusM)
Memory
2 GB/3GB
Graphics Card(s)
GeForce 8400 GS/GeForce 210
Sound Card
nVIDIA GT218 - High Definition Audio Controller
Monitor(s) Displays
Hitachi 40" LCD HDTV
Screen Resolution
"1842 x 1036"
Hard Drives
WDC WD50 00AAKS-007AA SCSI Disk Device
ST1000DL 002-9TT153 SCSI Disk Device
WDC WD3200AAJB-00J3A0 ATA Device
WDC WD32 WD-WCAPZ2942630 USB Device
WD My Book 1140 USB Device
PSU
Works 550w
Case
MSI "M-Box"
Cooling
Water Cooled
Keyboard
Dell Keyboard
Mouse
Microsoft Intellimouse
Internet Speed
Cable Medium Speed
Browser
Chrome/IE 10
Antivirus
Eset NOD32 6.x/Win Defend
Other Info
Recently lost my Windows 8 on my main PC, had to go back to Windows 7.
yep it is manual. it seems i had some issues with the Windows Update. I had ran 'Fix problems with windows update' and it reported 2 issues it managed to fix. now when idle, laptop doesn't get into Windows Update hog.
I'm still perplexed why this service utlilizes CPU with 100%, it is just beyond me. Properly designed OS should not peg CPUs to 100% during idle periods, period.
resolved the issue. it looks it had to do with the Logitech wireless mouse (M185) driver. Module service and system service consumed 60% and above of the CPU when in idle state. Windows 8 should really have a means of isolating bad behaving drivers or at least some way of recognizing the situation and providing the feedback. i know ddk provides utilities for troubleshooting system issues, however people with linux (or similar) background wouldn't want to deal with windows at that level.