XXHighEnd

In the 3 weeks I have had the Juli@ soundcard, it has only worked 2 times.  Every other time (about 40-50 attempts) I get a blue screen of death whenever I turn the computer on after installing the card.  In the 2 times it worked, I was able to use 24/176 through the SPDIF output and all worked properly, but when I turn the PC off I get the blue screen the next 10 times I turn it on, at which point I yell a lot and remove the card and then the PC works fine.  I don't know enough to diagnose the problem, so Monday I am turning it over to a local repair shop who assures me he can get it to run (although he admits to having very little expeience with sound cards).  The ESI site forum has several instances of others having a simlar problem.  Anyone here have any suggestions before I pay someone to work on it?

Hey Glynn,

Sorry to hear about your nasty problem, because it seems something with so few to do and taking so much time to test (reboots, removing the card again, etc.).

Assuming you use V1.07 for the driver (which will be the latest, unless there is a recent new one), I would try 1.21 (which is way older, depsite the higher number !). There's also another one which works for W7 and what we do with it, and Roy mentioned it somwhere (in that thread where I anounced that the Juli@ can do Kernel Streaming allright : So, a Juli@ doesn't dig KS, right ? (http://www.phasure.com/index.php?topic=1063.0)).

Next think about some possible problem with the buffer size, and that it may run on some size which is not the default (IIRC the default is 128), BUT that it won't store your change, and thus at a reboot falls back to that size at which it won't reboot at all. A bit vague maybe, and theoretically even impossible as the cause if you read well what I wrote, but still a kind of explanation for "it has worked a few times". On this latter, think about how it will  work the very first time, where at booting it can't do anything because it is not known. This "not known situation" however, only exists when the active driver has been removed, and in the thread I referred to is mentioned by me how to do that. So, next you can boot with the Juli@ in there, and now you can appoint your (own) driver (see description in that thread again), and ... this already may do tricks because possibly you didn't do it that way before.
If this doesn't help by itself, set the Buffer Size to e.g. 1024, and check a couple of times whether it's still in there. If yes, reboot (yeah, you will be 30 minutes further already, I know). If this helps, and you can determined it is the buffer size by setting it back to 128 and reboot (and then it dies again), never set it to 128 anymore.

Btw, the story about the buffer size is way too long, looking at the chance it is the cause. It is just a very wild guess.

Good luck now,
Peter

It looks like my problem is solved, at least for now.  Since I had plans to take it all to a repair place tomorrow, I decided I could take a few chances and delete some things.  Got rid of XXHighEnd, XMPlay, dbPoweramp and then looked at almost every file, removing things that looked out of place.  Then shut it down, reinstalled Juli@ sound card, fired it up and it worked.  Downloaded XXHighEnd and fired it up and it works flawlessly.  So finally I can proceed with what I started almost a month ago - comparing the Wavelength Brick DAC (USB 24/96) with a Benchmark DAC1 (SPDIF 24/192).  Just think about how much money I am spending because of you Peter  ;)

Haha, well, I can only hope for you it keeps on working, because I don't see much reason in how your removal of files etc. can be related. So it could be coincidence, like it happened a few times before ...