- Joined
- Jun 20, 2007
- Messages
- 3,942 (0.60/day)
| System Name | Widow |
|---|---|
| Processor | Ryzen 7600x |
| Motherboard | AsRock B650 HDVM.2 |
| Cooling | CPU : Corsair Hydro XC7 }{ GPU: EK FC 1080 via Magicool 360 III PRO > Photon 170 (D5) |
| Memory | 32GB Gskill Flare X5 |
| Video Card(s) | GTX 1080 TI |
| Storage | Samsung 9series NVM 2TB and Rust |
| Display(s) | Predator X34P/Tempest X270OC @ 120hz / LG W3000h |
| Case | Fractal Define S [Antec Skeleton hanging in hall of fame] |
| Audio Device(s) | Asus Xonar Xense with AKG K612 cans on Monacor SA-100 |
| Power Supply | Seasonic X-850 |
| Mouse | Razer Naga 2014 |
| Software | Windows 11 Pro |
| Benchmark Scores | FFXIV ARR Benchmark 12,883 on i7 2600k 15,098 on AM5 7600x |
EDIT: Solved by reinstall
While I used media creation tool to download Win 10 again and simply reinstall over the current system - which has resolved the issue.
I did note others had a similar problem and it was something possibly of the following two:
Best of luck to all that had this issue, shame a 'reinstall' was yet again the way forward.
===================================================================
Since CU my boot time has gone from around four seconds to about a minute.
I ran Process Monitor, setup a duration filter for anything over three total seconds. It came back with a few entries, most of which were post login to Windows.
There was one however that was pre Windows and the notice was concerning:
the \\MACHINENAME*\MAILSLOT\NET\NETLOGON path fails with the result BAD NETWORK PATH.
After some searching around this seems to be either related to Active Directory authentication failing or NetBios flaking out/not being assigned to the NIC.
AD - Not using it, device is in a standard WORKGROUP home environment
NetBios - Not having any 'network' issues with the NIC, can browse, view, navigate, access local network
Other things tried:
Note that while the system is loading up(splash image and circle dots animation, I can hit the power button at any moment up until right as it boots into Windows, and it will shut the machine off. In my experience once the proper Windows boot sequence has started, a single 'power' button press would not allow it to shut off. Instead you would have to hold it for several seconds. This indicates to me that it's not actually starting Windows - as if it was doing some back ground check or disk check[though hitting any keyboard strokes does not make a difference]).
*Safe mode behaves similar with the exception that it has no spinning circle animation. At about the same elapsed time, it will load into Windows.
Again, pressing power button once during this phase, shuts off the machine.
Any thing else to check?
While I used media creation tool to download Win 10 again and simply reinstall over the current system - which has resolved the issue.
I did note others had a similar problem and it was something possibly of the following two:
- The new Windows Defender system/rollout/upgrade was always scanning at boot up
- Graphics driver had corrupted display settings causing it to revert to Windows default then reload the saved clean copy of your current third party (nvidida/AMD) version from the drive repository
Best of luck to all that had this issue, shame a 'reinstall' was yet again the way forward.
===================================================================
Since CU my boot time has gone from around four seconds to about a minute.
I ran Process Monitor, setup a duration filter for anything over three total seconds. It came back with a few entries, most of which were post login to Windows.
There was one however that was pre Windows and the notice was concerning:
the \\MACHINENAME*\MAILSLOT\NET\NETLOGON path fails with the result BAD NETWORK PATH.
After some searching around this seems to be either related to Active Directory authentication failing or NetBios flaking out/not being assigned to the NIC.
AD - Not using it, device is in a standard WORKGROUP home environment
NetBios - Not having any 'network' issues with the NIC, can browse, view, navigate, access local network
Other things tried:
- Unplugged any drives sans the primary
- Unplugged all USB devices
- Run a system start up repair
- Safe mode*
Note that while the system is loading up(splash image and circle dots animation, I can hit the power button at any moment up until right as it boots into Windows, and it will shut the machine off. In my experience once the proper Windows boot sequence has started, a single 'power' button press would not allow it to shut off. Instead you would have to hold it for several seconds. This indicates to me that it's not actually starting Windows - as if it was doing some back ground check or disk check[though hitting any keyboard strokes does not make a difference]).
*Safe mode behaves similar with the exception that it has no spinning circle animation. At about the same elapsed time, it will load into Windows.
Again, pressing power button once during this phase, shuts off the machine.
Any thing else to check?
Last edited:
