Stop c000021a

[zone23]

OK took out 1 stick of RAM leaving 2gb. Installed x64 7 set to diagnostic start up reboot BSOD same error as posted. Try to enter safe mode BSOD.

 

[Snufffed]

What did diagnostics startup give you?
there should be a log.
also going back to earlier x64 systems to see what error says.

Applicable to the following Windows Vista configurations: Home Basic, Home Premium, Ultimate, Business, Enterprise, Starter, Home Basic N, Business N, Business 64-bit Edition, Home Basic 64-bit Edition and Business N 64-bit Edition.



This STOP error can occur during startup or at other times. The 8 digit hexadecimal number 0x00000001 translates to the error APC_INDEX_MISMATCH which may be caused by the following:

1. A kernel-level application or device driver running in kernel mode created a mismatch of thread and asynchronous procedure calls (APC) indexes. This is probably due to a file system mismatch in the number of processes that entered the critical area compared to those that left. Allowing the software to run at this point will corrupt or damage the system.
2. This could be due to newly added hardware or software issues.
3. This error can pop up when a CD or DVD is inserted into the drive
4. This error also happens when the computer uses the Windows Vista Aero color scheme.
5. Sometimes, when we unlock the computer and login to the default desktop this STOP error shows up.
6. This STOP error sometimes occurs after the computer transitions into to sleep mode repeatedly (by customer usage).
7. This problem can also happen in a secure desktop environment (when we lock the computer) where an application has registered an “event hook” using an Application Programming Interface
8. Problems in the Windows system file win32k.sys can trigger this STOP error.
9. Memory corruption can also create these conditions.
10. Too much RAM (> 2GB) may exceed motherboard and BIOS capabilities and create this STOP Error.

--------------------------------

1. Are you installing from DVD or HDD or other media. ?
2. have you tried cmd -> sfc /scannow to check for Corrupt system files.

have you looked into the EVENT Viewer log. to see what it says...

 

[Snufffed]

Other Techs in reference say it is a DRIVER Problem.... they recommend you state with a TOTALLY CLEAN install.
no printers, not extras at all. nothing that is not needed to simply get this system CLEAN and on the internet....
No upgrades or anything. If Windows 7 does not install it by default. DON'T DO IT.
I know nothing about a BSOD dmp file, but I'm sure some one else here does.

 

[zone23]

Were is the diagnostic start up log file?

System was totally clean I didn't install a single driver.

I'm installing from a DVD.
I have not run a sfc /scannow I will right now.

 

[Snufffed]

OK, that takes care of Drivers for 3rd party. stuff.

If you did not find any error with diagnostic startup:

If the problem does not occur, use Selective startup mode to try to find the problem by turning individual services and startup programs on or off.
Selective startup



Selective startup enables you to select the files and the settings that you want the computer to load when you restart the computer. Select from the following options:

• Process System.ini File
• Process Win.ini file
• Load System Services
• Load Startup Items

By default, no options are selected. The following actions apply to these options:

• When you select the check box, the configuration file is processed when you restart the computer.
• When you clear the check box, the configuration file is not processed when you restart the computer.
• When the check box is selected, and you cannot select the check box because it appears dimmed, some items are still loading from that configuration file when you restart the computer.
• When the check box is not selected, and you cannot select the check box because it appears dimmed, the configuration file is not present on the computer.
• You cannot change the Use Original BOOT.INI option button.

Note When you clear the Load System Services check box, you disable Microsoft services such as Networking, Plug and Play, Event Logging, and Error Reporting. You also permanently delete all restore points for the System Restore utility. Do not clear this check box if you want to keep your restore points for System Restore, or if you have to use a Microsoft service to test a problem.



To perform a selective startup, follow these steps:

1. Click Start, click Run, type msconfig, and then click OK.
2. On the General tab, click Selective Startup.
3. Select or clear the available settings.
4. Click OK.
5. Restart your computer.
6. Repeat steps 1 through 5 until you find the problem.

If the above does not help you find the device or driver problem. here is a link to
about 150 different things that cause your error.
http://social.msdn.microsoft.com/Search/en-US?query=c000021a&ac=8

 

[zone23]

Ok well I can't get into anything it just keeps blue screening so I will reinstall and do a selective start up before I reboot.

 

[zone23]

ok well hit selective startup deselected everything went into device manager turned off everything I didn't need. Rebooted and it booted up, 3 reboot BSOD. I give up.

 

[Snufffed]

Sorry its been a time since reply. All the searching, still leads to some Driver that Toshiba installes just to get the main things running, is the BAD BOY. Apparently they know what the problems is, since they say PAY for upgrade and you can get... your system is not included in the FREE upgrade, Vista had the same problem on many systems which was not fixed until SP1.
I can find reference to this problem in x64 as far back as Windows 98. should read Win XP.
Really I do wish I could be more help.

ok well hit selective startup deselected everything went into device manager turned off everything I didn't need. Rebooted and it booted up, 3 reboot BSOD. I give up.

you only need HDD access and network-monitor-mouse. If you install from HDD partition. it is faster and if for some reason there is an error intransfer this will stop that.

Quess your stuck with x86. you might try keeping a copy of all the x64-ini. then when you do x86 you can compare. or dual boot then compare.
if you clean install x86 on same all your x64 files will be there in windows.old .
Snuffy

 

[zone23]

Sorry its been a time since reply. All the searching, still leads to some Driver that Toshiba installes just to get the main things running, is the BAD BOY. Apparently they know what the problems is, since they say PAY for upgrade and you can get... your system is not included in the FREE upgrade, Vista had the same problem on many systems which was not fixed until SP1.
I can find reference to this problem in x64 as far back as Windows 98.
Really I do wish I could be more help.

ok well hit selective startup deselected everything went into device manager turned off everything I didn't need. Rebooted and it booted up, 3 reboot BSOD. I give up.

you only need HDD access and network-monitor-mouse. If you install from HDD partition. it is faster and if for some reason there is an error intransfer this will stop that.

Quess your stuck with x86. you might try keeping a copy of all the x64-ini. then when you do x86 you can compare. or dual boot then compare.
if you clean install x86 on same all your x64 files will be there in windows.old .
Snuffy

Well I ordered Windows 7 upgrades for all my machines when it was 50% off. My issue is I'm picky and all my machines must run the same OS or I'm just not happy. Even the same bit whether its x86 or x64. Today all my machines are running Vista x64 so I guess if Toshiba doesn't fix it buy October 22 then I will have to cancel my Windows 7 launch party j/k. I'm going to give them some more time heck I have another 30 days I hope they fix it by then. Like I said I have a windows home server so I was able to just restore this PC last night in about an hour and its like nothing ever happened which is nice. I would love to see how 7 x64 runs on this machine. Thanks again for your help and sorry if I was a little rude. I'm really not like that, just frustrated.

 

[H2SO4]

Well I managed to pull the memory.dmp really wasn't that hard so here it is:

There's almost nothing to be learned from a 0xC000021A dump because it's a reaction to an event which has already passed, as I believe Usasma and others have already pointed out.

The critical user-mode process crashes for some reason, and when the kernel notices it decides to switch the lights off and leave because there's really no point in continuing. Being purposefully triggered in response to an event elsewhere, the kernel's own "crash" dump does not contain interesting info.

I'm unclear as to whether you've reinstalled (RTM?) from scratch at any point during all this time? Sorry, there's a lot of stuff to read.

 

[zone23]

Well I managed to pull the memory.dmp really wasn't that hard so here it is:

There's almost nothing to be learned from a 0xC000021A dump because it's a reaction to an event which has already passed, as I believe Usasma and others have already pointed out.

The critical user-mode process crashes for some reason, and when the kernel notices it decides to switch the lights off and leave because there's really no point in continuing. Being purposefully triggered in response to an event elsewhere, the kernel's own "crash" dump does not contain interesting info.

I'm unclear as to whether you've reinstalled (RTM?) from scratch at any point during all this time? Sorry, there's a lot of stuff to read.

I'm doing fresh installs of Windows 7 Enterprise x64 I downloaded directly from Microsoft. I have also done upgrades with the same results (but not with Enterprise cause you can't upgrade from Home Premium to Enterprise). Thanks for the info I guess I can just delete the crash dump post then.

 

[H2SO4]

I'm doing fresh installs of Windows 7 Enterprise x64 I downloaded directly from Microsoft. I have also done upgrades with the same results (but not with Enterprise cause you can't upgrade from Home Premium to Enterprise). Thanks for the info I guess I can just delete the crash dump post then.

I wouldn't personally bother deleting it - debugger spew always looks pretty

How much non-default stuff are you installing after Windows itself before these crashes start? I'm particularly interested in things like (3rd-party) VPN clients, directory sync clients (are you on a corporate network?), anti-virus software... add-ons related to user authentication and account synchronisation.

If you can reproduce this crash relatively readily, it's possible to debug it, but it requires some fiddling.

 

[zone23]

I'm doing fresh installs of Windows 7 Enterprise x64 I downloaded directly from Microsoft. I have also done upgrades with the same results (but not with Enterprise cause you can't upgrade from Home Premium to Enterprise). Thanks for the info I guess I can just delete the crash dump post then.

I wouldn't personally bother deleting it - debugger spew always looks pretty

How much non-default stuff are you installing after Windows itself before these crashes start? I'm particularly interested in things like (3rd-party) VPN clients, directory sync clients (are you on a corporate network?), anti-virus software... add-ons related to user authentication and account synchronisation.

If you can reproduce this crash relatively readily, it's possible to debug it, but it requires some fiddling.

I don't get a chance to install anything because as soon as windows installs and I reboot it crashes.

 

[H2SO4]

I don't get a chance to install anything because as soon as windows installs and I reboot it crashes.

Having now read the rest of the thread...

There's an old rule of thumb that says that miscellaneous crashes before, during, and just after a "clean" install (from known-good media) are caused by hardware issues. That of course includes fundamental BIOS and driver type incompatibility with the OS, not just individually "broken" hardware instances.

If you're genuinely convinced by your research that there are no examples of others with the same exact hardware successfully running Win7, then it may really be an issue for Toshiba and MS to resolve. If I understand correctly, Toshiba are pointedly saying that they won't support the combination of that laptop plus Win7 before some time in November, and there may be real technical reasons for that beyond the knowledge of the phone droids one gets to speak to in support.

I'm interested but at the same time reluctant to recommend further "debugging" activity simply because it's not like we'll be able to make many changes to prevent the crash condition - whatever it may be - if you can't even log on reliably.

How "clean" is your reinstallation procedure? You mentioned WHS. You have tried booting the box from a known-clean DVD, nuking the HDD, and just starting from scratch, right?

Have you observed it to crash on reboot even before you try to log on?

It sounds like you're able to log on sometimes though. On average, how many attempts does it take before you can log on without an immediate crash?

If you do manage to log on, does it stay intact if you just leave it and walk away from the keyboard?

If you leave the networking defaults during setup, are you able to ping it across the network and perform any other type of network operation to that box from another machine, preferably while you're not logged on at all?

 

[zone23]

Well here I am at the final hour and still no fix. I just tried windows x64 again with the latest updates from MS and Toshiba drivers with the same end results. BSOD on first reboot with the thread topic error. Looks like I'm going to be running x86, booooo.

 

[hrishi]

I solved this problem.
1. Download both and burn32-bit and 64-bit Windows 7 ISOs.
2. Start install using the 32 bit dvd. It will go to the windows logo then after that it start expanding files showing 0% complete.
3. At this the point eject the dvd and put in the 64-bit dvd and used the power button to reboot.
4. Start the setup process again and let it continue. Windows 7 will get installed after this.
5. Turn off automatic updates (till windows 7 is more stable).


Full post:
Installing Windows 7 on a 64-bit Toshiba laptop « The Tech Bloggery

 

[rgartin]

Toshiba has posted a bios update for the L355D-S7901 along with additional models. I was able to flash the bios, installed Windows 7 x64, Avast and the AMD/ATI video drive with a reboot after each install. So far so good, but I am going to play with it some more. I'll post an update tomorrow.

 

[hrishi]

Here's the new bios link

Important 64-bit Windows 7 and BIOS Information - Toshiba Laptop Forums

 

[usasma]

Thanks for the link hrishi!

 

[zone23]

YES!!! finally this is exactly what I've been waiting for a BIOS update. Guess what? It worked!!!! I've installed rebooted a number of times and the system is now perfect. Funny thing is a check Toshiba's site everyday just about, funny they snuk that one in there. I knew that's what it was going to take. Thanks