Win 10 AU and SB Audigy SE

Hello,

Since the upgrade I have BSOD with p17.sys as possible origin. Driver
is 5.12.1.2018. On the site of SB the latest driver is 5.12.1.2017. I
have removed the soundcard and used the inbedded sound system of my msi
mobo. No issue anymore.
Is there a workaround ?

Kind regards,

alpibucky

I ran into something similar (different program) and discovered that the
dll's had to be re-registerd. The solution given to me was to
re-install the program. Problem was solved.
Dick

On 11/3/2016 3:28 PM, alpibucky wrote:
Hello,

Since the upgrade I have BSOD with p17.sys as possible origin. Driver is
5.12.1.2018. On the site of SB the latest driver is 5.12.1.2017. I have
removed the soundcard and used the inbedded sound system of my msi mobo.
No issue anymore.
Is there a workaround ?

Kind regards,

alpibucky

Dick a pensé très fort :
I ran into something similar (different program) and discovered that the
dll's had to be re-registerd. The solution given to me was to re-install the
program. Problem was solved.
Dick

On 11/3/2016 3:28 PM, alpibucky wrote:
Hello,

Since the upgrade I have BSOD with p17.sys as possible origin. Driver is
5.12.1.2018. On the site of SB the latest driver is 5.12.1.2017. I have
removed the soundcard and used the inbedded sound system of my msi mobo.
No issue anymore.
Is there a workaround ?

Kind regards,

alpibucky

Hello,

Thanks for your experience. In my case I tried to reinstall the whole
driver from the SB site and got a BSOD before the reintall ended.
Perhaps the driver in compatibility mode ?

With kind regards

"alpibucky" wrote in message
...
Dick a pensé très fort :
I ran into something similar (different program) and discovered that the
dll's had to be re-registerd. The solution given to me was to re-install
the program. Problem was solved.
Dick

On 11/3/2016 3:28 PM, alpibucky wrote:
Hello,

Since the upgrade I have BSOD with p17.sys as possible origin. Driver is
5.12.1.2018. On the site of SB the latest driver is 5.12.1.2017. I have
removed the soundcard and used the inbedded sound system of my msi mobo.
No issue anymore.
Is there a workaround ?

Kind regards,

alpibucky

Hello,

Thanks for your experience. In my case I tried to reinstall the whole
driver from the SB site and got a BSOD before the reintall ended.
Perhaps the driver in compatibility mode ?

With kind regards

Is this the driver you have?

http://support.creative.com/Products/ProductDetails.aspx?catID=1&subCatID=205&prodID=14 257&prodName=Sound%20Blaster%20Audigy%20SE&subCatN ame=Audigy&CatName=Sound+Blaster&VARSET=prodfaq:PR ODFAQ_14257,VARSET=CategoryID:1

Since the original and the update are listed, it might work to install the
original in compatibility mode for Win8.1, then run the update.

Use something like Revo Uninstaller or Geek Uninstaller to remove all signs
of the original driver(s), including Alchemy if you have that installed.
Physically remove the card, boot up without it, then shutdown and start the
installation over again. I don't remember the order (been a while since I've
had a SB), but IIRC, it's put the card in, boot up, cancel out of the
Windows driver installation, then run your downloaded setup file.
--

SC Tom

On 03-Nov-2016 3:28 PM, alpibucky wrote:
Hello,

Since the upgrade I have BSOD with p17.sys as possible origin. Driver is
5.12.1.2018. On the site of SB the latest driver is 5.12.1.2017. I have
removed the soundcard and used the inbedded sound system of my msi mobo.
No issue anymore.
Is there a workaround ?

Kind regards,

alpibucky

Check the Windows® 10 - Software Availability Chart to see if your card
is listed then d/l.

http://support.creative.com/kb/ShowA...spx?sid=126331

http://preview.tinyurl.com/owhv2z5

Sergey vient de nous annoncer :
On 03-Nov-2016 3:28 PM, alpibucky wrote:
Hello,

Since the upgrade I have BSOD with p17.sys as possible origin. Driver is
5.12.1.2018. On the site of SB the latest driver is 5.12.1.2017. I have
removed the soundcard and used the inbedded sound system of my msi mobo.
No issue anymore.
Is there a workaround ?

Kind regards,

alpibucky

Check the Windows® 10 - Software Availability Chart to see if your card is
listed then d/l.

http://support.creative.com/kb/ShowA...spx?sid=126331

http://preview.tinyurl.com/owhv2z5

Hello,

The soundcard is on the chart SB0570.I did use the latest driver
xx1-04-0092.exe but not successfully
Kind regards

alpibucky

SC Tom a couché sur son écran :

"alpibucky" wrote in message
...
Dick a pensé très fort :
I ran into something similar (different program) and discovered that the
dll's had to be re-registerd. The solution given to me was to re-install
the program. Problem was solved.
Dick

On 11/3/2016 3:28 PM, alpibucky wrote:
Hello,

Since the upgrade I have BSOD with p17.sys as possible origin. Driver is
5.12.1.2018. On the site of SB the latest driver is 5.12.1.2017. I have
removed the soundcard and used the inbedded sound system of my msi mobo.
No issue anymore.
Is there a workaround ?

Kind regards,

alpibucky

Hello,

Thanks for your experience. In my case I tried to reinstall the whole
driver from the SB site and got a BSOD before the reintall ended.
Perhaps the driver in compatibility mode ?

With kind regards

Is this the driver you have?

http://support.creative.com/Products/ProductDetails.aspx?catID=1&subCatID=205&prodID=14 257&prodName=Sound%20Blaster%20Audigy%20SE&subCatN ame=Audigy&CatName=Sound+Blaster&VARSET=prodfaq:PR ODFAQ_14257,VARSET=CategoryID:1

Since the original and the update are listed, it might work to install the
original in compatibility mode for Win8.1, then run the update.

Use something like Revo Uninstaller or Geek Uninstaller to remove all signs
of the original driver(s), including Alchemy if you have that installed.
Physically remove the card, boot up without it, then shutdown and start the
installation over again. I don't remember the order (been a while since I've
had a SB), but IIRC, it's put the card in, boot up, cancel out of the Windows
driver installation, then run your downloaded setup file.

Hello,

Yes, it is this one. I will give a try to your solution. Thanks

Kind regards,

alpibucky

SC Tom a utilisé son clavier pour écrire :

"alpibucky" wrote in message
...
Dick a pensé très fort :
I ran into something similar (different program) and discovered that the
dll's had to be re-registerd. The solution given to me was to re-install
the program. Problem was solved.
Dick

On 11/3/2016 3:28 PM, alpibucky wrote:
Hello,

Since the upgrade I have BSOD with p17.sys as possible origin. Driver is
5.12.1.2018. On the site of SB the latest driver is 5.12.1.2017. I have
removed the soundcard and used the inbedded sound system of my msi mobo.
No issue anymore.
Is there a workaround ?

Kind regards,

alpibucky

Hello,

Thanks for your experience. In my case I tried to reinstall the whole
driver from the SB site and got a BSOD before the reintall ended.
Perhaps the driver in compatibility mode ?

With kind regards

Is this the driver you have?

http://support.creative.com/Products/ProductDetails.aspx?catID=1&subCatID=205&prodID=14 257&prodName=Sound%20Blaster%20Audigy%20SE&subCatN ame=Audigy&CatName=Sound+Blaster&VARSET=prodfaq:PR ODFAQ_14257,VARSET=CategoryID:1

Since the original and the update are listed, it might work to install the
original in compatibility mode for Win8.1, then run the update.

Use something like Revo Uninstaller or Geek Uninstaller to remove all signs
of the original driver(s), including Alchemy if you have that installed.
Physically remove the card, boot up without it, then shutdown and start the
installation over again. I don't remember the order (been a while since I've
had a SB), but IIRC, it's put the card in, boot up, cancel out of the Windows
driver installation, then run your downloaded setup file.

Hello,

I followed your instructions and I have now 5.12.1.2017 installed in
compatibility mode for Seven. No issue anymore.

With my kind regards,

alpibucky

On 4/11/2016 3:28 AM, alpibucky wrote:
Hello,

Since the upgrade I have BSOD with p17.sys as possible origin. Driver is
5.12.1.2018. On the site of SB the latest driver is 5.12.1.2017. I have
removed the soundcard and used the inbedded sound system of my msi mobo.
No issue anymore.
Is there a workaround ?

Try removing the driver from Program and Features, delete driver files
in Device Manager, then let Windows Update to download and install a
driver from Micro$oft.

"alpibucky" wrote in message
...
SC Tom a utilisé son clavier pour écrire :

"alpibucky" wrote in message
...
Dick a pensé très fort :
I ran into something similar (different program) and discovered that
the dll's had to be re-registerd. The solution given to me was to
re-install the program. Problem was solved.
Dick

On 11/3/2016 3:28 PM, alpibucky wrote:
Hello,

Since the upgrade I have BSOD with p17.sys as possible origin. Driver
is
5.12.1.2018. On the site of SB the latest driver is 5.12.1.2017. I
have
removed the soundcard and used the inbedded sound system of my msi
mobo.
No issue anymore.
Is there a workaround ?

Kind regards,

alpibucky

Hello,

Thanks for your experience. In my case I tried to reinstall the whole
driver from the SB site and got a BSOD before the reintall ended.
Perhaps the driver in compatibility mode ?

With kind regards

Is this the driver you have?

http://support.creative.com/Products/ProductDetails.aspx?catID=1&subCatID=205&prodID=14 257&prodName=Sound%20Blaster%20Audigy%20SE&subCatN ame=Audigy&CatName=Sound+Blaster&VARSET=prodfaq:PR ODFAQ_14257,VARSET=CategoryID:1

Since the original and the update are listed, it might work to install
the original in compatibility mode for Win8.1, then run the update.

Use something like Revo Uninstaller or Geek Uninstaller to remove all
signs of the original driver(s), including Alchemy if you have that
installed. Physically remove the card, boot up without it, then shutdown
and start the installation over again. I don't remember the order (been a
while since I've had a SB), but IIRC, it's put the card in, boot up,
cancel out of the Windows driver installation, then run your downloaded
setup file.

Hello,

I followed your instructions and I have now 5.12.1.2017 installed in
compatibility mode for Seven. No issue anymore.

With my kind regards,

alpibucky

I'm glad it's working again :-) Enjoy!
--

SC Tom