New
#1
Can't pinpoint what prevents boot in normal non safe mode.
Greetings.
I'm currently stumped by my Dell Studio XPS 8100's sudden refusal to launch Win10 outside from safe mode.
The computer seems to boot fine, no error messages, the Dell splashscreen appears and goes, the stylized window of Windows appears above the circling white dots, then disappears aswell. Normal so far. Then I get a fully black screen, with perpetually circling white dots, and, after a few seconds, no audible disk access either. And so it stays. Dark. Spinning dots. Forever. The only way to reach the Windows OS is through safe mode.
I've been checking the Administration Tool's Event Viewer. All seems fine, except for :
"WARNING - Broadcom NetLink (TM) Gigabit Ethernet: The network link is down. Check to make sure the network cable is properly connected."
Followed with :
"WARNING - Un filtre TDI (\Driver\networx) a ete detect. Ce filtre n'a pas ete certifie par Microsoft et peut provoquer une instabilite du systeme."
(Yeah, french, sorry. Translatable as "A TDI filter has been detected. This filter hasn't been certified by Microsoft and may provoke a system instability".)
[Edited out, thanks NavyLCDR]
Followed with :
"ERROR - Le service LSM est en attente de demarrage."
(The LSM service is awaiting startup.)
Followed with three times :
"WARNING - Le chargement du pilote \Driver\WudfRd a echoue pour le peripherique SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Generic-&Prod_MS#MS-Pro&Rev_1.03#18E391066476&3#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}."
(The driver \Driver\WudfRd has failed to load up for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Generic-&Prod_MS#MS-Pro&Rev_1.03#18E391066476&3#{53f56307-b6bf-11d0-94f2-00a0c91efb8b})
Followed with :
"WARNING - Le service NetTcpActivator depend du service NetTcpPortSharing qui n'a pas pu demarrer en raison de l'erreur : Le service ne peut pas etre demarre parce qu'il est desactive ou qu'aucun peripherique active ne lui est associe."
(The NetTcpActivator service depends on the NetTcpPortSharing service which hasn't been able to start due to the error : The service cannot be started because it is deactivated and no activated device is associated to it.)
Followed with the two lasts infos, which aren't warnings nor errors, and just claim that
- The Windows activation service process (WAS) has started in "classic" mode using "ConfigurationSystem"
- The following system start drivers couldn't load : dam EhStorClass
And from there on, no further activity, no further entry, until I manually restart the computer (by maintaining the desktop's power button down for a couple minutes).
So, here is what I have attempted in the course of these last three days, apart from the occasional CCleaner and the disabling of all startup programs :
1) Launched an "sfc /scannnow" in safe mode, which has noticed no problem at all.
2) Launched a DISM in safe mode, no problem spotted there either.
3) Launched a "CHKDSK /f /r", which did hang for a long while at 22%, but didn't report any problem at the end.
4) Lenghtly hecked the whole system, including both HD, through Dell's pre-boot tools (F12). All tests passed, no error.
5) Attempted a Diagnosis and Repair through a WIN10 bootable DVD. No effect.
6) Attempted to restore all my three "restoration points", all failed.
7) Checked for virus and malware. None.
8) Used the safe mode command panel for a "bootrec.exe /rebuildbcd", a "bootrec.exe /fixmbr" and a "bootrec.exe /fixboot". Didn't change a thing.
9) Flailed my arms while spinning four times on my chair. Didn't help.
The safe mode functions flawlessly. But it's the only mode that functions. I have no idea if a silent driver update triggered the issue, but it didn't happen on a windows update day (wednesdays or thursdays, right), nor on a day whre I updated, installed, uninstalled anything.
So, the mystery is pretty opaque to me. Can any sleuth around here suggest another angle of investigation ?
Last edited by Cog; 08 Mar 2017 at 13:22. Reason: Oh god the layout