BSOD On Unbootable Windows 7

The bugcheck and all the ntfs entries would suggest a problem with the storage system, but there is also an entry for Bitdefender,

Code:

*** ERROR: Module load completed but symbols could not be loaded for gzflt.sys
 gzflt+0x1f9f6

Interestingly that is a Bitdefender file system driver,

Driver Reference Table - gzflt.sys

The first easiest step would be to remove Bitdefender and see how it acts.

Hi derekimo

Thanks for replying

Unfortunately I couldn't use the standard Windows uninstaller because it was inaccessible, due to not being able to boot. However, I've gone in and manually the deleted the referenced file in your post.

I'm still receiving the BSOD and I've attached an updated MEMORY dump file to this post.

(The previous URL will be invalid and will be replaced with the new one by the time that you see this post.)

You're welcome.

The same driver is getting flagged in this dump,

Code:

*** ERROR: Module load completed but symbols could not be loaded for gzflt.sys
 gzflt+0x1f9f6

I have a theory about why that may be, I can't prove it but I think these larger dumps get updated instead of new ones getting created every time a new crash happens.

What ever, there is still enough reason to stay on my first suggestion.

Here's a tutorial on fixing unbootable systems,

Troubleshooting Windows 7 Failure to Boot

My next suggestion would be testing the drive with Seatools for DOS which is a bootable test,

SeaTools for DOS and Windows - How to Use

Option two.

You must have something bootable if you went in and deleted that file, that's not the best way to go about that but I understand why you tried.

Can you get into safe mode?

You should be able to uninstall in safe mode, and get rid of that dump file in C:\Windows so it has to create a new one.

If you can get into safe mode you can run the DMlog collector from there too, it's not ideal but it will at least give more info.

I'm guessing you don't have a minidump folder or you would be sending those.

Hi Derekimo

Hmm, I removed the gzflt.sys driver and before recreating the crash dump, I'm sure that I removed the previous crash dump before creating a new one, I'll try doing it again just incase...

Unfortunately Safe Mode isn't an option as I still get a BSOD.

Also, here's some more information that I forgot to mention in my first post.

I have been using a virtual disc image file based entirely on the corrupt Windows 7 installation which I created using Hyper-V and booting it through using the same program, this is how I was able to delete the aforementioned file.

I also have a feeling that my other computer that Hyper-V is on, is decting errors that my other PC isn't, since it's at least 3 years old...

So this is a VHD?

All indications are either disk or file corruption and since the was a file system driver I went that route.

Honestly, I'm not very savvy with virtual machines so I can only suggest what would be tried on actual hardware.

What do you mean your other PC? I'm getting confused here.

Hi Derekimo

Ok

So basically what I meant by my 'other pc' is referring to the original laptop that used the HDD that had the BSOD, so I decided to remove the HDD from the PC and insert it into a 2.5 HDD enclosure and used Hyper-V to get the VHD.

I've also been able to boot the HDD, but only the slimmed down Windows recovery environment.

OK, can you do anything in there?

Disk check? Remove Bitdefender? Run seatools?

Did it ever boot up normally like that?

Hi Derkimo

Answers To Your Questions

Will reply to question, Can you do anything in there later, I promise.

1. Is disk check the chkdsk command?
2. I decided to remove the BitDefender folder manually by simply deleting it, however, I wonder if there's a way to search for all files containing the keyword 'Bitdefender' in the details tab in properties. A person from Bitdefender told me to just delete the folder and remove any remaining items later.
3. SeaTools is specifically hardware based.
4. Unfortunately, it still didn't boot up