Solved BSOD 1033 BCCode:1033 can not boot

[Tillysaint]

Yesterday I got the latest Microsoft Windows 7 updates, 16 in all! I selected the custom installation and watched. It took a long time especially the Malware update. It restarted a couple of times and during the last restart I got the BSOD below.

When I turn the computer on, it goes immediately to a blinking cursor. Tried PF 8, nothing. I was able to get to the HP Recovery Manager and ran all the HP tests. Every is OK. I ran the sfc /scannow and received a message that said a recovery action is pending and do a restart. When I restart I still immediately get the blinking cursor. Since I can't reboot, I can't send you the info you would like.

I looked for a similar post but couldn't find one that matched my problem. Thanks for the help, Tilly

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: c200
BCP1: 00000000000007
BCP2: 000000000000109B
BCP3: 0000000004040008
BCP4: FFFFFA8009265960
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\101514-80902-01.dmp
C:\Users\Ron\AppData\Local\Temp\WER-125393-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[Boozad]

http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[Tillysaint]

How do I comply to the BSOD Posting Instructions when I can't access my system for that information? I can't boot etc. I provided the info that I could. Where else should I post? Please advise! Thanks. Tilly Saint

 

[Boozad]

Apologies, I'm not quite sure how I missed that pertinent piece of information. Take a read through http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html and see if anything helps.

 

[Arc]

Hi Gav, please dont mind my friend. I want to verify a little thing.

Additional information about the problem:
BCCode: c200
BCP1: 00000000000007
BCP2: 000000000000109B
BCP3: 0000000004040008
BCP4: FFFFFA8009265960

Hi Tillysaint.

I am not aware of this bugcheck code. Bug Check Code Reference does not have any idea about it, too. So first of all it is to be sure that the reported bugcheck code is correct.

Please post a camera snap of the BSOD screen when you experience it next time.

As we cannot have the crash dumps, at least we need to know the right bugcheck code and other parameters, and the camera snap will help a great lot.

 

[Boozad]

Hi Gav, please dont mind my friend. I want to verify a little thing.

Not at all Arc, not all.

 

[Tillysaint]

Thanks. It should be C2! I don't know how C2 became C200. I cute & pasted the event into a .doc.

When I was trying some recovery scenarios, I got a message that "the boot manager could not be found." I've been trying to solve this problem with various Microsoft recovery tools and other vendor tools like EasyRE recovery.

My current status is that I can't boot any of the recovery media to correct the problem. The only solution I can boot are two HP System Recovery DVDs that rebuilds my Windows 7 to its original factory system. I tried to get to a command prompt somehow to enter some boot commands but I haven't been able to.

I can't believe this happen since I only use this laptop for email, spreadsheets, and documents.

Tilly Saint

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: c2
BCP1: 0000000000000007
BCP2: 000000000000109B
BCP3: 0000000004040008
BCP4: FFFFFA8009265960
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\101514-80902-01.dmp
C:\Users\Ron\AppData\Local\Temp\WER-125393-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[gregrocker]

Hi Tilly -

You are able to boot into HP diagnostics from ESC menu which clears the hardware, correct?

What happens when you try to trigger from the same ESC key the menu to boot the Win7 DVD or Repair CD which is provided in http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html?

How about rebooting to tap F8 repeatedly to access http://www.sevenforums.com/tutorials/668-system-recovery-options.html?

One of these methods should give you access to Startup REpair which should offer to automate System Restore. If not and it fails run System Restore manually. System Restore is always the remedy for updates causing unbootable condition, so its especially important to be sure its enabled on C with enough Disk space apportioned: System Protection - Change Disk Space Usage

Are you still running the HP Factory install which is the worst possible install of Win7 one can have, larded with the worst load of bloatware in the industry and duplicate factory utilties which intefere with much better versions built into Win7? If so I'd use this as the opportunity to do a perfect http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html#post1839164 which will probably take less time than troubleshooting the mess.

 

[Boozad]

Thanks Greg

 

[Tillysaint]

Again, thanks for the help! I've been concentrating on the boot manager problem.

No, I wasn't able to ESC to the HP diagnostics. Sometime time ago they were available when I was exploring W7. However, there was only some internal tests when I ESC like Start Up & Disk Check that I ran with no problems. I know you can get to HP diagnostics & repair thru escape but not at this time.

I actual went through all the many Seven Forum steps that someone suggested. F8 did not work and I couldn't do I system restore from any menu option. I can't dreate a Boot Manager or run boot repairs through a command line.

I'm actually looking at Win8 instead of Win7. I do keep backups and maybe will try a image restore.

My only option now is to try USB boots. I've already changed the priority sequence of the boot to CD & USB. The ISO - USB tools that I've looked at, e.g. EasyBCD, require a W7 system to generate. I'm afraid of corrupting a neighbor's system.

Tilly Saint

 

[gregrocker]

You need a Win7 DVD provided in http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html Step 6, to use for repairs or reinstall.

There is no threat downloading it from Win7 Home Premium x64 SP1 English Official ISO download and then burning to DVD or flash stick using http://www.sevenforums.com/tutorials/31541-windows-7-usb-dvd-download-tool.html?filter

 

[Tillysaint]

Will the W7 USB boot tool work on an XP system to create a W7 boot or do I need to find a W7 system to create it then try to boot it on my broken W7 system? Thanks for the help! Tilly Saint

 

[gregrocker]

Are you asking if the Win7 Download tool will write the Win7 ISO to stick from XP? As far as I know.

Is there any chance you have a UEFI BIOS? These are very new and require writing the installation media to stick using a special tool. To see if this is the case, boot into BIOS setup and look at Advanced and Boot tabs for any signs of UEFI, CSM, Compatibility modes including in the Boot Priority order.

 

[Arc]

Thanks. It should be C2! I don't know how C2 became C200. I cute & pasted the event into a .doc.

Really cute, but if the typo had not been there in the OP, it would have been easier to control.

A stop 0xC2 is basically a memory malfunction caused by a driver passing bad info to the memory. What Greg suggested to you will cure any driver/software related issue from the root.

Just to be safe, test your RAM modules with Memtest86+ in order to be sure that the physical RAM is cont causing the issue.

 

[Tillysaint]

Thanks for the responses & help!!

I had previously checked the memory & disk with the BIOS Tools and had no failures. I don't think I could use executit86+ since I couldn't boot my system. Since we've had this system, I have a habit to look daily at the Event Viewer. A long time ago I've learned that when technology fails completely you've probably had intermittent errors. I've seen no hardware or driver problems.

The good news is that my Windows 7 system is up and running!!!!!

I don't really know what solved the problem! When I started to shot this problem days ago, I began with using the HP recovery tools, the window 7 tools, the SevenForum 18 step " Troubleshooting Windows 7 Failure to Start," other vendor tools like EasyBCD/PartionMagic/EasyRE, etc. without success. Success being able to boot something!

When I woke up early this morning, I decided to restart my solution investigation at the very beginning. The first tool I had used was the HP W7 Repair Disk that I created when I bought this HP laptop. HP had recommended that I do this. I didn't expect it to work, I was simply looking for the ability to get Command Prompt. I was pleasantly surprise that it booted and repaired my system!

I guess somewhere in the mixture of things I tried, something fixed the boot problem. I don't know what it was!

Thanks you for all your advice. I sure it helped me but I don't know how!

Regards, Tilly DSaint

 

[Arc]

The good news is that my Windows 7 system is up and running!!!!!
.....
.....
.....

Thanks you for all your advice. I sure it helped me but I don't know how!

All is well that ends well. Good to know that your issue is solved.