mightyzuloo.blogg.se

1. #Sound blaster recon 3d drivers windows 10 install#
2. #Sound blaster recon 3d drivers windows 10 driver#

If the motherboard isn't properly identifying the card at boot-up, I don't think blocking that one driver is going to fix anything. Still, there's a problem there somewhere.

#Sound blaster recon 3d drivers windows 10 install#

When I get in tomorrow, I'm supposed to delete the card and the driver the next time it shows up as a SB Recon3D, then run the Windows Hide Update tool, so that Windows won't install that driver again. For some reason, restarting four times, eventually, it picks it up and identifies it correctly, then it works from then on.

For some reason, when booting from cold start, the motherboard isn't identifying the card properly, so Windows in loading a driver for another card, which really isn't the card I have, hence no sound and the reason the Sound Blaster Connect 2 app doesn't detect my card. Without sound, it shows I have a SB Recon3D. The funny thing is, with sound, under Sound Components, it shows I have Sound BlasterX AE-5. I sent Creative my System.nfo files from with sound and without sound. Before I go to the trouble of that, does this sound like it could help with my issue? I know disabling Secure Boot and going to Legacy Mode will require me to reinstall Windows and set my system up all over again. I thought the Legacy Boot options were for only for helping boot from various devices that don't properly work within a UEFI environment. Someone has mentioned that I may need to disable Secure Boot and turn on Legacy mode in the CSM. When I had it in my wife's system, hers boots to Windows 10 desktop in about 20 seconds, and it doesn't seem to have any trouble initializing. I disabled Fast Boot and put the Post Boot Delay to the maximum of 10 seconds, but it doesn't help. At first, they thought that maybe my system was booting too fast for the card to finish initializing. I've started working with Creative technical support. I moved the card to my wife's computer that has a Gigabyte motherboard, and it works just fine in her system. I've tried moving the card to different slots, but it makes no difference. It's just that initial boot from being turned off. Once I get it, everything works great and, once its up, a restart usually doesn't affect it. The trouble is, at cold boot, from a completely shutdown condition, it takes a minimum of four restarts for the card to properly initialize and get sound in Windows. It works great when it actually initializes. I've been having trouble with my Sound BlasterX AE-5 sound card.