Unexpected shutdowns with BSOD c000021a on startup

[set9676]

This has happened twice now in the past week. Computer will randomly shutdown unexpectedly (cold and dark) with the BSOD c000021a on startup. I am able to get windows to boot again using startup repair, but I'm getting sick of having unexpected crashes. Any suggestions?

Please advise if more info is needed. I'm new at this.


Spencer

 

[koolkat77]

Welcome

First off, please uninstall Norton Internet Security from your computer using this link https://www-secure.symantec.com/nor...&version=1&pvid=f-home&entsrc=redirect_pubweb reboot after the uninstall.

Download and install MSE from Microsoft Security Essentials - Free Antivirus for Windows Run a full scan after its installed.

Now run the system file checker to repair any damaged files within windows 3 times:
:ar: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Lastly run Disk check for errors http://www.sevenforums.com/tutorials/433-disk-check.html

Let us know if you still have crashes

 

[set9676]

Alright...I followed your suggestions and so far so good. The scans and disk checks revealed no problems. Does this mean I shouldn't re-install Norton? Was that causing the crashes?

 

[koolkat77]

One of your dump was showing Norton as the problem.
We need to wait and see how your computer performs for 3/4 days.

 

[koolkat77]

Hi

Just wanted to know are you getting more bsods?

 

[set9676]

Nope. I haven't had any problems for a little over a week now.

 

[koolkat77]

Do you want to observe more?
If not then you can mark this thread as solved.

But do come back if you have any problems.

 

[set9676]

Bad news...just recovered from another crash. I'll attach the most recent SF diagnostic / minidump file. Any new suggestions? I very much appreciate the help.

Spencer

 

[koolkat77]

The dump is of 09-06-2012 where's the latest one?

 

[set9676]

Weird...not sure why the old one wasn't overwritten. Is this attachment also back from 9/6/12? I have no idea how to read these things!

 

[set9676]

Hmmm...it looks like that one is old too. I don't understand. Why wasn't the most recent dump recorded?

 

[koolkat77]

Yup
Do you remember the stop code?

 

[set9676]

Ummm....it was the usual unexpected shutdown / black screen. The BSOD was on the startup. STOP: c000021a. Then a bunch of zeros; I think it ended in ...00037. After about 10 tries I finally got it to load the startup repair, which fixed the problem. I'm sorry I can't remember more info. If this isn't helpful at all I guess we'll just wait until it happens again, and I'll be sure to record all the details next time.

 

[koolkat77]

Okay so time for waiting till your computer crashes again..

If you want we can enable Driver Verifier

In the meantime fill in your specs
:ar: http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

__________________

1. Click on User CP on the top right of this page
2. Click on Edit System Spec
3. Fill in your computer specs
   :ar: http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

__________________

Edit: Did you look for an update on your BIOS version?

BIOS Version/Date	Phoenix Technologies LTD V1.04, [COLOR="Red"]10/22/2009[/COLOR]

 

[set9676]

I checked the Gateway website and the only BIOS update listed was "Set the critical low of battery from 3% to 5% and the warning of battery from 5% to 7%." The Phoenix Technologies website just had a link to some website that made you pay for BIOS updates, which seems sort of ridiculous to me.

How big is the risk inherent in Driver Verifier? I'm living in Ecuador right now, and I don't really have access to a computer other than the one that's been crashing. I wouldn't want to run into a situation where I don't have a computer available.

 

[koolkat77]

You'll be able to use your computer. No problem.

Lets enable driver verifier to rule out buggy drivers.

Driver Verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in verifier and press Enter
- Select Create custom settings (for code developers) and click Next
- Select Select individual settings from a full list and click Next
- Select everything EXCEPT FOR Low Resource Simulation and click Next
- Select Select driver names from a list and click Next
Then select all drivers NOT provided by Microsoft and click Next
- Select Finish on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.