Random BSOD

briand88 said:

I have figured out what these are no doubt you already knew though.

1. Audio Jacks from my Asus Xonar Ds sound card
2. Optical passthrough (from sound card or GFX card? not used)
3. Is my Monitors speakers the HDMI from my GFX card to my monitor
4. Is my built in Motherboard sound card and my front audio panel on my case (both ofwhich i dont use)

^ Yes you are completely correct.

briand88 said:

So from a playback devices point of view its sorted and is as before. As for the HD VDeck is this relating to my Motherboards Built in sound card and cases front panel Audio Jacks which i do not use?, If so would it be OK to disable them all in play back devices, The non used sources and uninstall/remove HD Vdeck? as i do not use the Front jacks or my Motherboards audio jack ports?.

^ Disabling the on-board audio will not increase your computers' speed or help it, it may even cause problems, you see the reason I asked you to install the VIA driver is because your PC was using a generic windows audio driver - this can cause problems later on. However, if you get sound problems in the future then by all means disable the VIA soundcard, if it's not causing a problem then i suggest leaving it.

HD VDeck is part of the VIA driver package so you can't uninstall it without removing the VIA driver.

briand88 said:

I also think i have figured out why i was Blue Screening in the first place, I was disabling some things on Startup to try and get the PC to boot a bit faster Already boots in like 15-20 seconds as the OS is installed on an OCZ Vector SSD so me being a pernickety s**t started to disable things in the Startup on System Configuration thinking i could get a faster boot time so i disabled things like Skype etc then i see HsMgr did not recognise it so i disabled it what is is though. Hsmgr.exe is a driver component for Asus, Auzentech, Creative and other sound cards. HsMgr.exe (32-bit) and HsMgr64.exe (64-bit) are services that provide the GX2.0 features. Under Vista, they also enable Directsound 2D/3D/EAX for applications, so it is not a good idea to disable them. These run at startup and in many cases you will be asked to allow the file to run on each startup. To eliminate that behavior and allow it on all bootups, open the file properties, and on the General tab click the "Unblock" button.


So now in System Configuration i now have my 2x old HsMgr Drivers 1x 32 bit and 1x 64 bit driver and also my two new ones. So the new freshly installed ones are ticked to boot on start up and my two old ones are un-ticked so what should i do with my old ones just leave them unticked or is there anyway to remove them?

^ Yes you can remove these, but make sure you delete the right ones - you can't undo the delete!

Download CCleaner: CCleaner - Download

When CCleaner is open, go to 'Tools' > 'Startup' - then choose what you want to delete and then press the delete button.

CCleaner is also good for cleaning temporary files and cleaning the registry. I highly recommend you keeping it on your system.

briand88 said:

So in reality it appears i caused myself my own pain in the ass, causing my own BSOD.

Also one more question I have a tri core CPU but noticed on startup it said only 3 cores were activated so I re activated the fourth is this something Tht would happen on a BSOD the CPU returning back to the 3 cores?

Apologies if you feel i am jumping the gun a bit.

Brian

^ If your PC is Tri-Core then it won't have a fourth core. :)

Hope this helps, let me know if you have any more questions.

briand88 said:

Thanks for all your help I really appreciate I will give this a bash when I go home later on today and well it's a quad core processor but for some reason the fourth core was locked when i purchased it and installed the CPU I unlocked the fourth through the bios screen after seeing a video online on how to do it .

If it is Quad-Core and it has locked the 4th core, this will be for safety reasons - maybe an in-built fail-safe in case of an over-clocking gone bad.

If it has locked out the core, leave it like that for now.

briand88 said:

MistUnleashed said:

briand88 said:

Thanks for all your help I really appreciate I will give this a bash when I go home later on today and well it's a quad core processor but for some reason the fourth core was locked when i purchased it and installed the CPU I unlocked the fourth through the bios screen after seeing a video online on how to do it .

If it is Quad-Core and it has locked the 4th core, this will be for safety reasons - maybe an in-built fail-safe in case of an over-clocking gone bad.

If it has locked out the core, leave it like that for now.

Ok I will revert it back but the fourth core has been unlocked for about 2 years and this is my first ever crash or BSOD incident so it was obviously caused by myself and disabling those drivers on startup why would a quad core have 1 disabled tho? When I bought it was advertised as a quad core it's an AMD Phenom II 965 Black Quad Core Processor Socket AM3 so why would it be disabled :S excuse my ignorance but seems to defeat the purpose of quad core.

I totally understand what you're saying!

My analysis of it was that it was a safe-guard. By all means go and re-enable it, just thought it would be safe to leave it as it is for now seen as though its working fine!

Personally I would leave it about 2 weeks before reverting, this is just to remove the possibility that the BSODing is due to your CPU.

CCleaner will show all 4 and whether they are disabled or enabled, it is up to you to select and delete the entries you do not want there.