Ultimate x64 BSOD on Boot. Please help second time.

[DaveX]

I've had the same computer and setup for 2 years now. I was playing a game and the power went out, something that has happened several times over the years with XP. When I rebooted, windows would not start. It would give me a stop error and hang at loading disk.sys in safe-mode. Windows recovery found no problems and would not repair anything. chkdsk passed and I was able to boot into a console and backup files on a spare drive.

It's been working fine for the last few weeks, but this morning I had an application hang. I was unable to end-task it, and eventually had to hard reboot.

Immediately after powering back-on, I got this message. BOOTMGR is corrupt, unable to boot windows. I tried windows recovery from the 7 cd-rom, no problems found. I disabled my other drives (spare backup, cd-rom) and windows attempted to boot, but then BSOD (like the first-time) Now each reboot gives me a stop error: c000021a

When I attempt to boot into safe-mode, just like before when it reaches ..\drivers\disk.sys, it hangs for a few minutes, then BSOD. (I have heard it's the driver after the last listed that's the problem?)

I have 3 HD's in a raid0 (same setup for two years) When this happened the first time I broke apart the raid, did complete chkdsks and low-level formats on each drive then reformed the raid before installing windows 7 again.

I'm not sure what to do at this point and my question is can anyone help? I would rather not have to go through console backup/format again.

Thanks!

 

[myzr7]

Welcome Dave.
Have you tried this
http://www.sevenforums.com/tutorials/681-startup-repair.html

 

[Zardoc]

Hi,

Can you boot with DVD drive for win 7 and go to dos command.

First type bootrec /fixboot press enter
Now type bootrec /fixmbr press enter

Try to reboot.

You can also try to access advanced system settings (right click my computer/properties/advanced system settings/Startup and recovery/ uncheck automatically restart.

Post message.

 

[DaveX]

Yes I have tried to do startup repair. I will attempt to do the dos boot repair command as soon as this chkdsk /R is complete on the raid (almost done) I will post the results here.

Thanks for the quick responses

 

[Zardoc]

I added a message to my post.

Also, (if you have some training), you can read a .dmp file which gives you a pretty good idea what caused the crash.

Get the .dmp search for the file (usually in Windows/mem dump)

Install debugging tool for Win 7.

http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx#d

Get symbols
HERE for 64 bit

You can also get online symbols
Follow instructions from HERE

Install the debugging tools

Follow instructions here
How to read the small memory dump files that Windows creates for debugging

Here is a Bad pool caller BSOD caused by Eset with Windows Vista. This is what the mem dump report looks like.


--------------------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\Test\Mini102108-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*d:\websymbols*Symbol information
Executable search path is:
Windows Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Kernel base = 0xfffff800`01c62000 PsLoadedModuleList = 0xfffff800`01e27db0
Debug session time: Wed Oct 22 00:22:12.299 2008 (GMT+2)
System Uptime: 0 days 11:16:14.068
Loading Kernel Symbols
.................................................. .................................................. .................................................. ...
Loading User Symbols
Loading unloaded module list
......
************************************************** *****************************
*
*
* Bugcheck Analysis
*
*
************************************************** *****************************

Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 110b, 402000a, fffffa8007498440}
Unable to load image eamon.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for eamon.sys
*** ERROR: Module load completed but symbols could not be loaded for
eamon.sys
GetPointerFromAddress: unable to read from fffff80001e8b080
Probably caused by : eamon.sys ( eamon+1ff5 )
Followup: MachineOwner
---------
0: kd> !analyze -v
************************************************** *****************************
*
*
* Bugcheck Analysis
*
*
*
************************************************** *****************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a
bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000110b, (reserved)
Arg3: 000000000402000a, Memory contents of the pool block
Arg4: fffffa8007498440, Address of the block of pool being deallocated

Debugging Details:
------------------


POOL_ADDRESS: fffffa8007498440

FREED_POOL_TAG: None

BUGCHECK_STR: 0xc2_7_None

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001d96fa8 to fffff80001cb7350

STACK_TEXT:
> fffffa60`0ce57f78 fffff800`01d96fa8 : 00000000`000000c2 00000000`00000007

> fffffa60`0ce589b8 fffffa80`07780600 : 00000000`00000001 00000000`00000000
> 00000001`07060000 fffffa60`0ce589d8 : 0xfffffa80`079c1820


STACK_COMMAND: kb

FOLLOWUP_IP:
eamon+1ff5
fffffa60`0d5b2ff5 ?? ???

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: eamon

IMAGE_NAME: eamon.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48a95947

SYMBOL_NAME: eamon+1ff5

FAILURE_BUCKET_ID: X64_0xc2_7_None_eamon+1ff5

BUCKET_ID: X64_0xc2_7_None_eamon+1ff5

Followup: MachineOwner

 

[DaveX]

Hi,

Can you boot with DVD drive for win 7 and go to dos command.

First type bootrec /fixboot press enter
Now type bootrec /fixmbr press enter

Try to reboot.

You can also try to access advanced system settings (right click my computer/properties/advanced system settings/Startup and recovery/ uncheck automatically restart.

Post message.

Both operation said completed successfully but did not help. I still get a stop error on boot-up, nothing has changed. Chkdsk also returned fine with no errors or results.

I can not boot into windows to use those tools
I did find about 5 .dmp files though.

 

[Zardoc]

Dave,

This means that you have been getting that mem dump more than once.

Did you try to get the screen message for the BSOD?

 

[DaveX]

The stop error is code: c000021a
I was mistaken there is only one .dmp file.

If I attach the .dmp file, can someone look at it and help me out?

 

[H2SO4]

Dave,

This means that you have been getting that mem dump more than once.

Did you try to get the screen message for the BSOD?

Now each reboot gives me a stop error: c000021a

Minidumps won't be useful in this instance because the OS is bugchecking due to the termination of a critical user-mode process. In other words, either winlogon, CSRSS, or SMSS is crashing. Once the kernel notices, it deduces that there's no point living and throws itself off a cliff.

Minidump analysis would show nothing other than "a critical user-mode process has died for reasons which are not to be found in this abridged summary of the kernel-mode memory space". Not in those words of course

 

[usasma]

More info on the STOP 0xc000021a error: BSOD Index

 

[DaveX]

Alright, so now im not sure what to do anymore :|
I've tried all the suggestions so far.

Anything else?

Also, is this a known problem with 7? As in, hard reboot, corrupt files? I've never had this happen with XP in over two years, then twice in 7 in a month.

 

[H2SO4]

Alright, so now im not sure what to do anymore :|
I've tried all the suggestions so far.

Anything else?

Also, is this a known problem with 7? As in, hard reboot, corrupt files? I've never had this happen with XP in over two years, then twice in 7 in a month.

Did you run a repair install? Currently, do both normal and safe mode boots consistently result in c000021a bugchecks?

If the answer to both questions is "yes", the quickest way out of your predicament may be a full reinstallation from scratch. That type of crash is far from trivial to troubleshoot, and unless you get lucky with a repair/chkdsk it's usually not worth it for a single-machine problem.

No, it's not a Win7 bug. Something on your machine led to this. It doesn't mean it was your fault, but there's no point in blaming the OS. I wouldn't want you to fear that this will always happen to you on Win7.

 

[Zardoc]

Something is corrupt (Wouldn't hurt to check drives) and I would agree with suggestions from HS.

Unless you have an image of a clean install (which you would have used by now)

Lesson to be learned. If you get a BSOD. Best is to post screen message which will save a lot of time and get to the core of the issue. Error codes give a lot of info as to whether the fix is simple or porbably a corrupt system.

Unless some cool dude can do a bug analysys which would give same results as above but doesn't take much time when you know how to.

 

[DaveX]

Alright so this is the second time it's happened in a month but never happened with any other OS. The events that let to it were just a hard reboot. What can I do to help safeguard against it and make a repair possible for the third time which seems inevitable?