now all I get are BSOD's

It was bugcheck EF.

Consider clean install.

Bugcheck EF?? Errrr could you explain please, I'm out of my depth here...

There are many codes that can be created when operating systems have problems.
That was one of the many bugchecks.

OK, so is it fixable... do we know whats causing the kernal error...

- - - Updated - - -

Just got a fresh SRT file...

The srttrail.txt was old.
dism error messages.

So it's safe to say it's a registry error created by a failed automatic Windows update attempt then... so can you refer me to an area that deals with this type of problem please...

Hello b1gt1m ,

It was good to see you have made progress and have got as far as starting to boot until you receive a BSOD caused by bugcheck with code 0xEF. The memory.dmp file is useful.

From the dump file we can see that the system crashed at around 5s into the boot process
System Uptime: 0 days 0:00:04.967

The system was still loading and it appears to have got stuck while services.exe was running.
FAILURE_BUCKET_ID: 0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_6f712080_ntdll!NtTerminateProcess

I believe your system is still very mixed up and does not know where to find files and services. I managed to extract the environment variables and they show a very confused picture of your operating system with a mixture of C: drive and E: drive locations. I suspect your registry is still corrupted. See below for your environment settings:



I am not sure how you can correct this but hopefully it points you in the right direction. Somehow you need to get all the operating system onto one drive/partition.

@philc43 Allo! Sorry for the late reply, things have been more nutty than an M&S fruit cake in work at the moment, so runnin around like a blue assed fly sufferin from a bad curry!? Anyway, could you refer to post #146 for some background. Is there any way I can edit the system hive?

b1gt1m said:

@philc43 Allo! Sorry for the late reply, things have been more nutty than an M&S fruit cake in work at the moment, so runnin around like a blue assed fly sufferin from a bad curry!? Anyway, could you refer to post #146 for some background. Is there any way I can edit the system hive?

I've looked back at your approach - it was a great idea and almost worked. I think what you needed to do was change the drive letters associated with the partitions so that when you installed the new Windows it was on drive C and therefore used all the correct drive letters for the paths in the registry hive.

Then when you revert back you would need to change the drive letters again before copying the hive over. I have no idea if this would work but it just might fix the confusion generated by having the mixture of C and E drive pathways in your current system.

I'm going to attempt to edit and modify/repair the 'System Hive' as everything is on one partition now... I'll keep you informed...