Automatic Repair Solution | Bitcointalksearch.org

dress

full member

Activity: 439

Merit: 100

Thanks you! I was helped by this decision. Can you advise where you found these solutions? And how about the tests?

zeef

newbie

Activity: 301

Merit: 0

I have an monitor plugged (powered off) and now have no problem.

I have before an dummy plug too.

And the automatic repair solution problem was solved by:

bcdedit /set {current} bootstatuspolicy ignoreallfailures
bcdedit /set {default} bootstatuspolicy ignoreallfailures

Thanks people

indiejeff

jr. member

Activity: 96

Merit: 2

reading the problem and situation i think the problem is on logic board.. Huh

zeef

newbie

Activity: 301

Merit: 0

Quote from: dragonmike on February 07, 2018, 12:11:51 PM

Quote from: zeef on February 07, 2018, 11:56:21 AM

@dragonmike how you know what is the problem if you are remotely, have an remotely socket to restart the rig too? and start by an automated process..and you never see the problem ? Cool

I've got a TP-Link wifi plug indeed, so I'm just seeing on the pool that the rig is offline. Use my app in my phone to turn off the plug and back on again. When then looking at the event viewer in Windows, I'm none the wiser: "Kernel Power blahblah the last shutdown was unexpected blahblah". Don't know what happened. Only thing I know is that the rig did either lock itself up or did not reboot after it crashed (for whatever fukkin reason).

I'm kinda hoping it's trying to reboot but gets stuck in auto-repair screen. Preventing this would fix that problem.

yeahh, probably like my problem...

We will report soon.

Now only have the monitor connected bug.

Maybe is the board..

zeef

newbie

Activity: 301

Merit: 0

Hi again Folks,

I Have this rig:

Asrock H110 PRO BTC
120gb SSD
8GB Ram
CPU G4400
1 Saphire 8gb NItro +
7 Shaphire 4gb Nitro +
2 EVGA 750 watts GQ
Windows 10

Like i said Sometimes my rig got a kernel power and restarst (3 days more or less) Grin

But when restarts if i doesnt have connected any monitor (just have an black screen) and doesn´t sig in to windows to do the automated processes to start miner etc..

I tryed type 'netplwiz'. uncheck the 'users must use password to logon' and enter in your credentials. it will auto-login to windows upon reboot. And do this stuff, but only if i have an monitor connected, otherwise if i remotely connect i just see an blackscreen in teamviewer.

So I will bought an dvi dummy plug to solve that and just stay my old monitor connect.

In bios i tested change the internal vga or pciexpress and the problem is the same.

Just curious if anybody had solutioned this problems hehe

dragonmike

hero member

Activity: 1274

Merit: 556

Quote from: zeef on February 07, 2018, 11:56:21 AM

@dragonmike how you know what is the problem if you are remotely, have an remotely socket to restart the rig too? and start by an automated process..and you never see the problem ? Cool

I've got a TP-Link wifi plug indeed, so I'm just seeing on the pool that the rig is offline. Use my app in my phone to turn off the plug and back on again. When then looking at the event viewer in Windows, I'm none the wiser: "Kernel Power blahblah the last shutdown was unexpected blahblah". Don't know what happened. Only thing I know is that the rig did either lock itself up or did not reboot after it crashed (for whatever fukkin reason).

I'm kinda hoping it's trying to reboot but gets stuck in auto-repair screen. Preventing this would fix that problem.

zeef

newbie

Activity: 301

Merit: 0

Quote from: dragonmike on February 07, 2018, 11:50:18 AM

Random thread, random day, but could go a long way resolving some of the intermittent issues I am having. Amazing.

My rig sometimes will crash (Kernel-power event, no idea wtf is wrong, maybe a flaky mobo, PSU, who knows). But sometimes it's not coming back up again. Could very well be that it's stuck in the Windows Auto Repair screen and I'm not seeing it because the rig is stored remotely and I can't access it.

I'll set the boot status policy. Many thanks.

Hi,

My rig have that problem too , checking events i have Kernel-power event.

Every 3 days or so (random) but autorestarts and worked good until today.

This time go to automatic repair, so i open that thread to get helped.

I will include the sugested boot status policy changes and will report

@dragonmike how you know what is the problem if you are remotely, have an remotely socket to restart the rig too? and start by an automated process..and you never see the problem ? Cool

dragonmike

hero member

Activity: 1274

Merit: 556

Random thread, random day, but could go a long way resolving some of the intermittent issues I am having. Amazing.

My rig sometimes will crash (Kernel-power event, no idea wtf is wrong, maybe a flaky mobo, PSU, who knows). But sometimes it's not coming back up again. Could very well be that it's stuck in the Windows Auto Repair screen and I'm not seeing it because the rig is stored remotely and I can't access it.

I'll set the boot status policy. Many thanks.

mshordja

member

Activity: 146

Merit: 10

Quote from: whoismoses on February 07, 2018, 11:19:19 AM

I've tested it, which is why I recommended it.

How did I test? Well...

I just turned the PSU off while windows was running then again. I'd get the recovery screen. I ran the commands, rebooted. Tested again the same way, no recovery.

and thank you again Wink

zeef

newbie

Activity: 301

Merit: 0

Quote from: whoismoses on February 07, 2018, 11:19:19 AM

I've tested it, which is why I recommended it.

How did I test? Well...

I just turned the PSU off while windows was running then again. I'd get the recovery screen. I ran the commands, rebooted. Tested again the same way, no recovery.

Cooll

whoismoses

member

Activity: 247

Merit: 59

I've tested it, which is why I recommended it.

How did I test? Well...

I just turned the PSU off while windows was running then again. I'd get the recovery screen. I ran the commands, rebooted. Tested again the same way, no recovery.

mshordja

member

Activity: 146

Merit: 10

Quote from: zeef on February 07, 2018, 10:50:37 AM

Quote from: mshordja on February 07, 2018, 10:47:09 AM

Quote from: zeef on February 07, 2018, 10:41:59 AM

Quote from: mshordja on February 07, 2018, 10:32:18 AM

Quote from: zeef on February 07, 2018, 10:29:27 AM

Quote from: mshordja on February 07, 2018, 10:19:36 AM

Quote from: whoismoses on February 07, 2018, 09:45:12 AM

Start a command prompt window as administrator, run the following two commands. Restart.

You have to restart. This will prevent windows from doing what it did for you after a crash.

bcdedit /set {current} bootstatuspolicy ignoreallfailures
bcdedit /set {default} bootstatuspolicy ignoreallfailures

thanks i need it too Shocked

Thanks for the tip,

Have you tested ?

nope, but i will do tomorrow

Ok,

the problem is now how to put in the previous state of failure

You know how to put it in automatic repair and include the changes to se if result? Cool

power on , shutdown suddenly and repeat? hehe

You have to press (hold) SHIFT and restart the pc from start menu -restart.

Hmm nice, it isnt for safe mode ? Can test the automatic repair too? Will try when come home Shocked

now i am at work, and i will not make test like that if i am not in front of my rigs Cheesy

, and only tomorrow i can test

zeef

newbie

Activity: 301

Merit: 0

Quote from: mshordja on February 07, 2018, 10:47:09 AM

Quote from: zeef on February 07, 2018, 10:41:59 AM

Quote from: mshordja on February 07, 2018, 10:32:18 AM

Quote from: zeef on February 07, 2018, 10:29:27 AM

Quote from: mshordja on February 07, 2018, 10:19:36 AM

Quote from: whoismoses on February 07, 2018, 09:45:12 AM

Start a command prompt window as administrator, run the following two commands. Restart.

You have to restart. This will prevent windows from doing what it did for you after a crash.

bcdedit /set {current} bootstatuspolicy ignoreallfailures
bcdedit /set {default} bootstatuspolicy ignoreallfailures

thanks i need it too Shocked

Thanks for the tip,

Have you tested ?

nope, but i will do tomorrow

Ok,

the problem is now how to put in the previous state of failure

You know how to put it in automatic repair and include the changes to se if result? Cool

power on , shutdown suddenly and repeat? hehe

You have to press (hold) SHIFT and restart the pc from start menu -restart.

Hmm nice, it isnt for safe mode ? Can test the automatic repair too? Will try when come home Shocked

mshordja

member

Activity: 146

Merit: 10

Quote from: zeef on February 07, 2018, 10:41:59 AM

Quote from: mshordja on February 07, 2018, 10:32:18 AM

Quote from: zeef on February 07, 2018, 10:29:27 AM

Quote from: mshordja on February 07, 2018, 10:19:36 AM

Quote from: whoismoses on February 07, 2018, 09:45:12 AM

Start a command prompt window as administrator, run the following two commands. Restart.

You have to restart. This will prevent windows from doing what it did for you after a crash.

bcdedit /set {current} bootstatuspolicy ignoreallfailures
bcdedit /set {default} bootstatuspolicy ignoreallfailures

thanks i need it too Shocked

Thanks for the tip,

Have you tested ?

nope, but i will do tomorrow

Ok,

the problem is now how to put in the previous state of failure

You know how to put it in automatic repair and include the changes to se if result? Cool

power on , shutdown suddenly and repeat? hehe

You have to press (hold) SHIFT and restart the pc from start menu -restart.

zeef

newbie

Activity: 301

Merit: 0

Quote from: mshordja on February 07, 2018, 10:19:36 AM

Quote from: whoismoses on February 07, 2018, 09:45:12 AM

Start a command prompt window as administrator, run the following two commands. Restart.

You have to restart. This will prevent windows from doing what it did for you after a crash.

bcdedit /set {current} bootstatuspolicy ignoreallfailures
bcdedit /set {default} bootstatuspolicy ignoreallfailures

thanks i need it too Shocked

Thanks for the tip,

Have you tested ?

Can we go to regedit and change there?

zeef

newbie

Activity: 301

Merit: 0

Quote from: mshordja on February 07, 2018, 10:32:18 AM

Quote from: zeef on February 07, 2018, 10:29:27 AM

Quote from: mshordja on February 07, 2018, 10:19:36 AM

Quote from: whoismoses on February 07, 2018, 09:45:12 AM

Start a command prompt window as administrator, run the following two commands. Restart.

You have to restart. This will prevent windows from doing what it did for you after a crash.

bcdedit /set {current} bootstatuspolicy ignoreallfailures
bcdedit /set {default} bootstatuspolicy ignoreallfailures

thanks i need it too Shocked

Thanks for the tip,

Have you tested ?

nope, but i will do tomorrow

Ok,

the problem is now how to put in the previous state of failure

You know how to put it in automatic repair and include the changes to se if result? Cool

power on , shutdown suddenly and repeat? hehe

mshordja

member

Activity: 146

Merit: 10

Quote from: zeef on February 07, 2018, 10:29:27 AM

Quote from: mshordja on February 07, 2018, 10:19:36 AM

Quote from: whoismoses on February 07, 2018, 09:45:12 AM

Start a command prompt window as administrator, run the following two commands. Restart.

You have to restart. This will prevent windows from doing what it did for you after a crash.

bcdedit /set {current} bootstatuspolicy ignoreallfailures
bcdedit /set {default} bootstatuspolicy ignoreallfailures

thanks i need it too Shocked

Thanks for the tip,

Have you tested ?

nope, but i will do tomorrow

zeef

newbie

Activity: 301

Merit: 0

Quote from: mshordja on February 07, 2018, 10:19:36 AM

Quote from: whoismoses on February 07, 2018, 09:45:12 AM

Start a command prompt window as administrator, run the following two commands. Restart.

You have to restart. This will prevent windows from doing what it did for you after a crash.

bcdedit /set {current} bootstatuspolicy ignoreallfailures
bcdedit /set {default} bootstatuspolicy ignoreallfailures

thanks i need it too Shocked

Thanks for the tip,

Have you tested ?

mshordja

member

Activity: 146

Merit: 10

Quote from: whoismoses on February 07, 2018, 09:45:12 AM

Start a command prompt window as administrator, run the following two commands. Restart.

You have to restart. This will prevent windows from doing what it did for you after a crash.

bcdedit /set {current} bootstatuspolicy ignoreallfailures
bcdedit /set {default} bootstatuspolicy ignoreallfailures

thanks i need it too Shocked

whoismoses

member

Activity: 247

Merit: 59

Start a command prompt window as administrator, run the following two commands. Restart.

You have to restart. This will prevent windows from doing what it did for you after a crash.

bcdedit /set {current} bootstatuspolicy ignoreallfailures
bcdedit /set {default} bootstatuspolicy ignoreallfailures

Topic: Automatic Repair Solution (Read 366 times)