BSOD errors 0x00000124 and 0x000000A

Hi JoePc,

Something badly wrong with the latest install
No point in troubleshooting BSOD's yet, we need to get the system upto date
Is this a Skylake processor??

please run
sfc /scannow

KB947821, (SURT)
post the checksur log from the CBS folder

and
chkdsk /r


Roy

Thank you for the reply Roy! I have attached the CheckSur.log as you requested.

Yes its Skylake: 6700K @ 4.0 GHZ and its not been overclocked.

I ran sfc /scannow in safe mode (it blue screened in normal mode):
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

chkdsk /r repaired some stuff.

As for KB947821, there was a lot of blue screens with different error codes: 0x0000003B, 0x0000009C, 0x0000000A, and 0x000000FC. I had Speccy opened on attempted install. The temps were 20-50 degrees Celsius.

A really strange one that occurred when logging in one time was 0x000000D1.

After installing Windows 7 from HP recovery discs it was blue screening and I noticed it never blue screened in Safe Mode so I messed with what was turned on in msconfig via selective startup. Before my first post I set it to normal startup. HP chose the 1 TB HD and installed onto it overwriting where I had Slackware installed. I installed Slackware on the SSD HD and created a fat32 for its EFI but it decided to install its boot on the 1 TB HD where Windows 7 is. Since HP was blue screening I decided to install FreeBSD and see what happens and use it as a back up OS since there are a few programs I require. I had to shrink the Windows 7 partition and I decided to move a partition HP recovery created in front of the new free space I created which may not have been a good idea. I'd rather not use HP recovery again and wipe out one of the other operating systems I've installed unless it is obfuscating the cause of the BSODs and failure of software to install since Windows 7 hasn't been usable outside Safe Mode since I installed it.

Hi Joe,

Couple of points of note

Downgrading back from W10 has been known to cause problems, especially in a dual boot configuration like yours. A clean install is the preferred option
note the HP hidden recovery partition doesn't help matters either - did it show in Freebsd

UEFI (Unified Extensible Firmware Interface) - Install Windows 7 with - Windows 7 Help Forums
Note the warnings

Unusuall for an OEM to ship W7 with Skylake as MS removed support for it
There are tweaks so you can update it @Megahertz07

Re the Checksur log as you said it failed and did not complete, so unfortunately of no help.

As this is a relatively new set-up i would go for a clean install

IF you plan to run Linux as well i would suggest you run it "inside" W7 (UEFI or Legacy Bios)
Dual Boot Windows 7 and Ubuntu - Windows 7 Help Forums

LEGACY BIOS ONLY
Dual Boot - Windows 7 and Linux - Windows 7 Help Forums

tip

Windows Easy Transfer - Transfer To From Computers - Windows 7 Help Forums

Roy

Thank you for the reply Roy!

The family member whose PC this is doesn't think a new fresh install will help because these BSOD errors occurred with the very recent completely fresh install with nothing but Windows 7 on it using the HP recovery disc set that I made when they first got the PC. It completely wrote over the Slackware partition and took the whole drive. The other hard drive where Windows 10 was installed I turned into unallocated free space. I had deleted everything pertaining to Windows 10. They don't want to do a fresh install again because HP will completely write over the hard disk which would erase Slackware or FreeBSD and we would still be stuck with BSODs from faulty hardware. They don't want to torture me with reinstalling these operating systems. It seems like luck that Windows 7 installed at all when the Windows 10 disc would BSOD in the installation process. They don't want to do another fresh install unless the BSOD problem is resolved. If that can't be done they seem to be fine with giving up Windows on this PC.

The family member wants to know which hardware components are causing the errors because they are considering getting a barebones computer and installing the working components from this one onto it if whatever it is can't be disabled. I have no idea how to further troubleshoot this issue for them on any operating system platform. They don't want to send it back to HP because its out of warranty. I've never seen Windows 10 BSOD during the early part of a completely fresh installation before and everything seems fine besides the BSODs. They have reinstalled Windows 10 dozens of times on that PC with no problem. Another option they are considering is just using Slackware and FreeBSD until their computer dies. They run Slackware from dawn to dusk on this machine and no instability issues are noticeably experienced. It serves their needs but they need me to update and configure it. If they went the barebones route they know they'll have to buy a new copy of Windows. I do not know what they plan to do. They probably don't know themselves because we don't know which piece of hardware is causing the problem.

I haven't looked to see if the HP recovery partition showed in FreeBSD. It hasn't been really used yet except I spent about 5 hours figuring out how to get wireless working. I'll check it out later today when my family member is done using their computer. I have seen it in bios but I don't dare run it. If I was going to reinstall Windows 7 I'd use the HP disc set like I did previously. rEFInd doesn't show it though. Oops.

The WUBI installer looks nice. The family member may just want Windows but they are starting to really like Slackware so they might want to keep it on there. They've never used Linux until a few days ago. Only Windows was on their PC until all these BSOD errors started to occur.

They've been using Slackware for 3-4 hours doing their normal routine and the linux sensors program shows that the CPU cores are 34 degrees Celsius or less.

I appreciate and suggestions. Its fine with me if you decide that you can't further help me without another fresh install. I understand where you are coming from on it.

Hi Joe,

Understand the problem.

The only other thing that can get us upto date, as the KB947821 wont complete, is to perform a repair install

Repair Install - Windows 7 Help Forums

MAKE SURE THE DRIVE ON WHICH W7 is installed is the ONLY HDD plugged in

notes
you said there were problems during the Chkdsk scan do you know what they were
bad blocks means the dics on its way out and anything trying to write to them will be affected
as these tend to be at the the start -whats on it first gets corrupted, maybe why Slackwares working
Reset Bios to default values.


Roy