Service Control manager 4007

xxx123 said:

[FONT="]PC:[/FONT]
[FONT="]108500K stock 4800mhz[/FONT]
[FONT="]2x16GB DDR4 GSKILL 3000 XMP[/FONT]
[FONT="]Aorus Z490 Pro Ax[/FONT]
[FONT="]Rtx Gigabyte 3090 Gaming OC ( stock )[/FONT]
[FONT="]Seasonic Tx-850 Prime Titanium[/FONT]

[FONT="]Windows 10 up to date[/FONT]
[FONT="]newest drivers[/FONT]


[FONT="]Hey guys again. ). I have a question. I left for 2 hours Quake 2 with RTX settings on 1440P. No crashing,stable,no drops,perfect. But after i quit i check event logs and 10 logs appeared:[/FONT]
[FONT="]service control manager 7040 service was changed.[/FONT]

[FONT="]Game was running only. I dont open any apps etc. That logs just appeared during when game was on.[/FONT]
[FONT="]service control manager 7040 <maybe 8-10 logs>[/FONT]


Its fine no reason to worry?

It's probably OK. Error 7040 just means that a Service "changed" from one setting to another.

Services can generally have four settings...
Disabled, Manual, Automatic, and Automatic (delayed start).

Quake is probably changing a Service from Manual to Auto. Many Services stay on Manual and only "turn on" when needed.



Here is a list of the Services configurations. On the right, down a bit you'll see a show/hide button.
Click that and turn OFF the "Surface" columns (two of them), so you can see ALL the Windows columns.

Black Viper’s Windows 10 Service Configurations – Black Viper | www.blackviper.com



In Event Viewer, you also need to see what "type" the error is... Critical, Error, Warning, or Information.

The ones in Information, you can usually disregard. In fact... in Windows 10 Event Viewer, you can disregard most everything. Especially, if it isn't causing "other" problems like... BSODs or sudden freezing or reboots... etc.



The Windows 10 Event Viewer has serious anxiety issues.

xxx123 said:

I replayed again Quake 2 rtx for 2 hours. This time no entries Service Control manager 7040. So i guess it was nothing wrong when that 8-10 entries happened before?

Just to check things out... open a command prompt as admin, and run these two commands, one at a time...

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth



Reboot the computer a few times, and when you're convinced it's not going to explode, clear the event viewer.
That way you'll only see the current entries, going forward.

Use Option One, here: Clear All Event Logs in Event Viewer in Windows







TIP:

Always view Event Viewer via Event Viewer (local)... RED dot (upper left).
THEN, in the center section you will see the Event ID "type". I just cleared my Event Viewer, and then rebooted.

As you can see, there are 7 Information entries and nothing else.
Windows 10 Event Viewer is fairly scary looking if it hasn't been cleared in a while.

xxx123 said:

Oki so that entries it was just INFORMATION and nothing wrong?

99% of the time you can ignore Information entries.
The higher up the list you go... the more you should worry. Keeping in mind that Event Viewer is just there to help you identify a problem you are having.
If the computer is running fine, and sfc /scannow comes up clean, you're pretty much... OK.


Now IF you start getting BSODs, lockups, freezing, reboots for no reason, etc., then you can check Event Viewer.

Follow the 1st troubleshooting rule: If it ain't broke, don't fix it.





On a side note... if you want to "light up" someone's "Notification" thing at the top of the screen...
...either quote their post, or type their account name with an @ symbol in front.

Like @xxx123