Z77-DS3H. Corrupted bios on startup - backup bios - BSOD 0x0000007B

[Brogan]

Came home from work, had made zero changes to system, turned on computer saw:

"Bios corrupted, loading bios from backup"

Got about 2 seconds into the windows startup, then : BSOD - STOP: 0x0000007B (0xFFFFF880009A97E8, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x00000000000000000)

Launched the Startup Repair utility - could not repair. " cannot determine cause..."

- no restore points to use

- no system image to use for backup

- Memory diagnostic completed with no problems

Not sure how to try Safe mode because the bios does not offer it as an option.  Did a chkdsk from repair utility but it found nothing.  Still cannot  figure out how to save my files.

My system:
i5 3570K  3.4Ghz
Z77-ds3h version F3
16GB corsair RAM
Intel 520 SSD 180GB
GeForce 560ti 1GB
800w psu
Windows 7 x64

[Brogan]

I really have no idea what it could be because like I said, I have not made any changes recently.

I have never seen the Bios message @ startup before however.  Bios corrupted, loading bios from backup - then BSOD.

That has to be the cause.

[zerowing]

Unplug PSU power cord. Unplug ATX power connectors on the motherboard. Close CMOS jumper to clear CMOS. Then remove CMOS battery. Wait 2-5 minutes. Then put the battery back in. Plug ATX connectors and PSU power cord, see what happens.
If the motherboard won't start with either the automatic BIOS recovery procedure or like nothing happened before then your only option highly likely is requesting a RMA. The board would probably be defective.
Do you have a UPS protecting the PC ? Did you have any power outage recently ?
Usually a motherboard does that when electrical transients hit one or more capacitors in a system where there is no proper protection from power outages.

[Brogan]

^ tried that.  Same BSOD error.

I did a chkdsk in dos prompt and the file system had no problems.

So, likely the mobo is bad then?  I did not have any power outages, tho the outlet it is on has been flakey in the past.

How do I go about retrieving my files from th SSD now?  I have no prob going the RMA route, but for now, I have docs I can't afford to lose.

[zerowing]

^ tried that.  Same BSOD error.

I did a chkdsk in dos prompt and the file system had no problems.

So, likely the mobo is bad then?  I did not have any power outages, tho the outlet it is on has been flakey in the past.

How do I go about retrieving my files from th SSD now?  I have no prob going the RMA route, but for now, I have docs I can't afford to lose.

Just connect the SSD to another PC, internal connectors or with an external SATA->USB or SATA->eSATA case.
The files should be there unless the SSD got affected too.

[Brogan]

^ tried that.  Same BSOD error.

I did a chkdsk in dos prompt and the file system had no problems.

So, likely the mobo is bad then?  I did not have any power outages, tho the outlet it is on has been flakey in the past.

How do I go about retrieving my files from th SSD now?  I have no prob going the RMA route, but for now, I have docs I can't afford to lose.

Just connect the SSD to another PC, internal connectors or with an external SATA->USB or SATA->eSATA case.
The files should be there unless the SSD got affected too.

Got it.  Something like this should work, right?

http://www.amazon.com/Vantec-NexStar-eSATA-Adapter-CB-ESATAU3/dp/B0064J75IQ/ref=sr_1_4?s=electronics&ie=UTF8&qid=1363047652&sr=1-4&keywords=usb+3+to+sata+adapter

[zerowing]

That is an eSATA to USB adapter.
You need to connect the SSD which has a standard SATA internal interface to either USB2.0/3.0 or eSATA to turn it into an external portable device.
So you need a case with USB and eSATA connectors, like these:

http://www.amazon.com/Satechi-Aluminum-External-Enclosure-SATA-III/dp/B00ANSYPQY/ref=sr_1_1?s=electronics&ie=UTF8&qid=1363051991&sr=1-1&keywords=esata+usb+case

http://www.amazon.com/2-5-Inch-External-Enclosure-Tool-free-Installation/dp/B005B5G4S6/ref=sr_1_2?s=electronics&ie=UTF8&qid=1363051991&sr=1-2&keywords=esata+usb+case

[ex58]

Better you goggle "BSOD 0x0000007B " and you will found couse of it.

[Brogan]

Thanks zerowing, I thought I had the wrong thing.  However I was able to root thru some old cables an figure out how to connect the drive to another computer and it showed up without any problems.  My docs are safe.  Thanks again.  Do you suggest getting a new mobo, or RMA'ing the Z77?

ex58, that was one of the first things I did and could not find anything in common.  Lot of probs with XP, but nothing that says its a windows 7 prob.

[albabeti]

I had the same problem with a Dell Optiplex 330. I received the
STOP 0x0000007B(0xF78DA63C,0x0000034,0X x0000000,0x0000000 error message if I booted with Windows XP. I resolved the issue by the following actions

1.   On start up (Dell logo), press F2 to enter BIOS

2.   Expand the "Drives" section

3.   Go to "SATA Operation"

4.   Change this from "RAID Auto/AHCI" to "RAID Auto/ATA"

[dmdilks]

Launched the Startup Repair utility - could not repair. " cannot determine cause..."

Not sure how to try Safe mode because the bios does not offer it as an option.  Did a chkdsk from repair utility but it found nothing.  Still cannot  figure out how to save my files.

If you got into where you can repair windows there is more likely nothing wrong with the board. I had this on a computer where somebody had downloaded something and corrupted both his win 7 & 8.

If you have another hard drive put that in and load windows on it. If that works than you have something that corrupted windows. When windows is loading and you get to the logo screen that is when all your drivers start loading.

To get into safe mode when you just get pass the bios screen start hitting F8. Saving your files once you get windows loaded on another drive. Just plug the old drive back in and see if there is anything still on the drive.

[johnplayer]

CAUSE

There can be multiple causes for this problem. For details, please refer to Microsoft Knowledge Base Artircle 324103 titled "How to troubleshoot 'Stop 0x0000007B' errors in Windows XP". In the context of a BootManage Administrator driven unattended Windows installation, it is most likely that the problem is related to a missing, inappropriate or faulty third-party mass storage driver:

1. The Windows version does not contain a driver for the target system's mass storage host adapter.

2. An inappropriate or faulty third-party driver was added to the "textmode" part of the unattended Windows installation.

3. A third-party mass storage driver was added via "textmode", but the target PC's system disk requires the "standard" IDE driver.


http://www.deskdecode.com/how-to-fix-blue-screen-stop-error-7b-stop0x0000007b/

[shadowsports]

John,
Last post was 4/26/15.  This thread is over 2.5 months old