Replies

OK, for the moment is the subject not completely true. It is possible to start the computer etc. if you’ve followed the thread.
To day I also found my Media Player 9 files so I could do a reinstall. It worked very well, the patch KB 819639, is already there and will not install again. So far WMP is up and running like ever before.
Thats always something…

Argus

(Edited by Argus on 16-Sep-03 11:52. Added more info.)

Bob and SMBP
Yes, drivers seems to be in conflict one way or the other.

Primo: I think, still, that having some of my DirectX files messed up, older together with new, might be a major problem that can cause errors in many ways. Exactly how DirectX works together with my graphic driver Nvidia (40.72) in day to day use I don’t know. I can understand that it can be big problem in games. Since some days back I can not run Media player 9., as described earlier. First error was that it did not get the expected version (2980 inst. of 3008?). I had the latest patch for WMP 9. So I reinstalled it, now it only say something: unexpected error.

Secundo: I have updated my audio driver some hours ago. In my case, onboard (ECS K7S6A mainboard), it is the SiS7012 driver from ECS, v 1.10 which I think is WHQL. I don’t think my previous version was WHQL. I also checked/updated the AGP driver from SiS to latest 1.16a.

Tertio: I’ve checked the “Verifier”, before I only know about “Sigverif”. I realy don’t know how I should use Verifier, and MS certainly don’t put much help in the help files. With Verifier in “standard settings” it finds some drivers not signed. Before audio was included not after new driver. The rest, all but one or two, are related to Roxio CD-burner program. I use Easy CD and DirectCD.

I also have one question, and I don’t know if it has something to do with my described problems. When I did a check with “Sandra” some month ago I saw one line in report: “Disabled host controllers are present. Check BIOS Settings.” I do not know how I should interpret this?

Regards,
Argus

(Edited by Argus on 16-Sep-03 11:52. Added more info.)

Bob and SMBP
Yes, drivers seems to be in conflict one way or the other.

Primo: I think, still, that having some of my DirectX files messed up, older together with new, might be a major problem that can cause errors in many ways. Exactly how DirectX works together with my graphic driver Nvidia (40.72) in day to day use I don’t know. I can understand that it can be big problem in games. Since some days back I can not run Media player 9., as described earlier. First error was that it did not get the expected version (2980 inst. of 3008?). I had the latest patch for WMP 9. So I reinstalled it, now it only say something: unexpected error.

Secundo: I have updated my audio driver some hours ago. In my case, onboard (ECS K7S6A mainboard), it is the SiS7012 driver from ECS, v 1.10 which I think is WHQL. I don’t think my previous version was WHQL. I also checked/updated the AGP driver from SiS to latest 1.16a.

Tertio: I’ve checked the “Verifier”, before I only know about “Sigverif”. I realy don’t know how I should use Verifier, and MS certainly don’t put much help in the help files. With Verifier in “standard settings” it finds some drivers not signed. Before audio was included not after new driver. The rest, all but one or two, are related to Roxio CD-burner program. I use Easy CD and DirectCD.

I also have one question, and I don’t know if it has something to do with my described problems. When I did a check with “Sandra” some month ago I saw one line in report: “Disabled host controllers are present. Check BIOS Settings.” I do not know how I should interpret this?

Regards,
Argus

Bob,
—
The probability of hardware failure is HIGHER in the first few months of operation than after a longer period.
—
Yeah, I should know that, I am a engineer (not data, electronics etc.). You are right, almost every man made system have a probability of higher failure rate first period.

Some minutes ago I was in the process of writing this answer to you, and exactly when I was going to write: “it now seems OK”, BANG. Blue screen:
BAD_POOL_CALLER
STOP: 0x000000C2 (0x00000007,0x00000CD4,0x00000000,0xE2107f08)

A short search shows something about driver problem. Result includes MS info at KB314492. I really don’t know what to do next…
To my knowledge I only have two drivers not signed by MS etc. and it’s to my modem and sound. Over the last year it’s been hard to find, for instance a specific XP driver for my modem. They say it’s XP driver on the manufacturer site, but may seem like a win2000, and from my point of view should that not be a big problem.

Regards,
Argus

Bob,
—
The probability of hardware failure is HIGHER in the first few months of operation than after a longer period.
—
Yeah, I should know that, I am a engineer (not data, electronics etc.). You are right, almost every man made system have a probability of higher failure rate first period.

Some minutes ago I was in the process of writing this answer to you, and exactly when I was going to write: “it now seems OK”, BANG. Blue screen:
BAD_POOL_CALLER
STOP: 0x000000C2 (0x00000007,0x00000CD4,0x00000000,0xE2107f08)

A short search shows something about driver problem. Result includes MS info at KB314492. I really don’t know what to do next…
To my knowledge I only have two drivers not signed by MS etc. and it’s to my modem and sound. Over the last year it’s been hard to find, for instance a specific XP driver for my modem. They say it’s XP driver on the manufacturer site, but may seem like a win2000, and from my point of view should that not be a big problem.

Regards,
Argus

Bob

Yes, your’e right, sounds like memory, but I could not understand (or didn’t want to) why hardware failure, because the computer is only 12 months old. Anyway, I checked the memory, looks fine and clean. I moved it from slot 0 to slot 1. I only have on memory stick with 256 MB. Before I moved it the computer had been turned of for some day, after all the rebooting.
Well, after the move I turned it on, changed quick power on self test in BIOS to do a full check on start. No problem!

One funny side effect. I had a question in an earlier post with programs like Sandra, Aida32 and windows system reporting more memory than installed. That time it looked like this:
Bank 0 256 MB
Bank 1 Empty
Bank 2 512 MB
Thus 768 MB, even if there only was 256 MB installed. No, big problem. The who built the machine may have programmed wrong info. to DMI.
Now it looks like this
Bank 0 512 MB
Bank 1 Empty
Bank 2 512 MB
As I said, I moved memory stick to Bank 1 and this is programmed to DMI as empty… So now AIDA32 DMI info shows me 1024 MB, but installed memory is shown as 256 MB. Also Windows System info. from Help/about, About this machine shows 1024 MB.

Funny, but it works.

Also, I found a loose screw inside the machine! Ah well, not the first time. I can not find anything were it should be placed. When the machine was only 2 months I had problem with a CPU fan and had to send it for a change. That time I also found a loose screw. Those who built the machine had missed one of the screw to the MB, and I had to put it there myself.

Regards,
Argus

Bob

Yes, your’e right, sounds like memory, but I could not understand (or didn’t want to) why hardware failure, because the computer is only 12 months old. Anyway, I checked the memory, looks fine and clean. I moved it from slot 0 to slot 1. I only have on memory stick with 256 MB. Before I moved it the computer had been turned of for some day, after all the rebooting.
Well, after the move I turned it on, changed quick power on self test in BIOS to do a full check on start. No problem!

One funny side effect. I had a question in an earlier post with programs like Sandra, Aida32 and windows system reporting more memory than installed. That time it looked like this:
Bank 0 256 MB
Bank 1 Empty
Bank 2 512 MB
Thus 768 MB, even if there only was 256 MB installed. No, big problem. The who built the machine may have programmed wrong info. to DMI.
Now it looks like this
Bank 0 512 MB
Bank 1 Empty
Bank 2 512 MB
As I said, I moved memory stick to Bank 1 and this is programmed to DMI as empty… So now AIDA32 DMI info shows me 1024 MB, but installed memory is shown as 256 MB. Also Windows System info. from Help/about, About this machine shows 1024 MB.

Funny, but it works.

Also, I found a loose screw inside the machine! Ah well, not the first time. I can not find anything were it should be placed. When the machine was only 2 months I had problem with a CPU fan and had to send it for a change. That time I also found a loose screw. Those who built the machine had missed one of the screw to the MB, and I had to put it there myself.

Regards,
Argus

kaplinb
I agree XP is very stable. That is the reason why I got worried from the error message that time, and also the machine is so new that I would not think of hardware problem.
Thanks for your tips
Regards,
Argus

kaplinb
I agree XP is very stable. That is the reason why I got worried from the error message that time, and also the machine is so new that I would not think of hardware problem.
Thanks for your tips
Regards,
Argus

I have turned System Restore on, on system drive. Did that when the rebooting stoped.

Yes, no memory stop error (I suppose you refer to my other thread, sorry was trying to post an answer to that as well, but had problem with connection.) I have only seen that error once before this time, some months ago, but that time I didn’t find any source, what might caused, and it didn’t come back until some days ago.

I don’t understand what: Storage, is not a problem. Well I just said that I like to download patches to have them for future use.

Ah, well I suppose it can not go any worse. I will try and run SFC.

OK, I don’t have any more problem with Roxio. As I described, when you use DirectCD, it uses CDUDFRW file system when cd-rw disk is in burner, but if I move the cd-rw disk to my CD/DVD-drive the file system is UDFRDR, and now it can be read in any CD-drive that support UDF, My, one time , problem was that it behaved as it was in a CD-drive and not in the CD-RW. If you want to know version is:
Roxio Easy CD Creator 5, 5.1 (60), and Direct CD 5.10(115).

Yepp, Well it IS fine that registry say version 9.0b, and I am not worried that the patch isn’t there. Because I know it is there. But it is annoying that “dxdiag.exe” in system32 got changed, and that some other files was changed or damaged so that when I run the new dxdiag it finds errors.

Argus

I have turned System Restore on, on system drive. Did that when the rebooting stoped.

Yes, no memory stop error (I suppose you refer to my other thread, sorry was trying to post an answer to that as well, but had problem with connection.) I have only seen that error once before this time, some months ago, but that time I didn’t find any source, what might caused, and it didn’t come back until some days ago.

I don’t understand what: Storage, is not a problem. Well I just said that I like to download patches to have them for future use.

Ah, well I suppose it can not go any worse. I will try and run SFC.

OK, I don’t have any more problem with Roxio. As I described, when you use DirectCD, it uses CDUDFRW file system when cd-rw disk is in burner, but if I move the cd-rw disk to my CD/DVD-drive the file system is UDFRDR, and now it can be read in any CD-drive that support UDF, My, one time , problem was that it behaved as it was in a CD-drive and not in the CD-RW. If you want to know version is:
Roxio Easy CD Creator 5, 5.1 (60), and Direct CD 5.10(115).

Yepp, Well it IS fine that registry say version 9.0b, and I am not worried that the patch isn’t there. Because I know it is there. But it is annoying that “dxdiag.exe” in system32 got changed, and that some other files was changed or damaged so that when I run the new dxdiag it finds errors.

Argus

OK, one answer to my post mentioning WU, could be:
Your files in program filesWindowsUpdate may have been damaged and thus you get strange results from Windows Update, nothing to worry about, there are other ways to check that your patches are still intact.

I have read your posts about Microsoft Security Site, and I’ve been there before, even though I don’t read Bulletins just for the fun of it. I don’t have a fast Internet connection, and I also want to save the patches for future use, so I normally d/l from the Catalog. I, and many people, find WU as an easy way to check if there are any new patches, but I have learned now that one can not trust it.

Regards,

Argus

OK, one answer to my post mentioning WU, could be:
Your files in program filesWindowsUpdate may have been damaged and thus you get strange results from Windows Update, nothing to worry about, there are other ways to check that your patches are still intact.

I have read your posts about Microsoft Security Site, and I’ve been there before, even though I don’t read Bulletins just for the fun of it. I don’t have a fast Internet connection, and I also want to save the patches for future use, so I normally d/l from the Catalog. I, and many people, find WU as an easy way to check if there are any new patches, but I have learned now that one can not trust it.

Regards,

Argus

Sometimes it’s hard to know if problems are unrelated. But I agree that the questions about the tools (chkdsk, RC and sfc) should have been in another thread.

1) OK, for the moment, given how the problems has developed, I consider to do a clean install. If/how/when I do that is not a result only from having trouble with SFC or DirectX individually. I do not urge people to not use sfc, I just mentioned that I have had some trouble with it and how File protection messed with my DirectX files. I think SFC, as you said, can be a great tool, but somehow it didn’t work as planned some days ago.

2) Regarding Roxio, at that time it didn’t work. Some days later, and after the rebooting started, it’s now working. My intention with mentioning problem with Roxio was not to ask for help regarding that specific problem. I just added the info. to the thread to give a broader picture of the situation.

4) OK. I don’t know. If software can cause file errors etc. that can be repaired with chkdsk, then the next time your “bad software” causes an error you will get a new error/fix with chkdsk, and no specific hardware problem is involved, possible?

5) Yes, I know the places in registry. In my case, before the trouble with sfc and after, still the same:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftDirectXVersion
Value is: 4.09.00.0902.
Regarding the patch, same before trouble and after;
HKEY_LOCAL_MACHINESOFTWAREMicrosoftUpdatesDirectXdx819696IsInstalled
is present and has the value of 1.

That all seem so fine, so good. And of course I could stop there and rest assured I have the very latest DirectX and also the patched version. But my trouble is that during the process of running sfc something happened. As I mentioned earlier “dxdiag” (the tool – not DirectX files) in system32 changed back to the old version.

If I run dxdiag from Run, or my Quick launch toolbar, both will run the version that is placed in System32, thats OK, but please take a look at the screenshot. It is the old dxdiag, and it reports 8.1 AND 4.09.00.0902)! The second tab DirectX files reports no problems as I have mentioned before.

But if I do a search on the disk for the new dxdiag I find it in WindowsRegisteredPackages (and System32dllcache if I uncheck Hide protected system files). If I run the new dxdiag it reports 9.0 and 4.09.0000.0902, see second screenshot. The new dxdiag second tab report “some problems with DirectX files, try reinstall”. But then I can not reinstall the because it find that it’s already there.

Regards,

Argus

Sometimes it’s hard to know if problems are unrelated. But I agree that the questions about the tools (chkdsk, RC and sfc) should have been in another thread.

1) OK, for the moment, given how the problems has developed, I consider to do a clean install. If/how/when I do that is not a result only from having trouble with SFC or DirectX individually. I do not urge people to not use sfc, I just mentioned that I have had some trouble with it and how File protection messed with my DirectX files. I think SFC, as you said, can be a great tool, but somehow it didn’t work as planned some days ago.

2) Regarding Roxio, at that time it didn’t work. Some days later, and after the rebooting started, it’s now working. My intention with mentioning problem with Roxio was not to ask for help regarding that specific problem. I just added the info. to the thread to give a broader picture of the situation.

4) OK. I don’t know. If software can cause file errors etc. that can be repaired with chkdsk, then the next time your “bad software” causes an error you will get a new error/fix with chkdsk, and no specific hardware problem is involved, possible?

5) Yes, I know the places in registry. In my case, before the trouble with sfc and after, still the same:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftDirectXVersion
Value is: 4.09.00.0902.
Regarding the patch, same before trouble and after;
HKEY_LOCAL_MACHINESOFTWAREMicrosoftUpdatesDirectXdx819696IsInstalled
is present and has the value of 1.

That all seem so fine, so good. And of course I could stop there and rest assured I have the very latest DirectX and also the patched version. But my trouble is that during the process of running sfc something happened. As I mentioned earlier “dxdiag” (the tool – not DirectX files) in system32 changed back to the old version.

If I run dxdiag from Run, or my Quick launch toolbar, both will run the version that is placed in System32, thats OK, but please take a look at the screenshot. It is the old dxdiag, and it reports 8.1 AND 4.09.00.0902)! The second tab DirectX files reports no problems as I have mentioned before.

But if I do a search on the disk for the new dxdiag I find it in WindowsRegisteredPackages (and System32dllcache if I uncheck Hide protected system files). If I run the new dxdiag it reports 9.0 and 4.09.0000.0902, see second screenshot. The new dxdiag second tab report “some problems with DirectX files, try reinstall”. But then I can not reinstall the because it find that it’s already there.

Regards,

Argus