New
#31
Normally Safe Mode with Networking would support an internet connection- but depends on devices and drivers. Remember many drivers are not loaded in Safe Mode.
Windows 10 Random Reboot Loop before and after Update version 1909
-
-
New #32
I went into MSConfig and ticked Load System Services and now I have access to the internet again. Just another question, when I leave this going overnight the power settings of the PC will put the PC to sleep if there is no activity in that hour, should I take the Power Settings off so that it doesn't go to sleep?
Another question is what settings should I turn on or off in msconfig? If any. But as I look at the PC now it looks like it is in normal mode, not safe mode. I'm not sure about this so I thought I'd ask?
Thanks
I'm going to log out now.
-
New #33
A useful little program isso that it doesn't go to sleep?
Don't Sleep 6.22 Prevent Shutdown, Stand By, Turn Off, Restart
-
New #34
24 hours Safe Mode
I've just run 24 hours on Safe Mode between 3:00pm 9th Feb 2020 and 3:00pm 10th Feb 2020. Subsequently I ran Event Viewer and filtered for Error Codes 1074, 6006 and 6008 for between the times as above. I've attached the image of results below. I hope that helps. I just want to say thank you Dalchina for sticking with me through this problem, I hope we are getting close to finding an answer(s).
Last edited by ozdave; 09 Feb 2020 at 23:59.
-
New #35
Sounds as if it's not RAM, disk, PSU or over-heating.
Suggest you try a clean boot and run for 'long enough'
Then time for Driver Verifier.. #25.
-
New #36
I'm frightened to ask how long "long enough" is? I'm not sure that the PSU has been ruled out yet? I was going to get my Multi-Meter out tomorrow and see if I can find something. I haven't created a bootable USB in case a restoration is needed, which reminds me, I haven't done it before but I'll follow the tutorial on setting a Restore Point. I'm just checking through your original list Dalchina to see if there is anything else I've overlooked.
In #12 Basics you have chkdsk c:\scan is that command for PowerShell? Or from command prompt? I think that is about all. I still haven't done that search in TenForums for "Windows 10 random restart". I'll do that now and see what results I get. I ran a query and it brought up a lot of threads. Plenty to read there.
-
New #37
Hi, you said you'd run it in Safe Mode for a long time without a crash- whilst not definitive (think coincidence, loading) if that was much longer than the typical time to crash, it suggests no basic PSU issue.
chkdsk: #12 said
If ok from an admin command or Powershell prompt run
chkdsk c: /scan
and report the summary result.
Clean boot - 'long enough' is a matter for you- compared to the time to wait for a crash.
Then there's driver verifier.
-
New #38
Hi Dalchina, you said that whilst not definitive (think coincidence, loading). I'm not sure what you mean there.
I'll need to run through the tutorials for chkdsk and Powershell, I'm certainly getting exposed to new learnings for me, that is really great as far as I am concerned, even though I would be happy to resolve the issue. By the way, the issue hasn't happened for a few days now, which is OK but there is still the lingering doubt that I will be in the middle of an important document and lose it just at the wrong time.
And then there's driver verifier, yes there is. That is another tutorial to learn what settings to use, going on the first time I tried to use it a few days ago. Anyway, I do enjoy the learning. By the way, my specialty is MS Excel and Access, a long way from what I'm learning here, but in a good way. You have been very generous with your time, I am grateful. So much to learn isn't there?
-
-
New #39
whilst not definitive (think coincidence, loading). I'm not sure what you mean there.= not 100% = not absolute proof or certaintywhilst not definitive
- coincidence- the simultaneous occurrence of 2 or more events - i.e. you waited, but it did not occur: but it may not have happened to occur just in that time frame but might have if you'd waited 5s longer...think coincidence, loading
loading: loading on power supplies uses more current. In safe mode, you expect loading to be a bit less- PC less busy. Increased demand on power supplies can reveal problems. That said, I'd expect your PC to be very very busy for the load to change significantly.
Phew.
chkdsk - no need except for interest to read up on that. At a command prompt try
chkdsk /?
to see options - some are a bit obscure.
Just run the command as given. Driver verifier is much more likely to be relevant.
-
New #40
chkdsk /? Is there a space after chkdsk (or it doesn't matter) and do I include the question mark? I just want to make sure I have the syntax correct.
Quote
Related Discussions
