BSOD on vacation: Cannot log on to Windows

I opened my laptop today while on vacation in North Carolina and I get the start up repair screen. I've conducted the given repair options repeatedly (except for System image Recovery because I didn't bring the installation disc with me and Command Prompt) but I get the same thing over and over. When I looked up the information after it started up the following information was given.

Event Name: StartupRepairOffline
Signature01: 6.1.7600.16385
Signature02: 6.1.7600.16385
Signature03: unknown
Signature04: 21199512
Signature05: AutoFailover
Signature06: 17
Signature07: CorruptRegistry
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

I took a picture of the blue screen the the following technical information was given.

0x00000074 (0x0000000000000002, 0xFFFFF88002EE69e0, 0x0000000000000002, 0xFFFFFFFFC000009A)

If any of you know what this means, please tell me what I should do to fix the problem. Thanks!

ACMDogfight1997 said:

0x00000074 (0x0000000000000002, 0xFFFFF88002EE69e0, 0x0000000000000002, 0xFFFFFFFFC000009A)

Click to expand...

Hi ACMDogfight1997.

Boot into http://www.sevenforums.com/tutorials/666-advanced-boot-options.html > Last Known Good Configuration. Does it boot?

If not, try SFC /SCANNOW : Run in Command Prompt at Boot. Does it find and recover any corruption?

If still it does not boot, we have very limited things to try, but better you test your RAM modules for possible errors. Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.

"If not, try SFC /SCANNOW : Run in Command Prompt at Boot. Does it find and recover any corruption?"

I have tried scannow in the command prompt in the recovery options, it tells me this:

"Beginning system scan. This process will take some time.


There is a system repair pending which requires a reboot to complete. Restart Windows and run sfc again."

I restarted the laptop, went through the BSOD again, got back on the cmd prompt via recovery options, typed it again, said the same thing.

Am I doing something wrong or is this telling me something else?

I also did the last known good configuration thing, didn't work

And I can't do the memtest86+ thing because I didn't bring a flash drive or cd/dvd with me so I may have ran out of options.:devil:

So the situation is ....

• Last Known Good Configuration did not work. I was not expecting that it may work. But that is the first thing to try.
• SFC is not being able to recover the corruptions successfully.

Now, Memtest86+ is needed there, because ....

STOP 0x00000074: BAD_SYSTEM_CONFIG_INFO
Usual causes: System hive corruption, Missing registry keys/values, bad memory

Click to expand...

It is not that you dont have an alternative. You may follow the traditional methods of making an unbootable system work. Follow it: Troubleshooting Windows 7 Failure to Start

If that also fail to do nothing there, consider a Clean Reinstall - Factory OEM Windows 7 .... last resort.

But if memory problems are really there, nothing will be effective. So I think you should verify the health of the memory before proceeding to further steps.

EDIT: I should have paid attention. You said ....

ACMDogfight1997 said:

I didn't bring a flash drive or cd/dvd with me so I may have ran out of options.:devil:

Click to expand...

Sorry to say, you are really out of options. You need something to boot from, whichever you want to do next.

EDIT: I should have paid attention. You said ....

ACMDogfight1997 said:

I didn't bring a flash drive or cd/dvd with me so I may have ran out of options.:devil:

Click to expand...

Sorry to say, you are really out of options. You need something to boot from, whichever you want to do next.[/QUOTE]

Nvm, my brother brought his flash drive. Now I don't have to wait until I come home. Good for him. I'll respond to see what happens after I try to fix it.

If still it does not boot, we have very limited things to try, but better you test your RAM modules for possible errors.
Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.[/QUOTE]

Well my parents just bought a new flash drive (in considering that the tutorial said "Plug in an empty USB key drive",) downloaded the Auto-Installer for USB Key link as said in the tutorial, double clicked the file in the zip folder, reached the choose USB drive location and noticed something wrong. It doesn't display in which directory the USB is at (C:, D:, E:, etc.) and it wouldn't let me choose the directory where it is at. The flash drive my parents bought is a SanDisk Cruzer Glide 4GB which already has some files related to it on it. Can you tell me what's going on?

Format the flash drive and try again.

The files which are there are not needed for anything.

Well I have formatted the USB and still does the same thing. Not to worry though, I have just arrived home and I burned the iso version to a CD. It's running tests right now.

Also, in the Memtest forum, it said that if any errors are detected, I would have take out RAM sticks. If that means I would have to disassemble my laptop, I'll have to take it to my local PC repair shop to do that (because that's beyond my league, especially for a 17 year-old.)

Age is not the question, but experience is. If you feel yourself uncomfortable to do such jobs, you should take the help of someone who can do it.

Well it just went through 9 passes for around 29 hours and luckily there are no errors. Now what?

ACMDogfight1997 said:

Well it just went through 9 passes for around 29 hours and luckily there are no errors. Now what?

Click to expand...

STOP 0x00000074: BAD_SYSTEM_CONFIG_INFO

Usual causes: System hive corruption, Missing registry keys/values, bad memory

Click to expand...

Two of the possibilities are checked, nothing found.

Now, the other thing that you should have tried is to do a repair install. But it is not possible with a non-bootable system.

As the last resort, try it:
Troubleshooting Windows 7 Failure to Start

If it also fails, then you have to perform a clean install.

Well I don't know if that's going to work out right so I might as well have to perform a clean install by myself (which is an accomplishment I've done successfully before.) I probably wasn't able to create a recovery option before probably because it wouldn't let me for some reason :huh:. I hope it'll let me do that once I install all of the drivers. To bad that we couldn't reverse the issue. I've had a lot of good files that I wanted to keep on that thing. Never predicted that this could happen . Oh well, we all learn something new based on past mistakes. Thanks for the support anyways!

All the files can be saved.

http://www.sevenforums.com/tutorials/93347-copy-paste-windows-recovery-console.html

Thanks for telling me this! I guess not everything is in vein.