I think that was just a bug with the monitor or something. I have felt the air from the radiator being. Quite warm at other times and that was with temp less than 60c. It has to be just a bug because it hasn't done it since or before the reported time. I'll have a quick check of that tnite aswell but I'm doubtful there is anything wrong there. I have even ran stress tests on this thing that had my temp not go higher than 65c.
24 seconds to log in to windows 10?
- Thread starter D1craig
- Start date
im guna stick it near the root. where is the root lol? sounds easier than the usb option.
im guna stick it near the root. where is the root lol? sounds easier than the usb option.
yeah, 24 seconds isn't much at all. These days the mobo POST procedure takes longer than windows loading.
Make sure it's not old hardware and has a sata 3 socket.
Root of a windows drive e.g. c:\
Makes it easier to find, and avoids nonsense bugs of old flashers that couldn't handle spaces in file paths.
it was a one off that seems to have been a bug in the temp reading stuff. nothing on the computer suggests them temps where correct. ive stress tested for over an hour and it doesnt pass 53C, ive performed the actions i was performing when it read those temps and it goes no where near 60C.
Ok back to the main point of the thread.
Since putting all my watercooling in the computer I have noticed that this doesn't happen all the time now. Maybe 1 in 3 times its logs into windows as quick as you would expect.
I didn't get around to updating the BIOS. Lot software info suggests it's really dangerous to update BIOS so I was worried. I Will get around to it soon though. Before putting it under water I never once noticed it log in as fast as would be expected.
Since putting all my watercooling in the computer I have noticed that this doesn't happen all the time now. Maybe 1 in 3 times its logs into windows as quick as you would expect.
I didn't get around to updating the BIOS. Lot software info suggests it's really dangerous to update BIOS so I was worried. I Will get around to it soon though. Before putting it under water I never once noticed it log in as fast as would be expected.
It's really easy to update it safely from within the BIOS, it's under the last tab where you save and exit, you launch the flashing tool and have a fat32 usb stick on hand with the new bios on it.
P.s the danger is no less than fitting a watercooling solution in your system so you needn't fret about it, just download the correct Bios from Gigabyte's website: http://www.gigabyte.com/products/product-page.aspx?pid=5529#bios
I've updated the Bios. Nothing has changed. It still does it. It has grown to every single time now.
Had to install my ethernet drivers last night, didn't realise I had been using just wifi for a while and noticed I didn't have them installed. This problem stopped the next time I logged in but after that it persisted.
Had to install my ethernet drivers last night, didn't realise I had been using just wifi for a while and noticed I didn't have them installed. This problem stopped the next time I logged in but after that it persisted.
So this happened to me again this morning although it didn't occur yesterday.
The 1st item for today under the following section in Event Viewer is;
Windows Logs>Application
Time: 11:50:58, Level: Error, Source: ATIeRecord, General Details: ATI EEU Service event error, Event ID: 16387
Time: 11:51:11, Level: Information, Source: Security-SPP, General Details: Successfully scheduled Software Protection service for re-start at 2116-05-21T10:51:11Z. Reason: RulesEngine, Event ID: 16384
Time: 11:51:11, Level: Information, Source: Security-SPP, General Details: The Software Protection service has stopped, Event ID: 903
I then get 4 identical entries that correspond to the time of Winlogon with the following details;
Time: 11:51:28, Level: Information, Source: igfxCUIService1.0.0.0, General Details: The description for Event ID 0 from source igfxCUIService1.0.0.0 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted, Event ID: 0
Windows Logs>System
Time: 11:50:56, Level: Information, Source: Kernel-General, General Details: The system time has changed to 2016-06-14T10:50:56.500000000Z from 2016-06-13T20:34:28.293110300Z. Change Reason: System time synchronized with the hardware clock, Event ID: 1
Time: 11:50:56, Level: Warning, Source: e1cexpress, General Details: Network link is disconnected, Event ID: 27
Time: 11:50:57, Level: Information, Source: Kernel-Boot, General Details: The firmware reported boot metrics, Event ID: 30
Time: 11:50:57, Level: Information, Source: Kernel-Boot, General Details: There are 0x1 boot options on this system, Event ID: 18
Time: 11:50:57, Level: Information, Source: Kernel-Boot, General Details: The bootmgr spent 0ms waiting for user input, Event ID: 32
Time: 11:50:57, Level: Information, Source: Kernel-Boot, General Details: The boot menu policy was 0x1, Event ID: 25
Time: 11:50:57, Level: Information, Source: Kernel-Boot, General Details: The boot type was 0x1, Event ID: 27
Time: 11:50:57, Level: Information, Source: BTHUSB, General Details: Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during start-up, Event ID: 18
Time: 11:50:59, Level: Information, Source: Power-Troubleshooter, General Details: The system has returned from a low power state. Sleep Time: 2016-06-13T20:34:26.510994400Z Wake Time: 2016-06-14T10:50:57.079550500Z Wake Source: Unknown, Event ID: 1
Time: 11:51:00, Level: Information, Source: e1cexpress, General Details: Network link has been established at 1Gbps full duplex, Event ID: 32
<Here is where I think the delay occurs in processing the login credentials>
Time: 11:51:28, Level: Information, Source: Winlogon, General Details: User Log-on Notification for Customer Experience Improvement Program, Event ID: 7001
So my thoughts are these which I wonder if someone more knowledgeable is able to shed some light on please:
Is the ATIeRecord source something to do with my AMD drivers, perhaps this is trying to ping home to check for updated drivers but can't at that time because the network link is down?
Is this just a symptom of using a Microsoft Account to login as it doesn't occur every time so I'm wondering is it connected to handshaking with Microsoft's servers?
Now there are also some networking options in the BIOS but I have never enabled them as I thought these were for non Windows OS purposes. I shall have to check on the BIOS options and report back on these.
I don't have integrated graphics enabled in the BIOS but Win10 did do a driver update relating to this a couple of weeks ago. It may have removed my AMD driver too but I have since reinstalled that as there was a more up to date driver available.
I also have secure and fast boot enabled, unsure if these could be related to the issue.
The 1st item for today under the following section in Event Viewer is;
Windows Logs>Application
Time: 11:50:58, Level: Error, Source: ATIeRecord, General Details: ATI EEU Service event error, Event ID: 16387
Time: 11:51:11, Level: Information, Source: Security-SPP, General Details: Successfully scheduled Software Protection service for re-start at 2116-05-21T10:51:11Z. Reason: RulesEngine, Event ID: 16384
Time: 11:51:11, Level: Information, Source: Security-SPP, General Details: The Software Protection service has stopped, Event ID: 903
I then get 4 identical entries that correspond to the time of Winlogon with the following details;
Time: 11:51:28, Level: Information, Source: igfxCUIService1.0.0.0, General Details: The description for Event ID 0 from source igfxCUIService1.0.0.0 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted, Event ID: 0
Windows Logs>System
Time: 11:50:56, Level: Information, Source: Kernel-General, General Details: The system time has changed to 2016-06-14T10:50:56.500000000Z from 2016-06-13T20:34:28.293110300Z. Change Reason: System time synchronized with the hardware clock, Event ID: 1
Time: 11:50:56, Level: Warning, Source: e1cexpress, General Details: Network link is disconnected, Event ID: 27
Time: 11:50:57, Level: Information, Source: Kernel-Boot, General Details: The firmware reported boot metrics, Event ID: 30
Time: 11:50:57, Level: Information, Source: Kernel-Boot, General Details: There are 0x1 boot options on this system, Event ID: 18
Time: 11:50:57, Level: Information, Source: Kernel-Boot, General Details: The bootmgr spent 0ms waiting for user input, Event ID: 32
Time: 11:50:57, Level: Information, Source: Kernel-Boot, General Details: The boot menu policy was 0x1, Event ID: 25
Time: 11:50:57, Level: Information, Source: Kernel-Boot, General Details: The boot type was 0x1, Event ID: 27
Time: 11:50:57, Level: Information, Source: BTHUSB, General Details: Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during start-up, Event ID: 18
Time: 11:50:59, Level: Information, Source: Power-Troubleshooter, General Details: The system has returned from a low power state. Sleep Time: 2016-06-13T20:34:26.510994400Z Wake Time: 2016-06-14T10:50:57.079550500Z Wake Source: Unknown, Event ID: 1
Time: 11:51:00, Level: Information, Source: e1cexpress, General Details: Network link has been established at 1Gbps full duplex, Event ID: 32
<Here is where I think the delay occurs in processing the login credentials>
Time: 11:51:28, Level: Information, Source: Winlogon, General Details: User Log-on Notification for Customer Experience Improvement Program, Event ID: 7001
So my thoughts are these which I wonder if someone more knowledgeable is able to shed some light on please:
Is the ATIeRecord source something to do with my AMD drivers, perhaps this is trying to ping home to check for updated drivers but can't at that time because the network link is down?
Is this just a symptom of using a Microsoft Account to login as it doesn't occur every time so I'm wondering is it connected to handshaking with Microsoft's servers?
Now there are also some networking options in the BIOS but I have never enabled them as I thought these were for non Windows OS purposes. I shall have to check on the BIOS options and report back on these.
I don't have integrated graphics enabled in the BIOS but Win10 did do a driver update relating to this a couple of weeks ago. It may have removed my AMD driver too but I have since reinstalled that as there was a more up to date driver available.
I also have secure and fast boot enabled, unsure if these could be related to the issue.
Last edited:
