Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Started with 0xc0000225 and ended up with 0xc0000007b BSOD


  • Please log in to reply
13 replies to this topic

#1 zero50

zero50

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:03 PM

Posted 23 March 2018 - 06:37 PM

The last 5 days I've been trying to fix a really peculiar issue.

My system is set up like this:

500 GB Evo SSD - Windows Installation
1 TB WD Black HDD - Data Storage
3 External drives connected by USB
Focusrite Audio Device by USB
Dolphinbar (Device for Wii Emulation) by USB
DVD Reader/Writer drive by SATA
HDMI to HDMI splitter to Dell monitor
At the time of System Freeze, DAEMON tools Lite was emulating an ISO as a Dvd Drive.

It all started 5 days ago. I was browsing the web and at the same time managing my files with 3 external HDDs connected via USB. I was using Spacesniffer to see which huge files I did not need anymore.
I also had CCleaner cleaning up the System. At this point I had about 18-20 GB free space on the SSD.

Suddenly, I noticed that the SSD free drive space decreased significantly. I brought Spacesniffer to view only to see something really weird. There was a file in C:/ with a huge, seemingly random name (Capital letters and numbers) file, with no type, that kept getting bigger and bigger in front of my eyes.

In a matter of seconds, I opened "my computer" and saw that the SSD had only 1GB left.
And at that moment the whole system froze 100%. No ctrl + alt + del, just froze like a picture.
I had no choice but to do a hard reboot. And I was greeted by a this screen:
 

See the attached image.

[Error 0x0000225]

I can't really remember the course of events that followed exactly but I will try my best.
I removed all external devices from the machine.

F8 Repair would give the same exact error I think.
As did all the other options (Safe mode etc.)
I booted up a Windows 7 installation disk, but it couldn't find any Windows installations on the drive to restore!

I then used an Ubuntu Live usb to find the weird huge file and delete it (It was about 20GB and had no more space to grow.)
I then ran a Bitdefender Live usb to check and aside from some false positives the system was clean.
I tried various fixes I found online in Win7 disk's command line (Fixboot, Fixmbr, etc).
/Rebuildbcd found 1 installation but couldn't add it ("Element not found")
Nothing worked.

I switched the drives' SATA cables. No difference.
Tried different SATA ports.
I did a power reset of the system. Nothing.
Then I changed the BIOS settings to "Fail-Safe Defaults".
(Which I did not know then but changed the SATA mode from AHCI to IDE.)
I still couldn't boot though I saw more of the Windows boot animation than before.

I'm not really sure which of the two errors showed at this point.
The change though made Startup Repair see the Windows installation.
I ran it several times through System repair.
I think this is where the previous error stopped appearing and another took its place.

 

See the attached images for the error screen.

Error:
Oxc0000007b (0xFFFFF880009A97E8,0xFFFFFFFF0000034, 0x0000000000000000, 0x0000000000000000)


From this point, I tried everything I could find.
Medicat utilities, Hiren's CD, EasyRe, Paragon, etc. nothing worked. Some made weird changes to the BCD that I had to fix.

I managed to set it back to AHCI where it still gave me the same error and then I installed another Windows 7 instance on the 1TB HDD. The system installed, worked and booted great.

I did chkdsk /r /f 5-6 times from the W7 Instalaltion disk's Command line, only the first one did fix some corrupt files from what I can remember. SFC said everything is fine.
I copied some drivers that I read around could be at fault for the error from the new installation to the old.
Nothing. Switched the files back.

I saw then that in while trying to boot in safe mode it BSOD-ed when loading the driver aswbidsha.sys, which is from Avast Antivirus. I renamed the file, and then I got a BSOD at another Avast driver.
I renamed that one too, and then it happened again. I renamed the third one and rebooted.
And then it gave me a BSOD on Classpnp.sys.

I tried renaming it too, and then the BSOD happened at disk.sys.
At some point the Classpnp.sys file appeared again.
I tried changing all SCSI Miniport drivers in the registry to load at boot (By changing the "Start" value to 0).
It loaded them but kept BSOD-ing at Classpnp.sys.

I went to my mobo's site and got the correct AHCI drivers and loaded them up with Dism.
They load fine but still, BSOD at Classpnp.sys.

I unplugged my SATA DVD drive. No difference.
At some point, I did something and got stuck at cdfs.sys that time.
Things got worse, and I restored the "Regback" registry which put me back against classpnp.sys.

EasyRE had found a Restore snapshot in the drive.
I restored it. No change happened.

I tried booting to my TV with another HDMI cable.
I put the Focusrite back in. Nothing.

During all this I tried Startup repair about 55 times.
At later times everything checked fine with the exception of a 0x490 error, that System file integrity tried to fix and failed. Most startup repair log entries even said something along the lines of "The OS booted successfully." Unfortunately, I could not get a picture of the 0x490 error. SFC command though still reported that everything's fine.

The Startup Repairs always end with a message window that states that the problem can't be fixed automatically and with the following log:
 

See attached images for a picture of the log.

Log in Written form-
Problem Event Name: StartRepairOffline
Problem Signature 01: 6.1.7600.16.385
Problem Signature 02: 6.1.7600.16.385
Problem Signature 03: unknown
Problem Signature 04: ExternalMedia
Problem Signature 05: 11
Problem Signature 06: CorruptFile
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

I can't figure out what ExternalMedia means.
If it's external, it should be something that I can fix easily, right?

Anyway, some more things I tried:
Memtest86 for an hour and a half.
HDSentinel Pro. All great. Health 97% for SSD, 100% HDD.
Replacing Avast driver files with ones from another PC. Back to BSOD at Avast files.
Ran Malwarebytes and RogueKiller through the second installation. Nothing.

At this point, I really don't know what to do anymore.
I can't help but feel that even though this seems broken beyond hope, there exists a simple fix I can't grasp...

What do you think? I'm open to all suggestions...

 

Specs:

Intel 2500k (Was overclocked to 4.00 ghz at time of system Freeze)
Gigabyte GTX 650 Ti Boost
Corsair Vengeance 2133MHz 16GB Ram
Gigabyte Z68P- DS3 Motherboard
500GB Samsung Evo SSD
1TB WD Black HDD
Focusrite Solo Audio Device

Attached Files


Edited by zero50, 23 March 2018 - 06:37 PM.


BC AdBot (Login to Remove)

 


#2 RokTV

RokTV

  • Members
  • 133 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:03 PM

Posted 23 March 2018 - 07:12 PM

I suggest seeing if the Windows 7 disc will show the original Windows installation after trying the possible solution from >> Mann_Manohar replied on  April 2, 2014

 

https://answers.microsoft.com/en-us/windows/forum/all/windows-7-recovery-disk-operating-system-isnt/54ab7807-2326-4754-a734-6d61041a5cda



#3 zero50

zero50
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:03 PM

Posted 23 March 2018 - 07:20 PM

I suggest seeing if the Windows 7 disc will show the original Windows installation after trying the possible solution from >> Mann_Manohar replied on  April 2, 2014

 

https://answers.microsoft.com/en-us/windows/forum/all/windows-7-recovery-disk-operating-system-isnt/54ab7807-2326-4754-a734-6d61041a5cda

 

I've managed to make it see the original installation when I loaded the fail-safe defaults in the BIOS (That changed AHCI to IDE).

I stated that in my post (I don't blame you for missing it, it's a big wall of text )-: )

I've also tried that fix, making the System Reserved Partition Active. It did not work for me.... :(



#4 RokTV

RokTV

  • Members
  • 133 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:03 PM

Posted 23 March 2018 - 07:28 PM

I did miss that lol. See post number 5 https://www.bleepingcomputer.com/forums/t/477609/virus-that-caused-windows-7-64bit-startup-repair-loop/ If you have tried that, it is another thing that I have missed.


Edited by RokTV, 23 March 2018 - 07:30 PM.


#5 zero50

zero50
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:03 PM

Posted 23 March 2018 - 07:28 PM

Today I run extensive scans with Eset Antivirus Rescue Live usb and nothing was found.

I've also tried resetting 100% the bios settings by touching the the clr_cmos pins in the mobo with a screwdriver.

That made my heart skip a beat when the booting animation almost completed, but once again I got the BSOD...

 

Geez... Any ideas are welcome... Especially about that "ExternalMedia" entry in the last log.

The only External device I have now connected is the monitor via HDMI  and the wireless mouse and keyboard dongle by microsoft.

 

I have tried to boot without those too and I still got the BSOD...



#6 zero50

zero50
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:03 PM

Posted 23 March 2018 - 07:30 PM

Oh, I haven't seen that thread. Let's see....



#7 zero50

zero50
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:03 PM

Posted 23 March 2018 - 07:33 PM

 

Oh, I haven't seen that thread. Let's see....

 

 

Hmm... Ok I think I've tried this fix too. Deleting the bcd and then recreating it.

I can't remember if I used this command though:

 

attrib bcd -s -h -r

 

I remember doing an attrib command at some point but I'm not sure...

What does it do?



#8 zero50

zero50
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:03 PM

Posted 23 March 2018 - 07:43 PM

Ok, I've tried it. No change.

I don't think this is a boot file issue anymore.

I think it is a driver issue...



#9 RokTV

RokTV

  • Members
  • 133 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:03 PM

Posted 23 March 2018 - 08:11 PM

Does EasyRE do the same as Windows System Restore, replaces the same files as Windows?


 

 

Oh, I haven't seen that thread. Let's see....

 

 

Hmm... Ok I think I've tried this fix too. Deleting the bcd and then recreating it.

I can't remember if I used this command though:

 

attrib bcd -s -h -r

 

I remember doing an attrib command at some point but I'm not sure...

What does it do?

 

 

+   Sets an attribute.
 
-   Clears an attribute.

 

S   System file attribute.
 
H   Hidden file attribute.
 
R   Read-only file attribute.

Edited by RokTV, 23 March 2018 - 08:13 PM.


#10 RokTV

RokTV

  • Members
  • 133 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:03 PM

Posted 23 March 2018 - 08:24 PM

Have you tried Last Known Good Configuration?  http://www.thewindowsclub.com/benefits-good-configuration-windows-7



#11 zero50

zero50
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:03 PM

Posted 23 March 2018 - 09:25 PM

Have you tried Last Known Good Configuration?  http://www.thewindowsclub.com/benefits-good-configuration-windows-7

 

Yes, many times... No change...



#12 zero50

zero50
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:03 PM

Posted 23 March 2018 - 09:30 PM

 

Does EasyRE do the same as Windows System Restore, replaces the same files as Windows?


 

 

Oh, I haven't seen that thread. Let's see....

 

 

Hmm... Ok I think I've tried this fix too. Deleting the bcd and then recreating it.

I can't remember if I used this command though:

 

attrib bcd -s -h -r

 

I remember doing an attrib command at some point but I'm not sure...

What does it do?

 

 

+   Sets an attribute.
 
-   Clears an attribute.

 

S   System file attribute.
 
H   Hidden file attribute.
 
R   Read-only file attribute.

 

 

I think so, yeah. Seems like a good tool, maybe better than WinRe but it did not fix the issue. )-:



#13 RokTV

RokTV

  • Members
  • 133 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:03 PM

Posted 23 March 2018 - 10:56 PM

Does EasyRE do the same as Windows System Restore, replaces the same files as Windows?



#14 zero50

zero50
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:03 PM

Posted 24 March 2018 - 05:17 AM

Does EasyRE do the same as Windows System Restore, replaces the same files as Windows?


I think so, yeah.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users