Solved BSOD - Stuck in Endless Startup Repair Loop

[Cheesenium]

Still getting the same error:

BAD_POOL_ERROR
*** STOP: 0x00000019 (0x00000000000000003, 0xFFFFFA8006C98C20, 0x0000000000000000, 0x0000000000000000)

And I still cannot boot into windows at all.

 

[VistaKing]

Does it always stop on C:\Windows\System32\drivers\BMLoad.sys

 

[Cheesenium]

Does it always stop on C:\Windows\System32\drivers\BMLoad.sys

Yes, it does. It either stop at BMLoad.sys or loads the login screen, then, BSOD.

 

[VistaKing]

Open Notepad . Inside Notepad paste the highlighted text inside notepad


start
LastRegBack: 2013-07-22 20:56
end


Click on File ====> Save As

File Name : Fixlist.txt

Save as type : All Files

Location : USB Flash Drive

Click on the [Save] button .

Open the FRST tool again inside System Recovery and click on the [Fix] button . Once complete it will create a new log called Fixlog.txt . Upload the new log created in your reply . It should be inside the usb drive .

 

[Cheesenium]

Here is the Fix Log:

Fix result of Farbar Recovery Tool (FRST written by Farbar) (x64) Version: 30-07-2013 03
Ran by SYSTEM at 2013-07-31 12:44:37 Run:3
Running from H:\
Boot Mode: Recovery
==============================================

DEFAULT hive was successfully copied to System32\config\HiveBackup
DEFAULT hive was successfully restored from registry back up.
SAM hive was successfully copied to System32\config\HiveBackup
SAM hive was successfully restored from registry back up.
SECURITY hive was successfully copied to System32\config\HiveBackup
SECURITY hive was successfully restored from registry back up.
SOFTWARE hive was successfully copied to System32\config\HiveBackup
SOFTWARE hive was successfully restored from registry back up.
SYSTEM hive was successfully copied to System32\config\HiveBackup
SYSTEM hive was successfully restored from registry back up.

==== End of Fixlog ====

Results: Still stuck in the Starting Windows with a Windows logo and a black background screen with no HDD activity.

 

[VistaKing]

Lets see something .

Can you remove the battery . Remove one or the memory sticks . Place the battery back in and turn on the laptop and see if it passes the Windows 7 logo .

 

[Cheesenium]

Alright, tried that, still the same outcome. Boot up until i see the Starting Windows screen with no HDD activity.

Got another blue screen with 0x000007E error.

 

[VistaKing]

Take a look at these links below

:ar: Download Kaspersky Rescue Disk 10

and this one will show you how to use Kaspersky Rescue Disk

:ar: How to start scan for viruses using Kaspersky Rescue Disk?

 

[Cheesenium]

Take a look at these links below

:ar: Download Kaspersky Rescue Disk 10

and this one will show you how to use Kaspersky Rescue Disk

:ar: How to start scan for viruses using Kaspersky Rescue Disk?

Scanned only the Disk Boot Sectors and Hidden Startup Objects. No threats found. Okay, this is getting really strange.

 

[VistaKing]

Ok no Rootkits . Select the C drive .

 

[Cheesenium]

I guess i'll just scan the C drive then. Scanning C drive now.

I managed to access to 3 minidumps files from the Rescue Disk with one of them that has yesterday's date. Trying to extract them out of the system and i'll post it here.

 

[VistaKing]

I will have someone take a look at them . I'm on an iPad

 

[Cheesenium]

I will have someone take a look at them . I'm on an iPad

No problem. Thanks for your help. I appreciate it as i manage to extract all my work files from the dead PC.

At least I can resume my work now on my secondary PC without needing to find another SATA cable.

Anyway, here are the minidumps that I could extract from the Windows folder by accessing the mounted files in the Rescue Disk.

 

[VistaKing]

I have asked someone to take a look at the dmp files .

 

[Cheesenium]

Using Blue Screen View, I have found out the cause of the BSOD was due to CI.dll and ntoskrnl.exe

However, after googling around, I found this tool: How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)?

I'll give it a short once the current virus scan on the Karspersky Rescue Disk finished.

 

[Cheesenium]

Failed to find any Trojan on the the PC's HDD with Karpesky Rescue Disk.

I really have no idea what to do now.

 

[VistaKing]

Lets see if you could try this

Get back to the Command Prompt in System Recovery

In the command prompt that shows
X:\Sources
Type in bcdedit | find "osdevice"

   Note

the | pipe symbol is the key above Enter . Hold shift down and press the key with \ on it

Press the enter key after you inputted the command . It will tell you the drive letter of Windows . It might say its os device partition=D:

Then type

SFC /SCANNOW /OFFBOOTDIR=c:\ /OFFWINDIR=d:\Windows

press ENTER

   Note

here we assume that c: is the boot partition, d: is the windows installation partition, you may need to change the drive letters
accordingly.

 

[Cheesenium]

deleted

 

[Cheesenium]

Anyway, I know my PC boots from C: and the OS is also in C: so, i just typed in this:

SFC /SCANNOW /OFFBOOTDIR=C:\ /OFFWINDIR=C:\WINDOWS

System has begun. Will post the results later.

 

[Cheesenium]

Also, when i took out my HDD for system scan, my old laptop's Avira manage to found a TR/Crypt.XPACK.Gen trojan. Delete it and hopefully it works this time.