Boot to Bluescreen in normal mode, Black screen in safe mode

goku2 · Aug 18, 2018

I want to preface everything by saying that I changed the bootloader configuration to "legacy" so that I can use F8 in order to boot into safe mode directly. (Makes things a lot easier IMO). No, I cannot "reset PC" even if I hadn't set the bootloader config to legacy and I also have no system restore points. After the computer stopped being able to boot normally, I used to be able to boot into "safe mode with networking" with the F8 command. However, after about 8 hours of doing manual file repairs and using dism and changing MSCONFIG to Diagnostic Startup, now when I go to safemode, I get stuck on a black screen.

Through MSCONFIG following settings were set:Bootlog
Basevideo
OS boot information
All the system services available through MSCONFIG were selected off due to the "diagnostic startup" selection.

On this system, I have an SSD installed on this system with version 1803 installed. I also have at my disposal another computer I specifically installed (1709 July) just in case I needed files to fix my damaged (1709 May?) installation. I thought I should also mention I have a bootable 1709 USB flash drive.

When I boot regularly, I get a Critical Service Failed error and according to the minidump, it's related to NTOSKRNL and ntkrnlmp. The computer used to boot normally until there were several bad sectors that were found on this computer. After the bad sectors were repaired, the computer had this critical service failed problem. I'm assuming some system files got corrupted along with some drivers.
I've run Checkdsk /r, it 'fixed (meaning deleted) the corrupted files and now chkdsk no longer shows any bad sectors and it completes the scan successfully.

ntbtlog.txt does not appear to log anything when booting normally, only in safe mode which I guess it means it's crashing very early in the boot process.

I have DISM and CBS logs I can provide if need be. When I boot from the working SSD OS install (1803), if I run DISM on the offline image (1709) dism stops at around 84%.
Due to possibly corrupted system file permissions and ownership, those things may need to be repaired. I've had to take ownership of several files in order to repair them. I had at least two corrupted catroot catalog files that I successfully replaced but did not repair their permissions and about 20 Winsxs files the same thing. I've tried very hard to make sure when I replaced a file, I was using the exact same file version but there are a small handful of driver files that I used newer versions of than what came with the computer. I have a pretty good idea of the files I've replaced and which permissions I have not restored.

My primary goal is to get the computer to boot relatively normally so that I can do a repair installation if necessary.

goku2 · Aug 18, 2018

I don't know what happened to my post but the post above is an older version of the post I had written. So I would like to update the OP with some information.

DISM actually now completes to 100% thanks to windows update catalog download extraction and using DISM to update the image, so that's good a baseline. However, as shown in the CBS (System file checker) logs, while tens of thousands of files are noted for replacement, SFC gets hung up on the primitive installer so it's not able to complete any tasks. I have probably 80K pending renamed in the WinSXS temp folder.

What I was hoping to figure out is if I should fix the dependencies of the SFC program that are preventing it from conducting its tasks or use some sort of SFCfix utility that can be run on an offline image. SFCFix does not work in the Windows RE. When the computer used to be able to boot into safemode, when I ran the SFCFix program, it would hard crash and left a sizable dumpfile behind. I'm thinking SFCFix tried to force usage of the primitiveinstaller or some other critical dependencies that SFC typically uses that are likely corrupt. Windows Startup Repair fails in basically the same spot as you'd expect, in the system file verification stage.

I guess the summary of this post is: How do I get SFC working properly again or figure out why it's getting hung up.

jcgriff2 · Aug 18, 2018

Hi. . .

I have a lot of questions, but let's start here. . .

goku2 said:
...However, after about 8 hours of doing manual file repairs...

I assume that you are running Windows 10 x64...?
When did you install Windows 10? i.e., how old is this W10 installation?
You can run systeminfo.exe from an Admin/elevated CMD screen to learn the installation date. Execute the systeminfo command by typing it in to the CMD screen; it will take about 1 minute to run; scroll up to the top of the output in the CMD screen; look on line 10 - it contains the OS install date or if the system was new, it will contain the date of the first time that the system was turned on and the initial user account was created, which is good enough for our purposes here
What kind of file repairs were/are you doing?
What does a file repair entail?
How do you do a file repair?
Why do you need to do file repairs?
How do you know which files need to be repaired?
Why not use sfc /scannow for such file repairs?
How do you know that a file repair was successful?
Are you somehow altering code in Microsoft drivers?
Why are you doing file repairs?
How long after initial boot/Windows installation did you do the first file repair?
Did you have BSODs before the first file repair?
Have you [tried to] reinstalled Windows to start anew?

Given what I have read so far, I would think that the possibility is high that your BSODs have to do with kernel corruption (bugcheck 0x109 - CRITICAL_STRUCTURE_CORRUPTION) -- just a guess on my part.

Are you able to run the jcgriff2/Sysnative app found in step 1 of the BSOD Posting Instructions?

Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 + Vista

If so, please do so and attach the resulting Sysnative ZIP file to your next post.

If not able to run the app, I need for you to somehow obtain all of the dump files in \windows\minidump; ZIP them up; attach the resulting zip file to your next post.

I must see/process the mini kernel memory dumps to see if they offer us any clues as to the cause of the BSODs. BSODs occur within Windows only, which means that Windows would have been loaded at the time of the BSODs.

goku2 said:
...according to the minidump, it's related to NTOSKRNL and ntkrnlmp

These two files are directly related to the Windows kernel and are not the actual cause (unless you have somehow "repaired" them). They are listed in the dumps as the probable cause of the crashes as a default of sorts (because the actual cause is unknown).

goku2 said:
...After the bad sectors were repaired, the computer had this critical service failed problem. I'm assuming some system files got corrupted along with some drivers.
I've run Checkdsk /r, it 'fixed (meaning deleted) the corrupted files and now chkdsk no longer shows any bad sectors and it completes the scan successfully. ...

If chkdsk showed bad sectors at any time, the HDD must be replaced to ensure good system functionality.

chkdsk simply marks bad sectors as unusable, then attempts to move the file(s) that resided in the bad sectors to different, "good sector" areas. But once bad sectors start appearing on a hard drive, it's time to replace it, in my opinion.

Files (including apps and drivers) are moved constantly between the hard drive (page file) and [are loaded into] RAM for execution. An executable file or driver must be loaded into RAM before it can be executed. When the system no longer needs the app or driver, it unloads it from RAM back to the page file.... and this process is repeated and repeated.

If a file is corrupted for *whatever* reason, it obviously will not/ cannot be loaded/moved from the page file into RAM successfully and whole. This is just one cause of APPCRASHes or BSODs. Then the system may try to unload it, but at this time, a corrupted file is definitely what the system is working with.

sfc /scannow is the only Microsoft-sanctioned method to fix corrupted files. You can also manually copy files hidden throughout \windows\winsxs and elsewhere to their correct destination to fix corrupted files as well. You can also obtain a copy from another system -- but the file version must be identical (including Windows Updates). But the latter two methods are not Microsoft sanctioned as much can go wrong and end up ruining your Windows installation.

goku2 said:
ntbtlog.txt does not appear to log anything when booting normally, only in safe mode which I guess it means it's crashing very early in the boot process.

I would agree on this point.

goku2 said:
I have DISM and CBS logs I can provide if need be. When I boot from the working SSD OS install (1803), if I run DISM on the offline image (1709) dism stops at around 84%.
Due to possibly corrupted system file permissions and ownership, those things may need to be repaired. I've had to take ownership of several files in order to repair them. I had at least two corrupted catroot catalog files that I successfully replaced but did not repair their permissions and about 20 Winsxs files the same thing. I've tried very hard to make sure when I replaced a file, I was using the exact same file version but there are a small handful of driver files that I used newer versions of than what came with the computer. I have a pretty good idea of the files I've replaced and which permissions I have not restored.

My primary goal is to get the computer to boot relatively normally so that I can do a repair installation if necessary.

I am not a Windows Update expert like others here are. However, one reason for things like DISM getting stuck can be a faulty hard drive. Think about it... the system is writing/reading to/from the HDD/SSD, hits a bad sector and simply gets stuck and cannot go on. I'm sure there are other reasons, but I don't know what they are off-hand.

Reading the rest of your paragraph here is now starting to answer my questions that I posted earlier.

Taking ownership of Microsoft Windows files without expert assistance and guidance can lead to disaster, as you are now finding out. Windows knows who the owner of each file should be and when these permissions get out of whack, strange things can happen as Windows may look upon it as a [security] attack.

It's too bad that you did not find us sooner as we very likely could have helped you, but I fear it is now too late due to all of the changes that you have made to your Windows installation.

goku2 said:
I guess the summary of this post is: How do I get SFC working properly again or figure out why it's getting hung up.

I will ask a Windows Update expert to take a look at your thread and ask if your Windows installation is salvageable or not.

If it were me - I would replace the SSD and reinstall Windows, thus starting from scratch.

Please at least get me the BSOD dumps. I really would like to take a look at them. Thank you.

Regards. . .

jcgriff2

EDIT: You mentioned that you have an SSD.

Go to the SSD manufacturer's support site and check for a firmware upgrade/update. **VERY IMPORTANT **

goku2 · Aug 18, 2018

Yes the system is X64, and the 1709 install was from october though the system had been updated through may of 2018 with the bad sectors occurring sometime in June. System worked reliably until I had to fix the bad sectors on the drive which obviously corrupted some files or even outright deleted otherwise as through checkdisk. As for the concerns about bad sectors and whatnot, after using a low level drive utility, while there are many reallocated sectors via firmware, there are no more bad sectors being detected when a sector by sector HDD scan is performed which took several days perform on a 1TB hdd. While it's still likely a good idea to replace the drive as the previous bad sectors could have been caused by manhandling the machine, because the HDD has worked reliably over the past 2 months, I'm confident I can continue to use the drive at least until I get the computer working properly again. Once the computer boots up normally, I plan to image this to the SSD and replace what's on there. I had originally backed up everything from the mechanical drive to the SSD AFTER doing the bad sector repairs (so the drive could be easily read), then did some OS repairs but I failed at that. Then, due to running out of time, I tried again to do the OS repairs to the original mechanical drive (a little more carefully) and I borked that as well. So I technically have two OS installs of this system, both borked, one on the SSD which dual boots to a working version of 1803 and the original install on the mechanical drive. I receive a 0xc000007b bluescreen when I boot to safe mode on the SSD version of the broken OS.

The SSD was purchased recently and was installed in the machine as an upgrade. I have a working copy of 1803 Win 10 X64 running on that SSD that I dual boot into when I'm conducting repairs on the old mechanical HDD or to the SSD version of the broken OS.

Attached in this post are some minidumps and here is a link to a larger memory dump: Larger Dump.zip - Google Drive

Just keep in mind at this time, we're only working on the mechanical drive version as the SSD version I did a lot of non-kosher stuff so I'd imagine it's less salvageable. On the mechanical drive, I'm 90% certain I can isolate all the files I touched as I only did a small handful before realizing I should stick with DISM for file replacement. Either way, before or after I was no longer able to boot into safe mode, I was still being held hostage by the fact that SFC couldn't perform its tasks whether operating in online or offline mode.

jcgriff2 · Aug 18, 2018

Hi. . .

Thank you for the dump files -- I'll get to those in a moment.

First thing - you have the same Windows OS installation on 2 different drives? One is a 1 TB HDD (the drive with bad sectors) and the other is an SSD?

Have both been used and connected to the Internet?

If so, Microsoft may see this as a copy of an existing, validated Windows OS and now seeing 2 OS' with the same keycode, but different hard drives, may invalidate both copies.

However, if you're telling me that you simply made an image of the HDD and copied that to the SSD and that the SSD has never been used (booted) and connected to the Internet, all should be fine. Make sure that the SSD is never in the system while connected to the Internet.

To help solve the status of the questionable 1 TB HDD, run SeaTools for DOS, LONG test - Hard Drive Diagnostics & SSD Test

SeaTools will tell us about bad sectors.

As for the 4 dumps -

The bugchecks (STOP error) on all 4 dumps was the same - 0x5a = a system service critical to Windows failed for an unknown reason. That is all of the information available from Microsoft MSDN on 0x5a as this bugcheck is very rarely ever seen.

From Microsoft MSDN:

Code:

[SIZE=4]Bug Check 0x5A: CRITICAL_SERVICE_FAILED[/SIZE]
The CRITICAL_SERVICE_FAILED bug check has a value of 0x0000005A.

This bug check appears very infrequently.

"Memory Corruption" is listed as the probable cause on all 4 dumps. This DOES NOT necessarily mean that RAM is at fault, but it may be. RAM should be tested. Run memtest86+, one stick at a time; alternate the slots - Test RAM with memtest.org MemTest86+

A short summary of the 4 dumps and their bugchecks and parms (numbers inside the parenthesis):

Code:

[font=lucida console]
BugCheck 5A, {1, ffffa682bfb4f970, ffff86067fc1c410,[COLOR="#FF0000"] ffffffffc0000428[/COLOR]}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 5A, {1, ffffb78639cb3820, ffff9209d1261a10, [COLOR="#FF0000"]ffffffffc0000428[/COLOR]}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 5A, {1, ffffcd0530d44330, ffffe28e4f1991a0,[COLOR="#FF0000"] ffffffffc0000428[/COLOR]}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 5A, {1, ffffb40ac8b43240, ffff9d0634295ef0, [COLOR="#FF0000"]ffffffffc0000428[/COLOR]}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

Parm 1 (0x1) appears to be an internal unknown code
Parm 2 ad 3 - memory addresses -- reason listed as P2 + P3 = unknown
Parm 4 - 0xc0000428 = NT Status Exception Error Code = Windows cannot verify the digital signature for this file

So, all 4 BSODs were caused by an unidentified Microsoft driver for which the digital signature of the file was bad. It appears that one or more of your file fixes did not go well or file/kernel corruption has reared its ugly head again.

Furthermore, I am getting what are called "symbol errors" in Windbg. If you ran Windbg yourself, you would have seen them -- large boxes created by repeating asterisks (*) with error information inside.

Just for info - system up-time for each BSOD. Three were 41 seconds each; the 4th was just 7 seconds:

Code:

[font=lucida console]
System Uptime: 0 days 0:00:41.084
System Uptime: 0 days 0:00:41.305
System Uptime: 0 days 0:00:41.589
System Uptime: 0 days 0:00:07.285
[/font]

Your Windows OS is far beyond repair. I heard back from one of our Windows Updates expert and he agrees with me (he reviewed the CBS logs you submitted) about the status of your OS.

The bottom line here is that your Windows installation is not salvageable. You need to reinstall Windows on a good hard drive.

My guess here is that your HDD went bad, caused file corruption; you attempted to repair the corruption, but to no avail. In the future, if sfc /scannow cannot fix file corruption, please come back here and seek help.

Regards. . .

jcgriff2

`

Code:

[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\081818-19203-01.dmp]
Built by: 16299.431.amd64fre.rs3_release_svc_escrow.180502-1908
Debug session time: Sat Aug 18 09:21:47.362 2018 (UTC - 4:00)
System Uptime: 0 days 0:00:41.084
Probably caused by : memory_corruption
BUGCHECK_STR:  0x5A_c0000428
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
Bugcheck code 0000005A
Arguments 00000000`00000001 ffffa682`bfb4f970 ffff8606`7fc1c410 ffffffff`c0000428
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\081818-19968-01.dmp]
Built by: 16299.431.amd64fre.rs3_release_svc_escrow.180502-1908
Debug session time: Sat Aug 18 07:17:10.603 2018 (UTC - 4:00)
System Uptime: 0 days 0:00:41.305
Probably caused by : memory_corruption
BUGCHECK_STR:  0x5A_c0000428
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
Bugcheck code 0000005A
Arguments 00000000`00000001 ffffb786`39cb3820 ffff9209`d1261a10 ffffffff`c0000428
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\081718-24921-01.dmp]
Built by: 16299.431.amd64fre.rs3_release_svc_escrow.180502-1908
Debug session time: Fri Aug 17 13:47:02.887 2018 (UTC - 4:00)
System Uptime: 0 days 0:00:41.589
Probably caused by : memory_corruption
BUGCHECK_STR:  0x5A_c0000428
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
Bugcheck code 0000005A
Arguments 00000000`00000001 ffffcd05`30d44330 ffffe28e`4f1991a0 ffffffff`c0000428
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\081718-24093-01.dmp]
Built by: 16299.431.amd64fre.rs3_release_svc_escrow.180502-1908
Debug session time: Fri Aug 17 11:41:23.582 2018 (UTC - 4:00)
System Uptime: 0 days 0:00:07.285
Probably caused by : memory_corruption
BUGCHECK_STR:  0x5A_c0000428
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
Bugcheck code 0000005A
Arguments 00000000`00000001 ffffb40a`c8b43240 ffff9d06`34295ef0 ffffffff`c0000428
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

goku2 · Aug 18, 2018

As for the two Windows installs and product key stuff, I have another machine with Windows 10 installed on the same HDD dual booting, one with 32bit and one with 64bit. Both have connected to the internet and got their Digital Entitlement license from Microsoft. I've never seen an issue with cloning a windows installation onto another drive and connection to the internet invalidating any product keys. Changing the motherboard like swapping the HDD between two identical laptops (which have different mac addressess) however does not work.

I've already run seatools equivalent tools and the drive while it does have a lot of reallocated sectors, has no more pending reallocation of sectors and all the sectors on the drive read acceptably (though there are a handful of slowish sectors which can't be reampped unless they're outright bad).

Back to the memory corruption. Since I have a working Windows 10 install on the machine we're working on (1803) and I've done software ram tests as well, I'm confident there are no hardware issues. As for your suggestion that I should have just posted here prior to doing any work on the machine, the SFC logs are almost identical to when I was able to boot into safe mode. I have a copy of the CBS logs from when the computer could still boot into safe mode. DISM and CBS logs haven't changed materially.

The DUMP files were generated only when booting normally. No dumpfiles are being created when booting into safe mode, at least the safemode for the Mechanical drive which is the one we're working on right now.
If I had come to you when the computer booted acceptably into safemode but not normally, how would you have treated this issue differently? How can/should I run SFC on an OS build where the primitiveinstallers function seems to be an issue?

jcgriff2 · Aug 19, 2018

The BSOD dumps would have been an eye opening clue to me.

There is another similar and very common bugcheck to 0x5a -- 0xf4.

From MSDN:

Code:

[SIZE=3]Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION[/SIZE]
The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. 

This indicates that a process or thread crucial to system operation has 
unexpectedly exited or been terminated.

Every time this bugcheck shows up, the HDD is to blame, even though OPs will swear to me that their HDD is fine.

When something critical to Windows suddenly and inexplicably fails (like the loading of a driver from the page file into RAM), the hard drive is obviously involved and in 99.99% of the cases with 0xf4, the HDD is to blame - a bad sector is hit. IMO, 0xf4 and 0x5a seem very close to me.

Humor me - run SeaTools!

A HDD with bad sectors cannot be trusted.

The Windows Update Team are drowning in threads and require certain apps to be executed and certainly requires a stable system. They could not possibly help you at this time. I'm sorry about that.

I guess I'm at a loss to understand why you don't just re-install Windows on the SSD and get it over with. You have made too many back door changes with file repairs then taking ownership finished things off, IMO.

Furthermore, the symbol errors in Windbg speaks volumes. It confirms the presence of invalid Microsoft drivers.

As for the dual boot with one keycode - I hope nothing happens. I've been at and behind these forums for over 10 years now having started this one in 2012 and could tell you horror stories about validation. You should not use one key for two copies of Windows, even though the hard drive is the only difference. I personally would not chance it. Perhaps these BSODs are connected!

Again, the problem here is your 1 TB HDD, the various repaired files and the perms.

I would wipe the SSD and install Windows on to it.

Regards. . .

John

goku2 · Aug 19, 2018

jcgriff2 said:
Every time this bugcheck shows up, the HDD is to blame, even though OPs will swear to me that their HDD is fine.

When something critical to Windows suddenly and inexplicably fails (like the loading of a driver from the page file into RAM), the hard drive is obviously involved and in 99.99% of the cases with 0xf4, the HDD is to blame - a bad sector is hit. IMO, 0xf4 and 0x5a seem very close to me.

I'm confused. Didn't I say before that the original reason for the BSOD was due to bad sectors corrupting system files? That I then ran various low level drive tools until the drive was usable again? I know there is file corruption due to the previous bad sectors (that were overwritten with blank data so they could be read) but I don't believe there is any NEW file corruption going on.

Furthermore, the symbol errors in Windbg speaks volumes. It confirms the presence of invalid Microsoft drivers.

That's what SFC is for, correct? I just wish there was some utility I could run offline that would verify the SHA or MD5 hashes of all the non windows files.

If you're not able to help me directly, at least guide me in the direction on how I would get SFC to continue operating. I don't absolutely need my hand held but I would like general guidance. Permissions causing this issue or not, the only thing that changed since I first started the attempted repairs is the black screen in safe mode (no longer fully booting) but otherwise, the dump logs, DISM logs and SFC logs are identical before and after I manually changed some files and their permissions. When I ran SFC while in safe mode or when offline, results were identical

SFCFix cannot be run on an offline partition, right? I don't want to do a full reinstallation because I have software on here that I do not have the product installation discs or product key to reinstall.

jcgriff2 · Aug 19, 2018

How do you know that prior BSODs were caused by bad sectors?

Where are those dumps?

Drivers are loaded from disk into RAM and back again (unloaded drivers). BSOD dumps are post-mortem, capturing kernel memory at the time of a BSOD. The dumps are telling me that your system contains corrupted drivers - again, at the time of the BSOD crash. Again, the contents of kernel memory is what BSOD dumps contain - not what resides on your disk; hence there are no drivers to "repair" while they reside on disk after system shutdown.

Somewhere between the driver(s) being loaded from disk into RAM an/or from RAM back to disk, your system is crashing. Only 2 things can cause this - a rogue 3rd party driver or hardware failure corrupting kernel memory. No 3rd party driver was listed on the stack, so unknown hardware failure is the probable cause.

Everything in your dumps indicate to me that unknown hardware failure is the cause.

Windows Updates Experts here at Sysnative have said that your best option is to reinstall Windows. There is nothing that they can do to help. I have said the same (reinstall Windows).

Wipe (format) the SSD; install Windows onto it and see if the BSODs continue.

Regards. . .

John

goku2 · Aug 19, 2018

jcgriff2 said:
How do you know that prior BSODs were caused by bad sectors?

Where are those dumps?

Drivers are loaded from disk into RAM and back again (unloaded drivers). BSOD dumps are post-mortem, capturing kernel memory at the time of a BSOD. The dumps are telling me that your system contains corrupted drivers - again, at the time of the BSOD crash. Again, the contents of kernel memory is what BSOD dumps contain - not what resides on your disk; hence there are no drivers to "repair" while they reside on disk after system shutdown.

Here is the history of the computer: I receive the computer because it's taking a really really long time to boot up, so long that I wasn't willing to wait hours for it to boot. So I turn off the computer, remove the HDD and put it into another computer and boot using a low level drive utility to glean information from the HDD. That's when I find out it has bad sectors as the HDD is getting hung up on some sectors. I saw many allocation events that had occurred previously so I decided the quickest way to get the drive working again was to use HDAT2 since Spinrite doesn't work on 1TB HDDs. While this is guaranteed to corrupt some data, I figured I'd do it this way because I wanted to prevent the HDD from reallocating sectors that I know have a good chance of being revived which can work if the sector just had weak magnetism from a shutdown event or something of the like vs. actually damaged. If the sectors are truly bad, then sometime in the future, usually pretty much right away, the sector will get flagged for reallocation again and will actually get reallocated. Once I was able to do a complete read through of the drive, I then shrunk the partition of the drive to the minimum size possible, then imaged that drive to the SSD. The first test is I booted up the mechanical drive (put it back into the laptop) and saw that I had that same stop code we're talking about now. To confirm it was a corrupted file issue, I also booted up the SSD and came up with the exact same stop code. From there, after booting into safe mode, I analyzed the dump files and the internal system logs and whatnot and figured I likely have some sort of bad driver or there is some system service that boots in normal but not in safe mode. I tried for the next month to isolate and figure out which service or driver was causing the crashes in normal mode but wasn't able to. I had little luck with SFC and DISM because they were never able to complete their work. I then decided to install Windows 1709 on the SSD on a second partition and when using SFC or DISM would reference this fresh windows install for source files. Windows forced an update on me to 1803 but because it was said that a newer install source could be used for DISM repairs I figured it was alright. Didn't work out that way as I continued to have issues with getting the replacement source files DISM needed.

Anyway, I know the laptop hardware is solid as I've done enough hardware testing and have used Windows 1803 on that computer long enough to know it is stable and working properly.
I have a 100% working copy of Windows 10 1803 where everything works properly and boots normally off the SSD.

So that goes back to the obvious issue, a lot of system files were corrupted but not corrupted enough to prevent the computer from working properly. Computer worked fine in Safe mode with networking, spent dozens of hours in Safe Mode with Networking either running software or browsing the web and it never crashed. In MSCONFIG I put it into Diagnostic Startup (which disables all system services and the boot mode I tried Bootlog Base Video and OS Boot Information. I even try uninstalling all the drivers I could from device manager and rebooting into normal mode but had no luck, same stop code in Normal mode. The older versions of windows used to show Non PNP drivers that could be directly removed/uninstalled but in Windows 10, that is no longer available unfortunately.

Somewhere between the driver(s) being loaded from disk into RAM an/or from RAM back to disk, your system is crashing. Only 2 things can cause this - a rogue 3rd party driver or hardware failure corrupting kernel memory. No 3rd party driver was listed on the stack, so unknown hardware failure is the probable cause.

My guess is, a corrupted driver or two are able to load into memory but because of a silently flipped bit here or there is causing the computer to crash as the driver behaves in a way it's not intended. Some system service or driver must have low level file corruption that can cause the computer to behave funny and crash not when it's loaded but when a certain section of the driver is utilized or called upon by the loading of another service or driver. If the hardware is 100% solid, I don't know what else can cause the kernel to crash.

Either way, since SFC works off of system file hashes, I was wondering, does SFC fix corrupted drivers in system32\drivers folder? It would appear that WinSXS is a repository for system drivers issued by Microsoft. That would mean SFC should be able to utilize this now 100% working folder as a source to repair files within the SYSTEM32 and its driverstore or drivers folder. I figured that if at the very least, I replace all the corrupted system files with good ones from the WinSXS folder that there is a better chance of the system booting properly. When files get replaced, don't they get replaced with their proper ownership and ACL permissions? That's why I want to get SFC working properly, so that the files I did replace improperly get replaced again by working copies with proper permissions.

To me, at this point, this section at the very end of the CBS log is the only hangup for the SFC to continue as analyzing the rest of the SFC log yields nothing:

00013c5c@2018/8/18:10:37:27.284 (F) onecore\base\wcp\componentstore\deltastore.cpp(3096): Error STATUS_INVALID_PARAMETER originated in function ComponentStore::CRawStoreLayout:

ecompressFile expression: Parameter check failed
00000003 Servicing stack shim unable to mark handle 24c ('\Device\HarddiskVolume3\Users\Grant\AppData\Local\Temp\SSS_e0e25816dc36d4010100000070471045\msdelta.dll') for delete-on-close, error STATUS_CANNOT_DELETE
00000004 Servicing stack shim unable to mark handle 1c4 ('\Device\HarddiskVolume3\Users\Grant\AppData\Local\Temp\SSS_e0e25816dc36d4010100000070471045') for delete-on-close, error STATUS_DIRECTORY_NOT_EMPTY

I can't find any references online to deltastore.cpp, where it's located or why it's not working properly.

I know you have no intention of helping, but I still want to know, what are the dependencies and or software that I can use that will make SFC work properly in offline mode or can at least utilize the CBS logs to conduct the primitive installer file movements. The way I look at this problem is, SFC has identified a bunch of files that need to be replaced due to mismatch hashes. Why not replace all the files it has already identified first, hope the system boots up, then come back and work on the rest if necessary. If SFC can and does Hash checking for all the system files and drivers on the computer, and I can run this program in offline mode, I don't see why I can't run this program until its conclusion where it hash checks every file on the computer and replaces every file it deems necessary.

Oh and here are the attached seatools scans. First is the Long Generic scan and the next is the SMART test. The most thorough way to check the drive is to check every sector sequentially but for a 1TB drive, I have no interest in doing that again as that took several days to conduct and I already know the drive is working reliably enough for these purposes.

jcgriff2 · Aug 19, 2018

goku2 said:
To confirm it was a corrupted file issue, I also booted up the SSD and came up with the exact same stop code. From there, after booting into safe mode, I analyzed the dump files and the internal system logs and whatnot and figured I likely have some sort of bad driver or there is some system service that boots in normal but not in safe mode. I tried for the next month to isolate and figure out which service or driver was causing the crashes in normal mode but wasn't able to.

Did you ever run Driver Verifier which would have analyzed every selected driver?

Our instructions state to select non-Microsoft drivers, but in your case, you could have selected Microsoft drivers to try and prove your point.

Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista

You're doing all of this with a bad HDD. I am no chkdsk expert, but once bad sectors show up, it's time for a new HDD or alternate SSD with a new Windows installation. The old HDD with the bad sectors becomes unreliable. I don't care how many bad sectors are marked unusable and you believe that the system will skip over them when writing new files. It does not always work that way - as you're dealing with a failing HDD. Why didn't you simply wipe the SSD and install Windows onto it, then connect the HDD to your system via PCIe or USB and retrieve wanted files?

The time (1 month+ --??) that you have spent trying to fix the unfixable is mind boggling.

goku2 said:
I had little luck with SFC and DISM because they were never able to complete their work.

Did you get the message that Windows was unable to fix all of the problems - SFC?

goku2 said:
I then decided to install Windows 1709 on the SSD on a second partition and when using SFC or DISM would reference this fresh windows install for source files.

So this is now the 3rd copy of this Windows 10 installation with the same keycode?

goku2 said:
I have a 100% working copy of Windows 10 1803 where everything works properly and boots normally off the SSD.

Why not then move on and use this OS and load your apps and programs and files onto it?

goku2 said:
So that goes back to the obvious issue, a lot of system files were corrupted but not corrupted enough to prevent the computer from working properly. Computer worked fine in Safe mode with networking, spent dozens of hours in Safe Mode with Networking either running software or browsing the web and it never crashed. In MSCONFIG I put it into Diagnostic Startup (which disables all system services and the boot mode I tried Bootlog Base Video and OS Boot Information. I even try uninstalling all the drivers I could from device manager and rebooting into normal mode but had no luck, same stop code in Normal mode. The older versions of windows used to show Non PNP drivers that could be directly removed/uninstalled but in Windows 10, that is no longer available unfortunately.

Why are you doing all of this when you now have a fully functional Windows 10 installation on the SSD? I don't understand the reason you are going to all of this trouble when we know that the 1 TB HDD is bad. What is so special about the W10 installation on the 1 TB HDD that you need to save it and continue using it?

You just proved the problem is the 1 TB HDD since the W10 on the SSD does not crash in regular mode.

goku2 said:
My guess is, a corrupted driver or two are able to load into memory but because of a silently flipped bit here or there is causing the computer to crash as the driver behaves in a way it's not intended. Some system service or driver must have low level file corruption that can cause the computer to behave funny and crash not when it's loaded but when a certain section of the driver is utilized or called upon by the loading of another service or driver. If the hardware is 100% solid, I don't know what else can cause the kernel to crash.

I won't say NO to that; however, the corruption could be taking place during the loading or unloading process -- involving the 1 TB HDD. The hardware is NOT 100% solid because of the 1 TB HDD.

goku2 said:
Either way, since SFC works off of system file hashes, I was wondering, does SFC fix corrupted drivers in system32\drivers folder?

As far as I know - YES, but I am not a Windows Update/SFC/DISM/SFCFIX expert the way others around here are.

goku2 said:
It would appear that WinSXS is a repository for system drivers issued by Microsoft.

Yes. But not for all of the files. Our Windows Updates Experts often have to go outside to KBs and elsewhere to locate replacement files for files that SFC could not fix. Not all files are in \winsxs or elsewhere on your system.

goku2 said:
That would mean SFC should be able to utilize this now 100% working folder as a source to repair files within the SYSTEM32 and its driverstore or drivers folder. I figured that if at the very least, I replace all the corrupted system files with good ones from the WinSXS folder that there is a better chance of the system booting properly. When files get replaced, don't they get replaced with their proper ownership and ACL permissions?

Go trough our Windows Update forum and see the 1,000s of systems where SFC was unable to fix files.

I cannot answer the permission question as I do not know the answer.

goku2 said:
I know you have no intention of helping...

That is just not true! I have helped thousands here at Sysnative Forums; tens of thousands at TSF forums where I am an Administrator and a Manager, Microsoft Support - Tech Support Forum - View Profile: jcgriff2

Furthermore, I was a Microsoft Most Valuable Professional (MVP) for 7 years and was just named a Microsoft Windows Insider MVP - based on community/forum help.

I have been volunteering on these and many other forums since 2007 -- for over 11 years now and have never not helped someone when I could.

It is not because I do not want to help you, rather it is because I cannot help. I am not a Windows Update/CBS Log expert and know as much about the CBS Log entry you cited as you do.

My field for over 10 years now is BSODs with hundreds of thousands of BSOD dumps processed.

My advice here has not changed -- it is time to stop fooling around with the failing 1 TB HDD and use the W10 installation that runs successfully on the SSD. Again, I cannot figure you or this situation out as to why you want to continue to try and use a failing 1 TB HDD that has obviously caused massive file corruption and then led to BSODs stating the same thing.

This is an absolute mystery to me - as to why you are trying to save the W10 installation on the bad 1 TB HDD. I simply cannot figure it out.

goku2 said:
I know you have no intention of helping, but I still want to know, what are the dependencies and or software that I can use that will make SFC work properly in offline mode or can at least utilize the CBS logs to conduct the primitive installer file movements. The way I look at this problem is, SFC has identified a bunch of files that need to be replaced due to mismatch hashes. Why not replace all the files it has already identified first, hope the system boots up, then come back and work on the rest if necessary. If SFC can and does Hash checking for all the system files and drivers on the computer, and I can run this program in offline mode, I don't see why I can't run this program until its conclusion where it hash checks every file on the computer and replaces every file it deems necessary.

You are working with a bad 1 TB HDD. I don't care what clusters chkdsk has marked or anything else about it.

The HDD is bad and trying to fix anything on it is futile.

goku2 said:
Oh and here are the attached seatools scans. First is the Long Generic scan and the next is the SMART test. The most thorough way to check the drive is to check every sector sequentially but for a 1TB drive, I have no interest in doing that again as that took several days to conduct and I already know the drive is working reliably enough for these purposes.

You ran SeaTools for Windows, which means a good portion of the drive was not tested.

You must run SeaTools for DOS.

I know that you don't want to run it again, because the results will be the same -- the drive has bad sectors and is failing.

Regards. . .

John

goku2 · Aug 20, 2018

The original post as written by goku2 at 05:59 AM (GMT-5/ EDT) on Monday, August 20, 2018 is contained within the SPOILER tags below (Edited by jcgriff2):

Read More:

jcgriff2 said:
goku2 said:

To confirm it was a corrupted file issue, I also booted up the SSD and came up with the exact same stop code. From there, after booting into safe mode, I analyzed the dump files and the internal system logs and whatnot and figured I likely have some sort of bad driver or there is some system service that boots in normal but not in safe mode. I tried for the next month to isolate and figure out which service or driver was causing the crashes in normal mode but wasn't able to.

Click to expand...

 
Did you ever run Driver Verifier which would have analyzed every selected driver? 
 
Our instructions state to select non-Microsoft drivers, but in your case, you could have selected Microsoft drivers to try and prove your point. 
 
<a href="!29!bsod-crashes-kernel-debugging/29-driver-verifier-bsod-related-windows-10-8-1-8-7-vista.html" target="_blank">Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista</a>

I tried but didn't make any progress. When I read you had to run it in a 24 hour loop, that's when I realized that I probably should still try and fix all the corrupted system files first before worrying about system drivers as SFC and DISM were suppose to make my life easier. 
 
You're doing all of this with a bad HDD. I am no chkdsk expert, but once bad sectors show up, it's time for a new HDD or alternate SSD with a new Windows installation. The old HDD with the bad sectors becomes unreliable. I don't care how many bad sectors are marked unusable and you believe that the system will skip over them when writing new files. It does not always work that way - as you're dealing with a failing HDD. Why didn't you simply wipe the SSD and install Windows onto it, then connect the HDD to your system via PCIe or USB and retrieve wanted files? 
 
The time (1 month+ --??) that you have spent trying to fix the unfixable is mind boggling.[/quote] I did it because I wanted to know if I could do it. I wanted to know that if I was ever in a situation where I could not reinstall the OS install, that I'd be able to recover the OS. The whole point of installing Windows 10 over Windows 7 was that Windows 10 was suppose to be significantly easier to repair and more reliable. Instead, I'm no better off than before. At least with Windows XP, if I couldn't boot into safe mode, I could do a repair install right from the CD and I would lose nothing. There were a million different ways I could repair an XP install but this Vista crap is just a massive headache. Since this is not my computer, it's really not my problem either way if I can't get the software or data back. I was willing to invest the time into this if I knew I came out learning something new but instead I'm not much better off than when I started.

goku2 said:
I then decided to install Windows 1709 on the SSD on a second partition and when using SFC or DISM would reference this fresh windows install for source files.

So this is now the 3rd copy of this Windows 10 installation with the same keycode? Actually it's the 5th copy of Windows 10 on the same key code. No problems here. Want me to reinstall it again 50 more times to make a point that it does not matter? I'll get another drive, set it to GPT partition, make a bunch of partitions and then install windows 10 on all of them and get them activated as well. You obviously do not understand how the Windows 10 licensing scheme works. This isn't the Windows XP/Vista/7/8 licensing scheme.

goku2 said:
So that goes back to the obvious issue, a lot of system files were corrupted but not corrupted enough to prevent the computer from working properly. Computer worked fine in Safe mode with networking, spent dozens of hours in Safe Mode with Networking either running software or browsing the web and it never crashed. In MSCONFIG I put it into Diagnostic Startup (which disables all system services and the boot mode I tried Bootlog Base Video and OS Boot Information. I even try uninstalling all the drivers I could from device manager and rebooting into normal mode but had no luck, same stop code in Normal mode. The older versions of windows used to show Non PNP drivers that could be directly removed/uninstalled but in Windows 10, that is no longer available unfortunately.

Why are you doing all of this when you now have a fully functional Windows 10 installation on the SSD? I don't understand the reason you are going to all of this trouble when we know that the 1 TB HDD is bad. What is so special about the W10 installation on the 1 TB HDD that you need to save it and continue using it? 
[/quote] Has software that cannot be replaced because the lack of availability of product keys.

You just proved the problem is the 1 TB HDD since the W10 on the SSD does not crash in regular mode.

After cleaning up the bad sectors on the 1TB HDD, the drive became reliable. If I wiped the 1TB HDD, I can with absolute certainty say that I could fill the entire drive with data and I won't experience corruption. However, due to age, performance and the circumstances of needing the computer to be reliable in the next year (I won't be available to fix it) I opted to upgrade the drive. I already told you that I had imaged the HDD to the SSD to attempt the repairs but after a few weeks of fiddling, I failed. Then I went back to the HDD and since I was rushed, I failed at that as well. But not once since I fixed the bad sectors did the drive give me suspicion of failing. For the purposes of doing the data/drive recovery, the drive was reliable enough for me to conduct me work on it and I had some data backed up onto the SSD in the event it did actually fail completely while working on the data (which it never did).

goku2 said:
My guess is, a corrupted driver or two are able to load into memory but because of a silently flipped bit here or there is causing the computer to crash as the driver behaves in a way it's not intended. Some system service or driver must have low level file corruption that can cause the computer to behave funny and crash not when it's loaded but when a certain section of the driver is utilized or called upon by the loading of another service or driver. If the hardware is 100% solid, I don't know what else can cause the kernel to crash.

I won't say NO to that; however, the corruption could be taking place during the loading or unloading process -- involving the 1 TB HDD. The hardware is NOT 100% solid because of the 1 TB HDD. 
[/quote] Drives fine, you won't believe it but it is. That doesn't mean I wouldn't recommend replacement due to various factors but for my purposes, it's reliable.

goku2 said:
Either way, since SFC works off of system file hashes, I was wondering, does SFC fix corrupted drivers in system32\drivers folder?

As far as I know - YES, but I am not a Windows Update/SFC/DISM/SFCFIX expert the way others around here are.

goku2 said:
It would appear that WinSXS is a repository for system drivers issued by Microsoft.

Yes. But not for all of the files. Our Windows Updates Experts often have to go outside to KBs and elsewhere to locate replacement files for files that SFC could not fix. Not all files are in \winsxs or elsewhere on your system.

goku2 said:
That would mean SFC should be able to utilize this now 100% working folder as a source to repair files within the SYSTEM32 and its driverstore or drivers folder. I figured that if at the very least, I replace all the corrupted system files with good ones from the WinSXS folder that there is a better chance of the system booting properly. When files get replaced, don't they get replaced with their proper ownership and ACL permissions?

Go trough our Windows Update forum and see the 1,000s of systems where SFC was unable to fix files. 
 
I cannot answer the permission question as I do not know the answer.

goku2 said:
I know you have no intention of helping...

That is just not true! I have helped thousands here at Sysnative Forums; tens of thousands at TSF forums where I am an Administrator and a Manager, Microsoft Support - <a href="https://www.techsupportforum.com/forums/members/jcgriff2-185203.html" target="_blank" rel="nofollow">Tech Support Forum - View Profile: jcgriff2</a> 
 
Furthermore, I was a Microsoft Most Valuable Professional (MVP) for 7 years and was just named a Microsoft Windows Insider MVP - based on community/forum help. 
 
I have been volunteering on these and many other forums since 2007 -- for over 11 years now and have never not helped someone when I could. 
 
It is not because I do not want to help you, rather it is because I cannot help. I am not a Windows Update/CBS Log expert and know as much about the CBS Log entry you cited as you do. 
 
My field for over 10 years now is BSODs with hundreds of thousands of BSOD dumps processed. 
 
My advice here has not changed -- it is time to stop fooling around with the failing 1 TB HDD and use the W10 installation that runs successfully on the SSD. Again, I cannot figure you or this situation out as to why you want to continue to try and use a failing 1 TB HDD that has obviously caused massive file corruption and then led to BSODs stating the same thing. 
 
This is an absolute mystery to me - as to why you are trying to save the W10 installation on the bad 1 TB HDD. I simply cannot figure it out.

I'm sure you've helped a lot of people. However, long ago you've consigned yourself to not helping because of the circumstances.

goku2 said:
I know you have no intention of helping, but I still want to know, what are the dependencies and or software that I can use that will make SFC work properly in offline mode or can at least utilize the CBS logs to conduct the primitive installer file movements. The way I look at this problem is, SFC has identified a bunch of files that need to be replaced due to mismatch hashes. Why not replace all the files it has already identified first, hope the system boots up, then come back and work on the rest if necessary. If SFC can and does Hash checking for all the system files and drivers on the computer, and I can run this program in offline mode, I don't see why I can't run this program until its conclusion where it hash checks every file on the computer and replaces every file it deems necessary.

You are working with a bad 1 TB HDD. I don't care what clusters chkdsk has marked or anything else about it. 
 
The HDD is bad and trying to fix anything on it is futile.

goku2 said:
Oh and here are the attached seatools scans. First is the Long Generic scan and the next is the SMART test. The most thorough way to check the drive is to check every sector sequentially but for a 1TB drive, I have no interest in doing that again as that took several days to conduct and I already know the drive is working reliably enough for these purposes.

You ran SeaTools for Windows, which means a good portion of the drive was not tested. 
 
You must run SeaTools for DOS. 
 
I know that you don't want to run it again, because the results will be the same -- the drive has bad sectors and is failing. 
 
Regards. . . 
 
John[/QUOTE] 
 You erroneously believe that just because bad sectors show up on a drive, it HAS to be a failing drive. That is not true. The first time I experienced this phenomenon was about 17 years ago when I bought some brand new Western Digital drive and I was transferring over 150GB of data onto a 250GB HDD (from multiple smaller drives). What ended up happening after about 60gb of data written, I started getting CRC errors and a bunch of garbage data on the drive. I touched the drive and it was hot. Looked up the Smart information and saw the drive was 60C. I figured out that the bad sectors and garbage data was caused by the heat. After I realized what happened, I cooled off the drive, did a complete low level wipe so that none of the sectors would get remapped and I started it up again but this time I put a fan on the HDD while I was copying the data. No more data corruption. Over the next 10 years, I've noticed that the mechanical drives became increasingly less tolerant to heat exposure. Used to be able to handle 70C but now the drives can't handle anything more than 45C. Never had this issue back when drives were 80GB and smaller. Anyway, that's one example of how bad sectors can show up on a drive that is otherwise reliable and perfectly fine. There are a ton of other usage scenarios where you can write garbage sectors to a drive and make the drive think it needs to remap them but if you wipe the sectors with a low level utility, they don't get remapped. The only reason I decided I didn't want to use the 1TB HDD anymore is because the computer needed a performance upgrade and since the drive was 5 years old with bad sectors, I couldn't risk the drive failing 6 months from now when I won't be around to fix it if it does indeed fail. However, for the purpose of data recovery and getting a working OS, the drive was plenty reliable. Oh and BTW, according to Seagate, the Windows version of Seagate tools is not only better but more comprehensive than the old DOS version. The only reason to use the DOS version is because you do not have a copy of windows on hand. http://knowledge.seagate.com/articles/en_US/FAQ/202435en

The "Short Drive Self Test" is adequate for most situations. The “Short Generic” test is similar and tests various areas of the drive. If you need a more comprehensive test then consider running the “Long Generic”, which reads each sector on the drive. The long tests will take time to complete. Because the long tests read every sector on the drive, the amount of time required will depend on the speed and capacity of the disk drive. The apparent lack of activity often gives the impression that the drive or software has stopped responding.

It took about 4-5 hours to complete this long generic test. Obviously this software works faster than the low level crap I'm used to using as it can fully take advantage of the SATA interface.

NOTE:

I edited the above post to fix the BB Code (mostly fixing the QUOTE BB Code); removed most of the HTML code that originated from an unknown source; fixed other minor BB Code; all told, the edits made the readability of the post easier, in my opinion.

We (Sysnative Forums) do not take post editing without expressed permission by a Registered Member lightly, hence the reason some HTML code was left in (although it does not work).

Furthermore, I have left the original post in-tact above, hidden by the spoiler tags and have listed the edited post below.

If anyone has comments, concerns or questions about the editing done (or any other item), please send me a PM. Here is a direct link - https://www.sysnative.com/forums/private.php?do=newpm&u=1

The EDITED / FINAL post:

goku2 said:
To confirm it was a corrupted file issue, I also booted up the SSD and came up with the exact same stop code. From there, after booting into safe mode, I analyzed the dump files and the internal system logs and whatnot and figured I likely have some sort of bad driver or there is some system service that boots in normal but not in safe mode. I tried for the next month to isolate and figure out which service or driver was causing the crashes in normal mode but wasn't able to.

jcgriff2 said:
Did you ever run Driver Verifier which would have analyzed every selected driver?

Our instructions state to select non-Microsoft drivers, but in your case, you could have selected Microsoft drivers to try and prove your point.

<a href="!29!bsod-crashes-kernel-debugging/29-driver-verifier-bsod-related-windows-10-8-1-8-7-vista.html" target="_blank">Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista</a>

I tried but didn't make any progress. When I read you had to run it in a 24 hour loop, that's when I realized that I probably should still try and fix all the corrupted system files first before worrying about system drivers as SFC and DISM were suppose to make my life easier.

jcgriff2 said:
You're doing all of this with a bad HDD. I am no chkdsk expert, but once bad sectors show up, it's time for a new HDD or alternate SSD with a new Windows installation. The old HDD with the bad sectors becomes unreliable. I don't care how many bad sectors are marked unusable and you believe that the system will skip over them when writing new files. It does not always work that way - as you're dealing with a failing HDD. Why didn't you simply wipe the SSD and install Windows onto it, then connect the HDD to your system via PCIe or USB and retrieve wanted files?

The time (1 month+ --??) that you have spent trying to fix the unfixable is mind boggling.

I did it because I wanted to know if I could do it. I wanted to know that if I was ever in a situation where I could not reinstall the OS install, that I'd be able to recover the OS. The whole point of installing Windows 10 over Windows 7 was that Windows 10 was suppose to be significantly easier to repair and more reliable. Instead, I'm no better off than before. At least with Windows XP, if I couldn't boot into safe mode, I could do a repair install right from the CD and I would lose nothing. There were a million different ways I could repair an XP install but this Vista crap is just a massive headache. Since this is not my computer, it's really not my problem either way if I can't get the software or data back. I was willing to invest the time into this if I knew I came out learning something new but instead I'm not much better off than when I started.

goku2 said:
I then decided to install Windows 1709 on the SSD on a second partition and when using SFC or DISM would reference this fresh windows install for source files.

jcgriff2 said:
So this is now the 3rd copy of this Windows 10 installation with the same keycode?

Actually it's the 5th copy of Windows 10 on the same key code. No problems here. Want me to reinstall it again 50 more times to make a point that it does not matter? I'll get another drive, set it to GPT partition, make a bunch of partitions and then install windows 10 on all of them and get them activated as well. You obviously do not understand how the Windows 10 licensing scheme works. This isn't the Windows XP/Vista/7/8 licensing scheme.

goku2 said:
So that goes back to the obvious issue, a lot of system files were corrupted but not corrupted enough to prevent the computer from working properly. Computer worked fine in Safe mode with networking, spent dozens of hours in Safe Mode with Networking either running software or browsing the web and it never crashed. In MSCONFIG I put it into Diagnostic Startup (which disables all system services and the boot mode I tried Bootlog Base Video and OS Boot Information. I even try uninstalling all the drivers I could from device manager and rebooting into normal mode but had no luck, same stop code in Normal mode. The older versions of windows used to show Non PNP drivers that could be directly removed/uninstalled but in Windows 10, that is no longer available unfortunately.

jcgriff2 said:
Why are you doing all of this when you now have a fully functional Windows 10 installation on the SSD? I don't understand the reason you are going to all of this trouble when we know that the 1 TB HDD is bad. What is so special about the W10 installation on the 1 TB HDD that you need to save it and continue using it?

Has software that cannot be replaced because the lack of availability of product keys.

jcgriff2 said:
You just proved the problem is the 1 TB HDD since the W10 on the SSD does not crash in regular mode.

After cleaning up the bad sectors on the 1TB HDD, the drive became reliable. If I wiped the 1TB HDD, I can with absolute certainty say that I could fill the entire drive with data and I won't experience corruption. However, due to age, performance and the circumstances of needing the computer to be reliable in the next year (I won't be available to fix it) I opted to upgrade the drive. I already told you that I had imaged the HDD to the SSD to attempt the repairs but after a few weeks of fiddling, I failed. Then I went back to the HDD and since I was rushed, I failed at that as well. But not once since I fixed the bad sectors did the drive give me suspicion of failing. For the purposes of doing the data/drive recovery, the drive was reliable enough for me to conduct me work on it and I had some data backed up onto the SSD in the event it did actually fail completely while working on the data (which it never did).

goku2 said:
My guess is, a corrupted driver or two are able to load into memory but because of a silently flipped bit here or there is causing the computer to crash as the driver behaves in a way it's not intended. Some system service or driver must have low level file corruption that can cause the computer to behave funny and crash not when it's loaded but when a certain section of the driver is utilized or called upon by the loading of another service or driver. If the hardware is 100% solid, I don't know what else can cause the kernel to crash.

jcgriff2 said:
I won't say NO to that; however, the corruption could be taking place during the loading or unloading process -- involving the 1 TB HDD. The hardware is NOT 100% solid because of the 1 TB HDD.

Drives fine, you won't believe it but it is. That doesn't mean I wouldn't recommend replacement due to various factors but for my purposes, it's reliable.

goku2 said:
Either way, since SFC works off of system file hashes, I was wondering, does SFC fix corrupted drivers in system32\drivers folder?

jcgriff2 said:

As far as I know - YES, but I am not a Windows Update/SFC/DISM/SFCFIX expert the way others around here are.

Click to expand...

goku2 said:
It would appear that WinSXS is a repository for system drivers issued by Microsoft.

jcgriff2 said:

Yes. But not for all of the files. Our Windows Updates Experts often have to go outside to KBs and elsewhere to locate replacement files for files that SFC could not fix. Not all files are in \winsxs or elsewhere on your system.

Click to expand...

goku2 said:
That would mean SFC should be able to utilize this now 100% working folder as a source to repair files within the SYSTEM32 and its driverstore or drivers folder. I figured that if at the very least, I replace all the corrupted system files with good ones from the WinSXS folder that there is a better chance of the system booting properly. When files get replaced, don't they get replaced with their proper ownership and ACL permissions?

jcgriff2 said:
Go trough our Windows Update forum and see the 1,000s of systems where SFC was unable to fix files. Maybe that will answer your question(s).

I cannot answer the permission question as I do not know the answer.

goku2 said:
I know you have no intention of helping...

jcgriff2 said:
That is just not true! I have helped thousands here at Sysnative Forums; tens of thousands at TSF forums where I am an Administrator and a Manager, Microsoft Support - Tech Support Forum - View Profile: jcgriff2

Furthermore, I was a Microsoft Most Valuable Professional (MVP) for 7 years and was just named a Microsoft Windows Insider MVP - based on community/forum help.

I have been volunteering on these and many other forums since 2007 -- for over 11 years now and have never not helped someone when I could.

It is not because I do not want to help you, rather it is because I cannot help. I am not a Windows Update/CBS Log expert and know as much about the CBS Log entry you cited as you do.

My field for over 10 years now is BSODs with hundreds of thousands of BSOD dumps processed.

My advice here has not changed -- it is time to stop fooling around with the failing 1 TB HDD and use the W10 installation that runs successfully on the SSD. Again, I cannot figure you or this situation out as to why you want to continue to try and use a failing 1 TB HDD that has obviously caused massive file corruption and then led to BSODs stating the same thing.

This is an absolute mystery to me - as to why you are trying to save the W10 installation on the bad 1 TB HDD. I simply cannot figure it out.

I'm sure you've helped a lot of people. However, long ago you've consigned yourself to not helping because of the circumstances.

goku2 said:
I know you have no intention of helping, but I still want to know, what are the dependencies and or software that I can use that will make SFC work properly in offline mode or can at least utilize the CBS logs to conduct the primitive installer file movements. The way I look at this problem is, SFC has identified a bunch of files that need to be replaced due to mismatch hashes. Why not replace all the files it has already identified first, hope the system boots up, then come back and work on the rest if necessary. If SFC can and does Hash checking for all the system files and drivers on the computer, and I can run this program in offline mode, I don't see why I can't run this program until its conclusion where it hash checks every file on the computer and replaces every file it deems necessary.

jcgriff2 said:
You are working with a bad 1 TB HDD. I don't care what clusters chkdsk has marked or anything else about it.

The HDD is bad and trying to fix anything on it is futile.

goku2 said:
Oh and here are the attached seatools scans. First is the Long Generic scan and the next is the SMART test. The most thorough way to check the drive is to check every sector sequentially but for a 1TB drive, I have no interest in doing that again as that took several days to conduct and I already know the drive is working reliably enough for these purposes.

jcgriff2 said:
You ran SeaTools for Windows, which means a good portion of the drive was not tested.

You must run SeaTools for DOS.

I know that you don't want to run it again, because the results will be the same -- the drive has bad sectors and is failing.

Regards. . .

John

You erroneously believe that just because bad sectors show up on a drive, it HAS to be a failing drive. That is not true. The first time I experienced this phenomenon was about 17 years ago when I bought some brand new Western Digital drive and I was transferring over 150GB of data onto a 250GB HDD (from multiple smaller drives). What ended up happening after about 60gb of data written, I started getting CRC errors and a bunch of garbage data on the drive. I touched the drive and it was hot. Looked up the Smart information and saw the drive was 60C. I figured out that the bad sectors and garbage data was caused by the heat. After I realized what happened, I cooled off the drive, did a complete low level wipe so that none of the sectors would get remapped and I started it up again but this time I put a fan on the HDD while I was copying the data. No more data corruption. Over the next 10 years, I've noticed that the mechanical drives became increasingly less tolerant to heat exposure. Used to be able to handle 70C but now the drives can't handle anything more than 45C. Never had this issue back when drives were 80GB and smaller. Anyway, that's one example of how bad sectors can show up on a drive that is otherwise reliable and perfectly fine. There are a ton of other usage scenarios where you can write garbage sectors to a drive and make the drive think it needs to remap them but if you wipe the sectors with a low level utility, they don't get remapped.The only reason I decided I didn't want to use the 1TB HDD anymore is because the computer needed a performance upgrade and since the drive was 5 years old with bad sectors, I couldn't risk the drive failing 6 months from now when I won't be around to fix it if it does indeed fail. However, for the purpose of data recovery and getting a working OS, the drive was plenty reliable. Oh and BTW, according to Seagate, the Windows version of Seagate tools is not only better but more comprehensive than the old DOS version. The only reason to use the DOS version is because you do not have a copy of windows on hand.How to use SeaTools for Windows | Seagate Support

goku2 said:
The "Short Drive Self Test" is adequate for most situations.The “Short Generic” test is similar and tests various areas of the drive. If you need a more comprehensive test then consider running the “Long Generic”, which reads each sector on the drive. The long tests will take time to complete. Because the long tests read every sector on the drive, the amount of time required will depend on the speed and capacity of the disk drive. The apparent lack of activity often gives the impression that the drive or software has stopped responding.

goku2 said:

It took about 4-5 hours to complete this long generic test. Obviously this software works faster than the low level crap I'm used to using as it can fully take advantage of the SATA interface.

Click to expand...

jcgriff2 · Aug 20, 2018

I have no idea what happened in the last post, but the QUOTing is off and HTML chars showed up making it almost impossible to read.

The Windows version of SeaTools is not more comprehensive than DOS version as the DOS version can read the entire disk; Windows cannot.

So what is so precious about the Windows OS on the 1 TB HDD?

It's NOT your computer??? Whose is it?

axe0 · Aug 20, 2018

Difficult to find, but this is the reason why the OS is important

Has software that cannot be replaced because the lack of availability of product keys

goku2 · Aug 20, 2018

jcgriff2 said:
I have no idea what happened in the last post, but the QUOTing is off and HTML chars showed up making it almost impossible to read.

The Windows version of SeaTools is not more comprehensive than DOS version as the DOS version can read the entire disk; Windows cannot.

So what is so precious about the Windows OS on the 1 TB HDD?

It's NOT your computer??? Whose is it?

That may be true if you're running seatools on the primary drive. However I ran seatools on an attached drive, not the primary os drive. While it's entirely possible there are a handful of sectors being utilized by the OS that cannot be read by the utility (though it can because IIRC the drive was dismounted when it was scanned), the point of the test was to see if there are any bad sectors. If the parts of the drive that are currently being utilized do not crash the system or generate a fault and all the other sectors NOT being utilized do not show any bad sectors, then I'd say with confidence that there is a .0001% chance of an umarked bad sector on the drive. Even if there is a bad sector here or there on a 1TB drive, as long as it's not increasing (which there has been nary of evidence of such a thing) then it's safe to say the drive is fine for now. I've worked with enough HDDs to know when one is about to kick the bucket.

Computer is my neighbor's.

jcgriff2 · Aug 20, 2018

I have no idea what happened in your last large post, but the QUOTing is off and HTML chars showed up making it almost impossible to read. Post #12 in this thread - Boot to Bluescreen in normal mode, Black screen in safe mode

The Windows version of SeaTools is not more comprehensive than DOS version as the DOS version can read the entire disk; Windows cannot.

EDIT: - You mentioned apps/programs for which you no longer have the keycode(s) for. ¹

EDIT: I ended up editing your last large post for readability reasons. Please see my notes.

________________________________________________

¹ Apps that can help obtain product key codes:
Magical Jelly Bean Keyfinder - KeyFinder | Magical Jelly Bean
NirSoft ProduKey - ProduKey - Recover lost product key (CD-Key) of Windows/MS-Office/SQL Server
Recover-Keys - Recover Keys. Product key finder, recover lost Windows product key
Belarc Advisor - Products: Belarc Advisor
Lazesoft Windows Key Finder - Free Windows Key Finder - Lazesoft Windows Key Finder
Winkeyfinder - https://www.lifewire.com/winkeyfinder-review-2625103
LicenseCrawler - http://www.klinzmann.name/licensecrawler.htm
KeyFinder Thing - https://keyfinderthing.net/
Product Key Finder - https://davehope.co.uk/projects/product-key-finder/
Abelssoft MyKeyFinder - https://www.abelssoft.de/en/windows/Helpers/MyKeyFinder
Windows Product Key Viewer - http://www.rjlsoftware.com/software/utility/winproductkey/
Free PC Audit - https://www.majorgeeks.com/files/details/free_pc_audit.html
Windows Product Key Finder Pro - https://www.gearboxcomputers.com/products/product-key-finder/
WinGuggle - https://downloads.tomsguide.com/WinGuggle,0301-61081.html
SIW - https://www.gtopala.com/
RockXP - https://www.portablefreeware.com/?id=462 (Likely that support ends with Windows XP)
SterJo Key Finder - https://download.cnet.com/SterJo-Key-Finder/3000-2094_4-75329775.html
Product Key Finder (OTT Solutions) - http://www.softpedia.com/get/System/System-Info/OTT-Product-Key-Finder.shtml
MSKeyViewer Plus - http://www.softpedia.com/get/System/System-Info/MSKeyViewer-Plus.shtml
Windows Product Key Informer - https://gallery.technet.microsoft.com/Windows-Product-Key-7110d573
Game Key Revealer - https://sites.google.com/site/cakirbey/gamekeyrevealer

Try installing a few and see if in fact the apps provide the key codes.

You had mentioned something about no system services running at some point in time. I don't see how this is possible. To check on system services that are currently running - run WMI -- #53 -

Windows Management Instrumentation (WMI) - (Windows 10, 8.1, 8, 7, Vista)

You can run the HTML version - https://www.sysnative.com/SysnativeTutorials/wmi/batch/service_h.bat

Or you can run the TEXT version - https://www.sysnative.com/SysnativeTutorials/wmi/batch/service_t.bat

Another WMI goodie - detailed listing of system drivers - WMI #61 - Windows Management Instrumentation (WMI) - (Windows 10, 8.1, 8, 7, Vista)

I know that one WMI command/ batch file provides installed apps/programs, but I cannot seem to locate it at this time.

Regards. . .

jcgriff2

jcgriff2 · Aug 20, 2018

Going through the above list, I hit one that requires payment. My apologies for that as that certainly was not my intention.

I do not have any monetary or other interest in any of the apps that I listed.

A lot of awesome tools - primarily LoadOrd, Process Explorer, AutoRuns, etc.. found in the SysInternals Suite, available free from Microsoft - Sysinternals Suite - Windows Sysinternals | Microsoft Docs

The 3 I mentioned - zip version --
LoadOrder - Windows Sysinternals | Microsoft Docs
Process Explorer - Windows Sysinternals | Microsoft Docs
Autoruns for Windows - Windows Sysinternals | Microsoft Docs

All are stand-alone executables; nothing to install. Direct EXE downloads - live.sysinternals.com - /
https://live.sysinternals.com/LoadOrd.exe
https://live.sysinternals.com/procexp.exe
https://live.sysinternals.com/autoruns.exe

Be sure to save each to Documents or Desktop. RIGHT-click on the EXE file, select "Run as Administrator"

These apps must be executed at an elevated/Admin level.

LoadOrd - displays the order in which drivers load beginning from power-on - from my system (Windows 8.1 x64):

Code:

Boot	WdfLoadGroup	n/a*	Wdf01000	@%SystemRoot%\system32\drivers\Wdf01000.sys,-1000	system32\drivers\Wdf01000.sys
Boot	Boot Bus Extender	7	acpiex	Microsoft ACPIEx Driver	System32\Drivers\acpiex.sys
Boot	Boot Bus Extender	2	msisadrv		System32\drivers\msisadrv.sys
Boot	Boot Bus Extender	3	pci	@machine.inf,%pci_svcdesc%;PCI Bus Driver	System32\drivers\pci.sys
Boot	Boot Bus Extender	10	isapnp		System32\drivers\isapnp.sys
Boot	Boot Bus Extender	11	vdrvroot	@vdrvroot.inf,%vdrvroot_svcdesc%;Microsoft Virtual Drive Enumerator	System32\drivers\vdrvroot.sys
Boot	Boot Bus Extender	n/a*	partmgr	@%SystemRoot%\system32\drivers\partmgr.sys,-100	System32\drivers\partmgr.sys
Boot	Boot Bus Extender	n/a*	pdc	@%SystemRoot%\system32\drivers\pdc.sys,-100	system32\drivers\pdc.sys
Boot	System Bus Extender	8	spaceport	@spaceport.inf,%Spaceport_ServiceDesc%;Storage Spaces Driver	System32\drivers\spaceport.sys
Boot	System Bus Extender	9	volmgr	@volmgr.inf,%volmgr_svcdesc%;Volume Manager Driver	System32\drivers\volmgr.sys
Boot	System Bus Extender	10	volmgrx	@%SystemRoot%\system32\drivers\volmgrx.sys,-100	System32\drivers\volmgrx.sys
Boot	System Bus Extender	6	vmbus	@%SystemRoot%\system32\vmbusres.dll,-1000	System32\drivers\vmbus.sys
Boot	System Bus Extender	17	nvraid		System32\drivers\nvraid.sys
Boot	System Bus Extender	18	pciide		System32\drivers\pciide.sys
Boot	System Bus Extender	19	intelide		System32\drivers\intelide.sys
Boot	System Bus Extender	20	viaide		System32\drivers\viaide.sys
Boot	System Bus Extender	22	b06bdrv	@netbvbda.inf,%vbd_srv_desc%;Broadcom NetXtreme II VBD	System32\drivers\bxvbda.sys
Boot	System Bus Extender	23	ebdrv	@netevbda.inf,%vbd_srv_desc%;Broadcom NetXtreme II 10 GigE VBD	System32\drivers\evbda.sys
Boot	System Bus Extender	25	pcmcia		System32\drivers\pcmcia.sys
Boot	System Bus Extender	n/a*	mountmgr	@%SystemRoot%\system32\drivers\mountmgr.sys,-100	System32\drivers\mountmgr.sys
Boot	SCSI Miniport	25	iaStorV	@iastorv.inf,%*PNP0600.DeviceDesc%;Intel RAID Controller Windows 7	System32\drivers\iaStorV.sys
Boot	SCSI Miniport	33	nvstor		System32\drivers\nvstor.sys
Boot	SCSI Miniport	34	LSI_SAS		System32\drivers\lsi_sas.sys
Boot	SCSI Miniport	64	LSI_SAS2		System32\drivers\lsi_sas2.sys
Boot	SCSI Miniport	65	LSI_SAS3		System32\drivers\lsi_sas3.sys
Boot	SCSI Miniport	66	LSI_SSS		System32\drivers\lsi_sss.sys
Boot	SCSI miniport	67	3ware		System32\drivers\3ware.sys
Boot	SCSI Miniport	68	mvumis		System32\drivers\mvumis.sys
Boot	SCSI Miniport	69	VSTXRAID	@vstxraid.inf,%Driver.DeviceDesc%;VIA StorX Storage RAID Controller Windows Driver	System32\drivers\vstxraid.sys
Boot	SCSI Miniport	70	megasas		System32\drivers\megasas.sys
Boot	SCSI Miniport	71	megasr		System32\drivers\megasr.sys
Boot	SCSI miniport	73	iaStorAV	@iastorav.inf,%iaStorAV.DeviceDesc%;Intel(R) SATA RAID Controller Windows	System32\drivers\iaStorAV.sys
Boot	SCSI miniport	74	amdsata		System32\drivers\amdsata.sys
Boot	SCSI miniport	75	amdxata		System32\drivers\amdxata.sys
Boot	SCSI miniport	76	amdsbs		System32\drivers\amdsbs.sys
Boot	SCSI miniport	79	arcsas	@arcsas.inf,%arcsas_ServiceName%;Adaptec SAS/SATA-II RAID Storport's Miniport Driver	System32\drivers\arcsas.sys
Boot	SCSI Miniport	80	vsmraid		System32\drivers\vsmraid.sys
Boot	SCSI Miniport	81	SiSRaid2		System32\drivers\SiSRaid2.sys
Boot	SCSI Miniport	82	SiSRaid4		System32\drivers\sisraid4.sys
Boot	SCSI Miniport	83	atapi	@mshdc.inf,%idechannel.DeviceDesc%;IDE Channel	System32\drivers\atapi.sys
Boot	SCSI Miniport	84	storahci	@mshdc.inf,%storahci_ServiceDescription%;Microsoft Standard SATA AHCI Driver	System32\drivers\storahci.sys
Boot	SCSI Miniport	85	stornvme	@stornvme.inf,%StorNVMe_ServiceDesc%;Microsoft Standard NVM Express Driver	System32\drivers\stornvme.sys
Boot	SCSI Miniport	86	stexstor		System32\drivers\stexstor.sys
Boot	SCSI miniport	88	iaStorA		System32\drivers\iaStorA.sys
Boot	SCSI Miniport	210*	ADP80XX		System32\drivers\ADP80XX.SYS
Boot	SCSI Miniport	259*	HpSAMD		System32\drivers\HpSAMD.sys
Boot	SCSI Class	4	EhStorTcgDrv	@ehstortcgdrv.inf,%EhStorTcgDrv.Desc%;Microsoft driver for storage devices supporting IEEE 1667 and TCG protocols	System32\drivers\EhStorTcgDrv.sys
Boot	SCSI Class	n/a*	EhStorClass	@%SystemRoot%\system32\drivers\EhStorClass.sys,-100	System32\drivers\EhStorClass.sys
Boot	FSFilter Infrastructure	1	FltMgr	@%SystemRoot%\system32\drivers\fltmgr.sys,-10001	system32\drivers\fltmgr.sys
Boot	FSFilter Bottom	n/a*	FileInfo	@%SystemRoot%\system32\drivers\fileinfo.sys,-100	System32\drivers\fileinfo.sys
Boot	FSFilter Compression	n/a*	Wof	Windows Overlay File System Filter Driver	
Boot	FSFilter Anti-Virus	n/a*	WdFilter	@%ProgramFiles%\Windows Defender\MpAsDesc.dll,-330	system32\drivers\WdFilter.sys
Boot	Filter	1	CLFS	@%SystemRoot%\system32\drivers\clfs.sys,-100	System32\drivers\CLFS.sys
Boot	Base	1	KSecDD		System32\Drivers\ksecdd.sys
Boot	Base	17	storvsc		System32\drivers\storvsc.sys
Boot	Base	n/a*	pcw	Performance Counters for Windows Driver	System32\drivers\pcw.sys
Boot	File System	n/a*	Fs_Rec		
Boot	NDIS Wrapper	n/a*	NDIS	@%SystemRoot%\system32\drivers\ndis.sys,-200	system32\drivers\ndis.sys
Boot	Cryptography	2	KSecPkg		System32\Drivers\ksecpkg.sys
Boot	PNP_TDI	3	Tcpip	@%SystemRoot%\system32\tcpipcfg.dll,-50003	System32\drivers\tcpip.sys
Boot	NDIS	19	WFPLWFS	@%SystemRoot%\System32\drivers\wfplwfs.sys,-6000	system32\DRIVERS\wfplwfs.sys
Boot	Extended Base	43	storflt	@%SystemRoot%\system32\vmstorfltres.dll,-1000	System32\drivers\vmstorfl.sys
Boot	Core*	2*	ACPI	@acpi.inf,%ACPI.SvcDesc%;Microsoft ACPI Driver	System32\drivers\ACPI.sys
Boot	PnP Filter*	7*	agp440	@machine.inf,%agp440_svcdesc%;Intel AGP Bus Filter	System32\drivers\agp440.sys
Boot	Core*	4*	CNG		System32\Drivers\cng.sys
Boot	n/a*	n/a*	disk	@disk.inf,%disk_ServiceDesc%;Disk Driver	System32\drivers\disk.sys
Boot	PNP Filter*	15*	edevmon	edevmon	system32\DRIVERS\edevmon.sys
Boot	Early-Launch*	1*	eelam	eelam	system32\DRIVERS\eelam.sys
Boot	PnP Filter*	5*	fvevol	@%SystemRoot%\system32\drivers\fvevol.sys,-100	System32\DRIVERS\fvevol.sys
Boot	PnP Filter*	5*	gagp30kx	@machine.inf,%gagp30kx_svcdesc%;Microsoft Generic AGPv3.0 Filter for K8 Processor Platforms	System32\drivers\gagp30kx.sys
Boot	PnP Filter*	12*	hpdskflt	@oem46.inf,%service_desc%;HP Filter	system32\DRIVERS\hpdskflt.sys
Boot	n/a*	n/a*	hwpolicy	@%systemroot%\system32\drivers\hwpolicy.sys,-101	System32\drivers\hwpolicy.sys
Boot	n/a*	n/a*	intelpep	@intelpep.inf,%INTELPEP.SVCDESC%;Intel(R) Power Engine Plug-in Driver	System32\drivers\intelpep.sys
Boot	Network*	n/a*	Mup	@%systemroot%\system32\drivers\mup.sys,-101	System32\Drivers\mup.sys
Boot	PnP Filter*	8*	nv_agp	@machine.inf,%agpnvidia_svcdesc%;NVIDIA nForce AGP Bus Filter	System32\drivers\nv_agp.sys
Boot	PnP Filter*	n/a*	rdyboost	ReadyBoost	System32\drivers\rdyboost.sys
Boot	*	n/a*	sbp2port	@sbp2.inf,%sbp2_ServiceDesc%;SBP-2 Transport/Protocol Bus Driver	System32\drivers\sbp2port.sys
Boot	PnP Filter*	6*	uagp35	@machine.inf,%uagp35_svcdesc%;Microsoft AGPv3.5 Filter	System32\drivers\uagp35.sys
Boot	PnP Filter*	9*	uliagpkx	@machine.inf,%uliagpkx_svcdesc%;Uli AGP Bus Filter	System32\drivers\uliagpkx.sys
Boot	n/a*	n/a*	volsnap	@volume.inf,%VolumeClassName%;Storage volumes	System32\drivers\volsnap.sys
Boot	Early-Launch*	n/a*	WdBoot	@%ProgramFiles%\Windows Defender\MpAsDesc.dll,-390	system32\drivers\WdBoot.sys
System	SCSI CDROM Class	3	cdrom	@cdrom.inf,%cdrom_ServiceDesc%;CD-ROM Driver	\SystemRoot\System32\drivers\cdrom.sys
System	FSFilter Anti-Virus	2	eamonm	eamonm	system32\DRIVERS\eamonm.sys
System	Base	1	Null		
System	Base	2	Beep	Beep	
System	Base	32	ehdrv	ehdrv	\SystemRoot\system32\DRIVERS\ehdrv.sys
System	Video	3	BasicRender		\SystemRoot\System32\drivers\BasicRender.sys
System	Video	4	BasicDisplay		\SystemRoot\System32\drivers\BasicDisplay.sys
System	File system	n/a*	Msfs		
System	File system	n/a*	Npfs		
System	PNP_TDI	4	tdx	@%SystemRoot%\system32\tcpipcfg.dll,-50004	\SystemRoot\system32\DRIVERS\tdx.sys
System	PNP_TDI	n/a*	AFD	@%systemroot%\system32\drivers\afd.sys,-1000	\SystemRoot\system32\drivers\afd.sys
System	PNP_TDI	n/a*	NetBT	@%SystemRoot%\system32\drivers\netbt.sys,-2	System32\DRIVERS\netbt.sys
System	NDIS	13	Psched	@%SystemRoot%\System32\drivers\pacer.sys,-101	\SystemRoot\system32\DRIVERS\pacer.sys
System	NDIS	27	vwififlt	@%SystemRoot%\System32\drivers\vwififlt.sys,-259	\SystemRoot\system32\DRIVERS\vwififlt.sys
System	NDIS	30	epfwwfp	epfwwfp	\SystemRoot\system32\DRIVERS\epfwwfp.sys
System	NetBIOSGroup	2	NetBIOS	@netnb.inf,%NetBIOS_Desc%;NetBIOS Interface	system32\DRIVERS\netbios.sys
System	n/a*	n/a*	ahcache	@%systemroot%\system32\drivers\ahcache.sys,-102	system32\DRIVERS\ahcache.sys
System	n/a*	n/a*	dam	@%SystemRoot%\system32\drivers\dam.sys,-100	system32\drivers\dam.sys
System	Network*	n/a*	Dfsc	@%systemroot%\system32\wkssvc.dll,-1008	System32\Drivers\dfsc.sys
System	*	n/a*	mssmbios	@mssmbios.inf,%mssmbios_svcdesc%;Microsoft System Management BIOS Driver	\SystemRoot\System32\drivers\mssmbios.sys
System	*	n/a*	npsvctrig	@npsvctrig.inf,%NPSVCTRIG.SvcDisplayName%;Named pipe service trigger provider	\SystemRoot\System32\drivers\npsvctrig.sys
System	n/a*	n/a*	nsiproxy	@%SystemRoot%\system32\drivers\nsiproxy.sys,-2	system32\drivers\nsiproxy.sys
System	Network*	4*	rdbss	@%systemroot%\system32\wkssvc.dll,-1000	system32\DRIVERS\rdbss.sys
System	n/a*	n/a*	VBoxDrv	VirtualBox Service	\SystemRoot\system32\DRIVERS\VBoxDrv.sys
System	n/a*	n/a*	VBoxUSBMon	VirtualBox USB Monitor Driver	\SystemRoot\system32\DRIVERS\VBoxUSBMon.sys
System	n/a*	n/a*	Wanarpv6	@%systemroot%\system32\rascfg.dll,-32012	\SystemRoot\system32\DRIVERS\wanarp.sys
Automatic	FSFilter Virtualization	n/a*	luafv	@%systemroot%\system32\drivers\luafv.sys,-100	\SystemRoot\system32\drivers\luafv.sys
Automatic	Base	n/a*	ekrn	ESET Service	"C:\Program Files\ESET\ESET NOD32 Antivirus\ekrn.exe"
Automatic	COM Infrastructure	n/a*	BrokerInfrastructure	@%windir%\system32\bisrv.dll,-100	%SystemRoot%\system32\svchost.exe -k DcomLaunch
Automatic	COM Infrastructure	n/a*	DcomLaunch	@combase.dll,-5012	%SystemRoot%\system32\svchost.exe -k DcomLaunch
Automatic	COM Infrastructure	n/a*	LSM	@%windir%\system32\lsm.dll,-1001	%SystemRoot%\system32\svchost.exe -k DcomLaunch
Automatic	COM Infrastructure	n/a*	RpcEptMapper	@%windir%\system32\RpcEpMap.dll,-1001	%SystemRoot%\system32\svchost.exe -k RPCSS
Automatic	COM Infrastructure	n/a*	RpcSs	@combase.dll,-5010	%SystemRoot%\system32\svchost.exe -k rpcss
Automatic	Event Log	n/a*	EventLog	@%SystemRoot%\system32\wevtsvc.dll,-200	%SystemRoot%\System32\svchost.exe -k LocalServiceNetworkRestricted
Automatic	ProfSvc_Group	n/a*	gpsvc	@gpapi.dll,-112	%systemroot%\system32\svchost.exe -k netsvcs
Automatic	profsvc_group	n/a*	ProfSvc	@%systemroot%\system32\profsvc.dll,-300	%systemroot%\system32\svchost.exe -k netsvcs
Automatic	ProfSvc_Group	n/a*	SENS	@%SystemRoot%\system32\Sens.dll,-200	%SystemRoot%\system32\svchost.exe -k netsvcs
Automatic	ProfSvc_Group	n/a*	Themes	@%SystemRoot%\System32\themeservice.dll,-8192	%SystemRoot%\System32\svchost.exe -k netsvcs
Automatic	AudioGroup	n/a*	AudioEndpointBuilder	@%SystemRoot%\system32\AudioEndpointBuilder.dll,-204	%SystemRoot%\System32\svchost.exe -k LocalSystemNetworkRestricted
Automatic	AudioGroup	n/a*	Audiosrv	@%SystemRoot%\system32\audiosrv.dll,-200	%SystemRoot%\System32\svchost.exe -k LocalServiceNetworkRestricted
Automatic	AudioGroup	n/a*	FontCache	@%systemroot%\system32\FntCache.dll,-100	%SystemRoot%\system32\svchost.exe -k LocalService
Automatic	AudioGroup	n/a*	STacSV	@%SystemRoot%\system32\stlang64.dll,-10101	C:\Program Files\IDT\WDM\STacSV64.exe
Automatic	MS_WindowsLocalValidation	n/a*	SamSs	@%SystemRoot%\system32\samsrv.dll,-1	%SystemRoot%\system32\lsass.exe
Automatic	Plugplay	n/a*	Power	@%SystemRoot%\system32\umpo.dll,-100	%SystemRoot%\system32\svchost.exe -k DcomLaunch
Automatic	PlugPlay	n/a*	TabletInputService	@%SystemRoot%\system32\TabSvc.dll,-100	%SystemRoot%\System32\svchost.exe -k LocalSystemNetworkRestricted
Automatic	NDIS	15	rspndr	@%SystemRoot%\system32\lltdres.dll,-5	\SystemRoot\system32\DRIVERS\rspndr.sys
Automatic	NDIS	16	lltdio	@%SystemRoot%\system32\lltdres.dll,-6	\SystemRoot\system32\DRIVERS\lltdio.sys
Automatic	NDIS	17	NativeWifiP	@%SystemRoot%\System32\drivers\nwifi.sys,-101	\SystemRoot\system32\DRIVERS\nwifi.sys
Automatic	TDI	n/a*	Dhcp	@%SystemRoot%\system32\dhcpcore.dll,-100	%SystemRoot%\system32\svchost.exe -k LocalServiceNetworkRestricted
Automatic	TDI	n/a*	Dnscache	@%SystemRoot%\System32\dnsapi.dll,-101	%SystemRoot%\system32\svchost.exe -k NetworkService
Automatic	TDI	n/a*	lmhosts	@%SystemRoot%\system32\lmhsvc.dll,-101	%SystemRoot%\system32\svchost.exe -k LocalServiceNetworkRestricted
Automatic	TDI	n/a*	Wcmsvc	@%SystemRoot%\System32\wcmsvc.dll,-4097	%SystemRoot%\system32\svchost.exe -k LocalServiceNetworkRestricted
Automatic	TDI	n/a*	WlanSvc	@%SystemRoot%\System32\wlansvc.dll,-257	%SystemRoot%\system32\svchost.exe -k LocalSystemNetworkRestricted
Automatic	ShellSvcGroup	n/a*	ShellHWDetection	@%SystemRoot%\System32\shsvcs.dll,-12288	%SystemRoot%\System32\svchost.exe -k netsvcs
Automatic	SchedulerGroup	n/a*	Schedule	@%SystemRoot%\system32\schedsvc.dll,-100	%systemroot%\system32\svchost.exe -k netsvcs
Automatic	SpoolerGroup	n/a*	Spooler	@%systemroot%\system32\spoolsv.exe,-1	%SystemRoot%\System32\spoolsv.exe
Automatic	SmartCardGroup	n/a*	WbioSrvc	@%systemroot%\system32\wbiosrvc.dll,-100	%SystemRoot%\system32\svchost.exe -k WbioSvcGroup
Automatic	NetworkProvider	n/a*	BFE	@%SystemRoot%\system32\bfe.dll,-1001	%systemroot%\system32\svchost.exe -k LocalServiceNoNetwork
Automatic	NetworkProvider	n/a*	LanmanWorkstation	@%systemroot%\system32\wkssvc.dll,-100	%SystemRoot%\System32\svchost.exe -k NetworkService
Automatic	NetworkProvider	n/a*	MpsSvc	@%SystemRoot%\system32\FirewallAPI.dll,-23090	%SystemRoot%\system32\svchost.exe -k LocalServiceNoNetwork
Automatic	n/a*	n/a*	AdobeARMservice	Adobe Acrobat Update Service	"C:\Program Files (x86)\Common Files\Adobe\ARM\1.0\armsvc.exe"
Automatic	n/a*	n/a*	AppHostSvc	@%windir%\system32\inetsrv\iisres.dll,-30011	%windir%\system32\svchost.exe -k apphost
Automatic	n/a*	n/a*	CryptSvc	@%SystemRoot%\system32\cryptsvc.dll,-1001	%SystemRoot%\system32\svchost.exe -k NetworkService
Automatic	n/a*	n/a*	DeviceAssociationService	@%SystemRoot%\system32\das.dll,-100	%SystemRoot%\system32\svchost.exe -k LocalSystemNetworkRestricted
Automatic	n/a*	n/a*	DiagTrack	@%SystemRoot%\system32\UtcResources.dll,-3001	%SystemRoot%\System32\svchost.exe -k utcsvc
Automatic	n/a*	n/a*	DPS	@%systemroot%\system32\dps.dll,-500	%SystemRoot%\System32\svchost.exe -k LocalServiceNoNetwork
Automatic	n/a*	n/a*	DSAService	Intel(R) Driver & Support Assistant	"C:\Program Files (x86)\Intel Driver and Support Assistant\DSAService.exe"
Automatic	n/a*	n/a*	EFS	@%SystemRoot%\system32\efssvc.dll,-100	%SystemRoot%\System32\lsass.exe
Automatic	n/a*	n/a*	ESRV_SVC_QUEENCREEK	Energy Server Service queencreek	"C:\Program Files\Intel\SUR\QUEENCREEK\x64\esrv_svc.exe" "--AUTO_START" "--start" "--start_options_registry_key" "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ESRV_SVC_QUEENCREEK\_start"
Automatic	n/a*	n/a*	EventSystem	@comres.dll,-2450	%SystemRoot%\system32\svchost.exe -k LocalService
Automatic	n/a*	n/a*	EvtEng	Intel(R) PROSet/Wireless Event Log	"C:\Program Files\Intel\WiFi\bin\EvtEng.exe"
Automatic	n/a*	n/a*	gupdate	Google Update Service (gupdate)	"C:\Program Files (x86)\Google\Update\GoogleUpdate.exe" /svc
Automatic	n/a*	n/a*	IAStorDataMgrSvc	Intel(R) Rapid Storage Technology	"C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe"
Automatic	n/a*	n/a*	ibtsiva	@oem81.inf,%SERVICE_NAME%;Intel Bluetooth Service	%SystemRoot%\system32\ibtsiva
Automatic	n/a*	n/a*	IJPLMSVC	Canon Inkjet Printer/Scanner/Fax Extended Survey Program	C:\Program Files (x86)\Canon\IJPLM\IJPLMSVC.EXE
Automatic	n/a*	n/a*	IKEEXT	@%SystemRoot%\system32\ikeext.dll,-501	%systemroot%\system32\svchost.exe -k netsvcs
Automatic	n/a*	n/a*	iphlpsvc	@%SystemRoot%\system32\iphlpsvc.dll,-500	%SystemRoot%\System32\svchost.exe -k NetSvcs
Automatic	n/a*	n/a*	jhi_service	Intel(R) Dynamic Application Loader Host Interface Service	"C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL\jhi_service.exe"
Automatic	n/a*	n/a*	LanmanServer	@%systemroot%\system32\srvsvc.dll,-100	%SystemRoot%\system32\svchost.exe -k netsvcs
Automatic	n/a*	n/a*	LMS	Intel(R) Management and Security Application Local Management Service	"C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\LMS\LMS.exe"
Automatic	n/a*	n/a*	MacriumService	Macrium Service	"C:\Program Files\Macrium\Common\MacriumService.exe"
Automatic	n/a*	n/a*	MMCSS	@%systemroot%\system32\mmcss.dll,-100	%SystemRoot%\system32\svchost.exe -k netsvcs
Automatic	Network*	6*	mrxsmb10	@%systemroot%\system32\wkssvc.dll,-1004	system32\DRIVERS\mrxsmb10.sys
Automatic	n/a*	n/a*	Ndu	@%SystemRoot%\system32\drivers\Ndu.sys,-10001	system32\drivers\Ndu.sys
Automatic	n/a*	n/a*	NlaSvc	@%SystemRoot%\System32\nlasvc.dll,-1	%SystemRoot%\System32\svchost.exe -k NetworkService
Automatic	n/a*	n/a*	nsi	@%SystemRoot%\system32\nsisvc.dll,-200	%systemroot%\system32\svchost.exe -k LocalService
Automatic	n/a*	n/a*	PcaSvc	@%SystemRoot%\system32\pcasvc.dll,-1	%systemroot%\system32\svchost.exe -k LocalSystemNetworkRestricted
Automatic	n/a*	n/a*	PEAUTH	PEAUTH	system32\drivers\peauth.sys
Automatic	n/a*	n/a*	RegSrvc	Intel(R) PROSet/Wireless Registry Service	"C:\Program Files\Common Files\Intel\WirelessCommon\RegSrvc.exe"
Automatic	n/a*	n/a*	sesvc	ShadowExplorer Service	"C:\Program Files (x86)\ShadowExplorer_SystemRostore_ShadowCopyFiles\sesvc.exe"
Automatic	n/a*	n/a*	SkypeUpdate	Skype Updater	"C:\Program Files (x86)\Skype\Updater\Updater.exe"
Automatic	n/a*	n/a*	sppsvc	@%SystemRoot%\system32\sppsvc.exe,-101	%SystemRoot%\system32\sppsvc.exe
Automatic	Network*	n/a*	srv	@%systemroot%\system32\srvsvc.dll,-102	System32\DRIVERS\srv.sys
Automatic	n/a*	n/a*	ss_conn_service	SAMSUNG Mobile Connectivity Service	"C:\Program Files (x86)\Samsung\USB Drivers\27_ssconn\conn\ss_conn_service.exe"
Automatic	n/a*	n/a*	stisvc	@%SystemRoot%\system32\wiaservc.dll,-9	%SystemRoot%\system32\svchost.exe -k imgsvc
Automatic	n/a*	n/a*	SysMain	@%SystemRoot%\system32\sysmain.dll,-1000	%systemroot%\system32\svchost.exe -k LocalSystemNetworkRestricted
Automatic	n/a*	n/a*	SystemEventsBroker	@%windir%\system32\SystemEventsBrokerServer.dll,-1001	%SystemRoot%\system32\svchost.exe -k DcomLaunch
Automatic	n/a*	n/a*	SystemUsageReportSvc_QUEENCREEK	Intel(R) System Usage Report Service SystemUsageReportSvc_QUEENCREEK	"C:\Program Files\Intel\SUR\QUEENCREEK\SurSvc.exe"
Automatic	n/a*	n/a*	tcpipreg	TCP/IP Registry Compatibility	System32\drivers\tcpipreg.sys
Automatic	n/a*	n/a*	TrkWks	@%SystemRoot%\system32\trkwks.dll,-1	%SystemRoot%\System32\svchost.exe -k LocalSystemNetworkRestricted
Automatic	ValiditySensors*	n/a*	valWBFPolicyService	Validity WBF Policy Service	C:\Windows\system32\valWBFPolicyService.exe
Automatic	n/a*	n/a*	Winmgmt	@%Systemroot%\system32\wbem\wmisvc.dll,-205	%systemroot%\system32\svchost.exe -k netsvcs
Automatic	n/a*	n/a*	wscsvc	@%SystemRoot%\System32\wscsvc.dll,-200	%SystemRoot%\System32\svchost.exe -k LocalServiceNetworkRestricted
Automatic	n/a*	n/a*	WSearch	Windows Search	%systemroot%\system32\SearchIndexer.exe /Embedding
Automatic	n/a*	n/a*	ZeroConfigService	Intel(R) PROSet/Wireless Zero Configuration Service	"C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe"

Process Explorer - Task Manager on steroids

AutoRuns - Lists start-up items in your system (click on "login" column).

Regards. . .

jcgriff2

jcgriff2 · Aug 20, 2018

I just have to ask - have you seen error code 0xc004e003 anywhere?

If so... 0xc004e003 = Product key already in use

You really cannot have 5 or 10 copies of Windows all with the same key code.

You will run into problems eventually.

jcgriff2 · Aug 20, 2018

Another great app from Microsoft SysInternals - ProcessMonitor - ProcMon

It records every disk + registry I/O.

Process Monitor - Windows Sysinternals | Microsoft Docs

Live SysInternals - https://live.sysinternals.com/Procmon.exe

Also, re: the key codes, it is possible to contact the authors of the apps/programs, explain your situation and try to obtain new key codes.

goku2 · Aug 21, 2018

jcgriff2 said:
I just have to ask - have you seen error code 0xc004e003 anywhere?

If so... 0xc004e003 = Product key already in use

You really cannot have 5 or 10 copies of Windows all with the same key code.

You will run into problems eventually.

What you don't understand about digital entitlement is that it's a uniquely generated product key that is specific to a machine. When you install Windows on a machine that has a digital entitlement code, you can do unlimited installs on that machine because that code is specific to that machine configuration. This is a feature that is unique to Windows 10. When I install windows, I do not provide a product key, I do the install, then when finished, connect to the internet, and the activation servers provide the product key. The issue with having too many activations on a product key is an issue that dates back to Windows XP activation nonsense and was likely an issue through Windows 8. But with Windows 10, as long as you have a digital entitlement, the system will be continually reactivated automatically when connected to the internet. Now if you use a Windows 10 product key, you may have issues if you decide to use that product key on several unique hardware installations. But since the hardware install is the same and unchanged when you reinstall Windows, there is no issue. The whole purpose of activation software is to make sure you're using that copy of Windows on a single machine.

Boot to Bluescreen in normal mode, Black screen in safe mode

Member

Attachments

Member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Member

Attachments

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Member

Attachments

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Administrator, BSOD Academy Instructor, Security Analyst

Member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Member

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Administrator,
BSOD Academy Instructor,
Security Analyst

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)