britechguy
Well-known member
Hello All,
First let me preface this with: I have a full system image backup for this machine from prior to when this began occurring (today, after a "long nap") so I can restore if that's the best thing to do. This is a backup machine that has had no activity on it since the last system image was taken. I'm asking what follows for my own education.
Today when I tried firing up my old HP laptop with an A8 APU, it was hanging at boot after the POST screen. So, I did the triple hard power-down technique to get Windows to try to repair itself. It didn't. Tried a second cycle, which triggered a chkdsk as part of the repair process, but it still would not start. I get a message stating that Automatic Repair couldn't repair your PC and telling me that the log is in D:\WINDOWS\System32\Logfiles\Srt\SrtTrail.txt.
I then try to boot into Safe Mode with Networking, and get a BSOD with the error code BAD_SYSTEM_CONFIG_INFO. (What a shock there!)
Just wondering if there is a method that could be used to make the machine "snap out of it" other than a restore? Though if the restore would be much less time consuming I'd just go ahead and do it if it's well known that this particular error code needs a deep dive into many dark recesses of Windows 10 in order to resolve otherwise.
First let me preface this with: I have a full system image backup for this machine from prior to when this began occurring (today, after a "long nap") so I can restore if that's the best thing to do. This is a backup machine that has had no activity on it since the last system image was taken. I'm asking what follows for my own education.
Today when I tried firing up my old HP laptop with an A8 APU, it was hanging at boot after the POST screen. So, I did the triple hard power-down technique to get Windows to try to repair itself. It didn't. Tried a second cycle, which triggered a chkdsk as part of the repair process, but it still would not start. I get a message stating that Automatic Repair couldn't repair your PC and telling me that the log is in D:\WINDOWS\System32\Logfiles\Srt\SrtTrail.txt.
I then try to boot into Safe Mode with Networking, and get a BSOD with the error code BAD_SYSTEM_CONFIG_INFO. (What a shock there!)
Just wondering if there is a method that could be used to make the machine "snap out of it" other than a restore? Though if the restore would be much less time consuming I'd just go ahead and do it if it's well known that this particular error code needs a deep dive into many dark recesses of Windows 10 in order to resolve otherwise.
