1) Choose the SSD.
2) Tools, smart tests, short (2 minutes with my 250gb ssd)
3) Tools, smart tests, extended
2) Tools, smart tests, short (2 minutes with my 250gb ssd)
3) Tools, smart tests, extended
HDaudbus pops
- Thread starter shahinyp
- Start date
If all the RAM is occupied, you should see the PC is sluggish.
If it's this way, let hcidesign memtest instances do their work until 400% or more.
About sk hynix SSD, skip it.
If it's this way, let hcidesign memtest instances do their work until 400% or more.
About sk hynix SSD, skip it.
Not sure... Indeed these RAM tests should be ran over night.
Did all instances reach 400%?
Did you also try windows memory diagnostics?
Did you also try windows memory diagnostics?
No, they didn't, two of them were above 400% and the other four were about 300% and above.
And I didn't try windows memory diagnostic. I thought I supposed to use one of them. Should I try windows memory diagnostic now ? And how long it will take ? Should I run it over night ?
Also I must mention that I changed those psi values to default (from the cmd command and the one from regeditor wich you said in previous posts) but it makes no difference so I changed them back. At first when I changed them back the crack sounds were a little better but they came back like before. I don't know why sometimes it gets better when I change something (like changing drivers, psi values and windows) and after thet they keep back again.
And I didn't try windows memory diagnostic. I thought I supposed to use one of them. Should I try windows memory diagnostic now ? And how long it will take ? Should I run it over night ?
Also I must mention that I changed those psi values to default (from the cmd command and the one from regeditor wich you said in previous posts) but it makes no difference so I changed them back. At first when I changed them back the crack sounds were a little better but they came back like before. I don't know why sometimes it gets better when I change something (like changing drivers, psi values and windows) and after thet they keep back again.
Yes, try also Windows memtest.
It Will probably be ok... Then we'll try something else.
It Will probably be ok... Then we'll try something else.
I estimated about 8 hours with 6gb (4gb + 2gb) 1333MHz ddr3 ram sticks on an intel h61 MoBo, with test mix extended, cache on, 15 passes.
You have 16GB ddr4, hence it could get about 22 hours.
Maybe ddr4 is faster, I don't know...
You can try to lower it to 6 passes to short it to 9 hours (or less, if ddr4 is faster).
You have 16GB ddr4, hence it could get about 22 hours.
Maybe ddr4 is faster, I don't know...
You can try to lower it to 6 passes to short it to 9 hours (or less, if ddr4 is faster).
Ok.
What program are you using to get a system image?
Do you have a recovery media (usb or cd) tested on your pc (i.e., does it boot your pc)?
Have you created a system image?
What program are you using to get a system image?
Do you have a recovery media (usb or cd) tested on your pc (i.e., does it boot your pc)?
Have you created a system image?
Using Macrium Free to Backup or Image your drives
A trick to lower the system image size is to leave partition c: without any programs (installing them in d: or other partitions).
Therefore you'll have only windows system files on c: (and very few windows programs in "c:\program files" and "c:\program files (x86)").
In this way, I have to select only the efi/esp partition, ms partition, windows partition and recovery partition(s).
The image occupies between 15 and 20GB and I can put it in another partition (in another disk).
It would be better to put it in an external HDD/SSD.
The recovery media must be tested; it have to work if things go wrong.
If you have very important files, or programs, on other partitions and disks, it would be better to create a FULL system image.
Or to backup at least the important files.
In both these cases, it's better to put the backups in external disks.
A trick to lower the system image size is to leave partition c: without any programs (installing them in d: or other partitions).
Therefore you'll have only windows system files on c: (and very few windows programs in "c:\program files" and "c:\program files (x86)").
In this way, I have to select only the efi/esp partition, ms partition, windows partition and recovery partition(s).
The image occupies between 15 and 20GB and I can put it in another partition (in another disk).
It would be better to put it in an external HDD/SSD.
The recovery media must be tested; it have to work if things go wrong.
If you have very important files, or programs, on other partitions and disks, it would be better to create a FULL system image.
Or to backup at least the important files.
In both these cases, it's better to put the backups in external disks.
Sorry for not answering for such a time. I've just not had enough space for a system image so I ignored my problem for a while and just turned audio enhancement of :))
now I just want to say that I've seen this thread: System interrupts, Latency, HDaudbus.sys and according to this I turned one other MSI value to 1 (besides that one which we changed before) and the cracks are gone for now.
now I just want to say that I've seen this thread: System interrupts, Latency, HDaudbus.sys and according to this I turned one other MSI value to 1 (besides that one which we changed before) and the cracks are gone for now.
I.e., do you have two hdaudbus services/devices?
when I run this command : reg query HKLM\SYSTEM\CurrentControlSet\Enum\PCI\ /s /f hdaudbus, I got two:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_10DE&DEV_1AEB&SUBSYS_3FFC17AA&REV_A1\4&1f1ffad1&0&0108
DeviceDesc REG_SZ @hdaudbus.inf,%hdaudio.devicedesc%;High Definition Audio Controller
Service REG_SZ HDAudBus
Mfg REG_SZ @hdaudbus.inf,%msft%;Microsoft
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_8086&DEV_A348&SUBSYS_380F17AA&REV_10\3&11583659&0&FB
DeviceDesc REG_SZ @hdaudbus.inf,%hdaudio.devicedesc%;High Definition Audio Controller
Service REG_SZ HDAudBus
Mfg REG_SZ @hdaudbus.inf,%msft%;Microsoft
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_10DE&DEV_1AEB&SUBSYS_3FFC17AA&REV_A1\4&1f1ffad1&0&0108
DeviceDesc REG_SZ @hdaudbus.inf,%hdaudio.devicedesc%;High Definition Audio Controller
Service REG_SZ HDAudBus
Mfg REG_SZ @hdaudbus.inf,%msft%;Microsoft
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_8086&DEV_A348&SUBSYS_380F17AA&REV_10\3&11583659&0&FB
DeviceDesc REG_SZ @hdaudbus.inf,%hdaudio.devicedesc%;High Definition Audio Controller
Service REG_SZ HDAudBus
Mfg REG_SZ @hdaudbus.inf,%msft%;Microsoft
Hi xilolee. Can I tack onto this and ask for assistance with a similar issue? I've been having these crackles and pops since March 2020, and HDAudBus.sys showed up for the first time in my LatencyMon report, leading me to this thread which seems to have a similar issue to mine. I want to see if I can sort this out as well. I have been trying to do so since that summer (I had to wait as I was finishing my final term of my second run at college, when the pandemic started, and was swamped with things to do at the time). Would like to PM regarding fixing this if possible but I can't start a PM unless I post some posts first.
An interesting quirk is that my PC has stopped being able to use the High Definition Audio Driver. It doesn't work at all, so I am forced to use Realtek to get any audio. This started with the update to, I think, build 2010 (1903 is where the crackles and pops started). Until then I could use either driver. I wonder if there might be something related to this with my PC, too. I really don't want to have further updates in version until this is sorted out as I suspect a registry entry to deal with a driver might be the necessary fix.
An interesting quirk is that my PC has stopped being able to use the High Definition Audio Driver. It doesn't work at all, so I am forced to use Realtek to get any audio. This started with the update to, I think, build 2010 (1903 is where the crackles and pops started). Until then I could use either driver. I wonder if there might be something related to this with my PC, too. I really don't want to have further updates in version until this is sorted out as I suspect a registry entry to deal with a driver might be the necessary fix.
Has Sysnative Forums helped you? Please consider donating to help us support the site!