System Recovered with Symantec System Recovery fails to boot with Error : STOP : 0x0000007B...
|Article:TECH165385|||||Created: 2011-07-24|||||Updated: 2014-05-20|||||Article URL http://www.symantec.com/docs/TECH165385|
A system recovered using Symantec System Recovery fails to boot with the following BSOD error and do not log any error information in kernel memory dump.
STOP : 0x0000007B (0xfFFFF880009A9928, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)
This can happen due to any of the following reasons.
- If Windows is not able to load the disk controller drivers for the system.
- Also in case the correct drivers for the NIC card is not provided.
- Missing or corrupt driver file -atapi.sys.
As Windows is not able to access the disk using the appropriate drivers, it fails to log any information during startup so kernel memory dump is not created.
- Fully functional System with same OS and service pack levels as on the system that needs to be restored.
- USB hard drive/thumb drive.
- System Recovery Disk (SRD).
- Copy the file atapi.sys from C:\windows\system32\drivers\ to USB drive of the working system.
- Use the SRD to boot the system that needs to be restored.
- Use browse my computer feature in recovery console to copy the atapi.sys file from the USB drive and place it in C drive of the system to be recovered. (same location C:\windows\system32\drivers\)
- Reboot the system.
- Start the System and enter the advance boot menu [F8] during startup.
- At the startup screen, select Last Known Good Configuration.
Note: The C drive is illustration. It can be any system drive with different drive letter assigned to it.
- Try to Repair the System using Windows Installation CD.
Not all hardware manufacturers give this option.
- Boot the system in BIOS mode.
- Change "Sata Controller Mode" from AHCI to RAID (If RAID configured on the system).
- Change "Sata Controller Mode" from RAID to AHCI (If RAID not configured on the system).
Article URL http://www.symantec.com/docs/TECH165385