BSOD c00021a fatal system error

hello since install of the windows 7 professional operating system i have been having this error . start-up repair claims it to be a corrupt boot file but i am not so sure as i have done a format install of the windows 7 operating system twice . i can sometimes get my laptop started by using the debugging mode . this takes sometimes 20-30 attempts and cannot continue. . i have pasted below the report that windows have given me as it thinks it was an unexpected shut down . i would like to add all my drivers are upto date and would like a fix if possible asap . microsoft told me to reinstall the operating system as did a tech shop i have taken it too . also sometimes with my laptop it will unexpectedly shut down in the middle of something as if you were holding the power button and all the lights go off and takes a while to start again if anyone can help i thank you so much as my only resort now is buying a new laptop

please find attached the minidump folder



Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: c000021a
BCP1: FFFFF8A004877C90
BCP2: 00000000C0000189
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\120909-31793-01.dmp
C:\Users\KXDAN\AppData\Local\Temp\WER-110043-0.sysdata.xm



the blue screen reads

STOP : c000021a fatal system error
status of 0x00000000 (0xc0000001 0x00100588)

thanks for your time

Please start with this: H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Please update or remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager. Please use the following instructions to locate the most current drivers:

How To Find Updated Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- some driver links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers:

Code:

agrsm64.sys  Mon Nov 10 10:01:35 2008 - Agere Systems Soft Modem (part of LSI Logic: Support and Downloads)
tap0901.sys  Wed Nov 19 13:22:35 2008 - OpenVPN driver
TVALZ_O.SYS  Thu Nov 08 22:08:41 2007 - Toshiba Value Added/Common drivers

Then, please run Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) 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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD's:

Code:

BugCheck C000021A, {fffff8a001e2fbe0, 0, ffffffffc0000001, 110588}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck C000021A, {fffff8a0007544e0, c0000189, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck C000021A, {fffff8a0007c60f0, c0000189, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck C000021A, {fffff8a0001b60e0, c0000189, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck C000021A, {fffff8a000734e50, c0000189, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck C000021A, {fffff8a004e3d3e0, c0000189, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck C000021A, {fffff8a000104d60, c0000189, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck C000021A, {fffff8a0000fb340, c0000189, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck C000021A, {fffff8a0097795c0, 0, ffffffffc0000001, 100588}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck C000021A, {fffff8a0000a8930, c0000189, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )

Here's the summary of the BSOD - essentially the same as the others:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan 14 13:14:13.608 2010 (GMT-5)
System Uptime: 0 days 0:00:22.339
BugCheck C000021A, {fffff8a009793980, c0000189, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  smss.exe

Please update the drivers mentioned above and see if that fixes the BSOD's.
If not, then I'll have to recommend:
- backing up your information
- wiping the hard drive with KillDisk or DBAN
- installing Windows again without any extra programs (to see if the error still occurs).

The Agere modem and the Toshiba Value Added stuff will be found at the Toshiba support website
The VNC stuff will be found at the site of the VNC flavor that you're using. If you didn't install it, then ask whoever did.

Frankly, I don't think that the drivers are that big of an issue - so you may be better off:
- backing up your information
- wiping the hard drive with KillDisk or DBAN
- installing Windows again without any extra programs (to see if the error still occurs).