stop: c000021a {Fatal System Error} -- newb meets minor heart attack... seeks me
The Session Manager Initialization system process terminated unexpectedly with a status of 0xc000003a (0x00000000 0x00000000). The system has been shut down. that's the whole error message. . . and all I see on the infamous blue screen.
The Session Manager Initialization system process terminated unexpectedly with a status of 0xc000003a (0x00000000 0x00000000). The system has been shut down."
that's the whole error message... and all I see on the infamous blue screen... though I refuse to acknowledge it has anything to do with death
Here we go...
I'm a newbie to Linux and this is one of those times when I feel like I should just regress and submit to the powers of M$, but I'm stubborn and actually care about civil liberties, invasion of privacy, etc, so I'm in this one to win it.
I have searched through th existing threads on this one as well as having done some poking around on the net for a solution and hereby throw myself upon the mercy of greater minds and experience (and have been pointed to linuxcompatible by a few seasoned vets):
Here's how the boys at M$ describe my problem -- that is, this is almost EXACTLY it:
http://support.microsoft.com/default.aspx?scid=kb;en-us;317189
There are 2 things that don't fit
1) they seem to imply it's only an NT thing -- my system is XP Pro (specs follow)
2) their message is for 0xc0000017 status - mine is 0xc000003a
-BRAND new (if it had ears, it would still be wet behind them - I'm talkin' this-week new, factory-direct)
-IBM Thinkpad T42, Pentium M 1.7 GHZ, 60GB, 7200 RPM HDD, 1GB PC2700 DDR SDRAM, Intel Pro Wireless 2200 integrated wireless B/G
It's been partitioned successfully using Partition Magic and all was well with XP... then I installed Ubuntu ( www.ubuntulinux.com - latest stable of Warty Warthog): my Linux distro of choice. The concept all along was to buy this machine with the express intent of running Windows parallel with Linux. No I'm starting to feel like it might be cheaper to pay programmers to write scripts for every non compatible peripheral that sparked this fine mess...
Now, I have a machine that loads to the GRUB boot loader beautifully, gives me 5 options (1 Ubuntu and one Windows safe, 1 Ubuntu and one Windows normal, and memory test, although the windows options both appear to be the same since neither says "safe", I imagine one is supposed to be safe... either way, neither works. ) The Ubuntu system works perfectly (of course, it WOULD be Windows with issues... ug.)
Regarding a post I read in the threads of similar topic, if the solution is to take the CDs tht came with it and do a "fixboot" or a "non-destructive reinstall", please provide some detail as I have no idea what the implications are / what I should expect during the process...
Here's another twist: If there are other Distros that make life easier, I'm willing to consider anything. I've used fluxbox (not my cup of tea), Mandrake (liked it) and a couple others... Since I'm just making the switch, Ubuntu is wonderful because the GUI is familiar, etc... still, I'm open.
Thank you in advance for your time!
that's the whole error message... and all I see on the infamous blue screen... though I refuse to acknowledge it has anything to do with death
Here we go...
I'm a newbie to Linux and this is one of those times when I feel like I should just regress and submit to the powers of M$, but I'm stubborn and actually care about civil liberties, invasion of privacy, etc, so I'm in this one to win it.
I have searched through th existing threads on this one as well as having done some poking around on the net for a solution and hereby throw myself upon the mercy of greater minds and experience (and have been pointed to linuxcompatible by a few seasoned vets):
Here's how the boys at M$ describe my problem -- that is, this is almost EXACTLY it:
http://support.microsoft.com/default.aspx?scid=kb;en-us;317189
There are 2 things that don't fit
1) they seem to imply it's only an NT thing -- my system is XP Pro (specs follow)
2) their message is for 0xc0000017 status - mine is 0xc000003a
-BRAND new (if it had ears, it would still be wet behind them - I'm talkin' this-week new, factory-direct)
-IBM Thinkpad T42, Pentium M 1.7 GHZ, 60GB, 7200 RPM HDD, 1GB PC2700 DDR SDRAM, Intel Pro Wireless 2200 integrated wireless B/G
It's been partitioned successfully using Partition Magic and all was well with XP... then I installed Ubuntu ( www.ubuntulinux.com - latest stable of Warty Warthog): my Linux distro of choice. The concept all along was to buy this machine with the express intent of running Windows parallel with Linux. No I'm starting to feel like it might be cheaper to pay programmers to write scripts for every non compatible peripheral that sparked this fine mess...
Now, I have a machine that loads to the GRUB boot loader beautifully, gives me 5 options (1 Ubuntu and one Windows safe, 1 Ubuntu and one Windows normal, and memory test, although the windows options both appear to be the same since neither says "safe", I imagine one is supposed to be safe... either way, neither works. ) The Ubuntu system works perfectly (of course, it WOULD be Windows with issues... ug.)
Regarding a post I read in the threads of similar topic, if the solution is to take the CDs tht came with it and do a "fixboot" or a "non-destructive reinstall", please provide some detail as I have no idea what the implications are / what I should expect during the process...
Here's another twist: If there are other Distros that make life easier, I'm willing to consider anything. I've used fluxbox (not my cup of tea), Mandrake (liked it) and a couple others... Since I'm just making the switch, Ubuntu is wonderful because the GUI is familiar, etc... still, I'm open.
Thank you in advance for your time!
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
i noticed on the previous posts that people had split thier hard drive to cause the problem, i haven't.
i thank you for your help.
i thank you for your help.
i should have probably added that i have windows xp sp2 and nothing else. i don't even know what a dual boot situation is so i'm going to say no to that as i only have windows xp sp2.
Realize that you posted on a Linux thread. The previous folks also had a dual boot system with Linux...so that is why I asked, to make sure.
See this Microsoft article for a descrpition of the issue.
Has something changed in your system just before this occured, say a newly installed program, driver or hardware that required you to install a driver?
Did you just try to install a service pack that failed?
Did you do a recent backup of the system, or have a another problem that caused the system to reboot?
See this Microsoft article for a descrpition of the issue.
Has something changed in your system just before this occured, say a newly installed program, driver or hardware that required you to install a driver?
Did you just try to install a service pack that failed?
Did you do a recent backup of the system, or have a another problem that caused the system to reboot?
before i begin, should i start a new post on the xp section?
i had accidentally installed spyware locked. i tried to remove it on the programs list but messages kept coming up with something along the lines of
'please restart your computer before removing this program'
after lots of restarts i realised that it wasn't working and decided to delete it manually ( a bad mistake i now know)
realising my mistake i went on the internet and saw this program and guide that should get rid of the program. this failed horribly after some messages about regedit.
i hope this answers your question
i had accidentally installed spyware locked. i tried to remove it on the programs list but messages kept coming up with something along the lines of
'please restart your computer before removing this program'
after lots of restarts i realised that it wasn't working and decided to delete it manually ( a bad mistake i now know)
realising my mistake i went on the internet and saw this program and guide that should get rid of the program. this failed horribly after some messages about regedit.
i hope this answers your question
Hey everybody.
Well, needless to say, I am in the same exact pickle.
Quote:"....status of 0xc000003a (0x00000000 0x00000000). The system has been shut down."
Had the autocheck bad boy as well. Eliminated it via registry. So, pretty much 0xc000003a is left. Also, autocheck as I understand is just an indicator of a problem rather than a cause...
Okay, some background:
Have Windows 7 x64, decided to install Linux Mint x64 (I am on it right now).Obviously, had to move some partitions around - that went well. At one point, I had nice dual boot with grub: Win7 and Mint. However, probably from having nothing else to do, I decided to be anal and react to this warning in Mint that I have a lot "...bad sectors...". So, I scanned/checked them and tried to repair on Mint. And that was the breaking point, I think.
After googling a lot, I fixed up nicely my boot records, mbr... So I now I got dual boot sys as well, it is just that Win 7 gives me that autocheck + 0xc000003a
I have tried the following:
1) Registry editing "Bootexecute"...
2) Tried tackling this hidden partitions issue. AFAIK, they are not hidden. Although, not sure. Tried unhide(hdX,Y) - did not work ("select disk does not exist"). Here is a "fdisk -l" by the way:
Quote:Disk /dev/sda: 160.0 GB, 160041885696 bytes255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0000000a
Device Boot Start End Blocks Id System
/dev/sda1 * 1 17346 139331713+ 7 HPFS/NTFS
/dev/sda2 17347 19457 16956607+ 5 Extended
/dev/sda5 19203 19457 2048287+ 82 Linux swap / Solaris
/dev/sda6 17347 17996 5221062 83 Linux
/dev/sda7 19071 19201 1052226 7 HPFS/NTFS
/dev/sda8 17997 19070 8626873+ 83 Linux
Partition table entries are not in disk order
3) repairing with windows 7 cd
4) setting the drive in question as active numerous times
5) some other desperate stuff as replacing identical autocheck.exe from different (but same cd) win7 instalations in case it was corrupt.
6) PTedit - doesnt work because win7 is x64
It has been 2-3 days with at least 6hours each. I am running out of options and MS tech support sites dont help.
Thanks.
Well, needless to say, I am in the same exact pickle.
Quote:"....status of 0xc000003a (0x00000000 0x00000000). The system has been shut down."
Had the autocheck bad boy as well. Eliminated it via registry. So, pretty much 0xc000003a is left. Also, autocheck as I understand is just an indicator of a problem rather than a cause...
Okay, some background:
Have Windows 7 x64, decided to install Linux Mint x64 (I am on it right now).Obviously, had to move some partitions around - that went well. At one point, I had nice dual boot with grub: Win7 and Mint. However, probably from having nothing else to do, I decided to be anal and react to this warning in Mint that I have a lot "...bad sectors...". So, I scanned/checked them and tried to repair on Mint. And that was the breaking point, I think.
After googling a lot, I fixed up nicely my boot records, mbr... So I now I got dual boot sys as well, it is just that Win 7 gives me that autocheck + 0xc000003a
I have tried the following:
1) Registry editing "Bootexecute"...
2) Tried tackling this hidden partitions issue. AFAIK, they are not hidden. Although, not sure. Tried unhide(hdX,Y) - did not work ("select disk does not exist"). Here is a "fdisk -l" by the way:
Quote:Disk /dev/sda: 160.0 GB, 160041885696 bytes255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0000000a
Device Boot Start End Blocks Id System
/dev/sda1 * 1 17346 139331713+ 7 HPFS/NTFS
/dev/sda2 17347 19457 16956607+ 5 Extended
/dev/sda5 19203 19457 2048287+ 82 Linux swap / Solaris
/dev/sda6 17347 17996 5221062 83 Linux
/dev/sda7 19071 19201 1052226 7 HPFS/NTFS
/dev/sda8 17997 19070 8626873+ 83 Linux
Partition table entries are not in disk order
3) repairing with windows 7 cd
4) setting the drive in question as active numerous times
5) some other desperate stuff as replacing identical autocheck.exe from different (but same cd) win7 instalations in case it was corrupt.
6) PTedit - doesnt work because win7 is x64
It has been 2-3 days with at least 6hours each. I am running out of options and MS tech support sites dont help.
Thanks.
