ruudboek

1. What was the exact BSOD message? 2. Still some AC'97 soundcards could cause a BSOD. Could you try the unattended installation again, but without the driverpack sound A? 3. You have 2 soundcards in your system, maybe you have conflicting hardware because of that. Could you take out the SB Live and try again? Ruud

@RogueSpear As experiment you could also try to replace the de forceware 81.85 drivers in the driverpack graphics A by beta (leaked) forceware drivers version 81.89. You can download those drivers right here : http://files.tweakers.net/nVidia/ForceWare 81.89 Win2kXP.rar Let us know the results! Ruud

Hey that looks very nice It past my radar aswell However this database is a bit too detailed. The amount of BSOD devices are only a handfull. I was more looking for a small list, so you get an overview of all known BSOD's in one page. Maybe a sticky or something. Ruud

It looks like we've got a solution here then. @Bashrat, what do you think of placing all the sil3112 entries before the sil3112r entries in txtsetup.sif? Are you not afraid that the BSOD for sil3112 systems will be solved, but the BSOD will then happen to sil3112r systems? Ruud

@Maxximum, So you didn't remove the driverpack Graphics V5.11.1? Why would you need to install forceware 81.95 manually? Driverpack Graphics V5.11.1 already has forceware version 81.95! You should have had a BSOD then. Regarding the removal of the "N" directories : i don't think you have a problem with the nforce drivers, because it has already been proven that not the combination of the nforce drivers with forceware drivers are causing BSOD's but only the forceware driver itself of version 81.94 and higher. To answer your question : yes, removing all nvidia nforce and nvidia forceware directories will result in a working XPCD, but keeping the nvidia nforce and the older nvidia forceware drivers version 7.8.0.1 [78.01] will also result in a working XPCD. Ofcourse you will then need to install the forceware drivers version 81.95 manually. As experiment you could also try to replace the de forceware 81.85 drivers in the driverpack graphics A by beta (leaked) forceware drivers version 81.89. You can download those drivers right here : http://files.tweakers.net/nVidia/ForceWare 81.89 Win2kXP.rar Let us know the results! B.t.w. what soundcard is in the BSOD system? I am asking this because in this post a confict between the latest forceware drivers and realtek HDA drivers has been found : http://www.msfn.org/board/index.php?s=&sho...ndpost&p=428779 He solved his BSOD by removing the Realtek HDA sound drivers from the driverpack sound A. I think you also have a realtek HDA soundcard (probably a Realtek ALC850). You could try it yourself by removing the driverpack sound A. Again, let us know the results! Ruud

@Discountpc and @swampy New Realtek AC'97 drivers version 3.80 are out. When i look at the changelog i see the following : 1.For special customize settings. 2.For modem remote wake up issue in ALI chipsets. Now the last time the rather vague entry "For special customize settings" solved quite a lot of soundmax problems, maybe the latest changes solve the portcls.sys on the asus systems aswell. Can someone try to follow this procedure to see if the portcls.sys error is gone? Hereby the steps to take : 1. Download the latest Realtek AC '97 drivers from : http://www.realtek.com.tw/downloads/dlac97...8&Software=True ( Size should be 17689k) 2. Extract the downloaded WDM_A380.exe with 7zip. 3. Extract the driverpack sound A with 7zip. 4. Delete the Contents of D\S\R folder, except for the D\S\R\HD folder. 5. Go back to the folder in which you extracted the WDM_A378.exe file and copy the CONTENTS of the WDM folder to the D\S\R folder. 6. 7Zip the D folder with maximum compression (archivename has to be the same as the name of the driverpack sound A). 7. Do a new slipstream of the driverpacks. 8. Done! Ruud

Hello all, i would like to clear some things up : @Muiz What was the exact errormessage you encountered? Was it a BSOD? @RogueSpear 1.What was the exact errormessage in the BSOD? 2. Did you also try to remove the Realtek HDA drivers from DP sound A or not use the DP sound A at all, then after the installation install the HDA drivers manually? 3. When installing the HDA drivers manually, do you also get a BSOD? ( in that case it would not be a DP problem). @anyone Can other people also confirm a BSOD with systems with Nvidia Geforce graphics AND Realtek HDA sound hardware present? Ruud

@Maxximum According to that, you are not using the original Driverpacks, Bashrat probably meant if you could try with just your plain XPCD with the original, latest DP's. Ruud @Maxximum Why remove all the nvidia drivers, you can also use the older 7.8.0.1 [78.01] nvidia drivers. They might not support the latest geforce graphic cards, but they will support most nvidia cards without the BSOD's, right? Ruud

I agree with you on that it should definitely be known under what circumstances these BSOD's can occur. However, wouldn't simply adding an extra description column be sufficient in that case? If this list would be in colums it could be something like this : 1. Drivername. 2. Hardware involved. 3. Description of the cirumstances under which the BSOD occurs. 4. Location of the driver(s) in the driverspacks. 5. Known methods to get around the BSOD (including removal of those specific drivers from the driverpacks). 6. Link to the topic where the problem is addressed. Ruud

As far as i know, not the HDA drivers, but the AC '97 drivers are causing this BSOD. It has already been proven in these topics : http://www.msfn.org/board/index.php?showtopic=60550 http://www.msfn.org/board/index.php?showto...9689&hl=prevent http://www.msfn.org/board/index.php?showtopic=30389 Removing them will prevent the BSOD for ALL soundmax hardware for which no proper soundmax driver is available as far as i know, so yess, those AC '97 drivers are causing BSOD's. The point of this list would also be to prevent a possible BSOD and removing those AC '97 drivers will help preventing these BSOD's right? Also i would like to add, that when you take out the AC'97 drivers, but leave the soundmax drivers, no more BSOD's occur. When you would keep the AC'97 drivers, but take out the soundmax drivers, BSOD's will still happen. To me it is obvious that one can conclude from that, that the AC'97 drivers alone can cause BSOD's, but even worse, the AC'97 are not compliant with a multiple-hardware-vendor-slipstreamed-installation and it really should be solved by Realtek as far as i'm concerned. I am even wondering if realtek is voilating the driversigning policy with this bug Anyway in the case of the Realtek AC '97 drivers i would say that there is no confusion anymore, so that issue is therefore solved Ruud

Hello all, I think we all agree that BSOD's are quite destructive to a unattended installation, because you cannot do -anything- when you're looking at a bluescreen during an unattended installation. Maybe it would be a good idea to start an official BSOD driverlist which consists of a list of known drivers and matching hardware which will cause BSOD's? We could include the following information : Drivername - Hardware involved - Location of these driver(s) in the driverspacks - Known methods to get around these BSOD's (including removal of those specific drivers from the driverpacks) - Link to topic where the problem is addressed. People can then have a quick look at this list before starting to use their unattended installation on their hardware. That way they know what to expect right away. Ofcourse a driver should only be added to that list if it is 100% certain that a BSOD is caused by a certain driver of which it has been proven to cause a BSOD. To prevent non-proven drivers of individuals to be added to that list i think it would be wise to have Bashrat become the moderator of that list. We could for example include the following drivers to the BSOD list : Sil3112 driver Realtek AC'97 drivers Ati Radeon 8500 driver VIA's VT8237 driver Ruud

@Bashrat, why did you update the nvidia drivers to version 8.1.9.5 [81.95]? I thought that you explicitely downgraded the nvidia drivers to version 7.8.0.1 [78.01] because the higher versions are causing BSOD's? Ruud

This is very interesting, If this BSOD is also an portcls.sys BSOD, then it looks like the AC '97 realtek drivers not only cause portcls.sys BSOD's on soundmax-compatible soundcards but even on actual realtek soundcards themselfs. That will mean that we now have some prove that the realtek AC '97 realtek drivers are most likely not slipstream-compatible. In that case we can file a bugreport at realtek! But first things first, @mjc, can you tell me if the word portcls.sys was in the BSOD error? Ruud

It looks like a new problem with the Realtek AC'97 drivers, this time they give a BSOD with Asus systems when soundmax drivers ARE available. @swampy, Were you using the latest driverpack sound A v5.11? Ruud

Hello Bashrat, just out of interest, how exactly do you explicitely integrate hem as System Bus Extender? And why would that prevent them from using the atiide2k.sys driver? Ruud

Hello Bashrat, you are very right on that, i once witnessed the difference in the speed of installation with chipset drivers (including sata controller drivers) installed during the xp installation vs afterwards. I think the installation finished within halve the time it took if the chipset drivers were added afterwards, so yes the perfomance gain can be dramatic. By the way, since muiz already gotten rid of his now-most-likely-performance-challenged pc and no other means of testing my suggestion is available, would it be an idea to replace the atiide.inf file already in the next release of your driverpack massstorage? It could prevent BSOD's. Ruud

Thats correct Njay, if i understand correctly you posted the same BSOD in this topic : http://www.msfn.org/board/index.php?showto...asraid.sys&st=0 and it was continued in this topic : http://www.msfn.org/board/index.php?act=ST...t=0#entry371196 If i look at the hardware id of the GAK8VT800 Pro VIA SATA RAID Controller i can see that the following string is the same as the one from your motherboard : PCI\VEN_1106&DEV_3149 Since the vendor and device string are the most important, it looks like we are talking about the same kind of hardware and BSOD here. Now bashrat apparently closed this topic stated as SOLVED, which i don't understand because as we can see in this topic the BSOD is still present even with the latest driverpacks (i presume) and you are saying you still have to make adjustments to prevent the BSOD. @Bashrat, Why is that topic stated as SOLVED? Ruud

I would really appreciate that, Thx Dave Ruud

@Bashat Why would you think that it isn't the 5.11 driver that has been included? Ruud

@ Muiz, ah cool, was already wondering who you've got so many different machines Great stuff, keep posting! Anyway, you are quite right on the fact that the default windows xp ide drivers work just fine on that pc. As you can read from this site, with or without the ati ide drivers it will work, but the ati ide drivers seem to be able to prevent errors with clone cd or something : http://www.internetforen.de/viewtopic.php?...6&view=previous @ Bashrat, Why did you include the ati ide drivers in the driverpack massstorage anyway? Ruud

Hello Muiz, can you tell me what was in the BSOD error message? Ruud

I don't think your BSOD is caused because of the PRESENCE of the realtek ac '97 drivers. As everybody knows by now, the problem with the portcls.sys BSOD was caused in the case that NO soundmax compatible driver for your soundcard can be found. In your case however an soundmax compatible driver should really be present! I just checked the website from ASUS and i found and downloaded the soundmax driver for your K8S-MX motherboard. (http://support.asus.com/download/download.aspx?SLanguage=en-us) I presume your K8S-MX is SIS based, therefore your soundcard driver inf file should be smwdmSIS.inf. This file is also present in the driverpack sound B in the D\S\SM\A\3 folder. To be specific, you apparently have an SoundMAX AD1888 integrated soundcard and the BTS supported devices list confirms that your soundcard is supported indeed : http://www.driverpacks.net/Projects/Driver...ack_Sound_B.htm So apparently, we have to start looking at the current SoundMAX AD1888 drivers present in the driverpack sound B. However, i would really like to be certain that the portcls.sys BSOD is no longer caused by the presence of the realtek ac '97 driver in the driverpack sound B. @Discountpc, 1. Just to make certain, are you sure you were using the driverpack sound A version 5.11? 2. Could you do us a HUGE favor, try to do the installation again, *but* leave out the driverpack sound A? then reply to this topic if you are still getting this portcls.sys BSOD? 3. To solve your problem permanently and leave you with a working installation could you try to replace the current SoundMAX AD1888 drivers with the SoundMAX AD1888 drivers from Asus? Follow these steps to replace the SoundMAX AD1888 drivers in the driverpack sound B 5.11 : 1. Download the asus K8S-MX SoundMAX AD1888 drivers from : http://dlsvr01.asus.com/pub/ASUS/mb/sock75...-mx/adi1888.zip ( Size should be 18.91 MB) 2. Extract the downloaded adi1888.zip with 7zip. 3. Extract the driverpack sound B 5.11 with 7zip. 4. Delete the CONTENTS of the D\S\SM\A\3 folder. 5. Go back to the folder in which you extracted the adi1888.zip file and copy the CONTENTS of the Windows\SMAXWDM\W2K_XP folder to the D\S\SM\A\3 folder. 6. 7Zip the D folder with maximum compression ( archivename has to be the same as the name of the driverpack sound B ). 7. Do a new slipstream of the driverpacks. 8. Done! Ruud

I did some inf reading. I checked the \D\M\AT\atiide.inf file from the driverpack massstorage. The solution to this problem can be found right in there. I seems that this inf file seems to want to differentiate the w2k drivers from xp drivers, however i think it is a mistake in the inf file made by ATI. Just before the w2k section it tries to identify if the w2k OS is present or not, it does this by these lines : [Manufacturer] %ATI%=ATI_HDC,NTx86.5.1 ;**********************... W2K .....************************* ;********** ; ATI Dual Channel Bus Master PCI IDE Controller [atiide_Inst2k] CopyFiles = @atiide2k.sys As you can see in this w2k section it tries to use the atiide2k.sys file, which apparently is for w2k only, because in the xp section it only uses the atiide.sys file. Now in the XP section it tries to identify the XP OS and does this by this line : ;*********************.... XP ....************************* [ATI_HDC.NTx86.5.1] %PCI\VEN_1002&DEV_4349.DeviceDesc% = atiide_Instxp, PCI\VEN_1002&DEV_4349 ;******** ; ATI Dual Channel Bus Master PCI IDE Controller [atiide_Instxp] CopyFiles = @atiide.sys As you can clearly see, to identify the w2k OS it uses %ATI%=ATI_HDC,NTx86.5.1, but to identify the XP OS is seems to use the exact same string! Correct me if i am wrong but I think for the w2k OS shouldn't it have been %ATI%=ATI_HDC,NTx86.5.0? Anyway, because of this mistake in the atiide.inf, windows xp will most likely try to use the atiide2k.sys file instead of the XP compatible atiide.sys file, which gives a very good explanation for the atiide2k.sys BSOD! For this reason i went looking for another version of the 1.00.0000.3 ATI IDE driver and yes i found a previous version (1.00.0000.2) of this driver and that one only supports XP. Well i took a look at the inf file from this older driver and it does not differentiate between w2k of XP at all. If i then compare the old and the new version of the inf file it seems that there is no differences at all except for this differentiation between the w2k and XP OS. It looks like this problem can be very easily solved be replacing the current atiide.inf file for the older version (1.00.0000.2) of the atiide.inf file in the driverpack massstorage. @Muiz, Could you follow these steps to replace the atiide.inf file in the driverpack massstorage and try again? 1. Extract the driverpack massstorage with 7zip. 2. Download the atiide.inf file from this post. 3. Go to the folder in which you extracted the driverpack massstorage. 4. Copy the atiide.inf file to D\M\AT and replace the current one when asked. 5. 7Zip the D folder with ULTRA compression (archivename has to be the same as the name of the driverpack massstorage). 6. Do a brand new slipstream of the driverpacks. 7. Done! 8. Please post your results by replying to this topic. @Bashrat, What do you think of my solution, i'm 99.99% certain that this solves the BSOD Ruud ATIide.inf

Hello alhaddar, if i understand correctly this problem is already solved. Check this post : http://www.msfn.org/board/index.php?s=&sho...ndpost&p=409959 Apparently this problem was not related to the driverpack Massstorage but due to the driverpack Base. From driverpack Base version 5.10.5 the problem should be solved. Could please download the latest driverpack Base, try again and post your results in this topic? Ruud

Hello Muiz, can you show me a link to the site where you downloaded the ati drivers which you installed manually? I can then make a comparison with the driverpacks. Ruud