joeyeti Posted March 7, 2006 Share Posted March 7, 2006 (edited) Hiya Guys and Gals,I had just an error with BSOD when trying an unattended WinXP install with nLite under VmWare...It said in most words this:STOP: c000021a {serious system error}The Logon Process accidentaly terminated with state 0xc0000018 (0x00000000 0x00000000).System was shutdown.I think it has something to do with latest updates after SP2 - could it be ryanvm's updatepack? I dont wanna blame anybody just suggesting...... I used the 2.0.2a version, will try it with the latest though....Anyone experienced similar problem? Edited March 7, 2006 by joeyeti Link to comment Share on other sites More sharing options...
nuhi Posted March 7, 2006 Share Posted March 7, 2006 First try it with 2.0.3 on CLEAN English Windows then report with preset used if error remained. Link to comment Share on other sites More sharing options...
joeyeti Posted March 7, 2006 Author Share Posted March 7, 2006 Hmmm, the UpdatePack will probably not be the problem, as I just tried it also with the newest one and the problem persists....I will try to make the unattend with nLite from scratch (I was reusing) and maybe only slipstreaming the SP2 without any CABs adding....Will let you know... Link to comment Share on other sites More sharing options...
joeyeti Posted March 8, 2006 Author Share Posted March 8, 2006 Hiya,from continuing testing it would indeed point to the Updates in RyanVM's UpdatePack.... Looks like some of the newest Updates (post SP2) causes this - I would say it corrupts some files at installation, but these are all yet ASSUMPTIONS, not hard-proof Statements.... Anyone tested too?BTW Ryan, your UpdatePack is good , only M$ s***s, you know... Link to comment Share on other sites More sharing options...
Siginet Posted March 8, 2006 Share Posted March 8, 2006 I would have to say it can't be caused by the update pack... if everyone else who uses it doesn't have a problem.I would be more inclined to think that you are not using a fresh xp disk. If you have previously had hotfixes or anything modified on your original disk before adding the updatepack you are more inclined to have issues. Link to comment Share on other sites More sharing options...
joeyeti Posted March 8, 2006 Author Share Posted March 8, 2006 I would be more inclined to think that you are not using a fresh xp disk. If you have previously had hotfixes or anything modified on your original disk before adding the updatepack you are more inclined to have issues.Hm, I AM using a fresh XP install disk, eg. I always copy the WinXP Install CD on the drive (a czech version), slipstream the SP2 into it and only then add the CABs in nLite (one of them is the UpdatePack). Now I tried several installs WITHOUT the UpdatePack and they went ok. After the currently running install finishes, I will redo it again and only add the UpdatePack to see if it causes the same error again. It may not be the whole UpdatePack, only some of the Hotfixes alone, or....... could it be a compatibility error with nLite? But I would doubt this one, as I used the same 2.0.2 UpdatePack a few weeks ago with nLite RC6 and all went ok....before: nLite RC6 with 2.0.2 updatepack - oknow: nLite RC6 with 2.0.2 updatepack - badnLite RC7 with 2.0.2 updatepack - badnLite RC7 with 2.0.3 updatepack - badCan someone tell, if this could also not be a WinXP system issue? I mean the hardware PC operating system, not the unattended install? Link to comment Share on other sites More sharing options...
nuhi Posted March 9, 2006 Share Posted March 9, 2006 I think this says all:before: nLite RC6 with 2.0.2 updatepack - oknow: nLite RC6 with 2.0.2 updatepack - badMeaning it's either something new you did or your hardware.Check the integrated drivers or hotfixes if any. Link to comment Share on other sites More sharing options...
joeyeti Posted March 10, 2006 Author Share Posted March 10, 2006 Hiya,hmmm I cant think of any new thing I would have done.... I tried also to download the standalone hotfixes - only the crucial ones (about 45 pieces of KB EXEs) and integrate them instead of the UpdatePack. I got the error also....So could be, that with my particular WinXP Proffesional CD the Hotfixes just dont wanna cooperate....It is not a major issue for me, as I am always capable of adding the Hotfixes after installation via WindizUpdate (and dont bother with the M$ one...). It just annoys........If anyone comes to a solution, please let me know. Link to comment Share on other sites More sharing options...
Thauzar Posted August 5, 2006 Share Posted August 5, 2006 I've got the SAME error yesterday while trying to install on my new M2N32-SLIAll cds where made from the same Gold source, so the source is not in question.The first cd was fullu hotfixed, updated, drivers integrated etc. got the errorThe 2nd cd was full hotfixed, nothing else added. got the errorThen I stumbled upon here, tried a last cd with only SP2 integrated, no hotfixes or anything except the sata driver integrated: works fine.So I guess there is something wrong with either ryan's latest pack, or the combination of this pack with nlite 1.01 final. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now