Different BSOD behaviour on two systems

I have read the BSOD threads to see if there are any references to this particular problem. Especially
BSOD Analysis - Getting Started
As I couldn't spot any, I post this quick(ish) question to see if anyone can point me to a thread that covers it.

I have an Acer desktop that originally had XP Pro 32 bit. I wanted to try Win 7 before the XP EOL date, but I didn't like the dualboot method that MS provided some years ago. To get round that, I added a hard drive and loaded that with Win 7 Pro 32 bit. The XP was left untouched as it worked fine. That was about 6 years ago.

I carried on using XP but gradually transferred programmes and functions to the Win 7 HD. I kept the XP up to date, but by 2014 I only ever booted into the XP HD to use programmes that were not suitable for Win 7.
(Both the HDs were of course available to either OS to recover/copy any files I did not have on the OS in action at the time.)

Three months ago the XP OS was getting very dodgy and so I decided to upgrade it to Win 10 as a tryout, but leaving the Win 7 OS untouched on its dedicated HD. The compatibility check I ran showed severe limitations with the Acer, so in the end I upgraded the OS from XP to Win 7 Pro to give me a backup to be useful if the working Win 7 HD/OS ever gave me any trouble. (In the meantime I bought a refurbished 64 bit Lenovo desktop with a clean Win 10 Home license and installed that. It is that PC that I am using to send this question.)

Now the question!
The new Win 7 installation on what was the XP HD completed successfully and after LOTS of updates, booted correctly. But after a few days I got a BSOD on the original Win 7 HD when booting into that! Then it failed to boot at all. I tried a few minor things, including using the install DVD to Repair Startup.
It now will boot into Safe Mode with Networking. Trying any other boot option immediately gets BSOD - no Win 7 OS in any form.

Why? And what should I do to investigate?

I had a look at various threads/tutorials but couldn't find a basic step by step guide.

NOTE - the BSOD message about hardware or drivers cannot(?) refer to hardware as the whole PC is physically the same when booting from either HD. I do NOT plugin or switch on any hardware specifically for the HD I boot from.

If I can't avoid it happening again (!) I will try to take a photo before I restart.

Paul Black said:

Hi Snugglebugs,

BSOD - Posting Instructions => BSOD - Posting Instructions.

Thanks. But I wonder if there is any guide to how to investigate possible problems before making the file. Especially as I can't get the file if I can't boot the PC

I booted the Acer problem OS normally and after some seconds of the Win logo showing, the system crashed.
The error code on the screen was
STOP: 0X000000C9 (0X00000224, 0X94379DCE, 0X8C5C4E70, 0X00000005)

I then restarted the same OS in Safe mode with networking and when the system settled I ran the DM log collection exe which worked without any problems and collected the information to that desktop.

With a bit of maneuvering I have now transferred the information requested to this Lenovo PC so I can attach the zip file.

Now I hope that this wonderful forum can interpret the results for me

Thanks in advance!

Tony

axe0 said:

I noticed driver easy is installed, this kind of programs are programs you do not need.
Most, if not all, of the drivers you need you can get from your pc vendor or Windows Update.

If you installed any drivers with this program, use a system restore point or system backup. If neither are available and you don't want to go for a clean install,
- if you don't know what drivers were installed, check if these programs have logs of driver installations, if requested I can spit the logs for you to find out
- if you do know, go into device manager and revert the drivers.


I also noticed in your eventlog a lot of issues related to your hard drive, although these events are from a few months back, have you dealt with this? If not, just let me know and we'll have a look at the drives together.


Could you upload the kernel dump from C:\Windows\MEMORY.dmp to onedrive, google drive, dropbox or a similar service and post a share link in your next reply. Just for some investigation purposes, I noticed something I haven't seen before with the 0x9C and the minidumps do not have enough information to have a look at it.

Thanks - I do know some of the answers and write these below.

Driver Easy - DAMN - I got a trial of that from another website, and then realised it was a con. I thought I had got rid of it. I will see what is left and try and dump it. Not easy(?) as I have to use Safe Mode.

And no, I didn't install anything from it unless it tried to slip anything past me at the time.

The drive problem from a few months back may be from an installation of AOMEI Backupper on our networked computers. The installation may have been faulty as every time an automatic backup took place on one of them the information sent to the external hard drive via NAS caused a crash IF the NAS host PC was active on another programme at the sscheduled time. I reinstalled and shifted the drive plus NAS configuration to my Lenovo (Win 10) and haven't had any trouble since. But maybe the Win 7 drive still has rubbish on it? What do you think I should check? I have the Seagate check tools and can run those easily. What should I look for?

Kernel dump - I will find that and see if I can upload the file to Dropbox. I might not have time today.